Perform Post Import Steps for Processes

The Process Import tool handles migration of selected process applications and decision models from Oracle Process Cloud Service to Oracle Integration. After import, complete additional steps in Oracle Integration.

  1. In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.
  2. If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure. See Security, Authentication, and Authorization in REST API for Oracle Integration.
  3. In runtime administration, configure supporting services and settings, as needed.
    On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace. In the My Tasks navigation pane, select Administration.
  4. IMPORTANT: Under Archive and Purge, configure purge and archive settings for process instances and analytics data.
    Be sure to verify the retention policies set to purge unused information. Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged. (Purged instances cannot be recovered.) Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity. See Archive and Purge Data in Using Processes in Oracle Integration.
  5. Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications. See How do I integrate with Oracle Content and Experience Cloud? in Using Processes in Oracle Integration.
  6. Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.
    1. In the URL field, enter the URL constructed as follows:
      https://swiftobjectstorage.region.oraclecloud.com/v1/tenancy

      For example:

      https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/paasdevoic
    2. In the Container Name field, enter the storage bucket name.
    3. In the User field, enter your administrator username (my.email@oracle.com)
    4. In the Password field, enter the OAuth token you generated when creating the storage bucket.
  7. Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications. This service must be configured for users to receive email notifications. See Enable Email Notifications.
  8. Open imported decision models used by process applications. Decision models are automatically activated during import.
    Navigate to Decisions and update the references.
  9. Activate imported integration flows if used by process applications. Note that integrations must be activated.

    In Oracle Integration, previously separate processes and integrations now reside in the same environment. After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.

    1. On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.
    2. Select an integration to update, click Edit and update as needed.
    3. Update the security for the called service. Click the Security tab, then the Keystore Credential and update as needed. Set or import credentials/certificates for each REST or SOAP connector used in your process applications.
    4. Complete changes and click Update, and save.
  10. If a basic form was imported, a placeholder web form is created automatically. Open the imported form to complete the transformation from basic form to web form; this is a one-time activity. The new web form contains business objects, presentations, and layouts identical to the original form. However, certain features of basic forms aren't supported or supported differently in web forms. See Processes Migration Restrictions for the complete list.
  11. Rework business rules, as needed.
    Business rules in imported process applications continue to function, but are read-only and cannot be edited. To change them, you must recreate them as decision models. See Create Decisions in Using Processes in Oracle Integration.
  12. Activate imported process applications. See Activate Applications in Using Processes in Oracle Integration. You can also use the Processes REST APIs that allow you to activate process applications.
    Previous runtime instance data is not migrated. See Handle In-Flight Process Instances.
  13. Remap Processes user roles (swim lanes) for all process applications.

    Process role mappings are not migrated. Reconfigure role mappings for each process application under Manage Roles in Workspace Administration. Note that users must be migrated to Oracle Integration before they can be mapped to roles. See Assign and Manage Roles in Using Processes in Oracle Integration.