This documentation is for WSO2 Enterprise Integrator version 6.2.0 . View documentation for the latest release in the 6.x.x family and the latest release in the 7.x.x family.

All docs This doc
Skip to end of metadata
Go to start of metadata

A module is an archive file that bundles a set of classes, related libraries and third party library dependencies. 

Introduction to Axis2 modules

The folder structure of the module archive file will look as follows:

     - module.xml

The ESB profile of WSO2 EI has the following modules deployed by default:






This module provides WS-Security and WS-SecureConversation functionalities for Axis2, based on the Apache WSS4J, Apache XML-Security and Apache Rahas implementations.



This is the WS-Addressing implementation on Axis2, supporting the WS-Addressing 1.0 Recommendation, as well as the submission version (2004/08).



Unwraps the binary messages coming from the Message Relay for Admin Services.



This module is used to enable STS for service where it adds the RequestSecurityToken operation to a service that the module is engaged to.

For more information on Axis2 Modules, see Apache Axis2 Architecture Guide.

The ESB profile of WSO2 EI provides a user-friendly interface to work with modules. See the following topics for more information on how to work with modules:

Adding a module

You can add a module to the ESB profile of WSO2 EI if you need to extend its capabilities. Follow the instructions below to add a module:

  1. Sign in. Enter your user name and password to log on to the ESB's management console.
  2. Click on "Main" in the left menu to access the "Manage" menu.
  3. In the "Manage" menu, click on "Add" under "Modules."
  4. The "Add modules" page appears.
  5. Click "Browse" to select the module archive file (MAR) you want to upload. To learn the detailed information about custom modules, see Writing an Axis2 Module.


    Use the plus sign button to upload more than one module.

  6. Click Upload.
  7. If the file was uploaded successfully, a message will appear prompting you to restart the server to activate the module. Click "OK."
    Once the server has been restarted, the module will be active and displayed on the "Deployed Modules" page. 

Engaging modules

A module is an archive file that bundles a set of classes, related libraries and third party library dependencies. After uploading a module to the system, you can engage the module to make it active. You can engage a module on a global level as well as at service level.

To engage a module at service level

Add the engagedModules service parameter to the proxy service and specify the modules you want to engage as comma separated values. For example, if you need to engage the rampart module and the sample-logging module, add the following parameter to the proxy service:

<parameter name="engagedModules">rampart,sample-logging</parameter>

Following is a sample proxy service where the engagedModules parameter is specified to engage the sample-logging module:

 <proxy xmlns=""
        		<address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
 	<parameter name="engagedModules">sample-logging</parameter>

To engage a module on a global level  

  1. In the <EI_HOME>/conf/axis2/axis2.xml file, under the Global Engaged Modules section, add a <module ref="modulename"/> entry for every module that you want to engage on a global level.
  2. Restart the server.

For example, to engage the rampart module on a global level, add the following entry and restart the server.

<module ref=“rampart"/>


The  WS-Addressing  module is always engaged on a global level by default.

  • No labels