A DeployHub deployment can point to one or more Repositories which contain the artifacts (.ear, .jar, and .war files) that make up a WebSphere application. These are referenced in DeployHub by one or more Components (and one or more of their Component Items) within an Application. A Post Action is then executed which deploys these artifacts into WebSphere. The user creates the Action, which itself contains Procedures. The Procedure defined to the Action for a WebSphere deployment is called “WebSphereDeploy.

Define Your WebSphere Action

  • From the Flows Menu, select the Actions tree view.  
  • Right click on your Domain and select “New Action in this Domain.”  
  • Create a new Action.  
  • Once your Action is created, go to the Workflow tab.  
  • Find the “WebSpheredeploy” Procedure from the Activities tree view on the right.  
  • Drag it out to your design pallet.
  • To use the “WebSphereDeploy” Procedure, enter the parameters unique to your WebSphere application.

Variables in Parameters

You can use variables in the Parameters fields. The use of variables enables your deployment to adapt across Components and your continuous delivery pipeline. Hard coded values are not recommended. The values for the variables are defined as attributes to Components, Applications, Environments and Endpoints. To resolve the variables, you define them at these higher levels. For example, a database connection that is unique to an Environment can be defined at the Environment level.