Actions for Tomcat Windows servers are pre-defined within DeployHub. A deployment points to one or more Repositories with that application’s artifacts. These are referenced by one or more Components (and one or more of their Component Items) within an Application. Pre and Post Actions at the Application level are used for Tomcat deployments. The Pre Action stops the Tomcat instance, the Post Action starts it. In between the start and stop, the Components will deployed.
Define Your Tomcat Action to Your Component
- 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.
- Open the Tomcat folder from the Activities tree view on the right.
- Find the “Tomcat Pre Deploy” Procedure from the tree view.
- Drag it out to your design pallet.
- To use the “Tomcat Pre Deploy” Procedure, enter the parameters unique to your Tomcat application.
Repeat the same steps for creating your “Tomcat Post Deploy” Action. Connect the “Tomcat Pre-Deploy” Procedure to the “Tomcat Post Deploy” to create your flow logic.
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.