This topic applies only on the z/OS operating system.

Using the Profile Management Tool to enable existing z/OS managed (custom) nodes for the Java Persistence API 2.0 feature

You can use the Profile Management Tool to enable the Java Persistence API 2.0 feature of the Feature Pack for OSGi Applications and Java Persistence API 2.0 on an existing z/OS managed (custom) node.

Before you begin

Before starting this procedure, perform the following actions:
  1. Install the feature-pack code on the target z/OS® system.

    For more information, read Installing and configuring the feature pack on z/OS systems.

  2. Install the workstation-based WebSphere® Customization Tools, which include the Profile Management Tool.
  3. Install the Java Persistence API 2.0 feature extension for the Profile Management Tool.

    For more information, read Installing and configuring the feature pack on z/OS systems.

  4. Fill out a copy of the z/OS augmentation worksheet: Managed (custom) nodes with the Java Persistence API 2.0 feature for the managed (custom) node that you want to enable for the Java Persistence API 2.0 feature.

Procedure

  1. Start the Profile Management Tool.
  2. Create a customization definition for augmenting a profile with the Java Persistence API 2.0 feature of the Feature Pack for OSGi Applications and Java Persistence API 2.0.

    For more information, read z/OS augmentation worksheet: Managed (custom) nodes with the Java Persistence API 2.0 feature.

    1. In the Customization Locations table, select the location of the customization definition that you want to create.
    2. Click the Customization Definitions tab if it is not already selected.
    3. Click Augment.
    4. Select Managed (custom) node.
    5. Click Next.
    6. Select Managed (custom) node with the JPA 2.0 feature with the appropriate version number.
    7. Click Next.
    8. Complete the fields in the panels using the configuration values that you entered for the variables on the configuration worksheet that you created, clicking Back and Next as necessary.
      Tips:
      • Hover your cursor over a field for help information.
      • Click Cancel at any time to leave the creation process without generating a customization definition.
      When you have successfully entered all of the necessary information on the panels for this type of customization definition, the Profile Management Tool displays the definition type, location, and name on the Customization Summary panel.
    9. Click Create.
    10. Click Finish.
      Tips:
      • You might want to make a note of the customization definition name and response-file location for future reference.
      • If you just make note of the name, you can get the response file location later from the Customization Summary panel after you select the customization definition name.
  3. Review the customization definition response file to confirm that the values are correct.
  4. Click Process to upload the customization jobs and instructions to the target z/OS system or export them to the file system.
  5. Follow the generated instructions, which you can view using one of the following methods:
    • In the Profile Management Tool, select the desired customization definition and select the Customization Instructions tab.
    • After you upload the definition, view the IWOMINSN job in the target CNTL dataset, which contains a text version of the instructions.
  6. If you encounter problems caused by your values in the customization definition, modify your variables using the Profile Management Tool, regenerate the instructions, and upload the customization definitions again.
    Notes:
    • Do not attempt to fix a typographical error or make a change by modifying the generated output. Many of the variables are used in multiple members of the target datasets; if you do not change them all, therefore, you might experience errors that are difficult to diagnose.
    • Remember that you cannot upload new customization jobs while either configuration dataset is open.

Results

Your existing WebSphere Application Server for z/OS managed (custom) node is enabled for the Java Persistence API 2.0 feature of the Feature Pack for OSGi Applications and Java Persistence API 2.0.

What to do next

Augment the deployment manager for the managed node with the Feature Pack for OSGi Applications and Java Persistence API 2.0 and Java Persistence API 2.0 feature.



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    

Terms of Use | Feedback

Last updated: Oct 22, 2010 3:02:28 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700osgijpa&product=was-nd-mp&topic=tins_augmn_enable_jpa2_zos
File name: tins_augmn_enable_jpa2_zos.html