Re: SSL support using other packages other than openSSL ?
Ok, I sent this to the list the other day, but it hasn't shown up yet?? Here's another try - sorry if people get duplicates. I'm getting pretty frustrated with the Axis C++ binary installation. I'm going to go step-by-step through the installation instructions provided. Sorry for the long email - think of it as a complete newbie trying to learn your system. For what it's worth, I'm working on a Fedora Core 5 system I downloaded axis-c-linux-current-bin.tar several days ago and unpacked it to reveal axis-c-1.6b-Linux-trace-bin Then I went to axis-c-1.6b-Linux-trace-bin/docs/install-guide.html and found the instructions for server install config. Step 1: Download Axis C++ Done - unpacked to /home/myname/WebServices/axis-c-1.6b-Linux-trace-bin Step 2: Install Apache Web Server Done - I have httpd-2.2.2-1.3 installed via RPM and modules are supported. 3. Install Xerces C++ (2.2.0) Done - I then downloaded installed xerces-c-src_2_8_0 This yielded the following libraries: /usr/local/lib/libxerces-c.so - libxerces-c.so.28.0 /usr/local/lib/libxerces-c.so.28 - libxerces-c.so.28.0 /usr/local/lib/libxerces-c.so.28.0 /usr/local/lib/libxerces-depdom.so - libxerces-depdom.so.28.0 /usr/local/lib/libxerces-depdom.so.28 - libxerces-depdom.so.28.0 /usr/local/lib/libxerces-depdom.so.28.0 4. Configure environment variables Done: export AXISCPP_DEPLOY=/home/myname/WebService/axis-c-1.6b-Linux-trace-bin/ export LD_LIBRARY_PATH=/usr/local/lib:$AXISCPP_DEPLOY/lib (There appears to be a missing linefeed in the 3rd line of this section) 5. Configure Engine Wide Settings in Configuration File Ok, here is some confusion. I read the following instruction: A sample configuration file is installed in $AXISCPP_DEPLOY/etc I understood earlier that AXISCPP_DEPLOY was to point to the directory I unpacked the tarball to. In this case /home/myname/WebServices/axis-c-1.6b-Linux-trace-bin But there is no etc directory here?? I did find an etc directory under /home/myname/WebServices/axis-c-1.6b-Linux-trace-bin/deploy. So, the first question: ** What should AXISCPP_DEPLOY point to?? ** Should it point to the unpacked directory, or the 'deploy' directory with it? Or did I miss something above? I'll take a guess and re-assign the AXISCPP_DEPLOY environment variable to the deploy directory within the top-level directory: export AXISCPP_DEPLOY=/home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/ export LD_LIBRARY_PATH=/usr/local/lib:$AXISCPP_DEPLOY/lib So now I look in $AXISSCPP_DEPLOY/etc ... there is no axiscpp.conf file present, as stated in your instructions?? There is a axiscpp.conf_linux file, with a structure similar to what is described in the docs, so I copy it to axiscpp.conf Not to much of a leap, but it would be nice if the docs pointed this out. cp $AXISCPP_DEPLOY/etc/axiscpp.conf_linux $AXISCPP_DEPLOY/etc/axiscpp.conf I go in and take a look ... and all of the paths reference /usr/local/axiscpp_deploy/. There is nothing in the server install instructions which says anything about copying stuff to /usr/local/axiscpp_deploy. Why not use the $AXISCPP_DEPLOY environment variable? So I change the paths to point to /home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/ Now my config file looks like this: LogPath:/home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/log/AxisLog WSDDFilePath:/home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/etc/server.wsdd ClientLogPath:/home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/log/AxisClientLog XMLParser:/home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/lib/libaxis_xmlparser.so Transport_http:/home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/lib/libaxis2_transport.so Just for grins, I take a look for this stuff: LogPath:/home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/log/AxisLog No such file or directory - ok, I'll assume it creates this file on the fly WSDDFilePath:/home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/etc/server.wsdd No such file or directory - looking I see the following: server.wsdd_linux server.wsdd_linux_handler I'm guessing this is similar to the axiscpp.conf_linux stuff, but which to rename??? *** What is server.wsdd? Candidates would appear to be: server.wsdd_linux server.wsdd_linux_handler *** I flip a coin and pick server.wsdd_linux cp deploy/etc/server.wsdd_linux deploy/etc/server.wsdd
Re: SSL support using other packages other than openSSL ?
Eric, Have not really worked on the server-side of thingsthe client is (latest code in SVN) is very stable. I would first urge you to build new binaries using ant from the code in SVN, the binaries you are using are very old and buggy. AXISCPP_DEPLOY should point to the directory containing etc/axiscpp_conf. For example, if I have the following /client/etc/axiscpp.conf Then AXISCPP_DEPLOY should point to /client. If I have time I will try to go through the server-step process and update the docs. I do plan on releasing newer binaries, but currently fixing bugs so I have no set time-table. Nadir Amra Eric R George [EMAIL PROTECTED] wrote on 08/13/2008 10:27:32 AM: Ok, I sent this to the list the other day, but it hasn't shown up yet?? Here's another try - sorry if people get duplicates. I'm getting pretty frustrated with the Axis C++ binary installation. I'm going to go step-by-step through the installation instructions provided. Sorry for the long email - think of it as a complete newbie trying to learn your system. For what it's worth, I'm working on a Fedora Core 5 system I downloaded axis-c-linux-current-bin.tar several days ago and unpacked it to reveal axis-c-1.6b-Linux-trace-bin Then I went to axis-c-1.6b-Linux-trace-bin/docs/install-guide.html and found the instructions for server install config. Step 1: Download Axis C++ Done - unpacked to /home/myname/WebServices/axis-c-1.6b- Linux-trace-bin Step 2: Install Apache Web Server Done - I have httpd-2.2.2-1.3 installed via RPM and modules are supported. 3. Install Xerces C++ (2.2.0) Done - I then downloaded installed xerces-c-src_2_8_0 This yielded the following libraries: /usr/local/lib/libxerces-c.so - libxerces-c.so.28.0 /usr/local/lib/libxerces-c.so.28 - libxerces-c.so.28.0 /usr/local/lib/libxerces-c.so.28.0 /usr/local/lib/libxerces-depdom.so - libxerces-depdom.so.28.0 /usr/local/lib/libxerces-depdom.so.28 - libxerces-depdom.so.28.0 /usr/local/lib/libxerces-depdom.so.28.0 4. Configure environment variables Done: export AXISCPP_DEPLOY=/home/myname/WebService/axis-c-1.6b- Linux-trace-bin/ export LD_LIBRARY_PATH=/usr/local/lib:$AXISCPP_DEPLOY/lib (There appears to be a missing linefeed in the 3rd line of this section) 5. Configure Engine Wide Settings in Configuration File Ok, here is some confusion. I read the following instruction: A sample configuration file is installed in $AXISCPP_DEPLOY/etc I understood earlier that AXISCPP_DEPLOY was to point to the directory I unpacked the tarball to. In this case /home/myname/WebServices/axis-c-1.6b-Linux-trace-bin But there is no etc directory here?? I did find an etc directory under /home/myname/WebServices/axis-c-1.6b-Linux-trace-bin/deploy. So, the first question: ** What should AXISCPP_DEPLOY point to?? ** Should it point to the unpacked directory, or the 'deploy' directory with it? Or did I miss something above? I'll take a guess and re-assign the AXISCPP_DEPLOY environment variable to the deploy directory within the top-level directory: export AXISCPP_DEPLOY=/home/myname/WebService/axis-c-1.6b- Linux-trace-bin/deploy/ export LD_LIBRARY_PATH=/usr/local/lib:$AXISCPP_DEPLOY/lib So now I look in $AXISSCPP_DEPLOY/etc ... there is no axiscpp.conf file present, as stated in your instructions?? There is a axiscpp.conf_linux file, with a structure similar to what is described in the docs, so I copy it to axiscpp.conf Not to much of a leap, but it would be nice if the docs pointed this out. cp $AXISCPP_DEPLOY/etc/axiscpp.conf_linux $AXISCPP_DEPLOY/etc/axiscpp.conf I go in and take a look ... and all of the paths reference /usr/local/axiscpp_deploy/. There is nothing in the server install instructions which says anything about copying stuff to /usr/local/axiscpp_deploy. Why not use the $AXISCPP_DEPLOY environment variable? So I change the paths to point to /home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/ Now my config file looks like this: LogPath:/home/myname/WebService/axis-c-1.6b-Linux-trace-bin/deploy/log/AxisLog WSDDFilePath:/home/myname/WebService/axis-c-1.6b-Linux-trace- bin/deploy/etc/server.wsdd ClientLogPath:/home/myname/WebService/axis-c-1.6b-Linux-trace- bin/deploy/log/AxisClientLog XMLParser:/home/myname/WebService/axis-c-1.6b-Linux-trace- bin/deploy/lib/libaxis_xmlparser.so Transport_http:/home/myname/WebService/axis-c-1.6b-Linux-trace- bin/deploy/lib/libaxis2_transport.so Just for
Re: SSL support using other packages other than openSSL ?
Hi Samisa, Thanks for your reply. In that case, which module or files are implementing ssl related stuff? Is that all under src\core\transport\http\sender\ssl for a client (sender)? Is there any document for this? Thanks much! Ray --- On Wed, 8/13/08, Samisa Abeysinghe [EMAIL PROTECTED] wrote: From: Samisa Abeysinghe [EMAIL PROTECTED] Subject: Re: SSL support using other packages other than openSSL ? To: Apache AXIS C User List axis-c-user@ws.apache.org Date: Wednesday, August 13, 2008, 4:38 AM Raymond Zhou wrote: Hi, All, I understand that AXIS2/c depends on openSSL to support SSL communication. I was wondering if it is possible, or if any other people have tried, to use other packages other than openSSL to do so. My company has licensed another product for support security-related features and this product support SSL, so we would prefer using this product instead of openSSL to aviod potential IP issues (We need to redistribute the product). Well, I think you can replace the current openSSL related implementations with whatever the library you wish to use. There is no abstraction layer as such for SSL related implementation, but with some effort, you would be able to separate this out for your custom implementation. Thanks, Samisa... Thanks! Ray No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.1/1605 - Release Date: 8/11/2008 4:59 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SSL support using other packages other than openSSL ?
Raymond Zhou wrote: Hi, All, I understand that AXIS2/c depends on openSSL to support SSL communication. I was wondering if it is possible, or if any other people have tried, to use other packages other than openSSL to do so. My company has licensed another product for support security-related features and this product support SSL, so we would prefer using this product instead of openSSL to aviod potential IP issues (We need to redistribute the product). Well, I think you can replace the current openSSL related implementations with whatever the library you wish to use. There is no abstraction layer as such for SSL related implementation, but with some effort, you would be able to separate this out for your custom implementation. Thanks, Samisa... Thanks! Ray No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.1/1605 - Release Date: 8/11/2008 4:59 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
