• Tidak ada hasil yang ditemukan

Web Services Customer Scenarios

N/A
N/A
Protected

Academic year: 2023

Membagikan "Web Services Customer Scenarios"

Copied!
41
0
0

Teks penuh

(1)

Web Services Customer Scenarios

Ryoo, JungHyung

e-business Architect

Developer Relations, IBM Korea

[email protected]

(2)

Web services Opportunity?

2001 2002 2003

$0

$10

$20

$30

$40

$50

Billions

EAI Software e-business Integration Services

Source: IDC

The need for software

that simplifies integration is projected to approach $50 billion by 2003

jStart

(3)

What do the Analysts Say?

Trough of Disillusionment

Slope of Enlightenment

Plateau of Productivity

Maturity Technology

Trigger

ASPs

Speech Recognition Smart Cards

Micropayments Digital Ink

Synthetic Characters

Biometrics

Enterprise Portals

Audio Mining

Jini

xDSL/Cable Modems

3D Web WAP/Wireless

Web Voice Portals Visibility

XML

Quantum Computing

Webtops

Voice over IP Bluetooth

Java Language Less than two years

Two to five years Five to 10 years More than 10 years

S o u r c e : G a r t n e r , j S t a r t

W e b S e r v i c e s

jStart

(4)

?

All leading e-business platforms will support at least basic Web services infrastructure by 2002

?

By 2003, more than 75% of Web services in production will be supported by Web services

infrastructure provided by IBM, Microsoft and two to three other vendors

?

"The industry desperately wants vendors to move away from proprietary systems that lock firms into technologies. IBM has seen the writing on the wall, and is moving early. This is the way the industry is moving."

What do the Analysts Say?

Source: GartnerGroup

Source: GartnerGroup

Rob Hailstone, director of software infrastructure at research house IDC Silicon.com

(5)

What is the press saying?

?

"Web Services - IBM Gets it “

?

IBM shows an unmistakably greater sense of openness and customer-centricity.

?

With IBM, customers can use the combination of language,

operating system and hardware that makes sense for them, not the one that furthers the platform ambitions of their supplier.

?

In general, IBM "gets it" when it comes to multivendor interoperability on the Web.

?

IBM learned the hard way that embracing open, interoperable standards is not just a good strategy?it's the only strategy.

We wonder how long it will take for Microsoft and Sun to learn

the same lesson.

(6)

Storebrand ASA

?

Challenge:

? Want to sell finance and Insurance products through external distributors over Internet, which will require integration between COM and EJB

environments.

?

Solution:

? TietoEnator (one of Scandinavia's largest payroll vendors), will extract

necessary data which will be converted into a industry-standard XML-format, XMLife from Acord.

? A COM-component will generate a SOAP-request

? A Web Service will receive the data and pass it on to MQSeries Integrator

?

IBM Content:

? MQSeries, WebSphere, Web Services Toolkit.

?

Value:

? Espen Sletteng, Architect: “The entry of Web Services Technology into the IT industry is very timely as our customers are demanding Internet based solutions. Our early experience has shown efficiency improvements for Pension data maintenance.”

(7)

Transacttools

?

Challenge:

? Provide an ASP environment that will allow financial entities to certify the integration of their business applications with mirror images of the systems of their trading partners without human intervention.

?

Solution:

? Deploy UDDI and Web Services tooling from IBM as well as support for FIX, SWIFT and other financial protocols to deliver a peer-to-peer connectivity service. For example, the directory will play a role in the discovery of trading partners, the products and markets they trade, and the protocol/system

interfaces they support.

?

IBM Content:

? IBM WebSphere Application Server, IBM Web Services Toolkit, UDDI4J.

?

Value:

? Sam Johnson, CEO: “UDDI can provide a standard, consistent, and scalable framework for business directory services. These types of directories will be critical for industries that require sophisticated system-to-system

connectivity, like financial services. UDDI provides a convenient framework for delivering the directory service we’ve been creating.”

(8)

CommerceQuest

?

Challenge:

? How to extend the CommerceQuest enableNet Business Park such that

electronic business application services can be discovered and used via UDDI and Web Service technologies.

?

Solution:

? Initial effort will involve making the US Customs Service (a proprietary interface) available as an enableNet Web Service both internally and externally.

?

IBM Content:

? MQSeries, WebSphere, Web Services Toolkit, UDDI4J.

?

Value

? Paul Roth, CTO: “UDDI and Web Services are important because they allow any two random companies to learn how to interact with each other electronically. The ultimate aim of B2B commerce is to enable these ad hoc relationships .”

(9)

Visualize, Inc.

?

Challenge:

? Enable software product portfolio to be sold as services.

? Expand marketplace and revenue channels for visualization technology

? Reduce barriers to technology adoption

?

Solution:

? Initially, host and publish StockPlot™ as a Web Service for new and existing customers. Follow-up with other product services.

?

IBM Content:

? IBM WebSphere Application Server, IBM Web Services Toolkit.

?

Value:

? Gary Manton, SVP of Marketing: “We feel that Web Service technologies will help to form a significant new market through which we can deploy some of our current applications and upcoming financial market analytic technologies. It will enable us to deliver our product portfolio to customers with less

implementation costs on their side, which should help to increase our potential market.”

(10)

IMI

?

Who are IMI?

?

Global Supply Chain and Customer Service ISV - www.im.se

?

Java, MQ and WebSphere based product suite - Vivaldi

?

Vision and Challenge

?

Speedy integration of new services

?

Allow better fit to individual customers

?

Reduce integration cost/time

?

Allow ASP customers to aggregate other services to fit their individual customer requirements - "Just in Time" Integration

?

Solution

?

IBM Web Services Tooling

?

Speed of integration

?

No rebuild of business logic

?

Value

?

Promise of decreased time and cost to market, with better ability to

focus on customer needs

(11)

WAND

?

Challenge:

? Complement existing global trade directory assets with UDDI technology to provide their customers with broader exposure to the global marketplace.

?

Solution:

? WAND will be working with IBM to register their members into IBM’s UDDI registry and to enable the support of the WAND indexing system into IBM’s UDDI registry as well as the UDDI specification.

?

IBM Content:

? IBM’s UDDI registry system

?

Value:

? Ross Leher, Chairman and CEO: “WAND has a similar objective as UDDI in attempting to provide an overall, standardized means of facilitating identification, communication and trade for companies on a global basis.

We see this as our primary goal, and with the assistance of IBM … along with our classification assets, we hope to greatly facilitate the movement of this ideology forward.”

(12)

Hewitt Associates LLC

?

Vision

? Hewitt Associates is a global management consulting firm specializing in human resource solutions

? Want to easily deliver benefit plan participant data to 3rd party service providers

?

Challenge

? Data being provided is sensitive and thus access must be secure

? Many different 3rd party providers with multiple IT requirements

?

Solution

? Hewitt is intending to move from a proprietary protocol to a SOAP protocol in the very near future

? Hewitt is studying the WSDL specification and are looking to describe their services using this specification

? VA Java, WebSphere

?

Value

? Tim Hilgenberg, Hewitt's Chief Technology Strategist: "IBM's support of these new standards is key for us because we rely on both IBM hardware (zOS - Parallel Sysplex) and IBM Middleware (CICS, MQ, WebSphere) and data bases (DB2) to deliver our back-office services."

(13)

Who is Storebrand ?

? Norway's largest financial corporation

?

Storebrand Bank, an award-winning Internet bank

?

Storebrand Funds

? Storebrand Life Insurance, produces life products

?

6.500 company-customers

?

500 of the customers with more than 100 employees

?

covering 390.000 employees in total

?

Are dependent on current data from the employers about

the employees

(14)

The Business Challenges

?

Storebrand manages the pension funds of around 6500 companies in Norway

?

To maintain the accuracy of the claims, personnel data needs to be send from the participating companies to Storebrand on a regular basis

?

Often fowarded manually on paper

?

50 employees permanently assigned

?

Customers demand online functionality

?

Want to sell their life products through external

distributors over Internet

(15)

jStart Project Objectives

? Proof of technology for: WebServices

? Create WebServices for Storebrand side (Servlet)

? Implement infrastructure

?

WebSphere 3.5

?

Security

? Enable Vendor Payroll System(s) for WebServices

? Connect 5 existing Business Partners

? Deliver Whitepaper for partner connection

? Time to get connected to the system: < 1 day

(16)

Storebrand B2B Phase 1

? Payroll vendor will extract necessary data

? The data will be converted into a industry- standard XML-format, XMLife from Acord

? A COM-component provided by the vendor will generate a SOAP-request

? A Web Service at Storebrand will receive the data

and pass it on to MQSeries Integrator

(17)

Building The Web Service

?

1- Build the service as a bean

?

2- Register the service with the SOAP router

?

3- Define a service using WSDL

?

4- Register the service with UDDI

?

5- Call the service from a client using SOAP over HTTP either …

?

5.1- Directly using the basic SOAP interface ignoring the UDDI registration

?

5.2- By looking up the service in UDDI and binding to it

through WSDL

(18)

Basic Design Choices

? 1) just SOAP

?

Point-to-Point, single client technology

? 2) SOAP + WSDL definition

?

just WSDL - can configure, but not full repository lookup

? 3) SOAP + WSDL + UDDI

(19)

Step 1: Building the SOAP Connection

?

1) Define and build the service and its interfaces

?

build Java classes, C++, VB, COM component

?

2) Register the service with the SOAP router (deploy)

?

Can be entered via Webform at the Apache SOAP administrator GUI

?

Manually create a deployment descriptor and send it to the SOAP router by:

?

Invoking program from Apache to 'deploy' - i.e. a bat file

?

Develop your own program/script to perform deployment

steps automatically

(20)

Step 1: (continued)

?

3) Write a client to exercise the service:

?

At a minimum:

?

Build a Java program to make a Apache SOAP API call

?

This will:

?

create the SOAP envelope

?

send HTTP request

?

rpc router picks up the deployment descriptor for the requested services

?

creates a Java object and pass parameter into the correct method

?

which should create a response object or return a fault

(21)

WebServer - HTTP

RPC Router Client

Web Service

To define a WebService

1) Create a deployment descriptor file (or use Webform for definition)

2) Invoke Apache utility to deploy to RPC router HTTP

Deploy

WebSphere

1

Descriptor

2

3

Execute the client from a JVM - invoke SOAP APIs

3

2 1

Define the service and its interfaces

HTTP Listener

Step 1: (continued)

Now the service is known by the server hostname, port, and the Servlet "rpcrouter"

(22)

Step 2: Creating the WSDL

?

For an existing bean:

?

Use Service Wizard from WSDE to build a WSDL

?

Deploy WSDL to the Webserver:

?

So that it can be located via an URL

?

Can now use WSDL to configure client

?

Still a level of 'manual' interaction required

?

To provide access to WSDL

?

Benefit of WSDL:

?

Other technologies can read it, i.e. MS toolkit

?

(but MS toolkit cannot use the IBM/Apache WSDL today)

?

W3C standardization on WSDL (but implementation is

currently different)

(23)

Step 2: Creating the WSDL

WebServer - HTTP

RPC Router Client

Web Service

Make WSDL file external available:

I.e. URL through Webserver

HTTP

WebSphere

1 2

1

Use Wizard from WSDE to create:

1) WSDL file

2) client proxy

WSDL 2

Client can now request the WSDL data and construct invocation from provided information i.e the URL of the WSDL object

For example, http://localhost:8080/myservicesdescription.wsdl ---or use a provided proxy ! ? ? ?

(24)

Step 2: From the Client Side...

? Accessing the WebService:

?

1) Easiest way: using a proxy object (I.e. no changes for the app)

?

2) A bit more work: use the Toolkit APIs

?

3) Terrible way: code the SOAP requests directly

?

(e.g over HTTP today)

? Consequence:

?

The more you code directly into your client application,

the less flexibility you have on choosing aspects of the

service dynamically.

(25)

Service Discovery (Binding)

? 1) Dynamic - at runtime

? 2) At startup of services (deployment time)

? 3) Static ? services found and bound to at development time

?

Tools browse/search

?

? UDDI registry is a services directory

?

Contains service definitions

?

Programatically searchable

(26)

Step 3: Connecting to a UDDI Registry

GOAL: be able to obtain WSDL from UDDI

?

1) Use e.g. UDDI browser to register business (service provider) with UDDI

?

2) Register services (e.g. through UDDI4J)

?

3) from client: need to issue a ‘ FIND ’

?

Very specific:

?

Category #

?

Get WSDL file (first instance) from list

?

Queries could be:

?

‘ Give me all services of this company ’

?

Once the service description is obtained, the service can be

invoked as described in ‘ Step 2 ’

(27)

Client Side API Selection

? 2 options for Interface APIs again … .

? What Storebrand did not use … ..

?

1) SOAP level APIs using MS SOAP Toolkit V2 B1

? This beta does not support security reliably (too many bugs)

? It was also not supported for production

?

status of March 2001

(28)

Client Side API Selection

?

What Storebrand has implemented:

?

2) low level API: WININET

?

APIs from INET access (as explorer)

?

Gives for HTTPS well known interfaces

?

We needed to prove during the project the same level of security as the WEB solution with Smartcards

?

Use of client side certificate authentication

?

distribution method of certificate has not been determined yet

?

SSL

?

Consequence of using the WININET APIs:

?

need to construct SOAP envelop

?

cumbersome to get the messages right

(29)

Context Propagation

?

SOAP does not offer a standard mechanism to pass

additional information to a service beyond the parameter description

?

Need for adding data like session ids, admin or security data

?

Apache has implemented a ‘ pluggable provider ’ facility that can be used as a temporary remedy

?

Future versions of Apache SOAP will provide AXIS (Apache eXtensible Interaction System)

?

A pluggable (handler) framework for pre- and

postprocessing

(30)

To WSDL or Not?

? Storebrand did not use a WSDL - Why ?

? This is what actually got implemented:

?

Services information retrieved from a property file

?

Contains location info PLUS config parameters for COM environment, e.g. max msg size, etc.

?

No benefit of using WSDL in current scenario

(31)

Interoperability

?

No standard test suite available

?

Check discussion at:

?

http: // groups.yahoo.com/group/soapbuilders

?

who should do this ?

?

Apache / IBM vs MS

?

SOAP support fixed since Toolkit V2.2

?

WSDL 1.0 support problematic

?

SDL - NASSL heritage

?

document structure different from MS / IBM

?

can be fixed, by manual editing

?

W3C acknowledged standard submission of WSDL 1.1 on

March 6th

(32)

Reliable Message Delivery

? QoS - Quality of Service

?

Not there - at least in the specs

?

Need to be solved either

? on application level

? transport level

? Today: XML over HTTP (HTTPS)

?

Message Ids provided by application will guarantee that a message is delivered, and only delivered once

?

Data integrity guaranteed through SSL encryption

(33)

Key Technologies/Products Used

?

Server Side

?

WebSphere 3.5.2

?

Visual Age for Java 3.5

?

IBM XML Parser

?

IBM DB2 UDB PE v7.1

?

IBM WSTK 2.1

?

IBM WSDE

?

Client side

?

MS SOAP Toolkit V2 Beta 1

?

Visual Basic 6

?

XMLSPY editor

(34)

WebServer - HTTP

RPC Router Client

Pluggable provider HTTP

WebSphere

WSDL

UDDI registry

UDDI

List of services returned from UDDI

HTTP Listener

Web Service

Server Side - Overview

(35)

Impact On The Business

? Pension data maintenance is much more efficient

? Interest from Payroll vendors

?

Flocking for experience about how to enable their applications for Web Services

? Interest from Business Partners

?

Want to broaden the use of Web Services for

?

automating B2B

? Interest from other insurance companies

?

Establish standards (tModels) for industry use

(36)

Review of Achievements

?

Created standard to deliver Life insurance data in Norway for STBs 6.500 partners

?

Based on XMLife of ACORD

?

Standards based B2B - secure over Internet !

?

Using SOAP and HTTPS/SSL

?

Integrate vendor application(s)

?

Via XML file wrapped as COM object

?

Connect COM and Java WebSphere environment via SOAP

?

Combined 2 worlds

?

All this in less than 1 month !

(37)

Payroll appl

COM XML

SOAP

SOAP over HTTPS

WebServer - HTTP

RPC

Router Web

Service

WebSphere

JAVA Windows NT

Review of Achievements

(38)

MicroDoc GmbH

?

Challenge

? Help a customer to provide information and services to third parties having a variety of IT infrastructures. Online access was essential, so they needed a technology that allowed them to create manageable B2B connections. As the customer services evolve, they must publish these offerings as quickly as

possible. To help their customers achieve a more efficient level of integration, MircoDoc looked to Web Services technologies and partnering with IBM.

?

Solution

? Provide the customer with a Web Services-based call management center, using SOAP messaging to communicate between the host site and 80 remote offices. The solution was designed to be expanded to handle new service types which will be published in a UDDI registry.

?

IBM Content

? Call management system based on WebSphere, SOAP, JSPs, and DB2.

?

Value

? The customer will be able to share new internal processes with business

partners through the use of Web Services without extra effort. Application design is simplified because a single service-architecture will be used for

HTML and XML communication to end users and business partners alike. TCIs ability to quickly respond to new market demand will significantly be improved.

(39)

What do These Success Stories have in Common?

? Focused on business problems and successfully met objectives

? Innovated with proven, industry standard, leadership products

? Built a foundation that serves as a roadmap for the future

? Were all part of IBM jStart program

WebSphere

VisualAge for Java

Visual Age MQ Series DB2

(40)

Innovators

Early Adopters

Early Majority

Late Majority

Laggards

The jStart Audience

Technology Adoption Life Cycle

(41)

IBM jStart Partnership Program

?

Qualified Projects

?

Prototype or completion within 60-90 days

?

Project satisfies critical business requirement

?

Customer willing to be reference account

?

Must be building web services in conjunction with IBM

technology (Web Services ToolKit, WebSphere,DB2, MQ, ...)

?

Resources

?

design/development

?

mentor program

?

support

?

Joint Promotion

Referensi

Dokumen terkait

Several previous studies have found decreased corneal sensibility, decreased secretion and stability of tear film, lower goblet cell density also