The WSO2 SOA platform has the capabilities of Axis2 to add modules to extend it. The global modules will affect all the services deployed within the server.
A Module is an archive file that bundles a set of classes, related libraries and third party library dependencies. WSO2 Carbon provides a user-friendly interface to engage, disengage and configure these modules. You can learn more about Axis2 modules in the Modules section.
Modules can be engaged in three levels:
- Service level (As described here) - A module will be engaged only for a certain service.
- Service group level - A module will be engaged for a service group.
- Global level - A module will be engaged for all the services.
- Operations level - A module will be engaged for a particular operation of a service.
Note
To upload your module archive, all the class files and the module.xml descriptor file have to be available in the archive.
Follow the instructions bellow to engage modules to a service.
1. Log on to the Application Server Management Console.
2. Click the "Main" menu and select "List" under "Web Services."
3. The "Deployed Services" screen appears. Click on the necessary service.
4. The "Service Dashboard" page appears. Click "Modules" in the "Quality of Service Configuration" panel.
5. The "Engage Modules to Service" page appears. Choose a module to add. WSO2 Carbon provides the following modules, which you can engage into your service:
- WSO2xfer-3.20 - Is an implementation of WS-Transfer.
- WSO2mex-3.20 - Provides MetadataExchange services for any services that the module is engaged.
- rampart-1.61-wso2v1 - Provides the WS-Security and WS-SecureConversation functionalities for Axis2, based on Apache WSS4J, Apache XML-Security and Apache Rahas implementations.
- rahas-1.61-wso2v1 - Is used to STS enable a service, where it adds the RequestSecurityToken operation to a service that the module is engaged to.
- sandesha2-3.20 - Implements WS-Reliable Messaging.
6. Click on the "Engage" button to add a module to the list.