2.8.3.5 Run ER Schema in Different Workspaces

This section describes how to run the ER schema in different workspaces.

To run the ER schema in different workspaces:

1. The ER Data schema and Compliance Studio schema should be in the same wallet.
2. Update the following details for ER schema in the resources.xml file. The file can be found in: <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/ficdb/conf.
   For example:

   <Resource
   id="ER2_CSA_ABCD"
   name="jdbc/erdataschema"
   auth="Container"
   type="javax.sql.DataSource"
   driverClassName="oracle.jdbc.OracleDriver"
   url="jdbc:oracle:thin:@ER2_CSA_ABCD"
   connectionProperties= "oracle.net.wallet_location
   =<WALLET_PATH/ABCD>;
   oracle.net.tns_admin=<WALLET_PATH/ABCD>;”
   maxTotal="5"
   maxIdle="0"
   maxWaitMillis="-1" >
   </Resource>

   Note:

   Log in as either an SYS user or DBA user and grant these permissions to the ER schema created.
3. Ensure that the pre-staging and output tables are present in the given ER Data Schema.
   1. The following are the pre-staging table names by version:
      1. FSDF 81280:
         • STG_PARTY_MASTER_PRE
         • STG_PARTY_DETAILS_PRE
         • STG_DELETED_PARTIES_PRE
         • STG_CUSTOMER_IDENTIFCTN_DOC_PRE
         • STG_ADDRESS_MASTER_PRE
         • STG_PARTY_ADDRESS_MAP_PRE
         • STG_PARTY_PHONE_MAP_PRE
         • STG_PARTY_EMAIL_MAP_PRE
         • FCC_ER_MAPPING
         • FCC_ER_MANUAL_MAPPING
   2. The following are the output table names by version:
      1. FSDF 81280:
         • STG_PARTY_MASTER
         • STG_PARTY_DETAILS
         • STG_PARTY_EMAIL_MAP
         • STG_ADDRESS_MASTER
         • STG_PARTY_ADDRESS_MAP
         • STG_PARTY_PHONE_MAP
         • STG_CUSTOMER_IDENTIFCTN_DOC
         • FCC_ER_MAPPING
         • FCC_ER_OUTPUT