2012 - Wsrr Quick Start-final

1

Kevin Postreich,

IBM Software Services for WebSphere

2012A: Quick Start with WSRR

2

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

3 3

Today’s Agenda

Goals / Activities for a Simple Governance Solution You’ve bought WSRR, Now What??? 1

2 SOA Governance And the WSRR Governance Enablement profile (GEP)

4 Prescribed Lifecycle Simplifications

5 WSRR 7.5 Features for completing the configuration • Configuring the User Interface by role (Business Space) • Authoring governance policies (WSRR Studio)

3 Prescribed Business Model Simplifications

7 Moving to Run-Time Governance • Recommended Practices

W ISSW Fast Path Offering • Enabling SOA Governance for quick Return in Investment

4 4

Today’s Agenda

Goals / Activities for a Simple Governance Solution You‟ve bought WSRR, Now What??? 1







5 5

Today’s Agenda








6 6

Today’s Agenda








7 7

Today’s Agenda








8 8

Today’s Agenda







W ISSW Fast Path Offering • Guided approach for enabling SOA Governance

6

9 9

Today’s Agenda








6

1

0 1

0

Service and Asset

Development Service Deployment

SOA Management

Service Discovery Service Development Lifecycle

Runtime Repository Runtime Service Discovery

Operational Efficiency & Resilience

Configuration Data Discovery

Managing change

Rational

Asset Manager

WebSphere

Service Registry

& Repository (WSRR)

Tivoli Change and

Configuration Management

DB (CCMDB)

IBMs End-to-End SOA Governance Strategy

SOA Monitoring Monitoring service endpoints

Emitting events or situations

Tivoli ITCAM for SOA

Sophisticated and robust SOA governance strategy

1

1

About this Presentation

Identify areas where the WSRR Governance Enablement Profile

(GEP) is often simplified

– Where customers do not require the sophistication the GEP offers Out of

the box.

– Where there is a desire to quickly provision governed service meta-data

for production

Although not absolutely required for this presentation

– It is beneficial if you have some familiarity with a typical WSRR topology

– It is beneficial if you have some familiarity with the GEP

GEP related documentation

– WSRR v7.0 Infocenter

http://publib.boulder.ibm.com/infocenter/sr/v7r0/index.jsp

– Redbook: Service Lifecycle Governance with WSRR

http://www.redbooks.ibm.com/abstracts/sg247793.html

1

2

Goals for a simple governance process

Define activities to efficiently enable SOA Governance that is

consumable and implementable

Convey the main points for prescriptive recommendations to

quickly deploy a WSRR based solution

Define a simplified governance process in order to quickly

provision new services

– Minimize the number of business model objects and simplify lifecycles

The full scope of the changes required to make these

recommendations operational is not detailed, but is discussed

– Author governance policies in WSRR Studio

– UI Customization in Business Space

– With WSRR 7.5, these tasks are greatly simplified

Typical WSRR Topology From Design-Time to Run-Time

1

3

promotion

Promotion

config

Governance

WSRR

ESB ESB ESB

Development/QA

WSRR

Performance

WSRR

Production

WSRR

Online:dev Online:test Online:prod

Design-Time

Run-Time

SOA Governance Checkpoints for Compliance:

1

4

• Compliance check points ensure the service meta-data and artifacts

comply with the standards in the governance framework

• Each check point process defines the different documentation required for

that review

Is the review document available and complete?

Does the service pass the design guidelines?

Is the service really needed?

1

5

1

5

Today’s Agenda








1

6

WSRR and the Governance enablement profile

The GEP enables you to define and manage services in your SOA

environment

– Business models

– Governance lifecycles

– Governance roles

– Governance policies

The GEP implements recommended Practices for SOA Governance

– Addresses a variety of SOA governance concerns

– Such as: Service Identification, Service versioning, Service subscriptions,

Endpoint management

Starting with the GEP is a recommended practice for implementing SOA

Governance with WSRR.

– The GEP is fully customizable to suit specific customer requirements

– We will discuss some prescriptive recommendations for quickly enabling a

simplified SOA Governance process

16

1

7

GEP Business Models

Business Models (As visualized in WSRR Studio)

– The GEP models provide the entities that you need to:

• define services in your SOA environment

• manage services from initial specification through deployment in

production.

– For each type of entity, the models define:

17

• Relationships with other

entities or documents

• The properties specific to

that entity type

• Examples:

• Business Service

• Service Endpoint

1

8

18

GEP Business Model

Derived Logical Objects Auto generated

Service Subscription

Service Versioning

Qualities of service

Endpoint Management

Service Identification

Temperature Converter

Temperature Converter Version 1.1

Staging Environment http://staging production Environment

http://prod

Weather Application QoS forVersion 1.1

GEP Lifecycles

1

9

Lifecycle Governed entity Governed entity Governed entity

Capability Lifecycle Business Application

Business Process Business Service

SOA Lifecycle Application Version

Process Version Service Version

SLD Lifecycle Service Level Definition

SLA Lifecycle Service Level Agreement

Endpoint Lifecycle Endpoint

Asset Lifecycle Service Interface Specification

Schema Specification

Document of Understanding

Lifecycles provide governance checkpoints in SOA governance

8 different lifecycles shipped as part of the profile to support the

various new business modelled object types • We will focus recommendations for the most commonly used lifecycles

GEP Lifecycle for Service Endpoints

2

0

• Service Endpoint Lifecycle (As visualized in WSRR Studio)

2

1

2

1

Today’s Agenda








2

2

Activities to efficiently enable SOA Governance

1. Determine the information that is required to support the governance framework

and use case scenarios

– create a business model to represent the information within WSRR

2. Analyze multi-role interaction with the information and define a set of lifecycles

that support the coordination of that interaction.

– RACI (responsible, accountable, consulted and informed) charts are useful here

– Swim-lanes can also be useful for analyzing role interaction

3. Define Governance policies that enforce gate conditions on the transitions in

the lifecycle

4. Develop and deploy Governance plug-ins to enforce policies that cannot be

enforced via WSRR Governance Policies

5. Configure transition and CRUD authority by user role.

6. Configure the User Interface for your governance roles.

To use WSRR effectively in the Governance of SOA metadata, several factors must be addressed.

TIP: Develop a Technical Specification document before implementing the changes in WSRR. Include information from these topical areas.

2

3

23

WSRR Studio: Development environment

WSRR Studio is the development environment for SOA Governance profiles

– Eclipse based environment for creating and manipulating the content of custom

configuration profiles

• Develop business models

• Develop Lifecycles

• Author Governance policies

• Develop Named Queries

• Define Roles and Permissions

• Import and export WSRR configuration profiles

WSRR Studio is installed via the IBM Installation Manager

– Included in the WSRR Installation media

Integrates with a variety of source code control systems

– Install the eclipse plug-in provided by your Source Code Control vendor

WSRR Studio cannot be installed as a plug-in to an existing Eclipse

installation.

(Studio) Create a New Configuration Profile Project

2

4

24

WSRR Studio is the development environment for customizing the SOA Governance process

To manipulate a WSRR Business Model in WSRR Studio, a configuration project must be created

1. New WSRR configuration project

– From “File->New” menu or “New Project” wizard

2. Complete the new WSRR configuration project wizard

Select a configuration profile as a template

– Governance Enablement Profile -WSRR v7.0

2

5

GEP Models and Lifecycle Diagrams in Studio

25

WSRR Business Capability Model

Service Endpoint Lifecycle

2

6

26

GEP Business Model Simplifications: Conceptual view

Service Subscription

Service Versioning

Qualities of service

Endpoint Management

Service Identification

1 to 1 relationship

Assume 1-1 relationship between Service Version and SLD

2

7

Service Versions are defined to

offer multiple Service Levels

which addresses complexity that

most customers don‟t need today.

Govern Service Version and SLD in Single lifecycle

2

8

This simplification effectively merges SLDs and

Service Versions into a single 2-part entity that

can be created in a single operation* and

governed in a single lifecycle.

* WSRR configuration can accomplish the simultaneous creation to these objects with the

Configurable Modifier.

2

9

29

Configurable Modifier: Automated Service Metadata creation

• The configurable modifier is a plug-in to have WSRR create, modify, or delete objects automatically, in response to a user operation

• Example: When a new Capability Version is created, a corresponding SLD can be created and placed in the same lifecycle.

_ Required for modification on previous slide

• Allows modifiers to be authored using XML configuration

• Reduces the requirement to write custom plug-ins (Java)

• The Configurable Modifier is invoked as a WSRR modifier plug-in.

• Run when the modification properties configuration item specifies the

Configurable Modifier class

modifiers=com.ibm.sr.config.modifier.ConfigurableModifier

3

0

Configurable Modifier: Triggers and Actions

Triggers identify events that need to execute automatic behavior

– Each trigger identifies an event (a registry action + a target matching XPath)

– Triggering actions can be any of Create, Update, Delete, Transition, Make Governable, and Remove Governance.

– Example Trigger Event:

– Create a new Service Version

Actions are the tasks that are done when a trigger fires

– Actions can:

• be any Create, Update, Delete, Transition, Make Governable, Remove Governance events

• be reused from one trigger to another

– Example Actions Tasks:

– Create the SLD

– Associate it to the Service Version

– Assign it to the SOA governance Lifecycle

30

Eliminate DOUs (Document of Understanding)

3

1

• DOUs represent a logical dependency (agreement) between a

consumer and a provider.

• This same relationship is represented by a Service Level

Agreement (SLA).

• SLA‟s also represent a run-time dependency between a

consumer and provider.

Eliminate DOU’s - continued

3

2

Service

Consumer

Service

Provider

• Eliminates complexity and integrity

checking concerns

• Reduces steps a human has to do to

register a service consumer

dependency.

3

3

3

3

Today’s Agenda








The GEP Lifecycles - Recommendations

3

4

3

4

Capability Lifecycle

SLA Lifecycle

Endpoint Lifecycle

SOA Lifecycle

Version Lifecycle

Entity Lifecycle

Asset Lifecycle

SLD Lifecycle

Unchanged

Simplified

Not Used

New (Simple)

Not Used

Business Capability

Unchanged (SLA) Service Level Agreement

Unchanged Endpoint

Service Version

Application & Process Version (Register Service Consumers)

New (Simple) XML Schema

DOU, Interface Specification, Schema Specification

SLD (Service Level Definition)

Capability Lifecycle

3

5

Capability Lifecycle remained

unchanged from the out of the box

configuration.

SLA Lifecycle

3

6

SLA Lifecycle remained

unchanged from the out

of the box configuration.

Endpoint Lifecycle

3

7

Endpoint Lifecycle remained

unchanged from the out of the

box configuration.

3

8

Introduce a Lifecycle for Application Versions

Provide simple lifecycle management for applications registered as service consumers

Requires Less governance rigor than Service versions

3

9

Introduce a Lifecycle for Application Versions

Introduce a Lifecycle for XML Schemas

4

0

Provide simple lifecycle management for XSD

Schemas

To avoid the need to load the same XSD into WSRR

several times

Very simple, one approval step

Lifecycle can be applied to the XSD as it is loaded into

the registry

Introduce a Lifecycle for XML Schemas

4

1

Simplifying Service Version (SOA) Lifecycle: Version Identification and Scoping

4

2

The identification portion of the Lifecycle

for Service Versions will remain

unchanged.

Simplifying Service Version (SOA) Lifecycle: Remove Version Planning 4

3

Planning states may be redundant to other project management activities

already in place

Remove Planning states to simplify the lifecycle and move from scoped directly

to specification review – Implies that planning becomes a Project Management activity outside this lifecycle

Simplifying the Service Version (SOA) Lifecycle: Remove Service Deployment states

4

4

<<LifeCycleState>>

Specification Review

Eliminate „Assemble‟ and „Deploy‟

states from Capability Version

– Decouples the Service Deployment

activities from the SOA lifecycle

– Reinforces the separation of concerns

between Services Components and

Service Deployments

– Simplifies the lifecycle

Simplifying the Service Version (SOA) Lifecycle: Version Specification

4

5

On-line endpoints indicates the service version is deployed and available in an environment

4

6

Promotes to run-time

Promotes to run-time

Simplifying the Service Version (SOA) Lifecycle: Version Management

4

7

• Management phase of the Capability Version Lifecycle is used to deprecate and retire service versions

Simplifying the Service Version (SOA) Lifecycle: Final

4

8

The resulting „SOA‟ lifecycle:

– Contains only 7 non-terminal states

– Eliminates the need for the 7 states in the SLD

– Significantly reduces the complexity of introducing Service Versions.

– Introduces the need for an additional „re-promote’ transition to

refresh updated meta-data and relationships to the run-time

registries.

4

9

New SOA Lifecycle

Exporting a Modified WSRR Configuration Profile

5

0

50

1. Select File Export. The

Export pane is displayed.

4. Select the Configuration Project

from the drop down list.

5. Enter the directory path of the

target directory.

6. Click Finish.

2. In the Export pane, expand WebSphere

Service Registry and Repository (WSRR).

3. Click.WSRR Configuration Profile

5

1

51

Import the Generated Configuration Profile

1. Import the exported profile into WSRR

2. Activate the profile

Lifecycles and their governed entity (Updated)

5

2

Lifecycle Governed entity Governed entity Governed entity

Capability Lifecycle Business Application Business Process Business Service

SOA Lifecycle Service Version Service Level Definition

Version Lifecycle Application Version

SLA Lifecycle Service Level Agreement

Endpoint Lifecycle Endpoint

Entity Lifecycle XSD Schema

Lifecycle # States: Original

# States: Simplified

Capability Lifecycle 3 3

SOA Lifecycle 15 5

Application Version Lifecycle 15 3

SLA Lifecycle 4 4

Endpoint Lifecycle 2 2

Entity Lifecycle 0 3

SLD Lifecycle 5 0

Asset Lifecycle 7 0

5

3

5

3

Today’s Agenda








5

5

5

5

Configure the Governance Process to Fit the Need New and Enhance WSRR Studio Capabilities

Start with a prescriptive

recommend practice

governance profile

Drag and drop to build

out or extend metadata

model and lifecycles

Click to assign lifecycles

to entities

Click to assign policies to

lifecycles and entities in

the model

Click to deploy

governance profile

5

6

5

6

Easily Configure Experience Based On User’s Role New and Enhance Business Space Widgets for WSRR

WSRR V7.5 Provide Two New

Role based Business Space

templates

– Registry for Business

– SOA Governance

WSRR v7.5 provides the

following configurable widgets

– Search

– Collection

– Details

– Navigation

– Impact Analysis

– Actions

5

7

5

7

Today’s Agenda







W ISSW Fast Path Offering • Guided approach for enabling SOA Governance

6

5

9

IBM WebSphere Services for SOA Governance

A Prescriptive approach for

implementing SOA governance

A Well-Defined SOA governance

process allowing you to quickly achieve

return on your investment

Recommended practices from field

proven implementations For more information, visit:

ibm.com/websphere/serviceszone/

Fast Path for SOA Governance Enablement

IBM has structured this offering to ensure consistent delivery of the following outcomes:

Fast Path Offering Highlights

6

0

For customers that desire prescriptive guidance to enable an SOA

Governance process, based on best practices and standards

Planning Workshop

Review current development processes

Hands on with WSRR Studio

– Customize the Governance Enablement Profile

Deploy and Test the governance process

Training of the prescribed governance process

6

1

6

1

Today’s Agenda








6

6

2

Recommended Practices

Design-time to Run-time WSRR Deployment Topology

Contract Management

Service Versioning and decoupled endpoint selection

62

Typical WSRR Topology: From Design-Time to Run-Time

6

3

promotion

Promotion

config

Governance

WSRR

ESB ESB ESB

Development/QA

WSRR

Performance

WSRR

Production

WSRR

Online:dev Online:test Online:prod

Design-Time

Run-Time

6

4

64

(6) Message is transformed and routed to the selected endpoint.

Message

(1) A Message is received

ESB Mediation

(2) Invokes a selection mediation.

Publish Find Enrich Govern Manage

WebSphere Service Registry and Repository

(3) Send request for information

(4) Retrieves candidate providers information

Message

(5) Executes matching algorithm to identify the provider service for requestor service

Message

Service

Dynamic/Late Binding (Run Time)

ESB Mediation dynamically looks up a specific service endpoint at run time using service information and service

characteristics stored in WSRR

Recommended Practices –Contract management

6

5

65

Provides

Consumes

Subscribed

Service

Consumer invokes subscribed service

including (Consumer ID and Context ID) in the

header

Mediation extracts Consumer ID and Context ID, then looks up the SLD it supports to see if any SLAs have a matching

ID.

If a valid SLA is found, the mediation routes to an

endpoint that meets the SLA. If no SLA is found the

interaction is rejected.

Recommended Practices – Service Versioning

6

6

66

Provides

Compatible SLDs

6

7

6

7

6

8

We love your Feedback!

Don‟t forget to submit your Impact session and speaker

feedback! Your feedback is very important to us, we use it to

improve our conference for you next year.

Go to impactsmartsite.com from your mobile device

From the Impact 2011 Online Conference Guide;

– Select Agenda

– Navigate to the session you want to give feedback on

– Select the session or speaker feedback links

– Submit your feedback

6

9

© IBM Corporation 2011. All Rights Reserved. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Copyright and Trademarks

2012 - Wsrr Quick Start-final

Documents

Transcript of 2012 - Wsrr Quick Start-final