The WSO2 SOA platform has the capabilities of Axis2 to add modules to extend its capabilities. The global modules will affect all the services deployed within the server.
Note: If you want to engage the modules through a service, in the navigator, under Modules, click List. On the Deployed Modules page, you can select the modules you want to engage.
A module is an archive file that bundles a set of classes, related libraries and third party library dependencies. The WSO2 Carbon provides a user friendly interface to engage, disengage and configure these modules. You can learn more about Axis2 modules from the Axis2 manuals at: http://ws.apache.org/axis2/1_4_1/modules.html
To upload your module archive, all the class files and the module.xml descriptor file have to be available in the archive.
The folder structure of the module archive file will look as follows.
Test.mar
META-INF
Module.xml
TestModule.class
TestHandler.class
Figure 1: Uploading a module achieve file.
The WSO2 Carbon management console provides you with an interface to engage, disengage, configure or delete available modules.
The module list contains the following entries for each module.
You can perform the following actions on each module
Figure 2: Available modules
All the available modules are shown above the currently engaged modules. The WS-Addressing module is always globally engaged. This list will be updated when you engage other available modules.
For example, the Throttle module is available to be configured globally. Once you click the Configure icon, a new page appears with the configuring options available for that module.
Figure 3: Throttle Configuration
After you have engaged a module (for example, throttling), the Global Configurations window will be updated. (Figure: 4)
The icon in front of an already engaged module, will have a red mark to indicate that it can be disengaged or reconfigured by clicking on that icon.
Figure 4: After Engaging a Module