1. Using the Salesforce Adapter with Oracle Integration 3
  2. Create a Salesforce Adapter Connection
  3. Create a Connection

Create a Connection

Before you can build an integration, you must create the connections to the applications with which you want to share data.

To create a connection in Oracle Integration:

  1. In the navigation pane, click Design, then Connections.

  2. Click Create.

    Note:

    You can also create a connection in the integration canvas. See Define Inbound Triggers and Outbound Invokes.

  3. In the Create connection panel, 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.

  4. Enter the information that describes this connection.
    Element Description
    Name

    Enter a meaningful name to help others find your connection when they begin to create their own integrations.

    Identifier

    Automatically displays the name in capital letters that you entered in the Name field. If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY).

    Role

    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, assume 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.

    Keywords

    Enter optional keywords (tags). You can search on the connection keywords on the Connections page.
    Description

    Enter an optional description of the connection.
    Share with other projects

    Note: This field only appears if you are creating a connection in a project.

    Select to make this connection publicly available in other projects. Connection sharing eliminates the need to create and maintain separate connections in different projects.

    When you configure an adapter connection in a different project, the Use a shared connection field is displayed at the top of the Connections page. If the connection you are configuring matches the same type and role as the publicly available connection, you can select that connection to reference (inherit) its resources.

    See Add and Share a Connection Across a Project.

  5. Click Create.

    Your connection is created. You're now ready to configure the connection properties, security policies, and (for some connections) access type.

Configure Connection Properties

Enter connection information so your application can process requests.

  1. Go to the Properties section.
    The fields that are displayed are based on your instance version.
  2. Specify details based on your instance version.

    Note:

    If you create or edit your Salesforce Adapter connection on Oracle Integration release 21.2.1.0.0 (211110.1100.42360) or later, you must specify API version 47 or later in the API Version field or upload an enterprise WSDL of API version 47 or later.
    To Edit Existing or Create New Connections on... Description
    Release 20.2.2.0.0 (200524.0200.35760) or later of Oracle Integration
    1. From the Select Salesforce.com Instance Type list, select the instance type:
      • Production
      • Sandbox
      • Government: Select if you want to connect to Salesforce Government Cloud.

      Note: For more information about instance type, see Identify Instance Type of Your Salesforce Organization.

    2. In the Custom domain field, enter your custom domain name. For example, if your custom domain name is sfcustomdomain.my.salesforce.com, then enter sfcustomdomain. See Obtain the Custom Domain Name.
      Note:
      • The Government instance type option and Custom domain field are displayed for connections created in release 20.3.3 or later of Oracle Integration.
      • The Custom domain field is optional. However, if you are using Salesforce Government Cloud or a custom domain to log in to your Salesforce account, the custom domain name is required.
      • The Salesforce Adapter recommends that you not use your Salesforce instance value as your custom domain name (for example, with the URL https://ap1.salesforce.com, the value before salesforce.com is your Salesforce instance value).
      • Don’t use common words like test, login, sfcustomdomain.my, and sfcustomdomain.my.salesforce.com as the custom domain name.
    3. In the API Version field, enter the API version to use. See Find Your Current Salesforce API Version.

    Note: If you edit an existing connection created on release 20.2.2.0.0 (200524.0200.35760) or later of Oracle Integration, the instance type and API version fields are displayed.

    A release prior to Oracle Integration 20.2.2.0.0 (200524.0200.35760)
    1. Select the Upload File checkbox, then click Upload to select the enterprise WSDL to use in this integration. The enterprise WSDL is mandatory and must be specified regardless of whether you are also using a custom WSDL or an outbound messaging WSDL. See Generate the Salesforce Enterprise WSDL.

    Note: If you edit an existing connection created prior to release 20.2.2.0.0 (200524.0200.35760) of Oracle Integration, the field to upload an enterprise WSDL is displayed.

Configure Connection Security

Configure security for your Salesforce Adapter connection by selecting the security policy.

  1. Go to the Security section.
  2. From the Security Policy list, select the security policy.
    • Salesforce Username Password Policy
    • Authorization Code Credentials (Salesforce OAuth 3-legged)
    • Resource Owner Password Credentials

    Note:

    • If you need to use the Bulk 2.0 data operations, configure the OAuth-based security policies (Authorization Code Credentials or Resource Owner Password Credentials) for your Salesforce Adapter connection. Bulk 2.0 data operations are not supported when you configure the Username Password security policy for your Salesforce Adapter connection.
    • Configure the OAuth-based security policies (Authorization Code Credentials or Resource Owner Password Credentials) for your Salesforce Adapter connection if you need to use the Apex REST operation. The Apex REST operation is not supported when you configure the Username Password security policy for your Salesforce Adapter connection.
  3. If you select Salesforce Username Password Policy.
    1. In the Username field, enter the username.
    2. In the Password field, enter the password (combination of the password and security token).
      The security token must be appended to the end of the password. Salesforce.com APIs generate the security token at the time of password reset. For example, if the security token generated by Salesforce.com is SSSSSSSSSSS and the password is password, you must enter passwordSSSSSSSSSSS to log in. Obtain the security token by changing the password or resetting the security token through the Salesforce.com user interface. You receive the security token through the email address registered with Salesforce.com. This token is valid until you reset the security token for the respective account or change the password.
    3. In the Confirm Password field, re-enter the password a second time for confirmation.
  4. If you select Authorization Code Credentials.
    1. In the Client Id field, enter the consumer key/client ID that you obtained when creating a connected application. See Prerequisites to Use the Salesforce OAuth Three-Legged (Authorization Code Credentials) or Resource Owner Password Credentials Security Policy.
    2. In the Client Secret field, enter the client secret key that you obtained when creating a connection application. See Prerequisites to Use the Salesforce OAuth Three-Legged (Authorization Code Credentials) or Resource Owner Password Credentials Security Policy.
    3. In the Confirm Client Secret field, re-enter the client secret a second time for confirmation.
    4. In the Scope field, enter id api refresh_token. These are the minimum scopes required to configure a connection. Ensure that your connected application has these scopes configured. See Prerequisites to Use the Salesforce OAuth Three-Legged (Authorization Code Credentials) or Resource Owner Password Credentials Security Policy.

      Note:

      The Scope field is not marked with an asterisk (*). This incorrectly implies that this field is not mandatory. This field is mandatory.
    5. Click Provide Consent. You are redirected to the Salesforce login page.
    6. Log in to the Salesforce account with your credentials. Once you successfully log in, the following message appears: 
      Access Allowed! Please switch back to connection page to proceed with 
testing and saving connection configuration.
  5. If you select Resource Owner Password Credentials.
    1. In the Client Id field, enter the consumer key/client ID that you obtained when creating a connected application. See Prerequisites to Use the Salesforce OAuth Three-Legged (Authorization Code Credentials) or Resource Owner Password Credentials Security Policy.
    2. In the Client Secret field, enter the client secret key that you obtained when creating a connection application. See Prerequisites to Use the Salesforce OAuth Three-Legged (Authorization Code Credentials) or Resource Owner Password Credentials Security Policy.
    3. In the Confirm Client Secret field, re-enter the client secret a second time for confirmation.
    4. In the Username field, enter the username.
    5. In the Password field, enter the password (combination of the password and security token).
      The security token must be appended to the end of the password. Salesforce.com APIs generate the security token at the time of password reset. For example, if the security token generated by Salesforce.com is SSSSSSSSSSS and the password is password, you must enter passwordSSSSSSSSSSS to log in. Obtain the security token by changing the password or resetting the security token through the Salesforce.com user interface. You receive the security token through the email address registered with Salesforce.com. This token is valid until you reset the security token for the respective account or change the password.
    6. In the Confirm Password field, re-enter the password a second time for confirmation.

    Note:

    When switching the connection from one Salesforce environment to another or switching the security policy, you must reactivate the integration to point to the correct environment.

Configure the Endpoint Access Type

Configure access to your endpoint. Depending on the capabilities of the adapter you are configuring, options may appear to configure access to the public internet, to a private endpoint, or to an on-premises service hosted behind a fire wall.

Select the Endpoint Access Type

Select the option for accessing your endpoint.

Option This Option Appears If Your Adapter Supports ...
Public gateway Connections to endpoints using the public internet.
Private endpoint Connections to endpoints using a private virtual cloud network (VCN).

Note: To connect to private endpoints, you must complete prerequisite tasks in the Oracle Cloud Infrastructure Console. Failure to do so results in errors when testing the connection. See Connect to Private Resources in Provisioning and Administering Oracle Integration 3 and Troubleshoot Private Endpoints in Using Integrations in Oracle Integration 3.

Ensure Private Endpoint Configuration is Successful

  • To connect to private endpoints, you must complete prerequisite tasks in the Oracle Cloud Infrastructure Console. Failure to do so results in errors when testing the connection. See Connect to Private Resources in Provisioning and Administering Oracle Integration 3.
  • When configuring an adapter on the Connections page to connect to endpoints using a private network, specify the fully-qualified domain name (FQDN) and not the IP address. If you enter an IP address, validation fails when you click Test.
  • IPSec tunneling and FastConnect are not supported for use with private endpoints.

Test the Connection

Test your connection to ensure that it's configured successfully.

  1. In the page title bar, click Test. What happens next depends on whether your adapter connection uses a Web Services Description Language (WSDL) file. Only some adapter connections use WSDLs.
    If Your Connection... Then...

    Doesn't use a WSDL

    The test starts automatically and validates the inputs you provided for the connection.

    Uses a WSDL

    A dialog prompts you to select the type of connection testing to perform:

    • Validate and Test: Performs a full validation of the WSDL, including processing of the imported schemas and WSDLs. Complete validation can take several minutes depending on the number of imported schemas and WSDLs. No requests are sent to the operations exposed in the WSDL.

    • Test: Connects to the WSDL URL and performs a syntax check on the WSDL. No requests are sent to the operations exposed in the WSDL.

  2. Wait for a message about the results of the connection test.
    • If the test was successful, then the connection is configured properly.
    • If the test failed, then edit the configuration details you entered. Check for typos and verify URLs and credentials. Continue to test until the connection is successful.
  3. When complete, click Save.