TAGS

Recent Posts

Archives

Groovy-ETL: Building Better Oracle PBCS & OAC Integrations Using REST API Webinar Preview
Posted on March 19, 2019
Author: Andy Tauro, Performance Architects

This blog post provides a preview of the content the Performance Architects team will discuss during a free, live webinar on Tuesday, March 26, 2019 at 12:30 PM EST entitled “Groovy-ETL: Building Better Oracle PBCS & OAC Integrations Using REST API.” Register here to attend the webinar!

Integrating systems that do not natively communicate with each other is the single biggest technical challenge in deploying a solution that uses more than one tool set. Oracle Planning and Budgeting Cloud Service (PBCS) and Oracle Analytics Cloud (OAC) are two industry darlings that each provide complete solutions on their own. However, when a solution calls for using both of these products, integrating them together is not for the faint of heart.

One could go for another purpose-built tool, like an off-the-shelf integration toolset, to build a custom solution…but sometimes integrating the integration toolset creates even more effort!  This is especially true if the solution includes Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS) or Infrastructure-as-a-Service (IaaS) cloud capabilities, because then one needs to deploy software subsets or agents on staging hardware to connect to on-premises systems, adding to cost and complexity. Take a moment to guess where this will end…

While PBCS and OAC expose a programming interface like REST API, it is simpler to connect to relational sources with technology like Java Database Connectivity (JDBC). Then again, sometimes data needs to be sourced from or written to data files. So how does one put all these technologies together?

How about looking at a solution that is based on open-source software and that can be deployed on existing hardware behind corporate firewalls to reach out to the cloud solutions of the world? Groovy-ETL functionality offers this type of approach.

Based on the Groovy scripting language, which can use REST API to communicate with PBCS and OAC, Groovy-ETL uses JDBC to communicate with relational databases like Oracle RDBMS or MS SQL Server. It also uses native interfaces to read or write to files. Groovy-ETL standardizes these communication interfaces so that they can be reused across multiple environments to meet different business needs, while at the same time providing the means to extend the solution capabilities with additional functions. The best part is that it can run on Windows and Linux without modifications, so the functionality delivered by a packaged solution can run the same way regardless of the operating system it is deployed on.

One person’s “perfect” solution may not be the same as another’s. The goal of a methodology like Groovy-ETL is to provide a single solution for integration needs. Such a solution is based on open-source technologies and is extensible to incorporate connections to anything that has a “query friendly” interface, like REST API or JDBC. While it takes some programming knowledge to add functionality, it requires almost none to use existing functions.

If you want to find out more or have questions, please sign up and attend our upcoming webinar that covers this topic in a bit more detail.  If you have other questions that aren’t addressed in this blog post or the webinar content, please don’t hesitate to contact us at communications@performancearchitects.com or to leave a note below and we’ll be in touch to address your interests.

Share
© Performance Architects, Inc. and Performance Architects Blog, 2006 - present. Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Performance Architects, Inc. and Performance Architects Blog with appropriate and specific direction to the original content.

Leave a Reply

Your email address will not be published. Required fields are marked *