Ed Iweb Service Presentation

8/6/2019 Ed Iweb Service Presentation

1/31

How EDI fits into a Web Services worldPresented by Krishna Prasad

GM (Technology), HCL EAIServices (Formerly

Aalayance )


2/31

Agenda

Business Integration Technology

EDI

Competing technologies

Emerging Web Services technologies that

coexist with EDI

Conclusion


3/31

Business IntegrationTechnology


4/31

Definition:

BI = Business to business communication

(B2B) + Enterprise application integration

(EAI).

Example:

In a typical supply chain, plant and supplier

need to collaborate and ERP system of eachpartner has to be updated with this

collaborations.

Business Integration (BI) Technology


5/31

Necessary (but not sufficient) conditions

for success ofBI technology:

P

artner acceptance of theBu

sinessIntegration standard

Vendor consensus on implementing

standards

Simplicity

Business Integration (BI) Technology


6/31

Electronic Data Interchange(EDI)


7/31

Used forBusiness to Business communication

Dominant in supply chain management

Established Standards in EDI:

ANSI X12 (USA) EDIFact (Europe)

HIPAA (Healthcare)

Document standards at least 250+

E.g., PO (850), ASN (856)

Transport standards

E.g., VAN, AS2

Trading partner agreement framework

Electronic Data Interchange (EDI)


8/31

Example implementation EDI in

Publication Industry

Retail Shop

CommunityLibraries

Schools/Colleges

EnterpriseSystemFTP/

HTTP

GISProcessmodeler

Gentran 6.xFor Mapping

GentranIntegration

toEnterprise

System


9/31

Worldwide EDI market revenue


10/31

EDI is

Arcane: Age old Cobol-like data structures

Costly: Used to require Value added Network (VAN)

High development and support costs

Error-prone: Needs manual data collection

and data entry

Whats wrong with EDI?


11/31

Locked up investment in EDI

Backing by big guys:

WalMart, Novartis and Addison Wesley

Big guys drive partners to adopt it as well

Support from powerful vendors:

GE, Sterling Commerce

Critical mass ofusage resulting in Return

on Investment (ROI) for the big guys.

Why EDI will stay anyway?


12/31

AS2 (EDI over HTTP) reduced cost by

eliminating VAN. Walmart drove adoption

of AS2.

No real solution is in sight given the widevariations in processes, vocabularies and

practices around the world.

Why EDI will stay anyway?


13/31

Competing Technologies- RosettaNet- ebXML


14/31

RosettaNet standard is widely accepted in

electronics industry by leaders like Intel, Dell,

National Semiconductors.

Standardizes business processes in the form ofPIPs and RNIF.

They were the first to standardize on XML as a

standard payload.

RosettaNet is backed by vendors like Adobe,Inovis, National Semiconductors and Dell.

Will continue as a niche player

RosettaNet


15/31

Typical RosettaNet implementation

Source: WebLlogic


16/31

ebXML can be broken down into mod

ules like, ebMS (Messaging services)

ebBPSS (Business process Definitions)

ebCPPA (Collaborative protocol for Partner Agreement)

ebXML is trying to solve too many challenges. It is a complex

set of standards. We havent come across any real implementation of ebXML

ebMS diverges from Web Services standards

ebBPSS is in competition with BPEL that has much better

momentum. In terms of vendor backing, it is only backed by standard

committee like Oasis. It is not backed by any big vendors(IBM/Oracle/SAP).

ebXML is not where the money is

ebXML


17/31

Emerging Web Services technologies

(that coexist with EDI)


18/31

Radio Frequency Identifier (RFID) and ElectronicProduct Code Information System (EPCIS)standards emerging around Web Services forproduct tracking in the supply chain space.

Business Process Execution Language (BPEL) forprocess execution

Enterprise Service Architecture (ESA) for hookingup SAP into BPELs process execution

Frameworks like Web Services InvocationFramework (WSIF)

Emerging Web Services technologies


19/31

EPCGlobalInc.org: Consortium evolving a

EPCGlobal Network standard.

What is EPCGlobal Network?

A global network (web) of information about productitems

Consists of:

Electronic Product code (EPC)

EPC Middleware (ALE)

Discovery Services

EPCIS

RFID Revolution: ALE and EPCIS


20/31

RFID Technology building blocks

Source: Cambridge Auto-ID Labs

Web

Services

protocol

Web

Services

protocol


21/31

EDI Pushes data. This means: We cant get data on-demand. E.g., Balance on

Hand (BoH) cannot be dynamically obtained.

We cant pull missing data. E.g., Missing Item masterrecord cannot be pulled.

EPCIS complements EDI to provide pull capabilities.

RFID reduces errors by replacing manual datacollection and data entry.

EPCIS communicates with each otherusing costeffective Web Services standards

RFID/EPCIS - Impact on EDI


22/31

se case - ssoc a ng an unexpec e

shipment to a purchase order.

The retailers EPCISquerys the EPCglobal

Discovery Services tolocate the

manufacturers EPCIS.

Orphan Item came in

shipment to retailer

The ONS sends the

retailers EPCIS thelocation of themanufactures EPCIS.

Manufacturer

authenticates therequester

Stop

Manufacturer gets theSerial number and

identifies which PO theitem belongs to

Sends PO informationto requestors EPCISsystem. Which locatesthe PO and fulfils it.

Stop

No

Yes


23/31

Use case - On-demand inventory count with help from EPCISstores of retailers and warehouses

EPCIS query on EPCglobalNetwork for inventory levels inretailer DCs and stores. TheWeb appl. shows list ofparticipating retailers,Walmart, Sams Club, etc.User selects Walmart

Manufacturerrequest a BoH thrua web screen

Software usesEPCglobalNetwork to findWal*MartStores EPCIS andretrieve BoH forselected product


24/31

BPEL

EDI vendors did not use a well designed custombusiness process modeling tools.

BPEL brings the benefits of standardization. Rich process model including parallel execution (flow), event

handling and alarms

Compensatory mechanisms for handling failures in long runningtransactions

Have WSDL? BPEL can use it. Web Services of course! Legacyapps connected by WSIF via JCA/JDBC.

What it doesnt do,

No user interaction. Semi automated process cannot bemodeled.

No in-built support for transformation


25/31

rc ec ure: yp ca ne eques ,

One of Two Possible Responses

Source: Oracle

Request could be to order a product online, and the First

response could be either an in stock message, or an out of stock

message.


26/31

ESA

SAPs initiative to standardize how enterprise applications provideWeb Services interfaces.

An Enterprise Service is a Web Services whose interfaces fit into a

pattern with Create, Retrieve, Update, Delete, Query and Action

operations named and defined according to a convention.

Tools can take advantage of the conventions to discover and

integrate compliant enterprise services.

All SAP products to provide ESA compliant Web Services

interfaces by2007

Microsoft, IBM, Cisco, EMC, Intel and Macromedia have licensed

ESA from SAP.


27/31

What is WSIF, how it rescues BPEL?

Framework from Apache that lets you access back-endsystems, while providing a WSDL interface to BPEL.

Use case:

A prescription drug supplier had existing HTTP GET interfaces in

front of mainframe batch processes. A custom WSIF binding to support HTTP GET requests was built.

The WSDL interface to this HTTP "Web Services" means thatstandard BPEL processes can interact with the mainframeapplications without requiring support for a new interface.


28/31

Conclusion


29/31

Conclusion

EDI will continue as the backbone ofBI.

RosettaNet will be a niche player.

ebXML isnt succeeding in the market place.

All new developments will revolve around Web Services.

EPCIS complements static/push/batch EDI with dynamic

capabilities and reduces errors.

BPEL standardizes business process execution.

ESA standardizes Web Services interfaces to legacy applications.

Frameworks like WSIF is emerging to integrate BPEL with legacy

systems.


30/31

[email protected]


31/31

Ed Iweb Service Presentation

Documents

Transcript of Ed Iweb Service Presentation