Oracle Integration Cloud: Building Integrations That Survive Production · Module 3 · Connections and adapters
Connectivity agents, and when you need one
Lesson 30 of 175 · 2 min
Reaching a system that is not on the internet. A database inside a client's network, a file server behind a firewall, an application nobody is going to expose. THE AGENT IS A SMALL PIECE OF SOFTWARE THAT RUNS INSIDE THE CLIENT'S NETWORK and connects OUTWARD to OIC. That direction is the whole design: nothing has to be opened inbound, which is what makes it acceptable to a security team that will not open a port. WHERE IT RUNS is a real decision. A server inside the network, with access to the systems it must reach, that somebody keeps patched and running. It is infrastructure, not configuration, and that is the sentence to say early. WHO ENDS UP OWNING IT IN A CLIENT ESTATE IS THE QUESTION NOBODY ASKS AND EVERYBODY REGRETS. The integration consultant installed it; the client's infrastructure team does not know it exists; and it runs on a…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.
In this module: Module 3 · Connections and adapters
- 1What a connection is
- 2Choosing an adapterFree preview
- 3The REST adapter
- 4The SOAP adapter
- 5The FTP adapter
- 6The database adapter
- 7Testing a connection properly
- 8One connection or several
- 9Connectivity agents, and when you need one
- 10What breaks: four connection failures
- 11Lab briefing · Three connections, three systems