Creating Process Center deployment manager profiles with a DB2 for z/OS database server using the Profile Management Tool

You can configure a deployment manager profile for Process Center using the Profile Management Tool.

About this task

The language of the Profile Management Tool is determined by the default language on the system. If the default language is not one of the supported languages, English is used. You can override the default language by starting the Profile Management Tool from the command line and using the java user.language setting to replace the default language. Enter the following command:

install_root\java\bin\java -Duser.language=locale install_root\bin\ProfileManagement\startup.jar

For example, to start the Profile Management Tool in the German language, enter the following command:

install_root\java\bin\java -Duser.language=de install_root\bin\ProfileManagement\startup.jar

Restrictions:

• To run the Profile Management Tool on Windows 7, Windows Vista, or Windows Server 2008, you must elevate your Microsoft Windows user account privileges. Whether you are an administrative user or a non-administrative user, right-click the pmt.bat file and select Run as administrator. Alternatively, use the runas command at the command line. For example, the following command can be run from the install_root\bin\ProfileManagement directory:

  runas /user:MyAdminName /env pmt.bat

  Non-administrative users are prompted for the administrator password.
• If you install multiple instances of IBM® Business Process Manager as the root user and give a nonadministrative user access to only a subset of those instances, the Profile Management Tool does not function correctly for the nonadministrative user. In addition, a com.ibm.wsspi.profile.WSProfileException or Access is denied message occurs in the install_root\bin\ProfileManagement\pmt.bat file. By default, nonadministrative users do not have access to the Program Files directory, which is the default installation location for the product. To resolve this issue, nonadministrative users must either install the product by themselves or be given permission to access the other product instances.

To use a DB2 for z/OS database, you must choose Advanced profile creation and specify a database design file.

1. Use one of the following methods to start the Profile Management Tool.
   • Start the tool from the First steps console.
   • Run the command install_root\bin\ProfileManagement\pmt.bat
2. On the Welcome page, click Launch Profile Management Tool or select the Profile Management Tool tab.
3. On the Profiles tab, click Create.

   The Environment Selection page opens in a separate window.

4. On the Environment Selection page, locate the IBM Business Process Manager Standard configuration and expand the section. Select the profile to create and click Next.
5. On the Profile Creation Options page, choose Advanced and click Next.
6. Advanced: On the Optional Application Deployment page, select whether to deploy the administrative console for managing the server (recommended). Click Next.
7. Advanced: On the Profile Name and Location page, perform the following steps:
   1. In the Profile name field, specify a unique name or accept the default value. Each profile that you create must have a name. When you have more than one profile, you can tell them apart at their highest level by this name.
   2. In the Profile directory field, enter the directory for the profile or use the Browse button to go to the profile directory. The directory you specify will contain the files that define the runtime environment, such as commands, configuration files, and log files. The default directory is install_root\profiles\profile_name.
   3. Optional: Select Make this profile the default to make the profile you are creating the default profile. This check box is shown only if you have an existing profile on your system.

      When a profile is the default profile, commands work automatically with it. The first profile that you create on a workstation is the default profile. The default profile is the default target for commands that are issued from the bin directory in the product installation root. When only one profile exists on a workstation, every command operates on that profile. If more than one profile exists, certain commands require that you specify the profile to which the command applies.

   4. From the Server runtime performance tuning setting list, select a performance tuning level appropriate for the profile you are creating. This parameter is a WebSphere® Application Server parameter.
   5. Click Next. If you click Back and change the name of the profile, you might have to manually change the name on this page when it is displayed again.
8. Advanced: On the Node, Host and Cell Names page, perform the following actions for the profile you are creating:
   • In the Node name field, enter a name for the node or accept the default value. Try to keep the node name as short as possible, but ensure that node names are unique within your deployment environment.
   • In the Server name field, enter a name for the server or accept the default value.
   • In the Host name field, enter a name for the host or accept the default value.
   • In the Cell name field, enter a name for the cell or accept the default value.

   Click Next.

9. Required: On the Administrative Security page, enter values for the User name, Password, and Confirm password. The password specified during install for administrator will be used for all internal users including tw_admin and tw_user. Because all IBM Business Process Manager profiles must have administrative security enabled, Next is enabled only after you enter the values.
10. Advanced: On the Security Certificate (Part 1) page, specify whether to create new certificates or import existing certificates.
    • To create a new default personal certificate and a new root signing certificate, select Create a new default personal certificate and Create a new root signing certificate, and click Next.
    • To import existing certificates, select Import an existing default personal certificate and Import an existing root signing personal certificate and provide the following information:
      • In the Path field, enter the directory path to the existing certificate.
      • In the Password field, enter the password for the certificate
      • In the Keystore type field, select the keystore type for the certificate you are importing.
      • In the Keystore alias field, select the keystore alias for the certificate you are importing.
      • Click Next to display the Security Certificate (Part 2) page
      When you import a personal certificate as the default personal certificate, import the root certificate that signed the personal certificate. Otherwise, the Profile Management Tool adds the signer of the personal certificate to the trust.p12 file.
11. Advanced: On the Security Certificate (Part 2) page, verify that the certificate information is correct, and click Next to display the Port Values Assignment page.

    If you create the certificates, you can use the default values or modify them to create new certificates. The default personal certificate is valid for one year by default and is signed by the root signing certificate. The root signing certificate is a self-signed certificate that is valid for 15 years by default. The default keystore password for the root signing certificate is WebAS. Change the password. The password cannot contain any double-byte character set (DBCS) characters because certain keystore types, including PKCS12, do not support these characters. The keystore types that are supported depend on the providers in the java.security file.

    When you create either or both certificates, or import either or both certificates, the keystore files that are created are:

    • key.p12: Contains the default personal certificate.
    • trust.p12: Contains the signer certificate from the default root certificate.
    • root-key.p12: Contains the root signing certificate.
    • default-signers.p12: Contains signer certificates that are added to any new keystore file that you create after the server is installed and running. By default, the default root certificate signer and a DataPower signer certificate are in this keystore file.
    • deleted.p12: Holds certificates deleted with the deleteKeyStore task so that they can be recovered if needed.
    • ltpa.jceks: Contains server default Lightweight Third-Party Authentication (LTPA) keys that the servers in your environment use to communicate with each other.

    These files all have the same password when you create or import the certificates, which is either the default password, or a password that you specify. An imported certificate is added to the key.p12 file or the root-key.p12 file. If you import any certificates and the certificates do not contain the information that you want, click Back to import another certificate.
12. Advanced: On the Port Values Assignment page, verify that the ports specified for the profile are unique and click Next. The Profile Management Tool detects ports currently used by other WebSphere products and displays recommended port values that do not conflict with existing ones. If you have applications other than WebSphere ones that use specified ports, verify that the ports do not conflict. If you chose not to deploy the administrative console on the Optional Application Deployment page, the administrative console ports are not available on the Port Values Assignment page.
    Ports are recognized as being in use if the following conditions are satisfied:

    • The ports are assigned to a profile created under an installation performed by the current user.
    • The ports are currently in use.

    Although the tool validates ports when you access the Port Values Assignment page, port conflicts can still occur resulting from selections you make on subsequent Profile Management Tool pages. Ports are not assigned until profile creation completes.
    If you suspect a port conflict, you can investigate it after the profile is created. Determine the ports used during profile creation by examining the following file:

    profile_root\properties\portdef.prop

    Included in this file are the keys and values used in setting the ports. If you discover port conflicts, you can reassign ports manually. To reassign ports, see "Updating ports in existing profiles" in the WebSphere Application Server information center. Run the updatePorts.ant file through the ws_ant script detailed in this topic.
13. Advanced: If you do not have administrative privileges, skip to the next step. If you have administrative privileges, on the Service Definition, page indicate whether to use a Windows service to run IBM Business Process Manager.
    If the profile is configured as a Windows service, IBM Business Process Manager starts Windows services for processes started by the startServer or startManager commands. For example, if you configure a server as a Windows service and issue the startServer command, the wasservice command starts the defined services.

    Important: If you choose to log on as a specified user account, you must specify the user ID and the password for the user who is to run the service, and the startup type (default is Manual). The user ID must not have spaces in its name, must belong to the Administrator group, and must have the advanced user right "Log on as a service." If the user ID belongs to the Administrator group, the Profile Management Tool grants it the advanced user right if it does not already have it.

    During profile deletion, you can remove the Windows service that is added during profile creation.

    IPv6 (Internet Protocol version 6) considerations when running profiles as Windows services

    Profiles created to run as a Windows service fail to start when using IPv6 if the service is configured to run as Local System. Create a user-specific environment variable to enable IPv6. Because this environment variable is a user variable instead of a Local System variable, only a Windows service that runs as that specific user can access this environment variable. By default, when a new profile is created and configured to run as a Windows service, the service is set to run as Local System. When the IBM Business Process Manager Windows service tries to run, the service is unable to access the user environment variable that specifies IPv6, and thus tries to start as IPv4. The server does not start correctly in this case. To resolve the problem, when creating the profile, specify that the IBM Business Process Manager Windows service runs as the same user ID under which the environment variable that specifies IPv6 is defined, instead of as Local System.

14. On the Profile Summary page, review the information. Click Create to create the profile or Back to change the characteristics of the profile.
15. On the Profile Complete page, review the information. To proceed to the First Steps Console, make sure that Launch First Steps Console is selected and click Finish.