Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path. There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.
- Oracle Integration Classic Administration Restrictions
- Integrations Design-Time Metadata Migration Scope
- Integrations Migration Restrictions
- Processes Design-Time Metadata Migration Scope
- Processes Migration Restrictions
- Visual Builder Design-Time Metadata Migration Scope
- Visual Builder Migration Restrictions
Oracle Integration Classic Administration Restrictions
Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure. In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections. Once migration is complete, you no longer manage your instances. Oracle manages your instances, including performing all backups and patching/upgrading. This enables you to concentrate on developing your integrations, processes, and applications.
Restrictions By Design
With the move to Oracle-managed instances, the following restrictions are by design.
- Any custom configurations done outside of the Oracle
Integration Classic My Services Console are not migrated. For example:
- Configurations performed through direct VM access
- Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others
- Any external processes you created (
There are additional customizations that are not supported. See Unsupported Tasks of Administering Oracle Integration.
- You cannot log in to and access virtual machines (VMs).
- There is no log management through VM access.
- SSH access is not supported.
- IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).
- You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data). Oracle performs all backup and patching/upgrading tasks. The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.
- Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.
- Transport Level Security versions 1.0 and 1.1 are not supported. Oracle Integration endpoints support only TLS 1.2 as a trigger connection. Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.
- Private endpoints are not supported.
- Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.
Integrations Design-Time Metadata Migration Scope
You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure. The archive file consists of the following design-time metadata.
Integrations, connections, lookups, agent groups, and so on. Note that:
Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.
All resources such as lookups and connections that are not currently referenced by integrations are exported.
User-defined credentials. Note the following details:
Credentials are exported into
oracle.wsm.securitymaps are imported.
User-defined certificates (not the seeded certificates). Only user-uploaded trusted certificates (whose alias begins with
icsuser_||_) from the following keystores are exported:
All security policies. Existing policies are not overwritten.
Connection passwords stored in the CSF store.
Settings such as database settings, notification settings, and so on.
Recommendations engine details and API Platform connection details.
Integrations Migration Restrictions
Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.
- Logging settings that you configured are not migrated.
- A best effort is made to migrate database settings.
- After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically. You must manually stop the schedule in Oracle Integration, if necessary.
- If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.
- Only one export at a time can be started. Subsequent export requests are rejected if one is currently running.
- If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.
- If a parent integration calls a child integration, the child integration must be manually activated. This is because the child must be activated after the parent.
- Data of the same name is overwritten. For example, if an integration of the same name and version exists in Oracle Integration, it is overwritten by the integration of the same name and version imported from Oracle Integration Classic.
- Instance runtime data such as monitoring, tracking, and error details is not migrated.
- Custom adapters and their integrations are not migrated. File a service request to have your custom adapters and their integrations included in Oracle Integration.
Processes Design-Time Metadata Migration Scope
Use the Process Import tool to import Processes design-time metadata into Oracle Integration on Oracle Cloud Infrastructure. You can import the following design-time metadata.
- Process applications
- Decision models
Processes Migration Restrictions
Understand the following restrictions when migrating to Oracle Integration on Oracle Cloud Infrastructure.
- Application user role (swimlane) mapping: Process role mappings are not migrated. You must remap Process user roles (swim lanes) for all process applications after activation.
Running instances: Instances cannot be moved between environments.
Running (in flight) process instances and tasks are not migrated to Oracle Cloud Infrastructure.
- Completed process instances and tasks are not migrated to Oracle Cloud Infrastructure.
After importing process applications into Oracle Integration, you must activate them and create new running instances.
Visual Builder Design-Time Metadata Migration Scope
You export the design-time metadata for each visual application into an archive file to then import into the new instance on Oracle Cloud Infrastructure.
The archive file contains the design-time metadata for the applications in your visual application, plus a variety of other files that your visual application needs once it is imported in the new instance. The following directory structure for a visual application that contains a web and mobile app, plus a business object provides an illustrative example of the type of metadata that an archive file contains.
VisualApplicationArchiveDirectory +---businessObjects | \---Department +---mobileApps | \---hrmobileapp | +---flows | | \---main | | \---pages | +---pages | | \---resources | | \---strings | | \---app | | \---nls | | \---root | ... | \---settings | \---mobile-build-templates +---process | \---pcs +---services +---settings \---webApps \---hrwebapp +---flows | \---main | \---pages +---pages | \---resources ... +---resources | +---css | \---strings | \---app | \---nls | \---root \---settings
When you export the visual application you can choose if you want the archive to include the development data contained in the application’s custom business objects. Some information, such as the user credentials to access external REST end points, is removed when you export a visual application. Also, mobile build configurations are not exported. A mobile configuration comprises of artifacts like keystore, iOS provisioning profiles, and passwords. Export this information and artifacts separately so that you can provide it after the archive is imported into the new instance on Oracle Cloud Infrastructure.
Apart from the design-time metadata for each visual application, you also need to export the application data for live applications. Before you migrate this data, you need to lock the live application which prevents end users from accessing the application.
Visual Builder Migration Restrictions
Understand the following restrictions when migrating to a new instance on Oracle Cloud Infrastructure.
You can only migrate the latest version of an existing visual application from the Oracle Cloud Infrastructure Classic instance to Oracle Cloud Infrastructure. Visual Builder does not have a mechanism to import previous versions of the visual application into the new instance. Also, you can only export one version of the visual application from the Oracle Cloud Infrastructure Classic instance at a time. You cannot export all versions of a visual application in one action.
Post-migration, you need to communicate the new URLs that web app end users will use to access the applications that are hosted on the new instance of Oracle Cloud Infrastructure. For mobile app end users, you need to rebuild the mobile app on the Oracle Cloud Infrastructure instance, publish it to the appropriate app store, and inform your end users that they need to update to the newer version of the mobile app.