Closed-Loop Ordermanagement

(1)

Markus Grünewald,

Solution Architect

Torsten Winterberg,

Business Development & Innovation

OPITZ CONSULTING Deutschland GmbH

Integration Architecture for Salesforce and SAP

Frankfurt, May 2015

(2)

(3)

About me…

[email protected]

Position@OPITZ CONSULTING:

Business Development & Innovation

Competence Unit SOA/BPM & Software Dev.

Community:

Speaker: Jax, W-Jax, OOP, DOAG, OOW,

SOA Symposium, …

Author of several SOA/BPM related articles and

books

SOA/BPM @ DOAG Dev. Community

Oracle ACE Director

Oracle Expert Alliance

Enterprise BPM Alliance

Background:

(4)

About me…

[email protected]

Position@OPITZ CONSULTING:

Solution Architect

Competence Unit SOA/BPM

Community:

Speaker: DOAG

Trainer: Oracle University CEL

Author of several SOA/BPM related articles

Oracle Expert Alliance

Enterprise BPM Alliance

Background:

Siebel, EAI, Java EE, BPM, SOA

(5)

Agenda

1. Integration Today – The Cloud is approaching…

2. The Usecase: Closed-Loop Order Management

(6)

(7)

(8)

(9)

(10)

Google Glasses

© http://www.flickr.com/photos/azugaldia/7457645618

(11)

Google Glasses

© http://www.flickr.com/photos/azugaldia/7457645618

(12)

© http://www.flickr.com/photos/azugaldia/7457645618

Some strong business drivers…

Remote maintenance

Predictive maintenance

(13)

*Source: Computerworld Strategic Marketing Services, February-March 2014 Cloud Survey **Source: GigaOM Research and VC North Bridge

Cloud is

Mainstream

• Using Cloud

today

or will be in

Two Years

84 %

Top Cloud

Benefits

• Greater Agility

• Lower Cost

• Better Resource

Utilization

>80

%

PaaS

Growing Rapidly

• Will adopt

PaaS within

Five Years

~90

%

(14)

Classic integration was already complex

(15)

The new reality:

Cloud introduces a new dimension of complexity

Not All IT Is

in Your Control

Tooling is

Inconsistent

Security

On-premises

Integration

Challenges

Remain

Cloud Integration

(16)

Center of gravity

Hybrid

The concept of federated on-premises and cloud-based integration combined with the

improved interoperability of existing and new middleware silos of application,

business-to-business (B2B), business-to-business process management (BPM), business-to-business events, business-to-business rules, and

data integration. Key capabilities of hybrid integration platforms include metadata

life-cycle management and runtime interoperability, which help CIOs orchestrate a well-governed

but also rapidly changing agile integration platform from multiple integration products.

(17)

Reference architecture (High-Level)

MES

…

MES

Firewall

Cloud

Apps

Location

Production

Company

Business

Partner

Outside

VPN

Private Cloud On-Site Dedicated Public Cloud

Public Cloud

Cloud

Apps

Hosted Apps.

(18)

Dedicated PaaS

(Hosted & managed)

Categorization of integration / iPaas solutions

iPaaS

PaaS

IaaS

On-premise

Depth of vertical integration

(diminishing CAPEX)

Oracle SOA Suite

Talend Application Int.

Managed

Services

Oracle SOA Cloud

Service

Amazon

Oracle Java Cloud

A

ll

O

P

E

X

t

h

re

sh

o

ld

Oracle ICS

DELL Boomi

Talend Integration Cloud (TIC)

(19)

Anything that changed? (1)

CAPEX 2 OPEX works only in cloud, not on-premise

Wait! Managed Service possible.

(20)

Anything that changed? (2)

Customization

If integration target is SaaS system:

normally not the preferred way to customize in the SaaS.

Do your things outside in a middleware

E.g. triggering of processes: Not from Salesforce, but from process which calls into

Salesforce.

Only do configurable things in the SaaS system

If integration target is on-premise:

Typically both possible

Adapter discussion

(21)

Anything that changed? (3)

Classic IDE vs Pure Web

IPaaS typically developed via Browser (self service idea)

On-premise and CBI platforms allow usage of classic integration tooling

(IDEs)

(22)

Anything that changed? (4)

Scalability

On-premise:

Buy hardware and licences as needed. Not easy to scale

down.

Host your infrastructure elsewhere (no real cloud)

If dedicated: only classic scalability. Very limited if new

licenses have to be bought. Peak Load via Hybrid cloud

solution.

If multi-tenant: can use scale effects to some extend

CBI: use advantage of cloud and add/remove

resources like needed

(23)

Anything that changed? (5)

Security

On-premise 2 on-premise:

Same network, VPN tunnels, etc.

Cloud 2 ERP on-premise:

Use HTTPS, certificates, etc.

Distributed adapters?

ERP on-premise to Cloud

Cloud 2 Cloud

Compliance related to data

Current regulatory requirements

of the relevant industry?

(24)

Anything that changed? (6)

Location of data centers

Flow of integration data, data can be masked

On-premise, self-hosting: data stays inside your environment

On-premise, outsourced: data stays somewhere (contract possible)

Cloud: data can be everywhere (contract possible)

Managed Service (e.g. by OC): data stays in Germany

Location of integration data*

Integration platform needs to store runtime data (dehydration store), if

stateful

Normally, data masking is not the option, because of error handling and

monitoring

If only one dehydration datastore exists, NSA e.g. can get access to your full

data

(25)

But what about the processes???

Process based integration flows

Issues of point-to-point

• Monitoring of business objects

• Tracking & Tracing

• Loose coupling for flexibility

• Managebility

Example:

Telekom DSL pre order process

Webshop

ERP

Laundry

Shipping

--- ---

(26)

(27)

Management Summary

The Opitz/Oracle team was invited by Marketing & Sales to

do a PoC with the Oracle Integration platform running in the

Cloud

Customer is experiencing issues with their historically

grown integration platforms, e.g. system complexity,

missing functionality like end-to-end monitoring

Currently too complex: passing up to four different integration solutions

Project goal is to use only one global integration platform to become more

efficient

Proof-of-concept run in December 2014 at customer side.

Result: Two Use Cases realized successfully in 4 days as

planned.

(28)

Driving forces from Business and IT

IT-Goals:

Consolidation of up to 6 different integration platform solutions down to max.

1-2

Currently: SAP, IBM, Sonic, Informatica, Oracle, and some more

Business Pain

lost messages, double messages, send messages via up to 4 (!) integration

platforms

Cost pressure (Maintenance cost too high)

Integration platform in the Cloud, e.g. for SAP and Salesforce/Veeva

Business line Marketing&Sales Goals:

Effective Marketing by near realtime integration of Salesforce CRM and

SAP.

Closed-Loop Ordermanagement

Cloud CRM-Solution by Salesforce/Veeva with SAP on-premise via (hybrid)

integration platform

(29)

The Oracle Integration Solution

Mainframes

Databases

Files

Mobile

Cloud

Applications

Business Process Orchestration

Analytics & Events

Service

Orchestration

Business

Rules

Virtualization, Transformation,

Routing

C

o

n

e

c

t

D

is

c

o

v

e

r

API Management

C

o

n

e

c

t

D

is

c

o

v

e

r

Things

Trading Partners

(30)

Private Cloud

Integration

Public Cloud

Integration

Same

Architecture

Same

Standards

Same

Underlying

Components

Deploy Anywhere

Single technology for On-Premises and Cloud

Red rid of:

• Installation

• Configuration

• Patch-set

Updates

• Map from

scratch

• Hardware

incompatibility

• Hand-coded

integration

(31)

(32)

(33)

(34)

(35)

(36)

Reference Architecture

Salesforce Adapter SAP Adapter Adapter TBN JMS WebServices K o m m . L a y e r L a n d s c a p e

App-1 App-2 App-3 App-n

B a s ic S e rv ic e s _{SAP???Service}

Cannonical Data Model

Salesforce???Service App1???Service SAP???Service SAPOrderService Salesforce???Service Salesforce???Service App1???Service App1???Service P ro c e s s / O rc h e s tr a ti o n L a y e

r SalesforceToSapProcess SapToSalesforceProcess SystemXToSystemYProcess

Database

(incl. MDS)

XREF

DVM

Instancemonitoring

Dehydration

M

o

n

it

o

ri

n

g

/

E

rr

o

rh

a

n

d

li

n

g

M

o

n

it

o

ri

n

g

/

E

rr

o

rh

a

n

d

li

n

g

(37)

(38)

(39)

Closed-Loop Order Management –

Talend Integration Cloud (TIC)

Veeva Systems

Talend Integration Cloud

Customer

Order Object

Order Status Object

Salesforce

Adapter

Integration Cloud

Webservice

Veeva Entities:

Order_vod__c

Orderlines_vod__c

Transformation

Routing

Process Control

Tracking and

Tracing via

Web-UI

XML Data

Transfor-mation

SAP Adapter

XREF

Data

REST Client

(40)

Conclusion

More and more integration targets will be cloud systems

On-premise applications are the new legacy

Cloud-based integration (CBI) has to be taken in concern

Outlook: Microservices are good cloud citizens

Define your Integration Center of Gravity

There are some differences between CBI and on-premise

But not much spectacular. Look behind the marketing layers

iPaaS Self-Service is still deep marketing level

May become disruptive technology

Typically, hybrid solutions will be chosen

Make sure deployment on-premise and cloud is possible

CAPEX->OPEX is one of the biggest drivers

(41)

More information

OC Website: Systemintegration

http://www.opitz-consulting.com/leistungsangebot/business_loesungen/systemintegration.php

Whitepaper series:

(42)

Questions?

(43)

Contact:

Torsten Winterberg

Business Development & Innovation

Competence Center SOA/BPM

OPITZ CONSULTING Deutschland GmbH

Kirchstr. 6, 51647 Gummersbach, Germany

Phone:

+49 173 54 79 302

Mail:

[email protected]

Twitter:

@t_winterberg

Blog:

http://torstenwinterberg.blogspot.de/

Blog:

http://thecattlecrew.wordpress.com

Markus Grünewald

Solution Architect

Competence Center SOA/BPM

OPITZ CONSULTING Deutschland GmbH

Kirchstr. 6, 51647 Gummersbach, Germany

Phone:

+49 173 72 79 409

Mail

:

[email protected]