Module Configuration

A module is an archive file that bundles a set of classes, related libraries and third-party library dependencies. you can do module management in 4 levels as follows:

Global Level : A module is engaged to all services. For information, see Axis2 Modules.
Service Group Level : A module is engaged to a service group. For information, see /wiki/spaces/DSS400/pages/31293824 .
Operation Level : A module is engaged for a particular operation of a service. For information, see Operation Management.
Service Level : A module is engaged only for a certain service as described below.

To upload your module archive, all the class files and the module.xml descriptor file have to be available in the archive.

Service-level module engagement

Log in to the management console and select Services > List from the Main menu.
The Deployed Services window appears. Click on the necessary service to access its dashboard.
In the dashboard, under Quality of Service Configuration panel, click Modules.
The Engage Modules to Service window appears. Choose a module to add from the following and Engage.
- WSO2xfer-3.20 - Is an implementation of WS-Transfer
- WSO2mex-3.20 - Provides MetadataExchange services for any services that the module is engaged to.
- rampart-1.61-wso2v1 - Provides the WS-Security and WS-SecureConversation functionality for Axis2, based on Apache WSS4J, Apache XML-Security and Apache Rahas implementations.
- rahas-1.61-wso2v1 - Used to enable STS in a service. It adds the RequestSecurityToken operation to a service that the module is engaged to.
- sandesha2-3.20 - Implements WS-Reliable Messaging