If you do not want to share either configuration or libraries from the WSO2 SOA Enablement Server distribution, and you want to create a separate WSO2 SOA Enablement Server client runtime, you must install the WSO2 SOA Enablement Server client by using the Installation Wizard or installing it manually. In the latter case, follow the steps in Custom Configuration, where you will find a description of how to perform separate configuration for WSO2 SOA Enablement Server clients. Then copy the JAR files listed below from the WASP_HOME/lib directory to the /lib subdirectory of the WSO2 SOA Enablement Server Client directory you created.
The following JARs are needed for a minimum configuration:
Table 34. Required Client JAR Files
| Name | Type | Description |
|---|---|---|
| wasp.jar | WSO2 SOA Enablement Server JAR Library | WSO2 SOA Enablement Server core classes and SAAJ, JAXM and JAX-RPC interfaces |
| activation.jar | Third party JAR file | Java™ Activation Framework (JAF) |
| antlr.jar | Third party JAR file | ANTLR Translator Generator |
| builtin_serialization.jar | WSO2 SOA Enablement Server Client Package | WSO2 SOA Enablement Server built-in serializers and deserializers |
| core_services_client.jar | WSO2 SOA Enablement Server Client Package | Client to WSO2 SOA Enablement Server Core Services |
| jaas.jar | Third party JAR file | Java™ Authentication and Authorization Service |
| jaxm.jar | WSO2 SOA Enablement Server JAR Library | JAXM implementation |
| jaxrpc.jar | WSO2 SOA Enablement Server JAR Library | JAX-RPC implementation |
| jetty.jar | Third party JAR file | HTTP Server |
| log4j.jar | Third party JAR file | Jakarta-log4j logging framework |
| runner.jar | WSO2 SOA Enablement Server JAR Library | WSO2 SOA Enablement Server Runner Class, MANIFESTs |
| saaj.jar | WSO2 SOA Enablement Server JAR Library | SAAJ implementation |
| wsdl_api.jar | WSO2 SOA Enablement Server JAR Library | WSDL-API implementation |
| xercesImpl.jar | Third party JAR file | The Xerces XML parser |
| xml-apis.jar | Third party JAR file | XML APIs |
| xmlParserApis.jar | Third party JAR file | XML parser APIs |
Add the following jars to use WSO2 SOA Enablement Server with security on the client side:
Table 35. Additional JARs for Secure Clients
| Name | Type | Description | ||||
|---|---|---|---|---|---|---|
| security-ng.jar | WSO2 SOA Enablement Server JAR Library | Core WSO2 SOA Enablement Server Security | ||||
| security2-ng.jar | WSO2 SOA Enablement Server JAR Library | Specific WSO2 SOA Enablement Server Security | ||||
| Third party JAR files | Sun JCE™ | ||||
| jcert.jar | Third party JAR file | Part of Java(TM) Secure Socket Extension | ||||
| jnet.jar | Third party JAR file | Part of Java™ Secure Socket Extension | ||||
| jsse.jar | Third party JAR file | Part of Java™ Secure Socket Extension | ||||
| security_providers_client.jar | WSO2 SOA Enablement Server Client Package | Client side of WSO2 SOA Enablement Server security providers | ||||
| security_services_client.jar | WSO2 SOA Enablement Server Client Package | Client side to WSO2 SOA Enablement Server security Web services |
To use the XSLT Interceptor on the client side, add:
Table 36. Additional JAR Files for XSLT Interceptor
| Name | Type | Description |
|---|---|---|
| xsltinterceptor.jar | WSO2 SOA Enablement Server Client Package | XSLT interceptor WSO2 SOA Enablement Server client package |
| xalan.jar | Third party JAR file | The Xalan XSLT processor |
Additional optional JAR files are described in Distribution JAR files .
If you want to use any of these packages, add them to the client's CLASSPATH. A classpath builder tool is included in the distribution at WASP_HOME/install-log.html. For more details about client packages, please see Client Package.
WSO2 SOA Enablement Server's features are organized into Components, each of which is loaded in one or more JAR files. We have organized these components into a number of Installation Scenarios, including client-side scenarios, as described in Installation Scenarios.