Complete Post-Migration Tasks for Processes

After verifying and activating integrations, complete Processes tasks.

Topics:

• Perform Post Import Steps for Processes
• Handle In-Flight Process Instances
• Follow Migration Best Practices for Processes

Perform Post Import Steps for Processes

After import, perform additional Processes steps as needed.

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.
   Use values from earlier compartment and object storage configurations. See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service).
   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 ([e-mail])
   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.

   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. Activate imported process applications, if needed. 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.
11. 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.

Handle In-Flight Process Instances

After import, follow guidelines to handle currently running process instances.

Handling short lived instances and their human tasks

• For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.
  • Let classic environment instances and tasks complete and drain, with no new instances created. At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance. During this transition period, end users must use two inboxes.
  • After the transition period, all process runtime activity ends on the classic environment. End users no longer need to use two inboxes.

Handling long lived instances and their human tasks

• For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.
  • Let classic environment instances and tasks complete and drain, with no new instances created. At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance. During this transition period, end users must use two inboxes during the transition period.
  • After the transition period, use the Alter Flow option in the classic environment to terminate instances. Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment. Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process. You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment. See Alter the Flow of a Process Instance in Using Processes in Oracle Integration.

Follow Migration Best Practices for Processes

Follow best practices whenever possible after migration to Oracle Integration.

• Wrap all rules and policy logic into decision models rather than Oracle Business Rules.
• While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC Integrations area instead. From there, you can easily select them for use in structured and dynamic processes. This practice centralizes all integration efforts in the OIC Integrations area.
• Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks. It provides a lighter weight interface with better performance.
  • My Tasks works best for end users
  • Workspace works best for advanced users for back office and tracking purposes