Introduction to IBM WebSphere Registry and Repository (WSRR) Session 1251 at IBM IMPACT 2014

1. © 2014 IBM Corporation
1251: Service Visibility and
Management with IBM
WebSphere Service Registry
and Repository
Nick Butler – WSRR Architect
Bob Laird – WSRR Product Manager

2. 1
Please Note
IBM’s statements regarding its plans, directions, and intent are subject to change
or withdrawal without notice 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.
Performance is based on measurements and projections using standard IBM
benchmarks in a controlled environment. The actual throughput or performance
that any user will experience will vary depending upon many factors, including
considerations such as the amount of multiprogramming in the user’s job stream,
the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve results
similar to those stated here.

3. 2
Agenda
Overview
Find
Manage
Control
Visualize

4. 3
SOA Strategy
Process Modeling
Services
Portfolio Management
Organizational Change
Human Collaboration
Risk Management
Service Lifecycle
Management
Registry & Repository
Support
Policy Lifecycle
Management
Service Level
Agreements
Change Management
SOA Governance and Service Lifecycle Management
Service Visibility and
Management

5. 4
Ask yourself, How do I…
… manage the
consumers of a
service and the
details of
consumption?
… allow users
across the
enterprise to find
services to aid
Service Reuse?
… identify the
impact of changes
to a shared service?
… eliminate “rogue
services and
consumers” and
ensure control of my
Services?
… administer and
govern runtime
metadata (including
policies and
endpoints) across
my operational
environment?
… manage the
services lifecycle
and retire versions to
recover resources?
… provide a central
place for users to
download service
definitions?
… visualize the
level of consumption
and reuse of my
services?

6. 5
WebSphere Service Registry and Repository

7. 6
Google-style search
Collection filters
Email owner
Service catalog view
Download service definition

8. 7
Service Registry Dashboard
New UI platform, ?, ?,?

9. 8
‘Service Catalog’ View
Simple read-only view for finding services to consume

10. 9
Download Service Definition Documents
Service documents packaged as a ZIP

11. 10
Email Owner
Send an email to the service owner

12. 11
Subscription Support
Easily subscribe to services, in context
Manage subscriptions easily using ‘My Subscriptions’

13. 12
Service lifecycle management
Managing consumers
Managing versions

14. 13
Accounting
Currency Conversion
Service
Why is Service Management Important?
In this example, the accounting department creates a currency conversion service
for their own use.

15. 14
Sales
Order
Fulfilment
Legal
Purchasing
Accounting
Currency Conversion
Service
Why is Service Management Important?
Other departments find out about it, and start using it, without the knowledge of
its owners.

16. 15
Sales
Order
Fulfilment
Legal
Purchasing
Currency Conversion
Service
!
Accounting
Why is Service Management Important?
Over time the workload increases and the service quality suffers.

17. 16
Sales
Order
Fulfilment
Legal
Currency Conversion
Service
Purchasing
Accounting
Why is Service Management Important?
The accounting department add more servers to compensate.

18. 17
Sales
Order
Fulfilment
Legal
Currency Conversion
Service
! ! !
Purchasing
Accounting
Why is Service Management Important?
But eventually these are overloaded too, and they have to withdraw the service.

19. 18
Sales
Order
Fulfilment
Legal
Purchasing
Currency Conversion
Service
Accounting
Why is Service Management Important?
If the apps that use it are important to the business, then the business suffers.

20. 19
Sales
Order
Fulfilment
Legal
Purchasing
Accounting
Currency Conversion
Service
Why is Service Management Important?
Through service management, the accounting department can alleviate this
by keeping track of all the versions of services it has running, and of who is
using them.

21. 20
Business ServiceOrganization
Service Version
Service Level Definition
Service Endpoint
Business Service Organization
Service Version
Service Level Definition
Service Endpoint
Service Level Agreement
Service Provider Service Consumer
WSDL Document WSDL Document
Understand How Services are Consumed

22. 21
Register existing services
Describe the service
Load service definition
from WSDL and XSD
Add information to
make service easier to
find, use and manage,
for example
• Classification
• Owner contact details

23. 22
Manage the Lifecycle of a Service
Manage services through their life from Design to Deployment
Apply approvals at various stages in the lifecycle
Design Develop Deploy

24. 23
Manage the Versions of a Service
Keep a track of what versions are currently active and who is using
them
Actively manage consumers on to newer versions
Remove older versions to free resources and reduce operational costs
v1.1
v2.0
v1.0

25. 24
Email Consumers
Send an email to owners of consuming services

26. 25
Bring Visibility to MQ Applications
Catalog MQ queues in WSRR to
understand what you have
Make controlled changes to MQ
services based on usage by
processes & applications
Apply recommended practices to
govern MQ services

27. 26
Manage metadata across runtime environments
WSRR can store metadata for objects across multiple runtime
environments
• Development, test, production, etc
For example
• Endpoints for each runtime
• Policies specific to each runtime
Manage the promotion of information from one environment to
another
• E.g. promotion from Test to Production

28. 27
Start with a prescriptive recommended practice governance
profile
Extend metadata model and lifecyles
Assign lifecycles to entities
Add assertions to lifecycles and entities
Deploy governance profile directly to WSRR
Configure the Governance Process to Fit

29. 28
WSRR Access Control editor provides guidance for
authoring roles and permissions
Allows for advanced permissions with the specification of
an XPath expression
Click-to-Assign permissions to roles
Easy view for understanding what permissions are
assigned to the various roles
Configure Fine Grain Role Based Security

30. 29
View metrics over all
governance policies in a
selected date range
View individual policy
pass and failure rate
View metrics over all
governance policies in a
selected date range
Determine worst
performing policies and
take action
Analyze and Tune SOA Governance Process

31. 30
Service endpoint protection
Controlling consumption
Endpoint routing

32. 31
Enhance the Connectivity of ESB using WSRR
Integrating WSRR with your ESB allows you use the metadata
retrieved from WSRR when making decisions at runtime
The behaviour of your flow can be modified simply by changing
the metadata in WSRR
Enables your ESB to be more dynamic, more flexible, more
adaptable!
WSRR

33. 32
Usage Patterns
Service Proxy Service Selection Alternate Service
Provider
Service
Transformation
Service Gateway SLA Checking
500
Messages
per second
WLM Policy
Enforcement
File Transfer
Integration

34. 33
Service Transformation with IIB
Extends the service proxy pattern
Introduces transform(s) which allow the interface(s) presented by the ESB to
differ from that of the service provider
Various drivers:
• Not always desirable to expose the interface of a backend service as the
published interface of an enterprise service on the ESB
• Expose a standard interface to a number of semantically equivalent backend
services that have different interfaces
• Transform service requests/responses from one version of a service to another

35. 34
This example starts as before: the accounting department creates a currency
conversion service for their own use.
Accounting
Currency Conversion
Service
Regulating access to services

36. 35
Sales
Order
Fulfilment
Legal
Purchasing
Accounting
Currency Conversion
Service
Regulating Access to Services
Other departments find out about it, and start using it, without the knowledge of
its owners.

37. 36
Sales
Order
Fulfilment
Legal
Purchasing
Accounting
Currency Conversion
Service
Regulating Access to Services
The Accounting department notice this, and immediately put a gateway in place to
stop unauthorized access from other departments before anyone starts to rely on
the service.

38. 37
Sales
Order
Fulfilment
Legal
Purchasing
Currency Conversion
Service
Accounting
Regulating Access to Services
150100
The Sales and Legal departments negotiate to use the service, and help fund an
additional server. The Order Fulfilment and Purchasing departments choose not
to use the service.

39. 38
Sales
Order
Fulfilment
Legal
Purchasing
Currency Conversion
Service
Accounting
Regulating Access to Services
150100
!
Over time the Legal department workload goes above their limit, so their requests
are throttled and their usage of the service suffers. But the service is not affected
for other users.

40. 39
Sales
Order
Fulfilment
Legal
Currency Conversion
Service
Purchasing
Accounting
Regulating Access to Services
300100
The Legal department negotiate for additional capacity, and help fund the addition
of an additional server. There is now a process in place to maintain the quality of
the service and manage the cost of future growth.

41. 40
WSRR
DataPower
Centrally manage and
govern service and
associated policies exposed
at service gateway
Enable automatic
deployment of operational
policies and SLA to service
gateways
Be alerted and proactively
react to situations and
changes in your SOA
Use Policies to Control your SOA

42. 41
Business ServiceOrganization
Service Version
Service Level Definition
WSDL Document
Business Application Organization
Application Version
Service Level Agreement
Service Provider Service Consumer
Use policies to define service consumption

43. 42
SLA Enforcement - Common Usage Scenarios
v2.0
Credit Check Service
5000
500
300
Messages
per day
300
100
?

44. 43
Consume
WSDLs & All
Policies Enforce Policy
& SLAs
WSRR Define Policy
& SLAs
Policy Admin
& Operations
Author & Attach
Policy
SLA Policy
DataPower enforces WSRR policies, automatically

45. 44
SLA enforcement using DataPower
Mediation policies enforced automatically
• Using Web Service Proxy for SOAP services
• Using Multi-Protocol Gateway for REST services

46. 45
Author and attach mediation policies to control
DataPower gateways at runtime
Conditions
Parameters
Average Latency
Error Count
Message Count
Comparison
Greater than (also allowing bursts)
Less than
Schedule
Between dates
Days of week
Times of day
Actions
Notify
Queue Message
Reject Message
Route Message
Validate Message
Mediation Policy

47. 46
Workload Management Policy
Author and attach workload management policies to
control IBM Integration Bus flows at runtime

48. 47
Provides detailed pass and
failure rates for operational
policy over a period of time
Leverages IBM Integration Bus
Explorer to Author the Policy
Sets
Supports WS-Security Policy
Know What’s Going Right In the ESB

49. 48

50. 49
Consumption Visualizer
See who is consuming a service

51. 50
Graphical Explorer
Analyze the impact of making changes to a service

52. 51
Interactive Charts and Custom Reports
Visualize the data in your service registry
Service reuse
Service level definitions (SLDs) governance state
My Items
Services by owning organization
Documents by type
Services by governance state
Number of versions per business capability
Service consumption by version
SLAs by governance state
Endpoints by environment
Online/Offline endpoints per environment
Create custom reports using Business
Intelligence Reporting Tools (BIRT)
8.0

53. 52
Service Registry Dashboard
Managing views

54. 53
Service Registry Dashboard
Managing permissions

55. 54
Service Registry Dashboard
Editing pages: adding widgets

56. 55
Service Registry Dashboard
Editing pages: drag-and-drop page layout

57. 56
Configuring Widgets
Easily configure many aspects of the widget

58. 57
Instead of:
Architecture for
architecture’s sake
Complete re-engineering
Enterprise-wide initiatives
Start with:
End-to-end departmental
projects
Focus on IT
professional’s needs
Integrating existing
organizational structures
For Successful SOA… Keep It Simple

59. 58
Questions?

60. 59
WSRR v8.5 Overview Video - Now on YouTube
http://youtu.be/TwfkkjhMgBA

61. 60
WSRR Sessions at Impact 2014
Client use case presentations
2089: Lessons Learned Using a Service Registry for Service Governance
• Tuesday: 10:30 – 11:30 – Palazzo F; Steve Romanowski (State Farm), Dennis Miller (IBM)
3358: How PSCU Implemented Its Intelligent Platform Through a SOA COE
• Tuesday: 14:15 – 15:15 – Marcello 4402; Prithvi Srinivasan (Prolifics)
1501: API Lifecycle Management: Integrating IBM WebSphere Service Registry and Repository & API
Management
• Wednesday : 10:30 – 11:30 – Marcello 4402; John Falkl (Haddon Hill Group Associates)
2781: How CVS Caremark Implemented a Service Oriented Architecture Center of Excellence
• Wednesday : 10:30 – 11:30 – Marcello 4405; Prithvi Srinivasan (Prolifics), Ajay Behuria (CVS CareMark)
2740: Extending IBM WebSphere Service Registry and Repository to Legacy IBM WebSphere Application
Server
• Wednesday: 14:15 – 15:15 – Marcello 4405; Animesh Jain (Prolifics)
2699: SOA at Highmark - One Company's Journey
• Wednesday : 17:00 – 18:00 – Lando 4305; Rich Turney (Highmark Inc.), Ed Ober (Highmark Inc.)
3128: Implementing an ESB with IBM Integration Solutions at Danske Bank
• Wednesday : 17:00 – 18:00 – Marcello 4404; John Alex Jensen (Danske Bank)
1540: Reusable Policy Templates in IBM WebSphere Service Registry and Repository
• Thursday: 10:30 – 11:30 – Palazzo F; Yevgen Khibin (Kaiser Permanente)
2946: SOA Best Practices & Pitfalls
• Thursday : 15:45 – 16:45 – Lido 3005; Rich Turney (Highmark Inc.), Ed Ober (Highmark Inc.), Chris Hengst
(Highmark Inc.), Bryan Lichtenwalner (Highmark Inc.)

62. 61
WSRR Sessions at Impact 2014
Product presentations
1159: IBM Integration & Governance: Featured Session
• Monday: 14:30 – 15:30 – Palazzo H; Nicola Hills (IBM)
1250: What’s New in IBM WebSphere Service Registry and Repository
• Tuesday : 10:30 – 11:30 – Marcello 4405; Robert Laird (IBM), Nick Butler (IBM)
• Wednesday: 15:45 – 16:45 – Marcello 4405; Robert Laird (IBM), Nick Butler (IBM)
1200: IBM WebSphere Service Registry and Repository & IBM Integration Bus: Advanced Integration
• Tuesday : 17:00 – 18:00 – Palazzo I; Martin Smithson (IBM)
1251: Service Visibility & Management with IBM WebSphere Service Registry and Repository
• Wednesday : 13:00 – 14:00 – Marcello 4405; Robert Laird (IBM), Nick Butler (IBM)
3237: Meet the Experts: IBM WebSphere Service Registry and Repository
• Thursday: 13:00 – 14:00 – San Polo 3503; Nick Butler (IBM), Martin Smithson (IBM)
Roundtable Feedback Sessions
1244: Roundtable: IBM WebSphere Service Registry and Repository
• Monday: 17:15 – 18:15 – Zeno 4708; Robert Laird (IBM), Gary Thornton (IBM)
• Tuesday: 17:00 – 18:00 – Zeno 4708; Robert Laird (IBM), Gary Thornton (IBM)

63. 62
WSRR Sessions at Impact 2014
Hands on labs
1223: Enable Role-based Service Views & Change Notification to Effectively Govern Services
• Wednesday: 15:45 – 18:00 - Murano 3305; Martin Smithson (IBM), Dennis Miller (IBM)
1201: IBM WebSphere Service Registry and Repository & IBM Integration Bus: Advanced Integration Lab
• Thursday: 09:00 – 11:30 - Murano 3305; Martin Smithson (IBM), Dennis Miller (IBM)

64. 63
We Value Your Feedback
Don’t forget to submit your Impact session and speaker
feedback! Your feedback is very important to us – we use it to
continually improve the conference.
Use the Conference Mobile App or the online Agenda Builder to
quickly submit your survey
• Navigate to “Surveys” to see a view of surveys for sessions
you’ve attended

65. © 2014 IBM Corporation
Thank You

66. 65
Legal Disclaimer
• © IBM Corporation 2014. All Rights Reserved.
• The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained
in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are
subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing
contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and
conditions of the applicable license agreement governing the use of IBM software.
• References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or
capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to
future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by
you will result in any specific sales, revenue growth or other results.
• If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete:
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will
experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
• If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete:
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs
and performance characteristics may vary by customer.
• Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM
Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server).
Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your
presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in
your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International
Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.
• If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete:
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
• If you reference Java™ in the text, please mark the first use and include the following; otherwise delete:
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
• If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete:
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
• If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete:
Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and
other countries.
• If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete:
UNIX is a registered trademark of The Open Group in the United States and other countries.
• If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete:
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of
others.
• If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta
Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration
purposes only.