Oracle Intg2

Oracle® Cloud
Migrating Oracle Integration Cloud Service

and Process Cloud Service Instances to
Oracle Cloud Infrastructure
F15392-16
April 2020
Oracle Cloud Migrating Oracle Integration Cloud Service and Process Cloud Service Instances to Oracle
Cloud Infrastructure,
F15392-16
Copyright © 2019, 2020, Oracle and/or its affiliates.
Primary Author: Oracle Corporation
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,
license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,
any programs embedded, installed or activated on delivered hardware, and modifications of such programs)
and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end
users are "commercial computer software" or “commercial computer software documentation” pursuant to the
applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use,
reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or
adaptation of i) Oracle programs (including any operating system, integrated software, any programs
embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle
computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the
license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud
services are defined by the applicable contract for such services. No other rights are granted to the U.S.
Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,
and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise
set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be
responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface
Audience v
Documentation Accessibility v
Related Resources vi
Conventions vi
1 Learn About Migrating to Oracle Cloud Infrastructure

Why Migrate to Oracle Cloud Infrastructure 1-1
Key Feature Benefits of Oracle Integration on Oracle Cloud Infrastructure 1-1
About the Migration Scope 1-2
Integrations Migration Scope 1-2
Integrations Migration Restrictions 1-3
Processes Migration Scope 1-4
Processes Migration Restrictions 1-5
About Oracle Cloud Infrastructure 1-6
About the Migration Task Flow and Tooling 1-7
2 Prepare to Migrate Oracle Integration Cloud Service and Oracle

Process Cloud Service to Oracle Cloud Infrastructure
Plan Your Migration 2-1
Prepare to Migrate 2-2
Size Oracle Integration Instances 2-2
Size Processes 2-3
Whitelist IP Addresses 2-4
Enable Oracle Integration Generation 2 Entitlement 2-5
Enable Access to the Application Migration Service 2-5
Understand Best Practices for Migrating the Connectivity Agent 2-5
iii
3 Migrate Your Oracle Integration Cloud Service and Oracle Process
Cloud Service Instances to Oracle Cloud Infrastructure
Migrate Users and Roles 3-1
Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2
Step 2: Create a User and Group and Add Policies 3-3
Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not
Using the Application Migration Service) 3-5
Step 4: Migrate Oracle Integration Cloud Service and Oracle Process Cloud Service
Design-Time Metadata into Oracle Integration 3-8
Create a Source 3-9
Create a Migration 3-10
Configure the Migration Target Instance 3-12
Start and Complete the Migration 3-13
4 Complete the Post-Migration Tasks

Verify Your Environment and Activate Your Integrations 4-1
Replace the Filename Business Identifier Tracking Variable Before Integration
Activation 4-1
Perform Post Import Steps for Processes 4-1
Handle In-Flight Process Instances 4-3
Follow Migration Best Practices for Processes 4-4
5 Troubleshoot Migration Issues

Troubleshoot and Resolve Migration Issues 5-1
A Alternate Migration Options

Create and Validate Oracle Integration Instances A-1
Migrate Oracle Integration Cloud Service Design-Time Metadata into Oracle
Integration A-1
Export the Oracle Integration Cloud Service Design-Time Metadata A-2
Import Design-Time Metadata into Oracle Integration A-3
Check the Design-Time Metadata Import Status A-5
Migrate Oracle Process Cloud Service Design-Time Metadata into Oracle
Integration A-5
Import Oracle Process Cloud Service Design-Time Metadata A-6
Import Using the Import Command Line Utility A-7
iv
Preface
Migrating Oracle Integration Cloud Service and Process Cloud Service Instances to
Oracle Cloud Infrastructure describes how to migrate Oracle Integration Cloud Service
and Oracle Process Cloud Service to Oracle Integration on Oracle Cloud
Infrastructure.
Note:
The information in this guide applies to all of your Oracle Integration
instances. It doesn’t matter which edition you’re using, what features you
have, or who manages your cloud environment. You’ll find what you need
here, including notes about any differences between the various flavors of
Oracle Integration when necessary.
Topics:
• Audience
• Documentation Accessibility
• Related Resources
• Conventions
Audience
Migrating Oracle Integration Cloud Service and Process Cloud Service Instances to
Oracle Cloud Infrastructure is intended for users need to migrate Oracle Integration
Cloud Service and Oracle Process Cloud Service to Oracle Integration on Oracle
Cloud Infrastructure.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support
through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/
lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=trs if you are hearing impaired.
v
Preface
Related Resources
For more information, see these Oracle resources:
• Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help
Center.
• Oracle Cloud at http://cloud.oracle.com.
Conventions
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.
vi
1
Learn About Migrating to Oracle Cloud
Infrastructure
Learn about the benefits to migrating your existing Oracle Integration Cloud Service
and Oracle Process Cloud Service instances to Oracle Integration Generation 2 on
Oracle Cloud Infrastructure, and receive an overview of the migration process and
tools.
Topics:
• Why Migrate to Oracle Cloud Infrastructure
• About the Migration Scope
• About Oracle Cloud Infrastructure
• About the Migration Task Flow and Tooling
Video
Why Migrate to Oracle Cloud Infrastructure

Oracle encourages you to migrate your existing cloud resources from Oracle Cloud
Infrastructure Classic regions. You can gain several advantages by doing so.
In Oracle Cloud, you provision resources in specific regions, which are localized to
geographic locations. Certain regions support the Oracle Cloud Infrastructure platform.
Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the
latest cloud technologies and standards. It provides more consistent performance and
better features at lower costs. Oracle continues to invest in Oracle Cloud
Infrastructure, including the addition of new regions, services, and features. See Data
Regions for Platform and Infrastructure Services.
You can benefit from these additional administrative features when you migrate your
cloud resources to Oracle Cloud Infrastructure:
• Organize cloud resources into a hierarchy of logical compartments.
• Create fine-grained access policies for each compartment.
Key Feature Benefits of Oracle Integration on Oracle Cloud

Infrastructure
Migrating your Oracle Integration Cloud Service and Oracle Process Cloud Service
instances to Oracle Integration on Oracle Cloud Infrastructure lets you take advantage
of the substantial product features and enhancements included in Oracle Integration,
all available on a unified platform.
1-1
Chapter 1
About the Migration Scope
Note:
New features are continuously being released on Oracle Integration. These
new features are not being released on Oracle Integration Cloud Service or
Oracle Process Cloud Service. See What's New for Oracle Integration.
Here are some recent key Integrations and adapter features and enhancements:
• Connectivity agent high availability support
• Oracle Talent Acquisition Cloud (Taleo EE) Adapter
• Oracle HCM Cloud Adapter - HCM Atom feed and HCM data extracts support
• SOAP Adapter- Dynamic endpoint discovery support
Here are some recent key Processes features and enhancements:
• Dynamic processes (case management)
• Notification enhancements in human workflow
• Enhanced DMN modeling and integrated lifecycle with Processes
• Integration with robotic process automation
• Improved web forms and developer capabilities (including enhanced debugging)
• Improved interoperability with integration flows

Before migrating your existing Oracle Integration Cloud Service and Oracle Process
Cloud Service instances to Oracle Integration on Oracle Cloud Infrastructure, consider
the scope and constraints of this migration path. Once migration is complete, Oracle
continues to manage your instances.
• Integrations Migration Scope
• Integrations Migration Restrictions
• Processes Migration Scope
• Processes Migration Restrictions
Integrations Migration Scope

You export Oracle Integration Cloud Service 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.
• Endpoint configurations
1-2
Chapter 1
• User-defined credentials. Note the following details:

– Credentials are exported into cwallet.sso.
– The oracle.cloud.adapter map and oracle.wsm.security maps 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:
– system/trust
– owsm/keystore
– ics/keystore
• 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.
Note:
The Oracle Integration Cloud Service REST APIs are supported in Oracle
Integration.
Integrations Migration Restrictions

Understand the following restrictions when migrating Oracle Integration Cloud Service
to Oracle Integration on Oracle Cloud Infrastructure.
What is Not Migrated

• Logging settings that you configured in Oracle Integration Cloud Service are not
migrated. Reset previously configured logging settings by selecting Settings >
Logging on the Oracle Integration Home page. See Configure Settings for Error
Logs of Administering Oracle Integration.
• 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.
• The user interface for space management settings in Oracle Integration is divided
into three tabs (Database Space, Nightly Purge, and Auto Purge), whereas there
is only a single page for database settings in Oracle Integration Cloud Service.
Because of these differences, a best effort is made to migrate database settings.
Verify your database settings after migration completes to ensure that they are
correct for your environment.
• You cannot use Filename as a business identifier tracking variable in Oracle
Integration. If you do, integration activation fails after migration. Specify a different
business identifier variable. See Replace the Filename Business Identifier
Tracking Variable Before Integration Activation.
1-3
Chapter 1
Feature Differences Between Oracle Integration Cloud Service and Oracle

Integration on Oracle Cloud Infrastructure
• The Oracle Integration Cloud Service execution agent is not supported.
• You can continue using the Oracle Integration Cloud Service APIs. However, if
you need to use the newer capabilities of the advanced APIs, you must move to
the new URLs provided with Oracle Integration. The Oracle Integration Cloud
Service REST APIs relative path is /icsapis/v2/resource. The Oracle Integration
REST APIs relative path is /ic/api/integration/v1/resource.
• All inbound endpoints for Oracle Integration integrations are hosted on SSL
servers that can accept requests coming from clients supporting transport layer
security (TLS) 1.2. This is true regardless of whether they are SOAP- or REST-
enabled and regardless of the adapter used as the trigger connection. Oracle
Integration Cloud Service endpoints supported TLS 1.1 and TLS 1.2 for trigger and
invoke connections. If you were using TLS 1.1 for trigger connections with Oracle
Integration Cloud Service, note that Oracle Integration does not support this
version due to security issues. You must configure your client to use TLS 1.2 when
invoking Oracle Integration services.
Expected Behavior
• The Oracle Integration Cloud Service agent installation is not migrated because it
is installed on an on-premises host. You must install the newer, lightweight Oracle
Integration version of the connectivity agent on your on-premises host.
• 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 Cloud Service.
• After importing a scheduled integration (scheduled is started) from Oracle
Integration Cloud Service into Oracle Integration, the integration is imported and
the schedule is started automatically. You must manually stop the schedule in
Oracle Integration Cloud Service.
• If you modify the default value of the recovery job in Oracle Integration Cloud
Service, the migration 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.
Processes Migration Scope

Use the Process Import tool to import Oracle Process Cloud Service design-time
metadata into Oracle Integration on Oracle Cloud Infrastructure. You can import the
following design-time metadata.
• Process applications
• Decision models
1-4
Chapter 1
Processes Migration Restrictions

Understand the following restrictions when migrating Oracle Process Cloud Service to
Oracle Integration on Oracle Cloud Infrastructure.
• Forms: Oracle Integration supports web forms only. When you migrate a process
application with a basic form, the basic form is imported as a web form. But, the
complete transformation from basic to web form occurs when you open the
imported form for the first time. The new web form contains business objects,
presentations, and layouts identical to the original form. In addition, the migrated
form retains its links to human tasks and data associations. However, certain
features of basic forms aren't supported or supported differently in web forms.
Here's the complete list of limitations of migrating to web forms:
– Rules: Rules defined for controls in basic forms aren't retained upon migration
to web forms. You'll need to redefine rules using web form events.
– Image Control: Unlike basic forms, web forms don't support direct image
linking. Therefore, an image in a basic form is converted to its Base64
equivalent upon migration.
– Message Control: Different types of messages in basic forms, such as
Warning, Info, and so on, are all converted to a single type upon migration.
Additionally, rich text content is converted to plain text.
– HTML Text: Inline HTML links in any control's text or label within a basic form
are converted to plain links upon migration to web form.
– Checklist Control: The output of a checklist control migrated from a basic
form will be a plain string with comma-separated values.
– Section Control: Styling applied to a section control's label or border isn't
retained upon migration from basic form to web form. In addition, the layout of
sections may slightly vary after migration as web forms don't support
horizontal alignment of controls within sections.
– Control Labels: In basic forms, there's a provision to hide control labels,
which isn't supported in web forms. Therefore, all hidden labels are shown
upon migration.
– Table and Repeatable Section Controls: Generally, table or repeatable
section controls contain a certain number of rows by default in the basic form.
Upon migration, these rows aren't retained; instead, the User can Add/
Remove Rows check box is selected in the migrated web form.
• Decisions: Oracle Integration supports decision models (DMN) only. It is
recommended that before migrating process applications containing Oracle
Business Rules, you recreate rules as decision models. Oracle Business Rules
present in imported applications are retained as read only rules in Oracle
Integration. The read-only business rules will still function. You can delete them,
but you cannot edit them.
• Integrations: Guidelines differ depending on the integration type:
– Integrations created using REST and SOAP connectors in Processes continue
to work after migration. You can edit them in the Processes component.
However, it is a best practice to recreate them in the Integrations feature
whenever possible to centralize integrations in Oracle Integration.
1-5
Chapter 1
About Oracle Cloud Infrastructure
– Integrations created in Oracle Integration Cloud Service and called in

Processes must be exported from Oracle Integration Cloud Service and
imported into Oracle Integration. Process applications that call Oracle
Integration Cloud Service integrations cannot be activated.
• Users and roles: Oracle Integration uses Oracle Identity Cloud Service (IDCS) for
identity management. You must move users and roles from Oracle Process Cloud
Service to Oracle Integration.
Note:
You can migrate users and role memberships for Oracle Cloud services
from traditional cloud accounts to cloud accounts with Oracle Identity
Cloud Service. See Migrate from Traditional Cloud Accounts to Cloud
Accounts with Identity Cloud Service in Administering Oracle Identity
Cloud Service.
• 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. Note that users must be configured in IDCS before
administrators can map swimlane roles for them in process applications.
• Running Instances: Running 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.
About Oracle Cloud Infrastructure

Get familiar with basic Oracle Cloud Infrastructure security, network, and storage
concepts.
Cloud resources in Oracle Cloud Infrastructure are created in logical compartments.
You also create fine-grained policies to control access to the resources within a
compartment.
You create instances within an Oracle Cloud Infrastructure region. You also specify an
availability domain (AD), if supported in the selected region.
A virtual cloud network (VCN) is comprised of one or more subnets, and an instance is
assigned to a specific subnet. Oracle Cloud Infrastructure does not allow you to
reserve specific IP addresses for platform services.
A subnet's security lists permit and block traffic to and from specific IP addresses and
ports.
Instances can communicate with resources outside of Oracle Cloud by using Oracle
Cloud Infrastructure FastConnect, which provides a fast, dedicated connection to your
on-premises network. Alternatively, use an IPSec VPN.
1-6
Chapter 1
About the Migration Task Flow and Tooling
A bucket in Oracle Cloud Infrastructure Object Storage can be used to store files and
share them with multiple instances. A user's generated authentication token (auth
token) is required to access the bucket.
To learn more, see Key Concepts and Terminology in the Oracle Cloud Infrastructure
documentation.
About the Migration Task Flow and Tooling

Get an overview of the process that you use to migrate your existing Oracle Integration
Cloud Service and Oracle Process Cloud Service instances to Oracle Integration on
Oracle Cloud Infrastructure.
At a high level, the migration process consists of these tasks:
1. Plan and prepare for the migration and perform any prerequisite tasks in Oracle
Cloud Infrastructure if necessary.
2. Select the migration tool to export and import Oracle Integration Cloud Service and
Oracle Process Cloud Service design-time metadata into Oracle Integration on
Oracle Cloud Infrastructure:
a. (Recommended) Use the Application Migration Service to export and import
design-time metadata. The Application Migration Service provides a graphical
user interface to automate the migration process. When you use the
Application Migration Service tool, an object storage bucket and new target
instance are automatically provisioned for you.
b. (Alternate) Use the import tool (user interface or command line) to import
Oracle Process Cloud Service design-time metadata only. When you use the
import tool (user interface or command line), you must manually create the
object storage bucket and the target Oracle Integration instance in an Oracle
Cloud Infrastructure region.
c. (Alternate) Use the curl or postman commands to export and import design-
time metadata. You must manually create the object storage bucket and the
target Oracle Integration instance in an Oracle Cloud Infrastructure region.
3. Test your applications on the target instance, and perform any other post-
migration tasks.
1-7
2
Prepare to Migrate Oracle Integration
Cloud Service and Oracle Process Cloud
Service to Oracle Cloud Infrastructure
Before you migrate Oracle Integration Cloud Service and Oracle Process Cloud
Service instances to Oracle Integration Generation 2 on Oracle Cloud Infrastructure,
plan and prepare for migration.
Topics:
• Plan Your Migration
• Prepare to Migrate
Plan Your Migration

Review the following considerations when planning your migration from Oracle
Integration Cloud Service and Oracle Process Cloud Service to Oracle Integration on
Oracle Cloud Infrastructure.
• Migration considerations:
– Time sensitive migration: You have a window in which to migrate Oracle
Integration Cloud Service and Oracle Process Cloud Service instances to an
Oracle Integration. Contact your customer support representative for details.
– Side-by-side migration: You pay to run Oracle Integration side-by-side with
Oracle Integration Cloud Service and Oracle Process Cloud Service. This
option is recommended for high traffic Oracle Integration Cloud Service and
Oracle Process Cloud Service 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 Cloud Service and Oracle Process Cloud Service instances. This
means you need to identify other regions in which to run your instances. See
https://cloud.oracle.com/data-regions.
• Requirements for new features: New features are continuously being released on
Oracle Integration. These new features are not being released on Oracle
Integration Cloud Service or Oracle Process Cloud Service. See What's New for
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
Cloud Service and Oracle Process Cloud Service.
2-1
Chapter 2
Prepare to Migrate
• Devise a cut over strategy: Determine the best time for your company to migrate to
Oracle Integration.
• Address feature gaps: Understand all migration feature restrictions. See
Integrations Migration Restrictions and Processes Migration Restrictions.
• Migrate billing from metered/nonmetered: Oracle Integration uses a different billing
methodology than Oracle Integration Cloud Service and Oracle Process Cloud
Service. See Pricing and contact your customer support representative.
• Work out your financial details with the customer sales team.
Prepare to Migrate
Prepare to migrate your Oracle Integration Cloud Service instances to Oracle
Integration.
Review the following options when preparing your migration:
• Size Oracle Integration Instances
• Size Processes
• Whitelist IP Addresses
• Enable Oracle Integration Generation 2 Entitlement
• Enable Access to the Application Migration Service
• Understand Best Practices for Migrating the Connectivity Agent
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 Cloud Service and Oracle
Integration.
• Oracle Integration Cloud Service sizing is based on connections.
• Oracle Integration sizing is based on message packs.
There is no 1:1 correspondence between the number of connections 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 Cloud Service 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.
2-2
Chapter 2
Prepare to Migrate
• 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.
The concept of sizing is different between Oracle Process Cloud Service and Oracle
Integration.
• Oracle Process Cloud Service sizing is based on named users.
• Oracle Integration Process sizing is based on concurrent users, which are
converted to message packs.
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).
2-3
Chapter 2
Prepare to Migrate
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.
Whitelist IP Addresses
You may have whitelisted your Oracle Integration Cloud Service IP addresses. For
example, to access an FTP server. Or perhaps Oracle ERP Cloud calls back to Oracle
Integration Cloud Service and you whitelisted some of the Oracle Integration Cloud
Service IP addresses with Oracle ERP Cloud.
Perform the following steps:
• Provision your new instances. This is because whitelisting IP addresses can take
approximately three weeks.
2-4
Chapter 2
Prepare to Migrate
• File a service request to whitelist 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.
Enable Oracle Integration Generation 2 Entitlement

If your cloud account was created in a home region of North America or Asia before
Nov 13, 2019, or in a home region of EMEA or Latin America before Dec 12, 2019,
discuss with your Oracle representative whether your account needs Oracle
Integration Generation 2 entitlement.
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.
Understand Best Practices for Migrating the Connectivity Agent

If using the connectivity agent, follow these best practices for migrating the agent to
Oracle Integration.
1. If using the Application Migration Service:
• Create and complete a migration of Oracle Integration Cloud Service. See

Step 4: Migrate Oracle Integration Cloud Service and Oracle Process Cloud
Service Design-Time Metadata into Oracle Integration.
2. If using the curl or postman commands:
a. Export the Oracle Integration Cloud Service archive. See Export the Oracle
Integration Cloud Service Design-Time Metadata.
b. Import the archive into Oracle Integration, but do not select the mode to
activate integrations automatically. Instead, select ImportOnly. This allows
you time to verify that your integrations have been properly imported into
Oracle Integration before activation. See Import Design-Time Metadata into
Oracle Integration.
3. Download and install the Oracle Integration agent. You cannot use the Oracle
Integration Cloud Service agent installation.
4. Verify that the agent is registered in Oracle Integration and running.
5. Use the REST API to activate integrations or manually activate each integration on
the Integrations page.
Note:
If you run Oracle Integration and Oracle Integration Cloud Service side
by side, the agents for both environments can co-exist.
2-5
3
Migrate Your Oracle Integration Cloud
Service and Oracle Process Cloud Service
Instances to Oracle Cloud Infrastructure
Migrate your Oracle Integration Cloud Service and Oracle Process Cloud Service
instances to Oracle Integration Generation 2 on Oracle Cloud Infrastructure.
Topics:
• Migrate Users and Roles
• Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment
• Step 2: Create a User and Group and Add Policies
• Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not
Using the Application Migration Service)
• Step 4: Migrate Oracle Integration Cloud Service and Oracle Process Cloud
Service Design-Time Metadata into Oracle Integration
Note:
• If you have an Oracle Integration Cloud Service instance and an Oracle

Process Cloud Service instance, you can migrate the design-time
metadata of each instance to a single Oracle Integration on Oracle Cloud
Infrastructure instance.
• Oracle Integration Cloud Service for Oracle SaaS (also known as
ICS4SaaS) is a version of Oracle Integration Cloud Service targeted for
use with Oracle SaaS products. Oracle provides a path for ICS4SaaS
users to migrate their workloads to Oracle Cloud Infrastructure. See
Migrating from ICS4SaaS to OIC4SaaS.
Migrate Users and Roles

You can migrate users and role memberships for Oracle Cloud services from the
traditional cloud accounts used by Oracle Integration Cloud Service and Oracle
Process Cloud Service to Oracle Integration accounts managed with Oracle Identity
Cloud Service.
See Migrate from Traditional Cloud Accounts to Cloud Accounts with Identity Cloud
Service of Administering Oracle Identity Cloud Service.
In migrating users, groups, and memberships from SIM to IDCS, note the following
issues:
3-1
Chapter 3
Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment
• Oracle Integration Cloud Service and Oracle Process Cloud Service role names
map to different application role names in Oracle Integration. See Map Between
Traditional Cloud Roles and Application Roles in Oracle Identity Cloud Service.
• You must export users, groups and their memberships from My Services and then
import them into IDCS. It is EXTREMELY important that the names use the
same case.
• The minimum password length is eight characters for traditional cloud accounts.
This differs from Oracle Identity Cloud Service accounts, where the minimum
length is 12 characters. If you want to allow the use of traditional cloud account
passwords, change the minimum length of the custom password policy in Oracle
Identity Cloud Service to eight characters. See Migrate Users.
As an alternative, you can manually add users, groups, and roles if you have a small
number of users. See Grant Access and Manage Security of Administering Oracle
Integration.
Step 1: Create a Cloud Storage Compartment or Use an

Existing Compartment
Oracle Integration instances use the Oracle Cloud Infrastructure as their underlying
infrastructure. To export design-time metadata into an Oracle Integration instance, you
must first create a compartment (if one does not exist). This task is required regardless
of the migration tool you use.
Note:
If not using the Application Migration Service, you must have an Oracle
Storage Cloud Service account to perform these steps.
1. Log in to the Oracle Cloud Infrastructure Console as the Administrator user.

2. Open the navigation menu.
3. Under Governance and Administration, go to Identity, then click
Compartments.
A list of the compartments in your tenancy is displayed.
4. Click Create Compartment to create the compartment to use for upgrading.
5. Enter the following:
• Name: Enter a name that is unique across all compartments in your tenancy
(maximum 100 characters, including letters, numbers, periods, hyphens, and
underscores).
• Description: Enter a description for this compartment.
• Tags: Enter tags to organize and list resources based on your business
needs.
6. Click Create Compartment.
3-2
Chapter 3
Step 2: Create a User and Group and Add Policies

To export design-time metadata into an Oracle Integration instance, you must also
create a user and group and add policies that enable you to perform the migration.
1. Open the navigation menu.
2. Go to Governance and Administration > Identity > Users to create the user to
use for migration.
3. Click Create User.
4. Enter a name and description.
5. Click Create.
6. Under Governance and Administration, go to Identity, then click Groups.
A list of the groups in your tenancy is displayed.
7. Click Create Group to export your design-time metadata.
8. Enter a name and description.
9. Click Create Group.
You are now ready to add the user to the group. When configuration is complete,
users in this group can export design-time metadata into Oracle Integration.
10. Locate the group you created in the list.
11. Click the group. Its details are displayed.
12. Click Add User to Group.
13. Select the user you created from the list, then click Add User.
14. Return to the navigation menu.
15. Under Governance and Administration, go to Identity, then click Policies.
16. Select the compartment you previously created.
17. Click Create Policy.

18. Enter a name and optional description.
19. Leave KEEP POLICY CURRENT as the Policy Versioning selection.
20. Add the following statements to migrate to Oracle Integration Generation 2. The
statements to add are based on the migration tool you use.
3-3
Chapter 3
Migration Tool Statements

If using Add these statements:
Application
Migration allow service applicationmigration to inspect
Service
compartments in tenancy
allow service applicationmigration to
{ TENANCY_INSPECT } in tenancy
{ IDENTITY_PROVIDER_INSPECT } in tenancy
allow service applicationmigration to manage database-
family in tenancy
allow service applicationmigration to use vcns in
tenancy
allow service applicationmigration to use subnets in
tenancy
allow service applicationmigration to use vnics in
tenancy
{ VNIC_ATTACHMENT_READ } in tenancy
{ INSTANCE_INSPECT } in tenancy
allow service applicationmigration to manage analytics-
instances in tenancy
allow service applicationmigration to manage
integration-instances in tenancy
allow service PSM to inspect vcns in tenancy
allow service PSM to use subnets in tenancy
allow service PSM to use vnics in tenancy
allow service PSM to manage security-lists in tenancy
allow service PSM to inspect database-family in tenancy
If using a Either add three statements or condense them into two statements.
different • As three statements:
migration tool, – allow group Upgrade_Group to manage buckets in
for example: compartment Upgrade_Compartment
• Import tool – allow group Upgrade_Group to manage objects in
to export compartment Upgrade_Compartment where any
and import {request.permission='OBJECT_CREATE',
Processes request.permission='OBJECT_INSPECT'}
design-time
metadata – allow group Upgrade_Group to manage objects in
compartment Upgrade_Compartment where any
• curl or
{request.permission='OBJECT_DELETE'}
postman
command to • As two condensed statements:
export and – allow group Upgrade_Group to manage buckets in
import compartment Upgrade_Compartment
Integrations – allow group Upgrade_Group to manage objects in
and compartment Upgrade_Compartment where any
Processes {request.permission='OBJECT_CREATE',request.perm
design-time ission='OBJECT_DELETE',request.permission='OBJEC
metadata T_INSPECT'}
where:
• Upgrade_Group is the group you created.
• Upgrade_Compartment is the compartment you created.
3-4
Chapter 3
Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service)
This action enables users in this group to export design-time metadata to Oracle
Integration.
21. Click Create.
Step 3: Create an Object Storage Bucket and Construct the

Storage URL (If Not Using the Application Migration Service)
If you are not using the Application Migration Service for migration, you must create a
storage bucket (if one does not already exist) and construct the storage URL to specify
in order to export design-time metadata into an Oracle Integration instance. You must
specify this URL later during the configuration process to migrate your instance. If you
use the Application Migration Service, these tasks are automatically performed for you.
Note:
• If using the Application Migration Service, skip this section.

• Do not create a Classic Storage bucket. Classic Storage is not
supported.
1. Log in to the My Services Console with the user that the administrator added to
the group for exporting design-time metadata. You must have the admin role to
access this page.
2. If the Compute section is not displayed, select in the upper
right corner of the My Services Dashboard.
a. Click Show in the Compute section. This enables this service to appear on
the My Services page.
3. Click Compute to access the Oracle Cloud Infrastructure page.
4. In the upper right corner, click .

5. In the upper left corner of the Oracle Cloud Infrastructure page, click .
6. Select Object Storage > Object Storage.
7. Select the compartment in which to create the storage bucket. The compartment
to use for exporting design-time metadata was created in Step 1: Create a Cloud
Storage Compartment or Use an Existing Compartment. You can also click Learn
more about Compartments to find the appropriate compartment for your
environment.
8. After determining the compartment to use, click Create Bucket.
3-5
Chapter 3
9. In the Bucket Name field, enter a name.

10. In the Storage Tier section, select Standard.
11. Click Create Bucket.
The new bucket is displayed in the list.
12. If you want to view bucket details, click the name (for this example, cloneRepo).
Note:
Ensure that you click the Public button and deselect the Allow Users
To List Objects From This Bucket check box. This action ensures that
the storage bucket you create is publicly visible. Otherwise, the export
utility cannot see the storage.
3-6
Chapter 3
13. In the upper left corner of the page, click .

14. Select Identity > Users. This opens the Oracle Identity Service Console to
generate a password.
15. Select the appropriate user.
16. From the Resources list on the left side of the page, select Auth Tokens.
17. Click .
18. Provide a token description and click .

This token is used as part of your JSON payload when upgrading.
19. Copy and save the generated token.
a. The storage payload format is as follows with object storage bucket details:
{"storageInfo":
{
"storageUrl":"https://
swiftobjectstorage.region.oraclecloud.com/v1/
namespace/bucket",
"storageUser":"[email protected]",
"storagePassword":"generated_token"
}
}
For example:
{
"storageInfo":
{
"storageUrl":"https://swiftobjectstorage.us-
ashburn-1.oraclecloud.
com/v1/paasdevoic/cloneRepo",
}
}
20. Construct the storage URL using the following example. You must specify the URL
later during the configuration process to migrate your instance.
Step Description Example

1 Enter the Swift API as the https://
base for the URL because swiftobjectstorage
you are dealing with object
storage.
2 Enter a required data center. https://
To find a data center, swiftobjectstorage.us-
navigate to Menu > ashburn-1
Administration > Tenancy
Details > Home Region (for
example: us-ashburn-1).
3-7
Chapter 3
Step 4: Migrate Oracle Integration Cloud Service and Oracle Process Cloud Service Design-Time Metadata into Oracle
Integration
Step Description Example

3 Enter the domain name. This https://
is typically swiftobjectstorage.us-
oraclecloud.com. ashburn-1.oraclecloud.
com
4 Enter the version: v1. https://
swiftobjectstorage.us-
com/v1
5 Enter the automatically paasdevoic
generated object storage
namespace. Open the User
menu and click Tenancy:
your_tenancy_name. The
namespace string is listed
under Object Storage
Settings. See
Understanding Object
Storage Namespaces.
6 Enter the bucket name as https://
the last part of the URL. swiftobjectstorage.us-
com/v1/paasdevoic/
BUCKET_NAME
Examples of the full storage URL to use later in the payload are as follows:
https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/paasdevoic/
cloneRepo
https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/paasdevoic/
migrationartifacts_bucket-20190717-1223
Step 4: Migrate Oracle Integration Cloud Service and Oracle

Process Cloud Service Design-Time Metadata into Oracle
Integration
You can use the Application Migration Service to migrate your Oracle Integration
Cloud Service and Oracle Process Cloud Service design-time metadata into Oracle
Integration Generation 2. Access to the Application Migration Service is included in the
One Console of Oracle Cloud Infrastructure. A user that is an administrator of the
tenancy (in the Administrators group) can perform the migration.
Topics:
• Create a Source
• Create a Migration
• Configure the Migration Target Instance
• Start and Complete the Migration
3-8
Chapter 3
Integration
The Application Migration Service is also described in the Oracle Cloud Infrastructure
Documentation Library. See Manage Migrations.
Create a Source
You must create a source migration to map your Oracle Integration Cloud Service or
Oracle Process Cloud Service account to the Oracle Cloud Infrastructure tenancy. If
migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a
different source is required for each. Creating a source migration enables you to
discover the list of applications (instances) that are available to migrate.
Note:
Ensure you have the required permissions to perform a migration. See
Service Permissions.
1. Sign in to the One Console of Oracle Cloud Infrastructure.

2. In the upper left corner, select
.
3. Under Solutions and Platform, select Application Migration.
The Overview page shows a workflow for using the Application Migration Service.
The Application Migration Service also checks if you have satisfied migration
prerequisites and identifies any issues that must be satisfied before beginning.
4. In the left pane under Application Migration, click Sources.
5. From the Compartment list, select a compartment in which you have permission
to work. The page updates to display only the resources in that compartment. If
you're not sure which compartment to use, contact an administrator. For more
information, see Access Control.
6. Click Create Source.
Note:
The Create Source option is also available in the workflow on the
Overview page.
7. Enter the following details, then click Create.
Element Description
Name Enter a name for the source. This is not the
name for your new migrated application
(instance).
Description Enter an optional description.
Compartment Select the compartment to use for migration.
By default, the compartment that you
selected prior to clicking Create Source is
displayed.
3-9
Chapter 3
Integration
Element Description
Source Type Select Internal Compute to migrate an
Oracle Integration Cloud Service or Oracle
Process Cloud Service application
(instance). You cannot migrate both
services at the same time. However, both
Oracle Integration Cloud Service and Oracle
Process Cloud Service applications
(instances) can be discovered. A single
source can list multiple Oracle Integration
Service applications. When you create a
migration, you must create a migration for
each application.
Account Enter your Oracle Integration Cloud Service
or Oracle Process Cloud Service account.
The account number is used to identify the
location of your Oracle Integration Cloud
Service or Oracle Process Cloud Service
application (instance). If you use a
traditional account for Oracle Integration
Service, enter the identity domain ID.
Service Administrator Username Enter the service administrator username for
the Oracle Integration Cloud Service or
Oracle Process Cloud Service application
(instance). This user must be assigned the
INTEGRATIONCLOUD_ENTITLEMENT_A
DMINISTRATOR role.
Service Administrator Password Enter the service administrator password for
this username.
Create a Migration
When you create an Oracle Integration Cloud Service or Oracle Process Cloud
Service migration source, all applications (instances) available for you to migrate are
discovered.
3-10
Chapter 3
Integration
1. Wait for the page to refresh, then scroll down to view the instances in this tenancy.
Oracle Integration Cloud Service or Oracle Process Cloud Service applications are
identified as ICS and PCS, respectively, in the Type column.
2. In the far right section of the row of the Oracle Integration Cloud Service or Oracle
Process Cloud Service application to migrate, click
. For this example, an Oracle Integration Cloud Service application that is available
for migration is selected.
3. Select Create Migration.
4. Enter the following details, and click Create. Several fields are automatically
populated with details.
Element Description
Migration Name Accept the default name, which is appended
with a timestamp, or enter a different name.
Description Enter an optional description.
Source Displays the name of the selected source
migration.
Application Displays the name of the selected
application.
Service Instance User Enter the service instance username for the
application to migrate. This user must have
the ServiceAdministrator role.
Service Instance Password Enter the service instance password.
Target Instance Type Select the type of target instance in Oracle
Cloud Infrastructure. The availability of this
feature depends on your Oracle Cloud
Infrastructure home region and your
subscription. For Oracle Integration Cloud
Service or Oracle Process Cloud Service,
select Oracle Integration - Generation 2.
3-11
Chapter 3
Integration
5. View migration creation in the Percent Complete column.

When migration creation completes, you are ready to create a configuration in
which you provide details about the new target instance to create.
Configure the Migration Target Instance

Once migration creation completes, you create a configuration that describes the new
Oracle Integration Generation 2 target instance to create in Oracle Cloud
Infrastructure. This configuration automatically creates an object storage bucket and
new instance.
1. Click Configure to provide target instance details.
2. Review the overview page and click Configure. For this example, an Oracle
Integration Cloud Service instance is being migrated.
The Configure Target Integration Cloud Service Instance dialog is displayed

because Oracle Integration Cloud Service is being migrated for this example. If
you are migrating Oracle Process Cloud Service, the name of the dialog is
Configure Target Process Cloud Service Instance.
3-12
Chapter 3
Integration
3. Enter the following details, then click Configure.
Element Description
Instance Name Enter a name for the new instance that is
unique within your tenancy.
Description Enter an optional description to help identify
the new service instance.
Bring Your Own License Select the checkbox to bring your own
license option (BYOL) to the new instance if
your organization already owns an Oracle
Fusion Middleware software license for
Oracle Integration Cloud Service or Oracle
Process Cloud Service. Otherwise, leave
the checkbox unselected to subscribe to a
new Oracle Integration software license.
Number of Message Packs The maximum number of message packs
for an instance is based on your license
type.
• For BYOL, the instance can have
between 1 and 3 message packs. Each
message pack adds 20K messages per
hour to your instance.
• If you don’t have a BYOL license type,
the instance can have between 1 to 12
message packs. Each message pack
adds 5K messages per hour to your
instance.
Notification Email Enter an email address at which to be
notified of migration status.
IDCS Username Enter the PaaS username for the account.
This user must be a user with Oracle
Integration roles in Oracle Cloud
Infrastructure tenant:
• Service: INTEGRATIONCAUTO
• Service Role:
AUTONOMOUS_INTEGRATIONCLOU
D_ENTITLEMENT_ADMINISTRATOR
(Autonomous Integration Cloud
entitlement administrator role)
This service role is granted to the
AMS_AllServices_Admins group already in
the tenant AMSTESTROLLOUT (EMEA)
and Amstestapac (APAC). Ensure your user
is either in this group or has the Oracle
Integration role explicitly.
IDCS Password Enter the password for the PaaS username.
Start and Complete the Migration

Once scheduled, you can start the migration and execute the configuration. The
Application Migration Service creates a new Oracle Integration Generation 2 instance
in Oracle Cloud Infrastructure into which your Oracle Integration Cloud Service or
Oracle Process Cloud Service design-time metadata is imported.
3-13
Chapter 3
Integration
1. Review your configuration details, then click Save or click Save and Run to run
the migration now. This starts the migration to create a new Oracle Integration
Generation 2 instance. During this process, the Oracle Integration Cloud Service
(or Oracle Process Cloud Service, if you were migrating that service) design-time
metadata of the application is exported and imported into the new instance.
2. Follow the progress of migration in the Percent Complete column.
3. Click Migrate Application to view in-progress details about the entire migration
process, including:
• Creating an archive location in the object storage bucket for the Oracle
Integration Cloud Service or Oracle Process Cloud Service design-time
metadata.
3-14
Chapter 3
Integration
• Exporting the Oracle Integration Cloud Service or Oracle Process Cloud

Service design-time metadata of the application to the archive location.
• Creating a new Oracle Integration Generation 2 instance.
• Importing the Oracle Integration Cloud Service or Oracle Process Cloud
Service design-time metadata archive from the object storage bucket into the
new instance.
• Deleting the archive from the object storage bucket when the import
completes.
4. If successful, Succeeded is displayed in the status column and the following
message is displayed in the banner at the top of the page.
Application "instance_name" migrated successfully
a. Access your new instance by clicking the link immediately below the above
message.
b. See Complete the Post-Migration Tasks for any tasks for your service.
5. If unsuccessful, Failed is displayed in the status column. The logs provide details
about what failed.
3-15
4
Complete the Post-Migration Tasks
After successfully migrating your Oracle Integration Cloud Service and Oracle Process
Cloud Service instances to Oracle Integration Generation 2 on Oracle Cloud
Infrastructure, test your integrations thoroughly, and then perform cleanup and other
optional configuration tasks.
Topics:
• Verify Your Environment and Activate Your Integrations
• Perform Post Import Steps for Processes
• Handle In-Flight Process Instances
• Follow Migration Best Practices for Processes
Verify Your Environment and Activate Your Integrations

After Integrations migration to Oracle Integration is complete, perform the following
post-migration tasks.
1. Verify your integrations (for example, check the connections, lookups, and more).
2. Activate your integrations (if you did not do so automatically during the import
process).
Replace the Filename Business Identifier Tracking Variable Before

Integration Activation
If Oracle Integration Cloud Service has a scheduled integration in which an FTP
Adapter is used and Filename is used as the business identifier tracking variable,
integration activation fails after migration to Oracle Integration.
As a workaround, perform the following steps:
1. Edit the integration.
2. Remove Filename as the business identifier tracking variable.
3. If Filename was the primary business identifier, specify a different tracking
variable.
4. Save and activate the integration.
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.
4-1
Chapter 4
Perform Post Import Steps for Processes
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).
a. 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
b. In the Container Name field, enter the storage bucket name.
c. In the User field, enter your administrator username ([email protected])
d. 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
4-2
Chapter 4
Handle In-Flight Process Instances
integrations and invocations from both Processes and Integrations, as both

support direct interaction with each other from within Oracle Integration.
a. On the Oracle Integration Home page, select Process Applications in the
navigation pane, open an imported application, and select Integrations in the
navigation pane.
b. Select an integration to update, click Edit and update as needed.
c. 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.
d. 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.
Handle In-Flight Process Instances

After import, follow guidelines in transitioning currently running process instances from
Oracle Process Cloud Service to Oracle Integration.
Handling short lived instances and their human tasks
• For a short overlapping period, run the instances in parallel in Oracle Process
Cloud Service and Oracle Integration, then schedule a transition period during
which no new instances are created in Oracle Process Cloud Service.
– Let Oracle Process Cloud Service instances and tasks complete and drain in
the Oracle Process Cloud Service instance, with no new instances created. At
the same time, ensure all new instances and tasks get run on the Oracle
Integration instance. During this transition period, end users must use two
inboxes.
– After the transition period, all process runtime activity ends on Oracle Process
Cloud Service. End users no longer need to use two inboxes.
4-3
Chapter 4
Follow Migration Best Practices for Processes
Handling long lived instances and their human tasks

• For a short overlapping period, run the instances in parallel in Oracle Process
Cloud Service and Oracle Integration, then terminate instances in Oracle Process
Cloud Service and manually recreate them in Oracle Integration.
– Let Oracle Process Cloud Service instances and tasks complete and drain in
the Oracle Process Cloud Service instance, with no new instances created. At
the same time, ensure all new instances and tasks get run on the Oracle
Integration 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 Oracle Process Cloud
Service to terminate instances. Create new instances with the same payload
as in Oracle Process Cloud Service in the Oracle Integration environment. Use
Alter Flow in Oracle Integration to move newly created replicas of the Oracle
Process Cloud Service instances to the correct activity in the Oracle
Integration process. You can automate these actions by programmatically
invoking the Alter Flow option in Oracle Process Cloud Service and Oracle
Integration. 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
4-4
5
Troubleshoot Migration Issues
Review the following topics to learn about troubleshooting issues with migration.
Topics:
• Troubleshoot and Resolve Migration Issues
Troubleshoot and Resolve Migration Issues

Note the following migration errors and troubleshooting actions if using the curl and
postman commands.
5-1
Chapter 5
Error Error Occurrence Scenario Verification Steps

Exporting or importing design- If you are using an Oracle
HTTP/1.1 401 time metadata with a tool such federated user, you must
Unauthorized as postman or curl. preface the storage user with
The required the
oracleidentitycloudserv
information to
ice identity store (for
complete
example,
authentication was not oracleidentitycloudserv
provided ice/storageUser).
curl -k -v -H "Content-
Type: application/
json" -X POST -d '
{"storageInfo":
{"storageUrl":"
https://
region-1.oraclecloud.co
m/v1/
paasdevoic/
cloneRepo","storageUser
":"oracleidentityclouds
ervice/
[email protected]",
"storagePassword":"gene
rated_token"}}' -u
InstanceAdminUser:Insta
nceAdminPassword
https://host/
icsapis/v2/clonepod/
exportArtifacts
Non-Oracle federated users

can also be used. See
Federating with Identity
Providers.
5-2
Chapter 5

Exporting or importing design- Ensure that you specify the -u
<Jan 23, 2020, time metadata with a tool such InstanceAdminUser:Insta
12:46:03,699 PM UTC> as postman or curl. nceAdminPassword
<Warning> command and have the
<oracle.suite.clone> ServiceAdministrator
<BEA-000000> role. For example:
<CloneService running
in Async mode> curl -k -v -H "Content-
Error reading Type: application/
SERVICE_CLONE_KEY json" -X POST -d '
csfKey trying with {"storageInfo":
OIC_SERVICE_CLONE_KEY {"storageUrl":"
access denied https://
("oracle.security.jps.s swiftobjectstorage.us-
ervice.credstore.Creden region-1.oraclecloud.co
tialAccessPermission" m/v1/
"context=SYSTEM,mapName paasdevoic/
=oracle.clone,keyName=S cloneRepo","storageUser
ERVICE_CLONE_KEY" ":"[email protected]"
"read") ,
Error reading csfKey "storagePassword":"gene
used to encrypt json rated_token"}}' -u
data InstanceAdminUser:Insta
java.security.AccessCon nceAdminPassword
trolException: access https://host/ic/api/
denied common/v1/
("oracle.security.jps.s exportServiceInstanceAr
ervice.credstore.Creden chive
tialAccessPermission"
"context=SYSTEM,mapName
=oracle.clone,keyName=S
ERVICE_CLONE_KEY"
"read")
at
java.security.AccessCon
trolContext.checkPermis
sion(AccessControlConte
xt.
java:4
72)
5-3
Chapter 5

Exporting design-time Paste your payload into a
Note: Unnecessary use metadata to an Oracle validator to verify that the
of -X or --request, Storage Cloud Service JSON payload is correct
POST is already instance. For example: before exporting (for example:
https://
inferred. jsonformatter.curiousconcept.c
* Trying curl -k -v -H "Content-
om).
IP_Address... Type:application/json"
* TCP_NODELAY set -X POST -d
* Connected to icsdevx- '{"storageInfo":
xxxxxxx.integration.emx {"storageUrl":"https://
.oraclecloud.com swiftobjectstorage.uk-
(IP_Address) port 443 london-1.oraclecloud.co
(#0) m
* ALPN, offering h2 /v1/ljk1mltckxeg/
* ALPN, offering http/ bucket-
1.1 ICSToOICMigrationTest",
* TLSv1.3 (OUT), TLS "storageUser":"admin",
handshake, Client "storagePassword":"pass
hello (1): word"}}' -u
* TLSv1.3 (IN), TLS firstname.lastname@emai
handshake, Server l.com:PASSWORD!
hello (2): https://
* TLSv1.2 (IN), TLS instance_name.integrati
handshake, Certificate on.em3.oraclecloud.com/
(11): icsapis/v2/clonepod/
* TLSv1.2 (IN), TLS exportArtifacts
handshake, Server key
exchange (12):
* TLSv1.2 (IN), TLS
handshake, Server
finished (14):
* TLSv1.2 (OUT), TLS
handshake, Client key
exchange (16):
change cipher, Change
cipher spec (1):
handshake, Finished
(20):
* TLSv1.2 (IN), TLS
handshake, Finished
(20):
* SSL connection using
TLSv1.2 / ECDHE-RSA-
AES128-GCM-SHA256
* ALPN, server did not
agree to a protocol
* Server certificate:
* subject: C=US;
ST=California;
5-4
Chapter 5
L=Redwood City;
O=Oracle Corporation;
OU=Cloud Network
Operations;
CN=*.integration.emx.or
aclecloud.com
* start date: Aug 20
00:00:00 2018 GMT
* expire date: Feb 18
12:00:00 2020 GMT
* issuer: C=US;
O=DigiCert Inc;
CN=DigiCert SHA2
Secure Server CA
* SSL certificate
verify result: unable
to get local issuer
certificate (20),
continuing anyway.
* Server auth using
Basic with user
'[email protected]
m'
> POST /icsapis/v2/
clonepod/
exportArtifacts HTTP/
1.1
> Host: icsdevx-
xxxxxxx.integration.emx
.oraclecloud.com
> Authorization: Basic
dmlja2llLmNoYWxsaXNAY2F
wZ2VtaW5pLmNvbTpBdXNzeT
IwMjAtUk1KIQ==
> User-Agent: curl/
7.67.0
> Accept: */*
> Content-
Type:application/json
> Content-Length: 185
>
* upload completely
sent off: 185 out of
185 bytes
* Mark bundle as not
supporting multiuse
< HTTP/1.1 400 Bad
Request
< Date: Mon, 06 Jan
2020 15:29:56 GMT
5-5
Chapter 5
< Server: Oracle-

Application-Server-11g
< Content-Length: 0
< X-ORACLE-DMS-ECID:
005ardKsdLz6qIbLlIt1iZ0
005OG0000WQ
< Set-Cookie:
iscs_auth=LyZ7ehU2hYkdG
J4twSktcP1MloYQU7zIJ7uR
E4dTQwaU7xdGBv6I!-
176121991;
path=/; HttpOnly
< Connection: close
< Content-Type: text/
plain
< Content-Language: en
<
* Closing connection 0
alert, close notify
(256):
5-6
Chapter 5

Exporting design-time Use an Oracle Cloud
{"message":"Unable to metadata to the storage Infrastructure object storage
export the package container, some security files bucket. Classic Storage is not
error: Unexpected were downloaded to the supported. See Step 3: Create
storage container, but export an Object Storage Bucket and
character encountered Construct the Storage URL (If
failed later.
(lex state 13): Not Using the Application
'\"'","status":"FAILED" Migration Service).
}
The following issue appears in

the AdminServer Diagnostic
log.
[oracle.ics.common.stor
age] [tid: pool-3988-
thread-1] [userId:
[email protected]]
[ecid:
005at1bsSGe4yk4_rT8DyY0
004BH000bMq,0:3:11]
[APP:
icswebapp] Unable to
connect to OCI
Autonomous Storage
[https://Storage-
edtc.storage.oracleclou
d.com/v1/Storage-
d82c38bb83b9469583e0f8
5ff6ebde97/abctest123]
due to [Invalid
storage container
[https://Storage-
edtc.storage.oracleclou
d.com/v1/Storage-
d82c38bb83b9469583e0f8
5ff6ebde97/abctest123]
provided. Please use a
valid OCI storage. For
example
: [[
https://
ashburn-1.oraclecloud.c
om/v1/{namespace}/
{bucket}/]
5-7
Chapter 5

Exporting design-time Use an Oracle Cloud
HTTP/1.1 409 Conflict metadata. Infrastructure object storage
JSESSIONID=vOcYMt6ElFcs bucket. Classic Storage is not
YfM1PfqLaqnWzqZgayrUxNo supported. See Step 3: Create
an Object Storage Bucket and
2UzdIAtOHDi29hgSi! Construct the Storage URL (If
1807206143; Not Using the Application
path=/; HttpOnly Migration Service).
< Set-Cookie:
_WL_AUTHCOOKIE_JSESSION
ID=q73LlAtuQ8uJOMCbK0MK
; path=/;
secure; HttpOnly
< Access-Control-Allow-
Methods: GET, POST,
DELETE, PUT, OPTIONS
< X-ORACLE-DMS-ECID:
cc73d0a0-6f91-4f43-
be43-297ce161f691-00162
6c3
< Access-Control-Allow-
Origin: *
< X-XSS-Protection: 1;
mode=block
< X-Content-Type-
Options: nosniff
< Strict-Transport-
Security: max-
age=31536000;
includeSubdomains;
<
* Connection #0 to
host prod-1ics-
vaabc.usgov-
central-1.oraclecloud.c
om
left intact
* Closing connection #0
Error connecting to
Cloud Storage URL
https://storage-
vaabc.console.oracleclo
ud.com/v1/dev2ics/
cloneRepo :
Verify URL and
credentials are
correct[opc@dev-2ics-
wls-1 ~]$
5-8
A
Alternate Migration Options
Instead of using the Application Migration Service to migrate Oracle Integration Cloud
Service and Oracle Process Cloud Service design-time metadata (which is
recommended), you can use alternate migration methods.
Note:
See Step 1: Create a Cloud Storage Compartment or Use an Existing
Compartment through Step 3: Create an Object Storage Bucket and
Construct the Storage URL (If Not Using the Application Migration Service)
for tasks to perform before using these alternate migration methods.
Topics:
• Create and Validate Oracle Integration Instances
• Migrate Oracle Integration Cloud Service Design-Time Metadata into Oracle
Integration
• Migrate Oracle Process Cloud Service Design-Time Metadata into Oracle
Integration
Create and Validate Oracle Integration Instances

If you do not use the Application Migration Service, you must manually create new
Oracle Integration instances. Once creation and validation are complete, you can
migrate your Oracle Integration Cloud Service and Oracle Process Cloud Service
instances to Oracle Integration.
Perform the following options:
• Create Oracle Integration instances (development, test, and production). See
Creating an Oracle Integration Instance in Provisioning and Administering Oracle
Integration on Oracle Cloud Infrastructure.
• Validate development, test, and production instance setup.
Migrate Oracle Integration Cloud Service Design-Time

Metadata into Oracle Integration
You can export your Oracle Integration Cloud Service design-time metadata as an
archive and import that archive into Oracle Integration. For activated integrations in
Oracle Integration Cloud Service, you do not need to manually configure connection
endpoints and passwords and then activate the exported integrations in Oracle
Integration. Integration activations can occur automatically.
• Export the Oracle Integration Cloud Service Design-Time Metadata
A-1
Appendix A
Migrate Oracle Integration Cloud Service Design-Time Metadata into Oracle Integration
• Import Design-Time Metadata into Oracle Integration

• Check the Design-Time Metadata Import Status
Export the Oracle Integration Cloud Service Design-Time Metadata

You must export the Oracle Integration Cloud Service design-time metadata.
1. For the Oracle Integration Cloud Service instance to export to Oracle Integration,
invoke the REST API. This action asynchronously creates an archive that includes
the design-time metadata.
Headers
Authorization : Basic
Content-Type : application/json
payload
{
"storageInfo": {
"storageUrl": "https://swiftobjectstorage.us-
region-1.oraclecloud.com/v1/
paasdevoic/cloneRepo",
}
}
For example, use a postman or curl (as shown below) command to export all
Oracle Integration Cloud Service design-time metadata to an Oracle Storage
Cloud Service instance that you specify:
curl -k -v -H "Content-Type: application/json" -X POST -d '

{"storageInfo":{"storageUrl":" https://swiftobjectstorage.us-
region-1.oraclecloud.com/v1/
paasdevoic/cloneRepo","storageUser":"[email protected]",
"storagePassword":"generated_token"}}' -u
InstanceAdminUser:InstanceAdminPassword
https://host/icsapis/v2/clonepod/exportArtifacts
where:
• storageInfo: Is the URL of the storage container.
• storageUser: Is the storage user name. If you are using an Oracle federated
user, you must preface the storage user with the
oracleidentitycloudservice identity store (for example,
oracleidentitycloudservice/storageUser). Non-Oracle federated users can
also be used. See Federating with Identity Providers.
• storagePassword: Is the storage password.
Possible sample output from this command is as follows:
{
"archiveFilename": "archive_Local_Suite_Instance-d1e4295f-e17a-498a-
a96e-44dcb417dfb4.zip",
A-2
Appendix A
"jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4",
"location": "https://swiftobjectstorage.us-region-1.oraclecloud.com/v1/
paasdevoic/cloneRepo",
"status": "Starting"
2. Check the status of the export operation using a postman or curl (as shown
below) command:
curl -k -v -X GET -u InstanceAdminUser:InstanceAdminPassword https://

host/icsapis/v2/clonepod/exportStatus
{
"status": "COMPLETED"
}
The archive is created in the Oracle Storage Cloud Service instance of Oracle
Integration.
3. If the status is completed, you are now ready to import the archive.
Import Design-Time Metadata into Oracle Integration

When imported into Oracle Integration, the archive is referenced in the payload.
{
"archiveFile": "archive_file_name",
"importActivateMode": "ImportActivate",
// options are "ImportOnly" || "ActivateOnly" || "ImportActivate"
"storageInfo": { // storageUrl points to the storage container
"storageUrl":"https://swiftobjectstorage.us-region-1.oraclecloud.com/v1/
paasdevoic/
cloneRepo",
}
}
1. To import the archive, go to the Oracle Integration instance and invoke the REST
API. This action retrieves the archive from the Oracle Storage Cloud Service
instance where the archive was created.
Headers
Authorization : Basic
Content-Type : application/json
payload
{
"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-
e9b9e8374b68.zip
",
"importActivateMode": "ImportActivate",
A-3
Appendix A
// options are "ImportOnly" || "ActivateOnly" || "ImportActivate"

"storageInfo": {
"storageUrl":"https://swiftobjectstorage.us-
region-1.oraclecloud.com/
v1/paasdevoic/cloneRepo",
}
}
For example, use a postman or curl (as shown below) command to import the
archive of design time objects into Oracle Integration. You can set
importActivateMode to the following values:
• ImportOnly: Imports, but does not activate, integrations.
• ActivateOnly: Activates previously imported integrations. This enables you to
update connection parameters before activating integrations.
• ImportActivate: Imports and activates integrations.
curl -k -v -H "Content-Type: application/json" -X POST -d

'{"archiveFile":
"archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-
e9b9e8374b68.zip",
"importActivateMode": "ImportOnly", "storageInfo":
{ "storageUrl":"https://
swiftobjectstorage.us-region-1.oraclecloud.com/v1/paasdevoic/
cloneRepo","storageUser"
:"[email protected]", "storagePassword":"generated_token"}}' -u
InstanceAdminUser:InstanceAdminPassword https://host/ic/api/common/v1/
importServiceInstanceArchive
Note:
If you are using an Oracle federated user, you must preface the storage
user with the oracleidentitycloudservice identity store (for example,
oracleidentitycloudservice/storageUser). Non-Oracle federated
users can also be used. See Federating with Identity Providers.
{
"jobId":"554",
"status":"NOT_STARTED"
}
A-4
Appendix A
Migrate Oracle Process Cloud Service Design-Time Metadata into Oracle Integration
Check the Design-Time Metadata Import Status

Verify the design-time metadata import status after completing the import task.
1. Check the status of the import operation using a postman or curl (as shown
below) command:
curl -k -v -X GET -u InstanceAdminUser:InstanceAdminPassword https://

host/ic/api/common/v1/
importServiceInstanceArchive/554
Possible sample output from this command is as follows. Other potential output
includes RUNNING , COMPLETED, and FAILED.
{
"jobId":"5108",
"overallStatus":"RUNNING",
"componentStatus":[
{
"component":"Integration",
"status":"RUNNING"
}
]
}
{
"jobId":"5108",
"overall Status":"COMPLETED",
"componentStatus":[
{
"component":"Integration",
"status":"COMPLETED",
"percentage":100
}
]
}
2. Log in to your Oracle Integration instance.

3. Browse the pages and note that the design-time metadata you exported from
Oracle Integration Cloud Service (for example, integrations, connections, lookups,
and more) is now visible.
Migrate Oracle Process Cloud Service Design-Time

Metadata into Oracle Integration
As an administrator, you can import your Oracle Process Cloud Service design-time
metadata (process applications and decision models) into Oracle Integration. The
import tool provides migration flexibility: choose to migrate the entire instance, a
selected space, or individual items.
• Import Oracle Process Cloud Service Design-Time Metadata
A-5
Appendix A
• Import Using the Import Command Line Utility
Import Oracle Process Cloud Service Design-Time Metadata

Use the Process import tool to automatically move Process and decision design-time
metadata from one instance to another. The tool moves process applications and
active decision models from a selected source (an Oracle Process Cloud Service or
Oracle Integration instance) to a selected Oracle Integration destination, and activates
the decision models.
Note:
Run the import tool once only for a specified scope. (Running the tool
multiple times for a scope can cause unpredictable results.) Avoid refreshing
or closing the tool during the import.
1. On the Oracle Integration Home page, click Processes in the navigation pane.
2. Click Settings in the navigation pane, then Import from the top options on the
Administration page.
3. On the Import Administration page, specify a source for the import.
a. In the Identify the instance to import from fields, specify whether to import
from an Oracle Process Cloud Service instance or another Oracle Integration
instance.
b. In the Host Name field, enter the host, using the format https://host:port.
c. Enter a user name and password to sign in to the instance as an
administrator.
4. Identify a destination for the import.
• To import to your current instance, skip the Import to the current Oracle
Integration instance field.
• To import to another Oracle Integration instance than your current instance,
click Edit and complete the host, user name, and password fields for the
instance you want to import to.
• To select importing to the current instance, click Reset.
5. In the Scope field, identify what you want to import.
• Choose Entire Instance to import all process applications and decision
models from all spaces located on the instance.
• Choose Space to import a selected source only. Select the space in the
Source Space field that displays.
• Choose Process Application or Decision Model to import a selected
application or decision model only. In the additional fields that display, select
the source space, process application or decision model to import, and the
destination space.
6. Click Import.
7. Review the import log.
A-6
Appendix A
Note:
You MUST check the logs and make sure there are no errors before
proceeding with post migration steps.
Click Download Import Log in the import dialog to download a zip file containing
the import log. It lists any errors that might have occurred along with a summary of
the number of spaces or items (process applications or decision models) imported.
8. In Oracle Integration, change space settings as needed.
Return to the design-time Administration screen, and share the space(s) you
migrated to Oracle Integration and change their permissions.
Import Using the Import Command Line Utility

Optionally use an import command line to move Process and decision design-time
metadata from one instance to another instead of the user interface. (The user
interface tool is recommended.)
The utility moves process applications and active decision models from a selected
source (an Oracle Process Cloud Service or Oracle Integration instance) to a Oracle
Integration destination, and activates decision models.
Note:
Run the import utility once only for a specified scope. (Running the utility
multiple times for a scope can cause unpredictable results.)
Note:
The import utility requires Java version 8 or later. In addition, both the source
and target instances must return a ping response.
1. On the Oracle Integration Home page, click Processes in the navigation pane.
2. Click Settings in the navigation pane, then Import on the Administration page.
3. Click the Download Utility button and save it to a selected location.
4. Sign in to the Oracle Process Cloud Service (source system) and Oracle
Integration (target) environments.
5. Run the utility from the command line. Use arguments to import an entire Oracle
Process Cloud Service instance, one or more of its spaces, or one or more
process applications or decision models.
Format
$java -jar ImportTool.jar srcType=PCS srcHost=http://host:port
srcUser=user oicHost=http://host:port oicUser=user scope=scope
Example: Import the entire Oracle Process Cloud Service instance
A-7
Appendix A
$java -jar ImportTool.jar srcType=PCS srcHost=http://

abc01xyz.example.com:7001 srcUser=user1 oicHost=http://
def02uvw.example.com:7001 oicUser=user1 scope=SPACE
srcSpace="123456789"
Example: Import process applications (delimit items by pipe line)
$java -jar ImportTool.jar srcType=PCS srcHost=http://
abc01xyz.example.com:7001 srcUser=user1 oicHost=http://
def02uvw.example.com:7001 oicUser=user1 scope=PROJECT
srcSpace="132457689” srcProject="Loan Application|Travel Application"
oicSpace=”123456789”
6. When prompted by the utility, enter the source system password, then the target
system password.
7. Review the import log.
Note:
You MUST check the logs and make sure there are no errors before
proceeding with post migration steps.
A zip file containing the import log is created in the SRC_TO_OIC folder. It lists
any errors that might have occurred along with a summary of the number of
spaces or items (process applications or decision models) imported.
8. In Oracle Integration, change space settings as needed.
Return to the design-time Administration screen, and share the space(s) you
migrated to Oracle Integration and change their permissions.
A-8

Oracle Intg2

Uploaded by

Copyright:

Available Formats

Oracle Intg2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Intg2

Uploaded by

Copyright:

Available Formats

Oracle® Cloud

Migrating Oracle Integration Cloud Service

Copyright © 2019, 2020, Oracle and/or its affiliates.

Primary Author: Oracle Corporation

1 Learn About Migrating to Oracle Cloud Infrastructure

2 Prepare to Migrate Oracle Integration Cloud Service and Oracle

4 Complete the Post-Migration Tasks

5 Troubleshoot Migration Issues

A Alternate Migration Options

Access to Oracle Support

Why Migrate to Oracle Cloud Infrastructure

Key Feature Benefits of Oracle Integration on Oracle Cloud

About the Migration Scope

Integrations Migration Scope

• User-defined credentials. Note the following details:

Integrations Migration Restrictions

What is Not Migrated

Feature Differences Between Oracle Integration Cloud Service and Oracle

Processes Migration Scope

Processes Migration Restrictions

– Integrations created in Oracle Integration Cloud Service and called in

About Oracle Cloud Infrastructure

About the Migration Task Flow and Tooling

Plan Your Migration

Size Oracle Integration Instances

What's NOT counted?

Enable Oracle Integration Generation 2 Entitlement

Enable Access to the Application Migration Service

Understand Best Practices for Migrating the Connectivity Agent

1. If using the Application Migration Service:

• Create and complete a migration of Oracle Integration Cloud Service. See

• If you have an Oracle Integration Cloud Service instance and an Oracle

Migrate Users and Roles

Step 1: Create a Cloud Storage Compartment or Use an

1. Log in to the Oracle Cloud Infrastructure Console as the Administrator user.

Step 2: Create a User and Group and Add Policies

11. Click the group. Its details are displayed.

12. Click Add User to Group.

14. Return to the navigation menu.

15. Under Governance and Administration, go to Identity, then click Policies.

16. Select the compartment you previously created.

17. Click Create Policy.

19. Leave KEEP POLICY CURRENT as the Policy Versioning selection.

Migration Tool Statements

Step 3: Create an Object Storage Bucket and Construct the

• If using the Application Migration Service, skip this section.

3. Click Compute to access the Oracle Cloud Infrastructure page.

4. In the upper right corner, click .

9. In the Bucket Name field, enter a name.

11. Click Create Bucket.

The new bucket is displayed in the list.

13. In the upper left corner of the page, click .

18. Provide a token description and click .

Step Description Example

Step Description Example

Step 4: Migrate Oracle Integration Cloud Service and Oracle

1. Sign in to the One Console of Oracle Cloud Infrastructure.

7. Enter the following details, then click Create.

5. View migration creation in the Percent Complete column.

Configure the Migration Target Instance