Integrations and Processes Tasks

Plan and prepare for Oracle Integration Classic migration to Oracle Cloud Infrastructure.

Topics:

Plan Your Migration

Review the following considerations when planning your migration from Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.

Migration considerations:
- Time sensitive migration: You have a window in which to migrate Oracle Integration Classic instances to an Oracle Integration instance. Contact your customer support representative for details.
- Side-by-side migration: You pay to run Oracle Integration Classic side-by-side with Oracle Integration. This option is recommended for high traffic Oracle Integration Classic environments running business-critical integrations and processes in which a window to migrate is not feasible. This option enables you to migrate integrations and processes in a phased fashion.
How many instances (development, test, and production) do you have. This enables you to determine the number of Oracle Integration instances to provision.
Which data centers host the instances. This is important because Oracle Integration may not be available in the same data center regions as your Oracle Integration Classic instances. This means you need to identify other regions in which to run your instances. See https://cloud.oracle.com/data-regions.
Migration time line: Understand why and when to migrate to Oracle Integration.
Big bang versus staggered: If you are running business critical integrations, you cannot migrate everything at once. Create a new Oracle Integration instance for some integrations while continuing to run other instances on Oracle Integration Classic.
Devise a cut over strategy: Determine the best time for your company to migrate to Oracle Integration.
Work out your financial details with the customer sales team.

Prepare to Migrate

Prepare to migrate your Oracle Integration Classic instances to Oracle Integration.

Review the following options when preparing your migration:

Size Oracle Integration Instances

Size your Oracle Integration instances to determine the number of message packs required for your environment.

The concept of sizing is different between Oracle Integration Classic and Oracle Integration.

Oracle Integration Classic is based on CPUs.
Oracle Integration sizing is based on message packs.

There is no 1:1 correspondence between the number of CPUs and the number of message packs. Therefore, you must estimate the relationship. Follow these sizing best practices to determine the number of message packs needed:

Identify the number of Oracle Integration Classic messages by monitoring the Dashboard page. For example:
- How many messages were processed over a specific time period (for example, three days).
- What are the message types being processed (for example, file-based messages or SOAP/REST-based messages).
For specific questions, contact your customer support representative for advice on sizing.
Configure the development environment with different message pack numbers than test and production environments. For example, it is recommended that you configure development to use a minimal number of message packs because you are not running load or performance tests in that environment.
Size the test environment similar to the development environment, unless you know that you have regular usages large enough to require more message packs. A test environment may only run a fraction of the production environment volume most of the time. Typically, a performance test environment would run regular production volumes or more for a short period of time (such as two weeks).
Always estimate the number of messages before deciding on the number of message packs to use.
Guesstimates are fine. The message packs can be increased or decreased, if necessary, from within the Oracle Cloud Infrastructure Console.

Size Processes

Determine message packs needed for Processes for your environment, then add that number to those needed for standalone Integrations and other Oracle Integration features.

Oracle Integration Process sizing is based on concurrent users, which are converted to message packs, and added to message packs needed for integrations.

Each concurrent user (which is a distinct user during that hour) per hour is counted as 400 messages per user. This number is added to the integration volume towards the 5,000 messages per hour. If you have 1,000 messages per hour and 10 distinct users, these would count as 1,000 integration messages + (400)*10 users = 5,000, so 1 message pack of 5,000 messages per hour would suffice.

Another way to visualize Process sizing: 5,000 message packs per hour equate to 12.5 distinct concurrent users performing tasks.

What's counted?

A logged in user is counted for a minimum of one hour when performing any write operations that update a task or process instance, which includes:

Updating or processing tasks (approve/reject a task, add an attachment/comment, re-assign, or request for information)
Creating process instances

Within each hour of use, a distinct user can perform an unlimited number of write operations.

Oracle Integration has a 1 message pack minimum charge per hour to keep the system available, even with no usage. Note that you can turn off your Oracle Integration instance for billing purposes, but no instances are processed while the instance is stopped.

What's NOT counted?

This count doesn’t include:

Logged in users performing read-only only (query or read) operations.
Integrations triggered from the process (integrations are waived).

Example 1

Between 9am and 10am, 20 employees access Workspace. Within the one hour timeframe:

5 users (user1 through user5) create a total of 100 new process instances.
10 other users (user6 through user15) process different tasks created by user1 through user5, and complete them.
The remaining 5 users (user16 through user20) only check the task and process instance status, but do not perform any update/write operations.

Result: The 9am-10 am hour block reports 15 concurrent users (5 created new instances and 10 processed tasks).

Example 2

Between 10 and 11am, 10 users access Workspace and 5 access the Oracle Process Mobile app. Within the one hour timeframe:

10 users (user1 through user10) create new process instances and also approve at least 1 task total.
5 users (user11 through user15) log into the mobile app: 3 of them create new instances, and the other 2 perform only read-only operations.

Result: The 10am-11am hour block reports 13 concurrent users (10 workspace users plus 3 mobile users performed update/write operations, while 2 mobile users did not perform any update/write operations).

Example 3

Between 11am and 12pm, 5 users access Oracle Integration from a Visual Builder application and 5 other users access Workspace.

2 of the 5 Visual Builder users access Visual Builder, and interact with a Visual Builder app that in turn triggers execution of an API that creates new process instances and processes tasks.
The other 3 Visual Builder users access the Visual Builder app and read and access task and process instance status.
The 5 users access Workspace and approve a minimum of 1 task each within the hour timeframe.

Result: The 11am-12pm hour block reports 7 concurrent users (2 Visual Builder users and 5 Workspace users performed update/write operations). This result does not include the Visual Builder concurrent user licenses. Visual Builder concurrent users need to be sized separately.

Allowlist IP Addresses

You may have allowlisted your Oracle Integration Classic IP addresses (explicitly allowed identified entities access). For example, to access an FTP server or perhaps Oracle ERP Cloud calls back to Oracle Integration Classic and you allowlisted some of the Oracle Integration Classic IP addresses with Oracle ERP Cloud.

Perform the following steps:

Provision your instances. This is because allowlisting IP addresses can take approximately three weeks.
File a service request to allowlist IP addresses. Include information from the About button of your Oracle Integration instance. To access the About button:
1. Go to the Oracle Integration Home page.
2. In the upper right corner, click the username icon.
3. From the list, select About.

Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service

If you want to use the Application Migration Service to migrate from Oracle Integration Classic to Oracle Integration Generation 2 on Oracle Cloud Infrastructure, ensure that your Oracle Integration Classic version is 200113.1400.33494 or later. Consult with your administrator to ensure that you are on the correct version.

Enable Access to the Application Migration Service

If you plan to use the Application Migration Service (the recommended tool), ensure that you can access it in your Oracle Cloud Infrastructure tenancy.

See the Prerequisites section in Overview of Application Migration.