Instructions for Augmenting a WebSphere Application Server for z/OS Managed Node

The managed node will be augmented with:

The Profile Management Tool has created a response file that can be used to augment a WebSphere Application Server for z/OS managed node. This augmentation will update the runtime profile to configure ${productName} on the target node based on the information you provided.

Augmentation Steps

Complete the following steps to perform the augmentation:

1. Create and upload the customization job.

   Use the PMT Process action to create the customization job and associated data and upload these files to the target z/OS system. The files will be written to the following partitioned data sets:

        ${zTargetHLQ}.CNTL
        ${zTargetHLQ}.DATA
   

   
   
   
2. Stop the target managed node.
   
   
   
   
3. Back up the target configuration file system.
   
   
   
   
4. Run job ${jobnamePrefix}AUGN.

   This job generates symbolic links within the target configuration file system to the feature pack enablement code (which is contained within the base WebSphere install image) and the ${productName} install image. It also augments the profile in the target configuration file system for ${productName}.

   This job must be run under a user ID with the Unix System Services files access privileges:

   • Either uid=0, OR
     
     
   • the following UNIXPRIV class profile privileges:

     CONTROL access to SUPERUSER.FILESYS             
     READ    access to SUPERUSER.FILESYS.CHOWN       
     READ    access to SUPERUSER.FILESYS.CHANGEPERMS
     

     If the UNIXPRIV profile CHOWN.UNRESTRICTED is defined, then the SUPERUSER.FILESYS.CHOWN is not required. For information about the UNIXPRIV class, see the z/OS Unix System Services Planning book.

   If the managed node being updated is using a LocalOS (SAF) user registry, the user ID used to run this job must be connected to the managed node's configuration group.

   If SSL certificates are stored in the SAF keyrings, then the user ID used to run this job must have a SAF keyring whose name matches the value of com.ibm.ssl.keyStore in the ${zConfigMountPoint}/${zWasServerDir}/profiles/default/properties/ssl.client.props file, and this keyring must contain the managed node's CA certificate.

   
   
   
5. Restart the managed node.

   The target managed node is now augmented to include ${productName}.