[z/OS]

Enabling a z/OS application server for Feature Pack for EJB 3.0

You can use the Profile Management tool to enable the Feature Pack for EJB 3.0 on a z/OS application server.

Before you begin

Install the Feature Pack for EJB 3.0 code on z/OS, and mount the feature pack code filesystem on the target z/OS system.

Install the Profile Management fool for z/OS at the Version 6.1.1.5 level, or upgrade an existing copy of the Profile Management tool for z/OS to Version 6.1.1.5. For more information about installing the Profile Management tool, refer to Installing the Application Server Toolkit and Using the Profile Management Tool.

Select a stand-alone application server to enable for the feature pack.

Avoid trouble Avoid trouble: Managed application server nodes, including previously federated application server nodes, cannot be augmented with WebSphere Application Server Version 6.1 feature packs. After you enable an application server for the feature pack, you can federate that application. Any new application servers created in that federated node are then automatically enabled for the feature pack.gotcha

About this task

Complete the following steps to enable the Feature Pack for EJB 3.0 on a z/OS application server.

Procedure

  1. Launch the Profile Management tool for z/OS.
  2. From the customization definition type pane, select the Augment button.
    1. Read the Welcome panel, click Next.
    2. On the following panel, select Feature Pack for EJB 3.0, click Next.
    3. On the panel Enable an existing application server with Feature Pack for EJB 3.0, select the application server you want to enable for the feature pack.
    4. Click Next.
  3. On the panel "Customization Name and Location" enter the customization definition name, directory location and response file pathname, if you are using a similar definition to preload the default values, click Next.
  4. From the "Target datasets" panel enter datasets in which new augmentation jobs will be stored and uploaded to z/OS, click Next.
  5. On the "File System Location" panel specify the following:
    1. The home directory (WAS_HOME) of the application server whose profile you want to augment with the feature pack.
    2. Product file system directory, the location of WebSphere Application Server Version 6.1 directory
    3. The Feature Pack for EJB 3.0 product files, the location of the EJB 3.0 product files
    4. Click Next
    Note: If an error should occur during the process of creating the customization definition, a window will display the location of a log file. Review the log file for more details about the issue.
  6. Review the "Job Statement Definitions" panel, and make any required changes, click Next.
  7. Review the "Customization Summary" panel, click Next.
  8. At this time the Profile Management tool has created a response file and a customization job that can be used to augment a WebSphere Application Server for z/OS application server node. This augmentation updates 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, the upload action or the run action.
    To use the upload action
    Note: This action uploads the customization job and associated data that was created to the target z/OS system. After you complete the upload, you need to submit the customization job to generate the required symbolic links and update the target profile.
    1. Upload the customization jobs. Use the Profile Management tool upload action to upload the customization job and associated data to the target z/OS system. The data is written to the following partitioned data sets:
      • hlq.CNTL
      • hlq.DATA
    2. Stop the target application server.
    3. Back up the target configuration file system.
    4. Run the job IWOFAUGA. This job generates two sets of symbolic links. The first set of symbolic links is for the target configuration file system to the feature pack enablement code installation image. The second set of symbolic links to the Feature Pack for EJB 3.0 installation image. It also updates the profile in the target configuration file system for this feature pack.
    5. Restart the application server.
    To use the run action.
    Note: The run action is not yet supported.
    The run action will generate the required symbolic links and augment the target profile.
    Note: Use this procedure only if the target z/OS system has an active remote exec daemon (rexecd).
    1. Stop the target application server.
    2. Back up the target configuration file system.
    3. Update the target profile. Use the Profile Management tool run action to update the target profile. The run action generates two sets of symbolic links. The first set of symbolic links is for the target configuration file system to the feature pack enablement code install image. The second set of symbolic links is to the Feature Pack for EJB 3.0 install image. The action completes both of these before it updates the profile.
    4. Restart the application server.

Results

When this task is complete, your existing WebSphere Application Server for z/OS application server is now enabled for the Feature Pack for EJB 3.0.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tins_pmtaugbasealt
File name: tins_pmtaugbasealt.html