High Level Design for CrossWorlds: Service Level ...web.mit.edu/noto/ibm/ibm/9237.3.doc · Web...

HLD for ExtremeBlue : “CrossWorlds: Service Level Management and Web Services (BlueBiz)”

Version: 0.2

Rob Cutlip

Please address any queries to:Rob Cutlip

3039 Cornwallis AvenueRTP, NC 27709

E-mail: [email protected]

Telephone: (919) 486-1178Internal Telephone: 8-526-1178

Latest Revision: 25 May 2023Next revision planned: 03 June 2002

CrossWorlds: Service Level Management and Web Services”IBM Confidential

Document Control

NotesThe master copy of this document (BlueBiz_SLMandWebServices.doc) has been saved in the ExtremeBlue Team Room Database. Please refer to the master copy if in doubt about the currency of this document.

If a hard copy is made it is valid only on the day printed.

AuthorsKristin Firth

Neeraj Joshi

Malia Morley

Matt Notowidigdo

(Rob Cutlip)

ApprovalDate Name Title

Pam Durham Extreme Blue: Executive Representative

ReviewDate Name Title

Brent A. Miller Extreme Blue: Lead Technical Mentor

Richard Franck Extreme Blue: Technical Mentor

Gary McGibbon Extreme Blue: Lead Business Mentor

Marcel Kinard Extreme Blue Technical Liaison

John Graham Extreme Blue Technical Liaison

Rob Cutlip Extreme Blue: Technical Mentor

Change HistoryDate Amended by Details of amendment

12 April 2002 rrc 0.1 Initial draft

9 May 2002 rrc 0.3 draft

“BlueBiz” Specification Page 3 of 35


1 Table of Contents



2Document Control.....................................................................................................................3

Notes......................................................................................................................................3

Approval................................................................................................................................3

Review...................................................................................................................................3

Change History.....................................................................................................................3

1 Table of Contents Introduction.........................................................................................4

1 Introduction.......................................................................................................................8

1.1 PURPOSE OF THIS DOCUMENT.......................................................................8

1.2 BlueBiz Project Deliverables...................................................................................8

1.3 How to make changes to the document..................................................................8

2 “BlueBiz” Architectural Overview...................................................................................9

2.1 Architectural Overview – Service Level Management.........................................9

2.2 High Level Flows....................................................................................................102.2.1 Operational Flows............................................................................................102.2.2 Management Flows..........................................................................................11

2.3 Repositories.............................................................................................................122.3.1 Required...........................................................................................................122.3.2 Standard and required......................................................................................12

2.4 Services....................................................................................................................132.4.1 Portal Services..................................................................................................132.4.2 SLM Services...................................................................................................132.4.3 CrossWorlds Services......................................................................................13

3 BlueBiz Design Overview................................................................................................14

3.1 Scope........................................................................................................................14

3.2 Objectives................................................................................................................14

3.3 Components Overview...........................................................................................143.3.1 Applications.....................................................................................................143.3.2 Business Processes...........................................................................................143.3.3 Repositories:.....................................................................................................143.3.4 Generic Services:.............................................................................................143.3.5 SLM Services...................................................................................................143.3.6 TBD..................................................................................................................15

4 “BlueBiz” Component(s)................................................................................................16

4.1 Objectives addressed by Web Service-CW component......................................164.1.1 Synchronous Inbound Call (Web Service) to a CW Collaboration.................164.1.2 High Level Sequence.......................................................................................164.1.3 Boundary Considerations.................................................................................17



4.1.4 Security Considerations...................................................................................174.1.5 Performance Considerations............................................................................174.1.6 Expected Consumers of this Component.........................................................174.1.7 Assumptions and Dependencies:......................................................................174.1.8 Issues:...............................................................................................................18

4.2 Objective of Component “B”................................................................................194.2.1 Function............................................................................................................194.2.2 High Level Sequence Diagram........................................................................194.2.3 Boundary Considerations.................................................................................194.2.4 Security Considerations...................................................................................194.2.5 Expected Consumers of Component................................................................194.2.6 Assumptions and Dependencies:......................................................................194.2.7 Issues:...............................................................................................................19

4.3 Objective of Component “N”...............................................................................194.3.1 Function............................................................................................................194.3.2 High Level Sequence Diagram........................................................................194.3.3 Boundary Considerations.................................................................................194.3.4 Security Considerations...................................................................................194.3.5 Expected Consumers of Component................................................................194.3.6 Assumptions and Dependencies:......................................................................194.3.7 Issues:...............................................................................................................19

5 Hardware and Software Component Characteristics....................................................20

5.1 Operational Environment.....................................................................................205.1.1 Required Hardware..........................................................................................205.1.2 Required Software............................................................................................205.1.3 Optional and Available Software.....................................................................205.1.4 Optional AlphaWorks Technologies................................................................205.1.5 Non-Supported Hardware and Software..........................................................21

5.2 System Resources...................................................................................................215.2.1 Restrictions.......................................................................................................215.2.2 Estimates..........................................................................................................21

5.3 Migration Characteristics.....................................................................................215.3.1 Incompatibilities during Migration..................................................................215.3.2 Migration Aids.................................................................................................21

5.4 Security....................................................................................................................215.4.1 Securing Individual Services: Overview..........................................................215.4.2 Non-repudiation...............................................................................................225.4.3 Authorization....................................................................................................225.4.4 Authentication..................................................................................................22

5.5 Performance............................................................................................................225.5.1 Response Time.................................................................................................225.5.2 Throughput.......................................................................................................22

5.6 Capacities................................................................................................................22

5.7 Reliability, Availability, and Serviceability (RAS)..............................................225.7.1 Messages..........................................................................................................22



5.7.2 Tracing.............................................................................................................22

5.8 Standards Compliance...........................................................................................235.8.1 IBM..................................................................................................................235.8.2 International.....................................................................................................235.8.3 Domestic..........................................................................................................235.8.4 Industry............................................................................................................23

5.9 World Trade Considerations................................................................................235.9.1 National Language Support..............................................................................235.9.2 Legal Constraints.............................................................................................235.9.3 Import/Export Restrictions...............................................................................235.9.4 Certifications....................................................................................................23

5.10 Usability Characteristics.......................................................................................235.10.1 Service Level Management – Administrative Access.....................................235.10.2 Service Level Management – Customer Access..............................................23

5.11 Publications.............................................................................................................23

5.12 Packaging................................................................................................................23

6 Design..............................................................................................................................24

6.1 Technical Introduction and Overview.................................................................24

6.2 “BLUEBIZ” Service Flows....................................................................................246.2.1 Internal.............................................................................................................246.2.2 Outgoing...........................................................................................................246.2.3 Incoming..........................................................................................................24

7 External Interfaces..........................................................................................................25

8 Internal Interfaces...........................................................................................................26

9 Installation / Configuration / Administration................................................................27

9.1 Installation..............................................................................................................279.1.1 WebSphere Administration..............................................................................279.1.2 CrossWorlds Administration............................................................................279.1.3 Service Catalog Administration.......................................................................27

9.2 Configuration..........................................................................................................279.2.1 WebSphere Administrator................................................................................279.2.2 Service Catalog Administrator.........................................................................279.2.3 CrossWorlds Administrator.............................................................................27

9.3 Starting and Stopping the System........................................................................28

9.4 Test Considerations................................................................................................28

10 Appendix A: Recommended References and Documentation...................................29

10.1 Product Documentation.........................................................................................2910.1.1 CrossWorlds.....................................................................................................2910.1.2 WebSphere Studio Application Development.................................................2910.1.3 Ipedo.................................................................................................................29

10.2 Associated and Supporting Documentation.........................................................29



10.2.1 IBM Redbooks and RedPieces.........................................................................2910.2.2 Other References..............................................................................................30

11 Appendix B: xSP Solution Architecture.....................................................................31

11.1 xSP Services............................................................................................................3111.1.1 Service Creation...............................................................................................3111.1.2 Enrollment........................................................................................................3111.1.3 Subscription......................................................................................................3111.1.4 Provisioning.....................................................................................................3111.1.5 SLA..................................................................................................................31

11.2 “BlueBiz” Design Points........................................................................................3111.2.1 Metering...........................................................................................................3111.2.2 Gateway Support..............................................................................................3211.2.3 Web services support.......................................................................................3211.2.4 SLA..................................................................................................................3211.2.5 SLM..................................................................................................................3211.2.6 Service Catalog................................................................................................3211.2.7 WSDL – binding..............................................................................................3211.2.8 Portal – User Interface.....................................................................................33

11.3 Web Services: supported service flows...............................................................3311.3.1 Web Services Gateway....................................................................................3311.3.2 General Purpose Web Services........................................................................3311.3.3 Web Services with Crossworlds.......................................................................33

END OF DOCUMENT......................................................................................................34



3 IntroductionThis document addresses the architecture and design of the ExtremeBlue project referred to hereafter as BlueBiz. This design document addresses how the software component(s) are implemented to support the requirements. The components include service level agreement management and measurement moieties to address business opportunities in the service provider marketplace. This document also contains information useful to technical support, system test, information development, release management and product planning staff.

3.1 PURPOSE OF THIS DOCUMENT

The purpose of this document is to provide a starting point for the Extreme Blue team building the BlueBiz solution. It is meant to be descriptive, not proscriptive. It frames the larger architectural domain of the xSP Solution space, as well as a possible architecture for the BlueBiz solution. It also provides the beginnings of solution component definition, the software and hardware environment and a number of resources that can be leveraged to support design and execution. At the onset of the project, the BlueBiz interns assume ownership of this document and its use; its modification is left solely to their discretion.

3.2 BlueBiz Project DeliverablesThe major deliverables of the BlueBiz project are listed next. They were derived from the project proposal document “BlueBiz” Business-to-Business Service Level Management with CrossWorlds and Web Services: An Extreme Blue Project Proposal (bluebiz.doc).

A demonstrable solution featuring a service level management (SLM) software system, targeted toward service providers. The solution will leverage Web services and IBM CrossWorlds collaborative business processes.

Definition and demonstration of service level agreements (SLAs) using WSLA. Definition and demonstration of a service catalog using a native XML database. Definition and demonstration of portal for the SLM system. Definition and demonstration of SLM modules integrated with existing IBM SLA

software..

3.3 How to make changes to the documentRequests to change this document can be submitted via e-mail to the document owner. Any change to this document requires another approval cycle. The revised document is submitted as a draft to the original reviewers and approvers (or their replacements or delegates) for approval. Note that all draft changes are made as marked-up edits and also are summarized in the “Document Change History” section of the Preface. The document owner may batch up minor changes for the sake of approver efficiency. Once approved, the new version of the document becomes available for distribution.



4 “BlueBiz” Architectural OverviewAn architectural overview of the BlueBiz problem space is presented in this section. The architectural overview is present here to provide context for the remainder of the document. Refer to Appendix B for an overview of the xSP solution architecture. The philosophy governing this architectural approach is common component re-use, in terms of both commercially available software and standards.

4.1 Architectural Overview – Service Level Management

Figure 1. High Level overview of main features

At the far left of Figure 1 are the two external consumers of this system, the enterprise client and the enterprise application. The enterprise client interfaces with the system through the SLM portal services. The enterprise application interfaces with CrossWorlds collaborations through the use of Web services. Internally, administration of the SLM system, including the service catalog, is performed through SLM portal services. The SLM solution environment is composed of four major moieties: the portal services, the SLM services, the CrossWorlds services and the repositories.



4.1.1 Architectural Guidance

The CrossWorlds services and the flows that result from their use will be those that are standard and available at the onset of the project. The primary operational flow might or might not involve a gateway at the Internet boundary. It might or might not involve higher levels of binding abstraction. The basic operational flow outlines in section 3.2.1.1. should remain unchanged. The other three components (the repositories, the portal and the SLM services) roughly map to the model, view, controller (MVC) paradigm. Commercially available, off-the-shelf software should be used where appropriate.

4.2 High Level Flows4.2.1 Operational Flows4.2.1.1 Inbound Web Service call to CrossWorlds Collaboration.

Figure 2. Operational Flow to be monitored



4.2.1.2 Metering and monitoring of SLM metrics

Metering should be sufficient to meet the monitoring requirements of the SLM system. Metering may occur at one or many of the following points:

at the Internet boundary within the Web server supporting the CrossWorlds SOAP servlet on and with the CrossWorlds ICS and collaboration environment. The CrossWorlds

collaboration is a stateless, workflow engine that uses MQSeries as its primary mechanism for persistence.

4.2.1.3 Integration of SLM modules with existing IBM (service level) software

4.2.2 Management Flows4.2.2.1 Service Level Management administration through portal

Figure 3. Administration through Portal



4.2.2.2 Service Level Management - Client access through portal

Figure 4. Client services through Portal

4.3 Repositories 4.3.1 Required

A service catalog is required to support the SLM system. The Service Catalog is built upon a commercially available database

management system. The service catalog stores documents in the form of WSLAs.

WSLAs constitute service level agreements (SLAs) SLAs are composed of service level objectives (SLOs)

XML stored in the service catalog is stored in native XML format The database system that supports the service catalog must support XQuery

access. The data within the database system also may be exposed as a Web service.

4.3.2 Standard and required. WebSphere Application Server configuration database IBM UDDI registry IBM Crossworlds repository



4.4 Services4.4.1 Portal ServicesRequired services for the portal include:

X Y Z

4.4.2 SLM ServicesThe SLM services…

4.4.3 CrossWorlds ServicesThe CrossWorlds services…



5 BlueBiz Design Overview

5.1 Scope

5.2 Objectives

5.3 Components Overview5.3.1 Applications

tbd tbd tbd

5.3.2 Business Processes CrossWorlds Collaboration: ATP tbd

5.3.3 Repositories: CrossWorlds repository Service catalog implemented on native XML database UDDI Registry WebSphere configuration database on DB2 tbd

5.3.4 Generic Services: Authorization Billing Contracts Web service-to-CrossWorlds collaboration Identity License Management Offerings tbd

5.3.5 SLM Services Metering Quality of service (QOS) Rating Reporting Self-service Service catalog tbd



5.3.6 TBD tbd tbd tbd



6 “BlueBiz” Components

6.1 Objectives addressed by Web Service-CrossWorlds component

The Web Service-to-CrossWorlds collaboration component addresses how Web services are used to access CrossWorlds collaborations externally. This component also serves as a foundation flow on which to design, build and test the “Blue Biz” solution.

6.1.1 Synchronous Inbound Call (Web Service) to a CrossWorlds Collaboration

Figure 5 details the data synchronization collaboration.

Figure 5 . Web Service-to-CrossWorlds Collaboration Flow

6.1.2 High Level Sequence 1. Web services call originated by enterprise application2. SOAP Servlet that resides on a Web service makes appropriate proxy calls3. Proxy calls call the Server Access Interface (SAI) to CrossWorlds4. The SAI takes the SOAP message and passes it to a SOAP Data Handler5. The SOAP DataHandler uses the appropriate MetaObject to perform SOAP-to-

Business Object conversion.



6. A CrossWorlds collaboration within a collaboration group consumes the Business Object and makes calls to appropriate applications.

7. Application(s) return application-specific business object(s) to the CrossWorlds Collaboration Group

8. A Collaboration within the Collaboration Group calls SAI9. SAI calls the SOAP Data Handler, which converts Business Object(s) to SOAP

object(s)10. SOAP message is returned to SAI11. SAI sends SOAP return message to SOAP proxy12. SOAP proxy sends message to SOAP Servlet13. SOAP Servlet returns message to enterprise application

6.1.3 Boundary ConsiderationsThere are advantages to deploying a gateway server or gateway processes at the boundary between the Internet and the CrossWorlds Enterprise environment. These include the ability of the gateway to perform consistent validation (syntactic, security credentials and so on) of all of the traffic that passes through it and the ability of some gateways to perform content transformation, thus enabling legacy (non-Web services) applications to participate in the solution.In production deployments, the use of edge-of-network devices (edge servers) and intra-enterprise firewall considerations must be taken into account; neither of these is addressed here.

6.1.4 Security ConsiderationsN/A

6.1.5 Performance ConsiderationsN/A

6.1.6 Expected Consumers of this Component Designers of SLM components Developers of SLM components Testers of the BlueBiz solution SLM monitoring applications

6.1.7 Assumptions and Dependencies:6.1.7.1 Assumptions

Existing sample CrossWorlds collaborations can be re-used. DB2 is used as the CrossWorlds repository. Test connectors are used to stub any collaboration interfaces that are not available. WebSphere Application Server v4.+ is used.

DB2 is used as the WAS repository A “driver” that simulates an enterprise application will be developed. IBM’s Public UDDI Registry is used as the public registry services are published. IBM’s Private UDDI Registry may be used as the private registry services are

published. tbd



6.1.7.2 Dependencies

Requires CrossWorlds v 4.1. for Windows to support Web Services Requires CrossWorlds v4.1. for Windows to support DB2 as its repository CrossWorlds “ramp-up” dependencies include:

o Learning how to use the CrossWorlds componentso Learning how to create the necessary artifacts (WSDL, Business Objects,

Meta-objects and proxy classes)o Learning how to deploy and configure all of these artifacts, including using

WebSphere Application Servero Capturing the implementation procedures for building and using this

component The CrossWorlds Web Services Generation Utility with CrossWorlds 4.1 must

generate valid WSDL, XML schema definitions and CrossWorlds/ICS proxy code that can trigger collaborations in a CrossWorlds ICS node and can be deployed in WebSphere.

tbd

6.1.8 Issues:6.1.8.1 Compatibilities

tbd

6.1.8.2 Incompatibilities

tbd



6.2 Objective of Component “B”6.2.1 Function6.2.2 High Level Sequence Diagram 6.2.3 Boundary Considerations6.2.4 Security Considerations6.2.5 Expected Consumers of Component6.2.6 Assumptions and Dependencies:6.2.6.1 Assumptions



6.2.7.2 Incompatibles

6.3 Objective of Component “N”6.3.1 Function6.3.2 High Level Sequence Diagram 6.3.3 Boundary Considerations6.3.4 Security Considerations6.3.5 Expected Consumers of Component6.3.6 Assumptions and Dependencies:6.3.6.1 Assumptions



6.3.7.2 Incompatibles



7 Hardware and Software Component Characteristics

7.1 Operational EnvironmentDesign, coding and unit testing (DCUT) for the BlueBiz components uses the hardware and software described next. This list describes an operational development environment; production environments will differ from the one described here, based on non-functional requirements.

7.1.1 Required Hardware IBM xSeries 300 IBM Thinkpad T20 Ethernet network

7.1.2 Required Software WebSphere Application Server v4.0+ WebSphere UDDI Registry v1.1 CrossWorlds: v4.1.1

o DB2 v7.2 supporto Web Services supporto Collaboration support for known business processo Connector for Web serviceso Web Services Generation Utilityo CrossWorlds development tooling:

Process Designer Test Connector Map Designer Relationship Designer Connector Development Kit

Websphere Studio Application Developer v4.02 DB2 v7.2 Ipedo v3.1 native XML database TBD

7.1.3 Optional and Available Software WebSphere 5.0 (beta) WebSphere Portal Server Firewall software and/or appliances IBM WebSphere Edge Server IBM Policy Director IBM SecureWay LDAP V 4.2.1 Oracle 8.1.7 Tivoli Service Level Advisor v1.1 TBD

7.1.4 Optional AlphaWorks Technologies



http://www.alphaworks.ibm.com/

Web Services Gateway Web Services Invocation Framework Web Services Hosting Technology Web Services Tool Kit XML Schema Quality Checker Business Explorer for Web Services Servlet Manager XML Registry TBD

7.1.5 Non-Supported Hardware and Software

N/A

7.2 System Resources7.2.1 Restrictions7.2.2 EstimatesThe individual released products in the product stack provide their own documented resource estimates.

7.3 Migration Characteristics7.3.1 Incompatibilities during Migration

N/A

7.3.2 Migration AidsN/A

7.4 Security7.4.1 Securing Individual Services: Overview


http://www.alphaworks.ibm.com/


7.4.2 Non-repudiation 7.4.3 Authorization7.4.4 Authentication7.4.4.1 Privacy

7.5 PerformancePerformance benchmarks are not considered at this time for the BlueBiz Web services component.

7.5.1 Response TimeN/A

7.5.2 ThroughputN/A

7.6 CapacitiesCapacity/throughput has not been considered at this time for the BlueBiz components.

7.7 Reliability, Availability, and Serviceability (RAS)Tracing for the SLM Web services is performed using the built-in WebSphere Application Server trace support. This component can be configured using the WebSphere administration console. The SLM components of BlueBiz are expected to provide an alternate configuration GUI for WebSphere Application Server trace configuration.

.

7.7.1 MessagesExceptions are logged in WebSphere and CrossWorlds, where appropriate.

7.7.2 TracingWebSphere Application Server tracing is used. CrossWorlds tracing is also used.



7.8 Standards Compliance7.8.1 IBM

N/A

7.8.2 InternationalN/A

7.8.3 DomesticN/A

7.8.4 IndustryN/A

7.9 World Trade Considerations7.9.1 National Language Support

N/A

7.9.2 Legal ConstraintsN/A

7.9.3 Import/Export RestrictionsN/A

7.9.4 CertificationsN/A

7.10 Usability Characteristics 7.10.1 Service Level Management – Administrative Access

Service catalog access function UDDI Registry access function

7.10.2 Service Level Management – Customer Access Registration functions Offering catalog functions Subscribed services functions Reporting functions

7.11 PublicationsThe BlueBiz components have associated procedures and technical overviews that will

be used by teams that deploy SLM services on CrossWorlds-Web services. These publications, containing these procedures, are determined by the BlueBiz team.

7.12 Packaging



8 Design

8.1 Technical Introduction and Overview

8.2 “BlueBiz” Service Flows8.2.1 Internal8.2.2 Outgoing8.2.3 Incoming



9 External Interfaces



10 Internal Interfaces



11 Installation / Configuration / Administration

11.1 InstallationInstallation of BlueBiz Web services-related artifacts will consist of several tasks performed by people with different roles, as described next.

11.1.1 WebSphere AdministrationA WebSphere administrator will deploy this J2EE enterprise application (EAR) into WebSphere.

11.1.2 CrossWorlds AdministrationBlueBiz will include Meta Object definitions and SOAP Connector configuration information that can be deployed into the CrossWorlds ICS using a CrossWorlds 4.1.1 project.

11.1.3 Service Catalog AdministrationThe BlueBiz service catalog will be updated with WSLA definitions and WSDL definition updates will be made to the appropriate UDDI registry.

11.2 ConfigurationConfiguration of BlueBiz Web services-related artifacts consists of several tasks performed by people with different roles, as described next.

11.2.1 WebSphere AdministratorThe WebSphere administrator must set up WebSphere security for the node, defining roles and users in those roles.

11.2.2 Service Catalog AdministratorThe Service Catalog administrator must generate the appropriate WSAL definitions and add them to the service catalog and authorize access the service catalog.

11.2.3 CrossWorlds AdministratorThe CrossWorlds SOAP Connector must be configured to support collaborations that are called outbound through the Web services Gateway from within a collaboration. The administrator must provide proper mappings for the request and response that pass through the SOAP Connector and must configure CrossWorlds Meta Objects.

Inbound collaborations also require Meta Object configuration for the XML/SOAP DataHandler, which maps SOAP to business objects for the inbound requests and business objects to SOAP for the responses.



11.3 Starting and Stopping the System

The WebSphere Administration Console may be used to start and stop applications or their individual components. Additionally, starting CrossWorlds collaborations requires starting the MQ listener, the supporting database system, the Visigenics ORB and CrossWorlds (stopping CrossWorlds collaborations requires stopping these same components).

11.4Test ConsiderationsTesting should consider test cases based on the following scenarios:

Verification of inbound Web service to CrossWorlds Collaboration Verification and metering of inbound Web service to CrossWorlds Collaboration Verification and reporting of inbound Web service to CrossWorlds Collaboration Verification of SLA creation in the service catalog, in the form of a WSLA. Verification of discovery of WSLA through the use of a UDDI registry. Verification of administration of SLM through a portal. Verification of consumer registration, offering enrollment and reporting through a

portal



12 Appendix A: Recommended References and Documentation

12.1Product Documentation12.1.1 CrossWorlds

CrossWorlds Glossary

Administration Guide

Installation Guide for Windows

Connector Development Guide

Collaboration Development Guide

Business Objects Design Guide

Data Handler Reference Guide

Implementation Guide

Map Development Guide

Integrated Solutions and J2EE

Guide to the IBM CrossWorlds Connector for Web Services

12.1.2 WebSphere Studio Application Development Online Product Documentation

IBM Redbooks http://www.itso.redbooks.com

Developer Works http://www-106.ibm.com/developerworks/

12.1.3 Ipedo Ipedo Developer’s Guide

Ipedo Installation_Administration Guide

Ipedo_Administration Guide

12.2 Associated and Supporting Documentation12.2.1 IBM Redbooks and RedPieces. Web Services Wizardry with WebSphere Studio Application Developer, SG24-6292-00

Redbook, published April-5-2002, last updated April-5-2002

Self-Study Guide: WebSphere Studio Application Developer and Web Services, SG24-6407-00 Redbook, published February-28-2002



12.2.2 Other References

“IBM Web services provisioning for Websphere: Web Services Hosting Technology, v1.0”

“Metering and Accounting Services: Version for Web Services Toolkit”, Financial Transaction Web Services Team

“An Introduction to Web Service Level Agreement Language (WSLA)”, Richard Franck.

“Service Catalog and SLA in an xSP Environment”, Franck. “UDDI and LDAP: A Comparative White paper”, Cutlip, McGarvey and Ehnebuske “Service Level Management in an xSP Environment, xSP Architecture Team, SWG,

March 15, 2002 xSP Terminology: (a Glossary), xSP Architecture Team, SWG, January 2001 xSP Solutions: Requirements for XML DB v0.2, (A white paper), Cutlip, 12/15/2002. Foundations of Service Level Management, Sturm et al, Sams Publishing, ISBN

0672317435



13 Appendix B: xSP Solution Architecture

Figure 5. Major components of xSP solution architecture.

13.1 xSP Services 13.1.1 Service Creation13.1.2 Enrollment13.1.3 Subscription13.1.4 Provisioning13.1.5 SLA

13.2 BlueBiz Design Points13.2.1 Metering 13.2.1.1 Type

Response time tbd

13.2.1.2 Location

Edge of network



Enterprise-wide tbd

13.2.2 Gateway Support Web Services Gateway (WSGW) Other None

13.2.3 Web services support Document style RPC style

13.2.4 SLA Levels Content

13.2.5 SLM Internal functions External functions Interfaces

13.2.6 Service Catalog13.2.6.1 Storage model

Relational model Native XML model

13.2.6.2 WSLA13.2.6.2.1 Schema Definition

Proposed SPEC <spell out> “Roll-Your-Own”

13.2.6.2.2 Binding

Standard (SOAP/HTTP/MIME) Additional (EJB/CORBA, etc.) Abstracted (e.g.WSIF)

13.2.7 WSDL – binding Standard (SOAP/HTTP/MIME) Additional (EJB/CORBA, etc.) Abstracted (e.g.WSIF)



13.2.8 Portal – User Interface13.2.8.1 “Roll-Your-Own”

13.2.8.2 WebSphere Portal Server

Portlets Portlets with Web services

13.3 Web Services: supported service flows13.3.1 Web Services Gateway13.3.1.1 Usage

One point of entry for Web service calls Start/stop Web service calls Generate metering events

13.3.2 General-Purpose Web Services General-purpose Web services, implemented as either Java classes or Enterprise Java Beans and packaged as SOAP-enabled J2EE Enterprise Applications (EARs) can run on WebSphere. Generally speaking, Web services created in this fashion are RPC-style (as opposed to a document-style).

13.3.2.1 Java Class Web Services

Gateway interactions….

13.3.2.2 EJB Web Services


13.3.2.3 SOAP/HTTP Web Services


13.3.3 Web Services with Crossworlds13.3.3.1 SOAP/HTTP – CrossWorlds Collaboration Services

Web services interfacing Crossworlds hosted collaboration is a variant of 12.2.2.3. CrossWorlds provides a Java proxy class, a WSDL to interface with the Proxy along with XML schema definitions. The Schema definitions describe the message required to trigger the collaboration. Creation and deployment steps differ from the general-purpose web services. Additionally, CrossWorlds Web services are deployed as document-style web services.

13.3.3.2 EJB/Resource Adapter – CrossWorlds Collaboration Services

Web services that interface to CrossWorlds-hosted collaborations could be extended to support an EJB service implementation. The current Web Services Generation Utility that is



delivered with CrossWorlds does not generate EJB service bindings. This type of adapter could provide RPC-like bindings.

END OF DOCUMENT


High Level Design for CrossWorlds: Service Level ...web.mit.edu/noto/ibm/ibm/9237.3.doc · Web...

Documents

Transcript of High Level Design for CrossWorlds: Service Level ...web.mit.edu/noto/ibm/ibm/9237.3.doc · Web...