Augmenting network deployment profiles

In a network deployment environment, you must install IBM® Business Process Manager on each node that is in the deployment manager cell. After setting up the configuration file systems and creating deployment manager and empty managed node profiles, you must augment the deployment manager and empty managed nodes with IBM Business Process Manager for z/OS® functions.

About this task

When you run the JCL job that augments a profile, an augmentation response file is required to provide input to the augmentation job. This response file contains the definitions of how you want to configure the profile. The response file is created when you use the z/OS Profile Management Tool or the zpmt.sh script to process the customization definition for a deployment manager or an empty managed node. In the z/OS system, the augmentation response file is stored in the specified DATA target data set and is named BPZRSPx, where x is one of the following characters:
  • D for a deployment manager node
  • N for a managed node

Before you augment the profile, also ensure that connection to DB2® for z/OS is possible. If necessary, you can create a DB2JccConfiguration.properties file for this purpose.

  • Creating a DB2JccConfiguration.properties file
    You might require a DB2JccConfiguration.properties file to help establish a connection between your data source and the DB2 for z/OS database. If the DB2 subsystem ID (SSID) is not already specified in the DSNHDECP module, you can identify the DB2 subsystem to which you want to connect by creating a DB2JccConfiguration.properties file with the relevant setting.
  • Augmenting deployment manager profiles
    When you process the customization definition for a deployment manager, several JCL jobs are generated for creating and augmenting the default WebSphere Application Server profile. After you create the profile, you can run the JCL job that augments the deployment manager node.
  • Augmenting empty nodes
    When you process the customization definition for an empty managed node, several JCL jobs are generated for creating and augmenting the default WebSphere Application Server profile. After you create the profile, you can run the JCL job that augments the empty managed node.
Parent topic: Creating and augmenting IBM Business Process Manager for z/OS profiles