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 > Create and processing customization definitions for profiles > Use zPMT

Create customization definitions for fully customized profiles

To create a customization definition for a stand-alone server, dmgr, or empty managed node profile, you must collectively define the customization settings for WebSphere Application Server and IBM BPM in the z/OS Profile Management Tool (zPMT).

• Install the WebSphere Application Server product code and the IBM BPM product code in the z/OS system.
• Determine your topology and collate the customization information for your stand-alone or ND configuration.

• Install the WebSphere Customization Toolbox.
• Download the IBM BPM for z/OS extension to the WebSphere Customization Toolbox workstation. Optionally download the sample customization definition response files.

• Install the extension into the WebSphere Customization Toolbox.

When you create the customization definition for a profile, the customization settings that you specify in the zPMT windows are saved in a set of files on the workstation. Before you begin to define the settings, you must identify a customization location (or parent directory) in which to store the files. You can save multiple customization definitions in the same customization location, or you can use more than one customization location if you want to separate your customization definitions into logical groupings.

A customization response file is written whenever you create a customization definition. This file contains name-value pairs of the settings that you specify in zPMT. When creating a customization definition, you can use one of the supplied sample customization response files, or another existing response file, as a shortcut, to populate the zPMT windows with similar values to those you want to define. For maximum benefit, use a response file with a customization-definition type that matches the profile you want to create; for example, use a dmgr response file if you are creating a dmgr profile.

When defining the customization settings for a stand-alone server or dmgr, you can specify how to configure the databases for the IBM BPM components.

You can either indicate that you want to use a database design file to define the database configuration, or you can define the database configuration directly in the zPMT windows:

• If you intend to create your databases in a DB2 for z/OS subsystem, you must always use a database design file to define the database configuration. When prompted in the relevant zPMT window, ensure that you specify a fully qualified UNIX-style path for the database design file in the z/OS system; for example, /WebSphere/V8T8DM/DeploymentManager/util/dbUtils/bpm.advanced.nd.topology.dbDesign. If the file does not yet exist, you can specify a fully qualified file name (with a .dbDesign file extension) and then create the file later in the z/OS system by using the database design tool. This tool provides flexibility for the database design because you can use it to specify different configuration values for the various database components.

  If the file does not yet exist, make a note of the specified file name and file location so that you can use these settings when you create the database design file in the z/OS system.

  Also ensure that the Run database scripts to create the database tables check box is clear. At a later stage in the configuration process, you can use the database design tool to generate the required database scripts, and then use the createDB2.sh script or other tools to run the database scripts to create the database tables.

• If you are using a database product other than DB2 for z/OS, a database design file remains the preferred option, but you can alternatively choose to specify the database configuration properties directly in the zPMT windows. When you define the database configuration in zPMT, you are constrained to specifying the same set of configuration values for all the database components. If you are using a remote database, also ensure that the Run database scripts to create the database tables check box is clear.

You can also indicate whether you want to create an intermediate symbolic link that the configuration file system can use to access the product file system that contains the WebSphere Application Server and IBM BPM product code. This level of indirection makes it possible to switch to a new or different server level of IBM BPM by changing the single intermediate symbolic link. If you do not create an intermediate symbolic link, the configuration file system uses a direct symbolic link to access the product file system.

If you intend to connect to a Process Center repository that is installed and configured on Linux, Windows, or UNIX, you can also use zPMT to specify the web address for accessing the Process Center; for example, http:// host_name: port/ProcessCenter. The Process Center serves as a central repository for all processes, services, and other assets that are created in the IBM BPM authoring environments (Process Designer and Integration Designer). For more information about installing, configuring, and managing the Process Center repository, see The Process Center repository, Install IBM BPM Advanced, and Manage assets in the Process Center repository.

Procedure

1. Start zPMT in the WebSphere Customization Toolbox (if not already started):
   
   • On Linux. Use the menus used to start your programs.

     For example, click Linux_operating_system_menus > IBM WebSphere > WebSphere Customization Toolbox V8.5. Then click Profile Management Tool to open pmt.sh perspective.

   • On Windows. Click Start > All Programs > IBM WebSphere > WebSphere Customization Toolbox V8.5 > Tools > Profile Management Tool for z/OS.

   You must now specify a new or existing customization location in which to save your customization definition files. The customization location directory can be on a local or network drive, and the operating system must recognize the drive and have access to it.

2. In the Customization Locations view, click Add.

3. In the Add Customization Location window, choose either of the following options:

   • Add an existing customization location. Specify the directory path if you want to add an existing customization location to the list of locations that you can access in zPMT. This option is useful for sharing customization locations across installations of the WebSphere Customization Toolbox, and enables you to reuse or modify previously created customization definitions. You can also use this option for backup purposes.

   • Create a new customization location. Complete the fields as follows:

     Name

     Enter meaningful text that you can use to identify the generated customization response file and instructions in the customization location.

     Version

     Select 8.0 as the version of WebSphere Application Server for z/OS that will be customized by the definitions contained in this location. The 8.0 value is the only valid entry for this field.

     Location

     Specify the full directory path in which to store the customization definition files. This directory can either be an empty existing directory, or a new directory to be created.

4. Click Finish to add the customization location to your working set in zPMT. You must now define the customization values for creating and configuring the runtime environment.

5. In the Customization Locations view, ensure that the location to which you want to save the customization definition is selected. In the Customization Definitions view, click Create.

6. In the Environment Selection window, locate IBM BPM Advanced: Process Server for z/OS v8.0, and select the type of environment to create:
   • Deployment manager with IBM BPM Advanced: Process Server for z/OS v8.0

   • Application server with IBM BPM Advanced: Process Server for z/OS v8.0
   • Managed (custom) node with IBM BPM Advanced: Process Server for z/OS v8.0

7. Click Next.

8. In the Customization Definition Name window, complete the fields as follows:

   Customization definition name

   Accept the default value or specify a unique meaningful name that you can use to identify the customization definition in zPMT. Use alphanumeric characters for the name.

   Tip: This value is also used to construct a subdirectory name in the customization location, and is used as the stem of the customization response file name that is created in the customization location.

   Response file path name (optional)

   To populate the subsequent zPMT windows with a set of preconfigured values, you can specify the full path to a customization response file (of a matching or similar profile type) that was created earlier.

   You can also specify one of the downloaded sample customization response files:

   Sample customization response files for a stacked installation

   Operating system	Sample file
   Linux	Sample file for a stand-alone DB2 for z/OS stacked configuration: full_dir_path/ZBPMPSStandaloneDB2Stacked.WCT.responseFile Sample file for a dmgr DB2 for z/OS stacked configuration: full_dir_path/ZBPMPSDMgrDB2Stacked.WCT.responseFile
   Windows	Sample file for a stand-alone DB2 for z/OS stacked configuration: full_dir_path\ZBPMPSStandaloneDB2Stacked.WCT.responseFile Sample file for a dmgr DB2 for z/OS stacked configuration: full_dir_path\ZBPMPSDMgrDB2Stacked.WCT.responseFile

   Server runtime performance tuning setting

   This field is available only if you are creating a stand-alone server. Specify the performance-tuning setting that most closely matches the type of environment in which the application server will run:

   • Select Standard as the performance setting for general-purpose usage.

   • Select Peak as the performance setting for a production environment where application changes are rare and optimal runtime performance is important. The WebSphere Application Server installation on the target z/OS system must, at a minimum, be at the 8.0.0.3 service level.

9. Click Next.

10. Complete the rest of the windows to set up the customization definition, using the Back and Next buttons as necessary.

    Tip: To help you complete the required entries in each window, detailed help information is included within the body of text in the windows, or as hover help when you move the cursor over a field.

11. When you get to the Customization Summary window, review the details and click Create to create the customization response file and customization instructions.

    These files are created in a profiles subdirectory in the specified customization location.

12. In the Customization Definition Summary window, click Finish to close the window. In pmt.sh perspective, the following details are displayed in the tab views:
    • Customization Definitions: Displays an entry for the customization definition that was created.
    • Customization Summary: Displays details about the customization definition name, the configured environment type, the customization location path, and the file names for the customization response file and instructions. Also displays the z/OS target data sets to which generated jobs and other customization data are uploaded.
    • Customization Instructions: Displays instructions for generating the customized JCL jobs. Describes manual configuration updates that might be required on the z/OS system before you run the jobs. Identifies the requirements of the ID under which the jobs run. Also describes the sequence for submitting the jobs to create the WebSphere Application Server for z/OS profile and to augment it with IBM BPM for z/OS functions.
    • Customization Response File: Displays the configuration information that you specified in the zPMT windows, as a set of name-value pairs.

What to do next

You can now process the customization definition.

Create and processing customization definitions using zPMT

Related concepts:
About the WebSphere Customization Toolbox and the z/OS Profile Management Tool
Generate a design file and database scripts for the database objects

Related tasks:
Obtaining and installing the product code
Installing the WebSphere Customization Toolbox
Downloading the extension file and sample customization response files
Installing the product extension for zPMT
Processing customization definitions for fully customized profiles

Related reference:
Collating customization information for configuring your environment
Sample customization response files