Copying an Environment
There can be several reasons for copying or cloning an environment:
-
Copy a setup environment as the initial version of a test environment.
-
Copy a setup environment as the initial version of the production environment.
-
Copy the production environment to the test environment.
This chapter describes the procedure for copying environments. In the target environment, start by installing and configuring the Oracle Database and Oracle Fusion Middleware software that runs the Oracle Health Insurance application.
Clone the Database
Use the RMAN Backup tool to duplicate the database. See the Oracle Database documentation for more information.
Empty the Task Queue
In case the Oracle Health Insurance application makes use of task processing, empty the task queue before starting the application by executing:
DECLARE
po_t dbms_aqadm.aq$_purge_options_t;
BEGIN
dbms_aqadm.purge_queue_table('OHI_TASK_QUEUE_TABLE', NULL, po_t);
END;
Note that there is no support for performing direct data manipulation on the OHI_TASK_QUEUE_TABLE.
Deploy the Application
Follow the instructions in the Installation Guide for installing the Oracle Health Insurance application on the application server. Note that setting up specifically for the properties files and the data source configuration is essential for the target system.
Maintain Credentials
Note that there needs to be a per-WebLogic domain-based maintenance of credentials that the application uses to connect to external endpoints, like HTTP Basic Authentication credentials. Oracle Health Insurance database schemas do not store them, but the WebLogic domain’s repository database does.