TIBCO ActiveMatrix (AMX) BPM stores various configuration data generated by the BPM system in its configuration folder. For a single node environment, the default is CONFIG_HOME/bpm. For a distributed topology, the user is expected to provide a shared location. 

 

TIBCO ActiveMatrix (AMX) BPM stores various configuration data generated by the BPM system in its configuration folder. For a single node environment, the default is CONFIG_HOME/bpm. For a distributed topology, the user is expected to provide a shared location. This article will describe the steps to change AMX BPM's configuration folder.

ALL

Here are the steps to change the location of BPM configuration folder:

1. The following folders needs to be moved from <CONFIG_HOME>/bpm/amx.bpm.app (or <SHARED_DIR>/bpm_config/amx.bpm.app) to <NEW_SHARED_DIR>/bpm_config/amx.bpm.app - 

appdev
configuration
database
deployment
hawk
keystores

Note: amx.bpm.app is commonly the name of the system BPM application. The system application name can vary in your environment. 

2. Using TIBCO AMX Administrator, change the below JVM configuration on each node (Infrastructure > Nodes > [BPMNodeName] > Configuration > JVM Configuration - General Args) -

-Dn2.config.location="<NEW_SHARED_DIR>/bpm_config/amx.bpm.app/configuration"

3. When the change is saved, the node status changes to Out Of Sync. Select the node and click on "Install or Sync".

4.  Modify the following “Substitution Variables” (SVAR) for each of the BPM nodes. Give the new location of “keystore” folder (<NEW_SHARED_DIR>/bpm_config/amx.bpm.app/keystores/).
tibco.bpm.client.keystore
tibco.bpm.ldap.keystore
tibco.bpm.wss.keystore
tibco.bpm.wss.truststore

5. Re-install the resource instances (RI) which use these SVARs. When any SVAR is changed, the resource instance is set to Out Of Sync. Using AMX Administrator, check the status of all the RIs under Infrastructure > Hosts > (select the host name which manage a BPM Node) > Resource Instances. Repeat for each applicable host. 

Note: If any RI has a path to the keystore hard coded instead of using the SVAR, it will not be able to detect the change and remain In Sync. 

6.  Stop the BPM node(s).

7.  Start the BPM node(s).