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 it to activate the module. You can engage a module on a global level as well as at service level.
Engaging a module
To engage a module at service level
Add the engageModules 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>
To engage a module on a global level
In the <ESB_HOME>/repository/conf/axis2/axis2.xml file, under the Global Engaged Modules section add a <module ref> entry for every module that you want to engage on a global level. For example, to engage the rampart module on a global level add the following entry.
<module ref=“rampart"/>
Note
The WS-Addressing module is always engaged on a global level by default.
Disengaging a module
If required, you can disengage a module that is already engaged on a global level.
To disengage a module