B2B standards

1
B2B standards

• REGNET

2
INTEGRATION

• EAI
• B2B

3
EAI ? A2A ? IAI ? B2B ?
Enterprise Application Integration

• Set of processes and technologies dealing with
  the structural integration of software
  applications inside an organization. A2A
  Application To Application

InterEnterprise Application Integration

• Set of processes and technologies dealing with
  the structural integration of software
  applications between organizations
• B2B Business to Business

4
EAI ? A2A ? IAI ? B2B ? Position
Firewall
IAI / B2B
Firewall
5
EAI
6
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

7
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
8
Approaches

• RosettaNet
• ebXML
• Web Services SOAP WSDL UDDI

9
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, )

10
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),

11
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,

12
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.

13
ebXML a global view!
Phase 1
Phase 3
Phase 2
14
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

15
UDDI distributed Web services
Server
UDDI server
Publication
Query
Client
Request-activation
16
SOAP RPC in XML!
ltEnvelopegt ltHeadergtlttransIdgt1234lt/transIdgtlt/Heade
rgt ltBodygt ltAddgt ltagt3lt/agt
ltbgt4lt/bgt lt/Addgt lt/Bodygt lt/Envelopegt
Client
ltEnvelopegt ltHeadergtlttransIdgt1234lt/transIdgtlt/Heade
rgt ltBodygt ltAddResponsegt
ltcgt7lt/cgt lt/AddResponsegt
lt/Bodygt lt/Envelopegt
Application
Web Service
Business semantics
Business semantics
SOAP
Envelope/Header/Body
Envelope/Header/Body
Message formatting
Message formatting
Transport (ex. HTTP)
Transport (ex. HTTP)
TCP/IP
TCP/IP
17
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

18
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

19
XML chain
20
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/