Roadmap for Setting Up Unifier with Oracle Integration

This is a high-level roadmap for setting up Unifier with Oracle Integration.

Prerequisites
As an administrator, you have the required permissions to access the following applications:
  • Oracle Integration Administration Console (IDCS)
  • Unifier with Company Administration credentials
  • Oracle Integration application with administration credentials

Procedure

To setup business processes (BPs) configured to use Oracle Integration as the default integration engine, complete the following steps:

  1. In the Oracle Integration Administration Console (IDCS):
    1. Create a Trusted / Confidential Application.
    2. Set the Grant Type to Client Credentials.
    3. Ensure that the application (not a user) is assigned both Service User and Service Administrator privileges. For each of these roles, go to Manage Applications and add the confidential app created.

      For reference, verify the Client Credentials app flow as outlined in Setting Up OAuth and Calling Oracle Integration APIs: A Step-by-Step Guide

  2. Gather the following credentials and URLs:
    • The above step generates Client ID, Client Secret, and App Scope.
    • Keep the Oracle Integration URL and the IDCS URL. You will need this information in the subsequent steps below.
  3. In Unifier, configure the connection to Oracle Integration:
    1. Go to the Company Workspace tab, and switch to Admin mode.
    2. In the left Navigator, select Integrations and then select Oracle Integration Cloud.
    3. Complete the steps outlined in Initial Oracle Integration Setup.
  4. Test for a successful connection and ensure a token is generated.
  5. Obtain the API path by running a test execution in Oracle Integration (Activate integration and then select Run). You will need this information for the next step.
  6. Add integration with Oracle Integration for targeted BPs:
    1. Go to the Company Workspace tab, and switch to Admin mode.
    2. In the left Navigator, select Integrations and then select Oracle Integration Cloud.
    3. In the Oracle Integration Cloud (right pane), select the Integrations tab, and then select Business Processes in the left pane.
    4. Select + Add Integration.
    5. Enter the Integration URL and other details.
    6. Ensure the API Path is relative (usually starts with /ic/api/...).
  7. Link the integration with Oracle Integration in the targeted BPs:
    1. Go to project/shell tab, and switch to Admin mode.
    2. In the left Navigator, select Setup, select Business Process.
    • For workflow BPs, in the Workflow Setup, select the integration with Oracle Integration for specific workflow steps.
    • For non-workflow BPs, in the BP Setup, select the integration with Oracle Integration.
  8. Configuring Recipes/Adapter in Oracle Integration
    1. Trigger Setup
      • The integration should start with a REST trigger (POST method).
      • Do not configure a response. It ensures asynchronous execution.
      • Example POST request payload (JSON):

        {

        "unifierJobId": 12,

        "env_label": "dev",

        "project_number": "P-0001",

        "project_id": 1008,

        "bp_name": "Action Item",

        "bp_prefix": "uxueai",

        "record_no": "AIT-00001",

        "record_id": 1,

        "step_name": "Review",

        "action_name": "Submit" }

    2. Integration Logic
      • (Optional) Subsequent to REST trigger, setup REST Adapter or Unifier Adapter connection to get/send BP records.
      • To avoid 401 authentication errors, always use a dedicated Unifier integration user for each REST connection or Unifier Adapter connection pointing to Unifier.

        Note:

        The same connection can be shared across multiple integrations, but each connection must have its own separate integration user (by selecting the Company Workspace tab, selecting User Administration, and then selecting Integration User).
    3. Configure job status updates.

      Include intermediate invoke calls in Oracle Integration/recipe to update job status back into Unifier for user tracking as outlined in the Callback API.

    4. Validate the integration setup.
      • In Unifier, create or move the BP record to the step configured with Oracle Integration.
      • Verify that the integration is triggered and executed successfully.
    5. To monitor the integration job, users can check the status of the job in the Audit log of the BP record, and in the Company Workspace tab by selecting the System Information node and then selecting the Oracle Integration sub-node.
  9. Error Handling
    In case of a forbidden error, check the following applications: 
    • Oracle Integration IDCS: Verify that the confidential app has been assigned both Service User and Service Administrator privileges.
    • Unifier: Ensure that the correct Client ID and Client Secret from the confidential app created in Oracle Integration IDCS are being used.
Additional References
  • To set up REST Adapter connection in Oracle Integration, ensure:
    • Security Policy: OAuth Custom Two Legged Flow
    • Example of Access Token Request:
      -X GET -H "Content-Type: application/x-www-form-urlencoded" -H "Authorization: Basic <encoded username:password>" -d 'grant_type=client_credentials' https://<unifier url>/ws/rest/service/v2/auth/token

      Note:

      Replace <encoded username:password> with the Base64 encoding of integration username:password. Substitute the correct Unifier URL.