Compound Registration Deployment Guide

Introduction

This document describes the steps that are necessary in order to deploy Compound Registration in an empty environment. It is assumed that an Oracle or MySQL server exists, and a user account is created with the appropriate privileges to be able to create, alter tables, indeces, sequences, triggers, etc. It is also assumed that the application server is properly set up with a compatible version of operating system, Java environment and Apache Tomcat. For further details on the version compatibility please consult the System Requirements document.

Deploying the Application

  1. Configure Tomcat connector as needed in server.xml within the Tomcat conf folder.

  2. Copy all the provided external libraries into the Tomcat lib folder.

  3. Deploy the application war file (RegistryCxn.war) into the Tomcat webapps folder, and have the provided war file extracted in the webapps folder (e.g. start Tomcat, then stop it again)

  4. Create a copy of the properties file containing e.g. the connectivity information ($TOMCAT_HOME/webapps/RegistryCxn/WEB-INF/classes/registry.properties) in an arbitrary “home” folder. Create an environment variable called REGISTRYCXN_HOME that is pointing to this “home” folder.

  5. Adjust the database URLs, account, etc. in the first section of the copied properties file according to the local needs. (The configuration of the downstream databases can be skipped.)

  6. Copy the Compound Registration license file into the $HOME/.chemaxon folder of the user running Tomcat. Copy Marvin4JS license file in $TOMCAT_HOME/webapps/ROOT folder.

  7. Update user defined checker configuration files in the $HOME/.chemaxon folder with the provided ones.

For further configuration steps please consult the Compound Registration configuration guide, some of those system level changes need the restart of the application, others have immediate effect.

Steps of Database Deployment

Prior to successfully starting the application itself an initial database schema has to be created. Besides the application war file ( RegistryCxn.war ) a zip package (e.g. RegistryCxn-7.0.zip ) is provided that contains a script responsible for creating the DB.

  1. Extract the zip file into a selected folder.

  2. Make sure that the location of the registry.properties file containing the DB connectivity information is referred by the enviroment variable REGISTRYCXN_HOME.

  3. Start ./RegistryCxn bash script or RegistryCxn.bat in the RegistryCxn-7.0/bin folder of the extracted content (depending on the OS type). The following are available:

-disableGlobalProjectAccess together with sqldeploy, disables global
project access rights
-dropSchema drops all database objects from
registration schema
-dropSchemaDS drops all database objects from downstream
schema
-help print this help summary
-migrateSchema create or upgrade database objects in
registration schema
-migrateSchemaDS create or upgrade database objects in
downstream schema
-schemaInfo prints informations about the registration
schema
-schemaInfoDS prints informations about the downstream
schema

In order to create an initial DB schema or clean an existing one completely, please use the following command line:

./RegistryCxn -dropSchema -migrateSchema

Starting the Application

After a successful deployment the application can be started/stopped/restarted by controlling the application server / Tomcat container. Initially an administrator account is created in the local database with the admin/changeit credentials.


For further details please consult the product documentation.