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 profiles > Augmenting ND profiles

Augmenting an empty node

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.

You must augment the node before you federate it to the dmgr.

• Create and process a customization definition to generate the JCL jobs, augmentation response file, and other data files for the stand-alone server.
• Set up the configuration file system and create the WebSphere Application Server profile in the file system.

• If required, create a DB2JccConfiguration.properties file to enable connection to DB2 for z/OS .
• Ensure that you have administrator authority on the system so that you can run the augmentation job.

Procedure

1. Back up the data sets that contain the node configuration, so that you can restore the data sets if necessary. See Backing up the WebSphere Application Server for z/OS system.
2. Follow the instructions that are available in the Customization Instructions view in pmt.sh perspective, in the relevant HTML file in the customization location, or in the CNTL data set in the z/OS system:
   1. Submit the job to create the tailored cataloged procedures and copy them to your procedure library. Each different node type under the root directory of the configuration file system requires its own cataloged procedures under z/OS.
   2. Submit the augmentation job BPZAUGN. This job updates the symbolic links in the configuration file system and augments the WebSphere Application Server profile with IBM BPM functions.

   3. When the job completes, view the job output to verify that your profile augmentation completed successfully. You can also review the WAS_HOME/logs/manageprofiles/default_augment.log file.
   4. Continue with the remaining steps in the customization instructions until you get to the step to federate the node into the dmgr cell.

      Important: Before you federate the node, you must ensure that the databases have been created, and then start the dmgr.

3. Optional: Back up the file system that contains the empty node configuration.

Results

The empty node is now augmented with IBM BPM functions.

What to do next

Create and augment other empty nodes, if required.

You can then federate each of the empty nodes to the dmgr cell after starting the dmgr.

Augmenting ND profiles

Related tasks:
Create and processing customization definitions for the profile
Set up the configuration file system and creating a profile
Create a DB2JccConfiguration.properties file
Federating the empty node into the dmgr cell
Troubleshooting the z/OS installation and configuration
Completing the ND configuration