| <?xml version="1.0" encoding="iso-8859-1"?> | |
| <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" | |
| "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> | |
| <html xmlns="http://www.w3.org/1999/xhtml"> | |
| <head> | |
| <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> | |
| <title>Application Server Specific Configuration Guide</title> | |
| <meta content="amaya 9.2.1, see http://www.w3.org/Amaya/" /> | |
| <link href="../css/axis-docs.css" rel="stylesheet" type="text/css" media="all" /> | |
| </head> | |
| <body> | |
| <h1>Application Server Specific Configuration Guide</h1> | |
| <p>This document will give you that extra configuration information required | |
| for your Application Server to run Apache Axis2 to its fullest potential.</p> | |
| <p>Feel free to send your feedback or any learned information to our <a | |
| href="http://ws.apache.org/axis2/mail-lists.html">mailing lists</a>.</p> | |
| <a name="weblogic_websphere"></a> | |
| <h3>WebLogic/ WebSphere</h3> | |
| <p>We recommend using the exploded configuration to deploy Axis2 WAR in | |
| WebLogic and WebSphere application servers to support the hotupdate/ | |
| hotdeployment features in Axis2. However if you do want to deploy custom | |
| wars say in a clustering environment, You need to add two additional | |
| files into the WEB-INF named "services.list" and "modules.list" under | |
| modules and services directory respectively. | |
| </p> | |
| <ul> | |
| <li><b>WEB-INF/services/services.list</b> : should list all the services (aar files) that you want to expose.</li> | |
| <li><b>WEB-INF/modules/modules.list</b> : should list all the modules (mar files) that you want to use.</li> | |
| </ul> | |
| NOTE: In both cases, please list one entry per line | |
| <p>WebLogic ships with jars which conflict with jars present in Axis2. So, | |
| kindly use <prefer-web-inf-classes> to ensure that jars packaged in | |
| Axis2 WAR are picked up from WEB-INF/lib. You can do this by setting | |
| <prefer-web-inf-classes> element in WEB-INF/weblogic.xml to true. An | |
| example of weblogic.xml is shown below:</p> | |
| <pre><weblogic-web-app> | |
| <container-descriptor> | |
| <prefer-web-inf-classes>true</prefer-web-inf-classes> | |
| </container-descriptor> | |
| </weblogic-web-app></pre> | |
| <p>If set to true, the <prefer-web-inf-classes> element will force | |
| WebLogic's classloader to load classes located in the WEB-INF directory of a | |
| Web application in preference to application or system classes. This is a | |
| recommended approach since it only impacts a single Web module. </p> | |
| <p>Please look at the following documents in WebLogic/ WebSphere for more | |
| information:</p> | |
| <ul> | |
| <li><a | |
| href="http://e-docs.bea.com/wls/docs81/programming/classloading.html">WebLogic | |
| ServerApplication Classloading</a>- For more information on how | |
| WebLogic's class loader works</li> | |
| <li><a | |
| href="http://e-docs.bea.com/wls/docs81/webapp/deployment.html">Redeploying | |
| a Web Application in Exploded Directory Format</a></li> | |
| <li><a | |
| href="http://publib.boulder.ibm.com/infocenter/wsiihelp/v8r3/index.jsp?topic=/com.ibm.websphere.ii.product.ce.doc/configuring/iiyviigdepwebexpl.htm">Deploying | |
| the Web application in exploded form</a></li> | |
| </ul> | |
| </body> | |
| </html> |