This section explains the deployment procedure of Oracle Insurance Data Foundation (OIDF) on Oracle Autonomous Data Warehouse (ADW).
Topics:
· Oracle Autonomous Data Warehouse
· Deployment Architecture for ADW Certification
· Download Client Credentials (Wallet)
· Using a JDBC URL Connection String with JDBC Thin Driver
· Installation Notes Specific to ADW
Oracle Autonomous Database is Oracle's new, fully managed database tuned and optimized for both data warehouse and transaction processing workloads with the market-leading performance of the Oracle Database. It delivers a completely new, comprehensive cloud experience for data warehousing and transaction processing workloads that is easy, fast, and elastic and requires no database administration.
OIDF being an analytical data warehouse platform, it is qualified for ADW.
When you create an Autonomous Data Warehouse database, you can deploy it to one of two kinds of Exadata infrastructure:
· Shared: A simple and elastic choice. Oracle autonomously operates all aspects of the database life cycle from database placement to backup and updates.
· Dedicated: A private cloud in public cloud choice. A completely dedicated compute, storage, network and database service for only a single tenant. Dedicated infrastructure provides for the highest levels of security isolation and governance. The customer has customizable operational policies to guide Autonomous Operations for workload placement, workload optimization, update scheduling, availability level, over provisioning and peak usage.
The following illustration depicts the deployment architecture used for the ADW certification.
The deployment architecture consists of two Availability Domains used for OFSAA and WebLogic Server in the same Oracle Cloud Infrastructure (OCI) Compartment. Oracle Identity Cloud Service (IDCS) can be used to log in. The Load Balancer (LB) redirects the request to respective compute.
Both Availability Domain 1 and Availability Domain 2 computes use the ID-RSA key to transact between the nodes. The WebLogic Servers and DF Servers are configured to connect the ADW OFSAA schemas with the Wallet files.
Currently, Autonomous Database (ADB) provides 99.95% availability during any calendar month. For customers that need high availability, Autonomous Data Guard provides failover protection.
Oracle client credentials (wallet files) are downloaded from Autonomous Data Warehouse by a service administrator. If you are not an Autonomous Data Warehouse administrator, your administrator must provide you with the client credentials.
To download the client instance (Wallet), you can use the following consoles:
· Oracle Cloud Infrastructure (OCI) console
· Autonomous Data Warehouse Service console
See the Download Client Credentials (Wallets) for more information.
The connection string is found in the file tnsnames.ora which is a part of the client credentials download. The tnsnames.ora file contains the predefined services identifiable as high, medium, and low. Each service has its own TNS alias and connection string. See Predefined Database Service Names for Autonomous Data Warehouse for more information.
The following is a sample entry with dbname_low as the TNS alias and a connection string in the tnsnames.ora file:
dbname_low= (description= (address=(protocol=tcps)(port=1522)(host=adw.example.oraclecloud.com))(connect_data=(service_name=adw_jdbctest_high.oraclecloud.com))(security=(ssl_server_cert_dn="CN=adw.oraclecloud.com,OU=OracleUS,O=Oracle Corporation,L=Redwood City,ST=California,C=US")))
This section provides additional steps applicable to the installation on ADW in OFSAA for OIDF.
For OIDF qualification on ADW, the following software are used:
· Database is ADW
· Web application server is Oracle WebLogic Server 12.2.x
See the Oracle Financial Services Analytical Applications (OFSAA) Technology Matrix Release 8.1.0.0.0 for the hardware and software required for the installation of OIDF Application Pack Release 8.1.0.0.0.
The modifications applicable to configuring the schema creator utility for the OIDF installation on ADW are provided in this section.
NOTE |
The schema creator utility configuration is applicable for the OIDF installation on ADW also. See the Configure the Schema Creator Utility section for more information. The modifications applied to the OIDF installation on ADW are mentioned in this section. |
The ADW specific modifications are as follows:
· When configuring the OFS_OIDF_SCHEMA_IN.xml file for ADW, follow these modifications:
§ Set the <IS_TCPS> tag to TRUE:
<IS_TCPS>TRUE</IS_TCPS>
NOTE |
The connections to ADW is through the ADW Wallet. Therefore, the <IS_TCPS> tag must be always set to TRUE for OIDF installation on ADW. |
§ The tag <OPTION NAME="TDE" VALUE="TRUE"/> can be commented out because ADW is secure by default.
§ Tha tag <TABLESPACES> can be commented out because ADW does not consider the TABLESPACES inputs.
§ This is a sample of the <JDBC_URL> tag for connecting to the ADW: <JDBC_URL>jdbc:oracle:thin::@##dbname##_low</JDBC_URL>
See the sections Using a JDBC URL Connection String with JDBC Thin Driver, JDBC Thin Connections and Wallets and Predefined Database Service Names for Autonomous Data Warehouse for more information about the predefined database service names for ADW.
The additional steps applicable to the OFSAAI installation on ADW are as follows:
NOTE |
OFSAAI installation is applicable for the OFSAAI on ADW also. See the Oracle Financial Services Advanced Analytical Applications Infrastructure Installation Guide Release 8.1.0.0.0 for the detailed installation procedure. The additional steps applicable to the OFSAAI installation on ADW are mentioned in this section. |
1. Extract the Wallet_<databasename>.zip folder into the directory path $HOME/Wallet_<databasename>, where you are going to install OIDF on the OCI OEL 7.X virtual machine instance. This directory is also called as the WALLET_HOME. For information about downloading the Wallet for ADW, see Download Client Credentials (Wallets).
2. WALLET_HOME=/home/Wallet_<databasename>.zip
Example:
/u02/ofsa/Wallet_OFSADB
3. For the above-mentioned directory, set the TNS_ADMIN in the .profile file. Edit the sqlnet.ora file for the Wallet path and other directives.
Example:
The contents of the sqlnet.ora files are as following:
SQLNET.WALLET_OVERRIDE = TRUE
WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY="/u02/ofsa/Wallet_OFSADB")))
SSL_SERVER_DN_MATCH=yes
4. For the above-mentioned directory, set the parameter IS_ADW=TRUE in the .profile file, and point the ORACLE_HOME parameter to the Oracle Database 19c Client installation path.
Example:
Sample of the .profile file contents for OIDF with ADW on OCI is follows:
export FIC_HOME=/u02/ofsa/OFSAHOME
export TNS_ADMIN=/u02/ofsa/Wallet_OFSADB
export ORACLE_HOME=/u01/app/oracle/product/19.3.0/client_1
export JAVA_HOME=/usr/java/jdk1.8.0_121
export JAVA_BIN=/usr/java/jdk1.8.0_121/bin
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
export PATH=$ORACLE_HOME/bin:$JAVA_HOME:$JAVA_BIN:$PATH
export IS_ADW=TRUE
5. Follow the OFSAAI 8.1.0.0.0 installation procedure that supports TCPS. See the Oracle Financial Services Advanced Analytical Applications Infrastructure Installation Guide Release 8.1.0.0.0.
a. Before excecuting the Schema Creator utility, ensure to Configure the Schema Creator Utility.
b. Execute the Schema Creator utility:
Example:
$./osc.sh -s TCPS /u02/ofsa/Wallet_OFSADB
This prompts you to enter USER having SYSDBA privileges.
Enter the ADMIN and password details provided to you during the ADW provisioning.
See the Oracle Financial Services Advanced Analytical Applications Infrastructure Installation Guide Release 8.1.0.0.0 for more information.
The additional steps applicable to the OIDF installation on ADW are mentioned in this section.
NOTE |
OIDF installation is applicable for the OIDF on ADW also. See the Install the OIDF Application Pack section for the detailed installation procedure. The additional steps applicable to the OIDF installation on ADW are mentioned in this section. The ModelUpgrade utility was triggered using the TCPS mode during installation on ADW because the connections to ADW is through the ADW Wallet. |
The files configured for the OIDF installation are same for the OIDF installation on ADW also.
When configuring the OFSAAI_InstallConfig.xml file for ADW, follow these modifications:
· The <InteractionGroup name="OLAP Detail"> tag is not supported in ADW.
· Ensure to provide ADW database details similar to the following sample of the <InteractionGroup name="Database Details"> tag:
<InteractionGroup name="Database Details"><InteractionVariable name="ORACLE_SID/SERVICE_NAME">##dbname##_low</InteractionVariable><InteractionVariable name="ABS_DRIVER_PATH">/u01/app/oracle/product/19.3.0/client_1/jdbc/lib</InteractionVariable></InteractionGroup>
Follow the OFSAAI 8.1.0.0.0 installation procedure and OIDF 8.1.0.0.0 installation procedure.
Execute the ./setup.sh command.
See the OFS Advanced Analytical Applications Infrastructure Installation and Configuration Guide Release 8.1.0.0.0 for installation and post-installation procedure required for OFSAAI with TCPS.
See the Install the OIDF Application Pack section for installation and the Post-installation section for the post-installation procedure required for OIDF with TCPS.
For the OIDF deployment on ADW, the Object Store mechanism has been used as the repository for the inbound data.
The following steps were performed to load data to the OIDF schema on the ADW environment and to execute the OIDF batches:
· Importing Data into OIDF on ADW Using the OCI Object Storage
To import data into OIDF using the Object Storage, follow these steps:
1. To create an Object Storage in the OCI and load data into ADW, see Import Data Using Oracle Data Pump on Autonomous Data Warehouse.
2. To choose appropriate mode to import data into schema, see Examples of Using Data Pump Import for the data pump examples with all the possible ways to import data.
To execute the OIDF batches, follow these steps:
1. Log in to ADW OFSAA schemas and check the load status.
2. Execute the OIDF batches. The tasks executed and data moved successfully to target as are follows:
§ ##INFODOM##_POP_DATES_DIM
§ ##INFODOM##_MASTER
§ ##INFODOM##_DATA_FOUNDATION_SCD
§ ##INFODOM##_DIM_ACCOUNT_SCD
§ ##INFODOM##_POP_MAPPER_DATA
§ OIDF Source Run
§ OIDF Exe Run
See the Oracle Insurance Data Foundation Application Pack User Guide Release 8.1.0.0.0 for more information about the OIDF batch execution.
Currently, OIDF Release 8.1.0.0.0 is the qualified for deployment on the ADW.
For more information, log a service request on My Oracle Support (MOS).