Configure Enterprise Database

1. Configuring DB2

These scripts make use of some Java classes that manage the database scripts and can determine if the database is up to date. Subsequent releases might require additional scripts to be run, using the ${MV_HOME}/web-apps/db/bin/maintain-db2-db.sh (or bat) scripts will ensure only new scripts are run in.

The following steps give an example of how a user with sufficient database privileges could create and populate the MidVision database.

NOTE: MidVision is not licenced to supply the DB2 connector library files db2jcc-3.4.65.jar and db2jcc-license-3.4.65.jar To run tomcat with a DB2 database, copy these Jar files from the DB2 installation into the directory ${MV_HOME}/web-apps/tomcat/lib. To populate the DB2 database using the scripts below then also copy these Jar files from the DB2 installation into the directory ${MV_HOME}/web-apps/db/lib.

1. Create a database user e.g. on Linux create user rddbusr with useradd -m rddbuser
2. Stop your midvision application (if it is running)
3. Switch user (su) to a db2 admin user (db2inst1 by default)
4. Ensure the db2admin user has write permission on the web-apps directory (chmod 777 if necessary).
5. For first time database install run the ${MV_HOME}/web-apps/db/bin/install-db2-db.sh
   

   (or bat) script and fill in the details (leave as default unless you have a preference). This script creates the schema user and tablespaces. Note this option will drop any existing database of the same name so treat with caution.

6. Next run the ${MV_HOME}/web-apps/db/bin/maintain-db2-db.sh (or bat) script. The first time this is run the schema is created. This script may need to be run again when you upgrade RapidDeploy, but only if the schema changes, which happens very infrequently. Subsequent runs will run in any newly added database scripts. This can be done as any user with access to the script file.
7. Run ${MV_HOME}/web-apps/db/bin/reorg-local-db2-db.sh script
8. As the owning user edit the ${MV_HOME}/bin/rapiddeploy.properties
9. Ucomment all the DB2 settings
10. Update the userid and password fields
11. Comment out the HSQL settings
12. Comment out the JNDI settings
13. Start the web application

2. Configuring Oracle

Oracle does not require an operating system user. You do however need access to the Oracle sys account userid and password.

If your Databases are managed by a centralised database team it is unlikely you will have the necessary access to create the MidVision schema. In that instance the scripts can be given to your database administrators who may choose to use them as a basis for creating the schema. The procedure below can then be followed from ignoring Step 3 by the application owner running as the MidVision service id.

1. Stop your midvision application (if it is running)
2. Set the following variable export JRE_HOME=path to your Sun 1.8 version of jre
3. For first time database install run the ${MV_HOME}/web-apps/db/bin/install-oracle-db.sh (or bat) script and fill in the details (leave as default unless you have a preference). Note this option will drop any existing database of the same name so treat with caution.
4. For subsequent database data updates run the ${MV_HOME}/web-apps/db/bin/maintain-oracle-db.sh (or bat) script. This will run in any newly added database scripts. This can be done as any user with access to the script file and enclosing directory. Only run this script again if the schema changes, which happens very infrequently.
5. As the owning user edit the ${MV_HOME}/bin/rapiddeploy.properties
6. Uncomment all the Oracle settings
7. Update userid and password as appropriate from step 3 and optionally the URL as per your RAC requirements (see below)
8. Comment out the HSQL settings
9. Start the web application

grant select on pending_trans$ to <user>; 
grant select on dba_2pc_pending to <user>;
grant select on dba_pending_transactions to <user>;
grant execute on dbms_system to <user>;  (If using Oracle 10.2.0.3 or lower JDBC driver)
grant execute on dbms_xa to <user>; (If using Oracle 10.2.0.4 or higher JDBC driver)

        jdbc:oracle:thin:@$ORACLE_HOSTNAME:$ORACLE_PORT:$ORACLE_SID

        jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = RD_DB_HOST_NAME)(PORT = RD_DB_PORT_NUMBER))(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME=RD_DB_SERVICE_NAME)))

        jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = 10.245.229.108)(PORT = 1521))(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME=rapiddeploy-db.mycompany.co.uk)))

        jdbc:oracle:thin:@(DESCRIPTION=(load_balance=on)(ADDRESS = (PROTOCOL = TCP)(HOST = rddb1a.test.midvision.com)(PORT = 1521))(ADDRESS=(PROTOCOL = TCP)(HOST = rddb1b.test.midvision.com)(PORT = 1521))(CONNECT_DATA = (SERVICE_NAME = rddbdb.test.midvision.com)))

        -Dcom.midvision.rapiddeploy.db.script.runner.ScriptRunner.factory=com.midvision.rapiddeploy.db.script.runner.SqlPlusScriptRunnerFactory

        -Dcom.midvision.rapiddeploy.db.script.runner.ScriptRunner.factory=com.midvision.rapiddeploy.db.script.runner.JdbcScriptRunnerFactory