This topic describes the steps involved in taking a mediation module, as generated by WebSphere Integration Developer, and deploying it into a production WebSphere ESB environment.
A mediation module provides functions that can change the format, content or target of service requests between applications and services. These functions can help you to integrate applications and services. Mediation modules are types of Service Component Architecture (SCA) modules.
To enable WebSphere ESB to use the functions provided by the mediation module you need to deploy the module.
A mediation module is deployed to WebSphere ESB as a service application in the same way you would deploy enterprise applications, using an installable EAR (Enterprise ARchive) file.
During installation, you can configure the module enough to enable it to run in WebSphere ESB. After installation, you can configure the module further, start or stop the application, and otherwise manage its activity.
If you need to deploy many application files, you may want to use ANT. By using ANT tasks, you can define the deployment of multiple applications and have them run unattended on a server.
To deploy a mediation module as a service application, complete the following steps:
After you have deployed your EAR file, you can view the SCA modules you have deployed and monitor that the server or cluster is processing requests correctly.
To enable WebSphere ESB to use the functions provided by a mediation module, the deployed module must be started. You can start the mediation module manually or configure it to start automatically.
You can also make changes to the SCA import binding of the mediation module, to redirect one module to another module. This allows you to invoke different service providers, or process service requests and responses in different ways, without having to rebuild and redeploy the mediation module.