When the database and are not installed on the same machine (the database may be installed on any machine within the network), you need to transfer the database definition files.
Disable all workflow groups from the Execution Manager in Desktop, or by entering an mzsh command, for example:
$ mzsh mzadmin/<password> wfgroupdisable \*
Note!
If you use the wfgroupdisable command, make sure that you enable all system tasks again when you are done.
Stop all batch workflows and let them finish execution.
Shut down all connected Desktops.
If you want to see which Desktops that are connected, you can use the following command:
$ mzsh mzadmin/<password> pico -view
Set up the connection to the new database.
For Oracle:
$ cd ./scripts/system-configure
$ ./oracle.sh
For PostgreSQL:
$ cd ./scripts/system-configure
$ ./postgresql.sh
For SAP HANA:
$ cd ./scripts/system-configure
$ ./saphana.sh
When the saphana.sh script is launched without any parameters, it will return a list of expected parameters, an example command output is the following:
<host> <port> <username> <password> <dbname> <SAP HANA JDBC driver dir>
The user needs to specify the mandatory parameters such as the SQL port where the tenant database is listening. The <dbname> field indicates the tenant name, while the <SAP HANA JDBC driver dir> is the name of the directory where the ngbc.jar file is stored.