Enterprise Architecture ebXML Web services - PowerPoint - PowerPoint by vev19514


									Enterprise Architecture:
ebXML & Web services

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

       Background
       Introduction-WS & ebXML
       Adopters / Supporters
       Advantages / Limitations
       Evolution
       Government Examples
       Recommendation
       Questions
    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?

     Conduct Literature Review

     Interview Experts

     Benchmark studies
        Evolution of distributed
       OS, Mailboxes
                           CORBA, DCOM
                           The Web
                                   XML and RELATED
                                            eSpeak, XML-RPC, SOAP 0.9, etc.
                                                       SOAP & WSDL
                                                       Web services

1970     1980       1990      1997   1999   2000     2001      2002
       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
Web services concept
                     Service Broker

           Publish                     Find
           (UDDI)                     (WSDL)

Service                                        Service
Provider                                       Requester
                        Bind (SOAP)
      ebXML concept
   XML-based open framework for e-business
    transactions. ebXML provides:
      Messaging Service

      Registry/Repository

      Business Process

      Core Components

      Trading Partner Profiles
       Web services products

   Companies exposing their applications

   Application Servers

   Professional services firms
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
           Web services case: DELL
                              Edge Activity

  Customers                                   Suppliers


Core & Logistics Activities
             ebXML development:1
              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

                >57,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
           Customer switch “Initiation”

                                                     2. Retailer sends
       1. Customer                                   switch request &
        signs with                                       ERCOT
         Retailer                                     acknowledges

                       3. ERCOT sends switch
                       notification to customer

                      4. Customer can cancel the
                     switch within 3 business days
      Customer switch “Completion”

                                                      4. ERCOT forwards
Utility                                                final meter read to

                        2. Utility sends meter data

     1. Utility reads          Customer                  3. Completes switch
    Web services advantages

   Interoperability
   Ubiquity
   Loosely coupled applications
   Working applications
   Support of software industry leaders
      Web services limitations

   Security/Privacy
   Routing/Messaging, Reliability
   Transaction handling
   Manageability
   Interoperability
   Performance/Tuning
    ebXML advantages

   Business processes

   Registry/Repository

   Security
      ebXML limitations

   Payload

   Slow development
    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
      Web services future
Year 2003         UDDI adoption increases. Private registries proliferate to
                  support private exchanges. Government use of Web

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

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

   Message Services
       already implemented
            ERCOT (Electrical Reliability Council Of Texas)

   Registry & Repository
       work currently in progress
    Total cost of ownership

   Capital

   Operation

   Development

   IT staff training and consulting by vendor
    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)
    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
    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
   Web services platform architecture
                             Installation and Administration

               Business Process

                                     WorkFlow Engine


                                                                                       Adapters        ERP

 Modeling                                                                              Adapters        CRM

                                                                                       Adapters         DB

  Process                                              Web Services Support Protocols
              Messaging/TRP Protocols
                 (SOAP, ebXML,                                      XML                 MIME         Web Services
                    RosettaNet)                                   Processing           S/MIME        Management
Development                                                               Security &
              Transport Level Protocols                                                               Runtime
               HTTP/SMTP/FTP, etc.                                                                   Monitoring
                              Base Integration Platform

                                  Runtime Environment
                                                                                                  SOURCE:WebMethods, 2002
   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
    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 M&A data, enabled by a Web Services
        Security become less of an issue for Web services

To top