Moving IBM BPM Document Store into a separate DB schema

The task – move IBM BPM Document Store into a separate DB schema. This problem has two solutions:

1.    You can create properties file for the command BPMConfig and use it. But, if the environment has already been created, we cannot use BPMConfig because it does not permit to change all the parameters of Deployment Environment. We need to delete our Deployment Environment before.

2.     If you have already installed a new Deployment Environment, you can use this solution.

The disclaimer:
The solution is not recommended by IBM, it is hack and any actions you make on own risk!
The solution does not move the content of IBM BPM Document Store, it only creates a new one in the separate schema.

I prepared this solution for Oracle DB, but, I think, it can be used with some changes for other RDBMS.

Initial conditions (the example).

We have installed IBM BPM Deployment Environment named BPMAPS, the schema for Process Server named BPMDBAPS and Oracle SID is BPM8. It is necessary to move IBM BPM Document Store into another schema named ECMDBAPS.

1.      Create a new DB schema ECMDBAPS for IBM BPM Document Store.

2.    Create a new authentication alias BPM_DB_ALIAS_BPMAPS_5 using ISC >  Global security > JAAS - J2C authentication data using User ID ECMDBAPS and its password.

3.      Change in Resources > Data sources for jdbc/ECMDB and jdbc/ECMDBXA Security settings to the created alias BPM_DB_ALIAS_BPMAPS_5.

4.      Stop the environment, including Deployment Manager and Node Agents.

5.    Open in a text editor the file: <WAS_INSTALL_ROOT>/DmgrProfile/config/cells/<CellName>/cell-bpm.xml

6.      Find the strings and change them as described:

Before:

<components xmi:id="BPMComponent_1480923523559" name="ProcessPortal"/>
<components xmi:id="BPMComponent_1480923523560" name="EmbeddedECM">
 <databaseInfo xmi:id="BPMDatabaseInfo_1480923523559" name="BPM8" schema="BPMDBAPS"/>
</components>        

After:

<components xmi:id="BPMComponent_1480923523559" name="ProcessPortal">
       <databaseInfo xmi:id="BPMDatabaseInfo_1480923523559" name="BPM8" schema="BPMDBAPS"/>
</components>
<components xmi:id="BPMComponent_1480923523560" name="EmbeddedECM">
       <databaseInfo xmi:id="BPMDatabaseInfo_1480923523560" name="BPM8" schema="ECMDBAPS"/> 
</components>

The numbers using in this example will be different for different environments, but bold values must be equal to each other in a particular environment. In our case, for the string schema="ECMDBAPS" (After, number 5) you must use the value from the string name="EmbeddedECM" (Before, number 2). 

7.      Run Deployment Manager and Node Agents.

8.      Sync the configuration with nodes.

9.      Start Deployment Environment.

10.  After starting DE, check that in the schema ECMDBAPS the tables of IBM BPM Document Store were created.

11. Open Deployment Environments > BPMAPS > Health Center and check that all the components have the status Healthy and for the component EmbeddedECM the schema ECMDBAPS is set up.

12.   If you have any doubts, make the export of the settings of our IBM BPM environment using the command BPMConfig and check that you have the separate database EmbeddedECMDb:

######################################
# Database properties: EmbeddedECMDb #
######################################
bpm.de.db.4.name=EmbeddedECMDb
bpm.de.db.4.dbCapabilities=EmbeddedECM
bpm.de.db.4.type=Oracle
bpm.de.db.4.databaseName=BPM8
bpm.de.db.4.schema=ECMDBAPS