A-Team Chronicles

About The A-Team and A-Team Chronicles

The A-Team is a central, outbound, highly technical team comprised of Enterprise Architects, Solution Specialists and Software Engineers within the Oracle Product Development Organization. The team works closely with customers and partners, world wide, providing guidance on architecture, best practices, troubleshooting and how best to use Oracle Cloud Services and products to solve customer business needs. They specialize in using Cloud Solutions across IaaS, PaaS, SaaS as well as On-premise and hybrid deployments.

The A-Team provides this type of support by working with Oracle Consulting, Support and Sales – engaging in the toughest of situations, solving the hardest problems and the greatest of challenges.

The A-Team is lead from Oracle Headquarters in Redwood Shores, CA, but A-Team members are located and positioned globally, so that we are better prepared to respond quickly, and within an appropriate timezone for our Global customers.

“If you have a problem, if no one else can help, and if you can find them, maybe you can hire the A-Team”


Best Practices to model customer, supplier, and partner hierarchies in Oracle Fusion Cloud

In continuation to my previous blog on Best Practices to model parties in Oracle Fusion Cloud, I will discuss common use cases, design considerations, and options around managing hierarchies (customer, supplier, partner) within Oracle Application Cloud.

My objective for this blog, is to discuss the hierarchy capabilities within Oracle Fusion application cloud that supports functional use of hierarchies across Customer Experience, Procurement and Financials cloud applications.

The details provided here are guidelines that can be leveraged as guidance during your customer / supplier / partner hierarchy design for your Oracle Fusion application implementation.
A hierarchy is typically a tree like structure where branches and nodes are arranged acc…

Read more

Importing into the Autonomous Data Warehouse using Oracle Data Pump

This post details the steps required to import into the Autonomous Data Warehouse (ADW) using the Oracle Data Pump Import utility on Oracle Classic Infrastructure (OCI).

OCI Compute    Oracle-Linux-7.6-2018.11.19-0
Instant Client for Linux x86-64 (64-bit)
SQL Developer


An Oracle Cloud Account and an OCI Tenancy
Access to an ADW instance
Administrator Credentials to both of the above
An export file (.dmp) created by the Oracle Data Pump Export utility
The following components exist in the OCI tenancy see Setting Up the Prerequisites
— Customer Compartment under the root compartment of the tenancy
— Virtual Cloud Network
— Object Storage Bucket
— OCI Object Storage Administrator U…

Read more

Connecting Oracle Data Integrator Cloud Service to the Autonomous Data Warehouse

This post details the steps required to create connections in Oracle Data Integrator Cloud Service (ODICS) on Oracle Cloud Infrastructure (OCI) to the Autonomous Data Warehouse (ADW). It demonstrates both the Thin and Oracle Call Interface (oci) versions of the Oracle JDBC driver. It is a companion post to Connecting Oracle Data Integrator Studio to the Autonomous Data Warehouse which uses ODI Studio on Windows and Connecting DIPC ODI Studio to the Autonomous Data Warehouse which uses ODI Studio in the Data Integration Platform Cloud (DIPC).

ODICS is a service level of Java Cloud Service (JCS). For additional details about JCS, refer to About Java Cloud Service Instances in Oracle Cloud Infrastructure. This means that you specify the ODI service level when you provision JC…

Read more

Add a Logout Function to the Default Log Out Menu Item in Oracle Integration Cloud Visual Builder

Each Visual Builder (VBCS) web application in Oracle OICS (Oracle Integration Cloud Service) comes with a default shell. The default shell displays a simple title, username (as a menu button) and a Log Out menu item. See picture below.


However, if you click the Log Out button, nothing happens. This is because no event handler is configured for the Log Out menu item. Adding an event handler to the Log Out menu item to perform logout function is quite easy.

Add Logout Function
Follow the image below to open default shell page (1), open page structure (2), expand the page structure and click on menu component (3), select events on the right (4) and expand “+New Event” menu button and select “ojAction” (5).

Now you should see an empty action ch…

Read more

Trigger OIC Integration Using OAuth

As businesses move to the cloud there is a high demand for securing/protecting their HTTP resources from unauthorized access. There are several approaches to protecting these resources which include SAML for SOAP service, OAuth for REST services, HTTP basic for both, and sometimes home grown proprietary mechanisms. It may not be widely known yet, but all Oracle Integration Cloud (OIC) REST endpoints are OAuth protected and can be triggered from a client using OAuth 2.0 (August 2018 – https://doc…

Read more

Loren Penton

Loren Penton is a Principal Solution Architect in the Data Integration A-Team where he supports the Oracle GoldenGate product line and its integration to Kafka, Hadoop, JMS, and all sorts of databases - starting with Oracle obviously. Loren has 20 years’ experience in the design and testing of Oracle GoldenGate solutions and over 30 years’ experience designing solutions for the banking, aerospace, and healthcare industries.

Mani Krishnan

Mani Krishnan is a Cloud Solutions Architect in the 'A-Team', where he's mainly focused on integration of SaaS applications and cloud-based application integration tools. Mani has over 20 years integrating enterprise applications in various capacities at large enterprises. He is currently based in Pleasanton, California. His skill set includes standards-based application integration, integration platform as a service (iPaaS), SaaS extensions and digital transformation using both with Oracle and other industry leading tools. Mani joined Oracle in 2016 and has since worked successfully with clients around the world.