1. Using Integrations in Oracle Integration 3
  2. Design and Monitor Integrations in Projects
  3. Design a Project
  4. Add and Share a Connection Across a Project

Add and Share a Connection Across a Project

You can add a connection to use in an integration in a project. During creation, you can also select to make the connection available across projects. This selection allows you to share the connection resources from one project with other projects. This feature also eliminates the need to create separate connections in each project.

Share Connection Resources Across Projects

You can share adapter connection resources across projects. For example, you may have two projects that need to integrate with a common system, such as Oracle ERP Cloud. You create and configure the following connection types:
  • Publicly available connection: You create, configure, and maintain a single Oracle ERP Cloud Adapter connection that you select to share with other projects. This selection makes the connection publicly available to adapters of the same adapter type and role in other projects.
  • Local connections: You create additional connections in other projects that reference the publicly available connection. Referencing the connections means that you don't explicitly configure connection properties, security properties, or access types for these connections. You override the local connection settings by referencing the settings of the publicly available connection. This reference enables you to share resources across each project.

Oracle ERP appears at the top. Arrows connect to Oracle ERP from project 1 and project 2. Inside project 1 are integration 1 and connection 1. Connection 1 is labeled as publicly available. Inside project 2 are integration 2 and connection 2. Connection 2 is labeled as local. An arrow goes from connection 2 to connection 1.

Note:

Note the following connection sharing restrictions:
  • If you update the connection configuration settings for a publicly available connection, the activated integrations for any local connections that are referencing the publicly available connection must be reactivated to capture those updates.
  • Lookup and JavaScript library resources cannot be shared across projects.
  • You cannot track failed integration instances by the publicly-available connection.
The following example describes how to configure connection sharing:
  • You create and configure a publicly available connection.
  • You create a local connection that references the configuration settings of the publicly available connection.
  1. Open a project.
  2. In the Connections section, click Add if no connections currently exist or + if connections already exist.
  3. Create an adapter connection. For this example, a REST Adapter is selected. See Create a Connection.
  4. Select a role from the Role list (for this example, Trigger is selected) and click Share with other projects to make this connection publicly available for use across projects.


    The Create connection panel shows the Name, Identifier, Role, Keywords, Description, and Share with other projects elements.

  5. Configure the connection properties, connection security, and access control for the publicly available adapter.
  6. Test and save the connection, then exit the Connections page.

    The connection is displayed as Configured in the project.


    The Connections section shows the connection name, its role (trigger), its state (Configured), and the Actions menu.

  7. Open a different project to create the local connection.
  8. Create a connection of the same adapter type (REST Adapter) and same role (Trigger) to match the publicly available adapter.

    The Connections page is displayed. Note the Use a shared connection field at the top.

  9. Enter a letter that is part of the name of the publicly available connection (for this example, t is entered).

    A filtered list of connections is returned that shows only publicly available connections of the same adapter type (REST Adapter) and same role (Trigger) that include that letter.


    A letter is entered in the Use a shared connection field, which displays a selection that includes that letter and is of the same role type.

  10. Select the publicly available connection (for this example, testConn). If the project of the publicly available connection is configured with role-based access control (RBAC) settings, you must have at least view permissions in that project.
  11. Click Save.

    The local connection automatically references the connection configuration settings of the publicly available connection.


    The Connections page shows the Configured label at the top. Below is the Use a shared connection section. The View and Remove buttons are displayed. The Configuration progress section is shown, with a progress bar. Below is the Configure a connection section, with subsections for Security and Access type.

  12. Save the connection, then exit the Connections page.

    The connection is displayed as Configured in the project. The Override label is displayed, meaning this connection references the resources of the publicly available connection.


    The Connections section shows the connection name, its role (trigger), its state (Configured), and the Actions menu. The word Override appears under the connection name.

  13. Create an integration.

    The local connection is available for selection in the integration canvas. The Override label indicates that this connection is referencing the resources of the publicly available connection in the other project.


    The integration canvas shows the triggers list. The local connection is shown being selected.

  14. Design the remaining parts of your integration.
  15. Activate and run the integration.
  16. View the activity stream and note that the integration instance was run by referencing the resources of the publicly available connection.

Refresh Endpoints Using Connection Sharing

You can override a local connection in a draft state with a publicly-available connection in a configured state, and then regenerate the endpoints for the local connection. This section describes this capability with a brief example.
  1. Create a local connection and leave it in a draft state (for this example, the connection is named RIGHTNOW_CONN).


    The Connections section shows two connections in draft state.

  2. Go to the integration canvas and view the map action for the connection. This shows the contents of the mapper prior to endpoint refreshing. Note that there are source and target elements named regen 1 and regen 2.


    The mapper shows the Sources, Mapping canvas, and Target sections. The Validate button appears in the upper right corner. Three icons appear above the Sources section. Eight icons appear above the Target section.

  3. Return to the Connections section and open the connection (RIGHTNOW_CONN) for editing.
  4. In the Use a shared connection field, enter the beginning letter to filter the list, and select the shared connection to use (for this example, named right_NOW).


    The Connections page is shown for RIGHTNOW_CONN. The state is shown as Draft. The Role, Identifier, and Updated on values are shown. Below this is the Use a shared connection field. Available shared connections are shown.

  5. Save the connection.

    The connection state is changed to configured.


    The Connections page is shown for RIGHTNOW_CONN. The state is shown as Configured. The Role, Identifier, and Updated on values are shown. Below this is the Use a shared connection field, which includes a connection. The View button appears. Below this is the Configure a connection section, which includes the values for Properties and Security.

  6. Go to the Integrations section of the project.
  7. Hover over the row of the integration, and select Actions Actions icon, and then Refresh endpoints.

    The Refresh endpoints panel opens.

  8. Select the connection to refresh (RIGHTNOW_CONN), then click Refresh.
  9. Wait for the refresh to complete.
  10. Return to the mapper for the connection. Note that there are now source and target elements named Regen 1, Regen 2, Regen 3, and Regen 4.


    The mapper shows the Sources, Mapping canvas, and Target sections. The Validate button appears in the upper right corner. Three icons appear above the Sources section. Eight icons appear above the Target section.

  11. Validate the mappings.
  12. Save and exit the integration.

Share Connection Resources in Accelerator Projects

When you install an accelerator project, all connections are initially in a draft state. You can use connection sharing for these connections instead of configuring each connection individually.

For example, if the accelerator project is using Oracle ERP Cloud Adapter and Twilio Adapter connections, you can use connection sharing if the following conditions are met:
  • There are publicly available connections for Oracle ERP Cloud Adapter and Twilio Adapter.
  • The roles are the same.
  • You have view permissions at a minimum on the project that includes the publicly available connections.

After you configure connection sharing for these adapters, you can activate the integration in the accelerator project.