1. Using Integrations in Oracle Integration Generation 2
  2. Manage Integrations
  3. Regenerate a WSDL File for Integrations

Regenerate a WSDL File 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, username, 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. To get custom fields or updated fields to appear in the mapper, you must regenerate the endpoint in Oracle Integration.

As an example, you may have a scenario in which the WSDLs with one of your connections (for example, a Salesforce connection) change frequently and you must be able to uptake the latest WSDLs into your integrations. By regenerating the WSDL file, the custom fields of imported mappings are not deleted, and are available for editing, as needed. This eliminates the need for remapping source and target elements completely from scratch in the mapper.

Restrictions

  • Minimize your use of regeneration. Only use this feature when absolutely necessary.

  • There cannot be root level differences between the old and new WSDLs. If there are differences, WSDL regeneration 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 the Oracle Service Cloud (RightNow) Adapter WSDL is version 1.2 and try to regenerate it with Oracle RightNow Adapter WSDL version 1.3, a mapper error occurs.

  • JCA artifacts are not regenerated.

  • 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 does not get 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 regeneration 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 should not get changed.

    • The old root type should 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 regeneration 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 does not get imported or included in the final regeneration WSDL.

Note:

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

To regenerate a WSDL file for integrations:

  1. In the left navigation pane, click Home > Integrations > Integrations.
  2. Click the name of the integration in which to regenerate the WSDL. Customized integrations are designated with the words BUILT BY ORACLE and Customized to the right of the integration name.
    You can regenerate the WSDL for an individual endpoint or the WSDLs for all endpoints in an integration.
  3. To regenerate the WSDL for a single endpoint in the integration, click the appropriate source, target, request enrichment, or response enrichment icon.
    1. Select Regenerate.
      More Actions menu selected to show options for Regenerate and Delete.

      You are prompted with a message indicating that WSDL regeneration impacts the mappings in the integration.
    2. Click Regenerate.
      This regenerates the WSDL and any dependent artifacts so that any custom elements 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.
  4. To regenerate the WSDLs for all endpoints in the integration, select Regenerate Endpoints from the hamburger menu menu.
  5. Click Regenerate when prompted with a message indicating that WSDL regeneration impacts the mappings in the integration.
    This regenerates the WSDLs and any dependent artifacts with the same behavior.

See Mapping Data in Using the Oracle Mapper with Oracle Integration Generation 2.