Versions Compared

Old Version 8

changes.mady.by.user Robin Peel

Saved on

compared with

New Version 9

changes.mady.by.user Anna Rider (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.



StepsNotes
1Create the schema in the database for the new Data Location
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;
2Copy semarchy.xml in app server
cp /etc/tomcat8/Catalina/localhost/semarchy.xml /tmp/semarchy.xml
3Edit semarchy.xml in app server
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.

4Validate 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:


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. 

5Alert 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.

6Stop Tomcat
service tomcat8 stop
7Replace the existing semarchy.xml file with your newly modified version
cp /tmp/semarchy.xml /etc/tomcat8/Catalina/localhost/semarchy.xml 
8Start Tomcatservice tomcat8 start
9Rinse and repeat for your other environmentsWarning: check you choose the correct Data Location type in the Workbench for QA and PROD

...