Split (1)

train · 94.6k rows

text stringlengths 65 20k
The following topics describe how to define connections.Topics Prerequisites for Creating a Connection Create a Connection Prerequisites for Creating a Connection Satisfy the following prerequisites specific to your environment to create a connection with the Oracle Autonomous Data Warehouse Adapter.Download the Client Credentials Wallet Know Database Instance Details Complete Bulk Data Import Operation Prerequisites Download the Client Credentials Wallet Download the client credentials wallet from the Oracle Autonomous Data Warehouse instance.See Download Client Credentials (Wallets) of Using Oracle Autonomous Database on Shared Exadata Infrastructure .Know Database Instance Details 1.Ensure that the target database is accessible.2.Ensure that you have write permissions to the database.3.Ensure that you have the required permissions to run stored procedures and SQL statements.4.Know the database service name.5.Know the database service username and password for connecting to the database.Complete Bulk Data Import Operation Prerequisites If you want to use the bulk data import operation, you must configure the Oracle Autonomous Data Warehouse Adapter to use the JDBC With OCI Signature security policy on the Connections page.Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.
Topics Prerequisites for Creating a Connection Create a Connection Prerequisites for Creating a Connection Satisfy the following prerequisites specific to your environment to create a connection with the Oracle Autonomous Data Warehouse Adapter.Download the Client Credentials Wallet Know Database Instance Details Complete Bulk Data Import Operation Prerequisites Download the Client Credentials Wallet Download the client credentials wallet from the Oracle Autonomous Data Warehouse instance.See Download Client Credentials (Wallets) of Using Oracle Autonomous Database on Shared Exadata Infrastructure .Know Database Instance Details 1.Ensure that the target database is accessible.2.Ensure that you have write permissions to the database.3.Ensure that you have the required permissions to run stored procedures and SQL statements.4.Know the database service name.5.Know the database service username and password for connecting to the database.Complete Bulk Data Import Operation Prerequisites If you want to use the bulk data import operation, you must configure the Oracle Autonomous Data Warehouse Adapter to use the JDBC With OCI Signature security policy on the Connections page.Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .
Download the Client Credentials Wallet Know Database Instance Details Complete Bulk Data Import Operation Prerequisites Download the Client Credentials Wallet Download the client credentials wallet from the Oracle Autonomous Data Warehouse instance.See Download Client Credentials (Wallets) of Using Oracle Autonomous Database on Shared Exadata Infrastructure .Know Database Instance Details 1.Ensure that the target database is accessible.2.Ensure that you have write permissions to the database.3.Ensure that you have the required permissions to run stored procedures and SQL statements.4.Know the database service name.5.Know the database service username and password for connecting to the database.Complete Bulk Data Import Operation Prerequisites If you want to use the bulk data import operation, you must configure the Oracle Autonomous Data Warehouse Adapter to use the JDBC With OCI Signature security policy on the Connections page.Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.
See Download Client Credentials (Wallets) of Using Oracle Autonomous Database on Shared Exadata Infrastructure .Know Database Instance Details 1.Ensure that the target database is accessible.2.Ensure that you have write permissions to the database.3.Ensure that you have the required permissions to run stored procedures and SQL statements.4.Know the database service name.5.Know the database service username and password for connecting to the database.Complete Bulk Data Import Operation Prerequisites If you want to use the bulk data import operation, you must configure the Oracle Autonomous Data Warehouse Adapter to use the JDBC With OCI Signature security policy on the Connections page.Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.
Know Database Instance Details 1.Ensure that the target database is accessible.2.Ensure that you have write permissions to the database.3.Ensure that you have the required permissions to run stored procedures and SQL statements.4.Know the database service name.5.Know the database service username and password for connecting to the database.Complete Bulk Data Import Operation Prerequisites If you want to use the bulk data import operation, you must configure the Oracle Autonomous Data Warehouse Adapter to use the JDBC With OCI Signature security policy on the Connections page.Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.
2.Ensure that you have write permissions to the database.3.Ensure that you have the required permissions to run stored procedures and SQL statements.4.Know the database service name.5.Know the database service username and password for connecting to the database.Complete Bulk Data Import Operation Prerequisites If you want to use the bulk data import operation, you must configure the Oracle Autonomous Data Warehouse Adapter to use the JDBC With OCI Signature security policy on the Connections page.Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.
3.Ensure that you have the required permissions to run stored procedures and SQL statements.4.Know the database service name.5.Know the database service username and password for connecting to the database.Complete Bulk Data Import Operation Prerequisites If you want to use the bulk data import operation, you must configure the Oracle Autonomous Data Warehouse Adapter to use the JDBC With OCI Signature security policy on the Connections page.Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .
4.Know the database service name.5.Know the database service username and password for connecting to the database.Complete Bulk Data Import Operation Prerequisites If you want to use the bulk data import operation, you must configure the Oracle Autonomous Data Warehouse Adapter to use the JDBC With OCI Signature security policy on the Connections page.Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.
5.Know the database service username and password for connecting to the database.Complete Bulk Data Import Operation Prerequisites If you want to use the bulk data import operation, you must configure the Oracle Autonomous Data Warehouse Adapter to use the JDBC With OCI Signature security policy on the Connections page.Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.
Complete Bulk Data Import Operation Prerequisites If you want to use the bulk data import operation, you must configure the Oracle Autonomous Data Warehouse Adapter to use the JDBC With OCI Signature security policy on the Connections page.Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.
Before you can successfully configure this security policy on the Connections page, you must complete the following prerequisites.Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .
Create an object storage bucket in Oracle Cloud Infrastructure and obtain the OCID value of the compartment in which you create the storage bucket.You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.
You need this value when configuring the security policy on the Connections page.You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.
You specify the OCID of the object storage user on the Connections page when configuring the JDBC With OCI Signature security policy.This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.
This user should have the manage 2-1bucket and manage object privileges.Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.
Set the following policies to manage privileges on the bucket and object in the object storage: Allow group group_name to manage buckets in compartment compartment_name Allow group group_name to manage objects in compartment compartment_name See How Policies Work and Policy Reference .Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.
Obtain the tenancy OCID and user OCID details in the Oracle Cloud Infrastructure Console.You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .
You need these values when configuring the security policy on the Connections page.When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.
When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, which is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .
1.Sign in to the Oracle Cloud Infrastructure Console.2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.
2.In the upper left corner, select , then select Home > Governance & Administration > Tenancy Details .3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.
3.In the Tenancy Information section, click Show to display the OCID tenancy value.4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.
4.Copy the value.You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.
You need this value when configuring the security policy on the Connections page.5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.
5.In the upper right corner, click the Profile icon and select User Settings .Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .
Note: You can also select in the upper left corner, then select Identity > Users to access the user profile.6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)
6.Click Show to display the OCID user value.7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)
7.Copy the value.Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.
Create an API signing key.You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .
You then specify the signing key in Oracle Cloud Infrastructure.1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.
1.Sign in to the Oracle Cloud Infrastructure Console to upload the public key.Chapter 2 Prerequisites for Creating a Connection 2-22.In the upper left corner, select , then select Identity > Users .3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.
3.On the Users page, click the link of the user name to use.4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.
4.Scroll down to the API Keys section, and click Add Public Key .Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).
Note: Only a private key without a pass phrase/password is supported.5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).
5.In the Add Public Key dialog, enter the contents of the public key you created, and click Add.6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.
6.Copy the finger print value generated by Oracle Cloud Infrastructure.You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).
You need this value when configuring the JDBC With OCI Signature security policy on the Connections page.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.
Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.
To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.
2.Click Create .Chapter 2 Create a Connection 2-3Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .
A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.
3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.
To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .
4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.
a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.
The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.
If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.
b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.
You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.
c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.
Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.
When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.
If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .
For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.
Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.
d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.
5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.
Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.
You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.
Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.
1.Go to the Connection Properties section.2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.
2.If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent): a.In the Host field, specify the host.b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.
b.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.
It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.
The database service name is not the same as the database service username that you specify in the Security section.Chapter 2 Create a Connection 2-4Note: The service name must be the same as the one in the tnsnames.ora file in the wallet.However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.
However, if you receive an error when testing the connection, it may be because the name is too long.See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.
See Service Name Specified on the Connections Page is Too Long .3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.
3.If configuring the connection to use the connectivity agent: a.In the Host field, specify the host.b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.
b.In the Port field, specify the SQL*Net port.c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.
c.In the SID field, specify the database SID.d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.
d.In the Service Name field, specify the database service name.It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.
It is recommended that you use the low profile as the database service name.The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.
The database service name is not the same as the database service username that you specify in the Security section.Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).
Note: You must specify either a SID or service name value.Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.
Do not specify values for both fields.Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.
Configure Connection Security Configure security for your Oracle Autonomous Data Warehouse Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.
1.Go to the Security section.2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.
2.Select the security policy.3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.
3.If you select JDBC Basic Authentication : Note: Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance.If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.
If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).
a.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.
The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.
The database service username is not the same as the database service name that you specify in the Connection Properties section.b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.
b.Re-enter the password a second time.4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.
4.If you select JDBC Over SSL :Chapter 2 Create a Connection 2-5Note: The Oracle Autonomous Data Warehouse Adapter can connect through the connectivity agent when using the wallet.It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.
It can be used as a trigger connection only if the connectivity agent is used in the connection.However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.
However, all operations that you select on the Basic Info page such as Run a SQL Statement , Invoke a Stored Procedure , and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).
a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.
b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).
c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .
The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .g.In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.
The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .g.In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.alphanumeric.value ).
d.Enter the database service password a second time to confirm.5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .g.In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.alphanumeric.value ).h.In the Object Storage User OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.user.oc1.
5.If you select JDBC With OCI Signature : Note: This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .g.In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.alphanumeric.value ).h.In the Object Storage User OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.user.oc1.alphanumeric.value ).
a.In the Wallet field, select the check box, then click Upload to upload the wallet file.b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .g.In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.alphanumeric.value ).h.In the Object Storage User OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.user.oc1.alphanumeric.value ).i.In the Private Key field, click Upload to select the key you created.
b.Enter the wallet password, then re-enter it a second time to confirm.c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .g.In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.alphanumeric.value ).h.In the Object Storage User OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.user.oc1.alphanumeric.value ).i.In the Private Key field, click Upload to select the key you created.Ensure that the key is in RSA (PKCS1) format.Chapter 2 Create a Connection 2-6Note: Only a private key without a pass phrase/password is supported.
c.Enter the database service username and password to connect to the Oracle Autonomous Data Warehouse - Shared (ADW-S) database.The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .g.In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.alphanumeric.value ).h.In the Object Storage User OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.user.oc1.alphanumeric.value ).i.In the Private Key field, click Upload to select the key you created.Ensure that the key is in RSA (PKCS1) format.Chapter 2 Create a Connection 2-6Note: Only a private key without a pass phrase/password is supported.j.In the Finger Print field, enter the finger print that was generated when you created the key in the Oracle Cloud Infrastructure Console.
The database service username is the schema username for the user to log in to the database.The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .g.In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.alphanumeric.value ).h.In the Object Storage User OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.user.oc1.alphanumeric.value ).i.In the Private Key field, click Upload to select the key you created.Ensure that the key is in RSA (PKCS1) format.Chapter 2 Create a Connection 2-6Note: Only a private key without a pass phrase/password is supported.j.In the Finger Print field, enter the finger print that was generated when you created the key in the Oracle Cloud Infrastructure Console.Configure an Agent Group Configure an agent group for accessing the service hosted on your premises behind the fire wall.
The database service username is not the same as the database service name that you specify in the Connection Properties section.d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .g.In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.alphanumeric.value ).h.In the Object Storage User OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.user.oc1.alphanumeric.value ).i.In the Private Key field, click Upload to select the key you created.Ensure that the key is in RSA (PKCS1) format.Chapter 2 Create a Connection 2-6Note: Only a private key without a pass phrase/password is supported.j.In the Finger Print field, enter the finger print that was generated when you created the key in the Oracle Cloud Infrastructure Console.Configure an Agent Group Configure an agent group for accessing the service hosted on your premises behind the fire wall.1.Click Configure Agents .
d.Enter the database password a second time to confirm.e.In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1 ).f.In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value ).See Prerequisites for Creating a Connection .g.In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.alphanumeric.value ).h.In the Object Storage User OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.user.oc1.alphanumeric.value ).i.In the Private Key field, click Upload to select the key you created.Ensure that the key is in RSA (PKCS1) format.Chapter 2 Create a Connection 2-6Note: Only a private key without a pass phrase/password is supported.j.In the Finger Print field, enter the finger print that was generated when you created the key in the Oracle Cloud Infrastructure Console.Configure an Agent Group Configure an agent group for accessing the service hosted on your premises behind the fire wall.1.Click Configure Agents .The Select an Agent Group page appears.

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.