B2B standardsREGNET
INTEGRATION
EAI B2B
EAI ? A2A ? IAI ? B2B ?
Set of processes and technologies dealing with the structural integration of software applications inside an organization. A2A : Application To Application
Set of processes and technologies dealing with the structural integration of software applications between organizations
B2B : Business to Business
EAI ? A2A ? IAI ? B2B ? Position
EAI / A2A
J2EE
Firewall
End-User
EAI / A2A
J2EE
Firewall
IAI / B2B
EAI
B2B : Industrial Standards
A few organizations help to promote the development of industrial standards based on XML to support open common business processes RosettaNet Biztalk OASIS CEN/ISSS (European Committee for Standardization:
Information Society Standardization System)
Examples of supported business processes: Exchanging information on product catalogs Exchanges between selling and delivering companies
XML vs. EDI
EDI stakeholders have already raised such issues EDI defines vertical message format standards (i.e. one per
business) Example: EDIFACT for billing
Major obstacles to the massive adoption of EDI by companies Cost of solutions (software able to read messages, networks
used to convey messages,…) and rare human skills New industrial standards are widely based on works made
by EDI stakeholders Translation of EDI messages into XML Collaboration processes are taken over and adapted if
necessary
XML does not a substitute to EDI, but provides standardization and flexibility it lacks
Approaches
RosettaNet
ebXML
Web Services : SOAP + WSDL + UDDI
RosettaNet 1/2
Independent body 400+ partners: leaders in the electronic and information
components industry 1,000 million dollars
Creation of: Common data dictionaries Models of the 10 most widespread business processes
(PIPs= Partner Interface Processes) RosettaNet capitalized on existing standards (EDI, Web,
UN, …)
RosettaNet 2/2
RosettaNet is an infrastructure for managing: B2B exchanges using XML Based on formalized UML processes, and Using global XML data dictionaries
Software developers offer solutions along the RosettaNet model webMethods, Vitria, IBM/NetCommerce (WebSphere
commerce Suite),…
ebXML - Electronic Business XML
Mission: “Provide an open XML-based infrastructure to support the
use of electronic commerce between interested parties in an interoperable, secure and coherent fashion.”
Organization: Joint effort by OASIS and UN/CEFACT
Technologies: UML for modeling XML for describing what needs to be exchanged Internet protocols: HTTP, SMTP, FTP, …
ebXML – 3 phases
Implementation phase Creating an electronic commerce application that conforms to
the ebXML standard. Discovery and Collection phase
Finding partners and gathering their profiles Execution phase
This is the phase in which transactions planned in the application get executed.
ebXML – a global view!
Phase 1Phase 1Phase 1Phase 1
Phase 2Phase 2Phase 2Phase 2
Phase 3Phase 3Phase 3Phase 3
UDDI
Universal Description, Discovery and Integration An original project by IBM, Ariba and Microsoft Soon joined by major players in the computer industry
Objective: “Increase interoperability and adoption of (application)
services on the Web” Technologies:
XML to describe services in a reference format SOAP for transport
UDDI – distributed Web services
SOAP: “RPC” in XML!
Transport (ex. HTTP)
Application
Envelope/Header/Body
TCP/IP
Message formatting
Transport (ex. HTTP)
Web Service
Envelope/Header/Body
TCP/IP
Message formatting
Business semantics Business semantics
<Envelope> <Header><transId>1234</transId></Header> <Body> <Add><Add> <a>3</a><a>3</a> <b>4</b><b>4</b> </Add></Add> </Body></Envelope>
<Envelope> <Header><transId>1234</transId></Header> <Body> <Add><Add> <a>3</a><a>3</a> <b>4</b><b>4</b> </Add></Add> </Body></Envelope>
SOAPSOAP
<Envelope> <Header><transId>1234</transId></Header> <Body> <Add<AddResponseResponse>> <<cc>>77</</cc>> </Add</AddResponseResponse>> </Body></Envelope>
<Envelope> <Header><transId>1234</transId></Header> <Body> <Add<AddResponseResponse>> <<cc>>77</</cc>> </Add</AddResponseResponse>> </Body></Envelope>
WSDL - Web Service Description Language
Technically, WSDL services: Build on Internet protocols and on XML, Are used for building modular applications (a component
approach to the Web!) Perform a specific task
Examples: Airline ticket reservations Viewing stock prices Viewing restaurants by category
UDDI + WSDL + SOAP
XML is therefore used on three levels SOAP: to activate Web services WSDL: to describe Web services UDDI: to publish Web services in reference form
This ensures that any Web service will be easy to integrate with others (from the same company or a different one) to create a business process adapted to your needs.
This interoperability will allow companies to dynamically publish, find and link a series of services to create their own added value for the set
XML chain
WebWebServiceService
SOAPSOAP(Simple Object Access Protocol)
XMLXML
INTERNETINTERNETProtocols: HTTP, SMTP, …Protocols: HTTP, SMTP, …
WSDLWSDL(Web Service Description Language)
WWSSDDLL
UDDIUDDI(Universal Description Discovery & Integration)
TOOLS
IBM Web Services Development Environment: http://www.alphaworks.ibm.com/tech/wsde
Component-X: http://www.enterprise-component.com/products/ Only available for windows, price ?
Open ebXML http://openebxml.sourceforge.net/