data service based enterprise integration 06

8/8/2019 Data Service Based Enterprise Integration 06

1/23

1

Comparison of

Traditional Business Process Automationand Data Service Integration Styles


2/23

2

Topics

Discussion of integration service styles within anenterprise when using:

A Common Information Model (CIM)e.g. OAG Canonical Business Language

Standardized business processese.g. OAG Business Process Scenarios

How do traditional Business Process Automation(BPA) style adapters work

Single Purpose Servic es such as: PublishNewPO();

e.g. OAG message adapters and OAGIS WSDL

How do data service style adapters work

Generic Services such as: Publish(PO);

Comparison


3/23

3

OAG Integration Scenario

Definesstandardbusiness

process for usewithin an

enterprise


4/23

4

Traditional Business Process AdaptersApplication is supplier of E, F, and H and consumer of G.

Standardized process requires that E and F be joined in outgoing message

Native AppClasses

A

B

C

D

CIMClasses

E/F

G

H

TraditionalBPA Services

NotifyEF();

SubG();

H not part of any exi sting

standardized business process

Join hardcoded inadapter


5/23

5

Traditional Business Process Adapters

Native data exported/imported usingXML or via legacy API

Transform/join native representationfrom/to CIM message contents

Non Native CIM

Application

BPA Style

Adapter

CIM Based Message Bus

Non Native CIM

Application

BPA Style

Adapter

Publish/Receive only the standardizedmessages in CIM format (XML)


6/23

6

Alternatively, one could just use adaptersto put native data on the bus i n XML and

do all transformation/joining in a morecentralized Business Process Automati on(BPA) orchestrati on environment.

However this architecture precludes the

supply of off-the-shelf CIM adapters byvendors.



7/23

7

Alternate Architecture

Native data exported/imported using XML or vialegacy API for standardized transactions

Transform message contentsfrom/to native representation

into CIM Objects

Non Native CIM

Application

BPA Style

Adapter

Native/CIM Based Integration Bus

Publish/Receive standard messages in native format (XML)

Non Native CIM

Application

BPA Style

Adapter

BPA OrchestrationEnvironment

Only converts to JMS or WS,but not data conversion

Join E andF centrally


8/23

8

Standardized Business Process is encoded in theAdapter

Changing the business process requires that the datatransformation/join code in the adapter change.

BPA orchestration envi ronment not fully enabledbecause adapters don t support a query with whereclause . You are conf ined to the messages encoded f orthe standardized transactions

Example: A new Purchase Order BPA orchestration script

defines a special process for when the value of the PO is greaterthan 10. For example, if the value is greater than 10, then findout which salesperson made the sale. If the sales person sname is not in the original standardized process, how does theBPA script get it? An orchestration script can t query for thename using a where clause unless the business process (thatspecific query) is hard-coded in the traditional BPA adapter.



9/23

9

Traditional Business Process Automati on

adapters for use wi thin an enterprise arelimited to a predefined set of transacti onsWhile standard business processes may be requiredfor inter-enterprise messaging, they are overl yrestrictive when discussing processes within an

enterpriseStandardized Business Processes are typicall y notused exactly as is

Can t support other types of integration

Traditional Business

Process Adapters


10/23

10

Enterprise Integration

There are several major categories of Intra-Enterprise Integration including:

Business Process Automation (BPA): T wo or more

applications exchange messages for operationalneeds.

Data warehousing (ETL): Data is periodicallyextracted and transf ormed from a variety of datasources and loaded into a speci fic database for

analysis.Enterprise Information Integration (EII): Combiningdata on an ad hoc basis f or analysis.


11/23

11

Comparison of Requirements

for BPA, ETL, and EII Use Case

The data exchanged within an

enterprise for the ETL and EII usecases is more open ended.

Difficult to predefine a limited set of

transactions that satisfy BPA andETL/EII


12/23

12

Enterprise Integration Services

Design Principles

One should try to internalize applicationbusiness logic in a vendor s product

The vendor products know best how to handle datamanipulation at an application level.

One should try to externalize business processlogic from a vendor s product

Business Process Automation orchestration shouldbe done centrally: Custom orchestration enabl ed forevery enterprise.

This allows an off -the-shelf adapter to be used evenwhen business processes vary.


13/23

13

Going Beyond Fixed BPA Style Adapters

Need a way to adapt to changing businessprocesses

Need a way to support all integration use cases

Need a way for vendors to supply CIM applicationadapters off the shelf

Data Service based adapters fulfill theserequirements. A Data Service includes:

Unified Address Space with unif ied way of identifying

informationGeneric query with a where clause

Generic update request (di fferent from a database write)

Generic event noti fication with rich content f iltering


14/23

14

Where do Data Services Fit In

Analysis toolsAnd Libraries

ApplicationDevelopment

Service Layer

Generic Data Access Read/Write/Query

and Event Notification Services

Databasesand ContentRepositories

Data

ServiceLayer

Business

Service Layer

ProcessScheduler

WorkflowEngine

Legacy

Applications and

Data Layer

Applications

Create POProcessing

Report

Process

PurchaseOrder

Platform

Services

SingleSign-on

TimeSync

Service

Registry

MessagingSystem


15/23

15

The Benefit of Separating BusinessLogic from Application Adapters

Analysis toolsAnd Libraries

Application

Development

Service Layer

Generic Data Access Read/Write/Query

and Event Notification Services

Databasesand ContentRepositories

Data

ServiceLayer

Business

Service

Layer

ProcessScheduler

WorkflowEngine

Legacy

Applications and

Data Layer

Applications

Create POProcessing

Report

ProcessPurchase

Order

Platform

Services

SingleSign-on

Time

Sync

ServiceRegistry

MessagingSystem

Separating BusinessServices from Data

Services enablesbusiness logic tochange without

changing applicationadapters and

therefore enhances

the ability to createoff-the-shelf adapters


16/23

16

Data Service Style Adapters use business process neutralservices at the adapter

All data that the vendor wants to expose as CIM data is available.This can be supplied off the shelf by the vendor if standardQuery/Read/Write/Event Notification Data Services are defined.

Data Services should:

Include unified way to indentify information (unified address spacethat includes type and instance information).

Include generic query/update interface, but does not assume thecapabilities of a relational database

For example, No DB write capability, just an update reques t assupported in a version control system so that application businesslogic remains in the application

Include generic event notification that leverages standard messagepayloads and the ability for a server to expose what message typesand object instances it supplies data for.

Object instances exposed in a browseable address space which isused by clients to create a content filter via point and click.

Type info and content fi ltering used during subscription and query

Data Service Based Adapters


17/23

17

Native AppClasses

A

B

C

D

CIMClasses

E

FG

H

Data Sevice QueryAnd Update Servi ces

Query(Classes, Filter, join);Notify(Data);

Subscribe(Data,Filter);Update(Data);

H not part of any exi sting

WG 14 business process

Data Service Style AdapterApp is supplier of E, F, and H and consumer of G

E/F


18/23

18

Data Service Adapter

All public native data exposed usingXML or via legacy API

Transform all relevant public native datafrom/to legacy representation into CIM Objects

Legacy

Application

Data Service

Adapter

CIM Integration Bus

Servers expose all relevant pubic

data as a CIM address space

Legacy

Application

Data Service

Adapter

All business processingdone in the BPA

Orchestration Environment

and not in the Adapter

BPA OrchestrationEnvironment

BPA OrchestrationEnvironment has access to

all public CIM data


19/23

19

Business Process is NOT encoded in the Adapter but isentirely contained in the central BPA orchestration scripts

Use standardized message payloads to define a base set ofmessages that are supported by an application off the shelf but the

standard messages are not the l imit of what an application exposesAll business process logic developed and executed in a centralizedBPA orchestration environment

Vendor supplied off-the-shelf adapters expose all native data that ismapped to the CIM.

Not all data is used when adapter is deployed because not all dataneeded by current business processes. However, data need notpersisted in CIM format so overhead of having the ability to transformall data is negligible

Complementary with the use of tools such as Tibco fortransformation of data and as BPA Orchestration Environment

Data Service Style Integration Leverages and

Extends Work Done B y Groups Such As The OAG


20/23

20

Actual Script:App1 pub EF

then App 2 pubG then App1

Pub H

OriginalStandardized ScriptApp1 pub EF then

App 2 pub G

Example Traditional BPA Integration

Application 1Supplier of E, F, and H

and consumer of G

Application 1Supplier of G and

consumer of E, F, and H

Native API and

Data transformation

BPA Orchestration Environment

No

tifyEF()

;

Su

bG()

Native API and

Data transformation

Su

bEF()

;

No

tifyG()


21/23

21

Example Data Service Integration

Application 1Supplier of E, F, and H

and consumer of G

Native API and

Data transformation

BPA Orchestration Environment

No

tify(EF);

Su

b(G)

Query

(H)

Native API and

Data transformation

Su

b(EF);

No

tify(G)

Up

da

te(H)

Actual Script:App1 pub EF

then App 2 pubG then App1

Pub H

Application 1Supplier of G and

consumer of E, F, and H

Not in the original standardbusiness process, but can becompensated for in BPA script

Originalstandardized ScriptApp1 pub EF then

App 2 pub G


22/23

22

Data Service Adapters

Address ETL and EII use cases by providing:

Rich BPA orchestration environment as adapters

support query with where clause .Data service should not presume the capabilitiesof a relational database since many legacy API sdon t have this capability.

One down side is that adapters are more complex

to build. However, this needs to be done lessfrequently since a reusable reusable adapter canbe supplied off the shelf by the vendor or a thi rdparty.


23/23

23

The Bottom Line

Today, because of the lack of interoperableproducts, enterprise integration is custom workdone by system integrators.

This integration work comprises a large portionof money allocated to the use of applications.

The use of OPC UA Data Services goes a longway towards shrinking the integration gap and

thereby allows vendors to better meet theneeds of users.

data service based enterprise integration 06

Documents