8.3.2.5 Step 4: Add Oracle Call Interface Parameters (Optional)

To the same JSON file, add Oracle Call Interface configuration parameters.

This step is optional. With this configuration, you can override the Oracle Call Interface parameters configured in the oraaccess.xml file or omit configuring the file. The oraaccess.xml file is a client-side configuration file that lets you configure selected OCI parameters during deployment.

1. Specify Oracle Call Interface parameters in the oci JSON object.

   Note:

   Ensure that you specify only the allowed Oracle Call Interface parameters, as listed in Oracle Call Interface Developer's Guide.

   The following sales.json file shows Oracle Call Interface attributes along with the connect descriptor, database credentials, and wallet location values that are configured for the sales.myexample.com service:

   { 
    "connect_descriptor": "(DESCRIPTION=
                             (ADDRESS=
                               (PROTOCOL=TCP)
                               (HOST=my sales dbserver)
                               (PORT=1521))
                             (CONNECT_DATA=
                               (SERVER=DEDICATED)
                               (SERVICE_NAME=sales.myexample.com))
                           )", 
    "user": "admin", 
    "password": { 
       "type": "ocivault", 
       "value": "ocid1.vaultsecret.my-password-secret-id" 
    }, 
    "wallet_location" : {
       "type" : "ocivault",
       "value" : "ocid2.vaultsecret.my-wallet-secret-id"
    },
    "oci": { "statement_cache_size" : 5,
             "prefetch_rows" : 10, 
             "lob_prefetch_size": 1024, 
             "session_pool" : { "min" : 4, "max" : 10, "increment" : 2 }
    }
   } 

   Similarly, the following multi.json file shows Oracle Call Interface attributes along with the connect descriptor, database credentials, and wallet location values that are specified for the sales and hr objects:

   { 
    "sales" : { 
      "connect_descriptor": "(DESCRIPTION=
                               (ADDRESS=
                                 (PROTOCOL=TCP)
                                 (HOST=my sales dbserver)
                                 (PORT=1521))
                               (CONNECT_DATA=
                                 (SERVER=DEDICATED)
                                 (SERVICE_NAME=sales.myexample.com))
                             )",   
      "user": "scott", 
      "password": { 
         "type": "ocivault", 
         "value": "ocid1.vaultsecret.oc1.my-password-secret-id" 
      }, 
      "wallet_location" : {
         "type" : "ocivault",
         "value" : "ocid2.vaultsecret.my-wallet-secret-id"
      },
      "oci":{ "statement_cache_size" : 5, 
              "prefetch_rows" : 10, 
              "lob_prefetch_size": 1024, 
              "session_pool" : { "min" : 4, "max" : 10, "increment" : 2 }
      } 
    },
    "hr" : { 
      "connect_descriptor": "(DESCRIPTION=
                               (ADDRESS=
                                 (PROTOCOL=TCP)
                                 (HOST=my dbserver.my.example.com)
                                 (PORT=1521))
                               (CONNECT_DATA=
                                 (SERVER=DEDICATED)
                                 (SERVICE_NAME=hr.my.example.com))
                             )" 
      "oci":{ 
      "statement_cache_size" : 6, 
      "prefetch_rows" : 10 
      } 
    } 
   }

2. Store your updated JSON file in the OCI Object Storage:

   In the OCI console, navigate to the Object Storage - Bucket Details page of your bucket and upload the file to that bucket under Objects.