You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ro...@apache.org on 2004/10/12 07:09:44 UTC
cvs commit: ws-axis/c/docs wininstall-guide.pdf wininstall-guide.html lininstall-guide.html
roshan 2004/10/11 22:09:44
Modified: c/docs wininstall-guide.pdf wininstall-guide.html
lininstall-guide.html
Log:
Edited lininstall Guide. Edited by Rangika
Revision Changes Path
1.2 +157 -163 ws-axis/c/docs/wininstall-guide.pdf
<<Binary file>>
1.3 +50 -38 ws-axis/c/docs/wininstall-guide.html
Index: wininstall-guide.html
===================================================================
RCS file: /home/cvs/ws-axis/c/docs/wininstall-guide.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wininstall-guide.html 20 Sep 2004 06:08:19 -0000 1.2
+++ wininstall-guide.html 12 Oct 2004 05:09:44 -0000 1.3
@@ -41,7 +41,7 @@
-> samples<br>
<br>
-2.The folder �bin� contains sample clients and other dlls needed to run the Axis c++ server
+2.The folder �bin� contains sample clients and other dlls which are needed to run the Axis c++ server
<br> <br>
3.Inside the "deploy" folder following sub folders exist
@@ -83,43 +83,43 @@
5. Set environment variable AXISCPP_DEPLOY to point to above folder.<br>
<br>
-6. Add AXIS_FOLDER/libs to the PATH environment variable.<br>
+6. Add AXIS_FOLDER/lib to the PATH environment variable.<br>
<br>
7. Edit Apache configuration file httpd.conf located in APACHE_FOLDER/conf and add following lines at the end.<br>
<br>
LoadModule axis_module modules/AXISMODULE<br>
-<Location><br>
+<Location/axis><br>
SetHandler axis <br>
<\Location><br> <br>
-Where AXISMODULE is either mod_axis.dll for apache 1.3.X or mod_axis2.dll for apache 2.X. <br>
+AXISMODULE is either mod_axis.dll for apache 1.3.X or mod_axis2.dll for apache 2.X. <br>
<br>
-8. Copy AXISMODULE from the AXIS_EXTRACT/bin folder to APACHE_FOLDER/modules folder.<br> <br>
+8. Copy AXISMODULE from AXIS_EXTRACT/bin folder to APACHE_FOLDER/modules folder.<br> <br>
-9. Copy AxisServer.dll and AxisTransport.dll from the AXIS_EXTRACT/bin folder to AXIS_FOLDER/libs <br>
+9. Copy AxisServer.dll and AxisTransport.dll from AXIS_EXTRACT/bin folder to AXIS_FOLDER/lib <br>
<br>
-10.If you want to use the Expat parser with Axis C++,rename AxisXMLParser_Expat.dll from AXIS_EXTRACT/bin folder to AxisXMLParser.dll and copy it to AXIS_FOLDER/libs <br>
-<br> </p>
+10.If you want to use the Expat parser with Axis C++, rename AxisXMLParser_Expat.dll from AXIS_EXTRACT/bin folder to AxisXMLParser.dll and copy it to AXIS_FOLDER/lib <br>
+<br>
+11.If you want to use the Xerces parser with Axis C++, rename AxisXMLParser_Xerces.dll from AXIS_EXTRACT/bin folder to AxisXMLParser.dll and copy it to AXIS_FOLDER/lib </p>
+<br>
<p><b>Installing the Expat XML parser </b></p>
-<p>If you decide to use the Expat parser you need to install the Expat parser. Download the Expat-1.95.7 binary version from <a href="http://sourceforge.net/projects/expat/">http://sourceforge.net/projects/expat/</a> <br>
-Extract the Expat binaries to a folder Called Expat ,we will refer to this folder as [EXPAT_EXTRACT]. <br>
-Copy libexpat.dll file from [EXPAT_EXTRACT]\Libs to [AXISCPP_DEPLOY]/libs/ <br> <br>
-If you want to use the Xerces parser with Axis C++, rename AxisXMLParser_Xerces.dll from AXIS_EXTRACT/bin folder to AxisXMLParser.dll and copy it to AXIS_FOLDER/libs </p>
-
+<p>If you decide to use the Expat parser you need to install the Expat parser. Download the Expat-1.95.7 binary version from <a href="http://sourceforge.net/projects/expat/">http://sourceforge.net/projects/expat/</a> <br> <br>
+Extract the Expat binaries to a folder Called Expat ,we will refer to this folder as [EXPAT_EXTRACT]. <br> <br>
+Copy libexpat.dll file from [EXPAT_EXTRACT]\Libs to [AXISCPP_DEPLOY]/lib/ <br> <br> <br>
<p><b>Installing the Xerces XML parser</b>
-<br>
+<br> <br>
If you decide to use the Xerces parser you need to install the Xerces parser. Download the Xerces-C 2.2.0( 32 bit binary release)from:
-<a href="http://xml.apache.org/xerces-c/download.cgi">http://xml.apache.org/xerces-c/download.cgi</a> <br>
-<br>
-Extract the Xerces-C 2.2.0 binary version. We will refer to this folder as [XERCES_EXTRACT]. Copy xerces-c_2_2_0.dll from [XERCES_EXTRACT]/bin/ to [AXISCPP_DEPLOY]/libs/ <br>
+<a href="http://xml.apache.org/xerces-c/download.cgi">http://xml.apache.org/xerces-c/download.cgi</a> <br> <br>
+
+Extract the Xerces-C 2.2.0 binary version. We will refer to this folder as [XERCES_EXTRACT]. Copy xerces-c_2_2_0.dll from [XERCES_EXTRACT]/bin/ to [AXISCPP_DEPLOY]/lib/ <br>
<br> <br>
-11. Open the AXIS_FOLDER/axiscpp.conf_win for editing. The contents of the file will look as follows.<br> <br>
+12. Open the AXIS_FOLDER/axiscpp.conf_win for editing. The contents of the file will look as follows.<br> <br>
LogPath:XXXX <br>
WSDDFilePath:YYYY <br>
@@ -133,24 +133,33 @@
WSDDFilePath: [APACHE_HOME]\Axis\conf\WSDDFILE <br>
<br>
-WSDDFILE is [APACHE_HOME]\Axis\conf\server.wsdd for Apache 1.3 and Apache 2. (There will be three wsdd files in the [APACHE_HOME]\Axis\conf\ rename the relevant wsdd file of your platform to server.wsdd).<br>
-
-Also in order to run the provided samples do the following.<br>
-Open server.wsdd for editing. For each service element, locate the element "parameter", having the value "classname" for the "name" attribute.
-Change the value of the "value" attribute, to have the absolute path to the indicated webservice.dll in that value. <br> <br>
+WSDDFILE is located at [APACHE_HOME]\Axis\conf\server.wsdd for Apache 1.3 and Apache 2. (There will be three wsdd files in the [APACHE_HOME]\Axis\conf\ rename the relevant wsdd file of your platform to server.wsdd).<br> <br>
-Rename AXIS_FOLDER/axiscpp.conf_win to AXIS_FOLDER/axiscpp.conf <br> <br>
+Also in order to run the provided samples do the following.<br> <br>
+Open server.wsdd for editing. For each service element, locate the element "parameter", which has the value "classname" for the "name" attribute.
+Give the absolute path of the indicated webservice.dll in the "value" attribute <br> <br>
+Rename axiscpp.conf_win which is in AXIS_FOLDER to axiscpp.conf <br> <br>
-12. Restart the apache web server. If you have done correctly apache server should start without giving any error.</p>
+13. Restart the apache web server. If you have done correctly apache server will start without giving any error.</p>
<br>
<p><b>apache 1.3.X : </b> <br> <br>
It is recommended to start apache 1.3.X as "apache -k start" on the command line <br> <br>
<b>apache 2.X :</b> <br> <br>
-While testing the apache 2 module a problem was noted with the apache 2 web server, in that the webserver takes about 98% of CPU time and the server does not even serve the startup page. The workaround for this is to start the apache web server as "apache -X" to make it run single threaded. While this is sufficient to test the apache 2 module this problem needs to be investigated further. <br> <br>
+While testing the apache 2 module a problem was noted with the apache 2 web server, in that the webserver takes about 98% of CPU time and the server does not even serve the startup page. <br> The workaround for this is to start the apache web server as "apache -X" to make it run single threaded. <br> While this is sufficient to test the apache 2 module this problem needs to be investigated further.<br> <br>(However on a different machine, when I simply run the apache2 executable (version
+2.0.49) without any
+arguments, as, "apache" on windows 2000 professional, service pack 5,
+with/without Axis C++ it seems to be working fine. <br>
+
+But in this machine the apache could not be started as "apache -k start" (i.e. as a
+service). It
+simply exists and does not start. The 98% CPU usage scenario cannot be reproduced in
+this machine. <br>
+It could happen with some other apache 2 versions or in different service packs.
+) <br> <br>
-10. Open an internet browser and check http://localhost/axis. If the module has loaded properly then you should get the axis welcome page with a listing of deployed web services.<br> <br>
+14. Open an internet browser and check http://localhost/axis. If the module has loaded properly then you will get the axis welcome page with a listing of deployed web services.<br> <br>
<p><a name=#simpleaxis"></a></p>
@@ -163,14 +172,14 @@
3. Inside the extracted folder AXIS_EXTRACT there is a sub folder called deploy. Copy whole deploy folder to SIMPLE_AXIS_SERVER_FOLDER.<br> <br>
4. Rename copied "deploy" folder to "Axis". Lets say this folder to be AXIS_FOLDER.<br> <br>
5. Set environment variable AXISCPP_DEPLOY to point to above folder.<br> <br>
-6. Copy the exe SimpleAxisServer.exe from AXIS_EXTRACT/bin to the SIMPLE_AXIS_SERVER_FOLDER. <br> <br>
-7. Copy the content of AXIS_FOLDER/libs to the SIMPLE_AXIS_SERVER_FOLDER.<br> <br>
-8. Start the SimpleAxisServer by providing the port to which operate. (eg: c:\SimpleAxisServer>SimpleAxisServer 80) </p>
+6. Copy the SimpleAxisServer.exe from AXIS_EXTRACT/bin to the SIMPLE_AXIS_SERVER_FOLDER. <br> <br>
+7. Copy the content of AXIS_FOLDER/lib to the SIMPLE_AXIS_SERVER_FOLDER.<br> <br>
+8. Start the SimpleAxisServer by providing the port to which it operates.(eg: c:\SimpleAxisServer>SimpleAxisServer 80) </p>
<p><a name="#samples"></a></p>
<h1>Running Provided Samples</h1>
-<p>If Axis installation is a complete success, following sample web services and handlers have already been installed successfully.<br> <br>
+<p>If Axis installation is a complete success, then the following sample web services and handlers have been installed successfully.<br> <br>
You will find the built console applications at AXIS/c/bin directory. Following are the built .exe files. <br> <br>
1.base.exe <br>
@@ -178,12 +187,13 @@
3.doclitbase.exe <br>
4.doclitgroupB.exe <br>
5.groupB.exe <br>
-6.cgroupB <br>
+6.cgroupB.exe <br>
<br>
In order to run these samples you should have AxisClient.dll in the PATH environment variable or in the same directory where the client .exe is located.<br> <br>
-You can run the provided client programs to confirm whether the Axis cpp server and clients are working fine. To run this sample client applications you need to have the path to libexapt.dll in the "PATH" environment variable or libexapt.dll should be placed where the apache.exe is.<br>
+You can run the provided client programs to confirm whether the Axis cpp server and clients are working fine. <br> <br>
+To run these sample client applications you need to have the path to libexpat.dll in the "PATH" environment variable or libexpat.dll should be placed where the apache.exe is.(libexpat.dll can be found in [EXPAT_EXTRACT\libs)<br> <br>
<b> Note: These sample clients are compiled with the assumption that server is running at localhost port 80.</b><br>
<br>
@@ -191,19 +201,21 @@
<h1>Using Visual C++ to play with provided samples.</h1>
-<p>In your AXIS_EXTRACT/samples folder you have the samples. If you are using Visual C++ you can open the workspace file for client applications AXIS_EXTRACT\c\samples\client\interoptests\interoptests.dsw and For Deployable webservices, AXIS_EXTRACT\c\samples\server\interoptests\interoptests.dsw and play with them. There are seven projects in the workspace.
-<br> <br>
+<p>In your AXIS_EXTRACT/samples folder you have the samples.<br> <br>
+ If you are using Visual C++ you can open the workspace file for client applications which are in AXIS_EXTRACT\c\samples\client\interoptests\interoptests.dsw <br> <br>
+ Deployable webservices are in AXIS_EXTRACT\c\samples\server\interoptests\interoptests.dsw and you can play with them. <br> <br>
+There are seven projects in the workspace.
+<br> <br> </p>
<p><a name="#writews"></a></p>
<h1>Writing your web services and client applications using Axis C++.</h1>
-<p>For writing your own web services and client applications see the <a href="winuser-guide.html"><b>Windows User Guide</a></b>
-</p>
+<p>For writing your own web services and client applications see the <a href="winuser-guide.html"><b>Windows User Guide</a></b> </p>
+
<div id="pdf" align="right">
<a href="wininstall-guide.pdf"><img alt="PDF" src="../skin/images/pdfdoc.gif" class="skin"><br>
PDF</a>
-
1.4 +76 -78 ws-axis/c/docs/lininstall-guide.html
Index: lininstall-guide.html
===================================================================
RCS file: /home/cvs/ws-axis/c/docs/lininstall-guide.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- lininstall-guide.html 8 Oct 2004 08:24:58 -0000 1.3
+++ lininstall-guide.html 12 Oct 2004 05:09:44 -0000 1.4
@@ -19,7 +19,7 @@
<a href="#What">What You Need</a>
</li>
<li>
-<a href="Install">Installing Axis C++</a>
+<a href="#Install">Installing Axis C++</a>
</li>
<br>
@@ -44,24 +44,24 @@
<h3>What You Need</h3>
</div>
-<p>You need few helper libraries for parsing XML, WSDL processing and
+<p>You need a few helper libraries for parsing XML, WSDL processing and
introspection. You need to have the following in order to run Axis C++
engine.</p>
- <a href="http://httpd.apache.org/download.cgi">Apache web server </a> (2.0.x or 1.3.x) - You
+<p> <a href="http://httpd.apache.org/download.cgi">Apache web server </a> (2.0.x or 1.3.x) - You
need to have Apache built with module so support, hence you need to
-have source of Apache web server.<br>
+have the source of Apache web server.<br>
-Axis C++ uses Apache web server to host services.<br>
+Axis C++ uses Apache web server to host services.<br> </p>
-<br>
+<br>
- <a href="http://sourceforge.net/projects/expat/">Expat (1.95.7) </a> and/or
-<a href="http://archive.apache.org/dist/xml/xerces-c/Xerces-C_2_2_0/">Xerces C++ (2.2.0)</a> XML parser(s)<br>
+<p> <a href="http://sourceforge.net/projects/expat/">Expat (1.95.7) </a> and/or
+<a href="http://archive.apache.org/dist/xml/xerces-c/Xerces-C_2_2_0/">Xerces C++ (2.2.0)</a> XML parser(s)<br> <br>
Axis C++ needs an XML parser to parse SOAP messages and WSDD files. It
-has a parser abstraction layer that help users select/switch between
-parsers. However only once parser library could be used at a time. Currently Expat and Xerces parsers are supported by Axis C++.<br>
+has a parser abstraction layer that helps users to select/switch between
+parsers. However only one parser library could be used at a time. Currently Expat and Xerces parsers are supported by Axis C++.<br></p>
<br>
@@ -73,33 +73,33 @@
</div>
-1. Install Apache web server. In case you already have an Apache
-installation, make sure that 'so modules' are enabled. This is because
-Axis C++ server engine is implemented as an 'so module'. (For Apache
+<p>1. Install Apache web server. In case you have already installed Apache
+, make sure that 'so modules' are enabled. <br> This is because
+Axis C++ server engine is implemented as a 'so module'. (For Apache
1.3.x use --enable-module=so; for Apache 2.0.x use --enable-so when
-configuring. See Apache web server documentation for more details)<br>
+configuring. See Apache web server documentation for more details)</p> <br>
<br>
-2. Install Expat (1.95.7) and/or Xerces C++ (2.2.0) depending on your
+<p>2. Install Expat (1.95.7) and/or Xerces C++ (2.2.0) depending on your
parser preferences. See the respective parser's documentation for
-installation instructions. <br>
+installation instructions.</p> <br>
<br>
-3. <a href="http://ws.apache.org/axis/cpp/download.html">Download Axis C++</a> source or binary distribution and extract the package.<br>
+<p>3. <a href="http://ws.apache.org/axis/cpp/download.html">Download Axis C++</a> source or binary distribution and extract the package.</p><br>
<br>
-4. Define the following environment variables.<br><b>
+<p>4. Define the following environment variables.<br> <br>
-AXISCPP_HOME="Path to Axis C++ source or binary extracted folder"</b><br>
+<b>AXISCPP_HOME="Path to Axis C++ source or binary extracted folder"</b><br>
e.g. <i><b>AXISCPP_HOME="/my/home/axiscpp"</b></i><br>
<br><b>
-AXISCPP_DEPLOY="Path to folder where you want to install Axis C++"</b><br>
+AXISCPP_DEPLOY="Path to the folder where you want to install Axis C++"</b><br>
e.g. <i><b>AXISCPP_DEPLOY="/usr/local/axiscpp_deploy"<br>
</b></i>
@@ -111,24 +111,24 @@
<br><b>
-export AXISCPP_HOME AXISCPP_DEPLOY LD_LIBRARY_PATH</b><br>
+export AXISCPP_HOME AXISCPP_DEPLOY LD_LIBRARY_PATH</b> </p> <br>
<br>
-5. Build Axis C++ (If you downloaded Axis C++ binaries, you can skip this step)<br><b>
+<p>5. Build Axis C++ (If you have downloaded Axis C++ binaries, you can skip this step)<br> <br> <b>
-cd $AXISCPP_HOME<br>
+cd $AXISCPP_HOME </b> <br> <br>
-./configure --prefix=$AXISCPP_DEPLOY --with-apache2=/path/to/Apache2 --with-xercesc=/path/to/xerces-c<br>
+<b>./configure --prefix=$AXISCPP_DEPLOY --with-apache2=/path/to/Apache2 --with-xercesc=/path/to/xerces-c </b> <br> <br>
-make <br>
+<b> make </b> <br> <br>
-make install</b><br>
+<b> make install</b><br> <br>
<br>
@@ -143,132 +143,132 @@
specified directory given in prefix option<br>
<br>
-You need global access rights to Axis C++ deploy folder to make sure Axis C++ work properly.<br>
+You need global access rights to the Axis C++ deploy folder to make sure that Axis C++ works properly.<br> <br>
-<i><b>chmod -R 777 $AXISCPP_DEPLOY</b></i><br>
+<i><b>chmod -R 777 $AXISCPP_DEPLOY</b></i> </p> <br>
<br>
-6. Configure Apache module<br>
-Note: to execute the following steps, you may need to have super user rights on your machine.<br>
+<p>6. Configure Apache module<br> <br>
+<b>Note:</b> to execute the following steps, you may need to have super user rights on your machine.<br>
-Now you need to add to edit
+Now you need to edit
<b>httpd.conf</b> file in <path to Apache web server installation>/conf
-and add the following lines at the bottom of that file (assuming you
+by adding the following lines at the bottom of that file (assuming you
are using Apache 2.0.x):<br>
<br>
<b>LoadModule axis_module modules/libaxiscpp_mod2.so</b><br>
-<b><Location /axis><br>
-</b><b>SetHandler axis<br>
-</b><b></Location><br>
+<b><Location /axis></b><br>
+<b>SetHandler axis </b> <br>
+<b></Location></b><br>
<br>
-</b>For Apache1.3.x LoadModule line should read as:<br>
+For Apache1.3.x LoadModule line should read as:<br>
-<b>LoadModule axis_module libexec/libaxiscpp_mod.so</b><br>
+<b>LoadModule axis_module libexec/libaxiscpp_mod.so</b> </p> <br>
<br>
-7. Configure server deployment descriptor file<br>
+<p>7. Configure server deployment descriptor file<br> <br>
Now you need the server deployment descriptor (server.wsdd) to deploy server samples you built.<br>
-There is a sample deployment descriptor called server.wsdd_linux in $AXISCPP_DEPLOY/etc to help deploy samples.<br>
+There is a sample deployment descriptor called server.wsdd_linux in $AXISCPP_DEPLOY/etc to help to deploy samples.<br>
If you edit this file to your requirements then when you run step 9 it will be turned into server.wsdd. If you don't
-use scripts as described in step 9 then just rename server.wsdd_linux into server.wsdd after your changes.
+use scripts as described in step 9 then just rename server.wsdd_linux to server.wsdd after doing your changes.
-server.wsdd file is an XML file, and the contents are self descriptive.<br>
+server.wsdd file is an XML file, and the contents are self descriptive. </p> <br>
<br>
-8. Set engine wide settings in configuration file<br>
+<p>8. Set engine wide settings in configuration file<br> <br>
Axis C++ uses a configuration file to let the user specify preferences
such as log file locations, transport and parser libs to be used and
-location of deployment descriptor files. A sample configuration file
+location of deployment descriptor files. <br> A sample configuration file
named axiscpp.conf_linux is installed in $AXISCPP_DEPLOY/etc folder. Edit this
-file to your reqirements.When you execute step 9 this file will be turned
+file to your requirements.<br> When you execute step 9 this file will be turned
into axiscpp.conf. If you don't use scripts as described in step 9 then just rename
-axiscpp.conf_linux into axiscpp.conf after your changes<br>
+axiscpp.conf_linux to axiscpp.conf after your changes<br>
<br>
-Configuration file has the following <b>Syntax:</b><br>
+Configuration file has the following <b>Syntax:</b> </p> <br>
-<b>The comment character is '#'<br>
+<p> <b>The comment character is '#'</b><br> <br>
-WSDDFilePath: The path to the server wsdd file<br>
-ClientWSDDFilePath:The path to the client wsdd<br>
-LogPath: The path to the Axis C++ server log<br>
+<b>WSDDFilePath: The path to the server wsdd file</b><br> <br>
+<b>ClientWSDDFilePath:The path to the client wsdd</b><br> <br>
+<b>LogPath: The path to the Axis C++ server log</b><br> <br>
-ClientLogPath: The path to the Axis C++ client log<br>
+<b>ClientLogPath: The path to the Axis C++ client log</b><br> <br>
-Transport_http: The HTTP transport library<br>
+<b>Transport_http: The HTTP transport library</b><br> <br>
-XMLParser: The XML parser library</b>
+<b>XMLParser: The XML parser library</b>
-<b><br>
<br>
-</b>A sample <b>axiscpp.conf</b> file:<br>
+<br>
+A sample <b>axiscpp.conf</b> file: </p> <br>
-<p><b>LogPath:/usr/local/axiscpp_deploy/log/AxisLog<br>
+<p><b>LogPath:/usr/local/axiscpp_deploy/log/AxisLog</b> <br> <br>
-WSDDFilePath:/usr/local/axiscpp_deploy/etc/server.wsdd<br>
+<b>WSDDFilePath:/usr/local/axiscpp_deploy/etc/server.wsdd </b> <br> <br>
-ClientLogPath:/usr/local/axiscpp_deploy/log/AxisClientLog<br>
+<b>ClientLogPath:/usr/local/axiscpp_deploy/log/AxisClientLog</b> <br> <br>
-XMLParser:/usr/local/axiscpp_deploy/lib/libaxis_xercesc.so<br>
+<b>XMLParser:/usr/local/axiscpp_deploy/lib/libaxis_xercesc.so</b> <br> <br>
-Transport_http:/usr/local/axiscpp_deploy/lib/libaxis2_transport.so</b></p>
+<b>Transport_http:/usr/local/axiscpp_deploy/lib/libaxis2_transport.so</b></p>
<br>
-9. deploying in apache
+<p>9. Deploying in apache </p>
-<p>Now we need to copy apache module(libaxiscpp_mod2.so for apache2 and
+<p>Now we need to copy apache module (libaxiscpp_mod2.so for apache2 and
libaxiscpp_mod.so for apache) to the correct places and start apache. To
do that you can find scripts written in $AXISCPP_DEPLOY/bin.<p> <br>
-<b>cd $AXISCPP_DEPLOY/bin </b> <br>
+<b>cd $AXISCPP_DEPLOY/bin </b> <br> <br>
-To deploy on apache2 </br>
-<b>sh deploy_apache2.sh </b> <br>
+To deploy on apache2 <br>
+<b>sh deploy_apache2.sh </b> <br> <br>
To deploy on apache <br>
<b>sh deploy_apache.sh </b> </br>
-<p> Note that if you need to use different parser you need to edit the script.
+<p> Note that if you need to use a different parser you need to edit the script.
For example if you use expat <br>
-instead of <br>
-<b><i> cp -f ${AXISCPP_DEPLOY}/lib/libaxis_xercesc.so ${AXISCPP_DEPLOY}/lib/libaxis_xmlparser.so </i></b> </br>
+instead of <br> <br>
+<b><i> cp -f ${AXISCPP_DEPLOY}/lib/libaxis_xercesc.so ${AXISCPP_DEPLOY}/lib/libaxis_xmlparser.so </i></b> </br> <br>
you need <br>
<b><i> cp -f ${AXISCPP_DEPLOY}/lib/libaxis_expat.so ${AXISCPP_DEPLOY}/lib/libaxis_xmlparser.so </i></b> </br>
<br>
-Basically what is done in the script are, <br>
+Basically what is done in the script are, <br> <br>
1. libaxiscpp_mod2.so is copied to <your apache home>/modules
- (the corresponding folder in apache is libexec) <br>
+ (the corresponding folder in apache is libexec) <br> <br>
- 2. libaxis_xercesc.so or libaxis_expat.so (the parser you use) is renamed to libaxis_xmlparser.so. <br>
+ 2. libaxis_xercesc.so or libaxis_expat.so (the parser you use) is renamed to libaxis_xmlparser.so. <br> <br>
- 3. Restart Apache is restarted <br>
+ 3. Apache is restarted <br> <br>
So if you don't use the scripts you need to do the above three steps yourself.
</p>
-10. See Axis C++ in action<br>
+<p>10. See Axis C++ in action<br> <br>
-Now the installation is complete. You can verify that the server side is working by accessing the URL http<a href="http://localhost/axis">://localhost/axis</a>/
+Now the installation is complete. You can verify that the server side is working by accessing the URL http<a href="http://localhost/axis">://localhost/axis</a>/
using your web browser. You should get the Axis C++ welcome page and
this page will show you a list of deployed services as specified by the
-$AXISCPP_DEPLOY/conf/server.wsdd file.<br>
+$AXISCPP_DEPLOY/conf/server.wsdd file. </p> <br>
<p>Now you can run a client sample and see if it works.<br><i><b>
cd $AXISCPP_DEPLOY/bin <br>
@@ -287,6 +287,4 @@
<div id="pdf" align="right">
<a href="lininstall-guide.pdf"><img alt="PDF" src="../skin/images/pdfdoc.gif" class="skin"><br>
PDF</a>
-</div>
-
-</body></html>
+</body></html>
\ No newline at end of file