Tuesday Feb 02, 2016

A-Team Article: Integrating Oracle Data Integrator (ODI) On-Premise with Cloud Services

Benjamin Perez-Goytia of the Data Integration Solutions A-Team provides a very matter of fact summary regarding Cloud Integration with Oracle Data Integrator (ODI). For all the details: Integrating Oracle Data Integrator (ODI) On-Premise with Cloud Services.

The blog post details how to integrate Oracle Data Integrator (ODI) on-premise with cloud services.  Cloud computing is a service or utility in high demand and enterprises find themselves with a mix of on-premise data sources and cloud services.  Ben describes how Oracle Data Integrator (ODI) on-premise can enable the integration of both on-promise data sources and cloud services.

Happy reading! For more A-Team reads on ODI, browse through the A-Team Chronicles.

Friday Dec 18, 2015

Oracle Management Pack for Oracle Data Integrator for Enterprise Manager 13.1 is out! Make the most of the value of your Oracle Data Integrator investments!

We’ve mentioned before that to help you make the most of Oracle Data Integrator, and to deliver a superior ownership experience in an effort to minimize systems management costs, Oracle’s Management Pack for Oracle Data Integrator is a great addition! As a quick refresher: this product leverages Oracle Enterprise Manager Cloud Control's advanced management capabilities to provide an integrated and top-down solution for your Oracle Data Integrator environments. Management Pack for Oracle Data Integrator supports both 11g (11.1.1.7.0 and higher) and 12c versions of Oracle Data Integrator (12.1.2, 12.1.3 and 12.2.1).

Management Pack for Oracle Data Integrator provides a consolidated view of your entire Oracle Data Integrator infrastructure. This enables users to monitor and manage all their components centrally from Oracle Enterprise Manager Cloud Control.


In review, important capabilities include:

Performance Monitoring and Management

Management Pack for Oracle Data Integrator streamlines the monitoring of the health, performance, and availability of each and all components of an Oracle Data Integrator environment – this includes Master and Work Repositories, Standalone and JEE agents, as well as source and target Data Servers.

Configuration Management

To ensure that the configurations of all critical Oracle Data Integrator components in production environments are consistent with staging or test environments, Management Pack for Oracle Data Integrator provides Configuration Snapshots to save working configurations into the Management Repository or into an external XML file. These snapshots can then be compared with the active configuration in staging or test environments, or against any historical snapshot. Configuration Comparison is the next logical step which thus allows you to ensure the consistency of configurations in your application environment. Going one step further, Configuration History keeps track of all configuration changes, which can help in diagnosing performance problems that may be related to configuration changes along the way.

Service Level Management

Management Pack for Oracle Data Integrator allows for a proactive method to monitor Oracle Data Integrator environments at all levels. Many out of the box metrics are automatically collected for each Oracle Data Integrator component (repositories, agents, sources, targets…) which then provides users the ability to set up alerts based on critical or warning thresholds. Notifications can be provided to users in various ways through emails or Simple Network Management Protocol (SNMP) options.

Historical Analysis and Reporting

While real-time metrics certainly come in handy, there is also something to be said for historical collection of data! Management Pack for Oracle Data Integrator stores collected metrics and configurations data in a central repository –allowing users to thus analyze the metrics in various incremental views that include; last 24 hours, last 7 days, last 31 days. In addition, customizable service and system dashboard functionality allows users to create reports on various services and systems for service level availability, usage, performance, and business indicators – all in an effort to facilitate strategic trend analysis and reporting.

In a nutshell, Oracle Management Pack for Oracle Data Integrator benefits include: reducing the costs associated with monitoring the overall Oracle Data Integrator infrastructure and providing visibility into complex Oracle Data Integrator deployments across the enterprise, minimizing troubleshooting and performance tuning efforts as well as improving the overall ability to efficiently monitor Service Level Agreement compliance using powerful alerting capabilities. (For additional detail and to review another blog on the subject, click here.)

Oracle Management Pack for Oracle Data Integrator is licensed separately. From an installation perspective it is packaged in the Fusion Middleware plug-ins for Enterprise Manager (version 12.1.0.4 and higher) and comes with the base Enterprise Manager 12c or 13c download. There is no separate installation file to download. More information can also be found here.

Try it out! Getting Started with Oracle Fusion Middleware Management Plug-in

Monday Dec 14, 2015

Oracle Data Integrator Webcast Recap: Special Topic - Cloud Application Adapter

If you missed our Oracle Data Integrator Webcast two weeks ago about the simplicity of leveraging Oracle Data Integrator (ODI) with Cloud technologies – take a look here: Oracle Data Integrator Special Topic:  Salesforce.com & Universal Cloud.


With the explosion of the number of Cloud Applications today, the topic is top of mind for many organizations. ODI coupled with Progress DataDirect’s JDBC drivers can be the perfect fit – find out by viewing the webcast! Thanks again to our guest speakers: Sumit Sarkar, Chief Data Evangelist at Progress Software and Christophe Dupupet, Director – A-Team, Cloud Solutions Architects at Oracle.

For additional posts about ODI and the Cloud, browse the A-Team Chronicles – one of the posts you will find: A Universal Cloud Applications Adapter for ODI.

For other ODI webcasts, please view the Oracle Data Integrator Demo Webcast Archives. Our next one will cover ODI’s 12.2.1 New Features and is scheduled for January 14, 2016 at 1pm ET/10am PT. Join us!

Friday Dec 11, 2015

Oracle Data Integrator 12.2.1 - Release Management with Deployment Archives

In earlier articles on ODI Lifecycle Management features we covered Managing Versions in Apache Subversion and Parallel Development using Subversion Branches. Now let’s explore the Release Management aspects addressed in ODI 12.2.1.

Deployment Archive

The release management use cases are addressed in ODI 12.2.1 through the newly introduced object called Deployment Archive. It is an archive file containing a set of ODI objects along an XML file containing archive details. It is the vehicle to promote objects from a development environment to the testing or production environment as depicted in below diagram. In a typical release process a Deployment Archive is first deployed in testing environment where the validations can be performed and after testing is done it is applied to a production environment.


Deployment Archive Types

There are four types of Deployment Archives

  1. Initial Deployment Archive – It is used to initialize a fresh ODI repository. It is created with all the objects in your development project.
  2. Patch Deployment Archive – As the name suggest it is used to apply patch containing a bug fix or enhancement to an ODI repository that is already initialized with Initial Deployment Archive. It usually contains only the object having the bug fix or enhancement and all its dependencies.
  3. Rollback Deployment Archive – A Rollback Archive facilitates restoring a pre-patch state of deployment environment. It is created when a Patch Deployment Archive is applied to an ODI Repository and contains the artifacts from the repository that are being updated by the patch.
  4. Execution Deployment Archive – It holds only the runtime executable objects and gets created along with Initial or Patch Deployment Archive. It is used to promote artifacts to ODI execution repository, which holds only executable objects.

Creating Deployment Archive

All Deployment archive related operations can be invoked from the ODI Studio menu. There are three options available for creating a Deployment Archive, which differs in the way the objects to be included in the Archive are selected.


 Each of these options allows you to
  • Select the type of Deployment Archive to create (if applicable)
  • Provide Archive Name
  • Specify the file location where the archive is created
  • Specify an Export key which is used to encrypt sensitive data in the exported object XML
  • Provide an option to exclude physical topology containing connectivity details.

Create from a VCS Label (Tag)

The objects from a Subversion Tag are included in the Deployment Archive.

Create from Repository > Full Repository

All the objects from the entire repository are included in the Deployment Archive. Since all the objects are included here, with this option you can create only the Initial Deployment Archive.


Create from Repository >Selected Objects

You can selectively add the objects you wish to include in the Deployment Archive. All dependencies of an object is also automatically included along with the object so that the Deployment Archive always contains a consistent set of objects that can be applied in any environment.

Viewing Deployment Archives

You can list and view the details of Deployment Archives from ODI Studio by specifying the folder location where all the Deployment Archives are created.


You can double click on any entry to the list of objects present under that archive.


Applying an Deployment Archive

An empty repository can be initialized with the Initial Deployment Archive.


If the repository is already initialized then you can apply a Patch deployment Archive to it.


While applying patch archive you can also specify the file location where the corresponding Rollback Deployment Archive should be created. A Rollback Archive is used to restore the pre-patch state of the repository when the Patch application result in some problems. 

As shown below, a typical Production environment is first initialized with the released artifacts from a Initial Deployment Archive and then at some later point in time the Patch Deployment Archive is applied for some bug fix or enhancement.


Auditing Deployment Archives

ODI maintains the history of all the Deployment Archives applied to a repository and it can be easily view in ODI Studio.


The Inventory table for the applied patches has a number of columns as shown above providing important information.
  • It provides details about the Deployment Archive- its type, how it was created, who created it and when it was created.
  • It shows in what order a Deployment Archive was applied, by whom and when.
  • It provides the statistics - how many object got added, updated or deleted as part of it.
  • It shows if the Deployment Archive can be rolled back and the path where the corresponding Rollback Deployment Archive was created.

Rolling Back a Patch Deployment Archive

The patches for which a Rollback Deployment Archive was created can be rolled back from studio.