4 Setup Disaster Recovery (DR) in Compliance Studio
This section describes additional configuration required to setup Disaster Recovery
(DR) in the Compliance Studio.
Note:
The Incremental file system changes from the Active Compliance Studio server should be synced/reflected in all the fail over Compliance Studio servers as well.Prerequisites:
- Create a wallet. To create a wallet, see the Setup the Password Stores for Database User Accounts section in the OFS Compliance Studio Installation Guide.
- Add Secondary Database credentials in the wallet.
- ER/FSDF Schema, Atomic Schema, Studio Schema, and Graph Schema names should be the same as the Primary Database.
To setup DR in the Compliance Studio, follow these steps:
- Navigate to
<COMPLIANCE_STUDIO_INSTALLATION_PATH>/bin
directory. - Open
config.sh
file and update the parameters as mentioned in the following table.Table 4-1 Parameter Values in Config.sh File
Parameter Placeholder Value STUDIO_DB_HOSTNAME ##SECONDARY_STUDIO_DB_HOSTNAME ## STUDIO_DB_PORT ##SECONDARY _STUDIO_DB_PORT## STUDIO_DB_SERVICE_NAME ##SECONDARY _STUDIO_DB_SERVICE_NAME ## STUDIO_DB_SID ##SECONDARY _STUDIO_DB_SERVICE_NAME ## STUDIO_DB_USERNAME For example, CS81250_DR_2477 ATOMIC_DB_HOSTNAME ##SECONDARY _ATOMIC_DB_HOSTNAME ## ATOMIC_DB_PORT ##SECONDARY _STUDIO_DB_PORT## ATOMIC_DB_SERVICE_NAME ##SECONDARY _ATOMIC_DB_SERVICE_NAME ## ATOMIC_DB_SID ##SECONDARY _ATOMIC_DB_SERVICE_NAME ## ATOMIC_DB_USERNAME For example, STD_ATOM8125 GRAPH_DB_SERVER_NAME ##SECONDARY _GRAPH_DB_SERVER_NAME ## GRAPH_DB_PORT ## SECONDARY_GRAPH_DB_PORT ## GRAPH_DB_SERVICE_NAME ## SECONDARY _GRAPH_DB_SERVICE_NAME ## GRAPH_KEYSTORE_PASSWORD For example, password123 GRAPH_SCHEMA_DB_SCHEMA_NAME For example, GS81250_DR_2477 GRAPH_SCHEMA_WALLET_ALIAS For example, GS81250_DR_2477_alias GRAPH_SCHEMA_WALLET_LOCATION ##POINTING_TO_DR_DB## GRAPH_SCHEMA_TNS_ADMIN_PATH ##POINTING_TO_DR_DB## WALLET_LOCATION ##POINTING_TO_DR_DB## TNS_ADMIN_PATH ##POINTING_TO_DR_DB## Note:
For the parameter description, see the Configure the config.sh File section in the OFS Compliance Studio Installation Guide. - Stop the Compliance Studio by executing the following command.
./compliance-studio.sh --stop
- Reinstall the Compliance Studio by executing the following
command.
./compliance-studio.sh --reinstall
- Start the Compliance Studio by executing the following command.
./compliance-studio.sh --start
- Navigate to the
<COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/ficdb/conf
directory. - Open the resources.xml file and update the following details
for ER/FSDF
Schema.
Example:
<Resource id="###ER_SCHEMA#" name="jdbc/erdataschema" auth="Container" type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver" url="jdbc:oracle:thin:@ "###ER_SCHEMA#"" connectionProperties= "oracle.net.wallet_location =<WALLET_PATH/ABCD>; oracle.net.tns_admin=<WALLET_PATH/ABCD>;” maxTotal="5" maxIdle="0" maxWaitMillis="-1" > </Resource>