You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by ro...@apache.org on 2004/07/20 11:11:07 UTC
cvs commit: ws-site/targets/axis/cpp lininstall-guide.pdf lininstall-guide.html
roshan 2004/07/20 02:11:07
Modified: targets/axis/cpp lininstall-guide.pdf lininstall-guide.html
Log:
Made the Linux Installation Guide more user friendly.Changed by Rangika
Revision Changes Path
1.18 +51 -51 ws-site/targets/axis/cpp/lininstall-guide.pdf
<<Binary file>>
1.19 +28 -13 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.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- lininstall-guide.html 13 Jul 2004 09:56:35 -0000 1.18
+++ lininstall-guide.html 20 Jul 2004 09:11:07 -0000 1.19
@@ -288,6 +288,7 @@
<a href="#What">What You Need</a>
</li>
<li style="list-style: none">
+<br>
<p>
<a name="Introducti"></a>
</p>
@@ -296,12 +297,15 @@
<p>
<a name="What"></a>
</p>
-<h3>What You need</h3>
-<p>It needs a few helper libraries, for logging, WSDL processing and introspection. You need to have 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>
+<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>
-<strong>Note: In my environment I have autoconf 2.57, automake 1.6.3, libtool 1.4.3, gcc 3.2.2</strong>
-</p>
-<p>You can download the Axis C++ source or binary from one of the apache mirror sites<br> http://ws.apache.org/axis/cpp/download.html<br>You can get expat from the uri http://sourceforge.net/projects/expat/<br> You can get xercesc from the uri http://www.xml.apache.org/xerces-c/download.cgi<br> You must define some environment variables in order to build.AXISCPP_HOME is where you checkout Axis C++</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>
+<p>You can download the Axis C++ source or binary from one of the apache mirror sites<br> http://ws.apache.org/axis/cpp/download.html<br>
+<br>You can get expat from the uri http://sourceforge.net/projects/expat/<br>
+<br> You can get xercesc from the uri http://www.xml.apache.org/xerces-c/download.cgi<br>
+<br> You must define some environment variables in order to build.AXISCPP_HOME is where you checkout Axis C++</p>
<br>
<p>
<strong>AXISCPP_HOME="/home/damitha/projects/axiscpp"</strong>
@@ -326,10 +330,10 @@
<br>Give read write permissions to /usr/local/Axis<br>
<br>
</p>
-<p>EXPAT_HOME points to where you installed expat<br>XERCESC_HOME points to where you installed xereces-c</p>
+<p>EXPAT_HOME points to the place where expat is installed<br>XERCESC_HOME points to the place where xereces-c is installed</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 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 parer or expat parser<br>So if you use only Expat no need to define XERCESC_HOME vice versa.</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>So if you use only Expat you don't have to define XERCESC_HOME vice versa.</p>
<p>
<strong>When you build Axis C++ you can give options</strong>
</p>
@@ -357,6 +361,7 @@
<p>#AC_OUTPUT(Makefile src/Makefile src/common/Makefile src/soap/Makefile src/wsdd/Makefile src/xml/Makefile<br> src/transport/Makefile src/transport/axis/Makefile src/engine/Makefile src/engine/server/Makefile src/engine/client/Makefile<br> src/server/Makefile src/server/apache2/Makefile src/server/simple_axis_server/Makefile src/server/adminservice/Makefile<br> src/client/Makefile src/client/adminclient/Makefile src/xml/xerces/Makefile)</p>
<p>
<strong>#apache2 block ends</strong>
+<br>
<br> #<strong>{apache1.3 block starts</strong>
<br>
</p>
@@ -372,7 +377,10 @@
<strong>#if you need to build only axis_xerces</strong>
</p>
<p>#AC_OUTPUT(Makefile src/Makefile src/common/Makefile src/soap/Makefile src/wsdd/Makefile src/xml/Makefile<br> src/transport/Makefile src/transport/axis/Makefile src/engine/Makefile src/engine/server/Makefile src/engine/client/Makefile<br> src/server/Makefile src/server/apache/Makefile src/server/simple_axis_server/Makefile src/server/adminservice/Makefile<br> src/client/Makefile src/client/adminclient/Makefile src/xml/xerces/Makefile)</p>
-<p>#}apache1.3 block ends</p>
+<p>
+<strong>#}apache1.3 block ends</strong>
+</p>
+<br>
<p>You also need to do a selection at $AXISCPP_HOME/src/xml/Makefile.am</p>
<p>
<strong>SUBDIRS = expat xerces #Here I build both expat and xerces libraries</strong>
@@ -392,7 +400,7 @@
<strong>#SUBDIRS = apache adminservice</strong>
</p>
<p>Now you need to copy header files from apache and parser that you use</p>
-<p>I have installed xercesc at /usr/local/xerces-c, expat at /usr/local/expat1957,apache2 at /usr/local/apache2 and apache1.3 at /usr/local/apache</p>
+<p>I have installed xercesc at /usr/local/xerces-c<br> expat at /usr/local/expat1957<br> apache2 at /usr/local/apache2<br> apache1.3 at /usr/local/apache</p>
<p>I'm going to build Axis C++ for apache2 and for both xercesc and expat(But I'm going to<br>use only one parser. But anyway I can give instructions to build both as you've seen earlier)<br>
</p>
<p>
@@ -407,7 +415,10 @@
<br>
<strong>sh build.sh</strong>
</p>
-<p>Once you have finished, have a look at $AXISCPP_HOME/build_errors,<br> $AXISCPP_HOME/samples/server/sample_server_build_errors and<br>$AXISCPP_HOME/samples/client/sample_client_build_errors to identify any warnings and errors. 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 followed the instructions carefully. Note that if you see errors on build_errors file then client samples will also fail since it depends on libaxiscpp_client.so.</p>
+<p>Once you have finished, have a look at $AXISCPP_HOME/build_errors,<br> $AXISCPP_HOME/samples/server/sample_server_build_errors and<br>$AXISCPP_HOME/samples/client/sample_client_build_errors to identify any warnings and errors. 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 followed the instructions carefully.<br>
+<br>
+<strong>Note that if you see errors on build_errors file then client samples will also fail since it depends on libaxiscpp_client.so.</strong>
+</p>
<p>You can see the folder $AXISCPP_HOME/bin to see what are created</p>
<p>libaxiscpp_mod.so is apache module which is loaded when apache loads<br>libaxiscpp_mod2.so is apache2 module which is loaded when apache2 loads<br>libserver_engine.so is the Axis C++ server engine which is loaded by libaxis_mod(2).so module<br>libaxiscpp_client.so is Axis C++ client library<br>libaxis_transport.so is the Axis C++ client transport library<br>libaxis_expat.so is the expat parser library implementation for Axis C++<br>libaxis_xercesc.so is the xercesc parser library implmentation for Axis C++</p>
<p>Also $AXISCPP_HOME/samples/server samples are built and installed in $AXIS_HOME/web_services</p>
@@ -416,7 +427,8 @@
<strong>$ vi <apache install directory>/conf/httpd.conf</strong>
</p>
<p>At the bottom of the file you have to include following lines and save it.</p>
-<p>LoadModule axis_module modules/libaxiscpp_mod2.so (in apache1.3 replace modules with libexec and libaxiscpp_mod2.so with libaxiscpp_mod.so)<br>
+<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>
<strong>SetHandler axis</strong>
@@ -477,7 +489,10 @@
<p>To deploy on apache<br>
<strong>sh deploy_apache.sh</strong>
</p>
-<p>When you run the above script all the libraries are copied into corresponding places.<br>libaxiscpp_mod2.so is copied to /modules folder.<br>libserver_engine.so and libaxis_expat.so is copied to $AXIS_HOME/libs folder(and renamed 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>
+<p>When you run the above script all the libraries are copied into corresponding places.<br>libaxiscpp_mod2.so is copied to /modules folder.<br>
+<br>libserver_engine.so and libaxis_expat.so is copied to $AXIS_HOME/libs folder(and renamed libaxis_xmlparser.so).<br> Also apache is started and libaxiscpp_mod2.so is loaded into apache.<br>
+<br>libaxiscpp_mod2.so is the apache module for Axis C++. This will in term load Axis C++ server engine (libserver_engine.so)<br>
+<br>
<strong>Note that libaxis_xmlparser.so is loaded by the engine dynamically as parsing is required from the engine.</strong>
</p>
<p>