IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced for z/OS: Process Server > Configure IBM BPM Advanced for z/OS: Process Server > Create and augmenting profiles
Augmenting stand-alone and ND profiles
After creating the WebSphere Application Server profile, you must augment the application server, dmgr, or empty node to add support for IBM BPM for z/OS functions.
When you run the JCL job that augments the 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 stand-alone server, a dmgr, 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 BPZRSP x, where x is one of the following characters:
- "A" for a stand-alone application server node
- "D" for a dmgr 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.
- Create 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 a stand-alone profile
When you process the customization definition for a stand-alone server, 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 stand-alone server node.- Augmenting ND profiles
In an ND environment, you must install IBM BPM on each node that is in the dmgr cell. After setting up the configuration file systems and creating dmgr and empty managed node profiles, you must augment the dmgr and empty managed nodes with IBM BPM for z/OS functions.