Oracle OCI Architecture

Hello everyone, let's start talking about OCI. 

Picture details:

Tenancy 

When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for your company, a secure and isolated partition where you can create, organize, and administer your cloud resources.

To use any of the API operations, you must be authorized in an IAM policy. If you’re not authorized, talk to an administrator.

                                    

Compartment  

The compartment is a logical container. This container organizes and controls access to the Oracle Cloud Infrastructure (OCI) Resources (Network, Storage, Compute, Load Balancer, etc.) created within that compartment. You impose some policies to that compartment, which restricts who can use the resources created within than chamber other than administrators of your account.

Route Tables 

VCN uses virtual route tables to send traffic out of the VCN (for example, to the internet, to your on-premises network, or a peered VCN). These virtual route tables have rules that look and act like traditional network route rules you might already be familiar with. Each rule specifies a destination CIDR block and the target (the next hop) for any traffic that matches that CIDR.

CIDR - Classless inter-domain routing - Classless inter-domain routing (CIDR) is a set of Internet protocol (IP) standards that are used to create unique identifiers for networks and individual devices. The IP addresses allow particular information packets to be sent to specific computers.

Security List

A security list is a group of one or more instances that you can specify as the destination or source in a security rule. Instances within a networking group can communicate adequately with one another on all ports. When you attach an instance to a security list, the inbound and outbound policies defined in the security list apply to that instance.

Availability Domain

Availability Domain (AD) is one or many data centers located within a region. A region is composed of three availability domains. Services/Resources are related to a region (like VCN) or Availability Domain Specific (like Compute). We can also say that a low latency connects all the available domains in a region, high bandwidth network, which makes it possible for you to provide high-availability connectivity to the Internet and customer premises.

Service Gateway

A service gateway is a single access point and acts as a proxy for multiple services. A service gateway enables transformations, routing, and standard processing across all the services. A service gateway module is a single mediation that handles the requests for multiple service consumers and providers. Oracle Cloud Infrastructure service gateway allows access to Oracle services within the region to protect your data from the internet. Oracle Cloud Infrastructure service gateway enables consumer-to-service private connections (C2S). 

Let's share some examples of integration with OCI and on-premise systems:

  

1 - The Oracle Database Adapter - enables you to integrate the Oracle database residing behind the firewall of your on-premises environment with Oracle Integration through the use of the on-premises connectivity agent. Use the Oracle Database Adapter to poll for new and updated records for processing in Oracle Integration. For example, any new record added to the Employee table in your Oracle database can be synchronized with Oracle HCM Cloud using Oracle Integration. Besides, use the Oracle Database Adapter to execute SQL queries or stored procedures in the Oracle database. 

2- The Oracle SalesForce Adapter - Supports all custom objects defined by the user and custom fields created at SalesForce.com, along with the standard objects and fields.

Support for consuming custom Apex classes developed and exposed as SOAP services in SalesForce.com.

3- The REST Adapter - supports standard and custom HTTP request and response headers in the invoke and trigger directions.

• Outbound (Invoke) direction
• HTTP headers enable you to use an outbound invocation to specify header properties. Many REST APIs expect certain properties to be specified in the HTTP headers (similar to SOAP APIs, where you can specify header properties such as the WS address). Use the standard HTTP headers to specify these properties. You can also use the custom HTTP headers to specify properties. The REST APIs can expect the client application to pass properties in the custom headers, which can influence the behavior of the APIs. The standard and custom HTTP header properties configured in the Adapter Endpoint Configuration Wizard automatically start appearing in the mapper. You can map the header properties in the mapper.
• Inbound (trigger) direction
• You can expose integration flows as REST endpoints and enable client applications to populate the properties in the standard and custom headers. You can use these properties to create routing expressions in your integrations. The standard and custom HTTP header properties configured in the Adapter Endpoint Configuration Wizard automatically start appearing in the mapper. You can map the header properties in the mapper. 

I am going to be providing more details related to Oracle adapters and OCI integration in the next articles, stay tuned.

Thiago