Moving a Metastorm BPM Database to Another Server

Metastorm

The information in this article applies to:

Product: Metastorm BPM
Version: 6.x 7.x

Issue

• If the Process Engine is configured to run against a database, and the database is moved to another server, what changes need to be made?

Resolution

1. Stop the Engine.

2. Change the Metastorm DSN to point to the new location. To do this, go to Start --> Settings --> Control Panel --> Administrative Tools --> Data Sources (ODBC). Test the connection.

3. In the Windows registry, make sure the following entry reflects the new ODBC connection (this is the one specified in the DSN):
   HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database\\CONNECTION

4. In the Windows registry, edit the following value to reflect the change:
   For Oracle:
   HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database Connectors\\Oracle DBC\\Connection where 'Data Source' is the Oracle service name (TNS Service Name).

   For SQL Server:
   HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database Connectors\\SQL Server DBC\\Connection where 'Data Source' is the database server name and 'Initial Catalog' is the database name.

5. If the Engine had been installed to use a SQL Server database on the same server as the Engine, MSSQLServer is probably listed as a dependency for the Engine service. If the Engine will no longer be on the same server as the database, the dependency should be removed. This can be done by editing the following Windows registry key:
   HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\Metastorm Process Engine (or e-Work Engine)
   Remove the value 'MSSQLServer' from 'DependOnService'.

6. Start the Engine.