2. Agenda
Encrypt and Decrypt files
Stage file action
Lookup
Connectivity or on-premises Agent
Connectivity Agent Architecture
Agent in High Availability (HA)
Agent Group
Connectivity Agent Constraints
Pre-requisites to install agent
3. Connectivity Agent?
A connectivity agent or on-premises agent is a lightweight
component which solve the problem of cloud to on-premises
integrations.
The agent is required to exchange messages with on-premises
application such as database, Oracle E-Business Suite (EBS),
Systems, Applications and Products (SAP), Ariba etc. This
connectivity agent can be installed behind the firewall to
access on-premises applications.
4. Connectivity Agent Architecture
The agent work as a bridge
between OIC and on-premises
applications and without that
communication is not possible.
The OIC does not send any
request to connectivity agent but
connectivity agent does this job.
Agent sends his heartbeat signals
to Oracle Integration regularly to
tell that I am live to serve your
requests. In addition to that, agent
regularly poll for any design and
run time work on which agent need
to act upon.
5. Connectivity Agent Architecture
Design time work includes set of activities like Test connection,
activation or deactivation of integrations.
Same ways there are run time activities on which agent need to
act upon. For any communication between Integration Cloud
and on-premises system such as Database, EBS etc.
6. Agent Group?
An agent group is a unique identifier which represent the
connectivity agent and every connectivity agent must be
associated with an agent group.
You must create an agent group in Oracle Integration before you
can run the connectivity agent installer. For a single Oracle
Integration instance, you can create up to five agent groups. If
this limit exceeds you will get error as per below screenshot.
7. Connectivity Agent in HA
To tackle the high traffic on the single connectivity agent, you
can install connectivity agent in High Availability (HA) mode.
You can associate maximum two agents with single agent
group. To ensure high availability both the agent should run on
different host.
The high availability mode ensures the transactions will
continue if any one of the agents goes down or any hosts
becomes unavailable. You do not need to install any Load
Balancer (LB) to bring agents in HA mode. You just need to
install another agent on different host and associate with same
agent group.
8. Connectivity Agent Constraints
1) 10 MB Payload limit
The OIC agent can handle payload in size which is less than 10
MB in a single transaction.
Payload Size Exceeds Threshold.
The payload data size: "16089549" exceeds the configured payload threshold size: "10000000" .
No fix is required since the adapter would reject the message. at
oracle.tip.adapter.file.inbound.InboundSyncTranslatorDelegate.xlate(InboundSyncTranslatorDelegate.ja
va:306) ... 7 more
9. Connectivity Agent Constraints
2) 240 seconds Timeout
Every transaction sent out to the on-premises application via
agent must be completed within 240 seconds.
oracle.cloud.cpi.agent.transport.aq.CpiAQException: Message not
received within 240 seconds of wait interval.
10. Connectivity Agent Pre-requisites
Pre-requisites Requirement
JDK The agent is supported with Oracle JDK 8+
Operating System The agent is certified on below Operating
systems:
Oracle Enterprise Linux 6.x, 7.2, 7.5
RedHat Enterprise Linux 6.6, 7.2,7.5
Suse Linux Enterprise Edition 12 SP2
Windows Standard Edition 2016
Memory At least 8 GB memory with 4GB of heap size
dedicated for agent JVM
Storage 500 MB
Network The VM should be able to communicate with
on-premises server as well as with OIC
