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 WebSphere configurations and applications to different environments (for example, development, test, and production environments. The following steps provide an overview of the process you follow.

  1. Set up UrbanCode Deploy to support the process. Load plug-ins and install an agent on the host where the WebSphere installation resides.
  2. Create a component using the configuration template.
  3. Capture topology information from an existing WebSphere installation and model it in Resources. A resource tree represents scopes in the installation.
  4. Map the resources (scopes) to manage to the configuration template component.
  5. Associate the component with an application.
  6. Associate other components needed for deployment, for example components containing EAR or WAR files (application binaries)
  7. Associate the resources with an application environment.
  8. Generate the configuration template
  9. Deploy the configuration template to create new instances.

The process for using the plug-in is designed to support one application per scope (cell, cluster, server, or node). The process is not designed to support use cases where multiple applications are deployed within the same cell scope or the same cluster scope.

You can use custom properties on the component to differentiate resources across environments. The custom properties are used to generate tokens 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. See Using custom properties when deploying WebSphere configurations and applications

Updates for Version 5 of the plug-in

Various defects were fixed for Version 5 of the plug-in, which is supported in UrbanCode Deploy 6.0.1.

Updates for Version 4 of the plug-in

The following features were added for Version 4 of the plug-in, which is supported in UrbanCode Deploy 6.0.1.

Updates for Version 3 of the plug-in

The updates for Version 3 were internal and required documentation changes.

Updates for Version 2 of the plug-in

The following features were added for Version 2 of the plug-in, which is supported in UrbanCode Deploy 6.0.1.


Feedback