# Presentation: 280522

## Enterprise Architecture:ebXML & Web services

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

## Agenda

- 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?

## Approach

- Conduct Literature Review
- Interview Experts
- Benchmark studies

## Evolution of distributed computing

- Microcomputer,
- OS, Mailboxes

- SOAP & WSDL

-   Email

-   EDI

- RPCs

-   The Web

-   XML and RELATED

- eSpeak, XML-RPC, SOAP 0.9, etc.

-   CORBA, DCOM

- 1970 	1980	1990	1997	1999	2000	2001	2002

- ebXML

- Web services

## 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

**Notes:**
SOAP - programmatic interface
to enable applications to find and interact with one another
   Web Services use a common network - the Internet
to transport information and data between cooperating applications. 

-  Service Broker

**Bind (SOAP)**** **

- Service
- Provider

- Service
- Requester

**Publish**
**(UDDI)**

**  ****Find**
**(WSDL)**

-    Web services concept

## ebXML concept

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

**Notes:**
Messaging Service:
SOAP with Attachment
Registry/Repository: 
Specifications, profiles & scenario
Business Process:
Standardize diverse business transactions
Core Components:
Standardize items of exchanging messages
Trading Partner Profiles: 
CPP (Collaboration Protocol Profile), CPA (Collaboration Protocol Agreement)

## Web services products

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

**Notes:**
Companies exposing their applications 
Mapquest, Google, D&B, Amazon.com
Application Servers 
 turnkey application servers 
 WebSphere, SUN One
application server software
 Microsoft .NET
Professional services firms 
GE GXS, NextLinx , WebMethods

## 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 

- Suppliers

- Customers

- Assembly
- Line

- Logistics

- Edge Activity

- 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

**Notes:**
PRESENTER: Steve Grendel
KEY POINTS:
Discuss key ERCOT Attributes (see points in slide).
Emphasize key Retail Facts: 6.25 million customers; ~10% US demand
Electric Reliability Council of Texas   (ERCOT)Independent System Operator (ISO)Registration Agent (RA) for Electric     Industry Deregulation in Texas
ERCOT implements deregulation in     Pilot : July 2001
 ERCOT implements full deregulation in   Texas: January 2002
 ERCOT processes over 15 million   transactions per month
ERCOT is required to support both XML and EDI transaction standards.
 EDI implemented first in 2001 Pilot.
 XML in process of being implemented in 2002 with small volumes currently in production.

## Customer switch “Initiation”

**Notes:**
PRESENTER: Steve Grendel
KEY POINTS:
The process begins when the new Retailer submits a switch request to ERCOT.
ERCOT processes the switch request and notifies the submitting Retailer,  the TDSP, and sends the customer a postcard notifying him of an impending switch (if valid).  At this time, a customer review period begins that gives the customer an opportunity to cancel the switch.
If the switch request is invalid, ERCOT notifies the submitting Retailer and the switch process terminates.

## Customer switch “Completion”

- 3. Completes switch

**Notes:**
PRESENTER: Steve Grendel
KEY POINTS:
The TDSP sends the ESI ID information (including confirmed meter read date) and any requested historical usage to ERCOT which then forwards it to the Retailers.
The TDSP reads the meter and sends the data to ERCOT via two EDI transactions.  ERCOT then completes the switch and forwards this data to both Retailers and it becomes the initial meter read for the new Retailer (867_04) and the final meter read for the current Retailer (867_03).

## 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

**Notes:**
1.Hence, getting a company’s Web service known is difficult.
2. For example, WSDL needs to include the ability to negotiate payments for services delivered.

## ebXML advantages

- Business processes
- Registry/Repository
- Security

**Notes:**
Business Processes
Standard Business Processes - Enterprise Integration Available 
Registry/Repository 
Robust functionality
Authentication of  trading partners,dynamic build of schemas
Security
Messaging specs of ebXML are superior to those of SOAP for secure documents
Secure protocol, digital signature

## ebXML limitations

- Payload
- Slow development

**Notes:**
Payload
Success of payload is Critical Success Factor for ebXML
ebXML may be adopted only in parts until the payload (UBL) is introduced 
UBL(Universal Business Language)
First version: 2003
Slow going
Not yet ready for prime time
Political/ Vendor battles
Adoption curve dependent on registry and core components development
Not as easy to put in place as Web Services
Some components are still under construction

## 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 			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*

## 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)

## 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 

- 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

- The U.K. experience (continued)

**Notes:**
The Resource Description Framework (RDF) is a general framework for how to describe any Internet resource such as a Web site and its content. An RDF description (such descriptions are often referred to as metadata, or "data about data") can include the authors of the resource, date of creation or updating, the organization of the pages on a site (the sitemap), information that describes content in terms of audience or content rating, key words for search engine data collection, subject categories, and so forth. 

## 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

**Process **
**Modeling**

**Process**
**Definition**

**Service**
**Development**

**Transaction**
** ****Control**

**Adapters**

**Adapters**

**Adapters**

**Deployment**

**ERP**

**CRM**

**DB**

**Messaging/TRP Protocols**
**(SOAP, ebXML, **
**RosettaNet)**

**XML**
** ****Processing**

**MIME**
**S/MIME**

- Base Integration Platform

**Security & **
**Authentication **
**Services**

**Transport Level Protocols**
**HTTP/SMTP/FTP, etc.**

**Web Services **
**Management**
**and **
**Runtime**
**Monitoring **
**Tools**

**Business Process Collaboration**

**WorkFlow Engine**

**Web Services Support Protocols**

**Systems Monitoring Management**

- Runtime Environment

*SOURCE:WebMethods, 2002*

## 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

**Notes:**
Do feasibility analysis of working ebXML standard bodies; if no – establish standard body of its own
Work with ebXML standard bodies to include use cases for government transactions

## Questions?

## 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 implementation