For customers who ask us how to add a new Data Location, this guide describes the "back-end" changes that must happen to semarchy.xml on the app server. The "front-end" changes should be straight forward on how to add a new Data Location through the workbench.
Prerequisite: This document assumes that you have already created the schema in Oracle. If you have not yet, please refer to this guidance on How To Create Data Locations Schemas. This document also assumes you have crated a Data Location in the Workbench. If you have not yet, please refer to the product documentation on How To Create A Data Location.
Assumes that you are sudo user to run the following commands. If you are not and have sudo permissions, add "sudo" in front of command.
Steps | Notes | |||
|---|---|---|---|---|
| 1 | Create the schema in the database for the new Data Location |
|
|
|
|
|
| ||||
| 2 | Copy semarchy.xml in app server |
| ||
| 3 | Edit semarchy.xml in app server |
| ||
| 4 | Validate you have everything backed-up | Don't forget to back up your changes before you start editing semarchy.xml. For example, you could create a "backup" directory in the home folder and then back up like this:
Or you can add semarchy.xml to your organization's version control system (e.g. Github) to track the changes. | ||
| 5 | Alert ALL Users you are bringing Semarchy down for a few minutes | You have to stop Tomcat and restart it for the new changes to semarchy.xml to take effect. Note: advanced users are welcome to re-deploy just the Semarchy app rather than restarting Tomcat completely. Use the Tomcat Manager UI (or even command line management of tomcat). In the interest of simplicity we have not documented these alternatives. | ||
| 6 | Stop Tomcat |
| ||
| 7 | Replace the existing semarchy.xml file with your newly modified version |
| ||
| 8 | Start Tomcat | service tomcat8 start | ||
| 9 | Rinse and repeat for your other environments | Warning: check you choose the correct Data Location type in the Workbench for QA and PROD |