Augmenting deployment manager profiles for Process Server with an SQL Server database server using the Profile Management Tool

You can use the Profile Management Tool to augment an existing WebSphere® Application Server V8.0 deployment manager profile on a 32-bit architecture. For 64-bit architectures on Solaris, use the manageprofiles command-line utility.

Eclipse*spacing:0
Eclipse*fontList:-misc-fixed-medium-r-normal-*-10-100-75-75-c-60-iso8859-1

xrdb -load user_home/.Xdefaults

install_root/java/bin/java -Duser.language=locale install_root

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

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.sh.
2. Shut down any servers associated with a profile you plan to augment.
3. On the Welcome page, click Launch Profile Management Tool or select the Profile Management Tool tab.
4. On the Profiles tab, select the profile that you want to augment and click Augment. If you augment a WebSphere Application Server profile, it must be from the version of WebSphere Application Server on which IBM® Business Process Manager is installed. The Augment button cannot be selected unless a profile can be augmented. The Augment Selection page opens in a separate window.
5. On the Augment Selection page, select the type of augmentation you want to apply to the profile. Then click Next.
6. On the Profile Augmentation Options page, choose to perform a Typical or an Advanced profile augmentation, and click Next.

   The Typical option augments a profile with default configuration settings.

   The Advanced option lets you specify your own configuration values for a profile.

   Restriction: The Profile Management Tool displays a warning message if any of the following conditions occur:

   • The profile you selected to augment has a running server. You cannot augment the profile until you stop the server or click Back and choose another profile that does not have running servers.
   • The profile you selected to augment is federated. You cannot augment a federated profile. You must click Back and choose another profile that is not federated.
   • The profile you selected to augment is already augmented with the product you selected. You must click Back and choose another profile to augment.
7. If you selected Typical profile creation, skip to the Administrative Security step.
8. Advanced: On the Optional Application Deployment page, select whether to deploy the administrative console for managing the server (recommended). Click Next.
9. 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.
10. 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.

11. 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.

    Click Next. If you selected Typical profile creation, skip to the Database Configuration - Part 1 step.

12. 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.
13. 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.
14. 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.
15. Advanced: Configure the Common database using a design file.
    1. Select Use a database design file.
    2. Click Browse.
    3. Specify the fully qualified path name for the design file.
    4. To run the database scripts automatically (as part of the profile creation process), select Run database scripts to create database tables. Otherwise, you or the database administrator must run the scripts manually after profile creation completes. You must also load the database with system information by running the bootstrapProcessServerData command.
       Important: If you select Run database scripts to create database tables, ensure that Use an existing local or remote database is not selected. If both options are selected, errors occur.
    5. Click Next. If you choose to specify a design file, the database configuration panels in the Profile Management Tool are skipped. Instead, the design file location is passed to the command line to complete the database configuration.

    Skip to the Business Space Configuration step

16. On the Database Configuration - Part 1 page, specify the information for the Common database.
    1. From the Select a database product list, select Microsoft SQL Server.
    2. Optional: If you want to change the default values, enter new names for the required databases. The database names must be unique.
    3. To run the database scripts automatically as part of the profile creation process, select Run database scripts to initialize the databases. Otherwise, you or the database administrator must run the scripts manually after profile creation completes. You must also load the database with system information by running the bootstrapProcessServerData command.
    4. Click Next.
17. On the Database Configuration - Part 2 page, complete the configuration for the Common database. Specify the following fields.

    Table 1. Required database configuration fields for Microsoft SQL Server - Part 2

    Field	Action needed
    Select the Apply Windows Authentication option to indicate that you will connect to your databases using your Windows authentication information. If you select this option, the Process Server database, Performance Data Warehouse database, and Common database fields are made inactive.
    Common database user name	Enter the user name to authenticate with the database.
    Common database password	Enter a password to authenticate with the database.
    Confirm password	Confirm the password.
    Location (directory) of JDBC driver classpath files	The JDBC 2.0 driver classpath files (sqljdbc4.jar) are packaged with the product and are located in the following directory: ${WAS_INSTALL_ROOT}\jdbcdrivers\SQLServer
    Database server host name (for example IP address)	Accept the default value of localhost or enter the correct database server host name.
    Server port	Accept the default value of 1433 or enter the correct server port number.

18. Advanced: On the Business Space Configuration page, if you want to configure IBM Forms Server to work with Human Task Management widgets in Business Space, select Configure IBM Forms Server and enter the HTTP location of the IBM Forms Server translator and IBM Forms Server installation root. Then click Next.
19. Advanced: Select whether to configure a Business Process Rules Manager for the installation and click Next. Business Process Rules Manager is a web application that customizes the business rules templates for your business application needs.
20. On the Profile Summary page, review the information. Click Create to create the profile or Back to change the characteristics of the profile.
21. 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.