roshan 2004/10/06 01:53:37
Modified: targets/axis/cpp lininstall-guide.pdf lininstall-guide.html
Log:
Edited the lin-install-guide. Changed by Rangika
Revision Changes Path
1.20 +131 -115 ws-site/targets/axis/cpp/lininstall-guide.pdf
<<Binary file>>
1.21 +148 -60 ws-site/targets/axis/cpp/lininstall-guide.html
Index: lininstall-guide.html
===================================================================
RCS file: /home/cvs/ws-site/targets/axis/cpp/lininstall-guide.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- lininstall-guide.html 19 Aug 2004 06:39:55 -0000 1.20
+++ lininstall-guide.html 6 Oct 2004 08:53:37 -0000 1.21
@@ -278,7 +278,7 @@
<div class="h3">
<h3>Axis C++ Linux Installation Guide</h3>
</div>
-<h3>Installing and deploying web applications using xml-AxisC++</h3>
+<h3>Installing and deploying web applications using xml-Axis C++</h3>
<h3>Contents</h3>
<ul>
<li>
@@ -298,10 +298,11 @@
<a name="What"></a>
</p>
<h3>What You Need</h3>
-<p>You need few helper libraries for logging, WSDL processing and introspection.
You need to have the following in order to run Axis C++ engine.</p>
RedHat 9 (2.4.20-8)<br> expat-1.95.7 (source)<br>
xerces-c-src2_2_0 (I build xerces from source)<br>
httpd-2.0.48 (source)<br> apache_1.3.27 (source) <p></p>
+<p> Expat or Xercesc<br> Apache2 or
Apache1<br>
+</p>
<p>
-<strong>Note: In my environment I have</strong>
-<br> autoconf 2.57<br> automake 1.6.3<br>libtool 1.4.3<br> gcc 3.2.2</p>
+<strong>Note:</strong> If you are using provided configure and Makefile.in's you
don't need to run autogen.sh script to generate them for your platform. In any case if
you need to run it then following versions are recommended to be installed in your
environment.</p>
+<p>autoconf<br> automake<br>libtool<br> gcc</p>
<p>You can download the Axis C++ source or binary from one of the apache mirror
sites<br>
<a
href="http://ws.apache.org/axis/cpp/download.html";>http://ws.apache.org/axis/cpp/download.html</a>
<br>
@@ -309,18 +310,27 @@
<br>
<br> You can get xercesc from the uri <a
href="http://xml.apache.org/xerces-c/download.cgi";>http://xml.apache.org/xerces-c/download.cgi</a>
<br>
-<br> You must define some environment variables in order to build.<br>AXISCPP_HOME
is where you checkout Axis C++</p>
+<br>
+</p>
+<h3>Source distribution installation</h3>
+<p>Unzip and untar the tgz ball.<br>You must define some environment variables in
order to build.<br>
+<br>
+<strong>AXISCPP_HOME</strong> is where you checkout Axis C++</p>
<br>
<p>
<strong>AXISCPP_HOME="/usr/local/axiscpp"</strong>
<br>
<strong>AXISCPP_DEPLOY="/usr/local/axiscpp_deploy"</strong>
<br>
-<strong>LD_LIBRARY_PATH="$AXISCPP_DEPLOY/lib:$LD_LIBRARY_PATH"</strong>
+<strong>LD_LIBRARY_PATH="$AXISCPP_DEPLOY/lib:<path to parser library you
use>"</strong>
<br>
<strong>export AXISCPP_HOME AXISCPP_DEPLOY LD_LIBRARY_PATH</strong>
<br>
</p>
+<br>
+<p>
+<strong>AXISCPP_HOME</strong> is where you extracted the source distribution.<br>
+<strong>AXISCPP_DEPLOY</strong> is where Axis C++ will be deployed</p>
<p>Axis C++ core is independant of the parser layer and transport layer.</p>
<p>You can write your own transport or parser library according to the APIs
provided. Currently Axis C++ provides API implementations for Xerces-c and Expat. It
also provides it's own client side transport library implementation. In the server
side deployment, Axis C++ provides two modules that can be loaded into apache1.3 and
apache 2 as shared libraries.</p>
<p>So this sums upto two possibilities.<br>You can deploy Axis C++ server<br>
On Apache2 with xercesc parser or expat parser(Only one parser at a
time)<br> On Apache1.3 with xercesc parser or expat parser<br>
@@ -342,22 +352,26 @@
<p>
<strong>cd $AXISCPP_HOME</strong>
</p>
-<p>
+<br>
+<p>Following step is optional. If you need to generate configure and Makefile.in's
instead of the provided one's you need to run autogen.sh<br>
+<br>
<strong>sh autogen.sh</strong>
<br>
<br>
-<strong>./configure --prefix= \</strong>
+<strong>./configure --prefix=<Where you need to deploy axis c++> \</strong>
<br>
-<strong>--with-apache2= \</strong>
+<strong>--with-apache2=<path to apache2> \</strong>
<br>
<strong>--with-expat=/usr/local/expat1957</strong>
<br>
<br>
<strong>make</strong>
<br>
+<br>
<strong>make install</strong>
</p>
-<p>This will deploy Axis C++ into your folder of choice.<br>Following are some of
the options available with configure<br>
+<p>This will deploy Axis C++ into your folder of choice.<br>
+<br>Following are some of the options available with configure<br>
<br>
<strong>--with-apache2 :</strong> To use apache2 as server transport library<br>
<br>
@@ -371,13 +385,14 @@
<br>
<strong>--enable-testcases :</strong> Whether you need to build testcases<br>
By default test cases are built. If you don't want to build the
test cases then you need to specifically say no<br>
<br>
-<strong>--enable-log :</strong> Whether to enable log facility. By dafault this is
enabled. If you don't need it say no to this<br>
+<strong>--enable-log :</strong> Whether to enable log facility. By default this is
enabled. If you don't need it say no to this<br>
<br>
<strong>--enable-libwww :</strong> By default libwww client transport library is
built. If you don't need it say no to this.<br>
</p>
-<p>You may rename and edit build.sh_sample for one step building and installing.</p>
+<p>You may rename and edit <strong>build.sh_sample</strong> for one step
configuring and building.</p>
<p>Once you have finished , have a look at
<strong>$AXISCPP_HOME/build_errors.</strong> Most probably you will see many warnings.
Just ignore them. But if you see any errors it means that build was not successful and
check whether you have followed the instructions carefully.</p>
<p>You can see the folder <strong>$AXISCPP_DEPLOY/lib</strong> to see what are
created</p>
+<p></p>
<p>
<strong>libaxiscpp_mod.so is apache module which is loaded when apache
loads</strong>
<br>
@@ -393,60 +408,138 @@
<br>
<strong>libaxis_xercesc.so is the xercesc parser library implmentation for Axis
C++</strong>
</p>
-<p>Also $AXISCPP_HOME/samples/server samples are built and installed in
$AXISCPP_DEPLOY/lib</p>
-<p>$AXISCPP_HOME/samples/client samples are built and executables are in
$AXISCPP_DEPLOY/bin</p>
-<p>Now you need to add to <strong>$<apache install directory>/conf/httpd.conf
$ vi <apache install directory>/conf/httpd.conf</strong>
+<p>Also <strong>$AXISCPP_HOME/samples/server</strong> samples are built and
installed in <strong>$AXISCPP_DEPLOY/lib</strong>
+</p>
+<p>
+<strong>$AXISCPP_HOME/samples/client</strong> samples are built and executables are
in <strong>$AXISCPP_DEPLOY/bin</strong>
</p>
+<p>Add the following into <strong>$<apache install
directory>/conf/httpd.conf</strong>
<br>
-<p>At the bottom of the file you have to include following lines and save it.</p>
+<br>
+</p>
<p>
-<strong>LoadModule axis_module modules/libaxiscpp_mod2.so</strong> (in apache1.3
replace modules with libexec and libaxiscpp_mod2.so with libaxiscpp_mod.so)<br>
+<strong>LoadModule axis_module modules/libaxiscpp_mod2.so</strong> (in apache1.3
replace modules with libexec and libaxiscpp_mod2.so with libaxiscpp_mod.so)<br>
<strong><Location /axis></strong>
-<br>
+<br>
<strong>SetHandler axis</strong>
-<br>
+<br>
<strong></Location></strong>
</p>
<p>Now you need the deployment descripter (server.wsdd) to deploy server samples
you built.</p>
-<p>By default there is a deployment descripter in $AXISCPP_DEPLOY/conf to deploy
samples</p>
-<p>In $AXISCPP_DEPLOY/etc/axiscpp.conf file you can give paths to your log files,
configuration files libraries etc.</p>
+<p>By default there is a deployment descripter in
<strong>$AXISCPP_DEPLOY/conf</strong> to deploy samples</p>
+<p>In <strong>$AXISCPP_DEPLOY/etc/axiscpp.conf</strong> file you can give paths to
your log files, configuration files, libraries etc.</p>
<br>
-<p>
-<strong># The comment character is '#'</strong>
+<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.<br>To do that
you can find scripts written in <strong>$AXISCPP_DEPLOY/bin.</strong>
<br>
-<strong>#Available directives are as follows</strong>
+<strong>cd $AXISCPP_DEPLOY/bin</strong>
+</p>
+<p>To deploy on apache2<br>
+<strong>sh deploy_apache2.sh</strong>
+</p>
+<p>To deploy on apache<br>
+<strong>sh deploy_apache.sh</strong>
+</p>
+<p>When you run the above script,<br>libaxiscpp_mod2.so is copied to <your
apache home>/modules folder.<br>libaxis_expat.so is renamed to
libaxis_xmlparser.so. Also apache is started and libaxiscpp_mod2.so is loaded into
apache.<br>libaxiscpp_mod2.so is the apache module for Axis C++. This will in term
load Axis C++ server engine (libserver_engine.so).<br>Note that
<strong>libaxis_xmlparser.so</strong> is loaded by the engine dynamically as parsing
is required from the engine.</p>
+<p>Note that somewhere in the script above, it changes the name
<strong>libaxis_expat.so</strong> to <strong>libaxis_xmlparser.so.</strong>
+<br>If we use xerces we need to change <strong>libaxis_xercesc.so</strong> to
<strong>libaxis_xmlparser.so.</strong>
+</p>
+<p>If you have done installation successfully it will display the Axis C++ welcome
page when you point to URI <a href="http://localhost/axis";>http://localhost/axis</a>
<br>
-<strong>#(Some of these directives may not be implemented yet)</strong>
<br>
-<strong>#</strong>
+<strong>Note:</strong> In the axis welcome page all the services in
<strong>$AXISCPP_DEPLOY/conf/server.wsdd</strong> are listed. This does not mean that
the libraries corresponding to these services are deployed yet. It merely list
whatever in the server.wsdd.</p>
<br>
-<strong>#WSDDFilePath:The path to the server wsdd</strong>
+<p>To run interop samples<br>
+<strong>cd $AXISCPP_DEPLOY/bin</strong>
<br>
-<strong>#LogPath:The path to the axis log</strong>
+<strong>./base localhost 80 etc.</strong>
+</p>
+<p>(Check whether there is a script <strong>run_interoptests.sh</strong> in that
folder which can be used to run all the interop tests)</p>
+<p>If you don't get it right check with the following list<br>
+<br>Check whether <strong>AXISCPP_HOME</strong> is set where you build axis c++
by<br>
+<strong>echo $AXISCPP_HOME</strong>
<br>
-<strong>#ClientLogPath:The path to the axis client log</strong>
+<br>Check whether <strong>AXISCPP_DEPLOY</strong> and
<strong>LD_LIBRARY_PATH</strong> is set where you start apache<br> Build axis c++ and
run clients by<br>
+<strong>echo $AXISCPP_DEPLOY echo $LD_LIBRARY_PATH</strong>
<br>
-<strong>#ClientWSDDFilePath:The path to the client wsdd</strong>
<br>
-<strong>#Transport_http:The HTTP transport library</strong>
+</p>
+<p>Check whether you have necessary permissions to create the deploy folder which
you give in configure option prefix.<br>eg: configure
--prefix=/usr/local/axiscpp_deploy you need permission to write in /usr/local/ .
Otherwise if you type make install you will get permission problems</p>
+<p>Check whether paths in server.wsdd are pointing correctly to service or handler
libraries<br>
+<br> Check whether <strong>axiscpp.conf</strong> is containing correct entries<br>
+<br> Check whether Axis C++ can write to log
folder<strong>($AXISCPP_DEPLOY/log)</strong>
+</p>
+<br>
+<h3>Binary distribution installation</h3>
+<p>Unzip and untar the tgz ball.<br>You must define some environment variables
first.</p>
+<p>
+<strong>AXISCPP_DEPLOY="/usr/local/axiscpp_deploy"</strong>
<br>
-<strong>#Transport_smtp:The SMTP transport library</strong>
+<strong>LD_LIBRARY_PATH="$AXISCPP_DEPLOY/lib:<path to parser library you
use>"</strong>
<br>
-<strong>#XMLParser:The xml parser library</strong>
+<strong>export AXISCPP_DEPLOY LD_LIBRARY_PATH</strong>
</p>
<p>
-<strong>LogPath:/usr/local/axiscpp_deploy/log/AxisLog</strong>
+<strong>AXISCPP_DEPLOY</strong> is where you extracted the binary distribution</p>
+<p>Have a look at the folder <strong>$AXISCPP_DEPLOY/lib</strong> to see what is
there</p>
+<p>
+<strong>libaxiscpp_mod.so is apache module which is loaded when apache
loads</strong>
<br>
-<strong>WSDDFilePath:/usr/local/axiscpp_deploy/etc/server.wsdd</strong>
+<strong>libaxiscpp_mod2.so is apache2 module which is loaded when apache2
loads</strong>
<br>
-<strong>ClientLogPath:/usr/local/axiscpp_deploy/log/AxisClientLog</strong>
+<strong>libserver_engine.so is the Axis C++ server engine which is loaded by
libaxis_mod(2).so module</strong>
+<br>
+<strong>libaxiscpp_client.so is Axis C++ client library</strong>
+<br>
+<strong>libaxis_transport.so is the Axis C++ client transport library</strong>
+<br>
+<strong>libaxis_expat.so is the expat parser library implementation for Axis
C++</strong>
+<br>
+<strong>libaxis_xercesc.so is the xercesc parser library implmentation for Axis
C++</strong>
+</p>
+<p>Also server samples are in<br>
+<strong>$AXISCPP_DEPLOY/lib</strong>
+<br>Client samples are in <strong>$AXISCPP_DEPLOY/bin</strong>
+</p>
+<p>Axis C++ core is independant of the parser layer and transport layer.<br>
+<br>You can write your own transport or parser library according to the APIs
provided. Currently Axis C++ provides API implementations for Xerces-c and Expat. It
also provides it's own client side transport library implementation. In the server
side deployment, Axis C++ provides two modules that can be loaded into apache1.3 and
apache 2 as shared libraries.<br>So this sums upto two posibilities.<br>You can deploy
Axis C++ server<br> On Apache2 with xercesc parser or expat parser(Only
one parser at a time)<br> On Apache1.3 with xercesc parser or expat
parser</p>
+<p>This binary comes with libraries built for apache1.3 and apache2 support and
parser libraries both for expat and xercesc</p>
+<p>It also comes with all the sample libraries and sample executables and prebuilt
tests. But If you need to build the samples and tests for yourself from the sample and
test source do the following</p>
+<p>
+<strong>Sample and Test build process</strong>
+<br>
+<br>
+<strong>cd $AXISCPP_DEPLOY</strong>
+<br>
+<br>Following step is optional. If you need to generate configure and Makefile.in's
instead of the provided one's you need to run autogen.sh</p>
+<p>
+<strong>sh autogen.sh</strong>
+<br>
+<br>
+<strong>./configure --prefix=$AXISCPP_DEPLOY</strong>
+<br>
+<br>
+<strong>make</strong>
<br>
-<strong>XMLParser:/usr/local/axiscpp_deploy/lib/libaxis_xmlparser.so</strong>
<br>
-<strong>Transport_http:/usr/local/axiscpp_deploy/lib/libaxis_transport.so</strong>
+<strong>make install</strong>
+<br>
+<br>This will put sample libraries into <strong>$AXISCPP_DEPLOY/lib</strong> and
sample executables into <strong>$AXISCPP_DEPLOY/bin</strong>
+<br>
+<br>Add the following into <strong>$<apache install
directory>/conf/httpd.conf</strong>
+<br>
</p>
+<p>
+<strong>LoadModule axis_module modules/libaxiscpp_mod2.so</strong> (in apache1.3
replace modules with libexec and libaxiscpp_mod2.so with libaxiscpp_mod.so)<br>
+<strong><Location /axis></strong>
<br>
-<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.<br>To do that
you can find scripts written in $AXISCPP_DEPLOY/bin.<br>
+<strong>SetHandler axis</strong>
+<br>
+<strong></Location></strong>
+</p>
+<p>Now you need the deployment descripter(server.wsdd) to deploy server samples you
built.<br>By default there is a deployment descripter in
<strong>$AXISCPP_DEPLOY/conf</strong> to deploy samples</p>
+<p>In <strong>$AXISCPP_DEPLOY/etc/axiscpp.conf</strong> file you can give paths to
your log files, configuration files, libraries etc.</p>
+<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.<br>To do that
you can find scripts written in <strong>$AXISCPP_DEPLOY/bin.</strong>
+<br>
<strong>cd $AXISCPP_DEPLOY/bin</strong>
</p>
<p>To deploy on apache2<br>
@@ -455,34 +548,29 @@
<p>To deploy on apache<br>
<strong>sh deploy_apache.sh</strong>
</p>
-<p>When you run the above script,<br>libaxiscpp_mod2.so is copied to <your
apache home>/modules folder.<br>libaxis_expat.so is renamed to
libaxis_xmlparser.so. Also apache is started and libaxiscpp_mod2.so is loaded into
apache.<br>libaxiscpp_mod2.so is the apache module for Axis C++. This will in term
load Axis C++ server engine (libserver_engine.so).<br>Note that libaxis_xmlparser.so
is loaded by the engine dynamically as parsing is required from the engine.</p>
-<p>Note that somewhere in the script above, it changes the name libaxis_expat.so to
libaxis_xmlparser.so.<br>If we use xerces we need to change libaxis_xercesc.so to
libaxis_xmlparser.so.</p>
-<p>If you have done installation successfully it will display the Axis C++ welcome
page when you point to URI <a href="http://localhost/axis";>http://localhost/axis</a>
-<br>
-<br>
-<strong>Note:</strong> In the axis welcome page all the services in
$AXISCPP_DEPLOY/conf/server.wsdd are listed. This does not mean that the libraries
corresponding to these services are deployed yet. It merely list whatever in the
server.wsdd.</p>
-<br>
+<p>When you run the above script,<br>libaxiscpp_mod2.so is copied to <your
apache home>/modules folder.<br>libaxis_expat.so is renamed to
libaxis_xmlparser.so. Also apache is started and
libaxiscpp_mod2.<br>libaxiscpp_mod2.so is the apache module for Axis C++. This will in
term load Axis C++ server engine (libserver_engine.so).<br>Note that
libaxis_xmlparser.so is loaded by the engine dynamically as parsing is required from
the engine.</p>
+<p>Note that somewhere in the script above it changes the name libaxis_expat.so to
libaxis_xmlparser.so.<br>If we use xerces we need to change libaxis_xercesc.so to
libaxis_xmlparser.so.<br>
+<br>If you have done installation successfully it will display the Axis C++ welcome
page when you point to URI <a href="http://localhost/axis";>http://localhost/axis</a>
+<br>Note: In the axis welcome page all the services in
<strong>$AXISCPP_DEPLOY/conf/server.wsdd</strong> are listed. This does not
mean<br>that the libraries corresponding to these services are deployed yet. It merely
list whatever in the server.wsdd.</p>
<p>To run interop samples<br>
<strong>cd $AXISCPP_DEPLOY/bin</strong>
<br>
<strong>./base localhost 80 etc.</strong>
-</p>
-<p>(Check whether there is a script run_interoptests.sh in that folder which can be
used to run all the interop tests)</p>
-<p>If you don't get it right check with the following list<br>
-<br>Check whether AXISCPP_HOME is set where you build axis c++ by<br>
-<strong>echo $AXISCPP_HOME</strong>
-<br>
-<br>Check whether AXISCPP_DEPLOY and LD_LIBRARY_PATH is set where you start
apache<br> Build axis c++ and run clients by<br>
-<strong>echo $AXISCPP_DEPLOY echo $LD_LIBRARY_PATH</strong>
+<br>(Check whether there is a script <strong>run_interoptests.sh</strong> in that
folder which can be used to run all the interop tests)</p>
+<p>If you don't get it right check with the following list</p>
+<p>Check whether <strong>AXISCPP_DEPLOY</strong> and
<strong>LD_LIBRARY_PATH</strong> is set where you start apache<br>Build axis c++ and
run clients by<br>
+<br>
+<strong>echo $AXISCPP_DEPLOY</strong>
+<br>
+<strong>echo $LD_LIBRARY_PATH</strong>
+</p>
+<p>Check whether you have necessary permissions to create the deploy folder which
you give in configure option prefix.<br>eg: configure
--prefix=/usr/local/axiscpp_deploy you need permission to write in /usr/local/.
Otherwise if you type make install you will get permission problems<br>
+<br>Check whether paths in server.wsdd are pointing correctly to service or handler
libraries<br>
+<br>Check whether <strong>axiscpp.conf</strong> is containing correct entries<br>
+<br>Check whether Axis C++ can write to log
folder<strong>($AXISCPP_DEPLOY/log)</strong>
<br>
<br>
</p>
-<p>Check whether you have necessary permissions to create the deploy folder which
you give in configure option prefix.<br>eg: configure
--prefix=/usr/local/axiscpp_deploy you need permission to write in /usr/local/</p>
-<p>Check whether paths in server.wsdd are pointing correctly to service or handler
libraries<br>
-<br> Check whether axiscpp.conf is containing correct entries<br>
-<br> Check whether Axis C++ can write to log folder($AXISCPP_DEPLOY/log)</p>
-<br>
-<a href="lininstall-guide.pdf"><img alt="PDF" src="../skin/images/pdfdoc.gif"><br>
PDF</a>
</li>
</ul>
<div id="pdf" align="right">
