IBM WebSphere Application Server - Configure
WebSphere - Example 11 - Discover & Templatize Cluster Configuration Data
This process converts configuration data from a WebSphere Application Server cluster into a template that can be applied to other WebSphere Application Server instances. This process is not installed with the WebSphere Application Server – Configure plug-in. You must manually import this process into IBM UrbanCode Deploy. Download the process (JSON file).
Use this process if you want to capture and templatize WebSphere Application Server configuration at the cluster scope only.
Important: This sample process uses the ampersand (@) as the start and end delimiters. For example, the templatize steps create tokens that look like this example: @websphere.cell@. If the templatize steps are modified to use different delimiters, the Replace Tokens steps in the Apply component processes must be updated to use the correct delimiters.
WebSphere Application Server environment
This process is designed for all WebSphere Application Server environments that the plug-in supports.
The steps in this process follow this general flow:
Run the WebSphere Configuration Discovery step against a WebSphere cluster to generate a configuration data file that contains configuration data for the cluster.
Run the WebSphere – Templatize Cluster Configuration Data step to convert the configuration data of the cluster into a reusable template.
Create a component version that contains the cluster configuration data as a component version artifact.
Process properties to set
Configuration File: The location and name of the configuration data file. This file is created by a WebSphere Configuration Discovery step, and contains configuration data for the entire instance of WebSphere Application Server.
Output Directory: The directory for storing the template that is created by the process.
User Defined Tokenization: A list of values and their replacements, separated by newline characters. Use this list to change values or create tokens in the configuration data. Use the following format: stringToReplace->newValue. For example, if you specify abcd1234->@NewToken@, every occurrence of abcd1234 in the configuration file is replaced with @NewToken@.
Resource: The name of the cluster resource to templatize.
For static clusters, manage and templatize the server members separately. See WebSphere – Example 10 – Discover & Templatize Server.
For dynamic clusters, this process creates a dynamic cluster server template in the component version artifacts.
This process creates a component with the following naming convention: Cluster - cluster_name. The cluster configuration data is stored as a component version artifact, as shown in the following screen capture.