MWNiebuhr

Configure a new PAM Orchestrator instance to use existing PAM database

Discussion created by MWNiebuhr Employee on Aug 21, 2013
Latest reply on Apr 9, 2015 by Jennifer_Jessup
TEC596124 How to configure a new PAM Orchestrator instance to use existing PAM database tables


Title: How to configure a new PAM Orchestrator instance to use existing PAM database tables

Description:

Each PAM engine has a unique ID that it creates and writes to the database.

If you attempt to install a new Orchestrator against existing tables, it will display an error with the message "The Runtime Database is being used by another orchestrator."

Solution:

You can get the Orchestrator ID from the "properties" table in the database - You'll need this value to update the various config files so copy it out somewhere and mark it "Original ID". It will look something like d98853b2-ecbd-4d37-b71c-ecf7b46c17c4

Then install PAM against a dummy database and get it all patched up and running against this dummy database. They should use the same Database Host, Username and Password, only specifying a different database name such as "PAMDummy".

Stop the PAM service or application.

Open the NodeConfiguration file from the new install and make note of the nodeID. You will need this shortly, copy it out an mark it "Dummy ID".

Then go through the following files replacing the current "Dummy ID" with the "Original ID" from the properties table in the database.

Note: It is not called nodeid outside the nodeconfiguration file, you will have to search for the actual "Dummy ID" string to find it.

NodeConfiguration.properties

OasisConfig.properties

Domain.xml

c2osvcw.conf

Finally, in Oasisconfig.properties, review the various database 'dbname=' values and change all of them from "PAMDummy" to the name of the original database.

Start PAM.

Outcomes