Refresh Endpoints for Integrations

After you clone an integration, customize a prebuilt integration, or import an existing integration into Oracle Integration, you update the connection information (WSDL, user name, and password) according to the requirements of your integration environment. If the connection WSDL you specify contains any custom fields or if the connection WSDL is updated with a different version, they are not displayed in the mapper. For custom fields or updated fields to appear in the mapper, you must refresh the endpoints in Oracle Integration.

As an example, the WSDLs for one of your connections (for example, a Salesforce connection) change frequently and you must uptake the latest WSDLs into your integrations. By refreshing the WSDL file, the custom fields of imported mappings are not deleted, and are available for editing, when needed. This eliminates the need to remap source and target elements completely from scratch in the mapper.

Endpoint refreshing is an asynchronous operation. This reduces the chance of timeouts occurring. The refresh can scale from a single action to an entire integration.

Restrictions

• Integrations cannot be refreshed when they are active, being activated, or being deactivated.
• Integrations are locked during the refresh. No users can modify the integration during this period.
• Integration activation is blocked during a refresh.
• During endpoint refreshing, you can view or exit the integration canvas. If you are still on the canvas when endpoint refreshing completes, the canvas refreshes and you can resume editing. If you leave the canvas, you receive an alert that the refresh has completed, and the lock is released.
• The Connections page shows a warning message if you attempt to edit during integration refreshing.
• You cannot unlock an integration until refreshing completes.
• Once refreshing completes successfully, you cannot roll back to the previous state.
• Minimize your use of refreshing. Only use this feature when absolutely necessary.

• There cannot be root level differences between the old and new WSDLs. If there are differences, WSDL refreshing fails. Therefore, you can change the connection information, but must ensure that the new WSDL does not have root element differences from the previous WSDL.

• If you create an integration in which Oracle Service Cloud (RightNow) Adapter WSDL version 1.2 is used and try to refresh it with Oracle Service Cloud (RightNow) Adapter WSDL version 1.3, a mapper error occurs.

• JCA artifacts are not refreshed.

• A new WSDL can have references to a different schema with different data structures (for example, you change the schema by adding, modifying, or deleting a new complex element to the root element), only if the root element within the schema is not modified, added, or removed. In this situation, the child element within the root element can be changed or refer to any new data structure or data type.

  The refresh logic follows the reference and imports or includes the new data structure to the new WSDL. The root element within the schema is the first level of <xs:element/> or type element (<xs:complexType/> or <xs:simpleType/>). For the first level of <xs:element/>, the following applies:

  • Their QName cannot be modified.

  • A new root element cannot be added.

  • The old root element cannot be removed.

  For the first level of a type element, the following applies:

  • Their QName must not change.

  • The old root type must not be removed.

  • A new type element can be introduced by other referencing child elements or types.

  For example, one child element or type defined in a root element can refer to a new type element. The refresh logic imports or includes them into the existing schema if it has the same target namespace as the child element/type or by creating a new schema if it has a different target namespace from the child element/type. The new root level type element must be referenced by another child element/type. If it is a standalone root type element, it is not imported or included in the final refreshed WSDL.

Note:

If you receive an error during the refresh, do not save the endpoint/mapping updates. Instead, close and discard the integration without saving, reopen the integration for editing, and try refreshing again.

1. In the navigation pane, click Design, then Integrations.
2. Refresh the endpoints in either of two ways:
   1. Hover over the name of the integration in which to refresh the endpoints.
      You can refresh the endpoints for an individual endpoint or all endpoints in an integration.
   2. To refresh the WSDL for an endpoint in the integration, click Actions , then select Refresh endpoints for the appropriate endpoint.
      
      

      

      
      

      The Refresh endpoints panel opens.

   Or:
   1. Click the name of the integration in which to refresh the endpoints.
      The integration canvas is displayed.
   2. Click the icon in the palette above the integration to refresh the endpoints.
      
      

      

      
      

      The Refresh endpoints panel opens.

3. Select the connections from the list for which to refresh artifacts. Refreshing endpoints may impact the business identifiers and maps.
4. Click Refresh.

   The refresh of the impacted connection endpoints is displayed as in progress. On the Integrations page, the state of the overall integration refresh is also displayed as in progress.

   This process refreshes the endpoint and any dependent artifacts to enable any custom elements to appear during mapping. The imported mappings from any prebuilt integration are not deleted. The maps are validated and any warnings (identified by yellow icons) or errors (identified by red icons) for the impacted maps are displayed. If warnings and errors both exist for a single mapper, only a single error icon is displayed. Icons indicating that this mapper is customized (identified by the blue icons) are displayed at the bottom of the mapper.

5. If you need to cancel in-progress endpoint refreshing, click Stop and rollback.

See Map Data in Using the Oracle Mapper with Oracle Integration 3 .