Tuesday Apr 05, 2016

How to load data from Excel using ODI 12.2.1 and Progress DataDirect SequeLink

Author: Octavio Oliveira

Background

There is often a need to read data from Excel spreadsheets and integrate it with different target technologies in Data Integration projects. The challenge is that MS Excel only supports ODBC connectivity whereas Oracle Data Integrator (ODI) and many other tools only support JDBC connectivity natively. This is where the Sun JDBC-ODBC Bridge packaged with Sun Java Development Kit (JDK) proved very useful to make the bridge between ODBC and JDBCS. However, starting with JDK 1.8 (required for ODI 12.2.1) the Sun JDBC-ODBC Bridge has been deprecated.

Luckily there are many third-party JDBC-ODBC bridges out there that can be used with ODI. In this blog post we will be using a solution provided by Progress DataDirect named SequeLink (https://www.progress.com/connectors/sequelink).

[Read More]

Monday Mar 28, 2016

Leveraging Oracle Data Integrator (ODI) with the Amazon Elastic MapReduce (EMR) Cloud Service

Another interesting article from our A-Team – read on!

Benjamin Perez-Goytia recently published Using Oracle Data Integrator (ODI) with Amazon Elastic MapReduce (EMR). He provides details on how to use Oracle Data Integrator (ODI) with the Amazon Elastic MapReduce (EMR) cloud service.  Amazon EMR is a big data cloud service and a member of the Amazon Web Services (AWS) cloud computing services, offered by Amazon.com.

Thanks Benjamin!

Thursday Feb 18, 2016

Topology Configurations for Web Services in Oracle Data Integrator (ODI) 12.2.1

There are a couple of enhancements added in outbound Web Services invocation support in Oracle Data Integrator (ODI) 12.2.1. You can now configure the Web Service end point URLs in the Topology definition instead of hard coding it in the ODI Tools parameters. Logical Schema of such topology configuration can be then used directly in the OdiInvokeWebService tool parameters. Now ODI also allows you to invoke a WebService that is protected by OWSM policies and register those OWSM policies as part of Physical Schema definition.

To register the Web Services definition a new technology, “SOAP Web Service”, is added in the Topology where you create the Data Server for the Web Service and register its WSDL URL.

The Services, Ports, user credentials, OWSM policies for the endpoint service from the WSDL are configured as the Physical Schemas.

You can then create a Logical schema for it and bind it with Physical Schema through Context mapping. Such logical schema and context can be specified in the OdiInvokeWebService tool instead of hard coding Web Service URL and other parameters.

To learn more about the Topology Configurations for Web Services, there is an Oracle by Example tutorial available providing step by step instructions on using the feature: http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_newfeatures/ascii_files.html#section3s1

Additionally the new features introduced in Oracle Data Integrator 12.2.1 are also documented in our New Features white paper.

Tuesday Feb 16, 2016

More Tips on Oracle Data Integrator (ODI) for the Cloud from the A-Team

Check out this week’s post from Cecile Franchini of the A-Team, the title says it all: Tips for ODI in the Cloud: ODI On-Premise with DBCS.

If you are considering connecting to the Cloud and using Oracle DBCS – Oracle Database Cloud Service – ODI on-premise can help get the job done.

Friday Feb 12, 2016

Complex File Wizard is now available in ODI Studio 12.2.1

In the new Oracle Data Integrator 12.2.1 release the Native Format Builder wizard which is used by the Complex File technology is available directly within ODI Studio. Previously users had to use JDeveloper with the SOA Extensions to access it. The Native Format Builder wizard is used to parse a complex file structure and build a Native Schema (nXSD) description out of it, Oracle Data Integrator then uses this nXSD to reverse-engineer, read and write information from complex files.

You can find more information about the Native Format Builder and the Complex File technology in our documentation: http://docs.oracle.com/middleware/1221/odi/develop-connectivity-km/complex_files.htm#ODIKM1397

In addition you can find an Oracle By Example tutorial which will walk you through how to use this feature: https://apexapps.oracle.com/pls/apex/f?p=44785:24:103532390093139:::24:P24_CONTENT_ID,P24_PROD_SECTION_GRP_ID,P24_PREV_PAGE:12572,,24

Finally all the new features introduced in Oracle Data Integrator 12.2.1 are documented in our New Features white paper.


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.

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.