Enterprise Architecture: ebXML

1
Enterprise ArchitectureebXML Web services

• Anthony Arana
• Choong-Mok Kwak
• Mohandas Mavilavalappil
• Andrius Miksenas
• Sridhar Varri
• Doug White
• Dr. Sanjay Gosain
• December 9, 2002

2
Agenda

• Background
• Introduction-WS ebXML
• Adopters / Supporters
• Advantages / Limitations
• Evolution
• Government Examples
• Recommendation
• Questions

3
Project objectives

• What is the difference between ebXML and Web
  services?
• What is the projected maturity schedule for each
  of these architectures?
• Which business architecture is better suited to
  government transactions?
• What products are available today or in the near
  future that will allow the government to use
  ebXML and/or Web services?

4
Approach

• Conduct Literature Review
• Interview Experts
• Benchmark studies

5
Evolution of distributed computing
Email
EDI
Microcomputer, OS, Mailboxes
RPCs
CORBA, DCOM
The Web
XML and RELATED
eSpeak, XML-RPC, SOAP 0.9, etc.
SOAP WSDL
Web services
ebXML
1970 1980 1990 1997 1999 2000 2001 2002
6
Web services concept

• Program-to-program communication architecture
• using XML and one or more of the following
• UDDI - registry
• WSDL - template
• SOAP - programmatic interface
• Web Services use a common network
• Internet

7
Web services concept
Service Broker
Publish (UDDI)
Find (WSDL)
Service Requester
Service Provider
Bind (SOAP)
8
ebXML concept

• XML-based open framework for e-business
  transactions. ebXML provides
• Messaging Service
• Registry/Repository
• Business Process
• Core Components
• Trading Partner Profiles

9
Web services products

• Companies exposing their applications
• Application Servers
• Professional services firms

10
Early adopters of Web services

• Very large dynamic corporations with high
  integration requirements
• Verticals banking (JP Morgan), insurance (Blue
  Cross/Blue Shield), travel (Dollar),
  manufacturing (GM, Dell)
• Applications Demand/Supply Chain, Private
  Marketplace, ASP/WSP integrations

11
Web services case DELL
Edge Activity
Suppliers
Customers
Assembly Line
Logistics
Core Logistics Activities
12
ebXML development1 ERCOT adoption for Texas

• ERCOT is an independent, not-for-profit
  organization responsible for overseeing the
  reliable and safe transmission of electricity
  over Texas' main electricity power grid.
• 1 of 10 NERC reliability regions
• Single, integrated control area
• 37,000 miles of transmission
• 70,000 MW of generation capacity
• gt57,000 MW peak demand
• 6.25 million customers (2nd U.S.)
• 9 of U.S. electricity demand
• 75 of land area of Texas

1 Darnell, Dave Utilities Industry XML
Business Case Example, 2002
13
Customer switch Initiation
14
Customer switch Completion
3. Completes switch
15
Web services advantages

• Interoperability
• Ubiquity
• Loosely coupled applications
• Working applications
• Support of software industry leaders

16
Web services limitations

• Security/Privacy
• Routing/Messaging, Reliability
• Transaction handling
• Manageability
• Interoperability
• Performance/Tuning

17
ebXML advantages

• Business processes
• Registry/Repository
• Security

18
ebXML limitations

• Payload
• Slow development

19
Web services maturity

• SOAP / WSDL already mature with successful
  applications
• Another group of specs to provide more complex
  functionalities still evolving
• WS-Security, WS-Coordination
• Public UDDI is still evolving
• roadmap and directions already exist

20
Web services future

• Year 2003 UDDI adoption increases. Private
  registries proliferate to support private
  exchanges. Government use of Web accelerates.
• Year 2004 Business adoption of Web services-based
  models grows further. Private registries still
  dominate. Forty percent of financial service
  transactions leverage Web services model.
  Thirty five percent of government services are
  delivered as Web services.
• Year 2005 Public UDDI registries gain attention
  as public exchanges. Dynamic services gain more
  attention. Web services realize their true
  commercial potential as public UDDIs come into
  existence.

Source Gartner Report, Web Services Software
as Service Comes Alive, Daryl Plummer, October
2001
21
ebXML maturity

• Message Services
• already implemented
• ERCOT (Electrical Reliability Council Of Texas)
• Registry Repository
• work currently in progress

22
Total cost of ownership

• Capital
• Operation
• Development
• IT staff training and consulting by vendor

23
The U.K. experience

• e-Government interoperability framework (e-GIF)
• The factors underlying the e-GIF specifications
• Interoperability
• Market support
• Scalability
• Openness
• Scope
• Government and Citizens - G2C
• Government and Businesses (World wide) - G2B
• Government organizations G2G
• Government and other Governments (UK/EC, UK/US
  etc)

24
The U.K. experience (continued)

• Implementation
• Management Processes
• Technical Policies
• XML and XML schemas for data integration
• UML, RDF and XML for data modeling and
  description language
• XSL for data transformation

25
Australia experience

• Three key service areas identified
• Policy and business framework
• Service infrastructure
• Interoperability standards
• Development of a distributed online interactive
  repository to support framework
• Focus on identifying business processes and
  develop schemas

26
Web services platform architecture
Installation and Administration
Process Modeling
Adapters
ERP
Systems Monitoring Management
Transaction Control
Adapters
CRM
Business Process Collaboration
WorkFlow Engine
Adapters
DB
Process Definition
Web Services Support Protocols
Web Services Management and Runtime Monitoring
Tools
Messaging/TRP Protocols (SOAP, ebXML,
RosettaNet)
XML Processing
MIME S/MIME
Service Development
Security Authentication Services
Transport Level Protocols HTTP/SMTP/FTP, etc.
Deployment
Base Integration Platform
Runtime Environment
SOURCEWebMethods, 2002
27
Recommendations

• Qualify and prioritize processes that would
  derive maximum benefit from application
  integration
• Tap the synergies of Web services and ebXML in
  different areas
• Work with various standards bodies towards
  including use cases for government transactions
• Prepare the groundwork for implementation of Web
  services

28
Questions?
29
Security case Web services

• Safe behind the firewall
• Security issue Tolerable for sensitive
  information
• Baker McKenzie Knowledge Management System
• Deployed by Eloas Consulting
• Store all information related to transactions in
  digital, searchable form for internal users
  external users
• Collaborative system, containing highly valuable
  multinational MA data, enabled by a Web Services
• Security become less of an issue for Web services
  implementation