Porting WSO2 SOA Enablement Server Locate
Porting WSO2 SOA Enablement Server Overview Locate
This guide describes the porting of WSO2 SOA Enablement Server for Java to the most common J2EE application servers and JMS providers. The porting is closely related to porting J2EE features. For most application servers, we provide a special tool called J2eeIntegrate.bat (for Windows) or J2eeIntegrate (for UNIX-type systems). Running this tool opens a How To screen for the application server chosen.
![[Note]](images/note.gif) | Note |
|---|---|
WSO2 SOA Enablement Server must be installed before it is ported. | |
| Note |
|---|---|
If you are looking for a guide to porting security, see Porting Notes in the Security Guide. Please ensure that you have jaas.jar and jce1_2_2.jar in the jre/lib/ext directory of the JDK which is used by the application server. | |
Table 13. instType Values
| instType | Application Server | Porting Guide |
| j2ee | Sun J2EE reference application server 1.3.x, and 1.4.x Developer Release | Sun J2EE Reference Implementation Server porting guide |
| jboss | JBoss server 2.4.x, 3.0.x, 3.2.x, 4.0.1 and higher | JBoss Server porting guide |
| mqseries | MQSeries for Windows NT and Windows 2000 JMS provider porting guide | MQSeries 4.0 JMS provider porting guide |
| webspheremq | WebsphereMQ JMS provider porting guide | WebsphereMQ JMS provider porting guide |
| oracle | Oracle | Oracle Containers for J2EE porting guide |
| orion | Orion Server 2.0.1 and higher | Orion Server porting guide |
| sun1 | Sun ONE Application Server 7 | SunONE Application Server porting guide |
| swiftmq | SwiftMQ | SwiftMQ porting guide |
| sonicmq | SonicMQ | SonicMQ 5.x and higher porting guide |
| tomcat | Apache Tomcat 4.1.x, 5.0.x | Tomcat porting guide |
| weblogic | BEA WebLogic server 7.x, 8.x | BEA Weblogic porting guide |
| websphere | IBM WebSphere Server 5.x, 6.x | IBM Websphere Server porting guide |
| Note |
|---|---|
Within this part of the documentation, whenever you see a WASP_HOME string, replace it with the absolute path to the directory in which you have installed WSO2 SOA Enablement Server for Java. | |
![[Important]](images/important.gif) | Important |
|---|---|
Tomcat 3.x and Websphere 4.x are not Servlet 2.3 specification compliant. Due to this fact the user must perform manual porting to enable WSO2 SOA Enablement Server for Java on these servers. | |
Modifying the Classpath and java.security.auth.login.config Locate
The porting instructions for each application server often include an instruction for modifying the CLASSPATH variable or the java.security.auth.login.config property. A general discussion of these modifications follows. Where the process differs significantly for a particular application server, this is discussed under the porting instructions for that application server.
Modifying the Classpath Locate
Classpath modification is necessary because of WSO2 SOA Enablement Server's dependency on various libraries. These libraries are:
xalan.jar - Needed by console to transform its XML based pages into HTML using XSLT
xercesImpl.jar - XML parser required by WSO2 SOA Enablement Server core
xmlParserAPIs.jar - Generic interfaces for XML parsers (Xerces implementation used)
xml-apis.jar - Generic interfaces of XML processors (Xalan implementation used)
security-ng.jar - The core component implementing security in WSO2 SOA Enablement Server
The order of packages in the classpath is important because of the policy used by the classloader. WSO2 SOA Enablement Server needs to have the correct version of the class being used. If an outdated version of a class with the same name is present, it must not be passed to WSO2 SOA Enablement Server. Therefore we prefix the CLASSPATH with the packages that contain those classes which might be present in an outdated version, assuring that WSO2 SOA Enablement Server gets the correct version.
Modifying JAVA_OPTIONS Locate
This is necessary only if WSO2 SOA Enablement Server is running with the security features enabled. The property java.security.auth.login.config must point to a file where JAAS features concerning WSO2 SOA Enablement Server are correctly configured. This is accomplished either by setting the property to our WASP_HOME/conf/jaas.config file or pasting the jaas.config into the file to which the property refers.