WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Deploying a mediation module

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.

Before you begin

Before deploying a mediation module, assemble and test the module on a test server. After testing, export the mediation module and other files needed.

Why and when to perform this task

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:

Steps for this task

  1. Copy the file containing your mediation module into the production environment. If you have exported your mediation module as an EAR file then copy the EAR file to the production environment. If you have exported your mediation module as a JAR file then copy the JAR file to the production environment.
  2. Optional: Run the serviceDeploy command to create an installable EAR file. This step is only necessary if you have exported your mediation module as a JAR file rather than an EAR file.
    1. Locate the JAR file that contains the module to deploy.
    2. Issue the serviceDeploy command with the JAR file from the previous step as input.
  3. Install the EAR file onto an appropriate server or cluster. WebSphere ESB provides the same ways to install EAR files onto servers and clusters as provided by WebSphere Application Server. For information about how to use the administrative console to install the EAR file for a mediation module, see Installing a mediation module EAR file with the console.
  4. Save your changes to the master configuration.

Result

The mediation module is now installed.

What to do next

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.


Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\doc\tdep_depprodserver.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)