IBM BPM, V8.0.1, All platforms > Install and configure IBM BPM > IBM BPM Advanced: Process Server > Install and configure IBM BPM Advanced: Process Server > On Windows > Network deployment environment > Modify an existing installation

Customize the Process Server or Process Center cluster to work with a web server

After install IBM BPM, you must customize your environment so that it can function properly as a cluster with a web server.

Before you begin

Verify that the Process Server has been installed and configured, and that you have created and configured the servers and clusters. You cannot start the cluster until you complete the procedures in this topic.

About this task

The procedures in this topic describe how to:

Modify the XML configuration files on the deployment manager profile is the right thing to do. Make sure to only work in the file system of the dmgr profile. However, you need to hand-edit this file. These changes are not replicated by using the usual syncNode command or by using the Synchronize button in the WAS admin console. You need to use a full resynchronize to copy all files from the dmgr to the nodes, including changes that WebSphere Application Server does not track.

Procedure

  1. Configure the 100Custom.xml file in both the Process Server and the Process Center to point to a web server. Before you directly edit the 100Custom.xml configuration file, create a backup file for it. Add a .bak extension to keep the file safe.

    1. Stop the dmgr.

    2. Open the 99Local.xml file and locate the <authoring-environment> section.

    3. Copy and paste that section into the 100Custom.xml file.

    4. Update the text that you pasted into the 100Custom.xml file with a merge="mergeChildren" qualifier. If there is no web server, then all URLs in the 100Custom.xml files point to the cluster member host name and port. If there is no web server, the cluster server member xml files do not need to be changed.

      If you have a web server, change all values to point to the web server host name and port with the actual host name and port of the web server.

      If you are using the default port for http (80) or https (443), the port is an optional part of the URL. Ensure that you do not leave any tokenized value in the 100Custom.xml file. Here is an example of an entry after changes have been made:

      <authoring-environment merge="mergeChildren">
        <!--  Prefix for serving images in the Authoring Environment  -->
        <images-prefix merge="replace">https://server1.ibm.com:9447/teamworks</images-prefix>
      
        <!-- Prefix for URLs that refer to the portal -->
        <portal-prefix merge="replace">https://server1.ibm.com:9447/portal</portal-prefix>
      
        <!-- Prefix for URLs that refer to the repository view -->
        <repository-prefix merge="replace">https://server1.ibm.com:9447/ProcessCenter</repository-prefix>
      
        <servlet-prefix merge="replace">https://server1.ibm.com:9447/teamworks</servlet-prefix>
      
        <!-- Prefix for URLs that refer to the web api -->
        <webapi-prefix merge="replace">https://server1.ibm.com:9447/webapi></webapi-prefix>
      </authoring-environment>
      

    5. If you do not plan to continue with the rest of this procedure, start the dmgr. Otherwise, continue to the next step.

    6. Save the updates. In the administrative console, click Full Synchronize to synchronize the information to all the nodes.

    7. Restart the server.

  2. If you configure Process Center to use a web server, the URL that is used by clients to reach Process Center also changes. Online Process Servers regularly send http requests to Process Center, so every online Process Server must be configured to use the port of the web server.

    For example, port 9443 changes to port 443 for https. To change the Process Server from offline mode to online mode for use with a web server, follow these steps:

    1. Stop the dmgr.

    2. Open the 99Local.xml file and locate the following text:
      <repository-server-url>https://w2k8-64bitp.austin.ibm.com/ProcessCenter</repository-server-url>
      <repository-server-interval>10</repository-server-interval>
      (uncomment the following lines if you want to use https, which is usually advisable)
      <!-- Force Process Center Server to use https to deploy process applications and toolkits to Process Servers -->
      <!-- <deploy-snapshot-using-https>true</deploy-snapshot-using-https>
      <!-- Force Process Center Server to use https to deploy process applications and toolkits to Process Servers -->
      <!--
      <!-- Here HTTPS is enabled and the https port is used -->
      <deploy-snapshot-using-https>true</deploy-snapshot-using-https>
      <server-name>Process Server</server-name>
      <server-description>Process Server Production Cluster</server-description>
      <server-host>w2k8-64bitps1.austin.ibm.com</server-host>
      <server-port>443</server-port>
      <environment-type>Production</environment-type>
      
      In the previous example:

      • <repository-server-url>https://w2k8-64bitp.austin.ibm.com/ProcessCenter</repository-server-url> is the host name of the Process Center cluster web server. The first URL (repository-server-url) starts with https, but has no port number, because 443 is the default port for https, just as 80 is the default for http.

      • <repository-server-interval>10</repository-server-interval> is the repository server interval, which is set to -1 by default. Change it to a positive number such as 10. This value determines how often (measured in seconds) the Process Server sends connection data to the Process Center.

      • <server-host>w2k8-64bitps1.austin.ibm.com</server-host> is the host name of the Process Server cluster web server.

      • <server-port>443</server-port> is the Process Server web server https port. (If you are using http, specify the http port 80.)

    3. Copy and paste that text into the 100Custom.xml file.

    4. Edit the connection values in the 100Custom.xml file located on the Process Server cluster machine. Important: To prevent the values in 99Local.xml from being used instead of the ones that you have edited in 100Custom.xml, add merge="replace" attributes to the parent tree and to each line of the calls that you edited.

    5. If you do not plan to continue with the rest of this procedure, start the dmgr. Otherwise, continue to the next step.

    6. Synchronize the node agents from the administrative console.

      For information on how to synchronize node agents, see the syncNode command in the WebSphere Application Server information center.

  3. To set the Process Center to Process Server communication to work with HTTP over SSL or HTTP Secure (HTTPS).

    1. Import the Process Server SSL certificate into Process Center:

      1. On the Process Center administrative console, click Security > SSL certificate and key management > Manage endpoint security configurations > any node > Key stores and certificates > CellDefaultTrustStore > Signer certificates > Retrieve from port.

      2. Enter an alias, the host name, and secure port of the Process Server web server. The default IHS web server secure port is 443.

        If there is no web server, the host name and port values are the same as the host name and port values of the Process Center cluster member.

      3. Click Retrieve signer information, click Apply and Save.

      4. Restart the cluster.

    2. Import the Process Center SSL certificate into Process Server:

      1. On the Process Server administrative console, go to Security > SSL certificate and key management > Manage endpoint security configurations > any node > Key stores and certificates > CellDefaultTrustStore > Signer certificates > Retrieve from port.

      2. Enter an alias, the host name, and secure port of the Process Server web server. The default IHS web server secure port is 443.

        If there is no web server, the host name and port values are the same as the host name and port values of the Process Center cluster member.

      3. Click Retrieve signer information, click Apply and Save.

      4. Restart the cluster.

    3. Open the 99Local.xml file located in each Process Center cluster and locate the following text:
      <deploy-snapshot-using-https>true</deploy-snapshot-using-https>
      

    4. Copy and paste that text into the 100Custom.xml file in each Process Center cluster.
      <deploy-snapshot-using-https merge="replace">
      true
      </deploy-snapshot-using-https>
      

    5. For all the URLs in 100Custom.xml in the following folders, make sure that "http" is changed to "https" and that the URLs point to the secure port of the web server:

      • In the ND Process Server/Process Center cluster: DMGR-profile-root\config\cells\cell-name\clusters\ClusterName\process-center\config\system\100Custom.xml

      • In each Process Server/Process Center cluster member: DMGR-profile-root\config\cells\cell-name\nodes\node-name\servers\serverName\process-center\config\100Custom.xml

    6. Confirm that the following lines in the Process Server cluster 100Custom.xml file use "https" and point to the URL and port of the web server:
      <repository-server-url merge="replace">
      https://w2k8-64bitp.austin.ibm.com/ProcessCenter</repository-server-url> 
      <server-port merge="replace">443</server-port>
      

    7. Start the dmgr.

    8. Restart the cluster.
Parent topic: Modify an existing installation Related tasks:
Changing passwords after installation
Related information:

WebSphere Application Server syncNode command
Stop and restart a cluster member: