Migrating existing data to a centralized global datastore |
Top Previous Next |
If you already have an existing JSCAPE MFT Server installation and you want to migrate that installation's server configuration data from the built-in H2 database to a centralized global datastore, follow the instructions below.
1. Create a database in the external relational database that will hold the global datastore and create a user account that has the correct permissions for the said database
2. Stop the JSCAPE MFT Server service.
3. Launch a command line/terminal and navigate into the JSCAPE MFT Server installation directory. Copy the existing H2 global datastore database to your external relational database by entering the js-database-configuration -copy command line utility. In the example below, we're copying to a MySQL database named jscapeconfig hosted on a machine with IP address 192.168.100.105. Please replace the parameters below accordingly.
js-database-configuration -copy -destination-url jdbc:mysql://192.168.100.105/jscapeconfig -destination-user databaseuser1 -destination-password secret
5. Configure JSCAPE MFT Server to use your external database. Again, in the example shown below, we're configuring a MySQL database (hence the MySQL jdbc url). Please replace the parameters below accordingly.
js-database-configuration -configure -url jdbc:mysql://192.168.100.105/jscapeconfig -user databaseuser1 -password secret
6. Start JSCAPE MFT Server.
When you go to Settings > Datastore > JDBC URL, you'll notice that it's already using the JDBC URL of whatever external database you've configured it for instead of the built-in H2 database. |