Prerequisites for Creating a Connection

Satisfy the following prerequisites specific to your environment to create a connection with the Oracle Database Cloud Service Adapter.

• Know Oracle Database Classic Cloud Service Instance Details
• Complete Connectivity with SSL Prerequisites
• Complete Username Password Token Security Policy Prerequisites
• Complete Oracle Cloud Infrastructure Database version 18c Prerequisites
• Migrate from an Oracle Database Classic Cloud Service Database Instance to an Oracle Autonomous Transaction Processing or Oracle Autonomous Data Warehouse Database Instance

Know Oracle Database Classic Cloud Service Instance Details

Note details such as Public IP, SID, SQL*Net Port, PDB Name, and Connect String from the instance details page for the Oracle Database Classic Cloud Service instance in the Oracle Cloud Infrastructure Console. This information is required when configuring an Oracle Database Cloud Service Adapter connection on the Connections page.

Complete Connectivity with SSL Prerequisites

If using connectivity with SSL with the Oracle Database Cloud Service Adapter, note the following requirements.

Note:

Connectivity agent installation and agent group creation are not required when using direct connectivity.

• The Oracle Database Classic Cloud Service instance is accessible through a public IP address.
• Oracle Database Classic Cloud Service should be SSL-enabled along with the necessary wallet configuration. See the Oracle Database documentation for configuring secure sockets layer authentication for your respective database version. For example, for Release 18, see Configuring Secure Sockets Layer Authentication of the Security Guide.
• Once SSL is configured, the following files are available under the wallet directory:
  • cwallet.sso
  • ewallet.p12
  Follow these steps to create a wallet archive file:

  1. Generate the truststore and keystore using orapki:

     orapki wallet pkcs12_to_jks -wallet wallet_directory/ewallet.p12 
     -pwd password_provided_during_wallet_creation 
     -jksKeyStoreLoc wallet_directory/keystore.jks 
     -jksKeyStorepwd password 
     -jksTrustStoreLoc wallet_directory/truststore.jks 
     -jksTrustStorepwd password

  2. Create a ZIP file containing cwallet.sso, ewallet.p12, keystore.jks, and truststore.jks, including the tnsnames.ora file found in the $ORACLE_HOME/network/admin/ directory.

Complete Username Password Token Security Policy Prerequisites

If using the Username Password Token security policy with the Oracle Database Cloud Service Adapter, note the following requirements.

• Create an agent group. See Creating an Agent Group of Using Integrations in Oracle Integration Generation 2. Note the agent group name and agent group identifier that you specify. The agent group name is required when creating an Oracle Database Cloud Service Adapter connection. The agent group identifier is required when installing the connectivity agent.

• Download and install the connectivity agent on the same host as the Oracle Database Classic Cloud Service or a compute node from which the database is accessible. Understand the implications of installing on the same host. See Connectivity Agent Fails Frequently If Competing with Oracle Database Classic Cloud Service for Resources.

  See Downloading and Running the On-Premises Agent Installer of Using Integrations in Oracle Integration Generation 2.

Complete Oracle Cloud Infrastructure Database version 18c Prerequisites

If using Oracle Cloud Infrastructure Database version 18c, you must perform the following steps before using stored procedures in Oracle Cloud Infrastructure (that is, before generating wrapper packages). Some changes to the 18c database must be bypassed to get table/record type metadata information.

1. Run the first command to enable events to capture metadata:

   alter session set events '10946 trace name context forever, level 65536';
   

2. Run the second command to recompile and populate that metadata:

   alter package package_name compile;

Migrate from an Oracle Database Classic Cloud Service Database Instance to an Oracle Autonomous Transaction Processing or Oracle Autonomous Data Warehouse Database Instance

Perform the following steps if you want to migrate from an Oracle Database Classic Cloud Service database instance to an Oracle Autonomous Transaction Processing or Oracle Autonomous Data Warehouse database instance.

1. Migrate all the required database objects, stored procedures, wrapper procedures, and tables to the destination Oracle Autonomous Transaction Processing or Oracle Autonomous Data Warehouse database instance.
2. Change the Oracle Database Cloud Service Adapter connection details to point to an Oracle Autonomous Transaction Processing or Oracle Autonomous Data Warehouse database instance.
   1. Go to the Connection page for the Oracle Database Cloud Service Adapter.
   2. Click Configure Connectivity.
   3. Specify the new host name.
   4. Specify the new service name and click OK.
   5. Click Configure Security.
   6. Select the Oracle Wallet security policy.
   7. Upload the wallet.
   8. Specify the wallet password and reconfirm it.
   9. Specify the database service username.
   10. Specify the database service password, reconfirm it, and click OK.
   11. Delete the agent from the connection.
3. Test the connection.
4. Once the test is successful, click Save to save the connection details.
5. Reactivate the integrations.