1. Using Integrations in Oracle Integration 3
  2. Design and Monitor Integrations in Projects
  3. Manage a Project
  4. Manage Accelerator Projects

Manage Accelerator Projects

You can install accelerator projects from the Integration Store. You can extend (customize) integrations in the accelerator project and later upgrade an accelerator project to a newer version automatically without losing any extensions you made to the previous version.

Topics:

Extend an Integration in an Accelerator Project

You can extend (customize) an integration in an accelerator project by adding and configuring an extension group. An extension group enables you to extend your integration by adding invoke connections; stitch, for-each, switch, map, and integration actions; and global variables to the integrations in your accelerator project.

Learn About Accelerators Available in the Integration Store

The Integration Store provides accelerator projects that you can install and extend in a project. Newer, updated versions of accelerator projects can also become available in the Integration Store for you to re-install, as necessary.

See Find Recipes and Accelerators and Install Recipes and Accelerators in Getting Started with Oracle Integration 3.

Extend an Integration Before or After an Invoke Connection

You can extend an integration to add the following before or after an invoke connection:
  • Stitch action
  • For-each action
  • Switch action
  • Map action
  • Integration action (and associated map) for invoking a child integration
  • Invoke connection (and associated map)
  1. In the navigation pane, click Projects.
  2. Find the accelerator project to extend. The Accelerator and Oracle labels identify these types of projects. You can also use the Filter Filter icon to display a specific project type (all, user-developed, accelerator, extended accelerator, or recipe). For example:


    The projects page shows a project name with the labels Accelerator and Oracle. The type column says Accelerator. The date of the accelerator is also shown.

  3. Click the project name or click Edit icon.
  4. In the Integrations section, find the specific integration to extend.
  5. Click Actions Actions icon, and select Extend. The Extend option is only available in accelerator projects. This option behaves similar to the Edit option in non-accelerator integrations.

    The integration is displayed in the canvas.


    The integration canvas shows eight icons at the top. Below is an integration with a trigger, scope, map, and invoke.

  6. Perform one of the following actions before or after an invoke action.
    1. Add Add icon at the location where you want to add the extension, then select Extension Group.

    or

    1. Click Actions Actions icon inside the invoke action.
    2. Based on where you want to place the extension, select Extend before or Extend after. Both options are available if you have not yet added an extension to either side of the invoke.


      The Invoke action is selected to show options for View, Extend before, and Extend after.

      Note:

      If Extend before and Extend after are not available for selection and you have not added an extension to either side of the invoke, your administrator has restricted the use of extensions on the invoke connection. You cannot extend restricted invokes.

    The extension group is added to the integration.


    The integration canvas shows eight icons at the top. Below is an integration with a scope, map, extension group, and invoke.

  7. If you want to update the name, click Edit Edit icon in Edit extension group.
  8. Click Integration actions Integration actions icon and drag an invoke or action into the integration or click Add Add icon inside the extension group to add an invoke or action to the integration. For example, if you click Add Add icon, the following menu is displayed.


    The search field appears at the top. Below is the Actions list, which shows an option for Data stitch, Map, For each, Switch, and Integration.

    See the following sections for details:

Add a Stitch Action to an Extended Integration

  1. If you select Actions, then Data stitch:

    You can incrementally build a message payload from one or more existing payloads with a stitch action. For example, a data stitch enables you to customize the sales order created in an inbound application. Assume you have a use case in which whenever a sales order is created in an inbound application, your integration must retrieve and push information in a custom object to an outbound application. In the inbound application, the custom object consists of the following attributes.


    The Order Manager form is selected and includes columns for Oracle Manager Name, Account, Item Description, Item Name, Order Status, Quantity Purchased, Registry ID, and Requested Ship Date.

    The Configure stitch panel opens.

    1. Configure the stitch. This action enables you to customize the integration with mappings to or from attributes of custom objects. For this example, a stitch variable is created to process the order status attribute in the custom object.


      The Configure stitch panel is designed to process the Order Status.

      See Build Complex Assignment Statements with a Stitch Action.

    2. When integration design is complete, click Save.

      Assume you later need to further customize the custom objects in the inbound application that triggers your integration. For example, an additional field to handle the Item Number is added to the custom object.

      This use case is not about installing a newer version of the accelerator project available from the Integration Store. Rather, this is an informal user update to the custom objects. You can handle this use case by refreshing the endpoints to pick up the new object and editing the data stitch action to process the new object. You must use a new identifier and/or version. You can also set the name, keywords, and description.


      The Order Manager form is selected and includes columns for Oracle Manager Name, Account, Item Description, Item Name, Order Status, Quantity Purchased, Registry ID, Requested Ship Date, Unit List Price, and Item Number.

  2. Click Actions Actions icon, then select Refresh Endpoints. This action fetches the latest attributes added to the custom object.
  3. Open the stitch action in the extension group and add the latest custom attribute mapping to the extension group. For this example, a second stitch variable is created to process the item number attribute in the custom object.


    The Configure stitch panel is designed to process the Order Status and the Item Number.

Add an Ad-Hoc Map Action to an Extended Integration

  1. If you select Actions, then Map:

    The Add Map panel opens to show the endpoints available to which to map. Endpoints both inside and outside the extension group are shown.


    The Add Map dialog shows Cancel and Create buttons. Below is a list of the endpoints that you can select to map data to.

    If there are no endpoints available to which to map, the following message is displayed:
    No outputs available to map to
  2. Select the endpoint, and click Create.

    The mapper opens.

  3. Map appropriate source elements to target elements.

    A map action is visible in the Extension Group.


    The integration, map, and invoke actions are shown.

Add a For-Each Action to an Extended Integration

  1. If you select Actions, then For each:

    A for-each action is added to the Extension Group.


    The Extension Group includes a For each action inside it.

  2. Configure the for-each action. For this example, an Account element is defined as the repeating action.


    The Input sources section appears on the left side. Below it is the Sources section of elements. The Account element is selected. On the right side is the Configure for each section. The Repeating element field as a value of Account and the Current element name field as a value of 10_Account. To icons appear to the right of the Repeating element field.

  3. Perform further configuration, as necessary. For this example, a stitch action is added. For each iteration of the Account element, a value is updated to the current time.


    The Input sources and Functions (which is selected) tabs are shown. Below is the Functions list, which is expanded to show Advanced, Boolean, Conversion, and Date categories. Date is expanded to display the available functions. On the right is the Configure stitch section. Below this is the configured stitch action, the Variable field, the Operation list, and the Value field.

    The extension group design looks as follows:


    The Extension Group is shown with a For-each action. Inside the For-each action is a Stitch action.

Add a Switch Action to an Extended Integration

  1. If you select Actions, then Switch:

    A switch action is added to the Extension Group.

    You can add routing expressions in an integration with a switch action.


    The Extension Group shows a switch action with two branches: Route 1 and Otherwise.

    You can add a stitch action inside the switch action.

    1. Click Install icon, then select Stitch.


      The Extension Group shows a switch action with two branches: Route 1 and Otherwise. To the right, a stitch action has been added.

    2. Configure the stitch action. For example:


      The Configure stitch panel shows an edit icon at the top. Below that is the defined expression. Below that are the Variable, Operation, and Value fields. Each field has Clear and Developer Mode icons.

    3. Inside Route 1, click Actions Actions icon, then select Edit.


      The Actions … link of the Route_1 branch is selected to show an option for Edit.

      The Configure route panel opens.

    4. Configure the switch action. For example:


      The Configure route panel shows an edit icon at the top. Below that is the defined expression. Below that are the Value, Operation, and Value fields. Each field has Clear and Developer Mode icons.

      The extended portion of the integration looks as follows.


      The Extension Group shows a switch action with two branches: Route 1 and Otherwise. The Route 1 branch includes a stitch action.

Add an Integration Action to an Extended Integration

  1. If you select Actions, then Integration:

    The Integration Adapter Wizard is displayed.

  2. Click through the pages of the wizard to select the child integration to invoke.

    An integration action and associated map action are added to the Extension Group.


    The Extension Group includes a map and an integration action.

Add an Invoke Connection and Associated Map to an Extended Integration

  1. If you select Invokes, then select an invoke adapter connection:


    The Search field appears at the top. Below are the Invoke and Actions tabs. Invoke is selected to show the available connections.

    The Adapter Endpoint Configuration Wizard is displayed for the selected invoke connection.

  2. Click through the pages of the wizard and configure the invoke connection.

  3. When complete, the configured invoke connection and an associated map action are added to the Extension Group.


    The Extension Group includes a map and an invoke.

  4. Double-click the map action and map appropriate source elements to target elements.

Add a Global Variable to an Extended Integration

  1. In the Integrations section, find the specific integration to extend.
  2. Click Actions Actions icon, and select Extend.

    The integration is displayed in the canvas.

  3. In the right pane, click Global Variables Global variables icon.
    There are two types of global variables:
    • Extended global variables: Variables that you can create to extend the accelerator for your business requirements.
    • Default global variables: Variables that are defined by the producer of the extended accelerator. You cannot edit these variables.

    The Global variables (which is selected) and Integration properties tabs are shown. The Extended global variables section shows a + sign. The Default global variables section shows a value of target_gv.

  4. Click Add New Indicator icon to add your own extended global variable. For this example, extended_global_variable is added.


    The Global variables section shows the Extended global variables.

  5. Add an Extension Group to the integration.
  6. Add an action in which to use the extended global variable. For this example, a stitch action is added.


    The Extension Group includes a Stitch action.

  7. Configure the stitch action to use the extended global variable.


    The Input sources and Functions (which is selected) tabs are shown. Below is the Sources list. On the right is the Configure stitch section. Below this is the configured stitch action, the Variable field, the Operation list, and the Value field. The defined stitch value is extended_global_variable = tracking_var_1.

    Note:

    If there is a naming conflict with global variables (for example, two global variables have the same name), the entire merge is canceled. This cancellation occurs because a global variable can be used in any extension group. For example, if you create an extended global variable named conflict_gv, and a default global variable of the same name already exists, the merge is canceled, and an error is displayed.


    The error shows that the merge was aborted due to naming conflicts.

Add an Extension Group Before a Stage File Action Configured with a Write File Operation

You can add an extension group before a stage file action that is configured to write to a file. This is the only stage file action operation to which you can add an extension. This operation includes a preceding map action. For example, you may want to extend the contents of the map action with a data stitch action.
  1. Perform one of the following actions before the stage file action.
    1. Add Add icon at the location where you want to add the extension, then select Extension Group.

    or

    1. Click Actions Actions icon inside the stage file action and select Extend before.
  2. Add the appropriate action (for example, a data stitch action).


    The + sign in the extension is clicked to show a list with actions and invokes that can be added.

Add Connections to an Extended Integration

  1. In the navigation pane, click Projects.
  2. Find the accelerator project to extend.
  3. In the Connections section, click Add Install icon.
  4. Select an adapter and click Create.
  5. Enter a name. Note that the prefix BAEXT_ is automatically added to the name in the Identifier field to indicate that this is an extended connection.


    The Create connection panel shows fields for Name, Identifier, Role, Keywords, Description, and Share with other projects. The Identifier field has a prefix of BAEXT_ in front of the connection name.

  6. Click Create, then define your connection properties and security.

    Once complete, the extended connection appears in the Connections section, and can be used in integrations.

Add Lookups and JavaScript Libraries to an Extended Integration

To add a lookup to an extended integration.
  1. In the navigation pane, click Projects.
  2. Find the accelerator project to extend.
  3. In the Lookups section, click Add Install icon, then click Create.

    Note that the prefix BAEXT_ appears by default in the Name field, An extended lookup name must be prefixed with this value. If you delete the BAEXT_ prefix and attempt to create the lookup, you receive a warning.


    The Create lookup panel shows fields for Name, Keywords, and Description.

  4. Add a name after the prefix BAEXT_.
  5. Enter or select an existing keyword, and an optional description.
  6. Click Create.
  7. Design your lookup.

    Once complete, the extended lookup appears in the Lookups section, and can be used in integrations.

To add a JavaScript library to an extended integration.
  1. In the navigation pane, click Projects.
  2. Find the accelerator project to extend.
  3. In the Libraries section, click Add Install icon.
  4. Drag a JavaScript library file into the Import panel.

    The Name, Identifier, and Version fields are prepopulated with details from the file you imported. Note that the prefix BAEXT_ is automatically added to the function name in the Identifier field to indicate that this is an extended JavaScript library.


    The Import panel shows the library file name at the top. Below this are fields for Name, Identifier, Version, and Description.

  5. Click Import.
  6. Complete design of your JavaScript library.

    Once complete, the extended JavaScript library appears in the Libraries section, and can be used in integrations.

Merge Extension Group Changes into Updated Accelerator Projects

Oracle can periodically update and upload newer versions of accelerator projects to the Integration Store for your consumption. You can upgrade an accelerator project to this newer version automatically without making manual changes to the existing installation. During upgrade, you are prompted to automatically merge any customizations you performed in the extension group of the previous version into the newer version of the accelerator project. See Upgrade an Accelerator Project and Merge Extensions.

on an invoke connection also includes options for Extend before or Extend after. This enables you to install the supported accelerator actions before or after the invoke connection.

Upgrade an Accelerator Project and Merge Extensions

You can install and then extend (customize) accelerator projects in your instance. Oracle can periodically update and upload newer versions of these accelerator projects to the Integration Store for your consumption. You can upgrade an accelerator project to this newer version automatically without losing any extensions you made to the existing installation.

Understand the Rules for Merging Extensions

Before upgrading an extended accelerator project, it is important to understand the rules for merging extensions.

Rule Example
When you have multiple extended (customized) versions of an accelerator project installed, and select to install a newer version, the installer checks for extensions in the previously installed highest version. If that version includes extensions, they are automatically merged into the newer version. You currently have the following accelerator project versions installed:
  • Versions 2.0.0 (which includes extensions)
  • Versions 4.0.0 (which includes extensions)
If you install version 6.0.0, the extensions made in version 4.0.0 (previously installed highest version) are automatically merged into version 6.0.0. The extensions in version 2.0.0 are ignored.
When you have multiple versions of an accelerator project installed, and select to install a newer version, the installer checks for extensions in the previously installed highest version. If that version does not include extensions, nothing is merged into the newer version. You currently have the following accelerator project versions installed:
  • Version 2.0.0 (which includes extensions)
  • Version 4.0.0 (which does not include extensions)
If you install version 6.0.0, the installer checks for extensions in the previously installed highest version. In this case, no extensions are applied because version 4.0.0 included no extensions. The extensions in version 2.0.0 are ignored.
When you have a single version of an accelerator project installed, and select to install a newer version, the installer checks for extensions in the previously installed highest version. If that version includes extensions, they are automatically merged into the newest version. You currently have the following accelerator project version installed:
  • Version 1.0.0 (which includes extensions)

If you install a higher version of the accelerator project (for example, version 2.0.0, 3.0.0, 4.0.0, or higher), the extensions are applied to the newly installed version.
When you have multiple extended versions of an accelerator project installed, and select to install an older version, the installer does not check for extensions because you are installing a lower version. You currently have the following accelerator project versions installed:
  • Versions 2.0.0 (which includes extensions)
  • Versions 6.0.0 (which includes extensions)
If you install version 4.0.0, the extensions made in version 6.0.0 are not merged into version 4.0.0 because you are installing a lower version. The extensions in version 2.0.0 are ignored.

Automatically Merge Extensions

This section provides an overview of how to upgrade to a newer extended accelerator project and automatically merge your extensions (customizations). This process automatically merges the extensions in all integrations in the project.

Assume you have an accelerator project that includes two integrations on version 1.0.0.


The search field appears at the top. The Integrations section shows the integration, a calendar icon, version, the current state (Configured) and an Actions menu. An Add button appears above.

Both integrations include an extension group with a stitch action that you added.

Oracle Automerge1 Integration Oracle Automerge2 Integration

The integration shows a trigger, map, and extension group that includes a stitch action.
The integration shows a trigger, map, and extension group that includes a stitch action.

Newer versions of this accelerator project are then uploaded to the Integration Store. You want to install a newer version and not lose the extensions you made to your current version (1.0.0).

  1. On the Oracle Integration Home page, scroll to the Accelerators & Recipes section.
  2. Find the accelerator project to upgrade. The Get latest label indicates that a new version of the accelerator project is available for installation.
  3. Click Get latest.


    The accelerator recipe shows a Get latest button being selected. Configure and Delete icons appear to the right.

    You can also configure and delete installations from this location.

    The Install accelerator panel opens and shows the latest accelerator versions to which you can upgrade.

  4. Select the version to which to upgrade (for this example, v1.0.1 is selected).
  5. If you want to merge the extensions you added (for this example, the stitch actions you added to both version 1.0.0 integrations), then click Merge latest extensions.
  6. Click Install.


    The Install accelerator panel shows the accelerator versions available for installation. The v1.0.1 version is selected. In the Merge options section, the Merge latest extensions check box is selected.

  7. Click the link in the Confirmation message that is displayed. This takes you to your project to view installation progress.
  8. Click Refresh Refresh iconperiodically.
  9. Note that the latest installed versions (1.0.1) are successfully merged above the initial integration versions (1.0.0).


    The Integrations section shows the integrations, calendar icons, versions, the current state (Configured) and Actions menus.

  10. Click the latest integrations (1.0.1) to see that your customizations have been merged.


    The trigger, map, and extension group with a stitch action are shown.

  11. Click Merge report Merge report icon to view a report about the merge.


    The merge report shows the merge date, source version, any errors, the merge user, the target version, and any warnings. The activity stream for the merge is shown below.

  12. Exit the integration.
  13. Click Save when prompted.

Manually Merge Extensions

If you do not select the Merge latest extensions check box described in Step 5, your customizations are not applied. However, you still have the opportunity to manually merge your extensions.

  1. Select the version to install, but do not click Merge latest extensions.


    The Install accelerator panel shows the accelerator versions available for installation. The v1.0.1 version is selected. In the Merge options section, the Merge latest extensions check box is not selected.

  2. Go to the project.
  3. In the Integrations section, click the newly installed version. Note that the status label is listed as Configured, and not Merge Successful for the two newly-installed integrations.


    The Integrations section shows two version 1.0.1 integrations and two version 1.0.0 integrations.

    The Extended accelerator versions dialog prompts you to select to merge your extensions.


    The Extended accelerator versions panel is shown. You are prompted to select a version of the accelerator to merge into this version. At the bottom are Cancel, Skip, and Select buttons.

  4. Click Select to merge your extensions. You can also click Skip if you do not want to merge your extensions.
  5. Repeat these steps for any remaining integrations that include extensions you want to manually merge.