Guide to the IBM CrossWorlds Connector for Web Services - MIT

bugenigmaSoftware and s/w Development

Oct 30, 2013 (3 years and 10 months ago)

107 views


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 Avenue

RTP, NC 27709


E
-
mail:

cutlip@us.ibm.com

Telephone:

(919) 486
-
1178

Internal Telephone:

8
-
526
-
1178

Latest Revision:

31 October 2013

Next revision planned:

03 June 2002






D
ocument Control

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
3

of
34


Document Control

Notes

The master copy of this document (BlueBiz_SLMandWebServices.do
c) 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.

Authors

Kristin Firth

Neeraj Joshi

Malia Morley

Matt Noto
widigdo

(Rob Cutlip)




Approval

Date

Name

Title


Pam Durham

Extreme Blue: Executive Representative

Review

Date

Name

Title


Brent A. Miller

Extreme Blue: Lead Technical Mentor


Richard Franck

Extreme Blue: Technical Mentor


Gary McGibbon

Extreme Blu
e: Lead Business Mentor


Marcel Kinard

Extreme Blue Technical Liaison


John Graham

Extreme Blue Technical Liaison


Rob Cutlip

Extreme Blue: Technical Mentor

Change History

Date

Amended by

Details of amendment

12 April 2002

rrc

0.1 Initial draft

9 M
ay 2002

rrc

0.3 draft

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
4

of
34





CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
5

of
34


1

Table of Contents


Document Control
................................
................................
................................
.................

3

Notes
................................
................................
................................
................................
.....

3

Approval

................................
................................
................................
..............................

3

Review

................................
................................
................................
................................
..

3

Change History

................................
................................
................................
..................

3

1

Table of Contents Introduction

................................
................................
.................

5

1

Introduction

................................
................................
................................
....................

9

1.1

PURPOSE OF THIS DOCUMENT

................................
................................
.......

9

1.2

BlueBiz Project Deliverables
................................
................................
..............

9

1.3

How to make changes to the document

................................
.........................

9

2

“BlueBiz” Architectural Overview

................................
................................
..........

10

2.1

Architectural Overview


Service Level Management

..............................

10

2.2

High Level Flows

................................
................................
................................
.

11

2.2.1

Operational Flows

................................
................................
.........................

11

2.2.2

Management Flows
................................
................................
.......................

12

2.3

Repositories

................................
................................
................................
.........

13

2.3.1

Required

................................
................................
................................
.........

13

2.3.2

Standard and required.
................................
................................
.................

13

2.4

Services

................................
................................
................................
.................

14

2.4.1

Portal Services
................................
................................
...............................

14

2.4.2

SLM Services

................................
................................
................................
.

14

2.4.3

CrossWorlds Services

................................
................................
..................

14

3

BlueBiz Design Overview
................................
................................
..........................

15

3.1

Scope
................................
................................
................................
......................

15

3.2

Objectives

................................
................................
................................
.............

15

3.3

Components Overview

................................
................................
......................

15

3
.3.1

Applications

................................
................................
................................
....

15

3.3.2

Business Processes
................................
................................
......................

15

3.3.3

Repositories:

................................
................................
................................
..

15

3.3.
4

Generic Services:

................................
................................
..........................

15

3.3.5

SLM Services

................................
................................
................................
.

15

3.3.6

TBD
................................
................................
................................
..................

16

4

“BlueBiz” Compon
ent(s)
................................
................................
...........................

17

4.1

Objectives addressed by Web Service
-
CW component

...........................

17

4.1.1

Synchronous Inbound Call (Web Service) to a CW Collaboration

........

17

4.1.2

High Level Sequence
................................
................................
....................

17

4.1.3

Boundary Considerations
................................
................................
.............

18

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
6

of
34


4.1.4

Security

Considerations

................................
................................
...............

18

4.1.5

Performance Considerations

................................
................................
.......

18

4.1.6

Expected Consumers of this Component

................................
..................

18

4.1.7

Assumptions and Dependencies:

................................
...............................

18

4.1.8

Issues:

................................
................................
................................
.............

19

4.2

Objective of Component “B”

................................
................................
...........

20

4.2.1

Function

................................
................................
................................
..........

20

4.2.2

High Level Sequence Diagram

................................
................................
...

20

4.2.3

Boundary Considerations
................................
................................
.............

20

4.2.4

Security Considerations

................................
................................
...............

20

4.2.5

Expected Consumers of Component

................................
.........................

20

4.2.6

Assum
ptions and Dependencies:

................................
...............................

20

4.2.7

Issues:

................................
................................
................................
.............

20

4.3

Objective of Component “N”

................................
................................
..........

20

4.3.1

Function

................................
................................
................................
..........

20

4.3.2

High Level Sequence Diagram

................................
................................
...

20

4.3.3

Boundary Considerations
................................
................................
.............

20

4.3.4

Security Considerations

................................
................................
...............

20

4.3.5

Expected Consumers of Component

................................
.........................

20

4.3.6

Assumptions and Dependencies:

................................
...............................

20

4.3.7

Issues:

................................
................................
................................
.............

20

5

Hardware and Software Component Characteristics

................................
........

21

5.1

Operation
al Environment

................................
................................
..................

21

5.1.1

Required Hardware

................................
................................
.......................

21

5.1.2

Required Software

................................
................................
........................

21

5.1.
3

Optional and Available Software
................................
................................
.

21

5.1.4

Optional AlphaWorks Technologies

................................
...........................

21

5.1.5

Non
-
Supported Hardware and Software

................................
...................

22

5.2

System Resources

................................
................................
..............................

22

5.2.1

Restrictions
................................
................................
................................
.....

22

5.2.2

Estimates

................................
................................
................................
........

22

5.3

Migration Characteristics
................................
................................
..................

22

5.3.1

Incompatibilities duri ng Migration

................................
...............................

22

5.3.2

Migration Aids

................................
................................
................................

22

5.4

Security

................................
................................
................................
..................

22

5.4.1

Securing Individual Services: Overview

................................
....................

22

5.4.2

Non
-
repudiation

................................
................................
.............................

23

5.4.3

Authori zation

................................
................................
................................
..

23

5.4.4

Authentication

................................
................................
................................

23

5.5

Performanc
e

................................
................................
................................
.........

23

5.5.1

Response Time
................................
................................
..............................

23

5.5.2

Throughput

................................
................................
................................
.....

23

5.6

Capacities
................................
................................
................................
..............

23

5.7

Reliability, Availability, and Serviceability (RAS)

................................
.......

23

5.7.1

Messages

................................
................................
................................
.......

23

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
7

of
34


5.7.2

Tra
cing

................................
................................
................................
............

23

5.8

Standards Compliance

................................
................................
......................

24

5.8.1

IBM
................................
................................
................................
...................

24

5.8.2

International
................................
................................
................................
....

24

5.8.3

Domestic

................................
................................
................................
.........

24

5.8.4

Industry

................................
................................
................................
...........

24

5.9

World Trade Considerations

................................
................................
............

24

5.9.1

National Language Support

................................
................................
.........

24

5.9.2

Legal Constraints

................................
................................
..........................

24

5.9.3

Import/Export Rest
rictions
................................
................................
............

24

5.9.4

Certifications

................................
................................
................................
..

24

5.10

Usability Characteristics

................................
................................
...................

24

5.10.1

Service Level Management


Administrative Access
..............................

24

5.10.2

Service Level Management


Customer Access

................................
.....

24

5.11

Publications

................................
................................
................................
..........

24

5.12

Packaging
................................
................................
................................
..............

24

6

Design

................................
................................
................................
............................

25

6.1

Technical Introduction and Overview
................................
............................

25

6.2

“BLUEBIZ” Service Flows

................................
................................
................

25

6.2.1

Internal

................................
................................
................................
............

25

6.2.2

Outgoing

................................
................................
................................
.........

25

6.2.3

Incoming

................................
................................
................................
.........

25

7

External Interfaces

................................
................................
................................
......

26

8

Internal Interfaces

................................
................................
................................
.......

27

9

Installation / Configuration / Administration

................................
.......................

28

9.1

Installation
................................
................................
................................
.............

28

9.1.1

WebSphere Administration

................................
................................
..........

28

9.1.2

CrossWorlds Administration

................................
................................
........

28

9.1.3

Service Catalog Admi nistration

................................
................................
...

28

9.2

Configuration

................................
................................
................................
.......

28

9.2.1

WebSphere Administrator

................................
................................
............

28

9.2.2

Service Catalog Admi nistrator
................................
................................
.....

28

9.2.3

CrossWorlds Administrator

................................
................................
..........

28

9.3

Starting and Stopping the System

................................
................................
.

29

9.4

Test Considerations

................................
................................
...........................

29

10

Appendix A: Recommended References and Documentation

...................

30

10.1

Product Documentation

................................
................................
....................

30

10.1
.1

CrossWorlds
................................
................................
................................
...

30

10.1.2

WebSphere Studio Application Development
................................
...........

30

10.1.3

Ipedo
................................
................................
................................
................

30

10.2

Associated and Supporting Documentation

................................
...............

30

10.2.1

IBM Redbooks and RedPieces.

................................
................................
..

30

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
8

of
34


10.2.2

Other References

................................
................................
..........................

31

11

Appendix B: xSP Solution Architecture
................................
............................

32

11.1

xSP Services

................................
................................
................................
........

32

11.1.1

Service Creation

................................
................................
............................

32

11.1.2

Enrollment

................................
................................
................................
......

32

11.1.3

Subscription
................................
................................
................................
....

32

11.1.4

Provisioning

................................
................................
................................
....

32

11.1.5

SLA

................................
................................
................................
..................

32

11.2

“BlueBiz” Design Points

................................
................................
...................

32

11.2.1

Metering

................................
................................
................................
..........

32

11.2.2

Gateway Support
................................
................................
...........................

33

11.2.3

Web services support

................................
................................
...................

33

11.2.4

SLA

................................
................................
................................
..................

33

11.2.5

SLM

................................
................................
................................
.................

33

11.2.6

Service Catalog

................................
................................
.............................

33

11.2.7

WSDL


binding
................................
................................
.............................

33

11.2.8

Portal


User Interface
................................
................................
..................

34

11.3

Web Services: supported service flows

................................
......................

34

11.3.1

Web Services Gateway

................................
................................
................

34

11.3.2

General Purpose Web Services
................................
................................
..

34

11.3.3

Web Services with Crossworlds
................................
................................
..

34

END OF DOCUMENT

................................
................................
................................
......

35

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
9

of
34


2

Introduction

This 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 doc
u
ment also contains information useful to technical support,
sy
stem test, inform
a
tion development, release management and pro
d
uct planning staff.


2.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.



2.2

BlueBiz Project Deliverabl
es

The 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.do
c).




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 servi
ce 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
s
oftware.

.

2.3

How to make changes to the document

Requests 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 r
eviewers and approvers (or their replacements or delegates) for
a
p
proval. 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 m
i
nor chang
es for the sake of approver efficiency. Once approved, the new version of the
document becomes available for distribution.



CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
10

of
34


3

“BlueBiz” Architectural Overview

An architectural overview of the BlueBiz problem space is presented in this section. The
archi
tectural 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.




3.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 ent
erprise 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, administrat
ion 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.



CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
11

of
34



3.1.1

Archi
tectural 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.


3.2

High Level Flows

3.2.1

Operational Flows

3.2.1.1

Inbound Web Service call to CrossWorlds Collaboration.



Figure
2
.
Operational Flo
w to be monitored

3.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:

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
12

of
34




at the Internet boundary



within the Web server suppor
ting 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.

3.2.1.3

Integration of SLM modules with ex
isting IBM (service level) software

3.2.2

Management Flows

3.2.2.1

Service Level Management administration through portal


Figure
3
.
Administration through Portal

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
13

of
34



3.2.2.2

Service Level Management
-

Client access through portal


Figure
4
.
Client services through Portal

3.3

Repositories

3.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 XQuer
y
access.



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

3.3.2

Standard and required.



WebSphere Application Server configuration database



IBM UDDI registry



IBM Crossworlds repository

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
14

of
34




3.4

Services

3.4.1

Portal Services

Required services for the

portal include:



X



Y



Z


3.4.2

SLM Services

The SLM services…

3.4.3

CrossWorlds Services

The CrossWorlds services…

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
15

of
34


4

BlueBiz Design Overview


4.1

Scope

4.2

Objectives

4.3

Components Overview

4.3.1

Applications



tbd



tbd



tbd


4.3.2

Business Processes



CrossWorlds Collaboration: ATP



tbd


4.3.3

Repositorie
s:



CrossWorlds repository



Service catalog implemented on native XML database



UDDI Registry



WebSphere configuration database on DB2



tbd


4.3.4

Generic Services:



Authorization



Billing



Contracts



Web service
-
to
-
CrossWorlds collaboration



Identity



License Management



O
fferings



tbd

4.3.5

SLM Services



Metering



Quality of service (QOS)



Rating



Reporting



Self
-
service



Service catalog



tbd

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
16

of
34



4.3.6

TBD



tbd



tbd



tbd


CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
17

of
34


5

“BlueBiz” Components

5.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.

5.1.1

Synchronous Inbound Call (Web Service) to a Cross
Worlds
Collaboration

Figure 5 details the data synchronization collaboration.



Figure 5 .
Web Service
-
to
-
CrossWorlds Collaboration Flow

5.1.2

High Level Sequence

1.

Web services call originated by enterprise application

2.

SOAP Servlet that resides on a Web service

makes appropriate proxy calls

3.

Proxy calls call the Server Access Interface (SAI) to CrossWorlds

4.

The SAI takes the SOAP message and passes it to a SOAP Data Handler

5.

The SOAP DataHandler uses the appropriate MetaObject to perform SOAP
-
to
-
Business Object con
version.

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
18

of
34


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 SAI

9.

SAI calls the SOAP Data Handler, which converts Business Object(s) to SOAP
object(s)

10.

SOAP message is returned to SAI

11.

SAI sends SOAP return message to SOAP proxy

12.

SOAP proxy sends message to SOAP Servlet

13.

SOAP Servlet

returns message to enterprise application

5.1.3

Boundary Considerations

There 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 gat
eway 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 parti
cipate 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.

5.1.4

Security Considerations




N/A

5.1.5

Performance Con
siderations

N/A


5.1.6

Expected Consumers of this Component



Designers of SLM components



Developers of SLM components



Testers of the BlueBiz solution



SLM monitoring applications

5.1.7

Assumptions and Dependencies:

5.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 ente
rprise 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

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
19

of
34



5.1.7.2

Dependencies



Requires CrossWorlds v 4.1. fo
r 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 components

o

Learning how to create the necessary artifacts (WSDL, Busin
ess Objects,
Meta
-
objects and proxy classes)

o

Learning how to deploy and configure all of these artifacts, including using
WebSphere Application Server

o

Capturing the implementation procedures for building and using this
component



The CrossWorlds Web Service
s Generation Utility with CrossWorlds 4.1 must
ge
n
erate 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


5.1.8

Issues:

5.1.8.1

Compatibilities



tbd

5.1.8.2

Incompat
ibilities



tbd

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
20

of
34


5.2

Objective of Component “B”

5.2.1

Function

5.2.2

High Level Sequence Diagram

5.2.3

Boundary Considerations

5.2.4

Security Considerations

5.2.5

Expected Consumers of Component

5.2.6

Assumptions and Dependencies:

5.2.6.1

Assumptions

5.2.6.2

Dependencies

5.2.7

Issues:

5.2.7.1

Compatibilities

5.2.7.2

Incompatibles

5.3

Obje
ctive of Component “N”

5.3.1

Function

5.3.2

High Level Sequence Diagram

5.3.3

Boundary Considerations

5.3.4

Security Considerations

5.3.5

Expected Consumers of Component

5.3.6

Assumptions and Dependencies:

5.3.6.1

Assumptions

5.3.6.2

Dependencies

5.3.7

Issues:

5.3.7.1

Compatibilities

5.3.7.2

Incompatibles







CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
21

of
34


6

Hardware and So
ftware Component Characteristics

6.1

Operational Environment

Design, 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 wi
ll differ from the one described here, based
on non
-
functional requirements.

6.1.1

Required Hardware



IBM xSeries 300



IBM Thinkpad T20



Ethernet network


6.1.2

Required Software



WebSphere Application Server v4.0+



WebSphere UDDI Registry v1.1



CrossWorlds: v4.1.1

o

DB2 v7
.2 support

o

Web Services support

o

Collaboration support for known business process

o

Connector for Web services

o

Web Services Generation Utility

o

CrossWorlds development tooling:



Process Designer



Test Connector



Map Designer



Relationship Designer



Connector Develo
pment Kit



Websphere Studio Application Developer v4.02



DB2 v7.2



Ipedo v3.1 native XML database



TBD


6.1.3

Optional and Available Software



WebSphere 5.0 (beta)



WebSphere Portal Server



Firewall software and/or appliances



IBM WebSphere Edge Server



IBM Policy Dire
ctor



IBM SecureWay LDAP V 4.2.1



Oracle 8.1.7



Tivoli Service Level Advisor v1.1



TBD

6.1.4

Optional AlphaWorks Technologies

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
22

of
34



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



Web Services Gateway



Web Services Invocati
on Framework



Web Services Hosting Technology



Web Services Tool Kit



XML Schema Quality Checker



Business Explorer for Web Services



Servlet Manager



XML Registry



TBD


6.1.5

Non
-
Supported Hardware and Software


N/A


6.2

System Resources

6.2.1

Restrictions

6.2.2

Estimates

The individ
ual released products in the product stack provide their own documented resource
estimates.





6.3

Migration Characteristics

6.3.1

Incompatibilities during Migration

N/A

6.3.2

Migration Aids

N/A


6.4

Security

6.4.1

Securing Individual Services: Overview


CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
23

of
34


6.4.2

Non
-
repudiation

6.4.3

Authoriz
ation

6.4.4

Authentication

6.4.4.1

Privacy

6.5

Performance

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

6.5.1

Response Time

N/A

6.5.2

Throughput

N/A


6.6

Capacities

Capacity/throughput has not been considered at this time for the BlueBiz co
mponents.


6.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.


.

6.7.1

Messages

Exceptions are logged in WebSphere and CrossWorlds, where appropriate.

6.7.2

Tracing

WebSphere Application Server trac
ing is used. CrossWorlds tracing is also used.


CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
24

of
34


6.8

Standards Compliance

6.8.1

IBM

N/A

6.8.2

International

N/A

6.8.3

Domestic

N/A

6.8.4

Industry

N/A

6.9


World Trade Considerations

6.9.1

National Language Support

N/A

6.9.2

Legal Constraints

N/A

6.9.3

Import/Export Restrictions

N/A

6.9.4

Certifications

N/A

6.10


Usab
ility Characteristics

6.10.1

Service Level Management


Administrative Access



Service catalog access function



UDDI Registry access function

6.10.2

Service Level Management


Customer Access



Registration functions



Offering catalog functions



Subscribed services functions



Reporting functions


6.11


Publications

The 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.

6.12


Packaging

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
25

of
34


7

Design

7.1

Technical Introduction and Overview

7.2

“BlueBiz” Service Flows

7.2.1

Internal

7.2.2

Outgoing

7.2.3

Incoming

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
26

of
34


8

External Interfaces

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
27

of
34


9

Internal Interfaces

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
28

of
34


10

Installation / Configuration / Administration

10.1


Installation

Installation of BlueBiz Web se
rvices
-
related artifacts will consist of several tasks
performed by people with different roles, as described next.

10.1.1

WebSphere Administration

A We
b
Sphere administrator will deploy this J2EE enterprise application (EAR) into
WebSphere.

10.1.2

CrossWorlds Administr
ation

BlueBiz will include Meta Object definitions and SOAP Connector configuration
info
r
mation that can be deployed into the CrossWorlds ICS using a CrossWorlds
4.1.1 project.

10.1.3

Service Catalog Administration

The BlueBiz service catalog will be updated wit
h WSLA definitions and WSDL
definition updates will be made to the appropriate UDDI registry.


10.2


Configuration

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

10.2.1

Web
Sphere Administrator

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

10.2.2

Service Catalog Administrator

The Service Catalog administrator must generate the appropriate WSAL definitions
and add th
em to the service catalog and authorize access the service catalog.


10.2.3

CrossWorlds Administrator

The CrossWorlds SOAP Connector must be configured to support collaborations that
are called outbound through the Web services Gateway from within a collaboratio
n.
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.


CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
29

of
34


10.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).


10.4

Test Considerations

Te
sting 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 ser
vice 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 cons
umer registration, offering enrollment and reporting through a
portal


CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
30

of
34


11


Appendix A: Recommended References and
Documentation

11.1

Product Documentation

11.1.1

CrossWorlds



CrossWorlds Glossary



Administration Guide



Installation Guide for Windows



Connector Development G
uide



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

11.1.2

WebSphere Studio Application De
velopment



Online Product Documentation



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



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


11.1.3


Ipedo



Ipedo Developer’s Guide



Ipedo Installation_Administration Guide



Ipedo_Administration Guide



11.2


Associated and S
upporting Documentation

11.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 We
b Services
, SG24
-
6407
-
00 Redbook, published February
-
28
-
2002



CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
31

of
34




11.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
Transac
tion 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 Man
agement 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 Leve
l Management
, Sturm et al, Sams Publishing, ISBN
0672317435


CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
32

of
34


12

Appendix B: xSP Solution Architecture


Figure
5
.
Major components of xSP solution architecture.

12.1


xSP Services

12.1.1

Service Creation

12.1.2

Enrollment

12.1.3

Subscription

12.1.4

Provisioning

12.1.5

SLA

12.2


BlueBiz Design Points

12.2.1

Metering

12.2.1.1

Type



Response time



tbd

12.2.1.2

Location



Edge of network

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
33

of
34




Enterprise
-
wide



tbd

12.2.2

Gateway Support



Web Services Gateway (WSGW)



Other



None

12.2.3

Web services support



Document style



RPC style

12.2.4

SLA



Levels



Content

12.2.5

SLM



Internal functions



External f
unctions



Interfaces


12.2.6

Service Catalog

12.2.6.1

Storage model



Relational model



Native XML model

12.2.6.2

WSLA

12.2.6.2.1

Schema Definition



Proposed SPEC <spell out>



“Roll
-
Your
-
Own”

12.2.6.2.2

Binding



Standard (SOAP/HTTP/MIME)



Additional (EJB/CORBA, etc.)



Abstracted (e.g.WSIF)


12.2.7

WSDL


binding



Stand
ard (SOAP/HTTP/MIME)



Additional (EJB/CORBA, etc.)



Abstracted (e.g.WSIF)

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
34

of
34




12.2.8

Portal


User Interface

12.2.8.1

“Roll
-
Your
-
Own”

12.2.8.2

WebSphere Portal Server



Portlets



Portlets with Web services


12.3


Web Services: supported service flows

12.3.1

Web Services Gateway

12.3.1.1

Usage



One point of
entry for Web service calls



Start/stop Web service calls



Generate metering events

12.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 Applicati
ons (EARs) can run on
WebSphere. Generally speaking, Web services created in this fashion are RPC
-
style (as
opposed to a document
-
style).

12.3.2.1

Java Class Web Services

Gateway interactions….

12.3.2.2

EJB Web Services

Gateway interactions….

12.3.2.3

SOAP/HTTP Web Services

Gatew
ay interactions….

12.3.3

Web Services with Crossworlds

12.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 documen
t
-
style web
services.

12.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

CrossWorl ds: Service Level Management and Web Services”




IBM Confidential

“BlueBiz” Specification

Page
35

of
34


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











END OF DOCUMENT