IBM Support

Runtime server environments toggle in the Process Center console for IBM Business Process Manager (BPM)

Troubleshooting


Problem

When you attempt to deploy an application, you cannot select your runtime environment because the user interface keeps changing between each of your environments. For instance, it displays the development environment, then the production environment, and then staging environment instead of showing 3 distinct environments.

Symptom


The servers toggle between two different environments that have the same installation ID in the Process Server database. For example:

Cause

The same SQL scripts were used to set up each environment. The SQL scripts have a hard-coded installation ID for each environment. If the same installation scripts are used for each environment, then each environment is assigned the same installation ID.

This configuration causes the Process Center to assume the heartbeat from different environments that belong to a cluster environment. All the servers with the same installation ID are displayed on the same line.

Diagnosing The Problem

When you created the profile on your runtime server, the profile creation tool created an SQL file called createTable_ProcessServer.sql under the profile_name\dbscripts\ProcessServer\DBType\ directory. This file contains the unique installation ID that is generated during the profile creation process.

Check the LSW_SYSTEM table for the environment Process Server database and see if the value for InstallationGUID has the same value.


    INSERT INTO LSW_SYSTEM("KEY", "VALUE")
    VALUES ('InstallationGUID', '
    2be64e83-a455-4a15-a507-d5a9f47eaec8') ;

Resolving The Problem

To resolve the problem, you have two options:

Option 1:

Drop the Process Server database and recreate the database using the scripts that are generated for the profile under the profile_name\dbscripts\ProcessServer\DBType\ directory. For detailed instructions, refer to the following information center documents and click the appropriate link for your platform and database type:


Run the appropriate bootstrapProcessServerData command to load the system data after creating the new database for the Process Server database.

Option 2:


If recreating the database is not an option, complete the following steps to replace the existing InstallationGUID with an unique value:
  1. Locate the createTable_ProcessServer.sql file. The location of this table varies by profile name and database type. For example: C:\IBM\BPM\v7.5\profiles\profilename\dbscripts\ProcessServer\Oracle\ORCL\
    createTable_ProcessServer.sql


  2. In this file, locate the insert statement similar to the following code, which inserts in your InstallationGUID:


    INSERT INTO LSW_SYSTEM("KEY", "VALUE")
    VALUES ('InstallationGUID', '2be64e83-a455-4a15-a507-d5a9f47eaec8') ;
     

  3. Search again in the file to find the same InstallationGUID that is used for the ACL. For example:
    INSERT INTO LSW_ACL_ENTRY("ACL_ENTRY_ID",  "GROUP_ID",  "PO_TYPE",  "PO_ID",  "MASK")
    VALUES (1,  3,  5000,  '2be64e83-a455-4a15-a507-d5a9f47eaec8',  127) ;
    INSERT INTO LSW_ACL_ENTRY("ACL_ENTRY_ID",  "GROUP_ID",  "PO_TYPE",  "PO_ID",  "MASK")
    VALUES (2,  4,  5000,  '2be64e83-a455-4a15-a507-d5a9f47eaec8',  63)
     ;

  4. Use an appropriate database editor or create an SQL script to update the row that already exists in the LSW_SYSTEM and LSW_ACL_ENTRY table. Replace the InstallationGUID value that is found in the previous step.


    Note: Make sure that you use all lower-case letters when you replace the values. If you do not use lower-case letters,you see authorization errors when you run the bootstrap command.

  5. Restart the runtime server or servers.

The toggling server problem should be resolved after placing a unique InstallationGUID for each server in the LSW_SYSTEM table. For example:

The same InstallationGUID should be replaced in the LSW_ACL_ENTRY table for GROUP_ID 3 and 4. If not, you see exceptions when you upgrade the System_toolkit using the bootstrapProcessdata or upgradeProcessData command.


[{"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Application Deployment","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.0;7.5.1;7.5.0.1;7.5","Edition":"","Line of Business":{"code":"LOB15","label":"Integration"}},{"Product":{"code":"SSFTBX","label":"IBM Business Process Manager Express"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Installation \/ Configuration","Platform":[{"code":"PF016","label":"Linux"},{"code":"","label":"Linux zSeries"},{"code":"PF033","label":"Windows"}],"Version":"8.0;7.5.1;7.5.0.1;7.5","Edition":"","Line of Business":{"code":"LOB15","label":"Integration"}},{"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Installation \/ Configuration","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"","label":"Linux zSeries"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.0;7.5.1;7.5.0.1;7.5","Edition":"","Line of Business":{"code":"LOB15","label":"Integration"}}]

Product Synonym

BPM

Document Information

Modified date:
15 June 2018

UID

swg21572660