Oracle® Cloud

Administering Oracle Integration

E96094-45
August 2021
Oracle Cloud Administering Oracle Integration,

E96094-45

Copyright © 2017, 2021, 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 viii
Documentation Accessibility viii
Diversity and Inclusion ix
Related Resources ix
Conventions ix

1 Welcome to Oracle Integration

Learn About Oracle Integration 1-1
Explore All You Can Do with Oracle Integration 1-1
Assign Roles to Control Access 1-3
Oracle Integration Editions 1-3
Browse Oracle Help Center for Tutorials, Videos, and More 1-4

2 Grant Access and Manage Security

Oracle Integration Roles and Privileges 2-1
Oracle Integration Roles 2-1
WebLogic Server Roles for Oracle Integration 2-3
What Users Can Do in the Navigation Pane by Role 2-4
What Users Can Do on the Home Page by Role 2-4
What Users Can Do in the Monitoring Section by Role 2-5
What Users Can Do in the Settings Section by Role 2-7
What Users Can Do in Processes by Role 2-10
What Users Can Do in Visual Builder by Role 2-11
What Users Can Do in B2B for Oracle Integration by Role 2-12
What Users Can Do in the Integrations Design Section by Role 2-12
What Users Can Do from the Username Main Menu 2-16
Add Users, Groups, and Roles for an Existing Instance 2-17
Add a User 2-17
Assign Roles to a User 2-18
Add a Group 2-18

iii
 Add Users to a Group 2-19
Assign Roles to a Group 2-19
Use the Service Integration Account with No Password Expiration 2-20
Use OAuth Authentication for REST APIs 2-31
Trigger Integrations Using OAuth Authentication 2-31

3 Ready, Set Up, and Go

Accessing Oracle Integration 3-1
Access Oracle Integration from the Oracle Cloud Infrastructure Console 3-1
Access Oracle Integration Classic from the Oracle Cloud Infrastructure Console 3-3
Assign the Correct User Roles to Create an Instance 3-3
Create an Oracle Integration Instance 3-4
About the User Interfaces of the Oracle Integration Oracle Cloud Infrastructure Console 3-4
Explore the Oracle Cloud Infrastructure Console 3-4
Explore the Oracle Cloud Infrastructure Console Activity Page 3-6
Explore the Oracle Cloud Infrastructure Console Instance Overview Page 3-7
Subscribe to Regions Before Upgrading 3-8
Oracle Integration for Oracle SaaS 3-11
Differences between Oracle Integration and Oracle Integration for Oracle SaaS 3-11
Create an Oracle Integration for Oracle SaaS Instance 3-11
View Message Consumption for Oracle Integration for Oracle SaaS 3-11

4 Navigate and Explore

Sign In to Oracle Integration 4-1
What You Can Do on the Home Page 4-1
Navigate Anywhere 4-3
View and Drill Down by Status 4-5
Open Recently Worked on Items 4-6
Start Process Applications as a User 4-6
Start Developing by Feature 4-7
Monitor Health and Drill Down to Troubleshoot 4-7
Use Features Together 4-8
Use Integrations in Process Applications 4-8
Use Process Applications in Integrations 4-8
Use Processes in Visual Builder Applications 4-8

5 Move Design-Time Metadata Between Environments

Configure the Instance Object Storage Bucket 5-1
Export and Import Design-Time Metadata Between Instances 5-2

iv
 Create an Export Job 5-3
Create an Import Job 5-5
Export and Import Integration and Process Design-Time Metadata Between Instances with
the REST APIs 5-7
Migrate Process Design-Time Metadata into Oracle Integration 5-10
Import Process Design-Time Metadata 5-11
Import Using the Import Command Line Utility 5-12

6 Manage Oracle Integration

Scale an Oracle Integration Instance 6-2
Start or Stop an Oracle Integration Instance 6-3
Manage Integrations and Errors 6-4
Manage SSL Certifications 6-4
Manage Integration and Process Instance History 6-4
Configure Settings for Error Logs 6-5
Upload an SSL Certificate 6-6
Monitoring Billable Messages 6-8
About Integrations Usage 6-11
About Process Usage 6-15
Set Data Retention for Runtime Instances 6-17
Delete an Oracle Integration Instance 6-18
Change the BYOL Metering Option of an Existing Instance 6-19

7 Troubleshoot Oracle Integration

Resume Use of a Suspended Oracle Integration for Oracle SaaS Account 7-1

Part I Administer Oracle Integration Classic (User-Managed)

8 Ready, Set Up, Go in Oracle Integration Classic (User-Managed)

Assign the Correct User Roles to Create an Instance 8-1
Provision Oracle Integration Classic (User-Managed) on an IP Network 8-2
Create an Oracle Integration Classic (User-Managed) Instance 8-9
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration
Classic (User-Managed) 8-10
Explore the Oracle Cloud Infrastructure Console 8-10
Explore the Oracle Cloud Infrastructure Console Instance Overview Page 8-12
Explore the Oracle Cloud Infrastructure Console Activity Page 8-17
Explore the Oracle Cloud Infrastructure Console SSH Access Page 8-19

v
 Explore the IP Reservations Page 8-20
Support the Minimum Version of Oracle Integration Classic (User-Managed) 8-20

9 Manage Oracle Integration Classic (User-Managed)

Unsupported Tasks 9-2
Patch and Upgrade Oracle Integration Classic (User-Managed) 9-3
About Patching an Oracle Integration Classic (User-Managed) Instance 9-3
Typical Workflow for Patching an Oracle Integration Classic (User-Managed) Instance 9-4
Quick Tour of the Patching Page 9-4
View Details About the Available Patches 9-5
Perform Prechecks Before Applying a Patch 9-5
Complete Prerequisites Before Applying a Patch 9-6
Apply a Patch 9-10
Stop and Start Oracle Integration Classic (User-Managed) Instances and Nodes 9-11
About Stopping and Starting Instances and Nodes 9-11
Stop and Start Your Instance 9-12
Stop and Start the Nodes in Your Instance 9-12
Scale an Oracle Integration Classic (User-Managed) Instance 9-13
About Scaling Your Instance 9-13
Overview of Scaling Tasks for Your Instance 9-14
Scale Out an Oracle Integration Classic (User-Managed) Instance 9-15
Scale In an Oracle Integration Classic (User-Managed) Instance 9-15
Check Status of Scaling Requests 9-16
Manage Database Issues 9-17
Update the Database Schema Password in Oracle Integration Classic 9-17
Change the Database Schema Password 9-17
Managing Alerts 9-18
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance 9-18
About Backing Up and Restoring an Oracle Integration Classic (User-Managed)
Instance 9-19
Typical Workflow for Backing Up and Restoring an Oracle Integration Classic (User-
Managed) Instance 9-21
Quick Tour of the Backup Page 9-22
Configure an Automatic Backup 9-25
Initiate an On-Demand Backup 9-27
Disable or Enable Backups 9-28
Restore a Backup 9-29
Delete a Backup 9-30
Manage Integrations and Errors 9-31
Manage SSL Certifications 9-31
Manage Instance History 9-32

vi
 Configure Settings for Error Logs 9-32
Use SSH to Sign In to Oracle Integration Classic (User-Managed) 9-33
Diagnose Oracle Integration Classic (User-Managed) Problems 9-33
Access and View Diagnostic Logs 9-34
Use WebLogic Server Logs 9-34
Use Java Flight Recorder Performance Profiles 9-34
Use Oracle Integration Report Incidents 9-36
Export Suite-Generated Artifacts 9-36
Collect Database Statistics 9-36
View System Health 9-36
Delete an Oracle Integration Classic (User-Managed) Instance 9-37

10 Troubleshoot Oracle Integration Classic (User-Managed)

Provision an Instance Without the Correct User Roles Causes Failure 10-1
Provision Oracle Integration Classic (User-Managed) 10-2
504 Gateway Timeout Error May Require Editing an Instance's Load Balancer Access
Rules Manually to Add a New IP Address 10-2
Troubleshoot cURL Command Issues When Configuring an IP Network 10-3
Database Backups May Use Up Disk Space and Cause Oracle Integration Classic Servers
to Shut Down 10-3
Troubleshoot Backup and Restore Issues 10-3
Troubleshoot Patching Issues 10-4
Oracle Integration Classic (User-Managed) Fails to Connect to the Database Instance 10-6

vii
 Preface

Preface
Administering Oracle Integration describes how to use Oracle Integration to integrate
your applications and processes.

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
• Diversity and Inclusion
• Related Resources
• Conventions

Audience
Administering Oracle Integration is intended for users who want to create, activate,
and monitor integrations and processes.

Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at [Link]
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 [Link]
lookup?ctx=acc&id=info or visit [Link]
ctx=acc&id=trs if you are hearing impaired.

viii
 Preface

Diversity and Inclusion

Oracle is fully committed to diversity and inclusion. Oracle respects and values having a
diverse workforce that increases thought leadership and innovation. As part of our initiative to
build a more inclusive culture that positively impacts our employees, customers, and
partners, we are working to remove insensitive terms from our products and documentation.
We are also mindful of the necessity to maintain compatibility with our customers' existing
technologies and the need to ensure continuity of service as Oracle's offerings and industry
standards evolve. Because of these technical constraints, our effort to remove insensitive
terms is ongoing and will take time and external cooperation.

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 [Link]

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.

ix
1
Welcome to Oracle Integration
Oracle Integration combines business process automation, application integration, web and
mobile application development, and integrated analytics into one unified product.

Topics:
• Learn About Oracle Integration
• Explore All You Can Do with Oracle Integration
• Assign Roles to Control Access
• Oracle Integration Editions
• Browse Oracle Help Center for Tutorials, Videos, and More

Learn About Oracle Integration

Oracle Integration is a unified platform where you can integrate your applications, automate
processes, and create applications.
Specifically, with Oracle Integration, you can:
• Use integrations to design, monitor, and manage connections between your applications
• Create process applications to automate and manage your business work flows
• Build custom web and mobile applications
Critical business processes, such as those related to human capital management (HCM),
customer experience (CX), and enterprise resource planning (ERP), are frequently slow and
inflexible. For example, a multi-step process such as Lead to Opportunity to Quote to Order
can involve four or more applications and require human exception management at every
step of the process. In this scenario, the lack of integration between departments as well as
the delays caused by human-based problem resolution can result in lost revenue, frustrated
customers, and high costs.
Oracle Integration changes all that. It empowers you to:
• Establish connectivity between the many applications and people that are part of the
entire business process life cycle.
• Assemble existing technologies into new business services to better align with the
changing pace of new business demands.
• Deliver new business innovations faster by rapidly connecting diverse applications and
key business roles.

Explore All You Can Do with Oracle Integration

With Oracle Integration, you have the power to automate business processes, connect your
cloud and on-premises applications, build great web and mobile applications, collect
advanced metrics about your business, and get real-time analytics. The feature set for your

1-1
 Chapter 1
Explore All You Can Do with Oracle Integration

Oracle Integration depends on two factors: which edition you’re using (Enterprise or
Standard) and who’s managing your cloud environment (you or Oracle). Let’s explore
all the features that may be available to you.

Processes: Automate Business Processes

Use Processes to rapidly design, automate, and manage business processes in the
cloud.
You begin by creating a process application from scratch, by using a QuickStart App,
or by importing a file. Next, you model your process flow, including the requests,
approvals, decision paths, and roles for each task. Depending on the business
process, you may need to create web forms, add decision models, and interact with
web services to send and receive data.
At any point when you’re designing your process application, you can play your
process step-by-step to test each possible scenario. When you’re ready, activate the
process application to make it available, and assign roles to grant users access to your
application.

Integrations: Connect Applications

Use Integrations to connect your applications into a continuous business flow. You can
quickly develop and activate integrations between both your applications that live in
the cloud and your applications that still live on premises.
• Identify the applications that you want to integrate, and configure the connection
details for each application. You can also select from our portfolio of 50+ pre-built
adapters to connect with Oracle and third-party applications, such as Oracle Sales
Cloud, Oracle Service Cloud, Google Calendar, Salesforce, and SAP.
• Use browser-based visual tools to create integrations, and then map the data
between your applications. Mappings can range from simple data assignments to
complex expressions.
• Activate your integration when you’re ready.
• Monitor the dashboard to check the status and processing statistics for an
integration. The dashboard also measures and tracks the performance of your
transactions by capturing and reporting key information.

Visual Builder: Develop Applications

With Visual Builder, you can build great web and mobile applications yourself. There is
no coding, no setup, and no IT resources required.
Just use the visual drag-and-drop designer and the full palette of user interface
components to build applications as simple or as intricate as you need. The built-in
page templates implement best practices in design. In addition, the user interface
adjusts to the native look and feel of your iOS or Android operating system so building
applications optimized for mobile devices is easy as well.
Visual Builder provides all the necessary tools for building and publishing a modern
web application as well as providing the infrastructure for securing access to your
application, data, and the Oracle Cloud services that your application consumes.

1-2
 Chapter 1
Assign Roles to Control Access

Assign Roles to Control Access

Oracle Integration is designed to be used by any of the people involved in an end-to-end
business process regardless of their skill level or job title. You control access to Oracle
Integration by assigning roles to each user.
A role includes privileges that allow users to perform various tasks and to access certain
features. Users can hold multiple roles depending on their responsibilities. See Oracle
Integration Roles and Privileges.

Oracle Integration Editions

Oracle Integration is available in two editions: Standard and Enterprise.
Either edition gives you the power to integrate your Software as a Service (SaaS)
applications and your on‑premises applications. Enterprise edition enables you to also
design, automate, and manage your business processes in the cloud.
Regardless of which edition you choose, Oracle handles cloud and database management,
backup, restore, and other administrative tasks for you.
Here’s a side-by-side comparison of what’s licensed in each edition.

1-3
 Chapter 1
Browse Oracle Help Center for Tutorials, Videos, and More

Browse Oracle Help Center for Tutorials, Videos, and More

There are several other resources that you can use to learn about Oracle Integration:
• A series of tutorials that will guide you through hands-on exercises using Oracle
Integration is available at Oracle Integration Tutorials.
• A growing library of videos for Oracle Integration is available at Oracle Integration
Videos.
• The complete documentation set for Oracle Integration is available on the Oracle
Help Center. All getting started, using, and administering guides are available in
HTML and PDF formats. Documentation for REST APIs and JavaScripts is
available in HTML format.

1-4
2
Grant Access and Manage Security
Add users and grant roles to enable them to access, administer, and use feature sets of
Oracle Integration.

Topics:
• Oracle Integration Roles and Privileges
• Add Users, Groups, and Roles for an Existing Instance
• Use the Service Integration Account with No Password Expiration
• Use OAuth Authentication for REST APIs
• Trigger Integrations Using OAuth Authentication

Oracle Integration Roles and Privileges

Roles define the privileges available to users and the tasks that they can perform. You can
assign predefined roles to users to allow them to work with feature sets of Oracle Integration.

• Oracle Integration Roles

• WebLogic Server Roles for Oracle Integration (applies only to Oracle Integration Classic
(user-managed)
• What Users Can Do in the Navigation Pane by Role
• What Users Can Do on the Home Page by Role
• What Users Can Do in the Integrations Design Section by Role
• What Users Can Do in the Monitoring Section by Role
• What Users Can Do in the Settings Section by Role
• What Users Can Do in Processes by Role
• What Users Can Do in Visual Builder by Role
• What Users Can Do in B2B for Oracle Integration by Role

Oracle Integration Roles

Oracle Integration predefined roles govern access to various Oracle Integration features.
You can assign one or more of these predefined roles to Oracle Integration users and groups:
ServiceAdministrator, ServiceDeveloper, ServiceMonitor, ServiceDeployer, ServiceUser,
ServiceInvoker, and ServiceViewer. The following table lists the predefined roles available in
Oracle Integration, and the general tasks that users assigned the roles can perform.

2-1
 Chapter 2
Oracle Integration Roles and Privileges

Oracle Integration Description

ServiceAdministrator A user with the ServiceAdministrator role is a super user who can
manage and administer the features provisioned in an Oracle
Integration instance.
ServiceDeveloper A user with the ServiceDeveloper role can develop the artifacts
specific to the features provisioned in an Oracle Integration
instance. For example, in Integrations the user can create
integrations, and in Processes the user can create process
applications and decision models.
ServiceMonitor A user with the ServiceMonitor role can monitor the features
provisioned in an Oracle Integration instance. For example, the user
can view instances and metrics, find out response times, and track
whether instance creation completed successfully or failed.
This role provides privileges for users with limited knowledge of
Oracle Integration, but with high-level knowledge of monitoring
it. This user role does not grant permissions to change anything.
ServiceDeployer A user with the ServiceDeployer role can publish the artifacts
developed in a feature.
This role is not applicable for the Integrations feature.
ServiceUser A user with the ServiceUser role has privileges to utilize only the
basic functionality of a feature such as access to the staged and
published applications.
For example, in Integrations the user can navigate to resource
pages (such as integrations and connections) and view details, but
can’t edit or modify anything. The user can also run integrations and
start process applications.
ServiceInvoker A user with the ServiceInvoker role can invoke any integration flow
in an Oracle Integration instance that is exposed through SOAP/
REST APIs or a scheduled integration. See Run an Integration
Flow. A user with ServiceInvoker role cannot:
• Navigate to the Oracle Integration user interface or perform any
administrative actions in the user interface.
• Invoke any of the documented Oracle Integration REST APIs.
See About the REST APIs.
ServiceViewer A user with the ServiceViewer role can navigate to all Integration
resource pages (for example, integrations, connections, lookups,
libraries, and so on) and view details. The user cannot edit any
resources or navigate to the administrative setting pages.

In Oracle Integration, when you assign a role to a user, the user is granted that role for
all Oracle Integration features provisioned on an instance. For example, when you
assign the ServiceDeveloper role to a user for an instance provisioned with the
Integrations, Processes, and Visual Builder feature set, the user gets developer
permissions on each of these features. Further, each role grants different privileges for
different features to the same user. Depending on the feature the user is accessing,
the user can perform different tasks. For example, a user assigned the
ServiceDeveloper role can develop process applications in Processes, whereas the
same user can design integrations in Integrations. Note that not all Oracle Integration
predefined roles are available in all features. For example, the ServiceMonitor role is
not available in Visual Builder.

2-2
 Chapter 2
Oracle Integration Roles and Privileges

Note:

Applies only to Oracle Integration Classic (user-managed).

If a user is granted access to multiple service instances provisioned in the Oracle
Integration environment, it is a best practice to grant the same role to the user in all
the instances. For example, suppose you have provisioned Integrations and Visual
Builder as two separate instances in your Oracle Integration environment. If you
assign the ServiceAdministrator role to a user in the Integrations instance, then
assign the same role to the user in the Visual Builder instance too.

WebLogic Server Roles for Oracle Integration

Oracle Integration is a PaaS-layered service. There are predefined roles for the PaaS layer
that govern access to WebLogic Server.

Applies only to Oracle Integration Classic (user-managed).

The following table lists the predefined WebLogic Server roles available for Oracle
Integration.

Oracle Integration Description

Administrators A user with the Administrators role can:
• View the server configuration, including the encrypted value of
some encrypted attributes
• Modify the entire server configuration
• Deploy Enterprise Applications and Web application, EJB, Java
EE Connector, and Web Service modules
• Start, resume, and stop servers
Deployers A user with the Deployers role can:
• View the server configuration, including some encrypted
attributes related to deployment activities
• Change startup and shutdown classes, Web applications,
JDBC data pool connections, EJB, Java EE Connector, Web
Service, and WebLogic Tuxedo Connector components. If
applicable, edit deployment descriptors.
• Access deployment operations in the Java EE Deployment
Implementation (JSR-88)
Monitors A user with the Monitors role can:
• View the server configuration, except for encrypted attributes
• Get read-only access to WebLogic Server Administration
Console, WLST, and MBean APIs
Operators A user with the Operators role can:
• View the server configuration, except for encrypted attributes
• Start, resume, and stop servers

2-3
 Chapter 2
Oracle Integration Roles and Privileges

What Users Can Do in the Navigation Pane by Role

The following table lists the options in the Integration navigation pane and indicates
which options you can access based on your assigned role.

Option Service Service Service Service Service Service Service

Administrator Develope Deployer Monitor User Invoker Viewer
r
Welcome Yes Yes Yes Yes Yes No Yes
Home Yes Yes Yes Yes Yes No Yes
My Tasks Yes Yes Yes Yes Yes No Yes
Processes Yes Yes Yes No No No No
Integrations Yes Yes No Yes Yes No Yes
Can’t use Can use Can use
any all all
Monitorin Monitorin Monitorin
g, g options. g and
Designer, Can’t use Designer
or any options.
Settings Designer Can’t use
options. or any
Note: Settings Settings
User can options. options.
click
Integratio
ns, but
receives a
“not
authorize
d”
message.
Visual Builder Yes Yes Yes No No No No
Settings Yes No No No No No No

What Users Can Do on the Home Page by Role

The following table lists the tiles, sections, and buttons on the Oracle Integration Home
page and indicates what you can access based on your assigned role.

Home Page Service Service Service Service Service

Element Administrator Developer Deployer Monitor User
My Tasks Yes Yes Yes Yes Yes
Integrations Yes Yes No Yes No
Connections Yes Yes No Yes No
Visual Applications Yes Yes Yes No No
Recents Yes Yes Yes No No
Actions Yes Yes Yes Yes Yes

2-4
 Chapter 2
Oracle Integration Roles and Privileges

Home Page Service Service Service Service Service

Element Administrator Developer Deployer Monitor User
Processes: Create Yes Yes Yes No No
Applications
Processes: Use Yes Yes Yes No No
Quickstart
Integrations: Create Yes Yes No No No
Connections
Integrations: Create Yes Yes No No No
Integrations
Monitor Current Yes Yes Yes No No
Tasks
Monitor Process Yes Yes Yes No No
Health: Tracking
Monitor Process Yes No No No No
Health: Dashboard
Monitor Integrations Yes Yes No Yes No
Health

What Users Can Do in the Monitoring Section by Role

The following tables list Oracle Integration predefined roles available in the Monitoring
section, and the tasks users granted those roles can perform.
• Usage Metrics
• Integrations > Dashboards
• Integrations > Integrations
• Integrations > Agents
• Integrations > Tracking
• Integrations > Errors

Usage Metrics

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
View Yes No Yes No No No
Export Yes No Yes No No No

Integrations > Dashboards

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
View Activity Yes Yes Yes Yes No Yes
Stream

2-5
 Chapter 2
Oracle Integration Roles and Privileges

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
View Design- Yes Yes Yes Yes No Yes
time Audit
Download Yes Yes Yes Yes No Yes
Diagnostic
Logs
Note: Not
available in
Oracle
Integration
Generation 2
Download Yes Yes Yes Yes No Yes
Incident Logs
Note: Not
available in
Oracle
Integration
Generation 2
View Yes Yes Yes Yes No Yes
Runtime
Health
View System Yes Yes Yes Yes No Yes
Health
View Agent Yes Yes Yes Yes No Yes
Health
View Yes Yes Yes Yes No Yes
Integrations
View Yes Yes Yes Yes No Yes
Scheduling
View Design- Yes Yes Yes Yes No Yes
time Metrics
View the Yes Yes Yes Yes No Yes
Hourly / Daily
History

Integrations > Integrations

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
View Yes Yes Yes Yes No Yes

Integrations > Agents

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
View Yes Yes Yes Yes No Yes

2-6
 Chapter 2
Oracle Integration Roles and Privileges

Integrations > Tracking

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
View Details Yes Yes Yes Yes No Yes
Asserter Yes Yes Yes No No Yes
Recordings
View Yes Yes Yes Yes No Yes
Business
Identifiers
View Activity Yes Yes Yes Yes No Yes
Stream
Download Yes Yes Yes Yes No Yes
Activity
Stream

Integrations > Errors

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
View Yes Yes Yes Yes No Yes
Abort Yes Yes Yes Yes No No
Resubmit Yes Yes No Yes No No

What Users Can Do in the Settings Section by Role

The following tables list Oracle Integration predefined roles available in the Settings section,
and the tasks users granted those roles can perform.
• Import/Export
• Storage
• Certificates
• Integrations > Notifications
• Integrations > Database
• Integrations > Recommendations
• Integrations > API Management
• Integrations > Tracing
• Integrations > Schedule
• Integrations > Log Levels (Not Available in Oracle Integration Generation 2)

2-7
 Chapter 2
Oracle Integration Roles and Privileges

Import/Export

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
Import Yes No No No No No
Export Yes No No No No No
Download Yes No No No No No
Detailed
Report
View Yes No No No No No

Storage

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
View Yes No No No No No
Save Yes No No No No No
Reset Yes No No No No No

Certificates

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
View Yes No No No No No
Upload Yes No No No No No
Update Yes No No No No No
Delete Yes No No No No No

Integrations > Notifications

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
View Yes No No No No No
Revert Yes No No No No No
Save Yes No No No No No
Send Now Yes No No No No No
Reset All Yes No No No No No
Notifications

2-8
 Chapter 2
Oracle Integration Roles and Privileges

Integrations > Database

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
View Yes No No No No No
Revert Yes No No No No No
Save Yes No No No No No
Purge Now Yes No No No No No
Configure Yes No No No No No
database
space
Configure Yes No No No No No
Nightly Purge
Configure Yes No No No No No
Auto Purge

Integrations > Recommendations

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
View Yes No No No No No
Contribute Yes No No No No No
integration
mappings to
Oracle
Recommend
s
Save Yes No No No No No

Integrations > API Management

Table 2-1 API Platform

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
View Yes No No No No No
Save Yes No No No No No
Revert Yes No No No No No
Create Yes No No No No No
Connectivity
with API CS

2-9
 Chapter 2
Oracle Integration Roles and Privileges

Integrations > Tracing

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
View Yes No No No No No
Save Yes No No No No No
Revert Yes No No No No No
Include Yes No No No No No
payload

Integrations > Schedule

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
Save Yes No No No No No

Integrations > Logging (Not Available in Oracle Integration Generation 2)

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
View Yes No No No No No
Save Yes No No No No No
Revert Yes No No No No No
Download Yes No No No No No
Logs

What Users Can Do in Processes by Role

The following table lists the Oracle Integration predefined roles available in Processes,
and the tasks users granted those roles can perform. Note that in Processes, the
ServiceMonitor role and the ServiceUser role have the same privileges. In addition to
these predefined roles, there is a set of roles defined for each process application.
Service administrators are responsible for assigning process-specific roles to users.

Option Actions Service Service Service ServiceMonitor

Administrator Developer Deployer and ServiceUser
My Tasks Access Workspace (runtime), Yes Yes Yes Yes
initiate requests (start
applications), work on your
assigned tasks, and track the
status of processes
My Tasks Monitor dashboards Yes Yes Yes Yes

2-10
 Chapter 2
Oracle Integration Roles and Privileges

Option Actions Service Service Service ServiceMonitor

Administrator Developer Deployer and ServiceUser
Applications Perform all actions to develop and Yes Yes Yes No
manage process applications and
their components, except
restrictions on activating
Applications Activate process applications to a Yes Yes Yes No
test partition
Applications Activate process applications to a Yes No No No
production partition
Spaces View your spaces and the spaces Yes Yes Yes No
shared with you, and create, edit,
share, and delete your spaces
Spaces Administer any space (check Yes No No No
status, control permissions, and
delete)
Management Manage process applications Yes No No No
(activate to production partition,
retire, deactivate, shut down, and
manage web services)
Administration Configure connections to other Yes No No No
(runtime) services, configure process
runtime and logger settings,
schedule archive and purge,
configure UI custom settings,
assign and manage roles specific
to process applications, manage
credentials and certificates, and
view notification logs
Settings Administer any space (check Yes No No No
(design-time) status, control permissions,
delete), administer any process
application (delete, unlock), delete
QuickStart Apps from the gallery,
enable the application player, and
use the Import utility

What Users Can Do in Visual Builder by Role

The following table lists Oracle Integration predefined roles available in Visual Builder, and
the tasks that users granted those roles can perform.

Oracle Integration Role Tasks Users Can Perform in Visual Builder

ServiceAdministrator A user with the ServiceAdministrator role can:
• Use the visual design tool
• Create, manage, and change the owners of applications
• Create associations with other services
• Configure security options for applications in an instance
• Specify error messages for Access Denied pages

2-11
 Chapter 2
Oracle Integration Roles and Privileges

Oracle Integration Role Tasks Users Can Perform in Visual Builder

ServiceDeveloper A user with the ServiceDeveloper role can:
• Use the visual design tool
• Create, manage, secure, and publish web and mobile
applications
• Design pages, work with business objects, build and test
applications
ServiceMonitor The ServiceMonitor role is not applicable in Visual Builder.
ServiceDeployer The ServiceDeployer role is not applicable in Visual Builder.
ServiceUser A user with the role of ServiceUser can only access staged and
published applications. The default permission is enforced only
when the service administrator adjusts security settings for the
entire service instance to restrict all access to runtime applications
to the users granted the ServiceUser role.

What Users Can Do in B2B for Oracle Integration by Role

The following table lists Oracle Integration predefined roles available in B2B for Oracle
Integration and the tasks that users granted those roles can perform.

Note:
The list of tasks that different user roles can perform on B2B integrations
(integrations using the B2B action) are the same as the tasks they can
perform on other integrations. See What Users Can Do in the Integrations
Design Section by Role.

Action Service ServiceDevel ServiceMonit ServiceUser ServiceInvok ServiceViewe

Administrator oper or er r
View B2B Yes Yes No No No No
Documents
Create or Yes Yes No No No No
Modify B2B
Documents
View B2B Yes Yes No No No No
Schemas
Create or Yes Yes No No No No
Modify B2B
Schemas
Generate Yes Yes No No No No
Implementatio
n Guide

What Users Can Do in the Integrations Design Section by Role

The following tables list Oracle Integration predefined roles available in the
Integrations design section, and the tasks users granted those roles can perform.
• Integrations

2-12
 Chapter 2
Oracle Integration Roles and Privileges

• Connections
• Lookups
• Packages
• Agents
• Adapters
• Libraries

Integrations

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
Create Yes Yes No No No No
Create new Yes Yes No No No No
version
View Yes Yes No Yes No Yes
Edit Yes Yes No No No No
Delete Yes Yes No No No No
Activate Yes Yes No No No No
• Enable
tracing
(include
payload)
• Enable
Oracle
Recomm
ends
• Enable
asserter
recordin
g
Reactivation Yes Yes No No No No
after
connection
update
Deactivate Yes Yes No No No No
Clone Yes Yes No No No No
Run Yes Yes No Yes Yes No
Export Yes Yes No Yes No Yes
Import Yes Yes No No No No
Update Yes Yes No No No No
Property
Values
Asserter Yes Yes No No No No
Recordings
Enable Yes Yes No No No No
Asserter
Recordings

2-13
 Chapter 2
Oracle Integration Roles and Privileges

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
Submit Yes Yes No No No No
Asserter
Recordings
Configure Yes Yes No No No No
Assign Yes Yes No No No No
Business
Identifiers
Unlock Yes Yes No No No No
Add Yes Yes No No No No
Schedule
Edit Yes Yes No No No No
Schedule
Delete Yes Yes No No No No
Schedule
Run Yes Yes No Yes No No
Schedule
View Yes Yes No Yes No Yes
Schedule
Runs
Update Yes Yes No Yes No No
Schedule
Parameters
Convert Yes Yes No No No No
scheduled
integration to
app-driven
orchestration
integration
Run or Yes No No No No No
schedule
integrations
on behalf of
another user

Connections

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
Create Yes Yes No No No No
Edit Yes Yes No No No No
Delete Yes Yes No No No No
View Yes Yes No Yes No Yes
Test Yes Yes No No No No
Clone Yes Yes No No No No
Unlock Yes Yes No No No No

2-14
 Chapter 2
Oracle Integration Roles and Privileges

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
Refresh Yes Yes No No No No
Metadata

Lookups

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
Create Yes Yes No No No No
View Yes Yes No Yes No Yes
Edit Yes Yes No No No No
Clone Yes Yes No No No No
Delete Yes Yes No No No No
Export to Yes Yes No Yes No Yes
CSV
Import Yes Yes No No No No

Packages

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
View Yes Yes No Yes No Yes
Create Yes Yes No No No No
(during
integration
creation)
Import Yes Yes No No No No
Export Yes Yes No Yes No No
Update Yes Yes No No No No
(through
integration
update)
Delete Yes Yes No No No No
Configure Yes Yes No No No No

Agents

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
View Yes Yes No Yes No Yes
Edit Agent Yes Yes No No No No
Group

2-15
 Chapter 2
Oracle Integration Roles and Privileges

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
Delete Agent Yes Yes No No No No
Group
Create Agent Yes Yes No No No No
Group
Download Yes Yes No No No No
connectivity
agent

Adapters

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
View Yes Yes No Yes No No
Delete Yes Yes No No No No
Create Yes Yes No No No No
Connection

Libraries

Action Service ServiceDev ServiceMo ServiceUse ServiceInv ServiceVie

Administra eloper nitor r oker wer
tor
View Yes Yes No Yes No Yes
Edit Yes Yes No No No No
Create Yes Yes No No No No
Import Yes Yes No No No No
Delete Yes Yes No No No No
Update Yes Yes No No No No
Export Yes Yes No Yes No Yes

What Users Can Do from the Username Main Menu

The following table lists the Oracle Integration tasks available from the Username
main menu in the upper right corner of the Integrations pages, and the roles users
must be granted to perform those tasks.

2-16
 Chapter 2
Add Users, Groups, and Roles for an Existing Instance

Username Main Menu

Action Service ServiceDev ServiceMoni ServiceUser ServiceInvo ServiceView

Administrat eloper tor ker er
or
Set Time Yes Yes No Yes No Yes
Zone
Preferences
Report Yes Yes No Yes No Yes
Incidents

Add Users, Groups, and Roles for an Existing Instance

You can add users, assign roles to users, add groups, and add users and roles to groups for
an existing instance in Oracle Integration.

Topics:
• Add a User
• Assign Roles to a User
• Add a Group
• Add Users to a Group
• Assign Roles to a Group

Add a User
Add the users who need to use an Oracle Integration instance. You can add these users
before the instance is created.
You can create and manage user accounts only if you are a cloud account administrator, an
identity domain administrator, or have the user administrator role through delegated
administration.
1. Sign in to the Oracle Cloud Infrastructure Console.
2. In the upper left corner, click

, and select Users.

3. Select your instance.

4. Click the Users tab on the User Management page.

5. Click Add.

2-17
 Chapter 2
Add Users, Groups, and Roles for an Existing Instance

6. Enter your first name, last name, email address, and user name. You can also
select to use the email address as the user name.
7. Click Save.
You can now assign roles to the user or add the user to a group.
You also receive an email with a link for activating your account.
8. Follow the instructions in the email to activate your account.

Assign Roles to a User

You can assign roles to users to specify the tasks they can perform in Oracle
Integration. You can assign multiple roles to a user.
To assign roles to users, you must be a cloud account administrator, an identity
domain administrator, or have the user administrator role through delegated
administration. See Oracle Integration Roles and Privileges for a description of the
various predefined roles available in Oracle Integration. You essentially assign a user
to an Oracle Integration instance or provide a user access to an Oracle Integration
instance by performing these steps.
1. In the upper left corner, click

, and select Users.

2. Select your instance.

3. Click the Users tab on the User Management page.

4. Click the user to which to add the role.
5. Click the Roles tab.
6. Add the necessary roles, and click Save.

Add a Group
Instead of assigning roles to each user individually, you can create groups and add
users to groups to make it easier to assign roles. Each time you add a user to a group,
the user automatically gets the roles defined for the group. You can add the group
before an Oracle Integration instance is created.
You can create and manage groups only if you are a cloud account administrator, an
identity domain administrator, or have the user administrator role through delegated
administration. See Add Users to a Group.
1. In the upper left corner, click

, and select Users.

2. Select your instance.

2-18
 Chapter 2
Add Users, Groups, and Roles for an Existing Instance

3. Click the Groups tab on the User Management page.

4. On the Groups page, click Add.
5. On the Add Group page, provide a name and description for your group, and click Finish.
The group is visible in the Groups page. You can now add users to the group.

Add Users to a Group

Add users to a group so that they automatically get the permissions defined for the group.
To add users to a group from the Groups page:
1. In the upper left corner, click

, and select Users.

2. Select your instance.

3. Click the Groups tab on the User Management page.

4. On the Groups page, click the group to which to assign users.
5. On the Group Details page, select the Users tab.
6. Click Add to Group.
7. In the Add to Group dialog, select the users you want to add to the group, then click Add.
The selected users are added to the group. You can now assign roles to all the users in
the group, if required.

Assign Roles to a Group

After you create groups and add users to groups, you can assign roles and provide access to
services and instances to all the members of the group at once.
Note that this action assigns the selected roles to all the users in the group in a batch. You
can’t assign roles individually if you select the group role assignment.
See Oracle Integration Roles and Privileges for a description of the various predefined roles
available in Oracle Integration.
1. In the upper left corner, click

, and select Users.

2-19
 Chapter 2
Use the Service Integration Account with No Password Expiration

2. Select your instance.

3. Click the Groups tab on the User Management page.

4. On the Groups page, click the group to which to assign roles.
5. Click the Roles tab.
6. Optionally, use the Filter by Service box to search for specific services, if
required. By default, the Roles page displays all services in your cloud account. If
you want to assign roles for a specific service and its instances, delete All
Services from the Filter by Service box, then select your service from the list or
enter the service name.
7. From the Show drop-down list, select one of the following:
• Only Services: Lists all services. Select this if you want to assign roles to
group members to be able to provision and administer cloud services in the
Oracle Cloud Infrastructure Console.
• Only Instances: Lists all instances. Select this if you want to give access to
group member for specific instances.
• Both Services and Instances: Lists all services and instances. If you
selected a specific service in the Filter by Service box, it lists that service and
all its instances.
8. In the search result, go to the service or instance for which you want to assign
roles to group members.
9. For your service or instance, click the text box and select the required role from
the drop-down list.
For example, to assign the ServiceUser role for an instance, select Only
Instances from the Show drop-down list. Then in the search result, go to your
instance, click the text box below the instance name and select the ServiceUser
(Service instance user role) role.

Use the Service Integration Account with No Password

Expiration
Oracle Integration provides a service integration account in which the password does
not expire. The service integration account consists of a generic application role
created with specific predefined rules. Use this account when you need to invoke
integrations and require that the account password not expire.

Note:
To avoid expiring credentials, it is recommend that you use the JWT user
assertion grant. See Trigger Integrations with OAuth in Using the REST
Adapter with Oracle Integration.

2-20
 Chapter 2
Use the Service Integration Account with No Password Expiration

User credentials are typically used with the Basic Authentication security policy. Continuous
use of this security policy by clients increases the performance load on the authentication
service (Oracle Identity Cloud Service) because it must keep validating the same credentials
repeatedly. The increased performance load is dependent on two factors.
• Repeated requests to the Oracle Identity Cloud Service server for password
authenticator/asserter for the same basic authentication credentials.
• The Oracle Identity Cloud Service password policy requires accessing the ID store for
each of the requests.
To reduce the performance load caused by repeated requests, you can use the service
integration account without password expiration.
For Basic Authentication, you can use generic credentials: the client ID (that ends with
_BASICAUTH) and the associated client secret. This section describes on how to create these
credentials.

Obtain the PaaS Application Oracle Identity Cloud Service Application ID

1. In the upper left corner, click

, and select Users.

2. Select your instance.

3. On the User Management page, click Identity Console.

4. In the upper left corner, click

.
5. Select Applications.
6. Navigate to the Oracle Integration application.
7. Note the value in the Application ID field (for this example, referred to as $
{OIC_APP_ID}).

Configure the Service Administrator Application

1. Click Add and select Confidential Application to create a confidential application in
Oracle Identity Cloud Service. This task must be performed by an Oracle Identity Cloud
Service administrator.

2-21
 Chapter 2
Use the Service Integration Account with No Password Expiration

The Add Confidential Application wizard is displayed.

2. Configure the confidential application.
a. On the Details page, enter an application name.
b. On the Client page, enable Client Credentials and Refresh Token.

c. At the bottom of the Client page, click Add and select the Identity Domain
Administrator role.

3. Click Add, then click Next until you reach the final page.

2-22
 Chapter 2
Use the Service Integration Account with No Password Expiration

4. Click Finish. The Application Added dialog is displayed.

a. Note the application ID, client ID, client secret for the confidential application (for this
example, referred to as ${SA_APP_ID}, ${SA_CLIENT_ID}, and $
{SA_CLIENT_SECRET}), then click Close.

Configure the Service Integration Application

1. Create the service integration application.
a. Get an access token to create an application (for this example, referred to as $
{SA_ACCESS_TOKEN}).
• Get access token request:

curl -X POST [Link] -u $

{SA_CLIENT_ID}:${SA_CLIENT_SECRET}
-d
'grant_type=client_credentials&scope=urn%3Aopc%3Aidm%3A__myscopes__
'

• Get access token response:

{
"access_token":
"eyJ4NXQjUzI1NiI6IlVFQ1RyX25Ram9XYk9........................XV-2ei4
pAUYV9aw66k_qL3b842qHw",
"token_type": "Bearer",
"expires_in": 3600
}

b. Create an application with the _BASICAUTH suffix using the above access token.
• Create an application request:

curl -X POST [Link] -H 'Authorization:

Bearer ${SA_ACCESS_TOKEN}'
-H 'Content-Type: application/json' -d '{ "active": true,
"allUrlSchemesAllowed": false,
"allowAccessControl": false, "allowedGrants":
["client_credentials", "urn:ietf:params:oauth:grant-type:
jwt-bearer"], "attrRenderingMetadata": [{ "name":
"aliasApps", "visible": false }],
"basedOnTemplate": { "value": "CustomWebAppTemplateId" },
"clientType": "confidential",
"displayName": "OICTEST_BASICAUTH", "editableAttributes":
[ { "name": "allowedGrants" },
{ "name": "protectableSecondaryAudiences" }, { "name":
"asOPCService" }, { "name":
"accessTokenExpiry" }, { "name": "linkingCallbackUrl" },
{ "name": "isOAuthResource" },
{ "name": "appIcon" }, { "name": "clientType" }, { "name":
"refreshTokenExpiry" },
{ "name": "trustScope" }, { "name": "landingPageUrl" },
{ "name": "audience" },
{ "name": "samlServiceProvider" }, { "name":
"isLoginTarget" }, { "name": "redirectUris" },

2-23
 Chapter 2
Use the Service Integration Account with No Password Expiration

{ "name": "allowedScopes" }, { "name": "tags" },

{ "name": "logoutUri" }, { "name":
"allowedOperations" }, { "name": "termsOfUse" },
{ "name": "serviceParams" }, { "name":
"certificates" }, { "name": "aliasApps" }, { "name":
"schemas" }, { "name": "isWebTierPolicy" },
{ "name": "trustPolicies" }, { "name":
"logoutPageUrl" }, { "name": "secondaryAudiences" },
{ "name": "displayName" }, { "name":
"serviceTypeURN" }, { "name": "icon" }, { "name":
"description" }, { "name": "isOAuthClient" },
{ "name": "allowedTags" }, { "name":
"showInMyApps" }, { "name": "isObligationCapable" },
{ "name": "isMobileTarget" }, { "name":
"allowOffline" }, { "name": "idpPolicy" }, { "name":
"appSignonPolicy" }, { "name":
"postLogoutRedirectUris" }, { "name":
"isFormFill" }, { "name": "loginMechanism" },
{ "name":
"serviceTypeVersion" }, { "name": "errorPageUrl" },
{ "name": "signonPolicy" }, { "name":
"identityProviders" }, { "name":
"isSamlServiceProvider" }, { "name":
"appThumbnail" }, {
"name": "loginPageUrl" }, { "name": "scopes" },
{ "name": "allowAccessControl" }, { "name":
"isKerberosRealm" }, { "name":
"allUrlSchemesAllowed" }, { "name":
"urn:ietf:params:scim:schemas:
oracle:idcs:extension:samlServiceProvider:App:encryptionAlgor
ithm" }, { "name": "urn:ietf:params:scim:
schemas:oracle:idcs:extension:samlServiceProvider:App:groupAs
sertionAttributes" }, { "name": "urn:ietf:
params:scim:schemas:oracle:idcs:extension:samlServiceProvider
:App:includeSigningCertInSignature" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:samlServi
ceProvider:App:signResponseOrAssertion"
}, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:samlServi
ceProvider:App:
assertionConsumerUrl" }, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:samlServi
ceProvider:
App:nameIdUserstoreAttribute" }, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:
extension:samlServiceProvider:App:logoutResponseUrl" },
{ "name": "urn:ietf:params:scim:schemas:oracle:
idcs:extension:samlServiceProvider:App:succinctId" },
{ "name": "urn:ietf:params:scim:schemas:oracle:
idcs:extension:samlServiceProvider:App:logoutRequestUrl" },
{ "name": "urn:ietf:params:scim:schemas:
oracle:idcs:extension:samlServiceProvider:App:partnerProvider
Id" }, { "name": "urn:ietf:params:scim:
schemas:oracle:idcs:extension:samlServiceProvider:App:nameIdF

2-24
 Chapter 2
Use the Service Integration Account with No Password Expiration

ormat" }, { "name": "urn:ietf:params:

scim:schemas:oracle:idcs:extension:samlServiceProvider:App:logoutBi
nding" }, { "name": "urn:ietf:params
:scim:schemas:oracle:idcs:extension:samlServiceProvider:App:userAss
ertionAttributes" }, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:samlServiceProv
ider:App:signatureHashAlgorithm" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:samlServiceProv
ider:App:metadata" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:samlServiceProv
ider:App:encryptAssertion" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:samlServiceProv
ider:App:logoutEnabled" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:samlServiceProv
ider:
App:encryptionCertificate" }, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:
extension:samlServiceProvider:App:signingCertificate" },
{ "name": "urn:ietf:params:scim:schemas:
oracle:idcs:extension:samlServiceProvider:App:federationProtocol" }
, { "name": "urn:ietf:params:scim:
schemas:oracle:idcs:extension:webTierPolicy:App:webTierPolicyJson"
}, {"name": "urn:ietf:params:scim:
schemas:oracle:idcs:extension:managedapp:App:bundleConfigurationPro
perties" }, {"name": "urn:ietf:
params:scim:schemas:oracle:idcs:extension:managedapp:App:isAuthorit
ative" }, { "name": "urn:ietf:
params:scim:schemas:oracle:idcs:extension:managedapp:App:enableSync
" }, { "name": "urn:ietf:params:
scim:schemas:oracle:idcs:extension:managedapp:App:adminConsentGrant
ed" }, { "name": "urn:ietf:params:
scim:schemas:oracle:idcs:extension:managedapp:App:connected" },
{ "name": "urn:ietf:params:scim:
schemas:oracle:idcs:extension:managedapp:App:flatFileBundleConfigur
ationProperties" }, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:managedapp:App:
threeLeggedOAuthCredential" }, {
"name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:managedapp:App:
bundlePoolConfiguration" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:managedapp:App:
flatFileConnectorBundle" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillAppTemp
late:AppTemplate:revealPasswordOnForm" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillAppTemp
late:AppTemplate:userNameFormTemplate"
}, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillAppTemp

2-25
 Chapter 2
Use the Service Integration Account with No Password Expiration

late:AppTemplate:userNameFormExpression" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
ppTemplate:AppTemplate:formCredentialSharingGroupID" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
ppTemplate:AppTemplate:formCredMethod" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
ppTemplate:AppTemplate:syncFromTemplate" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
ppTemplate:AppTemplate:configuration" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
ppTemplate:AppTemplate:formFillUrlMatch" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
ppTemplate:AppTemplate:formType" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:kerberosR
ealm:App:masterKey" }, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:kerberosR
ealm:App:maxRenewableAge" }, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:kerberosR
ealm:App:maxTicketLife" }, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:kerberosR
ealm:App:supportedEncryptionSaltTypes" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:kerberosR
ealm:App:realmName" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:kerberosR
ealm:App:ticketFlags" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:kerberosR
ealm:App:defaultEncryptionSaltType" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:requestab
le:App:requestable" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
pp:App:revealPasswordOnForm" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
pp:App:userNameFormExpression" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
pp:App:formType" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
pp:App:formCredMethod" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillA
pp:App:configuration" }, { "name":

2-26
 Chapter 2
Use the Service Integration Account with No Password Expiration

"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillApp:App
:formFillUrlMatch" }, { "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillApp:App
:formCredentialSharingGroupID" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:formFillApp:App
:userNameFormTemplate" },
{ "name":
"urn:ietf:params:scim:schemas:oracle:idcs:extension:dbcs:App:domain
App" }, { "name": "active" },
{ "name": "grantedAppRoles" }, { "name": "userRoles" },
{ "name": "adminRoles" }, { "name": "clientSecret" }
], "infrastructure": false, "isAliasApp": false,
"isManagedApp": false, "isMobileTarget": false,
"isOAuthClient":
true, "isOAuthResource": false, "isOPCService": false,
"isSamlServiceProvider": false, "isUnmanagedApp": false,
"isWebTierPolicy": false, "loginMechanism": "OIDC",
"migrated": false, "name": "OICTEST_BASICAUTH",
"showInMyApps": false, "trustScope": "Explicit",
"urn:ietf:params:scim:schemas:oracle:idcs:extension:requestable:App
":
{ "requestable": false }, "schemas":
["urn:ietf:params:scim:schemas:oracle:idcs:App",
"urn:ietf:params:scim:schemas:
oracle:idcs:extension:requestable:App"] }'

• Create an application response:

{ "clientType": "confidential", "isAliasApp": false,

"meta": {
"created": "2019-04-01T07:51:47.025Z", "lastModified":
"2019-04-01T07:51:47.025Z",
"resourceType": "App", "location": "[Link]
{IDCS_HOST}/admin/v1/Apps/
0c228094b0f5456289b928f979800308" }, "active": true,
"isLoginTarget": true,
"idcsCreatedBy": { "display": "OIC_SI_TEST",
"type": "App", "value":
"5debb165fc6946708e2c1f27264fafb1", "$ref": "[Link]
{IDCS_HOST}/admin/v1/Apps/
5debb165fc6946708e2c1f27264fafb1" }, "displayName":
"OICTEST_BASICAUTH",
"showInMyApps": false, "isMobileTarget": false,
"allowOffline": false,
"isUnmanagedApp": false, "idcsLastModifiedBy":
{ "display": "OIC_SI_TEST",
"type": "App", "value":
"5debb165fc6946708e2c1f27264fafb1", "$ref":
"[Link]
5debb165fc6946708e2c1f27264fafb1" },
"isOPCService": false, "name": "OICTEST_BASICAUTH",
"isOAuthClient": true,
"isManagedApp": false, "isSamlServiceProvider": false,
"infrastructure": false,

2-27
 Chapter 2
Use the Service Integration Account with No Password Expiration

"allUrlSchemesAllowed": false, "trustScope":

"Explicit", "id":
"0c228094b0f5456289b928f979800308", "isWebTierPolicy":
false, "loginMechanism":
"OIDC", "allowAccessControl": false,
"isOAuthResource": false, "migrated":
false, "isKerberosRealm": false, "allowedGrants":
[ "client_credentials",
"urn:ietf:params:oauth:grant-type:jwt-bearer" ],
"attrRenderingMetadata": [ {
"name": "aliasApps", "visible":
false } ], "basedOnTemplate": {
"value": "CustomWebAppTemplateId", "lastModified":
"2018-05-31T22:35:08Z",
"$ref": "[Link]
CustomWebAppTemplateId" }, "schemas": [
"urn:ietf:params:scim:schemas:oracle:idcs:App" ],
"clientSecret": "91ac1189-b2ca-4ccb-a049-bbc635927646" }

c. Note the application ID, client ID, and client secret from the response (for this
example, referred to as ${SI_APP_ID}, ${SI_CLIENT_ID}, and $
{SI_CLIENT_SECRET}).
d. Activate the application using the above access token.
• Activate the application request:

curl -X PUT [Link]

{SI_APP_ID} -H
'Authorization: Bearer ${SA_ACCESS_TOKEN}' -H 'Content-Type:
application/json' -d
'{"schemas":
["urn:ietf:params:scim:schemas:oracle:idcs:AppStatusChanger"]
,"id":"${SI_APP_ID}",
"active":true}'

2. Associate the service integration application.

a. Identify the AppRoleID to be granted for the Oracle Integration application. The
ServiceUser role is assigned to the created application. Therefore, a search is
performed for that role (for this example, referred to as ${OIC_APP_ROLE_ID}).
• Get the application role ID request:

curl -X GET '[Link]

attributes=groups,urn:ietf:params:
scim:schemas:oracle:idcs:extension:user:User:appRoles&filter=
displayName+co+%22ServiceUser%22+
and+[Link]+eq+%22${OIC_APP_ID}%22' -H 'Authorization:
Bearer ${SA_ACCESS_TOKEN}'

• Get the application role ID response:

{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:ListResponse"

2-28
 Chapter 2
Use the Service Integration Account with No Password Expiration

],
"totalResults": 1,
"Resources": [
{
"displayName": "ServiceUser",
"id": "20e22fd1eb2e43ac8645e105abcab201",
"app": {
"value": "e0eea2c9fadb42c09d33035ff41e8f57",
"display": "OICSSA_oiccafdev7"
}
}
],
"startIndex": 1,
"itemsPerPage": 50
}

b. Grant the service integration application with the above role.

• Grant the role request:

curl -X POST [Link] -H

'Authorization: Bearer ${SA_ACCESS_TOKEN}' -H 'Content-Type:
application/json' -d '{
"app": {
"value": "${OIC_APP_ID}"
},
"entitlement": {
"attributeName": "appRoles",
"attributeValue": "${OIC_APP_ROLE_ID}"
},
"grantMechanism": "ADMINISTRATOR_TO_APP",
"grantee": {
"value": "${SI_APP_ID}",
"type": "App"
},
"schemas": ["urn:ietf:params:scim:schemas:oracle:idcs:Grant"]
}'

• Grant the role response:

{
"app": {
"value": "${OIC_APP_ID}",
"$ref": "[Link]
},
"entitlement": {
"attributeName": "appRoles",
"attributeValue": "${OIC_APP_ROLE_ID}"
},
"grantMechanism": "ADMINISTRATOR_TO_APP",
"grantee": {
"value": "${SI_APP_ID}",
"type": "App",
"$ref": "[Link]
},

2-29
 Chapter 2
Use the Service Integration Account with No Password Expiration

"schemas": [
"urn:ietf:params:scim:schemas:oracle:idcs:Grant"
],
"id": "6832316983c545baa01e9a9488022fa7",
"isFulfilled": true,
"grantor": {
"type": "App",
"value": "${SA_APP_ID}",
"$ref": "[Link]
{SA_APP_ID}"
},
"meta": {
"created": "2019-04-01T08:00:33.277Z",
"lastModified": "2019-04-01T08:00:33.277Z",
"resourceType": "Grant",
"location": "[Link]
6832316983c545baa01e9a9488022fa7"
},
"idcsCreatedBy": {
"value": "${SA_APP_ID}",
"type": "App",
"display": "OIC_SI_TEST",
"$ref": "[Link]
{SA_APP_ID}"
},
"idcsLastModifiedBy": {
"value": "${SA_APP_ID}",
"type": "App",
"display": "OIC_SI_TEST",
"$ref": "[Link]
{SA_APP_ID}"
}
}

Using the Service Integration Credentials

Once setup is complete, the credentials ${SI_CLIENT_ID} and $
{SI_CLIENT_SECRET} can be used as the user name and password for
authentication to an Oracle Integration endpoint as shown below.
Oracle Integration SOAP endpoint request sample:

curl -X POST [Link]

FLOW/1.0/ -u
${SI_CLIENT_ID}:${SI_CLIENT_SECRET} -H 'Content-Type: text/
xml;charset=UTF-8' -H 'SOAPAction:
process' -d '<soapenv:Envelope xmlns:rp="[Link]
rp_WS_Basic_Authentication_APP/
rp_WS_Basic_Authentication/rp_Basic_Authentication_WS"
xmlns:soapenv="[Link]
soap/envelope/">
<soapenv:Header>
<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://
[Link]/wss/2004/01/
[Link]" xmlns:wsu="http://

2-30
 Chapter 2
Use OAuth Authentication for REST APIs

[Link]/wss/2004/01/
[Link]">
<wsu:Timestamp wsu:Id="TS-0BC1DE3F9C8F739DB815541392855881">
<wsu:Created>2019-04-01T00:00:00.000Z</wsu:Created>
<wsu:Expires>2019-04-02T00:00:00.000Z</wsu:Expires>
</wsu:Timestamp>
</wsse:Security>
</soapenv:Header>
<soapenv:Body>
<rp:process>
<rp:input>OICTEST</rp:input>
</rp:process>
</soapenv:Body>
</soapenv:Envelope>'

Use OAuth Authentication for REST APIs

Authentication and authorization in Oracle Integration is managed by Oracle Identity Cloud
Service. Oracle Integration REST APIs as well as REST endpoints exposed in integrations
are protected using the OAuth token-based authentication. OAuth is an authorization
framework that enables an application or service to obtain limited access to a protected
HTTP resource.
To use REST APIs with OAuth in Oracle Integration, you need to register your Oracle
Integration instance as a trusted application in Oracle Identity Cloud Service. See Security,
Authentication, and Authorization in REST API for Oracle Integration.

Trigger Integrations Using OAuth Authentication

Oracle Integration REST endpoints are OAuth-protected and can be triggered from a client
using OAuth 2.0. You must perform several configuration steps for a client (in this example,
postman) to successfully trigger an Oracle Integration REST-based integration.
See this blog.

2-31
3
Ready, Set Up, and Go
You use the Oracle Cloud Infrastructure Console to install instances of Oracle Integration.

Topics:
• Accessing Oracle Integration
• Assign the Correct User Roles to Create an Instance
• Create an Oracle Integration Instance
• About the User Interfaces of the Oracle Integration Oracle Cloud Infrastructure Console
• Subscribe to Regions Before Upgrading

Accessing Oracle Integration

You access Oracle Integration from the Oracle Cloud Infrastructure Console.

Topics:
• Access Oracle Integration from the Oracle Cloud Infrastructure Console
• Access Oracle Integration Classic from the Oracle Cloud Infrastructure Console

Access Oracle Integration from the Oracle Cloud Infrastructure Console

You access Oracle Integration through a web console. Note that your cloud tenancy has been
enabled for Oracle Integration Generation 2. If you still have Oracle Integration instances,
note that the navigation menu has changed. Review this section for details.
1. Sign in to your Oracle Cloud account.
If you are a new user, you received a welcome email. Use it to identify the URL, your user
name, and your temporary password. After signing in, you are prompted to change your
password.

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.
Your cloud tenancy has been enabled for Oracle Integration Generation 2. Provisioning
and administration steps for Oracle Integration Generation 2 are described in a separate
guide. See Creating and Editing Oracle Integration Instances.
If you still have Oracle Integration instances, the navigation menu has changed. Follow
these steps to access your Oracle Integration instances.
• The old console (PSM) URLs continue to work. Those URLs look as follows:
– For Oracle Integration:

[Link]
[Link]?serviceType=OICINST

3-1
 Chapter 3
Accessing Oracle Integration

– For Oracle Integration for SaaS:

[Link]
faces/[Link]?serviceType=OICSUBINST

• If you log in through the Oracle Cloud Infrastructure Console using a URL
similar to [Link] you previously
selected Platform Services > Integration to access your Oracle Integration
instances.

This menu entry is no longer available. Instead, perform the following steps to
access your instances.
a. Open the navigation menu and click Developer Services. Under
Application Integration, click Integration.

This takes you to the landing page for Oracle Integration Generation 2
instances. At the top of the page, the following banner is displayed:

3-2
 Chapter 3
Assign the Correct User Roles to Create an Instance

b. Click Instances in the banner to see your Oracle Integration instances.

Access Oracle Integration Classic from the Oracle Cloud Infrastructure

Console
You access Oracle Integration Classic from the Oracle Cloud Infrastructure Console.
1. Sign in to your Oracle Cloud account.
If you received a welcome email, use it to identify the URL, your user name, and your
temporary password. After signing in, you are prompted to change your password.

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.
3. Click OCI Classic Services > Integration Classic.

Assign the Correct User Roles to Create an Instance

If you are the user that initially signed up and purchased universal credits for Oracle Cloud,
you automatically have the necessary service entitlement roles to create Oracle Integration
instances. Otherwise, the correct roles must be explicitly assigned to your user account to
create Oracle Integration instances. Without the necessary roles, instance creation fails.

3-3
 Chapter 3
Create an Oracle Integration Instance

To successfully create Oracle Integration instances, ensure that your user account is
assigned the following role for these services:
• Integration:
Service Entitlement: AUTONOMOUS_INTEGRATION:
CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud
entitlement administrator role)
To know how to add new users and assign roles, see Add a User and Assign Roles to
a User.

Note:
The Identity Cloud - Service Entitlement (Identity Domain Administrator) role
has super user privileges for the identity domain. Users with this role can
manage users, groups, applications, and system configuration settings. They
can also perform delegated administration by assigning users to different
administrative roles.

Create an Oracle Integration Instance

You can no longer create an Oracle Integration instance. If you want to create a new
instance, create an Oracle Integration Generation 2 instance. If you still have Oracle
Integration instances, open a service request with Oracle Support to learn how to
upgrade the instances to Oracle Integration Generation 2.
See Creating and Editing Oracle Integration Generation 2 Instances in Provisioning
and Administering Oracle Integration and Oracle Integration for SaaS, Generation 2.

About the User Interfaces of the Oracle Integration Oracle

Cloud Infrastructure Console
You can perform life cycle management tasks from the Oracle Integration Oracle
Cloud Infrastructure Console.

Topics:
• Explore the Oracle Cloud Infrastructure Console
• Explore the Oracle Cloud Infrastructure Console Activity Page
• Explore the Oracle Cloud Infrastructure Console Instance Overview Page

Explore the Oracle Cloud Infrastructure Console

You can use the Oracle Cloud Infrastructure Console to view all existing Oracle
Integration instances.

3-4
 Chapter 3
About the User Interfaces of the Oracle Integration Oracle Cloud Infrastructure Console

The following table describes the key information shown in the Oracle Cloud Infrastructure
Console.

Element Description
Click and select an option from the menu to open the service console for one of
the Oracle Services to which you are subscribed.

(Next to the word ORACLE in the

upper left corner of the page)
Welcome! Click to display the Oracle Integration Welcome page.
Click to sign in to the services to which you are subscribed.

Instances (Summary panel) Number of instances and message packs in the identity domain.
Search by instance name or Enter a full or partial service instance name or tags to filter the list of service
tags instances to include. You can create a tag of a service instance when installing
Oracle Integration with the stack templates.
Create Instance Create a new service instance. This option lets you customize the number of
message packs and select the region from which to provision your instance.
Service instance icon for a created instance. Click this icon to view more details.

Status icon indicating that the instance is being created.

Status icon indicating the service instance is undergoing maintenance or

terminating.

3-5
 Chapter 3
About the User Interfaces of the Oracle Integration Oracle Cloud Infrastructure Console

Element Description
Status icon indicating that the service instance has failed to be created. This
icon can also indicate that the service instance has stopped. See the Activity
page.
service-name Name of the service instance. Click the name to view more details.
Created On When provisioning is complete, the date and time in UTC at which the instance
was created.
Message Packs The number of message packs available with the instance.
Click to select one of the following options:
• Open Oracle Integration Home Page
• Start
• Stop
• Add Tags
• Scale Instance
• Change License Type
• Delete
Instance Create and Delete Shows details about created or deleted service instances.
History • Range—Specifies a range for which you are interested in viewing created
and failed service instances.
• Show only failed attempts—Check this box if you want to see failed
attempts only.
• Details—Displays system messages logged during the creation or deletion
process. Messages include information about auto-retry attempts.

Explore the Oracle Cloud Infrastructure Console Activity Page

You can use the Activity page to search for and review cloud service activities that
have occurred in your identity domain. To access this page, click the Activity tab.

The Activity page is divided into the following sections:

• The Search Activity Log section, from which you can specify search details that
determine which services you see. These details include:
– Date and time range
– Operation status

3-6
 Chapter 3
About the User Interfaces of the Oracle Integration Oracle Cloud Infrastructure Console

– Instance name and service type

– Operation type
• The Results pane, which shows the results of the search operation. You can limit the
number of results to return, per page, to 5, 10, 50, or 100.
The following table describes the key information shown on the Activity page.

Element Description
Start Time Range Filters activity results to include only operations started within a specified time
range. The range defaults to the previous 24 hours.
Operation Status Filters operations by status of the operation:
• All (default value)
• Scheduled
• Running
• Succeeded
• Failed
You can select any subset of status types.
Instance Name Filters the activity results to include operations only for the specified service
instance. You can enter a full or partial service instance name.
Service Type Filters the activity results to include operations only for instances of the
specified service type. The default value is the current cloud service.
Operation Filters the activity results to include selected types of operations. You can select
any subset of the given operations. The default value is All.
Search Searches for activities by applying the filters specified by the Start Time Range,
Status, Service Name, Service Type, and Operation fields, and displays activity
results in the table.
Reset Clears the Start Time Range and Service Name fields, and returns the Status
and Operation fields to their default values.
Results per page Specifies the number of results you want to view per page. The default value is
10. You can sort the columns in ascending or descending order.
Operation Shows the type of operation performed on the service instance.
Instance Name Shows the name of the service instance and its identity domain:
service_instance:identity_domain
Service Type Shows the type of cloud service for this instance.
Operation Status Shows the status of the operation performed on the service instance.
Start Time Shows the time the operation started.
End Time Shows the time the operation ended, if the operation is complete.
Initiated By Shows the user that initiated the operation. The user can be any user in the
identity domain who initiated the operation or, for certain operations such as
automated backup, the system.

Explore the Oracle Cloud Infrastructure Console Instance Overview Page

You can use view overview information for a specific instance. To access this page, click an
instance name or icon in the Oracle Cloud Infrastructure Console.

Instance Overview

3-7
 Chapter 3
Subscribe to Regions Before Upgrading

The following table describes the key information shown on the Overview page.

Element Description
Manage this instance Click to select one of the following options:
(adjacent to the service • Open Oracle Integration Home Page
instance name) • Start
• Stop
• Add Tags
• Scale Instance
• Change License Type
• Delete
Overview tab The Instance Overview tile displays overview information about the service
instance.
• Status: The service instance’s status (for example, ready).
• Active: Status of the instance.
• Messages Packs: Displays the number of message packs available with
this instance.
• Service Identifier: The unique identifier of the service instance.
• License: The type of cloud license (for example, bring your own license
(BYOL)).
• Version: The version of Oracle Integration.
• Feature Set: The provisioned feature set (for example, Integration or
Integration and Process).
• Oracle Integration Edition: The topology you selected when you
provisioned the service instance (either Enterprise Edition or Standard
Edition).
• IDCS Application: Click the link to open the Oracle Identity Cloud Service
Console to add users and assign roles. See Grant Access and Manage
Security.
Click to refresh the page. The date and time the page was last refreshed are
Refresh displayed adjacent to this button.

Subscribe to Regions Before Upgrading

Oracle has begun upgrading Oracle Integration instances to Oracle Integration
Generation 2 instances. However, you may have received a notification email

3-8
 Chapter 3
Subscribe to Regions Before Upgrading

indicating that your Oracle Cloud Infrastructure tenancy is not subscribed to all the necessary
regions. Follow these steps to quickly subscribe to all regions.

Subscribe to Regions Before Upgrade

Before upgrade, your Oracle Cloud Infrastructure tenancy must be subscribed to each region
in which an Oracle Integration instance exists. For example, if Ashburn is your home region,
but you created an Oracle Integration instance in the Phoenix region, the tenancy must be
subscribed to the Phoenix region.
1. In the Oracle Cloud Infrastructure Console, locate the region for each of your Oracle
Integration instances.
a. From the list of your instances, select each instance.

b. Click

in the top right corner of the page.

c. Locate the region.

3-9
 Chapter 3
Subscribe to Regions Before Upgrading

d. Repeat these steps for all other instances.

2. Subscribe to regions, as needed.
a. Open the Oracle Cloud Infrastructure Console, open the Region menu, and
click Manage Regions. The list of regions available to your tenancy is
displayed. Your home region is labeled.
b. Locate the region you want to subscribe to and click Subscribe. It may take
several minutes to activate your tenancy in the new region.
c. Repeat these steps to subscribe to all unsubscribed regions of an Oracle
Integration instance. You can manage infrastructure regions. See Managing
Regions.

Note:
If a message alerts you that you have exceeded the maximum number of
regions allowed for your tenancy, request a limit increase to your subscribed
region count from the Oracle Cloud Infrastructure Console. See Request a
subscribed region limit increase.

3-10
 Chapter 3
Oracle Integration for Oracle SaaS

Oracle Integration for Oracle SaaS

Oracle Integration for Oracle SaaS, a streamlined version of Oracle Integration, gives you the
features and benefits of Oracle Integration with a focus on SaaS.

Topics:
• Differences between Oracle Integration and Oracle Integration for Oracle SaaS
• Create an Oracle Integration for Oracle SaaS Instance
• View Message Consumption for Oracle Integration for Oracle SaaS

Differences between Oracle Integration and Oracle Integration for Oracle

SaaS
Oracle Integration for Oracle SaaS, a streamlined version of Oracle Integration, gives you the
features and benefits of Oracle Integration with a focus on SaaS. Here are the key
differences:
• Purpose-built for connecting and extending Oracle SaaS. Specifically, every
integration you create has an endpoint in an Oracle Cloud SaaS application, every Visual
Builder application you create uses at least one business object or API call from an
Oracle Cloud SaaS application, and every process application you create includes at
least one business object or API call from an Oracle Cloud SaaS application.
• Flexibility for hourly bursting. Oracle Integration for Oracle SaaS is offered as a
monthly subscription in packs of one million messages per month, which keeps costs
predictable even when you have unpredictable hourly volumes. Usage is reported
monthly instead of hourly.
• Provisioning. Creating an instance for Oracle Integration for Oracle SaaS is slightly
different from creating an instance for Oracle Integration, and Bring Your Own License
(BYOL) is not available in Oracle Integration for Oracle SaaS. For more details, see
Create an Oracle Integration for Oracle SaaS Instance.
Other than those differences, the product functionality, graphical user interface, and
documentation are the same.

Create an Oracle Integration for Oracle SaaS Instance

You can no longer create an Oracle Integration for Oracle SaaS instance. If you want to
create a new instance, create an Oracle Integration for Oracle SaaS Generation 2 instance. If
you still have Oracle Integration for Oracle SaaS instances, open a service request with
Oracle Support to learn how to upgrade the instances to Oracle Integration Generation 2.
See Creating and Editing Oracle Integration Generation 2 Instances in Provisioning and
Administering Oracle Integration and Oracle Integration for SaaS, Generation 2.

View Message Consumption for Oracle Integration for Oracle SaaS

In the Resource Quotas page, you can view the number message packs you have and how
many are remaining.
1. Sign in to your Oracle Cloud account.

3-11
 Chapter 3
Oracle Integration for Oracle SaaS

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.
3. Click Dashboards > Infrastructure Classic.
4. Click Integration for Oracle SaaS in the graph to display information about your
instance.

5. Select the Resource Quotas tab to view how many message packs you have,
how many you have used, and how many are remaining.

3-12
4
Navigate and Explore
After your system is provisioned and user roles are assigned, begin exploring the rich
features of Oracle Integration.

Topics:
• Sign In to Oracle Integration
• What You Can Do on the Home Page
• Use Features Together

Sign In to Oracle Integration

Before you can sign in, you must have a user account that defines your user name,
password, and identity domain, and access rights to the service. You also need the web
address (URL) for your instance.
When a service is activated, it sends the sign-in credentials and URL to the designated
administrators. An administrator then creates an account for each user who needs access to
the service. Check your email or contact your administrator for your account credentials and
service URL.

Tip:
New to administering Oracle Cloud Services? See Get Started with Your Cloud
Services in Getting Started with Oracle Cloud.

To sign in:
1. Open your web browser and go to the service URL given to you either in an email or by
your administrator. The Sign In page opens.
2. Enter your identity domain, user name (user ID), and password.
3. Click Sign In.
If you’re signing in for the first time, you’re prompted to create a new password for
security reasons. Follow the instructions on the screen to complete this task.
After you sign in, the Welcome page opens. Select any item on this page to learn more
about Oracle Integration and its features.
4. Click Home.

What You Can Do on the Home Page

Use the Home page as your launch pad and high-level dashboard. Return to it at any point,
and depending on your assigned role, launch features, return to previous work, monitor
instances, and drill down to troubleshoot as needed.

4-1
 Chapter 4
What You Can Do on the Home Page

The Home page includes two main areas: the navigation pane and the adjacent main
pane that displays tiles for viewing, developing, performing actions, and monitoring.
What you see on the Home page depends on:
• Your assigned role
For example, users assigned the ServiceAdministrator role are superusers that
see all available options on the Home page. Users assigned the ServiceDeveloper
role see options to develop for all features but not administer. See Grant Access
and Manage Security.
• The features available for your instance
For example, your instance might include the Integrations and Visual Builder
features, or it might include the Integrations, Processes, and Visual Builder
features. If you’re using Oracle Integration Classic (user-managed), your instance
might include the Integrations, Processes, and Visual Builder features.
Use the Home page to:
• Navigate Anywhere
• View and Drill Down by Status
• Open Recently Worked on Items
• Start Process Applications as a User
• Start Developing by Feature
• Monitor Health and Drill Down to Troubleshoot

4-2
 Chapter 4
What You Can Do on the Home Page

Navigate Anywhere
Use the navigation pane to launch features or drill down to specific options.
The links in the navigation pane change, depending on your location in Oracle Integration.
• When the Home page is displayed, the navigation pane lists all the features available to
you.

4-3
 Chapter 4
What You Can Do on the Home Page

• When you select a feature link, the navigation pane changes to list available
options for the feature. For example, after you click Processes in the navigation
pane, process-specific links display in the pane. Click Home to return to the
Home page.

Depending on your assigned role and available features, the following links may
display on the Home page.

Links Description
Learn about Oracle Integration’s features.
Welcome
Access the launch pad and high-level dashboard for Oracle Integration. You
Home can return to the Home page at any time.

4-4
 Chapter 4
What You Can Do on the Home Page

Links Description
Launch the runtime environment for process tasks. Start process applications,
My Tasks work on tasks as a user, view dashboards, and perform runtime administration
such as mapping process roles.
See Quick Tour of the Tasks Page in Using Processes in Oracle Integration.
Launch the design-time environment for process applications. Create process
Processes applications from scratch or by using QuickStart Apps. Model processes in the
process editor, and create web forms and decisions. Perform design-time
administration such as playing, testing, and deploying applications.
See Quick Tour of the Processes Page in Using Processes in Oracle
Integration.
Launch the design-time environment for integrations. Create and activate
Integrations integrations, as well as their connections and orchestrations. Work with
lookups, packages, agents, and adapters.
See Getting Started with Integrations in Using Integrations in Oracle
Integration.
Create and publish web and mobile applications.
Visual Builder
See Getting Started with Visual Builder in Using Oracle Visual Builder -
Classic Applications.
Change logging levels and download logs for Oracle Integration.
Settings See Configure Settings for Error Logs.

View and Drill Down by Status

Status tiles provide a quick view of key artifacts. Click any item for more information.
• My Tasks: See which process tasks are in progress. If needed, drill down to tasks.
– Overdue: Includes tasks whose due date has passed.
– Open: Includes tasks that are assigned.
– On Track: Includes tasks due in more than two days and those without a due date.
– Due: Includes tasks due within the next two days.
• Integrations: See the number of active integrations and drill down to scheduled
integrations.
• Connections: See the number of active connections used in integrations and drill down if
needed.
• Visual Applications: See the number of developed, staged, and published applications
and drill down if needed.
Status tiles display to all users.

4-5
 Chapter 4
What You Can Do on the Home Page

Open Recently Worked on Items

The Recents tile lists feature artifacts created or edited recently. For example, select a
recent integration to quickly begin editing it. From the tabs, select a feature, then
select a recent item.
The display of the Recents tile depends on the role assigned to you.

Start Process Applications as a User

The Actions tile lists process applications ready to start. This tile provides one of
several ways for end users to start process applications, and also allows developers to
try out process applications after activating them. (Users can also click My Tasks in
the navigation pane and then click Initiate Request to start an application.)

4-6
 Chapter 4
What You Can Do on the Home Page

The Actions tile displays to all users. To display in the Actions tile, the process application
must be activated and its roles must be mapped.

Start Developing by Feature

The Develop tile lets you quickly get started creating artifacts for selected features.
• Processes: Create an application from scratch or select from the QuickStart gallery of
completed applications that you can customize or activate as is.
• Integrations: Create connections and an integration that uses them or activate a ready-
to-use sample integration.
The Develop tile is displayed depending on the roles assigned to you.

Monitor Health and Drill Down to Troubleshoot

The Monitor tiles provide quick access to dashboard and monitoring information.
• Process Health displays the number of processes that are suspended, recoverable, and
alerted. Click Tracking to view specific instances. Click Dashboard to view process
instance health or create your own dashboards.
• Integrations Health displays details about the overall system health of integrations,
where green indicates that system health is acceptable and red indicates that errors are
occurring that can impact your active integrations. The total numbers of received
messages, processed messages, successful messages, and failed messages are also
provided. Click Monitoring to drill down to troubleshoot.

4-7
 Chapter 4
Use Features Together

The Monitor tiles that are displayed depend on your assigned roles.

Use Features Together

You can use Oracle Integration features together in a number of ways.
• Use Integrations in Process Applications
• Use Process Applications in Integrations
• Use Processes in Visual Builder Applications

Use Integrations in Process Applications

You can incorporate integrations into processes directly from the process editor. Drag
and drop an integration element from the palette to the process flow, and select the
active integration to call.
See Configuring Integrations in Using Processes in Oracle Integration.

Use Process Applications in Integrations

You can invoke a process from an orchestrated integration. When you drag the
process node into an integration, the Select Process wizard prompts you to select an
application, process, and operation to invoke.
See Connecting to Processes in Using Integrations in Oracle Integration.

Use Processes in Visual Builder Applications

You can use processes in Visual Builder applications to automate task assignment and
create task lists. After you associate a Visual Builder custom business object with a
process, you can add triggers, UI actions, and UI components to pages to start
processes and enable user tasks to be completed.

4-8
 Chapter 4
Use Features Together

See Creating Processes for Business Objects in Using Oracle Visual Builder - Classic
Applications.

4-9
5
Move Design-Time Metadata Between
Environments
Use the user interface or REST APIs to move metadata between Oracle Integration
instances.

Topics:
• Configure the Instance Object Storage Bucket
• Export and Import Design-Time Metadata Between Instances
• Export and Import Integration and Process Design-Time Metadata Between Instances
with the REST APIs
• Migrate Process Design-Time Metadata into Oracle Integration
Oracle encourages you to migrate your existing instances of Oracle Integration Service,
Oracle Process Cloud Service, and Oracle Integration Classic to Oracle Integration on Oracle
Cloud Infrastructure. You can gain several advantages by doing so.
• Migrate Oracle Integration Cloud Service and Process Cloud Service to Oracle Cloud
Infrastructure
• Migrate Oracle Integration Classic Instances to Oracle Cloud Infrastructure

Configure the Instance Object Storage Bucket

You must specify the Swift URL location and username and password credentials of your
existing object storage bucket instance before you can create export and import archives of
design-time metadata on the Import/Export page.
To complete the fields on this page, an object storage bucket instance must already exist.
Otherwise, you must create a new instance. See Step 3: Create an Object Storage Bucket
and Construct the Storage URL (If Not Using the Application Migration Service).
1. On the Home page, select Settings > Storage.

5-1
 Chapter 5
Export and Import Design-Time Metadata Between Instances

2. Enter the following details.

Element Description
Name Enter the name of the object storage bucket.
Swift URL Enter the object storage bucket Swift URL.
For example:

[Link]
[Link]/v1/
paasdevoic/cloneRepo

See Step 3: Create an Object Storage

Bucket and Construct the Storage URL (If
Not Using the Application Migration
Service).
User Specify the object storage bucket user
name. See Step 2: Create a User and Group
and Add Policies.
Password Specify the password.

3. Click Save. You can now export and import archives of design-time metadata on
the Import/Export page.

Export and Import Design-Time Metadata Between

Instances
You can export and import archives of integration and process design-time metadata
between instances. This feature can be useful if you want to take a snapshot of a
production environment and try to recreate a problem in a different environment, move
metadata from an instance in one region to an instance in another region, perform
manual archival backups, or automate your environment to archive backups daily to a
repository such as Git. You can also export Oracle Integration archives and import
them into Oracle Integration Generation 2.

Note:
Ensure that you first configure the Swift URL location and username and
password credentials of the object storage bucket instance to which to export
an archive of your design-time metadata on the Instance Storage page. See
Configure the Instance Object Storage Bucket.

• Create an Export Job

• Create an Import Job

5-2
 Chapter 5
Export and Import Design-Time Metadata Between Instances

Create an Export Job

You create an export job that consists of an archive file of design-time metadata that you
want to export to the object storage bucket you configured on the Instance Storage page.

1. On the Home page, select Settings > Import/Export in the navigation pane.
The Import/Export page is displayed with the status of any import and export jobs.

2. Click Export to create a job. A job consists of an archive file of design-time metadata that
you want to export to the object storage bucket you configured on the Instance Storage
page. If you have not configured an object storage bucket, you are prompted to click
Configure Now.
3. Complete the following fields.

Element Description
Job Name Enter a unique job name or accept the default
value.
Export security artifacts Select the check box to export the following
security artifacts with your job:
• Security policies
• Security credentials (for connections)
• Customer certificates
• Application role memberships in Processes
.
Description Enter an optional description that describes the
export job.

5-3
 Chapter 5
Export and Import Design-Time Metadata Between Instances

4. Click Start Export Job.

A message is displayed in the banner at the top of the page.

Export job has been successfully started.

5. View the status of export job creation and click the refresh icon periodically to
view progress. You can click the job name to view more specific job details.

When the export job completes successfully, Completed is displayed in the

Status field.
6. Click

to view details about a job.

5-4
 Chapter 5
Export and Import Design-Time Metadata Between Instances

7. If export archive creation does not complete successfully, click to download a report
about the export job.

Create an Import Job

You create a job to import the exported archive job from the object storage bucket instance
into the new instance.

1. Sign in to the instance in which to import the exported archive of design-time metadata.
2. On the Home page, select Settings > Import/Export.
3. Click Import to create a job to import the exported archive job from the object storage
bucket instance into the new instance.
4. Complete the following fields.

Element Description
Archive Filename Select the archive to import into the instance.
Import Mode Select the import mode:
• Import: Imports all integrations in the
archive. You can also select Activate and
Start Schedules to activate all integrations
and start all schedules during this same
import session or during a separate session
at a later time. Selecting those options
separately enables you to first update any
configuration properties in the imported
integrations (for example, modify any
necessary configuration or security
properties on the Connections page for
each integration).
• Activate: Activates all integrations imported
with the Import option during the same
session or during a separate session. You
can also select Start Schedules to start
any integration schedules.
• Start Schedules: Starts integration
schedules during the same session in
which you selected Import and Activate or
during a separate session.
Import security artifacts Select this check box if you previously selected
Export security artifacts when creating your
export archive job.
Job Name Enter a unique job name or accept the default
value.
Description Enter an optional description that describes the
import job.

5-5
 Chapter 5
Export and Import Design-Time Metadata Between Instances

5. Click Start Import Job to start the job to import the archive from the object
storage bucket instance into the new Oracle Integration instance.
A message is displayed in the banner at the top of the page.

Import job has been successfully started.

6. View the status of import job creation and click the refresh icon periodically to
view progress.
When the import job completes successfully, Completed is displayed in the
Status field.
7. Click

to view details about the job.

5-6
 Chapter 5
Export and Import Integration and Process Design-Time Metadata Between Instances with the REST APIs

8. If the import archive is not successful, click to download a report about the import job.
9. Browse the pages and note that the design-time metadata you exported is now visible.
For example, for Integrations, look for integrations, connections, lookups, and more. For
Processes, look for process applications and decision models.

Note:
Your archive file resides in the object storage bucket until you delete it.

Export and Import Integration and Process Design-Time

Metadata Between Instances with the REST APIs
You can export an Oracle Integration instance to another Oracle Integration instance (for
example, to take a snapshot of a production environment and try to recreate a problem in a
different environment).

Prepare to Export and Import Design-Time Metadata

Before you can export and import design-time metadata, you must create a user and group
and add policies and create an object storage bucket and construct the storage URL.
• See Step 2: Create a User, Group, and Policy.
• See Step 3: Create an Object Storage Bucket and Construct the Storage URL.
You must have the service administrator role to create the storage bucket and import and
export design-time metadata.

Export Oracle Integration Design-time Metadata from One Instance

Perform the following command to export Integration and Process design-time metadata to
an archive.
1. To export the Integrations design-time metadata to another Oracle Integration instance,
invoke the REST API. This action asynchronously creates an archive that includes all
above-mentioned objects.

Headers
Authorization : Basic
Content-Type : application/json
payload
{
"storageInfo": {
"storageUrl": "[Link]
[Link]/v1/
paasdevoic/cloneRepo",
"storageUser":"myemail@[Link]",
"storagePassword":"generated_token"
}
}

5-7
 Chapter 5
Export and Import Integration and Process Design-Time Metadata Between Instances with the REST APIs

For example, use a postman or curl (as shown below) command to export all
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":" [Link]
[Link]/v1/
paasdevoic/cloneRepo","storageUser":"myemail@[Link]",
"storagePassword":"generated_token"}}' -u admin:password
[Link]

where:
• storageInfo: Is the URL of the storage container.
• storageUser: Is the storage user name.
• storagePassword: Is the storage password.
Possible sample output from this command is as follows:

{
"archiveFilename": "archive_Local_Suite_Instance-d1e4295f-
[Link]",
"jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4",
"location": "[Link]
[Link]/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 admin:password [Link]

exportServiceInstanceArchive/{jobId}

Possible sample output from this command is as follows:

{
"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 the Design-Time Metadata into Another Oracle Integration Instance

After exporting Integration and Process design-time metadata to a zip archive file,
import the file to another Oracle Integration instance.
When imported into Oracle Integration, the archive is referenced in the payload.

{
"archiveFile": "archive_file_name",
"importActivateMode": "ImportActivate",

5-8
 Chapter 5
Export and Import Integration and Process Design-Time Metadata Between Instances with the REST APIs

// options are "ImportOnly" || "ActivateOnly" || "ImportActivate"

"storageInfo": { // storageUrl points to the storage container
"storageUrl":"[Link]
paasdevoic/
cloneRepo",
"storageUser":"myemail@[Link]",
"storagePassword":"generated_token"
}
}

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-
[Link]
",
"importActivateMode": "ImportActivate",
// options are "ImportOnly" || "ActivateOnly" || "ImportActivate"
"storageInfo": {
"storageUrl":"[Link]
[Link]/
v1/paasdevoic/cloneRepo",
"storageUser":"myemail@[Link]",
"storagePassword":"generated_token"
}
}

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-[Link]",
"importActivateMode": "ImportOnly", "storageInfo":
{ "storageUrl":"https://
[Link]/v1/paasdevoic/
cloneRepo","storageUser"
:"myemail@[Link]", "storagePassword":"generated_token"}}' -u
admin:password
[Link]

5-9
 Chapter 5
Migrate Process Design-Time Metadata into Oracle Integration

Possible sample output from this command is as follows:

{
"jobId":"554",
"status":"NOT_STARTED"
}

2. Check the status of the import operation using a postman or curl (as shown
below) command:

curl -k -v -X GET -u admin:password [Link]

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
}
]
}

3. Log in to your Oracle Integration instance.

4. Browse the pages and note that the design-time metadata you exported from your
Oracle Integration Classic instance are now visible. For example, for Integrations,
look for integrations, connections, lookups, and more. For Processes, look for
process applications and decision models.

Migrate Process Design-Time Metadata into Oracle

Integration
As an administrator, you can import your Process design-time metadata (process
applications and decision models) into Oracle Integration. The import tool provides

5-10
 Chapter 5
Migrate Process Design-Time Metadata into Oracle Integration

migration flexibility: choose to migrate the entire instance, a selected space, or individual
items.
• Import Process Design-Time Metadata
• Import Using the Import Command Line Utility

Import Process 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 [Link]
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.

5-11
 Chapter 5
Migrate Process Design-Time Metadata into Oracle Integration

7. Review the import log.

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. (Using the import tool, however, is strongly
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 ImportTool 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 [Link] srcType=PCS srcHost=[Link]
srcUser=user srcPass=password oicHost=[Link] oicUser=user
oicPass=password scope=scope

5-12
 Chapter 5
Migrate Process Design-Time Metadata into Oracle Integration

Example: Import the entire Oracle Process Cloud Service instance

$java -jar [Link] srcType=PCS srcHost=http://
[Link] srcUser=user1 srcPass=password1 oicHost=http://
[Link] oicUser=user1 oicPass=password1 scope=SPACE
srcSpace="123456789"
Example: Import process applications (delimit items by pipe line)
$java -jar [Link] srcType=PCS srcHost=http://
[Link] srcUser=user1 srcPass=password1 oicHost=http://
[Link] oicUser=user1 oicPass=password1 scope=PROJECT
srcSpace="132457689” srcProject="Loan Application|Travel Application"
oicSpace=”123456789”
6. 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.
7. 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.

5-13
6
Manage Oracle Integration
Oracle is responsible for maintaining the infrastructure on which Oracle Integration is built.
An administrator can increase or decrease the number of message packs for an instance,
delete an instance, view activity for an instance and can export diagnostic information if
problems occur in Oracle Integration.

Note:
Life cycle management tasks such as starting an instance, stopping an instance,
and so on may fail if the host is being upgraded or backed up. Retry the life cycle
management tasks in two hours. Any ongoing design-time/runtime functionality is
not impacted.

Topics:
• Scale an Oracle Integration Instance
• Start or Stop an Oracle Integration Instance
• Manage Integrations and Errors
• Manage SSL Certifications
• Manage Integration and Process Instance History
• Configure Settings for Error Logs
• Delete an Oracle Integration Instance
• Change the BYOL Metering Option of an Existing Instance

6-1
 Chapter 6
Scale an Oracle Integration Instance

Note:
Oracle Integration takes regular internal backups on your managed instance
to restore it in the event of a failure of underlying infrastructure resources.
You cannot request an explicit backup checkpoint or restore an instance to a
prior state. Oracle recommends that you use the integration level export
commands to take periodic copies of your design-time metadata and
configuration and use the corresponding import APIs to restore.
You can also use resource level APIs to perform the same tasks depending
on whether you want to use storage or source control for backups, need to
back up specific/critical resources, and so on.
See:
• Export and Import Integration and Process Design-Time Metadata
Between Instances with the REST APIs
• REST API for Oracle Integration
• Import and Export Integrations
• Manage Packages

Scale an Oracle Integration Instance

You can increase or decrease the number of message packs for your instance based
on the demand. The maximum number of message packs for an instance is based on
your license type. For a bring your own license type (BYOL), the instance can have a
maximum of 3 message packs and each message pack adds 20K Messages per Hour
Pack to your instance. If you don’t have a BYOL license type, the instance can have a
maximum of 12 message packs and each message pack adds 5K Messages per Hour
Pack to your instance.
To increase or decrease the message pack:
1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.
3. Access the Oracle Integration instance. See Access Oracle Integration from the
Oracle Cloud Infrastructure Console.

4. Click adjacent to the instance name and select Scale Instance.

The Scale Instance dialog opens.
5. In the Scale Instance dialog, specify the following options:
• Type of change, increase or decrease: Select Increase capacity to add
message pack to your instance or select Decrease capacity to remove the
message pack from your instance.
• Enter the number of 20K Messages Per Hour Packs: Enter a number of
message packs that you want to increase or decrease. This is an example of
BYOL license and thus shows 20K Messages Per Hour Packs.

6-2
 Chapter 6
Start or Stop an Oracle Integration Instance

6. Click Scale Instance.

For a successful scaling request, you’ll see the following message in the Service
Overview page:
Your scaling request was accepted.

7. After a few moments, click Refresh to update the page.

You might need to click the icon more than once to see any change to the page.
8. Note the change in the number of message packs in the Overview page has changed as
per your scaling request.

Start or Stop an Oracle Integration Instance

You can start or stop all nodes in an Oracle Integration instance cluster. Billing is stopped for
the duration that the instance is stopped.
To start or stop all nodes in an instance cluster:
1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.
3. Access the Oracle Integration instance. See Access Oracle Integration from the Oracle
Cloud Infrastructure Console.
4. Identify the instance to start or stop.
To start all nodes in an instance cluster:

a. From the menu to the right of the instance name, select Start.
b. Click Yes when prompted to confirm your selection.
To stop all nodes in an instance cluster:

a. From the menu to the right of the instance name, select Stop.
b. Click Yes when prompted to confirm your selection.
This action causes the following:
• Billing is stopped for the duration that the instance is stopped.
• Integration endpoints are quiesced.

6-3
 Chapter 6
Manage Integrations and Errors

• Process instances are quiesced.

• Runtime is quiesced.
• Scheduled integrations do not execute.
• Database purging continues to run.
• REST APIs are available for use.
• Design time is available for use.

Manage Integrations and Errors

You can manage integration and process errors in Oracle Integration.
Activate the service in Oracle Integration when the integration is ready to go live and
you can deactivate an active Integration. You can modify or clone the integration.
Delete an integration that is no longer needed. See Manage Integrations in Using
Integrations in Oracle Integration.
You can manage errors from the Errors pages in Oracle Integration at the integration
level, connection level, or specific integration instance level. See Manage Errors in
Using Integrations in Oracle Integration.

Manage SSL Certifications

You can upload and update security certificates in Oracle Integration to validate
external connections.
Certificates are used to validate outbound SSL connections. If you make an SSL
connection in which the root certificate does not exist in Oracle Integration, an
exception is thrown. In that case, you must upload the appropriate certificate. A
certificate enables Oracle Integration to connect with external services. If the external
endpoint requires a specific certificate, request the certificate and then upload it into
Oracle Integration. You can update or delete certificates you uploaded into Oracle
Integration.
For more information about managing SSL certificates in Integrations, see Managing
Security Certificates in Using Integrations in Oracle Integration.
For more information about managing SSL certificates in Processes, see Manage
Security Certificates during Runtime and Manage Security Certificates during Design
Time in Using Processes in Oracle Integration.

Manage Integration and Process Instance History

You can determine when to purge the data in your database. You can also view the
notification and quiesced thresholds for your database and the percentage of the
database that has been used.
For integration instance data, set retention and purging settings. See Set Data
Retention for Runtime Instances.
Process instance history is automatically purged periodically, based on settings in
Oracle Integration. See Archive and Purge Data in Using Processes in Oracle
Integration.

6-4
 Chapter 6
Configure Settings for Error Logs

Configure Settings for Error Logs

Need to troubleshoot errors? As an administrator, you can change logging levels and
download logs for Oracle Integration.
Use caution when changing logging levels because increasing them can affect performance.
Reset logging levels back to default settings after troubleshooting.
1. From the Home page, select Settings, then Logging.
The Logging screen is displayed. By default, loggers are contained within folder
containers, and the number of loggers contained (collapsed) within the folder is listed
after the folder name.

2. Filter and sort the logging list.

You can filter in several ways:
• Show Only: Select one or more options to limit the list. Note that loggers or folders
must meet all selected options to be listed.
– Oracle Integration Cloud: Displays loggers related to Oracle Integration
components.
– Top Containers: Displays the two top levels of folder containers.
– Unsaved Changes: Displays loggers whose levels you have changed but
haven’t saved, as indicated by an Unsaved icon.

• Filters Menu: Select Open Filters Menu to view loggers by their status (at
default, or increased or decreased) or by their selected logging level. Filter settings
display below the search field as you specify search criteria.
3. Search for logs.
In the Search field, enter a logger name (or partial name) and press Enter. Searching is
case sensitive. For example, enter [Link] to list all loggers that begin with those

6-5
 Chapter 6
Upload an SSL Certificate

characters. Note that searching is performed within the filtered list. For example, if
the Top Containers filter is selected, only the top containers are searched.
4. Change logging levels as needed.
• Use the up and down icons in the Logging Level column to change a logger
level. As you increase or decrease, an unsaved icon displays adjacent to the
new logging level to indicate unsaved changes. The Status column indicates
whether you increased or decreased the level and lists the default level.
• When a logging level lists Inherited, this indicates that its own current level is
inherited from its parent package because it doesn’t have a default level set.
Children packages may have a different level. Changing a package level will
automatically change the logging level of its children if they inherit from it (if
they don’t have a specific logging level set).
• To return to previous settings, click Revert and revert to either the last saved
configuration or set all levels back to their default level.
5. Save your changes. Download logs as needed.
Click Download Logs and save the entire logging file to a zip file.

Upload an SSL Certificate

Certificates are used to validate outbound SSL connections. If you make an SSL
connection in which the root certificate does not exist in Oracle Integration, an
exception is thrown. In that case, you must upload the appropriate certificate. A
certificate enables Oracle Integration to connect with external services. If the external
endpoint requires a specific certificate, request the certificate and then upload it into
Oracle Integration.
To upload an SSL certificate:
1. In the left navigation pane, click Home > Settings > Certificates.
All certificates currently uploaded to the trust store are displayed in the Certificates
dialog. The

link enables you to filter by name, certificate expiration date, status, type, category,
and installation method (user-installed or system-installed). Certificates installed
by the system cannot be deleted.

2. Click Upload at the top of the page.

The Upload Certificate dialog box is displayed.

6-6
 Chapter 6
Upload an SSL Certificate

3. Enter an alias name and optional description.

4. In the Type field, select the certificate type. Each certificate type enables Oracle
Integration to connect with external services.
• X.509 (SSL transport)
• SAML (Authentication & Authorization)
• PGP (Encryption & Decryption)

X.509 (SSL transport)

1. Select a certificate category.
a. Trust: Use this option to upload a trust certificate.
i. Click Browse, then select the trust file (for example, .cer or .crt) to upload.
b. Identity: Use this option to upload a certificate for two-way SSL communication.
i. Click Browse, then select the keystore file (.jks) to upload.
ii. Enter the comma-separated list of passwords corresponding to key aliases.
iii. Enter the password of the keystore being imported.

c. Click Upload.

SAML (Authentication & Authorization)

1. Note that Message Protection is automatically selected as the only available certificate
category and cannot be deselected. Use this option to upload a keystore certificate with
SAML token support. Create, read, update, and delete (CRUD) operations are supported
with this type of certificate.
2. Click Browse, then select the certificate file (.cer or .crt) to upload.
3. Click Upload.

PGP (Encryption & Decryption)

1. Select a certificate category. Pretty Good Privacy (PGP) provides cryptographic privacy
and authentication for communication. PGP is used for signing, encrypting, and
decrypting files. You can select the private key to use for encryption or decryption when
configuring the stage file action.
a. Private: Uses a private key of the target location to decrypt the file.
i. Click Browse, then select the PGP file to upload.
ii. Enter the PGP private key password.
b. Public: Uses a public key of the target location to encrypt the file.
i. Click Browse, then select the PGP file to upload.
ii. In the ASCII-Armor Encryption Format field, select Yes or No. Yes shows the
format of the encrypted message in ASCII armor. ASCII armor is a binary-to-
textual encoding converter. ASCII armor formats encrypted messaging in ASCII.
This enables messages to be sent in a standard messaging format. This
selection impacts the visibility of message content. No causes the message to be
sent in binary format.

6-7
 Chapter 6
Monitoring Billable Messages

iii. From the Cipher Algorithm list, select the algorithm to use. Symmetric-
key algorithms for cryptography use the same cryptographic keys for both
encryption of plain text and decryption of cipher text.
c. Click Upload.

Monitoring Billable Messages

As an administrator, you can monitor the number of billable messages consumed in a
selected Oracle Integration or Oracle Integration for SaaS instance.

Oracle Integration consumption models

The type of license you choose determines how message packs are defined and
metered. The Usage Metrics page is different for Oracle Integration versus Oracle
Integration for SaaS.
• For Oracle Integration:
– BYOL: For Bring Your Own License users, one message pack is defined as
20,000 messages per hour. You can select up to 3 message packs if you bring
an existing Oracle Fusion Middleware license to the cloud.
– Non-BYOL: For these license types, one message pack is defined as 5,000
messages per hour. You can select up to 12 message packs if you create a
new Oracle Integration license in the cloud.
• For Oracle Integration for SaaS, usage is tracked on a monthly basis in packs of
one million messages per month, which keeps costs predictable even when you
have unpredictable hourly volumes. Usage is reported monthly instead of hourly.
You can select up to 43 message packs.

Oracle Integration features included

Usage metrics cover the following features.

Oracle Integration Feature Usage

Integration For details on how Integration billable messages are
calculated, see About Integrations Usage.
Process Process metering tracks the number of concurrent, unique
users interacting within a 1 hour interval. Sizing is based on
concurrent users, which are converted to message packs.
One Process user/hour is equivalent to 400 messages/hour.
For details on how Process billable messages are calculated,
see About Process Usage.

Note:
Internal calls within the same Oracle Integration instance aren't counted as
messages. See each usage section to understand how messages are
counted when features are used together.

6-8
 Chapter 6
Monitoring Billable Messages

Viewing usage metrics

1. On the Home page, select Monitoring in the navigation pane, then Usage Metrics.
The Usage Metrics page is displayed.

Note:
Data metrics are displayed using UTC standard time.

• For Oracle Integration

The Usage Metrics page shows the total messages used during each hour of a
selected day. In the example illustration below, the blue Configured 5K line shows
that the Oracle Integration instance was configured for 5,000 messages per hour
during provisioning. Values below the configured usage are shown in light pink and
values above it are shown in dark pink.
– To view messages consumed on a different date, select a date using the View
calendar.
– Hover the cursor over an hour time period to view its approximate message
consumption.

– Click in the upper right of the screen to expand a table that lists each hour
and its billable messages for the selected day.

• For Oracle Integration for SaaS

The Usage Metrics page for SaaS shows the total messages used during each
month. In the example illustration below, the blue Configured 5M line shows that the
Oracle Integration for SaaS instance was configured for 5 million messages per
month during provisioning. Values below the configured usage are shown in light pink
and values above it are shown in dark pink.
– To view messages consumed during a different timeframe, select another
timeframe using the View calendar.
– Hover the cursor over a month time period to view its approximate message
consumption.

6-9
 Chapter 6
Monitoring Billable Messages

– Click in the upper right of the screen to expand a table that lists each
month and its billable messages.

2. Export usage metrics to a CSV file, if needed.

a. Click Export.
b. In the Export Usage Metrics dialog, select a start date and end date and click
Export.
Each hour is depicted as a record. A maximum of 1000 hours of information
(shown as lines in the CSV file) can be exported.
c. Use your browser's download list to access the CSV file.
The exported file shows columns for the date, configured messages, and total
messages consumed.

6-10
 Chapter 6
Monitoring Billable Messages

3. If needed, change the Oracle Integration instance's configured message packs. See
#unique_93.

About Integrations Usage

When creating Oracle Integration instances, administrators specify the number of message
packs they plan to use for per instance.

Rules for tracking Integration billed messages

Follow these rules to determine how message consumption is calculated.

Number Rule Description

1 Trigger Each trigger activity counts as at least one message, up to 50KB inbound. If the
inbound message payload exceeds 50KB, 1 additional message is counted for each
additional 50KB.
2 Invoke Invoke requests don't count as messages, but invoke responses over 50KB count. If
the message payload exceeds 50KB, 1 additional message is counted for each
additional 50KB.
3 File For file based scheduled flows where there are incoming files into integrations, each
file is converted into a billed message (in multiples of 50KB) only when the size is
greater than 50KB.
4 Internal Internal calls within the same Oracle Integration instance aren't counted as
messages. For example, the following aren't counted:
• Process to Integration
• Visual Builder to Integration
• Integration to Integration
Calling another Oracle Integration instance does incur messages in the target Oracle
Integration instance, and, depending on the response size, may also incur messages
in the calling Oracle Integration instance.

Integration Usage Examples

This table shows by example how message billing is calculated and the rules that apply.

Integration Scenario/Flow Billing Message Calculation Rules That

Type Apply
Sync/Async 1. Eloqua inbound with 40KB Payload size is considered at #1 (Trigger)
(Trigger) payload. trigger.
ceil(40/50) = 1 message
2. Data transformation.
3. External invoke to push data
to Sales Cloud.

Sync/Async 1. REST inbound with 120KB Payload size is considered at #1 (Trigger)

(Trigger) payload. trigger.
ceil(120/50) = 3 messages
2. Data transformation.
3. External invoke to push data
to Logfire.

6-11
 Chapter 6
Monitoring Billable Messages

Integration Scenario/Flow Billing Message Calculation Rules That

Type Apply
Sync/Async 1. SOAP inbound with 70KB Payload size is considered at #1 (Trigger)
(Trigger) payload. trigger. Any subsequent #3 (File)
response greater than 50KB is
2. Download files in a loop. also tracked. In this scenario,
only files greater than 50KB are
3. 3 files downloaded of sizes considered.
20KB, 170KB, and 40KB,
respectively. ceil(70/50) + ceil(170/50) = 2 +4
= 6 messages
4. Data transformation/
enrichment.
5. External invoke to push data
to an external system via
REST.

Sync/Async 1. Database adapter pulling in Payload size is considered at #1 (Trigger)

(Trigger) 20KB data and 2 rows. trigger. Any subsequent
response greater than 50KB is
2. For each row, 1 outbound also tracked.
REST invoke is made, which ceil (20/50) = 1 message
results in 20KB data for
each invoke.
3. Data enrichment/
transformation.
4. FTP to an external location.

Sync/Async 1. SOAP inbound with 10KB Payload size is considered at #1 (Trigger)

(Trigger) payload. trigger. Any subsequent #2 (Invoke)
response greater than 50KB is
#3 (File)
2. Download files in a loop. also tracked.
Two files downloaded of ceil(10/50)+ ceil (70/50) +
sizes 20KB and 70KB, ceil(100/50) = 1+2+2 = 5
respectively. messages
3. External invoke to get
further data via REST
adapter. Returns 100KB
data.
4. FTP to an external location.

Sync/Async 1. Simple REST GET request Payload size is considered at #1 (Trigger)

(Trigger) with template parameters trigger. Any subsequent
without payload. response greater than 50KB is
also tracked. Since the trigger is
2. Call to Oracle Service Cloud just a GET request with no
to get contact details. payload, it's considered 1 billed
Returns a response of message.
40KB. 1 message
3. Return the contact data.

6-12
 Chapter 6
Monitoring Billable Messages

Integration Scenario/Flow Billing Message Calculation Rules That

Type Apply
Scheduled flow 1. Scheduled trigger. Each invoke/file is considered in #3 (File)
multiples of 50KB when
2. Download files in a loop. response data is more than
Three files downloaded of 50KB.
sizes 20KB, 170KB, and ceil(170/50) = 4 messages
40KB, respectively.
3. Data transformation.
4. External invoke to transfer
data which results in 10
bytes of response.

Scheduled flow 1. Scheduled trigger. Each invoke/file is considered in None

multiples of 50KB when
2. Database adapter pulling in response data is more than
30KB data and 10 rows. 50KB.
3. Data transformation. Not counted.

4. External invoke to transfer

data which results in 5 bytes
of response.

Scheduled flow 1. Scheduled trigger. Each invoke/file is considered in #3 (File)

multiples of 50KB when
2. External SOAP invoke to get response data is more than
data via BIP reports. 50KB.
Returns 130KB data. ceil(130/50) = 3 messages
3. External invoke to get
further data via REST
adapter. Returns 10KB data.
4. Data transformation.
5. External invoke to transfer
data which results in 5 bytes
of response.

Scheduled flow 1. Scheduled trigger. Each invoke/file is considered in #2 (Invoke)

multiples of 50KB when
2. Download files in a loop. response data is more than
Two files downloaded of 50KB.
sizes 20KB and 40KB, ceil(100/50) = 2 messages
respectively.
3. External invoke to get
further data via REST
adapter. Returns 100KB
data.
4. FTP to an external location.

6-13
 Chapter 6
Monitoring Billable Messages

Integration Scenario/Flow Billing Message Calculation Rules That

Type Apply
Scheduled flow 1. Scheduled trigger. Each invoke/file is considered in #4 (Internal)
multiples of 50KB when None counted
2. External invoke to get data response data is more than
via REST adapter. Returns 50KB.
10KB data. Not counted.
3. Data transformation.
4. External REST invoke to
transfer data which results in
500 bytes of response.

Child 1. A parent Integration flow Integration child flow invoke is #4 (Internal)

Integration flow calls a child Integration flow waived from metering. None counted
via REST in a loop. Not counted. Note that the
parent may count.
2. The child Integration flow
sends a notification email
with the information passed
from a parent flow.
3. Child flow execution
completes.

Child 1. Parent Integration flow Integration child flow invokes are #2 (Invoke)
Integration flow downloads a CSV file via the waived from metering. Any
FTP adapter. The CSV subsequent response is
contains 5 rows. metered.
Each child = ceil(70/50) = 2
2. Each row in the CSV file messages
calls a child Integration child
Note that the parent may count.
flow.
a. The child Integration
flow reads a orderid
passed as an input.
b. Invokes a request to
Oracle Service Cloud to
get data about the
order. Each invoke
returns 70KB data.
c. Data transformation in
child flow.
d. Pushes the data via an
FTP adapter to write it
to a file.
e. Child execution
completes.

6-14
 Chapter 6
Monitoring Billable Messages

Integration Scenario/Flow Billing Message Calculation Rules That

Type Apply
Pub/Sub Flows 1. Single publisher flow with Pub counts as 1 message. #1 (Trigger)
REST trigger as 30 KB Sub is waived on trigger.
payload.
2. Single subscriber to the
above which processes data
and sends it to an external
service.

Pub/Sub Flows 1. Single publisher flow with Pub counts as 1 message. #1 (Trigger)
REST trigger as 30KB Sub trigger is waived. However, #2 (Invoke)
payload. the invoke is metered when the
response is greater than 50KB.
2. Single subscriber to the So the sub flow in this case
above which processes counts as 2 messages.
data.
3. Sub flow calls OSC to get a
response back as 70KB.
4. Sub flow completes.

About Process Usage

When creating Oracle Integration instances, administrators specify the number of message
packs they plan to use for per instance.

Process message metering

Process metering tracks the number of concurrent, unique users interacting within a 1 hour
interval. Sizing is based on concurrent users, which are converted to message packs. One
Process user/hour is equivalent to 400 messages/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.
• 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.

6-15
 Chapter 6
Monitoring Billable Messages

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).

Process Usage Examples

This table shows by example how message billing is calculated and the rules that
apply.

Scenario Type Scenario Billing Message Calculation

Process Between 9am and 10am, 20 employees The 9am-10 am hour block
Workspace access Workspace. Within the one hour reports 15 concurrent users (5
timeframe: created new instances and 10
• 5 users (user1 through user5) create processed tasks).
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.
Process Between 10 and 11am, 10 users access The 10am-11am hour block
Workspace and Workspace and 5 access the Oracle reports 13 concurrent users (10
mobile app Process Mobile app. Within the one hour workspace users plus 3 mobile
timeframe: users performed update/write
• 10 users (user1 through user10) operations, while 2 mobile users
create new process instances and did not perform any update/write
also approve at least 1 task total. operations).
• 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.
Process Between 11am and 12pm, 5 users access The 11am-12pm hour block
Workspace and Oracle Integration from a Visual Builder reports 7 concurrent users (2
Visual Builder application and 5 other users access Visual Builder users and 5
Workspace. Workspace users performed
• 2 of the 5 Visual Builder users update/write operations). This
access Visual Builder, and interact result does not include the
with a Visual Builder app that in turn Visual Builder concurrent user
triggers execution of an API that licenses. Visual Builder
creates new process instances and concurrent users are metered
processes tasks. separately.
• 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.

6-16
 Chapter 6
Set Data Retention for Runtime Instances

Set Data Retention for Runtime Instances

Specify how long to keep Oracle Integration historical data under standard or low space
conditions and whether data is purged when low space is reached. You can also perform an
immediate manual purge if needed.

Note:
Several settings on this page, including Purge When Low Space Reached and
Perform Manual Purge, affect Process runtime instances as well as Integration
data. To set Process data retention, see the Purge Retention field described in
Schedule Instances Archive and Purge in Using Processes in Oracle Integration.

1. Display data retention settings.

• In the Oracle Integration navigation pane, select Settings, then Data Retention.
• Alternately, if your instance goes into quiesced mode due to lack of space, a
message appears with a button directing you to this screen to adjust data retention
settings.
The Data Retention screen is displayed.
2. Under Data Retention Status, view your Oracle Integration instance’s data retention
status at any time.
You’ll see one of these statuses:
• Good: Indicates that Oracle Integration is retaining instances according to selected
standard settings, and space is currently available.
• Warning: Indicates that warning (low space) settings are in effect.
• Critical: Indicates that space is critical. Until more space becomes available, Oracle
Integration rejects incoming requests and stops all processes and integrations from
running.
3. Under Standard Settings, specify how long to retain Integration instances.
• In the Time Unit fields, specify a time unit (days or hours) for the Keep settings
below.
• Specify standard Integration retention:
– Specify a time unit (days or hours) to keep successful Integration instances,
meaning those that are waiting, running, completed successfully, or with a
recoverable fault.
– Specify how long to keep faulted Integration instances, meaning those that have
faulted without the possibility of recovery. You can choose to keep the faulted
instances data around longer to attempt fault recoveries.
4. Under Warning (Low Space) Settings, specify how long to retain Integration instances.
You must select warning settings lower than your standard settings.
• The Purge When Low Space Reached field determines whether Integration and
Process runtime data is automatically purged without reclaiming database space.

6-17
 Chapter 6
Delete an Oracle Integration Instance

Note that when this field is selected and low space is reached, Process
runtime instances are also deleted.
• In the Time Unit fields, specify a time unit (days or hours) for the Keep
settings below.
• Specify low space Integration retention:
– Specify a time unit (days or hours) to keep successful Integration
instances, meaning those that are waiting, running, completed
successfully, or with a recoverable fault, under low space conditions.
– Specify how long to keep faulted Integration instances, meaning those that
have faulted without the possibility of recovery, under low space
conditions. You can choose to keep the faulted instances data around
longer to attempt fault recoveries.
5. If needed, click Perform Manual Purge to perform a manual purge of all
Integration and Process runtime data.
Clicking the purge button opens a side pane, where you specify:
• Whether to purge Integration (and Process) runtime data
• Time Unit (Days)
• Number of items to purge
For example, if your usage is very high, you may choose to purge all successful
instances within one hour of completion. Instance data older than the retention
values specified is purged immediately when you click Purge Now.

Note:
Use this option with care. It immediately purges older Integration and
Process data. This is a one-off procedure and cannot be undone.
Automated purges continue to run.

6. At any point, click Revert to restore all data retention settings to their default
values.
7. Click Save.

Delete an Oracle Integration Instance

You can delete an Oracle Integration instance. To do so, you must delete the stack of
which the instance is a part.
When an Oracle Integration instance is deleted, the Oracle Database Cloud Service
database deployment is deleted.
If you want to delete an instance in an Oracle Integration Classic (user-managed)
environment, see Delete an Oracle Integration Classic (User-Managed) Instance.
To delete an instance:
1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.

6-18
 Chapter 6
Change the BYOL Metering Option of an Existing Instance

3. Access the Oracle Integration instance. See Access Oracle Integration from the Oracle
Cloud Infrastructure Console.
4. In the Oracle Integration Instances console, identify the instance you want to delete.

5. Click adjacent to the instance name and select Delete.

6. In the Delete dialog that opens, select the Force service deletion check box, if you want
the service instance to be deleted even if the database deployment cannot be reached to
delete the database schemas.
7. Click Delete.

Change the BYOL Metering Option of an Existing Instance

The bring your own license (BYOL) metering option enables you to bring your existing Oracle
Fusion Middleware license to use with Oracle Integration or other cloud services. You can
change the BYOL metering option of an already existing instance, as necessary.
This feature is useful for the following scenarios:
• You selected the wrong option when creating a new Oracle Integration instance and need
to change it.
• You need to shift the location of an on-premises license in the cloud. For example, you
need to move the license from one Oracle Integration instance to another or even to a
different type of cloud service instance such as Oracle SOA Cloud Service.
1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.
3. Access the Oracle Integration instance. See Access Oracle Integration from the Oracle
Cloud Infrastructure Console.

4. Click adjacent to the instance you want to change and select Change License Type.
5. Select the option required for your environment.
• The first option enables you to select to bring an existing Oracle Fusion Middleware
license to the cloud for use with Oracle Integration.
• The second option enables you to select the regular billing rate (non-BYOL), which is
a regular cloud subscription as if you did not own any on-premises licenses.

6-19
 Chapter 6
Change the BYOL Metering Option of an Existing Instance

In this example, which may have been metering as BYOL, the license is now
switched to non-BYOL (the regular subscription rate). This action eliminates the
need to recreate and upgrade your data to a new instance for a simple change
such as the billing rate. In your next hourly metering report, this instance reflects
the new billing rate. If you toggle back and forth within an hour, you most likely do
not see any change because it is only reported once per hour.

6-20
7
Troubleshoot Oracle Integration

Topics:
• Resume Use of a Suspended Oracle Integration for Oracle SaaS Account

Resume Use of a Suspended Oracle Integration for Oracle

SaaS Account
Your Oracle Integration for Oracle SaaS account can be suspended under the following
scenarios:
• When you create an instance using an Oracle Integration for Oracle SaaS account, you
see options for Integration (Standard Edition) and Integration and Process (Enterprise
Edition). If you create the instance without the corresponding entitlement, the account is
suspended.
• Nothing prevents you from creating instances or scaling instances to increase capacity
that exceeds your account quota limit. When this occurs, your account is suspended.
If your account get suspended, here are some procedures to follow to resume use of your
account.
• If you create an instance that is not entitled (for example, you created an Integration and
Process instance when using a Standard Oracle Integration for Oracle SaaS account,
you can delete the instance and wait for an hour or so to refresh your billing metrics, at
which time the account is resumed.
• If your account has the correct entitlement, but uses more resources than the quota limit,
you can:
– Order more resources to expand the account.
– Stop some instances so that the total number of message packs in the running
instances in the account stay within account quota. After an hour or so, the account
can be resumed. Then, scale an instance to decrease capacity until the total usage is
no more than the account quota. Then, start the previously stopped instance, as
needed.
– Delete an instance that is no longer needed to bring usage below the quota limit.

7-1
Part I
Administer Oracle Integration Classic (User-
Managed)
This part describes tasks that are unique to provisioning, administering, and troubleshooting
in Oracle Integration Classic (user-managed).

Topics:
• Ready, Set Up, Go in Oracle Integration Classic (User-Managed)
• Manage Oracle Integration Classic (User-Managed)
• Troubleshoot Oracle Integration Classic (User-Managed)
8
Ready, Set Up, Go in Oracle Integration
Classic (User-Managed)
You use the Oracle Cloud Infrastructure Console to install instances of Oracle Integration
Classic (user-managed).

Topics:
• Assign the Correct User Roles to Create an Instance
• Provision Oracle Integration Classic (User-Managed) on an IP Network
• Create an Oracle Integration Classic (User-Managed) Instance
• About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle
Integration Classic (User-Managed)
• Support the Minimum Version of Oracle Integration Classic (User-Managed)

Assign the Correct User Roles to Create an Instance

If you are the user that initially signed up and purchased universal credits for Oracle Cloud,
you automatically have the necessary service entitlement roles to create Oracle Integration
Classic (user-managed) instances. Otherwise, the correct roles must be explicitly assigned to
your user account to create Oracle Integration Classic instances. Without the necessary
roles, creation fails.
To successfully create Oracle Integration Classic instances, ensure that your user account is
assigned the following roles for these services:
• Compute Classic - Service Entitlement (Compute.Compute_Operations)
• Container Classic - Service Entitlement (OCCS_ADMINISTRATOR) (Unless someone
else with this role initializes the replication policy.)
• Database - Service Entitlement (DBaaS_Administrator)
• Database Backup - Service Entitlement (DatabaseBackup_Administrator)
• IntegrationCloud - Service Entitlement
(INTEGRATIONCLOUD_ENTITLEMENT_ADMINISTRATOR)
• Load Balancer Classic - Service Entitlement (LBAAS_ADMINISTRATOR)
To add new users and assign roles, see Add a User and Assign Roles to a User. When
following those instructions, note that you must select Platform Services, then Integration

Classic from the menu to access Oracle Integration Classic.

8-1
 Chapter 8
Provision Oracle Integration Classic (User-Managed) on an IP Network

Note:
The Identity Cloud - Service Entitlement (Identity Domain Administrator) role
has super user privileges for the identity domain. Users with this role can
manage users, groups, applications, and system configuration settings. They
can also perform delegated administration by assigning users to different
administrative roles.

Provision Oracle Integration Classic (User-Managed) on an

IP Network
If you want to provision Oracle Integration Classic (user-managed) on an IP network,
follow the steps described in this section.

Note:
There is support for only one public, dedicated, virtual Oracle Load Balancer
as a Service at a time. You cannot create multiple services at a time.

Prerequisites
• Start the Oracle Integration Classic provisioning wizard and check the value in the
IP Network drop-down list. If the Region and IP Network lists are not visible,
contact Oracle Support Services. This value is required when creating the JSON
file used to create the virtual Oracle Load Balancer as a Service.
• Obtain the compute site value. This value is required when creating the JSON file
used to create the virtual Oracle Load Balancer as a Service.
1. On the Dashboard page, select Open Service Console from the hamburger
menu in the Compute Classic tile.

2. Click the Sites value at the top of the page.

3. Copy the value in the Site field.

8-2
 Chapter 8
Provision Oracle Integration Classic (User-Managed) on an IP Network

• Obtain the tenant name value. This value is required when creating the virtual Oracle
Load Balancer as a Service.
1. On the Dashboard page, click the Identity Cloud tile.

2. In the Additional Information section, copy the value from the Identity Service Id
field.

Create an IP Network
To complete this task, you must have the Compute_Operations role. If you do not have this
role, ask your system administrator to assign you this role. See Modifying User Roles in
Managing and Monitoring Oracle Cloud.
1. Sign in to Compute Classic. If your domain spans multiple sites, select the appropriate
site. To change the site, click the Site menu near the top of the page.
2. Click the Network tab.
3. In the Network drop-down list, expand IP Network, then click IP Networks.

8-3
 Chapter 8
Provision Oracle Integration Classic (User-Managed) on an IP Network

4. Click Create IP Network.

5. Select or enter the required information:

Element Description
Name Enter a name for the IP network.

8-4
 Chapter 8
Provision Oracle Integration Classic (User-Managed) on an IP Network

Element Description
IP Address Prefix Enter the IP address prefix for this IP
network, in CIDR format. When you create
instances, you can associate a vNIC on the
instance with an IP network. That vNIC on
the instance is then allocated an IP address
from the specified IP network.
Select the IP address prefix for your IP
networks carefully. Consider the number of
instances that you may want to add to the
network. This helps determine the size of
the subnet required.
If you create multiple IP networks and you
may want to add these IP networks to the
same IP network exchange, then ensure
that you do not allocate overlapping address
ranges to these IP networks.
Similarly, if you plan to connect to your IP
networks using VPN, ensure that the
addresses you specify for your IP networks
do not overlap with each other or the IP
addresses used in your on-premises
network.
Note: RFC 6598 addresses are not
supported.
IP Exchange Specify the IP network exchange to which
you want to add this IP network. An IP
network can belong to only one IP network
exchange. Before you specify an IP network
exchange for an IP network, ensure that the
IP addresses in this IP network do not
overlap with the IP addresses in any other
network in the same IP network exchange. If
you do not specify an IP network exchange
while creating an IP network, you can do so
later by updating an IP network.
If you want to connect IP networks using an
IP network exchange, do this before creating
instances with an interface on those IP
networks. This ensures that routes are
appropriately configured on instances by the
DHCP client during instance initialization.
Description Enter a meaningful description for your IP
network, if required.
Tags Enter a list of the tags that you want to
associate with your IP network, if required.

6. Click Create
The IP network is created and added to the specified IP network exchange.

Find the Oracle Load Balancer as a Service URL for Your Account
You must identify the Oracle Load Balancer as a Service URL.
1. Activate your account after receiving your welcome email. When you log in to Oracle
Cloud Infrastructure Console, you must reset the password.

8-5
 Chapter 8
Provision Oracle Integration Classic (User-Managed) on an IP Network

2. Go to the Dashboard.
3. In the upper right corner, click Customize Dashboard.
4. Find Load Balancer Classic, and click Show.
5. Close the Customize Dashboard dialog.
This enables Load Balancer Classic to be displayed in your Dashboard.
6. Click Load Balancer Classic.
7. In the Additional Information section, find the REST Endpoint field.
8. Copy the value in the REST Endpoint field.
You need this REST endpoint value to run the REST API that creates the public
and private virtual Oracle Load Balancer as a Service.

Create the Public Virtual Oracle Load Balancer as a Service

1. Create a JSON file (for this example, named [Link]) with content
similar to the following. You specify this file when creating the virtual load balancer.

{
"name": "public-explicit-oic",
"disabled": "false",
"scheme": "INTERNET_FACING",
"compute_site": "uscom-central-1",
"ip_network_name": "/Compute-99999999/[Link]@[Link]/
IPNetworkOIC",
}

where:
• name: Specify any name you want to use.
• disabled: Set to false.
• scheme: Specify INTERNET_FACING.
• compute_site: Specify the value you copied in Prerequisites.
• ip_network_name: Specify the name of the IP network you copied in
Prerequisites. The name conforms to the following format:

compartment_name/user_name/subnet_name

For example:

/Compute-99999999/[Link]@[Link]/IPNetworkOIC-IPN

2. Create the virtual Oracle Load Balancer as a Service from the command prompt
on your on-premises host.

curl -i -X POST -u "username:password" -d @[Link]

-H "Content-type:application/
[Link]+json"
-H "X-ID-TENANT-NAME:idcs-xxxxxxxxxxxxxxxx" "https://
[Link]/vlbrs"

8-6
 Chapter 8
Provision Oracle Integration Classic (User-Managed) on an IP Network

where:
• -u: Specify the account username and password you received in the welcome mail.
You changed the password upon initial login.
• -d: Specify the payload file name you created in Step 1. For this example, named
[Link], but this name can be any name you choose.
• -H (first one): Specify Content-type:application/
[Link]+json.
• -H (second one): Specify your unique TENANT-NAME value you copied in Prerequisites
and the REST endpoint value you copied in Find the Oracle Load Balancer as a
Service URL for Your Account. The REST endpoint value must have /vlbrs
appended to the end.
See Troubleshoot cURL Command Issues When Configuring an IP Network.
3. Get the status for the virtual Oracle Load Balancer as a Service. This command should
result in a HEALTHY state response for a successful creation.

curl -i -X GET -u "username:password" -H "Content-type:application/

[Link]+json" -H "X-ID-TENANT-NAME:idcs-
xxxxxxxxxxxxxxxx"
"[Link]
central-1/public-explicit-oic"

Note that the region (for this example, uscom-central-1) and load balancer name (for
this example, public-explicit-oic) are appended to the end of the REST endpoint
URL.
You can also check that the status is healthy from the Oracle Cloud Infrastructure
Console.
4. From the hamburger menu in the upper left corner, select Platform Services > Compute
Classic.
5. Click the Network tab.
6. In the left navigation pane, click the Load Balancers arrow, then select Load Balancers.
The table shows the created load balancer. If it is in a healthy state, the icon on the left
appears as follows.

7. Click the name to display specific details about the load balancer.

8-7
 Chapter 8
Provision Oracle Integration Classic (User-Managed) on an IP Network

Provision Oracle Database Cloud Service

You must provision Oracle Database Cloud Service before using the provisioning
wizard to create an Oracle Integration Classic instance.

Note:
When you provision Oracle Database Cloud Service, specify the same IP
network value that you created in Create an IP Network.

Provision an Instance

1. Follow the steps to invoke the Oracle Integration Classic provisioning wizard.
2. In the IP Network field, specify the IP network you created in Create an IP
Network.
3. Understand the following details about IP networks:
• Oracle Database Cloud Service Behavior:
– When you do not choose Region/IP Network in the provisioning wizard
pages, the Oracle Integration Classic provisioning screens allow you to
choose Oracle Database Cloud Service instances that are not in the IP
network. This is equivalent to non-IP network functionality.
– When you choose the Regions/IP Network option in Oracle Integration
Classic provisioning screens:
* The Oracle Integration Classic provisioning wizard pages list all
Oracle Database Cloud Service entries from all IP networks.
* The Oracle Integration Classic provisioning wizard pages list Oracle
Database Cloud Service entries from the same subnet.
* The provisioning wizard pages do not list Oracle Database Cloud
Service entries from non-IP networks.
* Ensure that you use an Oracle Database Cloud Service instance from
an IP network with which your Oracle Integration Classic instance can
exchange packets. In other words, Oracle Integration Classic and
DBaaS should be in the same IP network or in IP networks that are
connected with an IP exchange.
* Internal IP addresses from the IP network subnet are assigned to VMs
when provisioning completes.
• Updating IP Networks:
– When you update IP networks:
* Ensure that you do not change the IP address of a subnet, only
change the IP prefix.
* Change the IP prefix to expand the current IP network (for example, to
change the prefix from /27 to /8 to expand the network).
* Restart VMs from the Oracle Integration Classic Oracle Cloud
Infrastructure Console as soon as you update an IP network prefix.

8-8
 Chapter 8
Create an Oracle Integration Classic (User-Managed) Instance

Failing to restart the VMs causes console URLs not to work properly during
backup.
• Deleting IP Networks:
– If you plan to delete the IP network/IP exchange, make sure all VMs and
instances are deleted.
– Instances are no longer functional when the IP networks are deleted. Therefore,
the Oracle Enterprise Manager Fusion Middleware Control, Oracle WebLogic
Administration Server, and other consoles are not accessible.
– To re-enable instances, you can recreate the IP networks/IP exchange with the
exact same name and IP subnet (with a similar prefix).
– Every time an instance is deleted, the private IP address is reclaimed by the
subnet.

Support for Multiple IP Networks Using Only One Created Oracle Virtual Load Balancer
as a Service
If you attempt to create more than one Oracle Virtual Load Balancer as a Service (either
public or private) with different IP networks, the REST API request is rejected with the
following warnings:

Only 1 VLBRs can be created with the scheme INTERNAL in a non Oracle Managed
Service https://
lbaas-****" (for private vlbr creation)

and

"Only 1 VLBRs can be created with the scheme INTERNET_FACING in a non Oracle
Managed
Service [Link]

If you want to create multiple IP networks that use only one virtual Oracle Load Balancer as a
Service, you must create an IP exchange connecting multiple IP networks.
1. Create IPNetwork1.
2. Create a virtual Load Balancer as a Service with IPNetwork1.
3. Create IPNetwork2.
4. Create an IP exchange.
5. Add IPNetwork1 and IPNetwork2 into the IP exchange.
6. Provision an Oracle Integration Classic instance with IPNetwork2. The provision
succeeds through with IPNetwork2.

Create an Oracle Integration Classic (User-Managed) Instance

You can no longer create an Oracle Integration instance. If you want to create a new
instance, create an Oracle Integration Generation 2 instance. If you still have Oracle
Integration instances, migrate the instances to Oracle Integration Generation 2.
See Learn About Migrating to Oracle Cloud Infrastructure in Migrating Oracle Integration
Classic Instances to Oracle Cloud Infrastructure.

8-9
 Chapter 8
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration Classic (User-Managed)

About the User Interfaces of the Oracle Cloud Infrastructure

Console for Oracle Integration Classic (User-Managed)
You can perform life cycle management tasks from the Oracle Integration Classic
(user-managed) Oracle Cloud Infrastructure Console.

Topics:
• Explore the Oracle Cloud Infrastructure Console
• Explore the Oracle Cloud Infrastructure Console Instance Overview Page
• Explore the Oracle Cloud Infrastructure Console Activity Page
• Explore the Oracle Cloud Infrastructure Console SSH Access Page
• Explore the IP Reservations Page

Explore the Oracle Cloud Infrastructure Console

You can use the Oracle Cloud Infrastructure Console to view all existing Oracle
Integration Classic (user-managed) instances and to create and delete instances.

The following table describes the key information shown in the Oracle Integration
Classic Oracle Cloud Infrastructure Console.

8-10
 Chapter 8
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration Classic (User-Managed)

Element Description
Click and select an option from the menu to open the service console for one of
the Oracle Cloud Services to which you are subscribed.

(Next to the word ORACLE in the

upper left corner of the page)
Click to sign in to the services to which you are subscribed.

Welcome! Click to display the Oracle Integration Classic Welcome page.

Instances (Summary panel) Number of instances in the identity domain.
OCPUs (Summary panel) Total number of Oracle Compute Units (OCPUs) allocated across all instances.
Memory (Summary panel) Total amount of memory in GBs allocated across all instances.
Storage (Summary panel) Total amount of block storage in GBs allocated across all instances.
Public IPs (Summary panel) Total number of IP reservations allocated across all instances.
Instances (heading) All instances in the identity domain.
Enter a full or partial service instance name to filter the list of service instances
to include only the services that contain the string in their service name.
Create Instance Create a new service instance.
Service instance icon for a created instance. Click this icon to view more details
such as patch availability and backup status.

Status icon indicating that the instance is being created.

Status icon indicating the instance is undergoing maintenance or terminating.

Status icon indicating that the instance has failed to be created. This icon can
also indicate that the service instance has stopped. See the Activity page.
service-name Name of the instance. Click the name to view more details.
Version Version of Oracle WebLogic Server configured for the instance.
Nodes Number of nodes allocated for the instance.
Created On When provisioning is complete, the date and time in UTC at which the instance
was created.
OCPUs Number of OCPUs allocated for the instance.
Memory Amount of memory in GBs allocated for the instance.
Storage Amount of storage in GBs allocated for the instance.

8-11
 Chapter 8
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration Classic (User-Managed)

Element Description

Manage this service Click to select one of the following options based on the service types you have
provisioned:
• Open WebLogic Server Administration Console
• Open Fusion Middleware Control Console
• Open Integration Home Page
• Start— Start Oracle Integration Classic.
• Stop— Stop Oracle Integration Classic.
• Access Rules—Open the Access Rules page, which enables you to create
and manage access rules for selected sources and destinations.
• SSH Access—Add public SSH keys to the VMs that make up this service
instance.
• Delete—Delete the service instance. In the Delete Service dialog box that
opens, set the following options and click Delete:
– Force service deletion—(Optional) Select this checkbox if you want
the service instance to be deleted even if the database deployment
cannot be reached to delete the database schemas. If enabled, you
may need to delete the associated database schemas manually on the
database deployment if they are not deleted as part of the service
instance delete operation.
– Database Administrator User Name—Enter the name of the
database administrator user that was specified when the database
deployment was created. This user owns the instance’s repository and
schemas. If you have specified two databases, specify the name of the
administrator for the database deployment for the Oracle required
schema.
– Database Administrator User Password—Enter the database
administrator user password for the database deployment that contains
the Oracle required schema.
• Skip Backup—Select to skip the backup of the terminated instance.
Instance Create and Delete Shows details about created or deleted service instances.
History • Range—Specifies a range of days for which you are interested in viewing
created and failed service instances.
• Show only failed attempts—Check this box if you want to see failed
attempts only.
• Details—Displays system messages logged during the creation or deletion
process. Messages include information about auto-retry attempts.

Explore the Oracle Cloud Infrastructure Console Instance Overview

Page
You can use view overview information for a specific instance. To access this page,
click an instance name or icon in the Oracle Cloud Infrastructure Console.
The instance overview page consists of the following sections:
• Overview Tile
• Administration Tile — Backup Tab
• Administration Tile — Patching Tab

Overview Tile

8-12
 Chapter 8
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration Classic (User-Managed)

The following table describes the key information shown on the Instance Overview tile.

Element Description
The Overview tile displays information about the service instance. It contains
the following four sections:
• Service Overview — Overview information about the service instance
• Oracle Load Balancer — Information about the Oracle Load Balancer
• Associations — Information about the Oracle Database Classic Cloud
Service database deployment used by the service instance

• Expand the turner icon to expose the following information about the
service instance:
– Location
– Description
– Service Level
– Edition
– Metering Frequency
– Identity Domain
– Created By
– Created On
– Entitlement ID
• Click the text Oracle Integration Classic to return to the main Oracle
Cloud Infrastructure Console page.
• Lists the name of the selected service instance.

8-13
 Chapter 8
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration Classic (User-Managed)

Element Description

Manage this service Click to select one of the following options based on the service types you have
(adjacent to the service instance provisioned:
name) • Open WebLogic Server Administration Console — Open the Oracle
WebLogic Server Administration Console to administer your application
environment.
• Open Fusion Middleware Control Console — Open Fusion Middleware
Control to administer your application environment.
• Open Oracle Integration Home Page — Open the Oracle Integration
home page.
• Start — Start the Oracle Integration instance.
• Stop — Stop the Oracle Integration instance.
• Scale in — Remove nodes from the Oracle Integration instance.
• Scale out — Add nodes to the Oracle Integration instance.
• Access Rules — Opens the Access Rules page, which enables you to
create and manage access rules for selected sources and destinations.
• SSH Access—Add public SSH keys to the VMs that make up this service
instance.
• View Activity—View activities that have occurred in your identity domain.
Click the start/stop/scale/monitor icons to:
• Start the VMs for the administration server, managed servers, and load
balancer.
• Stop the VMs for the administration server, managed servers, and load
balancer.
• Add a node.
• Display monitoring data:
– Date and time each node was last started.
– For each server, the percent of heap space used as compared to the
total heap space in GBs available. If you click the percentage number,
the heap usage graph is displayed.
Click to refresh the page. The date and time the page was last refreshed are
Refresh displayed adjacent to this button.
Instance Overview section Overview information about the instance.
• Nodes: Total number of Oracle CPUs allocated for the instance.
• OCPUs: Total number of Oracle Compute Units (OCPUs) allocated across
all instances.
• Memory: Total amount of memory in GBs allocated for the instance.
• Storage: Total amount of block storage in GBs allocated for the instance.
Other overview information • Status — The service instance’s status (for example, ready).
• Content Endpoint — The endpoint address.
• Integration Edition — The topology you selected when you provisioned the
service instance.
• Service Identifier — Service identifier.
• Version — The version of Oracle WebLogic Server configured for the
instance.
• Feature Set — The provisioned feature set.
• JDK — The supported Java Developer Kit version.
• IDCS Application — Click the link to open the Oracle Identity Cloud Service
Console to add users and assign roles. See Grant Access and Manage
Security.

8-14
 Chapter 8
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration Classic (User-Managed)

Element Description
Information about the administration server or managed server(s):
• Host Name
• Public IP address
Resources
• Instance name (managed server)
• Instance name (administration server)
• Number of Oracle CPUs allocated (OCPU)
• The amount of memory allocated to the node
• The amount of storage available to the node

Manage this service Displays operations such as Remove Node, Start, Stop, and Restart.
Load Balancer Information about the Oracle Load Balancer URL and type.
Associations section Information about the Oracle Database Classic Cloud Service database
deployment used by the instance. If the instance is based on two database
deployments (one for the Oracle required schema and the second for the
application schema), information for both database deployments is displayed.
• Service Name — The name of the Oracle Database Classic Cloud Service
database deployments used by the instance. The name was specified
during the process of creating the instance.
• Service Type— Specifies the connect string for the database deployment.
• Type — The only available value is Oracle Database Classic Cloud Service.
• Status — The status of the database deployment.

Administration Tile — Backup Tab

You can use the Backup tab of the Administration tile on the Instance page to view the
backup status and access backup configuration tasks for a specific instance. The Backup tab
provides the following details.

8-15
 Chapter 8
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration Classic (User-Managed)

The following table describes the key information shown on the Backup tab of the
Administration tile.

Element Description
Click the Administration tile to back up an instance. See Back Up and Restore
an Oracle Integration Classic (User-Managed) Instance.

Incremental Backups Displays the time at which incremental backups occur. For example:

Daily at 11:40:00 AM UTC

The amount of MB backed up to Oracle Cloud Infrastructure Object Storage

Classic is displayed.
Full Backups Displays the time at which the full backup occurs. For example:

Every Saturday at 11:40:00 AM UTC

The volume of backup space used is also displayed.

Last Successful Backup The time at which the last successful backup occurred. For example:

Tuesday at 11:40:00 AM UTC

The percentage of the backup volume used is also displayed.

Most Recent Backup Displays the time of the last backup. If a red icon is displayed, click it for backup
failure details.
Available Backups Click Manage backups on this service to display the following options:
• Backup Now
• Configure Backups
• Disable Backups
See Back Up and Restore an Oracle Integration Classic (User-Managed)
Instance.
Restore History The restoration operations history for this service instance.

Administration Tile — Patching Tab

You can use the Patching tab of the Administration tile on the Instance page to view
patching information and install patches for a specific instance.

8-16
 Chapter 8
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration Classic (User-Managed)

The following table describes the key information shown on the Patching tab of the
Administration tile.

Element Description
Available Patches Displays details about any available patches:
• Patch name
• Patch release date
• Whether patch installation requires a restart
• Readme link that displays information about the patch
See Patch and Upgrade Oracle Integration Classic (User-Managed).
Patch History Displays the history of patch installation.
Note: You cannot roll back a patch.

Explore the Oracle Cloud Infrastructure Console Activity Page

You can use the Activity page to search for and review cloud service activities that have
occurred in your identity domain. To access this page, click the Activity tab in the Oracle
Cloud Infrastructure Console.

8-17
 Chapter 8
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration Classic (User-Managed)

The Activity page is divided into the following sections:

• The Search Activity Log section, from which you can specify search details that
determine which services you see. These details include:
– Date and time range
– Operation status
– Instance name
– Service type
– Operation
• The Results pane, which shows the results of the search operation. You can limit
the number of results to return, per page, to 5, 10, 50, or 100.
The following table describes the key information shown on the Activity page.

Element Description
Start Time Range Filters activity results to include only operations started within a specified time
range. The range defaults to the previous 24 hours.
Operation Status Filters operations by status of the operation:
• All (default value)
• Scheduled
• Running
• Succeeded
• Failed
You can select any subset of status types.
Instance Name Filters the activity results to include operations only for the specified service
instance. You can enter a full or partial service instance name.
Service Type Filters the activity results to include operations only for instances of the
specified service type. The default value is the current cloud service.
Operation Filters the activity results to include selected types of operations. You can select
any subset of the given operations. The default value is All.

8-18
 Chapter 8
About the User Interfaces of the Oracle Cloud Infrastructure Console for Oracle Integration Classic (User-Managed)

Element Description
Search Searches for activities by applying the filters specified by the Start Time Range,
Status, Service Name, Service Type, and Operation fields, and displays activity
results in the table.
Reset Clears the Start Time Range and Service Name fields, and returns the Status
and Operation fields to their default values.
Results per page Specifies the number of results you want to view per page. The default value is
10. You can sort the columns in ascending or descending order.
Operation Shows the type of operation performed on the service instance.
Instance Name Shows the name of the service instance and its identity domain:
service_instance:identity_domain
Service Type Shows the type of cloud service for this instance.
Operation Status Shows the status of the operation performed on the service instance.
Start Time Shows the time the operation started.
End Time Shows the time the operation ended, if the operation is complete.
Initiated By Shows the user that initiated the operation. The user can be any user in the
identity domain who initiated the operation or, for certain operations such as
automated backup, the system.

Explore the Oracle Cloud Infrastructure Console SSH Access Page

You can use the SSH Access page to view and manage public SSH keys from the Oracle
Integration Classic Oracle Cloud Infrastructure Console.
The SSH Access page is divided into the following two sections:
• The Search Activity pane, from which you can specify the service name and service type
when you want to see SSH information for a specific service or group of services.
• The Results pane, which shows the results of the search operation. You can limit the
number of results to return, per page, to 5, 10, 50, or 100.
The following table describes the key information shown on the SSH Key Access page.

Element Description
Click to sign in to the services to which you are subscribed.

Instances tab Click to return to the Oracle Cloud Infrastructure Console.

Activity tab Click to navigate to the Oracle Cloud Infrastructure Console Activity page. See
Explore the Oracle Cloud Infrastructure Console Activity Page.
Instance Name Filters the results to include SSH keys only for the specified service instance.
You can enter a full or partial service instance name.
Search Searches for SSH keys by applying the filters specified by the Service Name
and Service Type fields, and displays the results in the table.
Service Type Filters the results to include SSH keys only for instances of the specified service
type. The default value is the current cloud service.
Results per page Specifies the number of results you want to view per page. The default value is
10.

8-19
 Chapter 8
Support the Minimum Version of Oracle Integration Classic (User-Managed)

Element Description

Expand Displays a description of an item in the results table. Clicking the resulting
downward arrow hides the description.
Instance Name Shows the name of the service instance.
Service Type Shows the type of cloud service for this instance.
Last Update Shows the most recent time the SSH keys for this instance were updated. When
the credential update is in progress, an hourglass icon is displayed before the
date/time, indicating that the service instance is in maintenance mode.
Actions Click the Add New Key button to add a new SSH public key to this instance.
This button is grayed out when the key is in the process of being added.

Explore the IP Reservations Page

If your identity domain is enabled for regions, you can reserve IP addresses. After you
create an IP reservation, you can use it when provisioning Oracle Integration Classic.

The following table describes the key information shown in the Oracle Integration
Classic IP Reservations page.

Element Description
Create Click to access the page for creating an IP reservation.
Welcome! Click to display the Oracle Integration Classic Welcome page.
• Region: Displays the region.
• Status: Displays whether the IP reservation is currently in use.
• Service Entitlement ID: Displays the service entitlement ID.
• IP Address: Displays the IP address.
• Created On: Displays the creation date.

Support the Minimum Version of Oracle Integration Classic

(User-Managed)
Oracle Integration Classic (user-managed) only provides maintenance fixes on top of
the latest software release. Therefore, when a software upgrade is available at the
beginning of a month, it is your responsibility to manually upgrade any existing Oracle
Integration Classic instances to the latest release by applying software upgrade
patches. If you are not on the latest release, you must patch your instance to be at the
latest software release before you can apply any additional maintenance fixes. For
example, if you provisioned Oracle Integration Classic 17.4.1, and there have been
several software upgrades since then, you must first upgrade to the latest software
release before you can apply any additional maintenance fixes. Note that the latest
software release patch always includes the previous software releases. Therefore, you
only need to apply that single patch to be upgraded to the latest release.
This situation does not apply to newly provisioned instances. For Oracle Integration
Classic instances that are provisioned after the maintenance fixes are announced and
available, they are automatically applied and available in the newly provisioned
instance.

8-20
 Chapter 8
Support the Minimum Version of Oracle Integration Classic (User-Managed)

For information about applying patches from the Oracle Integration Classic Oracle Cloud
Infrastructure Console, see Patch and Upgrade Oracle Integration Classic (User-Managed).

8-21
9
Manage Oracle Integration Classic (User-
Managed)
In Oracle Integration Classic (user-managed), an administrator is responsible for maintaining
the infrastructure on which Oracle Integration Classic is built.
An administrator can apply a patch, initiate on-demand backups, schedule automated
backups, add or remove nodes for increased or reduced load on an Oracle Integration
Classic instance. In addition, an administrator can monitor the instance and export diagnostic
information to resolve problems.

Note:
Oracle does not possess the credentials for consoles such as Enterprise Manager
(EM), WebLogic Server console, and Service Bus console. Therefore, a user is not
blocked from performing tasks from these consoles. However, Oracle highly
recommends that users DO NOT use these consoles.
See Unsupported Tasks.

Topics:
• Unsupported Tasks
• Patch and Upgrade Oracle Integration Classic (User-Managed)
• Stop and Start Oracle Integration Classic (User-Managed) Instances and Nodes
• Scale an Oracle Integration Classic (User-Managed) Instance
• Manage Database Issues
• Back Up and Restore an Oracle Integration Classic (User-Managed) Instance
• Manage Integrations and Errors
• Manage SSL Certifications
• Manage Instance History
• Configure Settings for Error Logs
• Use SSH to Sign In to Oracle Integration Classic (User-Managed)
• Diagnose Oracle Integration Classic (User-Managed) Problems
• Delete an Oracle Integration Classic (User-Managed) Instance

9-1
 Chapter 9
Unsupported Tasks

Unsupported Tasks
Oracle does not possess the credentials for consoles such as WebLogic Server or
Enterprise Manager. Therefore, a user is not blocked from performing tasks from these
consoles. However, Oracle highly recommends that users DO NOT use these
consoles.
The following lists some of the tasks that are not supported in Oracle Integration
Classic (user-managed). DO NOT perform these tasks unless recommended by
Oracle.
• Changing load balancer (LBaaS) settings
• Changing or removing CloudGate policies through Oracle Identity Cloud Service
REST API
• Changing WebLogic Server topology, including adding or deleting managed
servers
• Configuring SOA engine properties
• Configuring SOA MBean settings
• Changing the WebLogic JVM settings
• Configuring WebLogic resources including data sources, connection pools, JMS
servers, work managers, and partitions
• Configuring WebLogic MBean settings
• Deploying composites or service bus projects
• Deleting files including temporary files
• Deploying new Java EE applications to WebLogic
• Installing or uninstalling Linux programs
• Modifying date and metadata using SQL
• Modifying or deleting the Oracle Identity Cloud Service Applications, Application
ID, and roles that are created by default in Oracle Identity Cloud Service
administration console.
• Modifying firewall rules (iptables)
• Modifying Linux operating system privileges
• Modifying MDS metadata
• Modifying OPSS permissions
• Modifying SSH keys
• Patching Oracle Linux with unsupported updates
• Restarting WebLogic Server, Managed Server, or Node Managers through
WebLogic Server Console.
• Tuning Linux operating system settings
• Using compute console to modify security rules or reserve IP address
• Viewing, modifying, or deleting suite-generated composites, service bus projects,
and folders.

9-2
 Chapter 9
Patch and Upgrade Oracle Integration Classic (User-Managed)

Patch and Upgrade Oracle Integration Classic (User-Managed)

In Oracle Integration Classic (User-Managed), you can apply a patch to an Oracle Integration
Classic instance.

Topics:
• About Patching an Oracle Integration Classic (User-Managed) Instance
• Typical Workflow for Patching an Oracle Integration Classic (User-Managed) Instance
• Quick Tour of the Patching Page
• View Details About the Available Patches
• Perform Prechecks Before Applying a Patch
• Complete Prerequisites Before Applying a Patch
• Apply a Patch

About Patching an Oracle Integration Classic (User-Managed) Instance

You can quickly and easily apply patches to an Oracle Integration Classic (user-managed)
instance, without any command-line intervention.
Once you navigate to the Patching page in the Oracle Integration Classic user interface,
applying a patch to service instance is a one-click operation.

When to Apply Patches?

New approved patches are available and displayed on the Patching page. Apply the most
recent patches promptly to ensure new features and fixes are available.

What Happens to the Service During Patching?

Patching operations are rolling operations, so the service functions with very little interruption
during the patch process. The patching operation shuts down one virtual machine at a time
and the patching operation continues patching the servers on one virtual machine at a time
until all servers are patched. Patching restarts virtual machines. For example, if you have a
two-node, each node exists on a separate machine, and one node keeps running while the
other is being patched.
The user sessions that are running on a specific node can be lost during patching operation.
We recommend you to plan your patching operation during a time when there are minimal
user changes happening.
During patching, request for any administration task using REST API will be denied, and
administrative requests will not be accessible from the Integration Console.

What Happens When Patching is Not Fully Successful or Fails?

If the patching operation fails, then the patch is automatically reverted back.

9-3
 Chapter 9
Patch and Upgrade Oracle Integration Classic (User-Managed)

Typical Workflow for Patching an Oracle Integration Classic (User-

Managed) Instance
Consider the typical workflow for patching an Oracle Integration Classic (user-
managed) instance, as described in the following table.

Task Description More Information

Learn about approved patches View approved patches displayed on View Details About the Available
the Patching page periodically. Patches
Perform optional prechecks Learn about problems that would Perform Prechecks Before Applying a
cause patching to fail, so you can Patch
address those problems before you try
to apply a patch.
Apply a patch Initiate a patching operation. Apply a Patch

Quick Tour of the Patching Page

You can use the Patching page to view the available patch, initiate a patching process.
To access the Patching page, click the Administration tile on the Service Overview
page, then click the Patching tab.
The following table describes the key information shown on the Patching page.

Element Description
Scheduled Patches Displays details about any scheduled patches. Oracle handles all patch
installations:
• Patch name
• Status
• Patched By
• Notes
• Readme link that displays information about the patch
Represents an available patch.

This menu has two choices:

• Precheck—Performs prechecks without attempting to patch, and reports
any errors found so that you can address them before you patch.
• Patch—Performs prechecks, then patches the Oracle Integration Classic
(user-managed) instance with the selected patch.
Represents a successful patching precheck operation.

Represents a failed patching precheck operation.

Represents a patching operation in progress.

9-4
 Chapter 9
Patch and Upgrade Oracle Integration Classic (User-Managed)

Element Description
Patch History Displays the history of patch installation.
Note: You cannot roll back a patch.
Indicates a successful patching operation. Appears in the Patch History section.
Click this icon to obtain more information about the patching operation.

Displayed on a tools patch, indicates that the patch version for your existing
Oracle Integration Classic (user-managed) instance is older than the current
version. You will also see a warning stating that the service is on a deprecated
tools version. To address this issue, apply the latest tools patch to your Oracle
Integration Classic instance.

View Details About the Available Patches

You can use the Patching page to view the information about the available patches and
service patch history.
To view details of available patches:
1. Sign in to the Oracle Cloud Infrastructure Console.
2. In the Oracle Integration Classic (user-managed) console, click the name of your Oracle
Integration Classic instance.
3. In the Service Overview page, check the Administration tile to see the number of
available patches, and the date and time of the previous backup.
4. If patches are available, click the Administration tile, then click the Patching tab.

5. On the Patching page, check the information in the Available Patches section.

Perform Prechecks Before Applying a Patch

The patching process performs prechecks before applying a patch, but you can perform an
optional precheck operation before patching to identify and remedy issues first.
Prechecks occur automatically once you make a selection from the menu, then produce
messages letting you know the results.
Prechecks check for the following conditions:

9-5
 Chapter 9
Patch and Upgrade Oracle Integration Classic (User-Managed)

• Disk space shortage

• Missing database connectivity
• Servers not running
• Storage access failure
Prechecks do not check whether another administration task (backup, restoration, or
scaling) is in progress, which prevents patching.
If prechecks pass or you address all the issues identified by prechecks, you can run a
patching operation that will not encounter these issues.
You can only request prechecks for an approved patch that is listed on the patching
page.
1. Navigate to the Patching page.

2. On the Patching page, click to the right of the patch you want to check and
select Precheck.
A message appears beneath the patch name: Prechecks in progress.

3. Click Refresh to check whether prechecks are done.

When prechecks are done, a link appears: Precheck results.
• If prechecks pass, a green check mark icon appears.
• If prechecks fail, a red exclamation mark icon appears.
4. Click the Precheck results link.
The Patch Precheck Results dialog appears.
• If the prechecks succeed, the following message appears in the dialog:
Precheck succeeded for patch patch_name_and_version on
date_and_time. No conflicts found.
• If the prechecks fail, the following message appears in the dialog: Precheck
failed for patch patch_name_and_version on date_and_time.
Error messages appears in the dialog as well. If there are precheck failures,
check the error messages to learn about the problems that you need to
address.
The Precheck results link remains after prechecks complete.

Complete Prerequisites Before Applying a Patch

Every patch in an Oracle Integration Classic (user-managed) instance has a Readme,
which provides information required to apply the patch. Be sure to read the instructions
carefully and contact Oracle Support for any questions before applying the patch.

9-6
 Chapter 9
Patch and Upgrade Oracle Integration Classic (User-Managed)

Note:
These prerequisite steps are required only if you are upgrading a 17.4.1 or “new”
17.4.5 Oracle Integration instance to 18.1.x. They are not required if you previously
upgraded a 17.4.1 instance to 17.4.5 and are now upgrading to 18.1.x, or if you
already have an 18.1.x instance provisioned.
To view the history of your patch, see the Patch History section in the Patching
page. indicates a successful patching operation.

Expand the to read the instructions.

If required (see Note above), complete the following one-time prerequisites for each Oracle
Integration instance:
1. Access the Oracle Integration Oracle Cloud Infrastructure Console Overview page using
your browser and make a note of the administration server IP address.
See Explore the Oracle Cloud Infrastructure Console Instance Overview Page.

9-7
 Chapter 9
Patch and Upgrade Oracle Integration Classic (User-Managed)

2. Use an SSH client to connect to the Oracle Integration instance:

ssh -i private_key_file opc@admin_ip_address
where admin_ip_address is the IP address of the administration server.
3. Switch to the user oracle:
sudo su oracle
4. Delete the [Link] file, if it exists:
rm /u01/data/domains/[Link]
5. Access the Oracle Integration Oracle Cloud Infrastructure Console Overview page
using your browser and make a note of the database server details.
See Explore the Oracle Cloud Infrastructure Console Instance Overview Page.

9-8
 Chapter 9
Patch and Upgrade Oracle Integration Classic (User-Managed)

6. Connect to the database as a DBaaS Database Administrator.

See Connecting Remotely to the Database by Using Oracle SQL Developer and
Connecting Remotely to the Database by Using Oracle Net Services in Administering
Oracle Database Classic Cloud Service.
7. After you connect to the database, execute the following query to list all owners in your
current installation.
SELECT OWNER from "SYSTEM"."SCHEMA_VERSION_REGISTRY" where COMP_ID =
'SOAINFRA';
A list of owners that are currently created in the database is displayed. Here is the
sample output and you’ll find one entry for each Oracle Integration instance.

8. For each owner listed in the database (see step 7), execute the following command to set
the status to VALID:
UPDATE "SYSTEM"."SCHEMA_VERSION_REGISTRY" SET STATUS = 'VALID' where
STATUS='INVALID' and OWNER='OWNER';
where OWNER is the name of the owner or schema user.

9-9
 Chapter 9
Patch and Upgrade Oracle Integration Classic (User-Managed)

For example, UPDATE "SYSTEM"."SCHEMA_VERSION_REGISTRY" SET STATUS =

'VALID' where STATUS='INVALID' and OWNER='SP670824491_SOAINFRA';

Note:
If a schema is INVALID, it is set to VALID and the following output
appears:
1 rows updated.

9. For each owner listed in the database (see step 7) execute the following command
to grant the SELECT and UPDATE permissions to the database table:
GRANT SELECT,UPDATE on "SYSTEM"."SCHEMA_VERSION_REGISTRY$" to OWNER;
For example, GRANT SELECT,UPDATE on "SYSTEM"."SCHEMA_VERSION_REGISTRY$"
to 'SP670824491_SOAINFRA';
10. For each owner listed in the database (see step 7) execute the following command
to grant the SELECT and UPDATE permissions to the database view:
GRANT SELECT,UPDATE on "SYSTEM"."SCHEMA_VERSION_REGISTRY" to OWNER;
For example, GRANT SELECT,UPDATE on "SYSTEM"."SCHEMA_VERSION_REGISTRY"
to 'SP670824491_SOAINFRA';
11. For each owner listed in the database (see step 7) execute the following command
to provide access to DBA_TABLESPACE_USAGE_METRICS:
GRANT SELECT ON sys.DBA_TABLESPACE_USAGE_METRICS to OWNER;
For example, GRANT SELECT ON sys.DBA_TABLESPACE_USAGE_METRICS to
SP670824491_SOAINFRA;

Apply a Patch
You can use the Patching page to apply a patch of an Oracle Integration Classic (user-
managed) instance.
To apply a patch:
1. Navigate to the Patching page.

2. In the Available Patches section, click to the right of the patch you want to apply
and select Patch.
3. In the Patch Service dialog, enter the following information:
• Additional Note (optional): Type notes pertaining to the patch.
• Database Schema Password: You can either leave the field blank or enter
the correct database schema password only if you've changed the password
since the last time a patch was applied.

Note:
If you've not changed the database schema password, leave the
Database Schema Password field blank.

9-10
 Chapter 9
Stop and Start Oracle Integration Classic (User-Managed) Instances and Nodes

4. In the Patch Service dialog, click Patch.

Stop and Start Oracle Integration Classic (User-Managed)

Instances and Nodes
In Oracle Integration Classic (user-managed), you can stop and start an Oracle Integration
Classic instance and, when the instance is running, start, stop, and restart individual nodes.

Topics:
• About Stopping and Starting Instances and Nodes
• Stop and Start Your Instance
• Stop and Start the Nodes in Your Instance

About Stopping and Starting Instances and Nodes

You can stop and start an Oracle Integration Classic (user-managed) instance and stop, start
and restart virtual machines (nodes) when the instance is running.

Why Stop an Oracle Integration Classic (User-Managed) Instance?

Stopping an Oracle Integration Classic instance frees up compute resources used by the
instance’s nodes. Metering for those resources stops.
Storage volumes remain intact when the instance is stopped, and are reattached when your
start the instance. IP address reservations are retained when the instance is stopped, so the
nodes will have the same public IP addresses as before when you start the instance.

What Happens When an Oracle Integration Classic (User-Managed) Instance is

Stopped or Started?
Stopping and starting an Oracle Integration Classic instance has the following results:
• Stopping the instance: The nodes on which the Administration Server and Managed
Servers are running are stopped.
• Starting the instance: All nodes on which the Administration Server and Managed
Server are running are started. You can restart the Managed Servers individually.

Why Stop, Start, or Restart Managed Server?

If an Oracle Integration Classic (user-managed) instance is running:
• You can restart the nodes on which the Managed Server are running if you are
experiencing problems with the server that would warrant a reboot.
• You can stop the nodes on which the Managed Server is running to free up resources
and stop metering those resources. You might also want to stop the instance instead of
scaling, keeping the server ready for a later time.
• You can start a Managed Server if it is stopped and you want to use it again. Metering
begins again.

How Do I Monitor the Stop, Start, or Restart Operation?

You can monitor progress of a stop, start, or restart operation on the Activity page.

9-11
 Chapter 9
Stop and Start Oracle Integration Classic (User-Managed) Instances and Nodes

What Happens When an Instance Is Stuck in Maintenance Mode While Stopping?

When you try to stop an Oracle Integration Classic (user-managed) instance, on rare
occasions it might become stuck in maintenance mode due to some problem with the
instance.
For six hours, the software will continue to attempt to stop the instance, then change
the instance status from maintenance state to error state. At this point, you can debug
the problem causing the error and attempt to stop the instance again.

Stop and Start Your Instance

You can stop and start an Oracle Integration Classic (user-managed) instance using
the Oracle Cloud Infrastructure Console.
To stop or start an Oracle Integration Classic instance:
1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.
3. Select Platform Services, then Integration Classic.
The Oracle Integration Classic Instances page is displayed.
4. Identify the name of your Oracle Integration Classic instance.
5. Complete one of the following actions:

• Click adjacent to the service name and select Start or Stop.

• Click Start Instance or Stop Instance .

Note:
The Start and Stop options remain active while the operation is in
progress so that, if the operation gets stuck, you can try to start or stop
again.

A confirmation dialog opens.

6. Click OK in the confirmation dialog.
A yellow status icon appears adjacent to the service instance icon while the
service instance is in the process of stopping or starting.
When the operation completes, the Oracle Integration Classic instance stops or
stops. A red icon displays when the service instance is stopped. On the Activity
page, the entry for the service shows that the stop or start operation has ended.

Stop and Start the Nodes in Your Instance

You can stop, start, and restart a node in an Oracle Integration Classic (user-
managed) instance.
To stop, start, or restart a node:

9-12
 Chapter 9
Scale an Oracle Integration Classic (User-Managed) Instance

1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click the name of your Oracle Integration Classic instance.

3. On the page, click Manage this node to the right of the node and select Stop, Start,
or Restart.

4. Click OK in the confirmation dialog.

The node stops, starts, or restarts.

Scale an Oracle Integration Classic (User-Managed) Instance

In Oracle Integration Classic (user-managed), scaling lets you add or remove resources for
an Oracle Integration Classic instance on demand in response to changes in load on the
instance.

Topics:
• About Scaling Your Instance
• Overview of Scaling Tasks for Your Instance
• Scale Out an Oracle Integration Classic (User-Managed) Instance
• Scale In an Oracle Integration Classic (User-Managed) Instance
• Check Status of Scaling Requests

About Scaling Your Instance

You can scale an Oracle Integration Classic (user-managed) instance by scaling a cluster, a
node in the instance.

About Scaling Out an Oracle Integration Classic (User-Managed) Cluster

Scaling out an Oracle Integration Classic cluster adds one node to the cluster.
Before scaling out an Oracle Integration Classic cluster, ensure that all these conditions are
met:
• You have the Oracle Identity Cloud Service Administrator role.
• The instance is not under maintenance, such as during patching or backing up.
If any of these conditions is not met, the scaling operation fails and Oracle Integration Classic
logs an error message.

9-13
 Chapter 9
Scale an Oracle Integration Classic (User-Managed) Instance

Oracle Integration Classic logs a message when scaling out is started or completed, or
when a failure is detected.
If an attempt to scale out a cluster fails, Oracle Integration Classic does the following:
• Logs any diagnostic information.
• Sets the status of the instance to RUNNING to allow other operations to continue.
• Returns the instance to its original shape.
• Deletes the node that it created to run the additional Managed Server instance.

About Scaling In an Oracle Integration Classic (User-Managed) Cluster

Scaling in an Oracle Integration Classic cluster removes the selected node from the
cluster.
Before scaling in an Oracle Integration Classic cluster, ensure that the cluster contains
at least one Managed Server node in addition to the node for the Administration
Server and first Managed Server. You cannot scale in a cluster that contains only the
node for the Administration Server and first Managed Server. If you no longer require
that node, you must delete the entire instance.
By default, Oracle Integration Classic scales in a cluster gracefully by shutting down
the Managed Server instance before removing the Managed Server instance from the
cluster and terminating its node. To ensure that the node is removed even if the
Managed Server instance is unresponsive, you can choose to forcibly scale in a
cluster.
If an attempt to scale in a cluster fails, Oracle Integration Classic does the following:
• Logs any diagnostic information.
• Sets the status of the instance to RUNNING to allow other operations to continue.
• Cleans up any stale resources.

Overview of Scaling Tasks for Your Instance

You perform scaling tasks for an Oracle Integration Classic (user-managed) instance
as required.
The following table provides information about how to perform each task by using the
web-browser-based Oracle Integration Classic administration console.

Task Description More Information

Scale out an Oracle Integration Scale out an Oracle Integration Scale Out an Oracle Integration
Classic cluster Classic cluster to add one node to Classic (User-Managed) Instance
the cluster.
Scale in an Oracle Integration Scale in an Oracle Integration Scale In an Oracle Integration Classic
Classic instance cluster Classic cluster to remove a selected (User-Managed) Instance
node from the cluster.
View scaling requests View scaling requests to check the Check Status of Scaling Requests
status of ongoing scaling requests,
and the success or failure of
previous requests.

9-14
 Chapter 9
Scale an Oracle Integration Classic (User-Managed) Instance

Scale Out an Oracle Integration Classic (User-Managed) Instance

You can scale out an Oracle Integration Classic (user-managed) instance to add one node to
the cluster. When you scale out, Oracle Integration Classic instance creates a new node
running a WebLogic Server Managed Server instance.

Note:
Oracle Integration Classic allocates two threads per server to process scheduled
integrations. You can scale out Oracle Integration Classic (add nodes) to increase
the number of scheduled integrations that can run in parallel in a user-managed
environment.

To scale out an Oracle Integration Classic instance cluster:

1. Sign in to the Oracle Cloud Infrastructure Console.
2. Click the name of your Oracle Integration Classic instance.

3. Click or click Manage this service and select Scale Out.

The Scale Out dialog opens.
4. To confirm you want to scale out the cluster, click Scale Out.

5. After a few moments, click Refresh to update the page.

You might need to click the icon more than once to see any change to the page.
After a few moments of processing, the new node appears on the Overview page. The
Overview tile shows the number of nodes increased by one.

Note:

At any time during the scaling process, click Manage this service next to the
instance name and select View Activity. The Activity page opens and you can see
the scale-out status in the activity table.

Scale In an Oracle Integration Classic (User-Managed) Instance

You can scale in an Oracle Integration Classic (user-managed) instance to remove a selected
node from the cluster. When you scale in, Oracle Integration Classic removes the selected
WebLogic Server Managed Server instance and the virtual machine that it is running on.
1. Sign in to the Oracle Cloud Infrastructure Console.
2. Click the name of your Oracle Integration Classic instance.

3. In the Oracle Cloud Infrastructure Console, click Manage this node for the node you
want to remove and select Remove node.
The Remove Node dialog box opens.

9-15
 Chapter 9
Scale an Oracle Integration Classic (User-Managed) Instance

4. In the Remove Node dialog box, click Remove Node.

5. After a few moments, click Refresh to update the page.

You might need to click the icon more than once to see any change to the page.
After a few moments of processing, the node is removed from the Overview page. The
Overview tile will show the number of nodes decreased by one.

Note:

At any time during the scaling process, click Manage this service next
to the instance name and select View Activity. The Activity page will open
and you can see the scale-in status in the activity table.

Check Status of Scaling Requests

You can view scaling requests to check the status of ongoing Oracle Integration
Classic (user-managed) scaling requests, and the success or failure of previous
requests.
To view ongoing or past scaling requests:
1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.
3. Select Platform Services > Integration Classic.
4. Click the name of your Oracle Integration Classic instance.

5. On the page, click Manage this service at the top of the page and select
View Activity.
The Activity page of the Platform Services Console opens.
6. In the Search Activity Log panel, enter the necessary search criteria:

Option Description
Start Time Range The date and time range within which you want to see
scaling activity.
Operation Status The status of the scaling activity you want to view. This
option will filter out all scaling activity not in this status. To
see all status, select All.
Instance Name The name of the service instance for which you want to see
scaling activity.
Service Type This should be Oracle Integration.
Operation The operation for which you want to see activity. In the case
of scaling, select any or all of these options:
• Scale Application
• Scale In
• Scale Out
• Scale Up/Down

9-16
 Chapter 9
Manage Database Issues

7. Click Search.
All scaling activity that meets the search criteria appears in the results table. The Status
column will indicate whether the scaling operation succeeded or failed. To see more
details about a specific operation, click its drop-down control.

Manage Database Issues

A service administrator can manage passwords for database schemas, set alerts based on
performance metrics, and peform other database-related monitoring and management tasks.

Topics:
• Update the Database Schema Password in Oracle Integration Classic
• Managing Alerts

Update the Database Schema Password in Oracle Integration Classic

When you create an instance in Oracle Integration Classic, relevant database schemas are
created in the associated Oracle Database Cloud Service (DBaaS) instance. These database
schemas are required for Oracle Integration Classic to function properly.
Some of these database schemas are associated with:
• The core Oracle Integration Classic functionality (such as Integration, Process, and
Visual Builder).
• The non-Oracle Integration Classic-specific functionality such as OPSS and other critical
services that Oracle Integration Classic depends on.
These database schemas are used within the data sources defined for the Oracle Integration
Classic instance.
For security reasons, the password for the database schemas expires after 180 days. If the
password expires, it disrupts the functionality of the Oracle Integration Classic instance and
potentially leads to system downtime. It is highly recommended that you update the database
schema password within 180 days of the instance creation as described below in this section.
We strongly recommend that you note the new password. It will be required for subsequent
instance patching attempts.

Note:
If you actively use Visual Builder, file a service request to get help from Oracle
Support to complete the standard operating procedures required for the Visual
Builder specific schemas.

Change the Database Schema Password

This topic does not apply to Oracle Cloud at Customer.

Use Oracle Java Cloud Service to change the Oracle schema password in the database
deployment, and to also update your service instance to use the new password.

9-17
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

1. Access your service console.

2. Click the name of the service instance whose schema password you want to
change.
3. At the bottom of the Overview page, expand Associations.
4. From the list of associations for this service instance, identity the association with
these characteristics:
• Service Type - Oracle Database Cloud Service
• Type - Depends On

5. Click Manage Association for this association, and then select Update
Database Credentials.
6. Complete the following input fields:

Field Description
Database Administrator Enter the name of the system administrator for the selected database
Username deployment.
Database Administrator Enter the password for the database administrator.
Password
New Schema Password Enter a new password for the Oracle schemas in the selected database
deployment.

7. Click Update.
You can monitor the operation’s progress from this page or from the Activity page.

Managing Alerts
Service administrators can configure rules to generate alerts when metrics exceed or
are under specified thresholds for a specific time period. Service administrators will
receive the alert notifications. See Setting an Alert for a Performance Metric of
Managing and Monitoring Oracle Cloud.
To monitor and manage the Oracle database deployed on Oracle Database Classic
Cloud Service, you can use the standard management tool provided with the version
of the database. See Monitoring and Managing Oracle Database on Database Cloud
Service of Administering Oracle Database Classic Cloud Service.

Back Up and Restore an Oracle Integration Classic (User-

Managed) Instance
In Oracle Integration Classic (user-managed), you can back up and restore your
Oracle Integration Classic instances to return their software and data to a particular
state.

Topics:
• About Backing Up and Restoring an Oracle Integration Classic (User-Managed)
Instance

9-18
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

• Typical Workflow for Backing Up and Restoring an Oracle Integration Classic (User-
Managed) Instance
• Quick Tour of the Backup Page
• Configure an Automatic Backup
• Initiate an On-Demand Backup
• Delete a Backup
• Disable or Enable Backups
• Restore a Backup

About Backing Up and Restoring an Oracle Integration Classic (User-

Managed) Instance
By backing up your Oracle Integration Classic (user-managed) instances, you can preserve
them in a particular state..
When you create an Oracle Integration Classic instance, you can choose whether or not to
enable backups. These backups are recorded to local node storage as well as to an Oracle
Cloud Infrastructure Object Storage Classic container.

What a Backup Contains

The contents of a backup depend on whether it is a full backup or an incremental backup.
A full backup contains all the runtime artifacts required to restore the instance’s configuration
data. An incremental backup contains changes to configuration data on all nodes since the
last scheduled full backup.

Note:
All incremental backups are automated scheduled backups. You cannot create an
incremental backup on demand.

Contents of a Database Backup

A database backup contains Oracle database instance Oracle Fusion Middleware component
schemas, and application data for an Oracle Integration Classic instance.

Note:
Only scheduled automated backups of an Oracle Integration Classic back up the
database instance. On-Demand backups do not perform a database backup.
Alternatively, you can back up your database using the associated Oracle Database
Cloud Service database used by the instance. See Backing Up and Restoring
Databases on Database Cloud Service in Administering Oracle Database Classic
Cloud Service.

9-19
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

Where Backups Are Stored

Oracle Integration Classic stores all backups in an Oracle Cloud Infrastructure Object
Storage Classic container. To speed up restorations from recent backups, Oracle
Integration Classic also keeps a local copy of any backup it has recently created.

Note:
Do not attempt to download the backup files generated by Oracle Integration
Classic. These files are encrypted and not accessible offline. You must use
Oracle Integration Classic to restore an instance from a backup.

By default, Oracle Integration Classic stores backups in the container that was
specified when the instance was created.
Oracle Integration Classic automatically deletes a backup when the retention period
for the backup has elapsed.

How Local Copies of Backups Are Stored

Oracle Integration Classic stores local copies in a dedicated volume mounted on the
block storage attached to the node where the Administration Server is running.
• For an incremental backup, Oracle Integration Classic stores the local copy for
seven days before deleting it.
• For a full backup, Oracle Integration Classic stores the local copy for seven days,
or as long as the local copy of its last related incremental backups was stored,
whichever is longer.

How Backups and Local Copies Are Deleted Automatically

After completing the day’s scheduled backup, Oracle Integration Classic deletes any
backups or local copies that are due to be deleted that day. If the scheduled backup
fails because of insufficient space, backups and local copies that are due to be deleted
will still be deleted.

Note:
When an Oracle Integration Classic instance is deleted, all its backups are
deleted.

What Happens During a Backup

During a backup of an Oracle Integration Classic instance, the instance continues to
run and all applications deployed to the instance remain available.
To prevent configuration changes during a backup, Oracle Integration Classic locks the
Oracle WebLogic Server domain if the administration server is running. After locking
the domain, Oracle Integration Classic backs up files on each node.

9-20
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

While the backup is in progress, you cannot start any other management operation on the
instance. Similarly, if the administration server is not running at the time a backup is started,
do not attempt to start this server until the backup completes.
When the backup is complete, Oracle Integration Classic unlocks the Oracle WebLogic
Server domain. If the backup is a scheduled backup, Oracle Integration Classic also cleans
up older backups as follows:
• From local storage it deletes all backups old enough to be stored only in the Oracle
Integration Classic container.
• From all storage locations it deletes any remaining copies of backups whose retention
period has elapsed. The default is 30 days.

What Happens When an Instance Is Restored

When restoration of an instance is initiated, Oracle Integration Classic shuts down the
servers in the instance. After the restoration is complete, Oracle Integration Classic restarts
these servers.
If the instance contains any managed server nodes that are not in the backup, Oracle
Integration Classic warns you that it cannot restore these nodes.
Before trying to restore again, you can scale in the instance to delete these nodes.
If you choose to continue without scaling in the instance, Oracle Integration Classic asks you
to confirm that you understand that the instance will be scaled in automatically.
If the backup contains any managed server nodes that are not currently in the instance,
Oracle Integration Classic does not attempt to remove these managed servers from the
Oracle WebLogic Server domain. You must use the WebLogic Server to manually remove
these managed servers from the domain configuration after restoring the instance.
Oracle Integration Classic does not automatically remove any existing Oracle WebLogic
Server transaction records after restoring an instance from a backup.

Typical Workflow for Backing Up and Restoring an Oracle Integration

Classic (User-Managed) Instance
To back up and restore an Oracle Integration Classic (user-managed) instance, consider this
typical workflow.

Task Description More Information

Configure backups for an Oracle Customize the following properties of Configure an Automatic Backup
Integration Classic instance backups for a service instance:
• When automated backups are
performed
• Where backups are stored
• How long new backups are
retained
Initiate an on-demand backup of an Create a backup immediately without Initiate an On-Demand Backup
Oracle Integration Classic instance having to wait for the next scheduled
backup.

9-21
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

Task Description More Information

Delete a backup Delete a backup that you no longer Delete a Backup
require to release storage or prevent
an Oracle Integration Classic
instance from being restored from
the backup.
Restore an Oracle Integration Undo configuration changes you Restore a Backup
Classic instance from a backup don’t want by returning an Oracle
Integration Classic instance to a
particular state.

Quick Tour of the Backup Page

You can use the Backup page to back up and restore an Oracle Integration Classic
(user-managed) instance, and to manage backups for the service instance.

Element Description
Backups on Cloud Storage The total amount of space, in megabytes or gigabytes, that backups
are occupying in the Oracle Cloud Infrastructure Object Storage
Classic container for storing backups. This amount includes space
that is occupied by backups that have been manually uploaded to
the container, if any, in addition to the space occupied by backups
that Oracle Integration Classic has moved there.
Backup Volume Used The total amount of space, in megabytes or gigabytes, that local
copies of backups are occupying in the backup volume on the block
storage of the node where the Administration Server is running.
Backup Volume Used (%) The percentage of the available space that backups are occupying
in the backup volume on the block storage of the node where the
Administration Server is running.
Incremental Backups Indicates the schedule for running incremental backups.
Full Backups Indicates the schedule for running full backups.

Most Recent Backup Indicates that the most recent backup failed and the time of its
failure.
Last Successful Backup Indicates the time of the last successful backup.
Backup Now Click this button to create an on-demand backup of the Oracle
Integration Classic instance.
Configure Backups Click this button to update the backup schedule and where backups
are stored.
Disable Backups or Enable Backups Click this toggle button to disable/enable automated and on-demand
backups.
Available Backups List of available backups. By default, only backups for the last seven
days are listed. Use the search field to specify a range of dates for
which you want backups returned.

9-22
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

Element Description
Enter the start date of the period for which you want to filter the list
of available backups or the restoration history. By default, the start
date is set to seven days before the current date.
Enter the date in the format mm/dd/yyyy.
• mm is a one-digit or two-digit month number, for example, 2 for
February or 10 for October.
• dd is a number in the range 1–31 for the day of the month.
• yyyy is a four-digit year number, for example, 2104.
Alternatively, click the calendar icon to select the date from a
calendar.
Enter the end date of the period for which you want to filter the list of
available backups or the restoration history. Enter the date in the
format mm/dd/yyyy.
• mm is a one-digit or two-digit month number, for example, 2 for
February or 10 for October.
• dd is a number in the range 1–31 for the day of the month.
• yyyy is a four-digit year number, for example, 2104.
Alternatively, click the calendar icon to select the date from a
calendar.

Note:
The end date must not be earlier than
the start date.

Click to filter the list of available backups or the restoration history to

show only backups or restorations from within the period specified
by the Search from Date field and the Search to Date field.
In-progress backup for the Oracle Integration Classic instance. The
backup will not be available for use in restoring the service instance
until it is completed.
The backup is identified by the date and time when the backup
operation was started, which is displayed adjacent to icon that
represents the backup.
Click the icon to see additional information about the backup.
Completed backup for the Oracle Integration Classic instance. The
backup is available for use in restoring the service instance.
The backup is identified by the date and time when the backup was
created, which is displayed adjacent to icon that represents the
backup.
Click the icon to see additional information about the backup,
including its start date, complete date, expiration date and size. If a
database backup is included, its tag or timestamp is also displayed.

9-23
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

Element Description
Completed backup with a warning message. Oracle Integration
Classic instance tried but failed to move or delete one or more older
backups. For information about when and why Oracle Integration
Classic instance moves or deletes older backups. The backup is still
available for use in restoring the service instance.
To find out why Oracle Integration Classic instance could not move
or remove the older backup, place the cursor over the icon.
The presence of the older backup may cause future backups to fail
because of insufficient space.
The backup is identified by the date and time when the backup was
created, which is displayed adjacent to icon that represents the
backup.
Click the icon to see additional information about the backup.
The backup is in the process of being deleted.
Click the icon to see additional information about the backup.

Type A comma-separated pair of words that describes the type of the

backup.
The first word in the pair describes the extent of the backup:
• Full—The backup contains all the runtime artifacts required to
restore the service instance’s configuration data.
• Incremental—The backup contains changes to configuration
data on all nodes since the last scheduled full backup.
The second word in the pair indicates how the backup was initiated:
• If the backup was initiated automatically at the scheduled time,
the text “scheduled" is displayed.
• If the backup was initiated by a user, the user name of the user
who initiated the backup is displayed.
• If the backup was initiated in response to another management
operation by a user, the name of the user is displayed.
Available Until The date and time until which the backup will be retained.
Contains A row of up to two icons that indicates the content of the backup:
•
—Indicates that the backup contains configuration files.
•
—Indicates that the backup contains database files. Place
your mouse over this icon for additional database information.
Notes Click the link to display the notes that were provided when the
backup was created or the restoration was performed.
Click to select the following options:
• Restore—Restore the Oracle Integration Classic instance from
the backup.
• Delete—Delete the backup.
Restore History (Last 7 Days) Click the triangle adjacent to this label to display a list of all the
restoration operations on this service instance. By default, only
restoration operations for the last seven days are listed. Use the
search field to specify a range of dates for which you want
restoration operations returned.
Click Select to include unsuccessful restore attempts to include
the unsuccessful restoration operations in the list.

9-24
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

Element Description
Completed restoration operation for the Oracle Integration Classic
instance.
The restoration operation is identified by the date and time when it
was started, which is displayed adjacent to icon that represents the
restoration operation.
Click the icon to see additional information about the restoration
operation.
In-progress restoration operation for the Oracle Integration Classic
instance.
The restoration operation is identified by the date and time when it
was started, which is displayed adjacent to icon that represents the
restoration operation.
Click the icon to see additional information about the restoration
operation.
Unsuccessful restoration attempt for the Oracle Integration Classic
instance.
The restoration attempt is identified by the date and time when it
was started, which is displayed adjacent to icon that represents the
restoration attempt.
Click the icon to see additional information about the restoration
attempt.
From Backup The date and time when the backup from which the service instance
was restored was created.
Status The status of the restoration operation:
• Completed
• In-Progress
• Failed
Click the text to see detailed status messages for the operation.
Contains A row of up to two icons that indicates the items that were restored:
•
—Indicates that binary files were restored.
•
—Indicates that configuration files were restored.

Configure an Automatic Backup

You can configure backups for an instance to customize when the Oracle Integration Classic
(user-managed) instance is automatically backed up and how backups are stored.
Because the changes affect only one service instance, you can configure different values for
these properties for each of your service instances. Specifically, you can customize the
following properties of the service instance:
To configure automated backups for an Oracle Integration Classic instance:
1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.
3. Select Platform Services, then Integration Classic.
The Oracle Integration Classic Instances page is displayed.

9-25
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

4. Click the name of your Oracle Integration Classic instance.

5. In the Service Overview page, click the Administration tile.
6. Click the Backup tab.
The Backup page opens.

7. Click Manage backups on this service next to Available Backups and select
Configure Backups.
8. In the Configure Backups dialog, set the options to configure automated backups
for the service instance.
a. In the Schedule section, set options to configure when automated backups are
performed:

Note:
All times must be for the Coordinated Universal Time (UTC) time
zone, not your local time zone.

Option Description
Full Backup From the drop-down lists, select the day of the week and the
time of day UTC when you want full backups to be performed.
Incremental From the drop-down list, select the time of day UTC when you
Backup want incremental backups to be performed.

9-26
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

b. In the Set new retention period to field, enter the number of days that you want new
incremental backups and full on-demand backups to be retained.

Note:
If you decrease the retention period, any existing backups that are older
than this period will automatically be deleted during the next scheduled
backup.

Full scheduled backups are retained until their last linked incremental backup is no
longer available. The additional retention period for full scheduled backups is fixed
and you cannot change it.
9. Click Save.

Initiate an On-Demand Backup

You can create a full backup immediately without having to wait for the next scheduled
automatic backup.
Create a backup when making major changes to your Oracle Integration Classic (user-
managed) instance, for example, in these situations:
• Before any configuration changes that you may need to undo
• Before deploying an application
• After deploying an application

Note:
Do not attempt to start the administration server while a backup is in progress.

To initiate an on-demand backup of an Oracle Integration Classic instance:

1. Sign in to the Oracle Cloud Infrastructure Console.
2. Click the name of your Oracle Integration Classic instance.
3. In the Service Overview page, click the Administration tile.
4. Click the Backup tab.
The Backup page opens.

9-27
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

5. Click Manage backups on this service next to Available Backups and select
Back Up Now.
6. In the Back Up Now dialog, enter the notes up to 255 characters of free-form text
to provide additional information about the backup.
This text is displayed in the Notes field for the backup in the list of available
backups.
7. Click Back Up.
The Backup page is updated to show that the backup is in progress.
While the backup is in progress, you cannot start any other management operation on
the service instance.
When the backup is complete, it is added to the list of available backups on the
Backup page.

Disable or Enable Backups

Backups in an Oracle Integration Classic (user-managed) instance are enabled by
default on a new service instance but you can disable and enable this feature as
required.
After disabling backups for a service instance:
• Scheduled backups will not run.
• Automated backups will not run prior to patching or scaling operations.
• You cannot take an on-demand backup.
Disabling backups for a service instance does not affect any backups that were taken
previously.

9-28
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click the name of your Oracle Integration Classic instance.
3. In the Service Overview page, click the Administration tile.
4. Click the Backup tab.

5. Click Manage backups on this service next to Available Backups and select
Disable Backups.
6. When prompted for confirmation click Disable Backups.
7. To enable backups again at a later time, return to the Backup page and click Enable
Backups.

Restore a Backup
You can restore an Oracle Integration Classic (user-managed) instance from a backup to
return the service instance to a particular state or recover the service instance after a loss of
data.

Note:
If you restore a service instance's configuration files from a backup in which the
hosts do not match the hosts in the service instance, Oracle Integration Classic
handles the mismatch as follows:
• If the service instance contains any managed server hosts that are not in the
backup, Oracle Integration Classic warns you that it cannot restore the
managed server hosts that are not part of the backup.
Before trying to restore again, you can scale in the service instance to delete
the nodes that correspond to these managed server hosts. See Scale In an
Oracle Integration Classic (User-Managed) Instance
If you choose to continue without scaling in the service instance, Oracle
Integration Classic asks you to confirm that you understand that the service
instance will be scaled in automatically.
• If the backup contains any hosts that are not in the service instance, Oracle
Integration Classic does not attempt to remove the managed servers on these
hosts from the administration server configuration. You must use Oracle
WebLogic Server to remove the managed servers on these hosts from the
administration server configuration.
After you restore a service instance's configuration files from a backup that does not
match the service instance, you might need to modify the restored service instance
to return it to the state you require.

You can restore a service instance from an incremental backup without the need to restore
the full backup to which the incremental backup is linked. In this situation, you are
responsible for ensuring that the service instance is in a consistent state after the service
instance is restored.
Restoration from a backup that is stored on block storage is faster than restoration from a
backup that is stored in an Oracle Cloud Infrastructure Object Storage Classic container.

9-29
 Chapter 9
Back Up and Restore an Oracle Integration Classic (User-Managed) Instance

Before restoring an Oracle Integration Classic instance from a backup, you must
disable the load balancer for the service instance.
The applications deployed to your instance will be unavailable during the restoration
process.
To restore an Oracle Integration Classic instance from a backup:
1. Sign in to the Oracle Cloud Infrastructure Console.
2. Click the name of your Oracle Integration Classic instance.
3. In the Service Overview page, click the Administration tile.
4. Click the Backup tab.

5. Click Manage backups on this service next to Available Backups and select
Restore.
You can restore an instance from an incremental backup without the need to
restore the full backup to which the incremental backup is linked. Oracle
Integration Classic instance restores all the data from the linked full backup
required for a complete restoration of the instance.

Note:
If you choose to restore from an incremental backup, you are
responsible for ensuring that the service instance is in a consistent state
after the service instance is restored.

6. Enter Notes up to 255 characters of free-form text to provide additional information

about the restoration, such as why you are restoring the instance.
7. Click Restore.
The Backup page is updated to show that the restoration is in progress. While the
restoration is in progress, you cannot start any other management operation on
the instance.
When the restoration is complete, it is added to the restoration history in the
Backup page.

Delete a Backup
You can delete a backup that you no longer require to release storage or prevent an
Oracle Integration Classic (user-managed) instance from being restored from the
backup.

Note:
You can’t delete a full backup with linked incremental backups without
deleting the incremental backups. If the backup you’re deleting has linked
incremental backups, Oracle Java Cloud Service asks if you want to delete
both the full backup and its linked incremental backups.

9-30
 Chapter 9
Manage Integrations and Errors

To delete a backup:
1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click in the top left corner of the Oracle Cloud Infrastructure Console.
3. Select Platform Services, then Integration Classic.
4. Click the name of your Oracle Integration Classic instance.
5. In the Service Overview page, click the Administration tile.
6. Click the Backup tab.
The Backup page is displayed.

7. Click Manage backups on this service next to Available Backups and select
Delete.
8. When prompted, confirm that you want to delete the backup.
If the backup you’re deleting has linked incremental backups, Oracle Integration Classic
asks if you want to delete both the full backup and its linked incremental backups.

Manage Integrations and Errors

You can manage integration and process errors in Oracle Integration Classic (user-
managed).
Activate the service in Oracle Integration Classic when the integration is ready to go live and
you can deactivate an active Integration. You can modify or clone the integration. Delete an
integration that is no longer needed. See Managing Integrations in Using Integrations in
Oracle Integration.
You can manage errors from the Errors pages in Oracle Integration Classic at the integration
level, connection level, or specific integration instance level. See Managing Errors in Using
Integrations in Oracle Integration.

Manage SSL Certifications

You can upload and update security certificates in Oracle Integration Classic (user-managed)
to validate external connections.
Certificates are used to validate outbound SSL connections. If you make an SSL connection
in which the root certificate does not exist in Oracle Integration Classic, an exception is
thrown. In that case, you must upload the appropriate certificate. A certificate enables Oracle
Integration Classic to connect with external services. If the external endpoint requires a
specific certificate, request the certificate and then upload it into Oracle Integration Classic.
You can update or delete certificates you uploaded into Oracle Integration Classic.
For more information about managing SSL certificates in Integrations, see Managing Security
Certificates in Using Integrations in Oracle Integration.
For more information about managing SSL certificates in Processes, see Manage Security
Certificates during Runtime and Manage Security Certificates during Design Time in Using
Processes in Oracle Integration.

9-31
 Chapter 9
Manage Instance History

Manage Instance History

You can determine when to purge the data in your database. You can also view the
notification and quiesced thresholds for your database and the percentage of the
database that has been used.
Instance history is automatically purged periodically, based on settings in Oracle
Integration Classic (user-managed). See Archive and Purge Data in Using Processes
in Oracle Integration.

Configure Settings for Error Logs

Need to troubleshoot errors? As an administrator, you can change logging levels and
download logs for Oracle Integration Classic (user-managed).
Use caution when changing logging levels because increasing them can affect
performance. Reset logging levels back to default settings after troubleshooting.
1. From the Home page, select Settings, then Logging.
The Logging screen is displayed. By default, loggers are contained within folder
containers, and the number of loggers contained (collapsed) within the folder is
listed after the folder name.

2. Filter and sort the logging list.

You can filter in several ways:
• Show Only: Select one or more options to limit the list. Note that loggers or
folders must meet all selected options to be listed.
– Oracle Integration: Displays loggers related to Oracle Integration Classic
components.
– Top Containers: Displays the two top levels of folder containers.

9-32
 Chapter 9
Use SSH to Sign In to Oracle Integration Classic (User-Managed)

– Unsaved Changes: Displays loggers whose levels you have changed but
haven’t saved, as indicated by an Unsaved icon.

• Filters Menu: Select Open Filters Menu to view loggers by their status (at
default, or increased or decreased) or by their selected logging level. Filter settings
display below the search field as you specify search criteria.
3. Search for logs.
In the Search field, enter a logger name (or partial name) and press Enter. Searching is
case sensitive. For example, enter [Link] to list all loggers that begin with those
characters. Note that searching is performed within the filtered list. For example, if the
Top Containers filter is selected, only the top containers are searched.
4. Change logging levels as needed.
• Use the up and down icons in the Logging Level column to change a logger level.
As you increase or decrease, an unsaved icon displays adjacent to the new logging
level to indicate unsaved changes. The Status column indicates whether you
increased or decreased the level and lists the default level.
• When a logging level lists Inherited, this indicates that its own current level is
inherited from its parent package because it doesn’t have a default level set. Children
packages may have a different level. Changing a package level will automatically
change the logging level of its children if they inherit from it (if they don’t have a
specific logging level set).
• To return to previous settings, click Revert and revert to either the last saved
configuration or set all levels back to their default level.
5. Save your changes. Download logs as needed.
Click Download Logs and save the entire logging file to a zip file.

Use SSH to Sign In to Oracle Integration Classic (User-

Managed)
You must specify the opc username when using SSH to log in to the Oracle Integration
Classic virtual machine with a private key.

Diagnose Oracle Integration Classic (User-Managed) Problems

Oracle Integration Classic (user-managed) provides log files containing reports of an event,
errors, warning messages. You can diagnose problems using these log files.

Topics:
• Access and View Diagnostic Logs
• Export Suite-Generated Artifacts
• Collect Database Statistics
• View System Health

9-33
 Chapter 9
Diagnose Oracle Integration Classic (User-Managed) Problems

Access and View Diagnostic Logs

Use log files such as WebLogic Server log files or Java Flight Recorder to diagnose
problems, and report incidents in Oracle Integration Classic (user-managed).

Topics:
• Use WebLogic Server Logs
• Use Java Flight Recorder Performance Profiles
• Use Oracle Integration Report Incidents

Use WebLogic Server Logs

Use WebLogic Server Administration Console logs to diagnose errors.
To find the log files in WebLogic Server Administration Console:
1. Sign in to the Oracle Cloud Infrastructure Console.

2. Click Manage this service and select Open WebLogic Server Console.
A new browser opens and you are redirected to the login page.
3. Enter the user name and password you provided when you created the service
instance.
4. In the Domain Structure area, expand Diagnostics.
5. Click Log Files.
The Log Files table appears.
6. Select the option to the left of the log file you want to view.
7. Click View.
The log file you selected appears in the table.

Note:
If you do not find the information you are looking for, click the Customize
this table link above the log file and select the Time Interval or use the
other filter options available.

Use Java Flight Recorder Performance Profiles

You can use Oracle’s commercial profiling tools, Java Flight Recorder and Java
Mission Control, to analyze the performance of applications deployed on Oracle Java
Cloud Service.
Java Flight Recorder (JFR) and Java Mission Control (JMC) collect detailed runtime
information so that you can analyze incidents after they occur. JFR, available in Oracle
HotSpot JVM, is a performance monitoring and profiling tool that records diagnostic
information on a continuous basis, making it always available, even in the wake of
catastrophic failure such as a system crash. JMC enables you to monitor and manage

9-34
 Chapter 9
Diagnose Oracle Integration Classic (User-Managed) Problems

Java applications without introducing the performance overhead normally associated with
these types of tools. It includes the JFR user interface, which allows users who are running a
Java Flight Recorder-compliant version of Oracle HotSpot to view JVM recordings, current
recording settings, and runtime parameters. The JFR interface includes the Events Type
View, which gives you direct access to event information that has been recorded in the .jfr file,
such as event producers and types, event logging and graphing, event by thread, event stack
traces, and event histograms.

Basic Workflow for Profiling Applications with JFR

Monitoring applications with JFR comprises these steps:
1. Enable JFR in your WebLogic Server instance.
2. Obtain the flight recording by generating a diagnostic image capture.
3. Analyze the recording with the Flight Recorder UI.

Enable JFR in Your WebLogic Server Instance

Because it is a commercial feature, if WebLogic Server is configured with Oracle HotSpot,
Java Flight Recorder is, by default, disabled. To enable it, use the following JVM commands
in the startup script for the WebLogic Server instance in which the JVM runs:

-XX:+UnlockCommercialFeatures -XX:+FlightRecorder

Note:
The sequence of these commands is critical: +UnlockCommercialFeatures
command advises the JVM to recognize the command +FlightRecorder. The
commands must be entered in that order or the JVM will not start.

For example:

java -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -

XX:FlightRecorderOptions=defaultrecording=true,maxage=20m MyApp

You can also enter the +UnlockCommercialFeatures and +FlightRecorder commands in the
WebLogic Server configuration file’s JAVA_OPTIONS (or equivalent) variable.

For more detailed information on enabling JFR, see Running Java Flight Recorder in the
Java Platform, Standard Edition Java Flight Recorder Runtime Guide.

Obtain the Flight Recording by Generating a Diagnostic Image Capture

The diagnostic image capture itself is a single JFR file that contains individual images
produced by the different server subsystems. If the JFR file is available, it is included in the
diagnostic image as the file [Link].

You can generate a diagnostic image capture on-demand — for example, from the WebLogic
Server Administration Console, Fusion Middleware Control, WLST, or a JMX application — or
as the result of an image action. To generate a diagnostic image captures and configure the
location in which they are created, see Configuring and Capturing Diagnostic Images in

9-35
 Chapter 9
Diagnose Oracle Integration Classic (User-Managed) Problems

Oracle® Fusion Middleware Configuring and Using the Diagnostics Framework for
Oracle WebLogic Server.

Analyze the Recording with the Flight Recorder UI

Once you’ve obtained the recording, you can then view and analyze it by using the
Flight Recorder user interface, a JMC component. Assuming you are running a Java
Flight Recorder-compliant version of Oracle HotSpot, the JFRUI allows you to view
JVM recordings, current recording settings, and runtime parameters. The JFR
interface includes the Events Type View, which gives you direct access to event
information that has been recorded in the JFR file, such as event producers and types,
event logging and graphing, event by thread, event stack traces, and event
histograms. Some of the activity you can monitor on the JFR UI includes:
• Display Event Data for a Product Subcomponent
• View the Event Log to Display Details
• Track Execution Flow by Analyzing an Operative Set
• Expand the Operative Set and View Correlated Diagnostic Data
Use of the JFR UI for these tasks and more is described in greater detail in Analyzing
Java Flight Recorder Data in Oracle® Fusion Middleware Configuring and Using the
Diagnostics Framework for Oracle WebLogic Server.

Use Oracle Integration Report Incidents

You can report incidents for problematic issues that occur during design time in Oracle
Integration (for example, being unable to open an integration, the failure of connection
testing, or the failure of artifact regeneration).
To report incidents in Oracle Integration, see Report Incidents in Using Integrations in
Oracle Integration.

Export Suite-Generated Artifacts

Download artifacts of an integration to view and diagnose problems.
You can download artifacts as a zip file using the Download Artifacts option in Oracle
Integration, see Downloading Generated Artifacts for an Integration in Using
Integrations in Oracle Integration.

Collect Database Statistics

Collect database statistics to diagnose performance problems by comparing statistics
captured in a baseline to those captured during a period of poor performance.
See Gathering Database Statistics in the Oracle Database Performance Tuning Guide.

View System Health

You can view information about the system health of Oracle Integration components.
As you navigate around Oracle Integration, you receive a system health state that is
not older then five minutes. The only exception is the Messaging Service state, which
may take longer than five minutes to update.

9-36
 Chapter 9
Delete an Oracle Integration Classic (User-Managed) Instance

The state of system health is viewable from multiple locations in Oracle Integration instance:
• From the main banner of pages
• From the Integrations, Connections, and Lookups pages
• From the mapper or expression builder
• From the System Health section on the Dashboard page
See View the Dashboard in Using Integrations in Oracle Integration.

Delete an Oracle Integration Classic (User-Managed) Instance

When you no longer require an Oracle Integration Classic (user-managed) instance, you can
delete it.
Oracle Integration Classic can be running or stopped before you attempt to delete it. If the
instance is stopped, you must check Force Delete on the Delete Service dialog for proper
schema cleanup.
When you delete an Oracle Integration Classic instance:
• Resources such as IP addresses are removed.
• The Oracle Database Cloud Service database deployment is not deleted when you
delete the Oracle Integration Classic instance.
• The object storage container is not deleted when you delete the Oracle Integration
Classic instance.
To delete an Oracle Integration Classic instance:
1. Sign in to the Oracle Cloud Infrastructure Console.
2. Find the instance you want to delete.

3. From the menu, select Delete.

4. In the Delete Service dialog box that opens, set the following options:
• Force Delete—(Optional): Select this check box if you want the service instance to
be deleted even if the database deployment cannot be reached to delete the
database schemas. If enabled, you may need to delete the associated database
schemas manually on the database deployment if they are not deleted as part of the
service instance delete operation.
• Database Administrator User Name: Enter the name of the database administrator
user that was specified when the database deployment was created. This user owns
the instance’s repository and schemas. If you have specified two databases, specify
the name of the administrator for the database deployment for the Oracle required
schema.

9-37
 Chapter 9
Delete an Oracle Integration Classic (User-Managed) Instance

• Database Administrator User Password: Enter the database administrator

user password for the database deployment that contains the Oracle required
schema.
• Skip Backup: Select to skip the backup of the terminated instance.
5. Click Delete.
Once deleted, the Oracle Integration Classic instance is removed from the list of
service instances displayed on the Oracle Integration Classic instance Console.

9-38
10
Troubleshoot Oracle Integration Classic
(User-Managed)

Topics:
• Provision an Instance Without the Correct User Roles Causes Failure
• Provision Oracle Integration Classic (User-Managed)
• 504 Gateway Timeout Error May Require Editing an Instance's Load Balancer Access
Rules Manually to Add a New IP Address
• Troubleshoot cURL Command Issues When Configuring an IP Network
• Database Backups May Use Up Disk Space and Cause Oracle Integration Classic
Servers to Shut Down
• Troubleshoot Backup and Restore Issues
• Troubleshoot Patching Issues
• Oracle Integration Classic (User-Managed) Fails to Connect to the Database Instance

Provision an Instance Without the Correct User Roles Causes

Failure
If you attempt to provision Oracle Integration Classic (user-managed) without the required set
of user roles, you receive errors. For example, the following error occurred because the user
account did not possess the correct role for provisioning an Oracle Database Classic Cloud
Service instance.

Mar 7, 2018 7:41:57 PM UTC Service creation request accepted.

Mar 7, 2018 7:41:57 PM UTC Initializing OIC7786QS
Mar 7, 2018 7:42:34 PM UTC Failed to create Compute resources for Database
Server...[Compute Error: Unable to authenticate]
Mar 7, 2018 7:42:34 PM UTC Initiating Database Service Termination...

To successfully provision Oracle Integration Classic, ensure that your user account is
assigned the correct roles. See Assign the Correct User Roles to Create an Instance.

10-1
 Chapter 10
Provision Oracle Integration Classic (User-Managed)

Provision Oracle Integration Classic (User-Managed)

Ensure that you satisfy the following prerequisites before provisioning Oracle
Integration Classic (user-managed). Not doing so prevents you from successfully
provisioning Oracle Integration Classic.
• Know the Oracle Cloud Infrastructure Object Storage Classic account name when
you start to provision Oracle Integration Classic. This account name is
automatically created when you purchase your universal credits. You specify the
account name when provisioning Oracle Integration Classic with the provisioning
wizard or with the Oracle Cloud Stack templates. See Create an Oracle Integration
Classic (User-Managed) Instance for instructions on how to obtain the account
name.
• Review the minimum system requirements. See Create an Oracle Integration
Classic (User-Managed) Instance.
• If you want to provision Oracle Integration Classic with the provisioning wizard,
ensure that you first provision Oracle Database Classic Cloud Service. This is
because when using the provisioning wizard, you are prompted to specify the
Oracle Database Classic Cloud Service login credentials and service name. If you
provision Oracle Integration Classic with the Oracle Cloud Stack templates, this is
not a requirement because the Oracle Database Classic Cloud Service instance is
automatically provisioned for you.

504 Gateway Timeout Error May Require Editing an

Instance's Load Balancer Access Rules Manually to Add a
New IP Address
If an Oracle Integration Classic (user-managed) instance is provisioned when the
virtual load balancer has temporarily switched from, for example, three IP addresses
to one IP address due to a load situation, the instance’s four load balancer access
rules are created with only that one IP address even though the virtual load balancer
has multiple IP addresses. The access rule ideally should have all load balancer IP
addresses in comma-separated fashion.
The missing two IP addresses mean that when the Oracle Integration Classic instance
requests are routed through all load balancer IP addresses to the Oracle Integration
Classic instance, the requests coming from the unknown two IP addresses time out
(504 Gateway Timeout errors). Only requests routed from the registered IP address
route successfully.
To resolve this situation, manually disable (from the Oracle Platform Service Manager
console) the four load balancer access rules (ora_lb2admin_7001_1,
ora_lb2ms_7001_1, ora_lb2admin_8001_1, and ora_lb2ms_8001_1) and add a
duplicate set of four rules (with different names) with all load balancer IP addresses
included.

10-2
 Chapter 10
Troubleshoot cURL Command Issues When Configuring an IP Network

Troubleshoot cURL Command Issues When Configuring an IP

Network
Note the following potential issues when executing curl commands to create the virtual
Oracle Load Balancer as a Service.
• If you see the following exception while executing curl commands, use the -k option in
the command (for example, curl -i -k -X POST).

curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: [Link]

curl failed to verify the legitimacy of the server and therefore could
not
establish a secure connection to it. To learn more about this situation
and
how to fix it, please visit the web page mentioned above.

• When you receive an HTTP 500 Internal Server error, your JSON file content is likely
not correct. Check for special characters such as ”.
• When you submit a request and the curl command does not respond and print any
output, ensure the Oracle Load Balancer as a Service URL is accessible from a browser
and you are not behind a firewall/inside a corporate network.

Database Backups May Use Up Disk Space and Cause Oracle

Integration Classic Servers to Shut Down
If you cannot restart your managed server (it enters a failed state) and you receive the
following error, this may be due to excessive disk space usage on the database virtual
machine (for example, the backup mount is at 75% for /u01).

Received exception while creating connection for pool "SOALocalTxDataSource":

ORA-00257: Archiver error. Connect AS SYSDBA only until resolved.

This can result in archiving issues and the Oracle WebLogic Servers can only connect to the
database as SYSDBA.

To resolve this issue, increase the mount space. This enables the database to run again. If no
issues are found in the archive logs, clean up the files occasionally to avoid similar issues in
the future.
See Back Up and Restore an Oracle Integration Classic (User-Managed) Instance.

Troubleshoot Backup and Restore Issues

After a backup. if you scale in or out a managed server and then attempt to restore the
backup, additional managed servers are created during backup restoration. You need to
manually delete the additional managed servers for Oracle Integration Classic (user-
managed) Home page to display properly.

10-3
 Chapter 10
Troubleshoot Patching Issues

To delete additional managed servers:

1. Sign in to the Oracle Cloud Infrastructure Console.
2. Click the name of your Oracle Integration Classic instance.

3. On the page, click and choose Open WebLogic Server Console to open the
WebLogic Server Console.
A new browser opens and you are redirected to the WebLogic Server console’s
login page.
4. Sign in to Oracle WebLogic Server Administration Console.
5. In the Domain Structure pane, select Environment, then select Servers.
6. In the Change Center pane, click Lock & Edit.
7. Select the additional managed servers and click Delete. Click OK to confirm.
8. In the Change Center pane, click Activate Changes.

Troubleshoot Patching Issues

Patching Precheck fails if the current user session is locked. You need to unlock the
user session before performing prechecks for patching Oracle Integration Classic
(user-managed).
To unlock the user session:
1. Sign in to the Oracle Cloud Infrastructure Console.
2. Click the name of your Oracle Integration Classic instance.

3. On the page, click and choose Open WebLogic Server Console to open the
Oracle WebLogic Server Administration Console.
Alternatively, you can use the following URL format to access the console:
[Link]
A new browser opens and you are redirected to the Oracle WebLogic Server
Administration Console login page.
4. Sign in to Oracle WebLogic Server Administration Console as a WebLogic server
administrator.
5. In the Domain Structure pane, select Environment, then select Servers.

10-4
 Chapter 10
Troubleshoot Patching Issues

6. In the Configuration tab, verify the state of all the managed servers. Ensure that the state
for all the managed servers is displayed as Running.

7. In the Change Center pane, click View Changes and restarts.

8. On the Change and Restarts page, click the Other Edit Sessions tab and ensure that
there is only one row by default listed under the Current Edit Sessions table.

If the Owned By column in the Current Edit Sessions table is set to

JaaS_System_WLS_Admin, click Lock & Edit. Now you’ll see the logged-in user ID in
the Owned By column.

10-5
 Chapter 10
Oracle Integration Classic (User-Managed) Fails to Connect to the Database Instance

9. Click the Change List tab and verify if the Pending Changes table has no items
to display.

10. In the Change Center pane, click Release Configuration.

Oracle Integration Classic (User-Managed) Fails to Connect

to the Database Instance
If Oracle Integration Classic (user-managed) fails to connect to the database instance
for a period of four hours or more, you should restart your Oracle Integration Classic
instance.
By default, the maximum amount of time that an Oracle Integration Classic instance
tries to recover from a database connection failure without any intervention is four
hours. After this period of time, manually restart the Oracle Integration Classic
instance if the connectivity issue is not resolved.

10-6