identifying web service integration challenges

Identifying Web Service Integration Challenges

Frank GoethalsSAP-Research Chair on

‘Extended Enterprise Infrastructures’ K.U.Leuven – Belgium

frank.goethals@econ.kuleuven.ac.beIRMA Conference May 18, 2003

Intro 10 Challenges Conclusions

2

Introduction

• “A Web service is

Intro 10 Challenges Conclusions

a software system identified by a URI, whose public interfaces and bindings are defined and described using XML. Its definition can be discovered by other software systems. These systems may then interact with the Web service in a manner prescribed by its definition, using XML based messages conveyed by Internet protocols.”

[http://www.w3.org/TR/2002/WD-wsa-reqs-20021114]

• Enterprise Application Integration (EAI) vs. Business to Business Integration (B2Bi)

/7

3

Integration Challenges

1. Describe & DiscoverWSDL, DAML-S; UDDI, WSIL

2. Communicate SOAP

3. TransactionsBTP, WS-transaction

4. CompositionBPEL4WS, BPML, WSCI, WSCL

/7Intro 10 Challenges: 1-4 Conclusions

HTTP, FTP, IIOP

SOAP

WSDL

UDDI

4

UDDI: Universal Description Discovery and Integration

WS ProviderWS ProviderWS Requestor

WS Broker –UDDI business Registry

WS Requestor

WS Broker –UDDI business Registry

1. Register service and company1. Register service and company

2. Get service and company information2. Get service and company information

3. Look up technical details3. Look up technical details

4. WS binding4. WS binding

Intro 10 Challenges: 2 Conclusions /7

5

Integration Challenges

Intro 10 Challenges: 3/4 Conclusions

1

3

5

2

4

6

/7

6

Integration Challenges

5. Customization

6. Reliability

7. Security (WS-security, SAML, WSS)

8. Scalable, manageable, testing and debugging (Gartner’s WSMP, W3C, OASIS)

9. Business Documents (xCBL, UBL)

10.Combine different standards

Intro 10 Challenges: 5-10 Conclusions /7

7

Conclusions

• Problem of semantics

• Still a long way to go…

Intro 10 Challenges Conclusions /7