Page Comparison

...

Steps

Notes

1

Create the schema in the database for the new Data Location

Code Block
CREATE USER CUSTOMER_B2C IDENTIFIED BY CUSTOMER_B2C DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP; GRANT CONNECT, RESOURCE TO CUSTOMER_B2C; GRANT UNLIMITED TABLESPACE TO CUSTOMER_B2C;

2

Copy semarchy.xml in app server

Code Block
cp /etc/tomcat8/Catalina/localhost/semarchy.xml /tmp/semarchy.xml

3

Edit semarchy.xml in app server

Code Block
vim /tmp/semarchy.xml

Note: semarchy.xml includes commented-out templates for a new data location connection. Or, you can copy an existing connection and make the changes to point to your new schema name with your new password.

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:

Code Block
cp /tmp/semarchy.xml ~/backups/semarchy-YYYY-MM-DD.xml

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

Code Block
service tomcat8 stop

7

Replace the existing semarchy.xml file with your newly modified version

Code Block
cp /tmp/semarchy.xml /etc/tomcat8/Catalina/localhost/semarchy.xml

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

...

Versions Compared

Old Version 11

New Version Current

Key