Validation

• ODI Version 12.2.1.4.200721.1540

Note: this article was originally written for Oracle Data Integrator Cloud Service and was adapted to cover Oracle Data Integrator Marketplace, the current offering for ODI in the Cloud.

The #1 benefit of ODI Marketplace (ODI MP) is that when you provision your ODI image, the product is ready to use: the repository is created for you automatically, you studio is ready to connect to that repository, and your agent is up and running, ready to execute your mappings.

The one question that remains unanswered is how to use this ready-to-use environment with multiple developers.

1. Deploying ODI Marketplace

Start by deploying ODI MP following the Oracle documentation available here: Using Oracle Data Integrator on Oracle Cloud Marketplace.

As detailed in above document, the Marketplace image comes with ODI Studio which users will access with VNC. Do not try to use ODI on Premise when connecting to a Cloud Repository or you will experience very painful performance and timeout .... ODI Studio is chatty and needs to be close to its Repository.

2. Number of developers per Marketplace image

When deploying ODI Marketplace, the choice of the shape has a direct impact on the number of developers that can work run in parallel on that same image.

We have observed that:

1 OCPU=1 Agent and/or 1 OCPU=1 Studio

So, deploying ODI on a 4 OCPUs shape would allow to deploy, for example, 2 Agents and to connect using 2 distinct Studio, using distinct VNC Servers.

In order to have multiple users connecting to the same VNC Server, create multiple Linux users on the server where your ODI is deployed as described in the Article

"Oracle Linux: How to configure VNC Server on OL6" (Doc ID 2113867.1) or  https://wiki.centos.org/HowTos/VNC-Server.

3. Adding more developers

If you have more developers than what can be served by the amount of OCPU in your ODI instance on Marketplace, you will need to expand your environment. In the above example, if you have 2 agents and more than 2 developers working in parallel, you need to expand your footprint. The recommended approach is to deploy another instance of ODI on Marketplace for each additional developer (each instance with 1 single OCPU). When you provision a new instance of ODI, you have a choice of either creating a new repository or connecting to an existing one: select the latter option to connect each new Studio to the existing repository, and continue to leverage the agent(s) of the original instance.

Conclusion

It is important to understand the metrics that constrain the comfort of developers with ODI on Marketplace, and how to expand the number of developers in that environment. We saw how this can easily be achieved with additional instances on ODI on Marketplace, all sharing the same repository.

Beyond the basics

If you are interested in leveraging ODI Marketplace, the following articles might also be of interest to you:

Deploying Oracle Data Integrator Marketplace in a Private Subnet with Autonomous Database

Connecting Oracle Data Integrator Marketplace Studio to Autonomous Databases

Deploying Oracle Data Integrator Marketplace in a Public Subnet with Autonomous Database

Reference Architecture - Fusion SaaS Data Replication into ADW : Using ODI Marketplace and BICC

Reference Architecture - Salesforce Data Replication into ADW : Using ODI Marketplace