X

The Integration blog covers the latest in product updates, best practices, customer stories, and more.

  • January 22, 2020

Configurators - One stop solution for all your dependency configuration needs

Sindhu Suresh
Technical Lead

For those of you already familiar with the blog for Integration dependency configuration, we have something better to offer. The previous blog talks about replacing a connection dependency in the integration, with the another connection resource of the same role using Rest apis. We know how tedious handling rest apis can get, hence we have now come up with a snazzy UI do the same operation. This feature is available at the integration level and it has also been extended to work at Package level.  

Lets take a look at the Configurator, in detail in the upcoming section

Configurator

Prerequisite

The minimum Oracle Integration version required for the feature is 36410.

Accessing the Configurator

As mentioned earlier, configurator is supported at Integration Level as well as at Package Level.

  • Integration Level
    • If you configure an integration belonging to a package, configurator will open up in a mode that lists all the integrations belonging to the package along with its dependent resources. It will also highlight the integration that clicked to configure. 
    • If you configure an integration that does not belong to any package, configurator will open up in a mode that lists only the selected Integration and its dependent resources.
  • Package Level
    • If you configure a package, configurator will list all the integrations belonging to the package along with its dependent resources.

You can access the Configurator

  1. At Integration level:  In the 'Import Integration' popup, the user will now have an option to 'Import and Configure'. Clicking on which will import the integration/ and then redirect you to the configurator page.                                                               

    On the integration landing page, user can open the action menu and select the Configure option which will redirect you to the configurator page.                         
     
     
  2. At Package level:  On the package landing page, user can open the action menu and select the Configure option which will redirect you to the configurator page.

On the package landing page, click on the wrench icon you see on hover of a package to be redirected to the configurator page.

Using the Configurator

Now, lets take a look at the example below and understand the details of using the configurator. The configurator can be broadly classified into these 3 unique functionalities : 

List of Dependent Resources

Configurator lists the dependent resources present in a specific integration or all the integrations in a specific package.

  • Dependent Resources include Connections, Lookups, Libraries and PGP keys.
  • At Package Level, in addition to the above, it will include a list of integrations as well.

It also displays the corresponding related information of each of the dependent resource (like Connection, Lookup etc) which includes status and usage information. 

  • Status is the status of the resource - Draft, Configured etc
  • At Package Level, the usage information gives us info about how many integrations within the package are using this particular resource
  • At Package Level, in addition to the above, it will include integration information such as Integration Style and Status

In this example of configuring a package, pkg_configurator, all the resources used in the package are listed below. We can see that there are 3 Integrations, 2 Connections, 1 Lookup and 1 Library and 2 Certificates being used.  

We have also added sticky horizontal navigator at the top which will help user easily navigate to the dependent resource he is interested in.

User Actions for each resource

On Hover of each resource, user is presented with different options-  Edit and Replace (for Connections and Certificates), only Edit (for Lookups and Libraries), Add Schedule, Schedule and Update Integration Properties (for Integrations).

  1. Edit:  On Click , the user will be navigated to the corresponding edit page of the resource. Example - Connection Edit Page, PGP Key Edit page etc. 

    Edit action is supported for all resources - i,e Connections, Lookups, Libraries and PGP keys
  2. Replace: On Click, the user will see a popup containing connections that are the same role as original connection.The user can choose the connection with which you want to replace. Upon choosing, the users changes will be saved in memory so they can move on to making other changes. All the changes are collectively saved when the user clicks on the Done Button on top right side.

    Replace action is supported only for Connection and PGP Keys.

    At package level, replacing a resource would replace it across all the integrations in a package.


     
  3. Revert: Once the user has replaced the connection/ certificate, he may wish to revert it back by clicking on the Revert button next to Replace. Revert will undo the replace change and take the dependent resource back to the original.


     
  4. Add/Manage Schedule: On click of Add Schedule, the user will be navigated to the create schedule page with prepopulated schedule. User can save the schedule and navigate back to the configurator page via the Manage Schedule page. 

    On click of Schedule, the user will be navigated to the Manage Schedule page where he can perform actions such as Start Schedule, Stop Schedule, Delete Schedule etc

     
     
  5. Update Integration Properties: On click of Update Property Values, a drawer will open up inline where the user can update any previously added integration properties. 

    Update Integration is only supported for Integrations that already have Integration Properties configured.

     

Details supported for each resource

User can get more information about any resource by clicking on the expand button in the row. On click, a details section will be revelaed with the information captured in the screenshot.

          
 

So this has been a brief explanation about the Configurator. Hope you enjoy using it as much as we enjoyed building it!!

Join the discussion

Comments ( 1 )
  • Sivanadiyan Kumarappan Tuesday, February 11, 2020
    Thank you. It is a nice article.

    In SOA/OSB, we create the config files per UPPER env(Dev, Qat, Uat, Prod) using Jdev and refer this config file when deploying the code in UPPER enviroment. Is there a same config file concept is available for OIC ?

    In OIC Production, Only admin will have the full rights to import and configure. If we provide many steps to change the resource then definitely they don't agree for this and admin will ask for config file where all resource changes can happen with 1 file while importing the OIC code. Please advise on this.

    Thank you.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.