cloud enterprise integration

Copyright © 2014 NTT DATA Corporation

Oliver Koeth

NTT DATA Deutschland

Cloud Enterprise Integration

How a new generation of interfaces links enterprises with the cloud

www.nttdata.com/de

Cloud Integration for TODAY,

and for TOMORROW,

and a VISION for the day after tomorrow

Cloud Enterprise Integration

Connectivity – Many enterprise protocols (FTP, MQ, CICS) not cloud ready

Volumes – Cloud metering / governance imposes limits on data volumes and processing

Performance – High latency and limited bandwidth encourage bulkified data exchange

Operations and Error Handling – More technology layers add to complexity

Security – Cloud services often accessed through public internet. Security by obfuscation not really an option

CloudEnterpriseIntegra on

Point-to-Point

Start Small Establish direct interfaces with other systems as the

need arises. Challenges need to be repeatedly

solved.

Integration Bus

Enterprise Style Connect cloud to enterprise

bus. Connectivity only required once, but bus team

needs deep cloud know-how.

Bridgehead

Cloud Style Connect via Bridgehead to systems or integration bus. Optimises cloud enterprise

integration.

Extension Platform Core

ExportDB

Service Layer

Ente

rpri

se In

tegr

atio

n

Laye

r

Administration Nat

ive

Forc

e.co

m

Ad

apto

r

Bridgehead – Native cloud adaptor for optimised data exchange

Enterprise Connectivity – Supports all common (and uncommon) enterprise protocols

Service Layer – Allows implementation of on-premise services not available in the cloud (e.g. data quality)

Data Layer (Export DB) – Provides direct SQL access to cloud data, enabling advanced analytics and disaster recovery

Admin Layer – Web UI for operations and error handling, including automated re-processing in case of downtimes

OData

Open industry standard

(SAP, Microsoft, Salesforce,…) for data federation based on

metadata.

The Data Integrator

OData Connector

The OData Connector dynamically exposes tables from Export DB to Salesforce using OData

Extension Platform Core

ExportDB

Service Layer

Ente

rpri

se In

tegr

atio

n

Laye

r

Administration Nat

ive

Forc

e.co

m

Ad

apto

r Li

ghtn

ing

Co

nn

ect

Automatically generated

form Archive DB

OData

Open industry standard

(SAP, Microsoft, Salesforce,…) for data federation based on

metadata.

The Data Integrator

CORS

Open industry standard

for web application federation (beyond

domain boundaries).

The Frontend Integrator

JSON-P

The Workaround Supports same use-cases

as CORS but does not require CORS

implementation in cloud services.

JSPON-P REST Service

JSON-P allows the mesh-up of data across a multiple domains which leads to the notion of federated web apps

Extension Platform Core

ExportDB

Service Layer

Ente

rpri

se In

tegr

atio

n

Laye

r

Administration Nat

ive

Forc

e.co

m

Ad

apto

r

Federated Web App

(in SF)

Service Console

Owner Profile Vehicle Location

Service Integrator Cloud Gateway

OData

Open industry standard

(SAP, Microsoft, Salesforce,…) for data federation based on

metadata.

The Data Integrator

CORS

Open industry standard

for web application federation (beyond

domain boundaries).

The Frontend Integrator

JSON-P

The Workaround Supports same use-cases

as CORS but does not require CORS

implementation in cloud services.

IFTTT

The Automator Connect all kinds of cloud services without writing a

single line of code.

Cloud as Infrastructure Paradigm

Consumerisation of IT Consumerisation of InTegration

Rethinking Security