Deploying the module for production

Deploying a module created with the external service wizard to IBM® Business Process Manager or WebSphere® Enterprise Service Bus in a production environment is a two-step process. First, you export the module in IBM Integration Designer as an enterprise archive (EAR) file. Second, you deploy the EAR file using the IBM Business Process Manager or WebSphere Enterprise Service Bus administrative console.

  1. Adding external software dependencies on the server
    The adapter needs certain files installed on IBM Business Process Manager or WebSphere Enterprise Service Bus server to be able to communicate with the database.
  2. Installing the RAR file (for modules using stand-alone adapters only)
    If you chose not to embed the adapter with your module, but instead choose to make the adapter available to all deployed applications in the server instance, you need to install the adapter in the form of a RAR file to the application server. A RAR file is a Java™ archive (JAR) file that is used to package a resource adapter for the Java EE Connector Architecture (JCA).
  3. Exporting the module as an EAR file
    Using IBM Integration Designer, export your module as an EAR file. By creating an EAR file, you capture all of the contents of your module in a format that can be easily deployed to IBM Business Process Manager or WebSphere Enterprise Service Bus.
  4. Installing the EAR file
    Installing the EAR file is the last step of the deployment process. When you install the EAR file on the server and run it, the adapter, which is embedded as part of the EAR file, runs as part of the installed application.
Parent topic: Deploying the module
Previous topic: Configuring the module for deployment
Next topic: Administering the adapter module


Feedback

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