Monday 3 December 2012

Problems with non-unique InstallationGUID in IBM Business Process Manager v8

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.

Cause

You used the same SQL scripts to set up each environment. The SQL scripts have a hard-coded installation ID for each environment. If you use the same installation scripts for each environment, then they all have the same unique installation ID.

Solution

Check the createTable_ProcessServer.sql script and ensure that the statement: -

INSERT INTO LSW_SYSTEM("KEY", "VALUE") 
VALUES ('InstallationGUID', 'dba1912e-d0b0-46d4-b8cb-505e10296f99') ;

( actual value will vary from site to site )

*ALWAYS* uses a unique InstallationGUID value.

This IBM Technote puts it far far better than I can: -

No comments:

Visual Studio Code - Wow 🙀

Why did I not know that I can merely hit [cmd] [p]  to bring up a search box allowing me to search my project e.g. a repo cloned from GitHub...