Creating Process Server stand-alone profiles with an SQL Server database server using the Profile Management Tool

You can configure a stand-alone profile for Process Server using the Profile Management Tool on 32-bit architectures. 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. 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 Advanced: Process Server configuration and expand the section. Select the IBM BPM Advanced, Process Server Stand-alone profile and click Next.
5. On the Profile Creation Options page, choose to perform a Typical or an Advanced profile creation, and click Next. If you selected Typical profile creation, skip to the Administrative Security step.
6. Advanced: On the Optional Application Deployment page, select whether to deploy the administrative console for managing the server (recommended) and the default WebSphere® Application Server application. 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.

   Click Next. If you selected Typical profile creation, skip to the Process Server Configuration step.

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. Optional: Advanced: To include a web server definition in the profile, perform the following steps:
    1. Select Create a web server definition.
    2. Specify the web server characteristics on the page, and click Next
    3. Specify the web server characteristics on Part 2 of the page. If you use a web server to route requests to IBM Business Process Manager, you must include a web server definition. You can include the definition now, or define the web server to IBM Business Process Manager later. If you include the web server definition during the creation of this profile, you can install the web server and its plug-in after you create the profile. However, you must install both to the paths that you specify on the Web Server Definition pages. If you define the web server after you create this profile, you must define the web server in a separate profile.
    4. Click Next.
14. On the Process Server Configuration page, set the values for the following parameters.
    • Environment name: The environment name is used to connect from a Process Center to this Process Server.
    • Environment Type: Select how the Process Server is used:
      • Select Production if the server is to be used in a production capacity.
      • Select Stage if the server is to be used as a temporary location to host changes before putting them into production.
      • Select Test if the server is to be used as a testing environment, for example, for load testing.
    Restriction: Do not mix production and non-production servers in the same cell.
    Select Use this server offline if you did not select Production as the environment type or if this Process Server will not be connected to a Process Center. Offline servers can still be used when deploying snapshots of process applications, but the method for deploying process applications to an offline process server differs from the method for deploying process applications to an online process server.
    If you did not select Use this server offline, provide the following information for the Process Center that this server is to connect to:

    • Protocol: Select either http:// or https:// as the connection protocol to the Process Center.
    • Host name: Enter the host or virtual host that this Process Server will use to communicate with Process Center. Use a fully qualified host name. In an environment with a load balancer or proxy server between the Process Server and the Process Center services, make sure that what you designate here matches the URL for accessing the Process Center.
    • Port: Enter the port number of the Process Center. In an environment with a load balancer or proxy server between the Process Server and the Process Center, make sure that what you designate here matches the URL for accessing the Process Center.
    • User name: Enter the name of a Process Center user. Process Server will connect to Process Center as this user.
    • Password: Enter the password for the Process Center user.
    You can click Test Connection to check the connection to the Process Center.

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

15. Advanced: Configure the databases 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 your database information.
    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 database configuration. Then click Next to go to the Database Configuration - Part 3 page. Specify the following fields.

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

    Field	Action needed
    Do not select the Apply Windows Authentication option.
    Common database	For the Common database, enter values for the following parameters: User name Enter the Common database user name. Password Enter a password to authenticate with the Common database. Confirm password Confirm the password to authenticate with the Common database.
    Process Server database	For the Process Server database, enter values for the following parameters: User name Enter the Process Server database user name. Password Enter a password to authenticate with the Process Server database. Confirm password Confirm the password to authenticate with the Process Server database.
    Performance Data Warehouse database	For the Performance Data Warehouse database, enter values for the following parameters: User name Enter the Performance Data Warehouse database user name. Password Enter a password to authenticate with the Performance Data Warehouse database. Confirm password Confirm the password to authenticate with the Performance Data Warehouse database.
    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.
    Directory location 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

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

    Field	Action required for SQL Authentication	Action required for Windows Authentication
    CEI messaging engine schema name SCA Application bus messaging engine schema name SCA system bus messaging engine schema name Process Server messaging engine schema name Performance Data Warehouse messaging engine schema name	Messaging engine tables must be configured with different users and passwords. They cannot use the same user and password as any other messaging engine. Note: For SQL Authentication, the schema names are mapped to the user IDs.	Messaging engine tables must be configured with different schema names. They cannot use the same schema name as any other messaging engine.

    If you plan to use Microsoft SQL Server 2005 or Microsoft SQL Server 2008 with a stand-alone profile, and put the messaging engine tables into the Common database, you must create the following schemas in the CMNDB database as owner dbo using the SQL Server Studio. These schemas are required for the SIBus messaging engines.

    Important: You must configure these schemas either before you start the server and messaging engine (recommended) or while the messaging engine is starting. Note that these are the default values if Windows Authentication is selected. You can specify different values. For SQL Authentication, the values are the same as the specified user IDs.

    • MEDSS00 (Service Component Architecture (SCA) System Bus Messaging Engine)
    • MEDSA00 (Service Component Architecture (SCA) Application Bus Messaging Engine)
    • MEDCM00 (Common Event Infrastructure Bus Messaging Engine)
    • MEDPS00 (Process Server messaging engine)
    • MEDPE00 (Performance Data Warehouse messaging engine)

    For stand-alone configurations only, when you configure the Process Server database, the Process Server messaging engine tables are created in the Process Server database. When you configure the Performance Data Warehouse database, the Performance Data Warehouse messaging engine tables are created in the Performance Data Warehouse database. The Service Component Architecture (SCA) system, SCA application, and Common Event Infrastructure (CEI) messaging engine tables are all created in the Common database.

    For stand-alone configurations only, there are some additional considerations for the users and schemas.

    • SQL Authentication: The Service Component Architecture (SCA) system, SCA application, and Common Event Infrastructure (CEI) messaging engine tables must be configured with different users and passwords. They cannot use the same user and password as any other messaging engine.
    • Windows Authentication: With Windows Authentication, because the user and password are always going to be the same, all messaging engines must have custom schemas defined so that the tables can be created with a different schema for each messaging engine. When the messaging engines are configured, the schemas are automatically created using the Windows user. If the Windows user does not have privileges to create the schemas, they must be created before the product is configured.
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.