Augmenting a WebSphere for z/OS application server with the Feature Pack for EJB 3.0.

The Profile Management Tool has created a response file and a customization job that can be used to augment a WebSphere for z/OS application server node. This augmentation will update the runtime profile to configure Feature Pack for EJB 3.0 on the target node based on the information you provided.

You have a choice between two procedures that can be used to perform the augmentation:

  1. Perform the Upload action.

    The Upload action will upload the customization job and associated data that was created to the target z/OS system. You will then need to submit the customization job to generate the required symbolic links and augment the target profile.

  2. Perform the Run action.

    The Run action will generate the required symbolic links and augment the target profile. It requires an active remote exec daemon (rexecd) on the target z/OS system.

    Note: The Run action is not yet supported.

Using the Upload action

Complete the following steps to perform this task:

  1. Upload the customization jobs.

    Use the zPMT Upload action to upload the customization job and associated data to the target z/OS system. The data will be written to the following partitioned data sets:

         ${zTargetHLQ}.CNTL
         ${zTargetHLQ}.DATA
    
    Status of task Date
         


  2. Stop the target application server.

    Status of task Date
         


  3. Back up the target configuration file system.

    Status of task Date
         


  4. Run job IWOFAUGA.

    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 Feature Pack for EJB 3.0 install image. It also augments the profile in the target configuration file system for Feature Pack for EJB 3.0.

    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 application server being updated is using a LocalOS (SAF) user registry, the user ID used to run this job must be connected to the application server'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 ${zWasHome}/profiles/default/properties/ssl.client.props file, and this keyring must contain the application server's CA certificate.

    Status of task Date
         


  5. Restart the application server.

    The target application server is now augmented to include the Feature Pack for EJB 3.0.

    Status of task Date
         


Using the Run action

Complete the following steps to perform this task:

Note: This procedure can only be used if the target z/OS system has an active remote exec daemon (rexecd).

  1. Stop the target application server.

    Status of task Date
         


  2. Back up the target configuration file system.

    Status of task Date
         


  3. Augment the target profile.

    Use the zPMT Run action to augment the target profile. The Run action will generate the necessary 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 Feature Pack for EJB 3.0 install image before it augments the profile.

    Status of task Date
         


  4. Restart the application server.

    The target application server is now augmented to include the Feature Pack for EJB 3.0.

    Status of task Date