1 / 32

A Practical Approach to Application Integration

A Practical Approach to Application Integration. (aka, the Good, the Bad and the Ugly). February 12, 2013. Agenda. Problem Statement Approaches: Academic vs Reality TGS / Volant offering. Why is this stuff so difficult? and Why can’t I buy one off the shelf?. This is TGS.

niran
Download Presentation

A Practical Approach to Application Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Practical Approach to Application Integration (aka, the Good, the Bad and the Ugly) February 12, 2013

  2. Agenda • Problem Statement • Approaches: Academic vs Reality • TGS / Volant offering Why is this stuff so difficult? and Why can’t I buy one off the shelf?

  3. This is TGS • Leading provider of multi-client seismic data and related geoscientific products to the oil & gas industry • Main offices: Houston and OsloRegional offices: London, Perth, Calgary, Singapore and Rio de Janeiro • Fundamental values • Unmatched Quality and Service • Growth for Stakeholders • Approximately 800 employees • Traded on Oslo Stock Exchange, in OBX Index (25 most liquid shares at the OSE) • Market Cap: ~$3.2 billion • TGS Main Offices Leading and global provider of multi-client seismic data

  4. … and Volant • Founded January 2003 • Focus: Upstream Oil & Gas Integration • Volant Integration Solution • ENVOY Integration Server • Suite of Adapters • EnerConnect Application • Professional Services

  5. What problem are we trying to solve? • Trying to integrate… • Multiple (different) applications • Multiple (different) types of data • Multiple (different) data formats • Multiple (different) languages • Multiple (different) operating environments • Multiple (different) user communities • Multiple (different) customers • … and then things change Big Challenge!

  6. Geoframe GIS Finance Well Drilling Logs Typical Energy Company Browser GeoGraphix Geographix Petrel Paradigm

  7. The Academic Stuff

  8. Terminology Enterprise Service Bus (ESB) Enterprise Application Integration (EAI) Enterprise Information Integration (EII) Mediation Broker Integration Services Extract Transform Load (ETL) Adapter Federation

  9. Definitions • Enterprise Application Integration (EAI): an integration framework composed of a collection of technologies and services which form a middleware to enable integration of systems and applications across the enterprise. • Enterprise Information Integration (EII): ensure that information in multiple systems is kept consistent (aka, Data Integration) • Extract Transform Load (ETL): standard data movement and transformation process primarily targeted at bulk data integration or data warehousing Source: Wikipedia

  10. Integration Patterns • Mediation – EAI system acts as a broker between multiple applications; event-driven model • Federation– EAI system acts as an overarching façade across multiple applications; user-driven model Most Integration solutions leverage both. Source: Wikipedia

  11. Integration Approaches A B • Point-to-Point • Unique connector between applications or systems • Transformations, logic and messaging handled by connector • Fails to scale with additional systems • Broker / Hub • Provides transformation, messaging and routing • Supports asynchronous communication • Loose coupling • Potential single point of failure • Enterprise Service Bus (ESB) • Distribute integration tasks • Minimize single point of failure B Hub A C D E A C E B D

  12. Things to think about • Integration Method • Point-to-Point vs Hub/Broker vs ESB • Transformation Services • Point-to-Point • Half-Link • Canonical Data Model • Adapters / Connectors • Integration Services • Unit conversion, Exception handling • Transaction support • Guaranteed Delivery

  13. The Real Stuff

  14. Recipe for Success • Unfortunately, there really isn’t one… • One size does not fit all • Software + Services • Start small and contained • Do that well • Evolve and expand the solution • Case in point • Large Independent Energy Company • Scope: integrate OpenWorks and PETRA • Then… • Add PPDM and Recall • Add TGS Well Logs • Add INTELLEX, ADM (IRIS21) and GCS/GDS Tops • Add OpenWells (EDM) • Add GeoGraphix

  15. Adapter - Functionality • Exchanges data with the system or application • Use a devkit, if available • Keep ‘em stupid – no business logic • Business Logic belongs in the integration server / modules • Provide sufficient level of control • Attribute-level control • Create vs Update (or both) • Be extremely flexible • Things will change • Be externally manageable • Heartbeat • Configure • Start, Stop, Restart

  16. Integration Server - Functionality • Orchestrates business process • Provides standard services • Cartographic Conversion • Unit Conversion • Messaging • Reporting • Business Logic • Data Transformations • Transaction support • Administration Control • Monitor • Manage Components

  17. Key Questions to Ask • How many applications do I need to integrate?   • Will I need to add additional applications in the future? • How many communication protocols will I need to use? • Need for data routing or data aggregation? • How important is scalability to my organization? • Does my integration situation require asynchronous messaging, publish/subscribe messaging models, or other complex multi-application messaging scenarios?

  18. TGS’ Integration Solution

  19. Volant’s Evolution … • We built Adapters • Assumed that Integration Platforms were in place • Unfortunately, not the case • Implemented Integration Server • Adopted webMethods™ – Integration Server, Broker • Allowed us to focus on • Transformation • Business logic • Reporting • Transactions • We built user interface • Browser-based, Amazon-like application

  20. Today – Volant Integration Solution • Key Components • ENVOY Integration Server • EnerConnect Application (user interface) • Suite of Adapters • Key Features • Integration Platform (data transfer, data sync) • Common Data Access Layer • Software Development Kit • Key Functionality • Business Process • Guaranteed Delivery • Core Services – cartography, units, etc • Job Management – create, start, stop, pause, resume

  21. Geoframe 3rd-Party APP RECALL PIDM PxDM PPDM Petrel INTELLEX RECALL INTELLEX Geoframe Business Logic Paradigm EnerConnect / ENVOY EnerConnect GGX GeoGraphix Geographix Adapter GGX Petrel Paradigm

  22. How it all works

  23. Search for Data

  24. View Search Results

  25. Select and Add Data to Your Cart

  26. Transfer to PETRA

  27. Job Running / Complete

  28. Paradigm PPDM PIDM RECALL PxDM Paradigm Use Case: Transfer Process transfer request query price order

  29. Paradigm Well Data PPDM PIDM SIF LIC Proprietary Logs Log Data RECALL PxDM Paradigm Use Case: Transfer Process job report (email) Well Logs Business Logic Transform

  30. PETRA after Transfer

  31. In Summary • Integration is hard! • Focus on flexibility and extensibility • Hub / Broker and ESB are primary architectures • Start small and expand from there • Professional Services component is key … and, No, ya can’t buy one at Best Buy.

  32. Scott Schneider 832.667.4715 scott.schneider@tgs.com

More Related