Middleware Configuration for WebSphere plug-in

The Middleware Configuration for WebSphere® plug-in includes steps that deploy configuration templates of IBM® WebSphere Application Server that you generate from an existing cell.

This plug-in allows you to automate the process of deploying a configuration to different environments (for example, development, test, and production environments. The following steps provide an overview of the process you follow.

  1. Capture configuration information from an existing cell and use it to generate a configuration template.
  2. Add the configuration template to UrbanCode Deploy as a component.
  3. Associate the component with an application.
  4. Run the defined deployment process to configure the target WebSphere cell or cluster.

The process for using the plug-in is designed to support either one application at the cell scope or one application at a cluster scope. The process is not designed to support use cases where multiple applications are deployed within the same cell scope or the same cluster scope.

The configuration information captured does not include application binaries (EAR and WAR files). You must separately associate the binaries with another component that is part of the UrbanCode Deploy application deployment process for the configuration definitions.

You set up tokens to use when you generate the templates. Tokens are used like variables to substitute values in configuration information that varies depending on environment. For example, you may use a different database or a different JDBC resource in each of the deployment environments.

The plug-in includes steps to support the process defined in the provided component template.


Feedback