Académique Documents
Professionnel Documents
Culture Documents
November 2013
US Government Users Restricted Rights: Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM, the IBM logo, and ibm.com are 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.
Trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the
Office of Government Commerce.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, 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.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries,
or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the
U.S. Patent and Trademark Office.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used
under license therefrom.
Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and
other countries.
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 IBMs 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 publication 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 IBMs 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, savings or other results.
Contents
Instructor demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Student exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Lesson 2. Templates and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Service templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Template rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Service template examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Template and service relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Business service instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Service model hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Example: Web application service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Creating a template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
The Service Configuration page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Opening the Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Example: Creating a template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Example: Status rule threshold criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Creating an incoming status rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Selecting incoming status rule type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Incoming status rule form overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Rule Name and Data Feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Selecting event discriminators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Matching the service instance name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Choosing the status evaluation fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Setting the threshold filter criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Metric collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Saving the template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Service navigation view after template creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Instructor demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Student exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Lesson 3. Creating template dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Creating multiple-level template models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Dependency rules overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Creating dependency rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating a good, marginal, and bad aggregation dependency rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Saving the template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Viewing the template hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Instructor demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Student exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Lesson 4. Creating and testing service instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Creating service instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Creating service instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Example: Creating a WebServer instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Assigning a template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Adding dependent services to a parent service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Setting the service tree list order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Service models in the Service Viewer portlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Sending test events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Instructor demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Student exercise service hierarchies diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
iv IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
Contents
vi IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
Contents
viii IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
Contents
8 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Lesson 1. Security overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Authentication and authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Security services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Authentication overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
File-based user repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Example: File-based user repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
File-based repository configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
OMNIbus ObjectServer user and group repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
LDAP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
LDAP logical architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Federated repository overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Multiple repositories as a federated repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Example of a user lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Lesson 2. Configuring LDAP authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Configuring LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Starting the WebSphere administrative console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Adding an LDAP repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
LDAP configuration: Add base entry to realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Defining the LDAP base entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Defining the LDAP repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Saving configuration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Completing the WebSphere base entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Repository entity types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Instructor demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Student exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Lesson 3. Configuring SSL authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Configuring secure communications with an LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Tivoli Integrated Portal credential stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Retrieving the LDAP signer certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Entering LDAP certificate information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Configuring the Tivoli Integrated Portal server for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Instructor demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Student exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Lesson 4. Managing users, groups, and authorization roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
User, group, and authorization roles overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Managing users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Managing authorization roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Assigning roles to a user or group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Instructor demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Student Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
x IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
Contents
xii IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
Contents
xiv IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
About this course
For information about other related Cloud & Smarter Infrastructure courses, visit the Cloud &
Smarter Infrastructure education training paths website:
ibm.com/software/software/tivoli/education/
Details
Delivery method Classroom or instructor-led online (ILO)
Course level ERC 1.0
This course is a new course.
Product and version Tivoli Business Service Manager 6.1.1
Duration 5 days
Skill level Intermediate
xvi IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
About this course
Learning objectives
Learning objectives
After completing this course, you should be able to perform the
following tasks:
Business service management concepts
Define business service management concepts
Define IBM Tivoli Business Service Manager architectural components
Model business services
Evaluate business processes to develop service models
Build business service models using templates and template rules
Use business and monitor data to track the status of business service
models
Advanced service models
Evaluate service status using multiple rules
Track key performance indicators for using business and monitor data
Create and manage service level agreements (SLAs)
Copyright IBM Corporation 2013 2
xviii IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
About this course
Course agenda
Uempty
Course agenda
The course contains the following units:
1. Introduction to IBM Tivoli Business Service Manager 6.1.1
This unit explores the concepts of business service management. It also provides an overview
of the tools that are provided with Tivoli Business Service Manager to create, manage, and
visualize business services.
In these exercises, you learn how to create and modify the primary components of Tivoli
Business Service Manager templates, rules, and services. You create business service
hierarchies and test rule operations with simulated monitor events. The template capabilities
are extended in later exercises.
In these exercises, you expand the capabilities of the template rules you created in the Service
model basics exercises on page 2. You modify and create rules that are more flexible in
adapting to data from multiple sources.
maintenance windows, which provide a mechanism for temporarily removing SLA tracking on a
service.
5. Data fetchers
Business service models must be able to respond to business data and monitor events.
Templates can have multiple rules, which requires a complex evaluation of rule states. Template
rules can also calculate key performance indicators (KPIs). KPIs are then available to be
included in visual representations of business services. This unit demonstrates a function that is
called a data fetcher. Data fetchers extend service template functions to provide comprehensive
representations of business services.
In previous exercises, you created template rules that responded to incoming monitor events. In
these exercises you create template rules that evaluate business data that is retrieved from a
business database. You also create rules that calculate numerical values, known as key
performance indicators (KPIs). You modify the console interface to show the KPIs.
In these exercises, you develop External Service Dependency Adapter (ESDA) rules to
automatically create service instances and service models. The ESDA evaluates business data
from an external database and dynamically builds business services. For these exercises, the
simulated data is stored in the Tivoli Business Service Manager DB2 database.
In these exercises, you use several Tivoli Business Service Manager tools to automatically
create service instances and service models. You create automatic population rules that are
attached to incoming status rules. When the incoming status rule receives data, the automatic
population rule is triggered. You create a service instance using discovery data from an IBM
Tivoli Monitoring server. Last, you examine and enrich service models that are created by
processing discovery data from a Tivoli Application Dependency Discovery Manager (TADDM)
server.
8. Security
Controlling access to system resources is a critical component of monitoring system resources.
In this unit, you learn how authentication and authorization to the Tivoli Business Service
xx IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
About this course
Course agenda
Uempty Manager dashboard server is managed. The dashboard server, also known as the Tivoli
Integrated Portal, supports multiple user and group authentication repositories. You apply roles
to control authorization to data server software objects. This unit also covers how authentication
and authorization are configured to provide a comprehensive, secure environment.
User authentication and authorization are managed with the Tivoli Integrated Portal and Jazz
for Service Management security services. In these exercises, you configure an LDAP user
authentication service for the Tivoli Integrated Portal server. You then assign authorization roles
to an LDAP user group. You use authorization roles control user access to Tivoli Integrated
Portal server and Jazz for Service Management resources.
In these exercises, you customize the visualization of business service data with the Jazz for
Service Management visualization services. You create a dashboard for members of the
executiveManagementGroup group. The dashboard consists of two levels of linked pages. You
also create custom roles, views, and console preference profiles to manage access to the
dashboard pages.
The console-based Tivoli Business Service Manager administrative tasks are available with
command-line tools. In this unit, you use several common command-line tools to export
business service definitions and customizations.
A primary factor that affects the performance of the Tivoli Integrated Portal server and data
server is the Java virtual machine (JVM) configuration. This exercise demonstrates the effect of
changing server heap size on the Tivoli Integrated Portal Java virtual machine (JVM) garbage
collection cycle.
xxii IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
1 Introduction to IBM Tivoli Business
Service Manager 6.1.1
What this unit is about This unit explores the concepts of business service
management. It also provides an overview of the tools
that are provided with Tivoli Business Service Manager to
create, manage, and visualize business services.
How you check your progress You can check your progress in the following way:
Review questions
Objectives
When you complete this unit, you can perform the following
tasks:
Define business services and business service management
Describe the IBM Tivoli Business Service Manager 6.1.1 capabilities
Describe the primary Tivoli Business Service Manager architectural
components
Describe the tools that are available in Tivoli Business Service
Manager 6.1.1 to create, track, and visualize business services
Objectives
2 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
What this lesson is about In this lesson, you learn the basic concepts of business
services and business service management. You learn
the architecture, functions, and tools that are provided
with Tivoli Business Service Manager 6.1.1.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Define business services and business service
management
Describe the IBM Tivoli Business Service Manager
6.1.1 capabilities
Describe the primary Tivoli Business Service Manager
architectural components
Describe the tools that are available in Tivoli Business
Service Manager 6.1.1 to create, track, and visualize
business services
4 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
Business services are logical groupings of managed IT or software application resources that
represent a higher-level view of an application or business function. The tools that are provided with
Tivoli Business Service Manager 6.1.1 are used to create, manage, and view logical business
service models. You design the service models to track the status of a business service or key
performance indicators (KPIs). The service status and KPIs are configured with rules that react to
monitor events or business data.
Tivoli Business Service Manager provides these tools to track the status of business services:
Visualization services to show hierarchical relationships and high-level views of service models.
Business services logically group low-level monitored physical objects or business processes to
create higher-level logical objects that represent a business process or service. Online banking is
an example of a business service.
To a bank executive responsible for maintaining the online banking application, the customer
experience is one of many business services of which they are concerned. At a high level,
executives must know whether the components that support the online banking are working.
However, they do not need to see the status of low-level services, such as servers or routers.
A manager responsible for maintaining all networks is concerned with all of the bank network
resources. However, managers also must know which outages directly affect online banking
and which outages affect an individual bank office.
6 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty A network administrator must be able to see the status of all networks. However,
administrators also must see the status of each router and communication link in all networks.
When an outage is detected, they must be able to quickly pinpoint the location and cause of the
outage.
Tivoli Business Service Manager provides tools to track and present appropriate business service
data to each of these user types.
Tivoli Business Service Manager provides tools to support these major tasks:
Visualization of the status of business services.
Visualization of the impact of lower-level business performance on higher-level
business processes.
Tracking of business service status or key performance indicators with business
data, monitor events, and discovered resources.
Tracking of service level agreements (SLAs) in real time.
Copyright IBM Corporation 2013 6
Tivoli Business Service Manager provides tools to present logical views of business service data.
All available data can be evaluated to provide high-level, intermediate-level, or low-level business
service views.
Tivoli Business Service Manager relies on three main sources to track the status of business
services and KPIs:
Events: You use any type of monitor event sources to track service status and automatically
build service instances and relationships. Monitor event sources include Tivoli Monitoring, Tivoli
Composite Application Manager, and Tivoli Enterprise Console.
Business data: You use business data to provide another method of tracking service status
and creating business service instances and relationships. This evaluation is independent of
any systems management monitoring.
Dependencies and discovery: You discover business service relationship data with a product
such as Tivoli Application Dependency Discovery Manager. In addition, an application
developer can provide a software tool that is called a Discovery Library Adapter. This tool
produces relationship data within the scope of the managed application. You use the data to
build business service models.
8 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
The primary Tivoli Business Service Manager architectural components are as follows:
Dashboard server: This console application is a Java Platform, Enterprise Edition application
that is supported by the Tivoli Integrated Portal. The dashboard server provides business
service visualization and application administration, authentication, and authorization services.
Analysis tools and policy script facilities are provided with Tivoli Netcool/Impact technology.
Data server: The data server is the Tivoli Business Service Manager analysis and tracking
engine. Business service configuration and status information is processed with the data server.
Configuration and status information are stored in a DB2 database.
Discovery Library Toolkit: This component processes structured data to create, configure,
and modify business services. The structure conforms to the Common Data Model method for
Netcool/OMNIbus Probe for Tivoli EIF: This component forwards events that are generated
outside the Tivoli Netcool/OMNIbus probe infrastructure. Examples of other event providers
include Tivoli Monitoring, Tivoli Enterprise Console, and monitoring software from businesses
that are not IBM businesses.
10 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
Dashboard visualization
Dashboard visualization
Tivoli Business Service Manager 6.1.1 visualization services are provided with the Jazz for Service
Management 1.1 Dashboard Application Services Hub (DASH) server. The DASH server is
installed separately and is used to visualize business data from many business applications. The
Tivoli Integrated Portal 2.2 server provides the graphical administrative console services for Tivoli
Business Service Manager 6.1.1.
The dashboard visualization services are used to show service models, key performance indicators
(KPIs), and data from other applications for comprehensive views of business service health. An
administrator creates custom dashboards to present information for a specific audience and
business. More information about the visual tools is in the unit, "Custom dashboards and page
management".
Chart visualization
Business data and service model data can be shown as dynamic
charts or saved in reports.
Chart visualization
The visualization services that are used by Tivoli Business Service Manager include a charting
widget that renders business data in real time. You customize the presentation of data in various
formats, such as pie or bar charts. Use charts to enhance the information included in business
dashboards.
12 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
Report visualization
Reporting services are provided with the installation of the
Tivoli Common Reporting and Cognos Business Intelligence
infrastructure.
Predefined Tivoli Business Service Manager reports are
included with the installation.
You can create reports for mobile devices.
Report visualization
Tivoli Business Service Manager includes Tivoli Common Reporting services to analyze and show
business data. Tivoli Common Reporting is a separate application that is provided with the Tivoli
Business Service Manager installation media. You can generate reports from application and
business data.
Tivoli Common Reporting 3.1 is based on Cognos 10.2 Business Intelligence engine. Tivoli
Common Reporting 3.1 includes support for the Jazz for Service Management visualization
services and mobile devices.
Events
Events can drive both the creation and status of business
service models.
Events
Tivoli Business Service Manager uses the Tivoli Netcool/OMNIbus ObjectServer as an event
engine. Tivoli Business Service Manager generates and stores business service status events in
the ObjectServer. External events can come from many sources, including the following ones:
Tivoli Netcool/OMNIbus probes
Tivoli Enterprise Console Server
Tivoli Monitoring
Events can be used to automatically create business services and business service relationships.
14 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
Business data
Business service status can be driven with external
business data.
Business data
Business data can drive business service status and automatic business service creation. You can
query external data sources for the following purposes:
Evaluate business service status
Any available data can be used to provide a business service view into an enterprise infrastructure.
Tivoli Business Service Manager integrates with the IBM Tivoli Application Dependency Discovery
Manager and other Change and Configuration Management Databases. Business service data is
cataloged with the Common Data Model standards.
The Discovery Library Toolkit uses discovery data for these purposes:
Automatically create application, system, and network business service models
16 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
Tivoli Business Service Manager includes tools to track the status of a business service against a
defined service level agreement (SLA). Internal and external customers can define a target level of
service for any modeled business service. You can also use the Jazz for Service Management
visualization services to track SLAs, in addition to service status or key performance indicators.
Historical reports and real-time SLA charts can be included with other business dashboard views.
6.1 6.1.1
Customization artifacts are stored as structured data in the DB2
database and in the WebSphere instance that is installed with
the Tivoli Integrated Portal.
You have export and import tools to manage customizations for
the following purposes:
Incremental customization backups for disaster recovery.
Migration: Move customizations from one environment to another; for
example, a test environment to production.
Upgrades: Upgrade infrastructure components and incorporate
previous customizations.
Customizations, including dashboards, pages, and business service configurations, are stored in
the Tivoli Business Service Manager DB2 database. The customizations can be exported and used
to back up a deployment environment or move the customizations to another Tivoli Business
Service Manager installation.
18 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
The core functions provided by Tivoli Business Service Manager are as follows:
Modeling of business systems and business system relationships
Tracking the status and key performance indicators of those modeled business systems
You create business service models manually or automatically, based on available business data.
Business services are created to track physical and logical resources and processes. For example,
a service model can represent the health of a web server or the energy consumption in an office
building.
Business services are tracked with a logical device called a business service model. Tivoli
Business Service Manager service models consist of these configured items:
Templates: Business service model templates define the behavior of a modeled service. The
behavior is configured with one or more rules. Rules define how a template must react to one or
more of the following data inputs:
Monitor events
Business data
Changes in peer or child services
Instances: Instances are created to represent specific services based on one or more
templates.
Hierarchical service models are created with dependency rules in a template. Dependency rules
define a relationship between a higher-level, or parent, template and a lower-level, or child,
template. Status or key performance indicators tracked in parent levels in the model hierarchy are
dependent on values calculated for child services. This design allows the effect of changes in child
service values to be quickly propagated to higher level parent services.
20 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
Tivoli Business Service Manager provides several methods for managing business service models.
The method that is used depends on the type of data that is available to monitor the business
service and the requirements of the administrator. For example, services that correspond to
frequently changing business processes should be managed with automatic population rules. In a
test environment, manual service creation is quicker than developing complex automation rules.
The two types of rules that are most commonly used for tracking a business service status or key
performance indicator are as follows:
Incoming status rules: Incoming status rules evaluate incoming events or business data and
set the status of the affected business service instance. Status rules evaluate a numerical value
or set the status of a child service.
Dependency rules: Dependency rules are configured for a parent service. They evaluate the
aggregated status or a numerical value that is provided by all child business services. They set
the status according to the rule definition. The evaluation sets the service status or calculates a
key performance indicator for a parent service. Numerical formula rules calculate the status or a
key performance indicator for a parent service that is based on a comparison with other parent
services.
22 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
Incoming status rules evaluate an incoming event or database query to determine the business
service status or calculate a key performance indicator. In this example, each WebServer service
instance evaluates an event to determine the server response time. The response time is extracted
from a field in a received monitor event. If the response time is greater than 500 milliseconds, set
the service status to Marginal.
Dependency rules
You create hierarchical service models by configuring parent-
child dependency relationships between services.
The relationships are defined with dependency rules.
Example: Calculate the average response time of a web farm with the
response times of all child web server instances.
Dependency rules
You create complex service models by defining one or more relationships between a parent service
and one or more dependent child services. An aggregation of the values that are provided by the
child services is used to set the parent status or KPI. Use dependency rules to create models that
show the business impact of status and KPI changes to child services.
24 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
A numerical formula rule combines the rule output values of different rule types within the same
service instance. For example, a template contains three rules: Region1Total, Region2Total, and
Region3Total. Each rule calculates the number of open trouble tickets for a geographic region of a
company. You use a numerical formula rule to add the value of each rule to determine the total
number of open trouble tickets for the company: CompanyTotal = Region1Total.value +
Region2Total.value + Region3Total.value. A change to the value of Region1Total, Region2Total, or
Region3Total automatically triggers a new calculation for CompanyTotal.
Data fetchers
Use data fetchers to query databases for the following purposes:
Retrieve key performance indicator data
Trigger service status evaluation
Example: Evaluate the number of open trouble tickets for a web server
and set the service status.
WebServer6
Tickets: 2
Data Fetcher
WebServer13
Tickets: 7
Rows
WebFarm3
Ticket
DB WebServer21
Tickets: 0
WebServer15
Tickets: 4
Data fetchers
Data fetchers extend the capabilities of Tivoli Business Service Manager service models. Data
fetchers provide a mechanism to query a database and use the returned data with service model
tracking. This mechanism allows service models that represent business services that are not
monitored, directly or indirectly, with traditional monitoring infrastructures. For example, you create
a service model that represents the efficiency of your customer service organization. The service
model tracks the average customer problem resolution time, which is based on data that is stored in
your customer service database.
26 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
1 Introduction to IBM Tivoli Business Service Manager 6.1.1
Lesson 1. Business service management overview
Uempty
Summary
Now that you have completed this unit, you can perform the
following tasks:
Define business services and business service management
Describe the IBM Tivoli Business Service Manager 6.1.1 capabilities
Describe the primary Tivoli Business Service Manager architectural
components
Describe the tools that are available in Tivoli Business Service
Manager 6.1.1 to create, track, and visualize business services
Summary
What this unit is about Templates and rules provide the foundation for the Tivoli
Business Service Manager service model. This unit
explores the relationship between templates, services,
and rules.
How you check your progress You can check your progress in the following ways:
Student exercises
References SC23-6041-09 Tivoli Business Service Manager 6.1.1
Service Configuration Guide
Uempty
Objectives
When you complete this unit, you can perform the following
tasks:
Start and stop the major Tivoli Business Service Manager components
Explain how templates and services are used together to build service
models
Create event-based templates and rules
Create dependency templates and rules
Create service instances
Create dependencies between services
Test service models
Objectives
What this lesson is about In this lesson, you learn the commands that are used to
start and stop the primary Tivoli Business Service
Manager components.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Start and stop the major Tivoli Business Service Manager
components
30 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 1. Starting and stopping Tivoli Business Service Manager components
Uempty
The primary and required Tivoli Business Service Manager components that must be started are as
follows:
Tivoli/Netcool ObjectServer: The event engine that is used by Tivoli Business Service
Manager. The ObjectServer receives monitor events and status events that are generated
during Tivoli Business Service Manager operation. A second ObjectServer can be installed and
configured to provide redundancy.
Tivoli Business Service Manager data server: The analysis engine for Tivoli Business
Service Manager. This Java Platform, Enterprise Edition application is installed on embedded
WebSphere (default) or base WebSphere. The internal processing technology is based on
Tivoli/Netcool Impact. A second data server can be installed and configured to provide
redundancy. Service model status and customization artifacts are stored in an installed DB2
instance.
Tivoli Business Service Manager dashboard server: The visualization and administrative
console for Tivoli Business Service Manager. This Java Platform, Enterprise Edition application
is installed and managed on embedded WebSphere (default) or base WebSphere. The
dashboard service integrates with services provided by the Tivoli Integrated Portal. Multiple
dashboard servers can be installed and configured to provide redundancy and load balancing.
Event Integration Facility Probe: A Tivoli/Netcool monitor probe that is configured to receive
monitor events and forward them to the ObjectServer. The source of the monitor events that are
received by the probe can be from sources such as Tivoli Monitoring, Tivoli Network Manager,
Tivoli Enterprise Console, and Tivoli OMEGAMON XE. The probe can also be configured to
forward events from monitor sources other than IBM applications.
Tivoli Monitoring Agent: A standard Tivoli Monitoring agent that is designed to monitor Tivoli
Business Service Manager processes and operations. Additionally, the agent can be configured
to forward operational events to a Tivoli Data Warehouse database.
32 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 1. Starting and stopping Tivoli Business Service Manager components
Uempty
You start the Tivoli Business Service Manager ObjectServer with the following command:
/opt/IBM/tivoli/netcool/omnibus/bin/nco_obj -name <Server_Name>
The <Server_Name> value is configured during installation. The value is not necessarily the host
name on which the ObjectServer is installed. Because of the necessary interactions with the data
server, the ObjectServer must be installed as close to the data server as possible.
The data server can be installed on a separate computer, or on the same computer as the
ObjectServer or dashboard server. Database storage for Tivoli Business Service Manager
operations must be provided with a configured DB2 instance. The DB2 instance can be remote to
the data server. To optimize performance, the DB2 instance must be as close as possible to the
data server.
The data server must be started with the same user ID used to install the application. The data
server is installed in your laboratory environment on the tbsm01 virtual image. You start the data
server in the laboratory environment with the following command:
/opt/IBM/tivoli/tipv2/profiles/TBSMProfile/bin/startServer.sh server1
34 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 1. Starting and stopping Tivoli Business Service Manager components
Uempty
The dashboard server can be started before the data server or ObjectServer, but the dashboard
server has limited service.
Tivoli Integrated Portal server components are required and installed with the dashboard server.
Unless otherwise specified, the term Tivoli Integrated Portal is intended to indicate that the
dashboard server started in the Tivoli Integrated Portal profile.
The dashboard server must be started with the same user ID used to install the application. The
dashboard server is started as a WebSphere profile. The profile is installed on the tbsm01 virtual
image in your laboratory environment. You start the dashboard server in your laboratory
environment with the following command:
/opt/IBM/tivoli/tipv2/profiles/TIPProfile/bin/startServer.sh server1
To manually create a business service model, you must first log on to the Tivoli Business Service
Manager console. Console services are provided with the dashboard server installed in the Tivoli
Integrated Portal server.
The default administrative user ID is tipadmin. The administrative password is set during
installation.
36 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 1. Starting and stopping Tivoli Business Service Manager components
Uempty
Logout link
Console
workspace
Task list, or
Task view
The console has a list of tasks on the left and a console workspace on the
right.
You close the console connection by clicking the Logout link in the upper
right.
Copyright IBM Corporation 2013 9
When you log on to the Tivoli Integrated Portal server, the primary console elements that are used
in the first laboratory are highlighted in this image. The elements are as follows:
Task list or task view: This section at the left of the console is a list of folders, pages, or tasks.
Clicking a folder expands to show any contained folders, pages, or tasks. Clicking a page or
task changes the context view in the console workspace.
Console workspace: This section at the right of the console. This view changes based on
pages or tasks that are selected in the task list.
Logout link: Clicking this link disconnects the console connection. The link is in the upper right
of the console.
You learn how to modify these elements in the unit, Custom dashboards and page management
on page 391.
Instructor demonstration
Instructor demonstration
38 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 1. Starting and stopping Tivoli Business Service Manager components
Uempty
Student exercises
Student exercises
What this lesson is about In this lesson, you learn how templates are used to define
general characteristics for a business service model. You learn
how template rules are used to respond to monitor events and
business data. You also learn how template dependencies are
used to create multilevel template service models.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Explain how templates and services are used together
to build service models
Create event-based templates and rules
40 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
Service templates
Service
Template
Data Rule Service status
Key performance indicator
Event Rule
Service templates
Templates are the basis for all business service definitions. You create them to model any aspect of
your business infrastructure. Templates also define the parent-child relationships between business
services. Templates define general behavior and characteristics for a business service. The
behavior and characteristics are defined with one or more template rules. The rules respond to
incoming monitor events or database data queries and assign a status value or key performance
indicator (KPI).
Template rules
Template behavior is defined with one or more rules.
Incoming status rules are triggered with monitor events or
database queries.
Multiple-level template models are created with dependency
rules.
Automatic population rules create services with an association
with a status or dependency rule.
Template rules
Template rules define a response to monitor events or a database query. One or more rules are
assigned to a template. If the template contains multiple rules, the rules can be evaluated together
to determine the overall status of the business service. The rules are grouped into the following
three general types:
Incoming status rules: These rules assign a business service status or calculate a KPI with
information that is contained in a Tivoli/Netcool ObjectServer event or a database query.
42 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
Note: A fourth type of rule icon is shown in the console. These rules are known as Internet
Service Monitor (ISM) rules. They are designed to interact with the Internet Service Monitoring
component for IBM Tivoli Composite Application Manager (ITCAM) for Transactions. This feature
is not included in future product releases and is outside the scope of this course.
Tivoli Business Service Manager provides tools to model most business services or processes.
Creating templates and models that correspond to physical resources can be useful for many
purposes, but logical models provide more sophisticated views of business processes. For
example, a city government recently upgraded the power meters on all homes in the city limits. The
new meters provide numerous metrics that are related to power consumption. Using combinations
of templates and rules, you can create business service models that show a comprehensive view of
device and performance measures, like the following ones:
Real-time average household power consumption
For these examples, no single monitor event provides enough information. The templates include
rules to analyze multiple sources of data, such as the following ones:
Business data that is related to real-time power consumption and cost rates
Analysis of individual monitor events from each power meter
44 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
WebServer1
WebServer
Status Rule
WebServer
Status Rule
Response Rule
Response Rule
Open Tickets Rule
Open Tickets Rule
Template
Service instance
It is important to understand the concepts of, and differences between, a service template and a
service instance. A service template is a general description of the type and properties of some
monitored object. A service instance represents a specific monitored object with the properties
defined in the template. For example, a template might be a description of a bicycle, including
properties like color, frame type, wheel size, and number of gears. A service instance is equivalent
to an actual bicycle: red, 16-inch wheels, 10 speed.
Example
A template is created for each class of server.
Probe events include server class identification information.
The service instances are created with the corresponding template.
The Tivoli Business Service Manager console provides tools to create service templates for
common business service behavior. You can create one template for a general type of service. You
then use it as the basis for multiple service instances, such as in the following examples:
Identifying service events
You must identify service events with a combination of field values from an event. The fields that
you select must be unique to the service template you want to identify. For example, if database
monitor events come from an Oracle probe, you might define the Manager field as Manager =
nco_p_oracle.
You must identify the status of a service that is based on a numerical event field. Typically, you
use the Severity field, as in this example:
46 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
A service instance can be any hardware or software that supports a service template. An
example is something that generates OMNIbus alerts. When you analyze your events, select a
combination of event fields and values. Those field values are used to identify a service
instance. For example:
Node + AlertKey = WebServer18080
WebServer1 WebServer2
WebServer WebServer
Status Rule Status Rule
Response Rule Response Rule
Open Tickets Rule Open Tickets Rule
When customers connect to the application for online ordering, connectivity requires the availability
of these servers:
A web server in a web farm
A database server
An authentication server
A different service level agreement (SLA) might exist for each of these services. You might set up a
service template that is called WebApplication that monitors events from each service template
that is defined in a hierarchy. By defining the dependencies of each level of the hierarchy, status
changes can quickly propagate. As the status changes propagate, the effects of outages at all
levels are immediately shown.
Each of the service templates in a model represents its own set of supporting hardware and
software. After you determine the supporting hardware and software for a service template, you can
determine the events that affect this service.
48 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
DB1 DB2
WS1 WS2 WS3
In this example, the Online Ordering application is dependent on several services. These services
consist of web farms and Database servers. Each web farm contains several web servers. Each
database server might access multiple databases.
The web servers share information that is stored on the Database servers. The Database servers
can also monitor some internal components, such as processor, hard disk drive, and applications.
Tivoli Business Service Manager can monitor the status of each of these services that support the
Online Ordering application. To ease the creation of services, templates that define the general
properties of a service are created. Service instances can then be created with the templates.
Creating a template
To create a template with the Tivoli Business Service Manager
console, complete the following basic tasks:
1. Log on to the console.
2. Open the Service Configuration page.
3. Open the Template Editor.
4. Configure template behavior by creating one or more rules for the
template.
Creating a template
Use the service editor in the console to create a template and define one or more rules. Template
rules define how the template responds to monitor events or business data.
50 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
Expand the Administration folder in the All tasks view, and click
Service Configuration.
Copyright IBM Corporation 2013 21
The initial console elements that are shown consist of a page with two windows. The window on the
left is a list of folders or tasks, called a view. The window on the right is a workspace that changes
based on the task that is selected from a view. Templates and services are configured from the
Service Editor portlet, found on the Service Configuration page. You open this page by selecting the
Administration > Service Configuration task in the All tasks view.
Templates are created from the Templates section of the Service Navigation portlet. Click the
Templates menu in the Service Navigation portlet. From this section, you can create, delete, or edit
templates. Access the template form in the Service Editor portlet to the right of the Service
Navigation portlet.
The authorization roles that are assigned to a user control access to the Service Administration
page. Objects within the Tivoli Business Service Manager environment that the user is not
authorized to see or modify are not shown.
52 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
Click the Create New Template icon to open the template form
in the Service Editor pane.
Create one or more incoming status rules.
To create a template for the example web server, use the following steps:
1. Click the Create New Template icon in the Templates section of the Service Navigation portlet.
3. Select an icon for all instances that are based on the WebServer template.
4. Create a status rule. The Rules tab is where all the dependency and status rule information for
this template is stored. The configuration options available for this template are reviewed in
more detail in the section Incoming status rule form overview on page 57. For this example,
create an Incoming Status Rule for WebServer to use event data to set the service status.
Plan a naming convention for templates and services that are used in a production environment.
The status of a service can be based on an evaluation of one or more event fields from an
ObjectServer event. An incoming status rule can evaluate to a status of Good, Marginal, or Bad.
Note: The service status can be linked directly to the severity in an ObjectServer event. Any field
or set of fields can be used as a formula for service status.
For this example, the highest severity of each web server status event determines the overall status
of the web server. These tasks must be completed to create this service model:
Create a template for web servers. The template defines how the status of any web server is
determined.
A service instance represents each web server with the WebServer template.
54 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
The major tasks that are required to create an incoming status rule are described in more detail in
subsequent sections of this unit. Standardizing naming conventions for rule names simplifies
managing large numbers of templates.
The incoming status rule evaluates a matching monitor event. The overall service status is set
based on an evaluation of specified event fields.
56 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
The incoming status rule form for processing events consists of the four sections that are
highlighted in this image. Each section is described in detail in subsequent pages of this unit. If the
event matches a defined event discriminator, rule processing looks for a matching instance name. If
a matching instance name is found, the rule applies the filter and threshold definitions against the
contents of the event.
Enter a name for the rule that is both descriptive and unique. Naming standards can help
distinguish the origin and type of the object. For example, the text string StatusRule as a rule prefix
or suffix helps provide context.
If you have multiple data feeds configured, you can select them from this menu. When developing
the rule, clicking the View icon shows all events that match the rule filter definition. The filter
definition is explained later in this section.
58 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
The event discriminator section of the rule definition provides a prefilter of events. If an incoming
event does not match the selected discriminator, no additional processing of the event is done. The
overall load on the Tivoli Business Service Manager server is reduced.
You can select multiple discriminators. They are evaluated as a logical AND. For example, if two
discriminators are selected and either one evaluates as TRUE, rule processing continues.
This section uses the selected fields to determine whether the service exists. Each service name
must be unique. Continuing the example, the rule evaluates the Node field from the incoming
event. The rule then matches the Node value against all defined service names. If a match is
found, rule processing continues.
60 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
In the Filter section of the rule, information in the selected filter fields evaluates the overall rule
status. You can select multiple fields. Data from the selected fields populates the Threshold Filter
section.
In the final section of the rule definition, the filter field evaluation expressions are created. Because
this example is for a Good, Marginal, and Bad rule, each of the possible states must be accounted
for. This example defines the settings as:
If AlertGroup = WebServerStatus and Severity >= Critical, set the status to Bad.
If AlertGroup = WebServerStatus and Severity >= Minor, set the status to Marginal.
If AlertGroup = WebServerStatus and Severity >= Clear, set the status to Good.
62 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
Metric collection
Metric collection
Operational metric values from rules can be configured for collection. The data is stored up to 14
days. The data can then be used with a tool called the Time Window Analyzer to graphically
compare a rules performance over some time. The performance can also be compared to other
rules that are selected for metric collection. By default, metric collection is not enabled for any rule.
After saving rule definition, click the Save icon to save the
template definition.
Save work frequently while creating templates and rules.
After saving the rule definition, click the Save icon to update the template. If you require more rules,
click one of the rule creation icons and continue.
64 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
After you create new instances or templates, the view in the Services section of the Service
Navigation portlet is automatically updated.
Instructor demonstration
Instructor demonstration
66 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 2. Templates and rules
Uempty
Student exercises
Student exercises
What this lesson is about In this lesson, you learn how to create aggregation
dependency rules and how to use those rules to create
multilevel service models. Dependency rules are used to
create service models that propagate the business impact
of low-level business service status changes.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Create dependency templates and rules
68 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 3. Creating template dependencies
Uempty
Service models require the creation of hierarchies to fully define complex business services.
Template hierarchies are created by defining dependency rules for each higher level of a
relationship.
Numerical Aggregation: These rules aggregate a numerical status from each child service
and, based on the rule definition, assign a parent a numerical status. Additionally, you can
assign an output status (Bad or Marginal) to the parent.
Numerical Formula: These rules use a numerical formula to be defined to evaluate numerical
child values to assign a parent a numerical status. Additionally, you can assign an output status
(Bad or Marginal) to the parent.
You create a parent-child relationship in a service model template by first creating the parent and
child templates separately. You create the dependency rule at the parent level, assigning the child
template in the rule definition. Subsequent pages in this unit provide more detail on each of the
major tasks in creating a dependency rule.
70 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 3. Creating template dependencies
Uempty
Continuing the example, review the steps to create a template. Dependent templates rely on the
status of one or more subordinate templates.
Instead of populating the new template status that is based on an event rule, a dependent template
is based on some dependency, such as another template. For this example, the WebFarm template
evaluates the status of one or more web servers. To create this dependent template, use the
following steps:
1. Create a template and name it WebFarm. Select a different icon for this web farm.
2. Create a rule by clicking the Create Good, Bad, Marginal Aggregation Rule icon.
A dependency rule is created based on two kinds of conditions: percentage of child status and
worst case of any child.
A percentage of child status condition calculates the percentage of children in any state (Good,
Bad, or Marginal). The status of the parent is calculated, based on the selected rule. For example,
in this image, if fewer than 30% of the child services are Bad, then the parent status is Good. If
between 30% and 70% child services are Bad, then a Marginal state is assigned to the parent. If
over 70% of the child services are Bad, then the parent state is Bad.
Notice the way that this rule is defined. Only child events with a status of Bad are considered. To
consider Marginal child events, create another dependent rule to deal with this case.
The worst case of any child option propagates the worst status of any child to the parent.
72 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 3. Creating template dependencies
Uempty
After you add the rule, it is listed in the lower section of the page. You can add multiple rules to the
list. Multiple rules indicate, in the case of dependency rules, that the status of a parent is dependent
on multiple types of child services. Save the template after completing the rule definition.
Notice that the Service Navigation tree shows a structure of dependent templates. You can expand
or collapse trees by clicking the plus (+) and minus () symbols at the beginning of any branch of
the template tree.
74 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 3. Creating template dependencies
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
76 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 4. Creating and testing service instances
Uempty
What this lesson is about In this lesson, you learn how to create service instances
and how to apply templates to those services. You learn
how to test the template rules with simulated monitor
events. You also learn how to modify service properties to
change the order in which a service is shown in the
service tree.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Create service instances
Create dependencies between services
Test service models
78 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 4. Creating and testing service instances
Uempty
After you define a template model, you can use several of the following tools to create business
services:
Event-based automatic population rules create instances while matching events are received in
the ObjectServer.
A command-line API tool can be used in scripts, based on file or other input.
Data fetcher or External Service Dependency Adapter (ESDA) rules can automatically build
service instances with external data.
Discovery data can be used with the Discovery Library Toolkit to define business service
models.
The previous lesson showed how to model business service behavior with templates. The next step
is to create the business service instances.
For the following example, the business services are defined with the Tivoli Business Service
Manager console. The major tasks of creating a service instance are described in more detail later
in this section.
80 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 4. Creating and testing service instances
Uempty
The Services section in the Service Navigation portlet shows all the instances that are currently
defined in your environment. Click the Create New Service icon to create a service instance. You
configure the service in the Service Editor portlet.
Assigning a template
Assigning a template
3. Accept the default setting for Service Level, which is described in a later section.
4. For this example, leave the Display Name field blank. You can use it to show a more
descriptive or shorter name in a service tree or service viewer portlet.
5. Accept the default setting for Maintenance Schedule, which is described in a later section.
6. Under Templates, select which template to use for this instance. In this case, select
WebServer.
82 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 4. Creating and testing service instances
Uempty
2. Click the Dependents tab and select the appropriate dependent WebServer instances.
3. From the Available Services list, select one or more dependent services. Save the service
definition.
By default, the order in which the services are shown within the Service Navigation tree is based on
the alphanumeric value of the service name. You can override this order by entering values in the
Order parameter, found on the Additional tab of the service definition form.
84 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 4. Creating and testing service instances
Uempty
WebFarm1
WebServer1 and Service, which
WebServer4 is based on
Services, which WebFarm
are based on Template
WebServer
Template
This example shows the service model hierarchy, as seen in the Service Viewer portlet.
After creating the service instance, you can send test events to verify the service operation before it
actually receives monitor events. To send test events, start the Send Test Event tool.
1. Right-click a service instance, and click Show > Send Test Event. Send Test Event shows the
fields available for modification. The fields that are shown are based on the incoming status rule
that is defined for the instance. If no status rule is defined for the service, this menu option is not
available.
You can also use the script $TBSM_HOME/bin/rad_sendevent to enter an event. Be careful to
enter all values correctly to trigger events. This tool is case-sensitive.
Note: If you use the console to send a test event and an error is returned, enter this command:
$TBSM_HOME/bin/rad_discover_schema ObjectServer
86 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 4. Creating and testing service instances
Uempty
Instructor demonstration
Instructor demonstration
InetBanking AlliedSteel
WebServer5
This diagram shows the service models that you create in Exercise 4.
88 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics
Lesson 4. Creating and testing service instances
Uempty
Student exercises
Student exercises
Summary
Now that you have completed this unit, you can perform the
following tasks:
Start and stop the major Tivoli Business Service Manager components
Explain how templates and services are used together to build service
models
Create event-based templates and rules
Create dependency templates and rules
Create service instances
Create dependencies between services
Test service models
Summary
90 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
3 Expanding service model functions
All files and material for this course (TM337, Tivoli Business Service Manager 6.1.1 for Administrators)
are IBM copyright property covered by the following copyright notice. Copyright IBM Corporation 2013
US Government Users Restricted Rights: Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
What this unit is about Business services can receive probe events from several
sources. The template rules must respond correctly to the
additional information. Templates can include multiple
rules, and you must decide how to assess the overall
service status when each rule evaluates to a different
status. Also, template rules provide an important tool for
calculating key performance indicators (KPIs) of business
operations. KPIs are then available for visual
representations of business services. In this unit, you
learn methods of extending service templates to provide
comprehensive representations of business services.
How you check your progress You can check your progress in the following ways:
Student exercises
References SC23-6041-09 Business Service Manager 6.1.1 Service
Configuration Guide
Objectives
When you complete this unit, you can perform the following
tasks:
Modify an incoming status rule to use multiple probe event fields to
identify a business service.
Create and modify business service identification fields to manage
different event formats.
Use output expressions to evaluate multiple rules in a template
Use the service heartbeat function to provide additional service
tracking
Create template rules to calculate numerical values to use as key
performance indicators (KPIs)
Show KPIs in the Service Navigation portlet
Aggregate child service KPIs with dependency rules
Calculate a weighted average with dependency rules
Copyright IBM Corporation 2013 2
Objectives
92 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 1. Identifying services with multiple event fields
Uempty
What this lesson is about Service templates use one or more rules to model
business service behavior. Template rules can respond to
business and monitor data from various sources. In this
lesson, you learn how to expand the capabilities of a
template rule so that the rule correctly identifies the
service instance to which an incoming event should be
applied.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Modify an incoming status rule to use multiple probe
event fields to identify a business service.
94 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 1. Identifying services with multiple event fields
Uempty
In the exercises in Service model basics, the service names corresponded to the short host name,
or Node field, of the incoming event. In this example, you deploy a second web server instance on
the host name WebServer1. The first instance uses the listening port 80, and the second instance
uses 8080. The initial business service instance that is created is called WebServer1. A second
service instance, called WebServer18080, is created to track the business status. Because monitor
probes report the same Node value for each web server instance, each event is applied to each
service instance. You must modify the WebServerStatusRule rule configuration to ensure that the
events are applied to the correct service instance. The probe events also include the listening port
value for the web server instance. Adding this event field to the instance name match in the rule
solves the problem.
WebServer1
Status=Good
Node=WebServer1, Alertkey=8080,Severity=0
WebServer18080
Event 1 Status=Good
WebServer1
Status=Bad
Node=WebServer1, Alertkey=80,Severity=5
WebServer18080
Event 2 Status=Bad
Copyright IBM Corporation 2013 5
This diagram illustrates an example of the limitations of matching the service name with only the
Node field from the incoming event. Events for either web server instance match the Node field for
the incoming event, causing the service status to be identically set for both service instances.
Adding the AlertKey field to the rule evaluation provides a mechanism to correctly identify the
service instance.
96 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 1. Identifying services with multiple event fields
Uempty
Modifying WebServerStatusRule
Modify the WebServerStatusRule:
Use the Node and AlertKey fields to
match service names.
Add AlertKey to the Selected
Instance Name Fields column.
Saved changes are immediately
propagated to the tagged services.
Modifying WebServerStatusRule
Modify the WebServerStatusRule rule, adding the AlertKey field in the Instance Name section.
When the rule modification is saved, every service instance that is based on the WebServer
template immediately inherits the modifications.
When the rule is modified, the additional instance name field information is tracked for each tagged
service instance. The new field is modified for each service instance in the Identification Fields
tab in the Service Editor. By default, both fields are populated with the instance name. Modify the
AlertKey field to match the default web server communication port.
98 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 1. Identifying services with multiple event fields
Uempty
To support a new project, you installed a test web server. To stage the project deployment, the
Quality Assurance team uses a web server that is installed on the same computer. Probes are
deployed for both installations. The Node field reported for both instances is the same. The
listening port is the only element that differentiates the two web server installations. The web
servers are tracked as two separate service instances. However, you must visually differentiate
them in Service Tree and Service Viewer portlets.
Adding the AlertKey field to the WebServerStatusRule rule solves the problem is sufficient to
differentiate the server instances. To visually differentiate the two instances, explicitly set the
Display Name. In this example, the WebServer1 service definition was modified to set the Display
Name to the string WebServer1:80. The second instance was created with the Service Name set
to WebServer18080 and the Display Name set to WebServer1:8080.
The monitor events for both services use the same Node value. Edit the Identification Field
values for each service instance to match the different AlertKey values, as shown in the following
table.
100 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 1. Identifying services with multiple event fields
Uempty
Event Details:
Identifier=abc123
AlertKey=8080
Node=WebServer1
Severity=5
AlertGroup=WebServerStatus
10
This slide shows the services with the modified display name value. The WebServer1:8080 service
tree entry indicates an event was received with AlertKey=8080 and Node=WebServer1 values.
The Identification Field definitions ensure that the event is applied to the correct service instance.
Instructor demonstration
Instructor demonstration
102 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 1. Identifying services with multiple event fields
Uempty
Student exercises
Student exercises
What this lesson is about Events do not always use consistent formats for event
field values. For example, if a probe cannot connect with
a DNS server, the monitored host field is reported as the
IP address. In this exercise, you learn how to modify the
service identification properties to match multiple event
field values.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Create and modify business service identification fields to
manage different event formats.
104 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 2. Adding service identification fields to match events
Uempty
References SC23-6041-09 Business Service Manager 6.1.1 Service
Configuration Guide
This lesson shows how you can configure the template rule to accommodate variations in the Node
value that is delivered in the monitor event. Both the host name and IP address must match the
server instance. You can solve this situation by adding a second set of identification fields.
106 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 2. Adding service identification fields to match events
Uempty
Add a second set of identification fields by modifying the service configuration. Because of the
configuration of the WebServerStatus rule, adding another identification rule entry involves
specifying both the AlertKey and Node field values. In this example, the AlertKey entry is the
same for both events. Configure the second entry with the IP address of the service host.
WebServer4
Node=WebServer4, Alertkey=80,Severity=0 Status=Good
Event 1
WebServer4
Node=192.168.1.1, Alertkey=80,Severity=5 Status=Bad
Event 2
In this example, you add a second service identification field that matches a Node value of
192.168.1.1 and an AlertKey value of 80. When the ObjectServer receives Event 1, the status of
WebServer4 is set to a Good state. When Event 2 is received, the WebServer4 state is correctly set
to a Bad state.
108 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 2. Adding service identification fields to match events
Uempty
Instructor demonstration
Instructor demonstration
The instructor has the option to demonstrate the creation and use of service identification fields.
Student exercises
Student exercises
110 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 3. Using output expressions to evaluate template rules
Uempty
What this lesson is about When templates contain multiple rules, you need a
method for evaluating all of the rules to determine the
overall service status. By default, the worst rule
evaluation determines the overall service state. In this
lesson, you learn how to create output expressions to
override the default state evaluation.
What you should be able to do After completing this lesson, you should be able to
perform the following task:
Use output expressions to evaluate multiple rules in a
template
112 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 3. Using output expressions to evaluate template rules
Uempty
InetBanking InetBanking
Rule 1 = Marginal Rule 1 = Marginal
Rule 2 = Marginal Rule 2 = Marginal
Overall Status = Marginal Overall Status = Bad
By default, the rules in the list are evaluated independently. You can override the behavior by
creating an output expression in the template. For this example, edit the WebApplication template
to create an output expression to evaluate the combined state of the
WebApplicationStatusDBClusterRule and WebApplicationStatusWebFarmRule rules.
For any monitored service, you must consider several factors to determine the overall performance
status. Creating more incoming status rules provide a more accurate service assessment.
However, you must evaluate the evaluated status of both rules together to determine the overall
service status. You use output expressions to logically evaluate multiple rules in the same template.
In the previous example, a single rule was created because the monitor events contained enough
information. In this example, the template has multiple rules that are defined for multiple monitor
sources. The example template contains two rules, each of which can evaluate to a Good,
Marginal, or Bad status. The diagram shows the required logical outcome, depending on each
possible rule state.
114 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 3. Using output expressions to evaluate template rules
Uempty
22
Output expressions are configured in the Output Expressions section of the template properties.
The expressions are applied only to rules in the template.
23
To build an output expression, you click the Output Expressions tab in the Service Editor portlet.
You can enter the SQL logic directly, or you can build the statement with the expression builder
tools. You must define the logic for evaluating the rules as Bad and Marginal. The down arrow icon
is used to insert the text to the left of the arrow. Using the icon to insert the selected value reduces
typographical errors.
116 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 3. Using output expressions to evaluate template rules
Uempty
Setting the Bad or Marginal output expression to False prevents any output expression evaluation
for the corresponding service state.
This slide shows the output expression logic. By default, a WebFarm1 and DBCluster1 status of
Marginal evaluates as Marginal for the InetBanking service.
118 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 3. Using output expressions to evaluate template rules
Uempty
WebServer1 WebServer1
Probe Status = Good
Down Event
Communication WebServer1
link down Status = Unknown
If a problem event is not received for a service instance, the assumption is that the service state is
unchanged since the last received event. But there might be situations where, for example, a server
and network are simultaneously out of service. If the last known state for the server was Good, the
service instance status remains set to Good. This example is an unusual occurrence for a fully
deployed monitor environment. However, if the critical nature of a service requires continuous
positive confirmation of availability, you can configure a service with Service Heartbeat.
In the service definition, you define a time interval within which events are always sent, regardless
of status. The service heartbeat indicates how often the service must receive a monitor status
event. If the heartbeat interval is exceeded, the service status color changes to purple, and the
service state is set to Unknown.
Configure the service heartbeat for a template by selecting the Report Unknown Severity if No
Events after the following number of seconds check box. Assign a value, in seconds, for the
heartbeat interval and save the template.
Hint: Every service instance that is based on a specific template inherits all template changes.
Set this option only if you must have every related service instance use the configured heartbeat.
Otherwise, create a duplicate template and assign the second template only to those service
instances that require heartbeat monitoring.
120 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 3. Using output expressions to evaluate template rules
Uempty
28
This screen image shows the effect of assigning the service heartbeat function to the WebServer
template. After the heartbeat threshold duration is reached, any service in a Good state changes to
an Unknown state.
Instructor demonstration
Instructor demonstration
122 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 3. Using output expressions to evaluate template rules
Uempty
Student exercises
Student exercises
What this lesson is about In this lesson, you learn how to create numerical template rules
to track key performance indicators from incoming data. Key
performance indicators provide an additional tool in developing
service models that reflect many types of business services.
You also learn how to show the output from numerical template
rules in the service navigation tree.
124 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 4. Numerical rules and key performance indicators
Uempty
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Create template rules to calculate numerical values to
use as key performance indicators (KPIs)
Show key performance indicators (KPIs) in the Service
Navigation portlet
Numerical modeling
In addition to service event status, performance measurements
can also be associated with a service.
Numerical calculations can be used as metrics in determining a
service status.
Calculated metrics can also be used as a key performance
indicator (KPI) in a business dashboard.
Example:
Calculate the response time for a web server service model with a
monitor event field value.
Numerical modeling
Tivoli Business Service Manager can evaluate any of the properties that are available to a service.
Key performance indicator values of a service can be shown in business dashboards.
126 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 4. Numerical rules and key performance indicators
Uempty
This screen capture displays the average response time for monitored web servers. This response
time is shown in a separate column in the Services section of the Service Navigation portlet. Key
performance indicators are another way to show business service data, in addition to the event
status.
34
You create numerical rules by clicking the Create Incoming Status Rule icon in the template
editor. Then, you select Based on a Numerical Value for the rule type.
128 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 4. Numerical rules and key performance indicators
Uempty
The rule is configured similarly to the event-based incoming status rule. For this example, use the
AlertGroup field for the filter value. This rule evaluates events where AlertGroup =
WebServerResponseTime.
Use the data from the ITMTime event field as the numerical
value.
Optionally, set a numerical threshold value for assigning
Marginal and Bad status. If the threshold is matched or
exceeded, the appropriate status is set.
36
In this example, the value in the ITMTime field is a measurement of response time that is provided
by a monitor. You configure how the rule evaluates the numerical value. An expression is useful for
formatting or typecasting numbers to be displayed. For example, to cast a floating point field value
to an integer, use this expression:
int(fieldname)
To show this value as a floating-point number with three significant digits, use this expression:
float(int(fieldname)*1000/1000)
You can build more complex expressions with multiple fields from the ObjectServer by selecting the
Advanced Filter option. Optionally, you can assign values for the Status section. In this example,
the value of the ITMTime field is tested against a Marginal threshold of 10 and a Bad threshold of
20. If a threshold is exceeded, the overall rule status is set to the corresponding status.
130 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 4. Numerical rules and key performance indicators
Uempty
The Service Tree portlet can display any calculated value from a numerical rule as a column. To
change the columns that are displayed in the dashboard, modify the dashboard definition with the
Tree Template editor. The Tree Template editor icon is accessed from the Services section of the
Service Navigation portlet.
You can create multiple custom service trees and apply them to modify service tree views. The
default tree template that is used in Service Availability and Service Configuration pages is labeled
ServiceInstance.
132 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 4. Numerical rules and key performance indicators
Uempty
Adding a column
Click the Add new Tree Column icon to add columns to the
service tree.
Enter a column name.
Change the column order with the arrow icons.
39
Adding a column
3. Optional: Use the arrow icons next to each column definition to change the order in which the
columns are shown.
1. Select a template.
To assign a measurement to the new column, you must associate a template with the new column.
For this example, select the WebServer template. When selected, only services with the
WebServer template show a response time value.
3. Show this measurement by selecting the Response Time column from the Column Display
Name menu. Response Time is the column that is created in the previous step.
134 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 4. Numerical rules and key performance indicators
Uempty
41
To test the numerical rule, you send a test event to a service that is based on the WebServer
template. The Response Time column is updated with the supplied event value.
Reprocessing events
By default, events are processed:
When received by the ObjectServer
When the severity changes for an existing ObjectServer event.
The severity of the last received event for a service is stored in
RAD_RawInputLastValue.
If a probe event does not include a Severity value, you must
create a mechanism to trigger a reevaluation of an existing
event.
Reprocessing events
If you want the ObjectServer to process an event that is already processed, change the severity of
the event.
For example, after you send events to populate the response time for services with
Node=WebServer1, run the nco_sql commands on the ObjectServer:
update alerts.status set ITMTime=99 where Node=WebServer1;
go
update alerts.status set RAD_RawInputLastValue=6 where Node=WebServer1;
go
This change forces events to be reprocessed if they come in with a response time set in the
ITMTime field.
136 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 4. Numerical rules and key performance indicators
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
138 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 5. Aggregating numerical rules
Uempty
What this lesson is about In this lesson, you learn how to use numerical
aggregation rules to use a child service KPI to calculate a
parent service KPI. You also learn how to show numerical
values for a parent service in a service navigation tree.
What you should be able to do After completing this lesson, you should be able to
perform the following task:
Aggregate child service KPIs with dependency rules.
In previous exercises, you created aggregation rules for dependent services that are based on child
service status. You can create the same type of aggregation rules with numerical calculations for a
service.
140 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 5. Aggregating numerical rules
Uempty
47
In this slide, the WebFarm1 and WebFarm2 services show numerical values that are based on the
dependent services. The average response time for all dependent WebServer instances is
calculated and shown next to the WebFarm service. This value was obtained by adding a rule to the
WebFarm template and displaying the numerical value of the rule calculation.
142 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 5. Aggregating numerical rules
Uempty
To add the new numerical aggregation measurement that is created in the WebFarm template to
the service tree, complete these steps with the Tree Template Editor:
1. Select and add the WebFarm template as a selected template.
This example shows the Services tree after modifications with the Tree Template Editor. Refresh
the Services view to apply the changes to the service tree.
144 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 5. Aggregating numerical rules
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
146 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 6. Calculating weighted averages
Uempty
What this lesson is about The performance effect of some child services do not
always have an equal effect on a parent service. For
example, a web farm might include a web server that
processes three times the transaction load of the other
web servers. To calculate the aggregation effect of the
different child service capacity, you create a weighted
average. This lesson shows you how to create a weighted
average for a numerical aggregation rule.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Calculate a weighted average with a dependency rule
148 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 6. Calculating weighted averages
Uempty
WebFarm1 WebFarm2
3000 Transactions/hour 1000 Transactions/hour
You can modify the average function with a multiplier expression in a template. Services inherit a
default value from the template. The default value is modified in the service properties and used in
the numerical aggregation rule definition. For this example, WebFarm1 supports three times the
work load of WebFarm2. The response time value that is provided by WebFarm1 must carry three
times the weight of the WebFarm2 average response time.
You can use a multiplier expression to weight the calculations that are provided by the child service
rules. Because the weighting factor applies to each WebFarm instance, a parameter is created in
the WebFarm template. Under the Additional tab in the template editor, click the New Parameter
icon. Create the parameter name and assign a default value of 1.
150 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 6. Calculating weighted averages
Uempty
For this example, create a template that is called AllWebFarms. This template contains a
numerical aggregation rule, with WebFarm as the child template and the
AverageResponseTimeMetricRule as the child service rule that provides the numerical
calculation value. Select Average for the Aggregation Function and enter the name of the
multiplier expression, WeightParameter. Save the rule and the template.
Based on the WeightParameter definition in the WebFarm template, each WebFarm service
instance initially has the value of 1. To override this default value, edit the service definition. For this
example, change the WeightParameter value for WebFarm1, found under the Additional tab, to 3.
The number three represents the additional work that is provided by WebFarm1.
152 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 6. Calculating weighted averages
Uempty
To view the effect of a weighted average calculation, you create a service instance that is based on
the AllWebFarms template, called AllWebFarmServices, using WebFarm1 and WebFarm2 as
child services. After you add the weighted average value to the Response Time column, the value
is closer to the WebFarm1 response time than the unweighted average of 19.666. This value
shows that the response time value for WebFarm1 has a greater effect on the overall evaluated
response time for both WebFarm instances.
Instructor demonstration
Instructor demonstration
154 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
3 Expanding service model functions
Lesson 6. Calculating weighted averages
Uempty
Student exercises
Student exercises
Summary
Now that you have completed this unit, you can perform the
following tasks:
Modify an incoming status rule to use multiple probe event fields to
identify a business service.
Create and modify business service identification fields to manage
different event formats.
Use output expressions to evaluate multiple rules in a template
Use the service heartbeat function to provide additional service
tracking
Create template rules to calculate numerical values to use as key
performance indicators (KPIs)
Show KPIs in the Service Navigation portlet
Aggregate child service KPIs with dependency rules
Calculate a weighted average with dependency rules
Copyright IBM Corporation 2013 61
Summary
156 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
4 Service level agreements
What this unit is about A service level agreement (SLA) typically defines an
agreement, between a provider and a customer, that
specifies an acceptable level of service for a resource.
Tivoli Business Service Manager provides tools to define
and track SLAs for any service instance. In this unit, you
learn about the types of SLAs that are supported. You
learn how to configure SLAs and apply them to one or
more services. Most SLAs include routine maintenance
windows for a service. The maintenance windows are not
counted against an SLA calculation. You learn how to
create and apply maintenance windows to business
service instances.
How you check your progress You can check your progress in the following ways:
Student exercises
References SC23-6041-09 Business Service Manager Version 6.1.1
Service Configuration Guide
Objectives
When you complete this unit, you can perform the following
tasks:
Describe the types of service level agreements (SLAs) that are tracked
in Tivoli Business Service Manager 6.1
Create and view duration SLAs
Create and view cumulative duration SLAs
Create and view incident count SLAs
Configure SLA revenue penalty tracking
Create and use maintenance windows
Objectives
158 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 1. Creating service level agreements
Uempty
What this lesson is about In this lesson, you learn the concepts of Service Level
Agreements (SLAs) in Tivoli Business Service Manager.
You learn the function of, and how to create, the three
types of supported SLAs.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Describe the types of service level agreements (SLAs)
that are tracked in Tivoli Business Service Manager
6.1.1
Create and view duration SLAs.
Create and view cumulative duration SLAs.
Create and view incident count SLAs.
160 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 1. Creating service level agreements
Uempty
Service level agreements (SLA) provide benefits to a business, such as the following ones:
Reducing the opportunities for penalties because of SLA violations
Providing accurate metrics for a business to use to set internal goals for customer service
Tivoli Business Service Manager generates service-related events in the ObjectServer if threshold
values in an SLA are approached or exceeded. You can use a filter with the Active Event List to
monitor service-related events. SLA Warning events provide an opportunity to take corrective
action before the SLA is compromised. SLA Violation events indicate that an SLA is in a violation
state.
162 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 1. Creating service level agreements
Uempty
Any defined SLA continuously tracks service availability. When you set warning thresholds,
operations staff have time to determine and solve the problem before an SLA violation occurs.
When SLA violations occur, Tivoli Business Service Manager can track a predefined penalty cost.
Tivoli Business Service Manager provides the following three methods for tracking service level
agreements:
Duration: Any affected service instance outage is tracked from the time a service changes to a
Bad state until the Bad state is cleared.
Cumulative duration: The total accumulated duration violations are tracked for a configured
period.
Incident: Any time a service instance status changes to a Bad state, regardless of duration, it is
counted as an incident.
164 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 1. Creating service level agreements
Uempty
A duration-based SLA tracks one or more monitored services continuously. Violations and
warning values are set to track how long an outage occurs at any time. The tracked duration begins
when a service changes to a bad state.
A cumulative duration-based SLA tracks one or more services over a specified time. During that
period, any service outage durations are accumulated. Warnings or SLA violation events are also
generated if the accumulated violations exceed the value that is defined in the SLA.
166 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 1. Creating service level agreements
Uempty
10
An incident count SLA tracks one or more services over a specified time. During that period, any
transition of a service status to a Bad state, regardless of the duration, is counted as a single
incident. Warning or violation events are generated if the incident count exceeds the value that is
defined in the SLA.
11
You configure an SLA by editing the service template in the Service Editor. The status of the SLA
can then be tracked from the viewer portion of the Service Editor.
Details are shown when you click the indicator or when you select a service in the Service
Navigation portlet.
A gauge shows the duration-based SLA status. Colors are used to indicate status.
168 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 1. Creating service level agreements
Uempty
12
A duration-based SLA measures the outage when the service status is Bad. In the example, brief
outages are considered acceptable. However, if they exceed 1 minute, the service SLA status is set
to Marginal. If they exceed 2 minutes, the SLA status is set to Bad. A new alert is sent to the
ObjectServer, notifying the user of the specific instance and calculation. In this example, the service
is down for 2:03. The status is also seen in the navigation tree of the services, in the Time column.
SLA definitions are defined for a template in the SLA tab in the
Service Editor portlet.
Set the outage duration thresholds.
Select the check box to enable the SLA in the template.
13
To configure SLA settings, edit the template. This example uses the WebApplication template. Use
the form in the SLA tab to define one or more SLA types. Complete these tasks to create a
duration-based SLA:
1. Select Calculate duration based SLA violations.
2. Indicate how long the service violation must continue to cause an SLA Marginal state and what
duration causes an SLA Violation state.
170 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 1. Creating service level agreements
Uempty
14
A cumulative duration-based SLA is configured in the same manner as the single incident duration
SLA. To configure a cumulative duration-based SLA, complete these tasks:
1. Select the template to edit and select the SLA tab.
3. Set a time duration for warnings and violations. You can define combinations of months, days,
hours, and minutes.
15
An incident count SLA is configured in the same manner as the duration SLA. To configure an
incident count SLA, complete these tasks:
1. Select the template to edit and select the SLA tab.
3. Select Duration violations only to consider only a duration violation as an incident. Selecting
All violations considers any time a service changes to a bad state.
4. Set a time duration for warnings and violations. You can define combinations of months, days,
hours, and minutes.
172 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 1. Creating service level agreements
Uempty
A network service provider charges different fees for different SLAs. An IT department or data
center can have more than one SLA, depending on the customer contract or business unit. You can
define one or more SLAs, each of which you can assign to a specific instance of a business service.
Click the New Service Level icon to add another set of service
level definition forms.
Standard is the default SLA.
At the top of the SLA section in the template editor, add a service level name. By providing multiple
SLA definitions at the template, you can select an appropriate SLA level when you create a service
instance.
174 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 1. Creating service level agreements
Uempty
Add SLA definitions for a template with the template editor. Services that are based on templates
with multiple SLAs defined can select an SLA on an individual basis.
When creating a service instance, you select the service level from the Service Level menu in the
Service Properties section.
176 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 1. Creating service level agreements
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercise
178 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 2. Testing service level agreements
Uempty
What this lesson is about In this lesson, you learn how to trigger and test SLAs for
a service. You learn to analyze the visual changes to the
service model in the console and how to verify the SLA
operation. You also learn how to configure and use the
revenue penalty feature for an SLA.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Create and view duration SLAs
Create and view cumulative duration SLAs
Create and view incident count SLAs
Configure SLA revenue penalty tracking
180 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 2. Testing service level agreements
Uempty
23
An outage is based on the service that is evaluated in a Bad state. A duration SLA measures the
length of the current outage. In this screen image, the change in the icon status is shown as the
SLA status changes from a Warning to a Violation state.
24
In this example, the top-level icon for InetBanking shows the cumulative duration violation status
with the bar next to the sigma symbol. The single, or current, incident duration violation is shown
with the red line.
182 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 2. Testing service level agreements
Uempty
No single-incident duration
outage is currently being
tracked.
25
This screen capture shows the results of an incident count-based SLA violation. The total incident
count over a specified period is displayed under the cumulative duration status bar showing a Good
status. The bar showing a Violation status represents two service status changes to a Bad state
within a 30-minute time window. No change in the duration violation bar graph is displayed because
the overall service state is set to Good.
Revenue penalties
Tivoli Business Service Manager can calculate revenue penalties
based on SLA violations.
The penalty calculation uses the HourlySLAPenalty service parameter.
The default value for the HourlySLAPenalty parameter is set in the
template properties.
The service properties setting overrides the template default.
26
Revenue penalties
You can include an hourly SLA penalty calculation in SLA calculations. You set the penalty
multiplier at the template level as either a default for all services of the template, or individually at
the service level.
184 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 2. Testing service level agreements
Uempty
27
SLA penalty calculations are processed internally on the Tivoli Business Service Manager server
and shown in an attribute duration event. The number that is shown summarizes the percentage
of availability for a selected service instance. You can view the value by right-clicking a service and
selecting the SLA tab in the Services Details portlet.
28
You can reset the SLA state engine for a template by clicking Clear at the bottom of the SLA form.
The SLA timers for all services that are based on the template are reset.
186 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 2. Testing service level agreements
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercise
188 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 3. Creating and using maintenance schedules
Uempty
What this lesson is about Services that are part of an SLA must periodically be out
of service for scheduled maintenance. Service availability
during scheduled maintenance must not count against an
SLA calculation. Tivoli Business Service Manager
provides a maintenance window tool that temporarily
suspends SLA calculations for a service. In this lesson,
you learn how to create and apply an SLA maintenance
window. You then send test events and verify that the SLA
calculation is not affected.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Create and use maintenance windows.
190 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 3. Creating and using maintenance schedules
Uempty
Maintenance schedules
Maintenance schedules prevent SLA calculations.
Maintenance schedules are defined with a time window. Time
windows have one of two properties:
Repeating: Time windows occurring at regular intervals.
Absolute: A single time window occurring on a specific date.
Maintenance schedules are configured and set in the Service
Editor or with command-line tools.
All maintenance schedules are available to all services.
Maintenance schedules
You cannot calculate a planned outage of a monitored service against an SLA. These time periods,
or maintenance windows, can be one or more types of time windows, such as these examples:
A combination of time windows
You set these window definitions at the service level. Other service instances can share them. You
can also set maintenance windows at the top of a service model hierarchy and cascade them down
to all child services.
33
In this example, you define a window for weekly backups for InetBanking servers. For this type of
maintenance, you complete these tasks:
1. Edit the service instance in the Service Editor portlet.
192 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 3. Creating and using maintenance schedules
Uempty
Continuing the example, create a time window definition. Complete these tasks:
1. Enter a schedule name.
4. Click OK.
35
Three ways to set SLA maintenance schedules for services are as follows:
Create a maintenance schedule while editing the service definition. After you create the
maintenance schedule, select the definition from the Maintenance Schedule menu.
From the Service Viewer, right-click a service instance and select Maintenance window tools
> Schedule maintenance. A window is displayed where you can create and apply
maintenance windows. You can set the maintenance schedule for either a single service
instance, the service and all children, or only the children.
Use RAD shell commands to create and set maintenance schedules.
194 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 3. Creating and using maintenance schedules
Uempty
36
When you have a maintenance window in effect for a specific service, no incoming status events
are processed to evaluate the service status. The service icon turns blue to indicate that it is in
maintenance mode.
Instructor demonstration
Instructor demonstration
196 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements
Lesson 3. Creating and using maintenance schedules
Uempty
Student exercises
Student exercises
Summary
Now that you have completed this unit, you can perform the
following tasks:
Describe the types of service level agreements (SLAs) that are tracked
in Tivoli Business Service Manager 6.1
Create and view duration SLAs
Create and view cumulative duration SLAs
Create and view incident count SLAs
Configure SLA revenue penalty tracking
Create and use maintenance windows
Summary
198 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
5 Data fetchers
5 Data fetchers
What this unit is about Business service models must be able to respond to
business data and monitor events. Templates can have
multiple rules, which requires a complex evaluation of rule
states. Template rules can also calculate key
performance indicators (KPIs). KPIs are then available to
be included in visual representations of business
services. This unit demonstrates a function that is called
a data fetcher. Data fetchers extend service template
functions to provide comprehensive representations of
business services.
How you check your progress You can check your progress in the following ways:
Student exercises
References SC23-6041-09 Business Service Manager Version 6.1.1
Service Configuration Guide
Objectives
When you complete this unit, you can perform the following
tasks:
Create data sources
Create a data fetcher
Create data fetcher template rules to retrieve data from external
databases
Objectives
200 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
What this lesson is about In this lesson, you learn how to configure business
services to query and evaluate business data in a
template rule. The function that is used to retrieve the data
is called a data fetcher. A data fetcher requires a
connection to a database. You configure a database
connection with an object called a data source. You
configure the data fetcher to retrieve specific records from
a database. You then learn how to use the retrieved data
with an incoming status rule. Last, you learn how to
modify the Service Navigation portlet tree template to
show the calculated rule KPI.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Create data sources
Create a data fetcher
Create data fetcher template rules to retrieve data
from external databases
202 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
An important use of external data with Tivoli Business Service Manager is to populate a numerical
attribute for a service template. Tivoli Business Service Manager can use this value to determine a
service status, as with a monitor event.
Retrieve trouble ticket status information from a database and show the
number of open tickets assigned per service.
Copyright IBM Corporation 2013 5
In this example, the screen capture shows the numerical value in a column labeled Open Tickets.
This column represents values for open ticket instances from an external trouble ticket system. The
value is derived from data that is taken from an external database.
204 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
To show external database information to evaluate service models, the DB2 database in the data
server is used. This database is configured with sample trouble ticket data.
For the previous example, a final numerical value is derived by counting the number of rows with a
class status of Open. For example, you might update a service status if the number of open
WebServer tickets exceeds 2.
206 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
3. Create a numerical rule for the WebServer template. This template references the data fetcher.
4. Add a column to the Service Navigation tree to show the ticket data.
To create a data source, click the Create a Data Source icon in the Data section of the Service
Navigation portlet. In this example, the predefined data source that is called
troubleticketsDataSource is used. For any data source, provide this information:
SQL Type: The type of target database.
Data Source Name: A text string that represents the data source.
Username: The user name authorized to read data from the data source database.
Port: The TCP/IP port that the data sources uses to listen for data requests.
208 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
The simplest definition for a data fetcher is to fetch the data daily at a specified time. To define an
interval, Tivoli Business Service Manager fetches data at the multiplier x fetching time. For
example, assume 30 seconds to retrieve the data, with a multiplier of 10. In this case, the product
retrieves data every 5 minutes (30 seconds x 10 = 300 seconds, or 5 minutes). The minimum and
maximum fetch rate, if applicable, override this period.
To create a data fetcher, click the Create a Data Fetcher icon in the Data Fetcher section of the
Service Navigation portlet. For a recurring fetch schedule, select the appropriate section of the form
and specify these items:
Minimum Interval Between Fetches: The minimum time lapse between data fetches.
Maximum Interval Between Fetches: The maximum time lapse between data fetches.
Fetcher Interval Multiplier: The multiplied time, in seconds, that the data fetcher waits
between fetches. The actual time depends on the length of time that is needed to complete a
single fetch.
To configure a single daily data fetch, select that section of the form and specify the time of the
fetch.
210 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
Build the query that is used with the data source. If you know the SQL query, you can enter it
directly in the SQL query section of the data fetcher definition. Tivoli Business Service Manager
also provides a Query Builder utility. The opening page of the Query Builder wizard is shown in the
screen capture. For this example, troubleticketsDataSource is used. Select one or more
database tables. For this example, select the TBSMDEMO.TICKETS table and click Next.
Select the fields for the query. Use only the required fields for the data calculations to reduce the
query load. For this example, select the LOWLEVELSERVICEID and STATUS fields and click
Next.
212 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
Define a SQL WHERE clause to limit the data that is retrieved by the fetcher. In general, limit the
amount of data to the minimum needed. In this example, only open tickets are counted. Set the
WHERE clause to STATUS=Open, click Apply, and click Next.
Define measurements to be collected, if necessary, from the Create Metrics section. For this
example, count the open tickets for each LOWLEVELSERVICEID and assign the value to
NUMOPENTICKETS.
214 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
After selecting a function, select the Group By fields to organize the data. You can also order the
data, but this action typically does not affect the function of the data fetcher. In this example, the
results are grouped with the LOWLEVELSERVICEID and STATUS columns. Click Next.
The query builder wizard optionally orders the data in ascending or descending order. Click Finish
to complete the wizard.
216 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
The completed query is inserted in the SQL Query field. You can preview the data set. Click View
to the right of View Data. Verify the results and save the data fetcher definition.
After you save the data fetcher definition, it is listed in the Data Fetcher section of the Service
Navigation portlet. To override defined time constraints and immediately test the data fetcher,
right-click the data fetcher entry and click Fetch Now from the menu.
218 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
Use the
LOWLEVELSERVICEID
field value to match
service instances.
Use the
NUMOPENTICKETS
field value for the rule
metric.
To use the fetched data, you must create a status rule. This process is like what you used in the
previous creation of incoming status rules that are based on incoming events. For the
OpenTicketsRule status rule, the data fetcher is the source of the data, rather than an incoming
event. You can preview the data to verify that it is presented as you expected.
The Instance Name field is where you match the LOWLEVELSERVICEID field from the database
to the service name. You can also place an extra filter on the data.
You can use the numerical value that is provided by the rule as a KPI. You can also use the value
as part of a more complex evaluation, or the basis for setting the service status. For this example,
set threshold values for setting the Bad and Marginal status.
220 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
To add business data to the service tree, add a column to show the new measurement in the
Services section of the Service Navigation portlet. Service tree columns are added with the
Template Tree Editor.
The number of open tickets matching the WebServer instances are shown
on the service tree.
Copyright IBM Corporation 2013 23
The screen capture shows the calculated numerical value for each matching WebServer instance.
If the database is in a production environment, the calculation and show changes with each data
fetch.
222 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 1. Data fetcher overview
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
224 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 2. Dependency rules and data fetchers
Uempty
What this lesson is about In this lesson, you learn how to aggregate child service
KPIs that are calculated from a data fetcher. You then
learn how to modify the Service Navigation portlet tree
template to show the aggregated value in the service tree.
What you should be able to do After completing this lesson, you should be able to
perform the following task:
Create data fetcher template rules to retrieve data from
external databases
References SC23-6041-09 Business Service Manager Version 6.1.1
Service Configuration Guide
All child service numerical rule values are available to parent services. The parent services can
aggregate the child data and show the numerical value in a service tree.
226 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 2. Dependency rules and data fetchers
Uempty
Developing a service model to aggregate all web
servers
You can use templates and services in multiple service models.
To aggregate metrics from all web server instances, create a
template called AllWebServers.
For this task, you calculate the sum of all open WebServer
trouble tickets.
You use a numerical aggregation rule. Each WebServer
provides an individual count of open tickets with the
OpenTicketsRule.
Services and service templates can be configured in multiple service and template models. A
parent service in one model can be a child service in another model. For this example, calculate the
sum of all open trouble tickets for all defined WebServer instances. To aggregate all WebServer
instances, you must create a parent template with the WebServer template defined as the child.
You then assign all WebServer instances as dependent services. Show the sum in the Open
Tickets column of the service tree.
For this example, you create a numerical aggregation rule for the AllWebServers template. You
assign the WebServer template as the child, and select OpenTicketsRule as the child metric rule.
Then, you select Sum as the aggregation function. In this case, do not assign any status threshold.
228 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 2. Dependency rules and data fetchers
Uempty
For this example, create a service instance that is called AllWebServersOpenTickets, based on
the AllWebServers template. Assign all WebServer instances as dependent services.
The sum is available as a KPI when the service instance is defined. For this example, open the
Tree Template Editor and assign the AllWebServersOpenTicketsSumRule value to the Open
Tickets column.
230 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 2. Dependency rules and data fetchers
Uempty
This screen image shows the sum in the Open Tickets column. The value can be used in multiple
service tree views.
Instructor demonstration
Instructor demonstration
232 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers
Lesson 2. Dependency rules and data fetchers
Uempty
Student exercises
Student exercises
Summary
Now that you have completed this unit, you can perform the
following tasks:
Create data sources
Create a data fetcher
Create data fetcher template rules to retrieve data from external
databases
Summary
234 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
6 External Service Dependency Adapter
rules
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
What this unit is about External Service Dependency Adapters (ESDAs) rules
dynamically create service model hierarchies with
business data. ESDA rules go beyond the capabilities of
data fetcher rules, supporting multiple database queries
and data enrichment. ESDA rules create parent and child
service instances at all levels of a template model.
How you check your progress You can check your progress in the following ways:
Student exercises
References SC23-6041-09 Business Service Manager Version 6.1.1
Service Configuration Guide
Objectives
When you complete this unit, you can perform the following
tasks:
Describe when to use External Service Dependency Adapters
Configure External Service Dependency Adapter rules
Use policies in External Service Dependency Adapter rules to build
child services
Demonstrate how to trigger External Service Dependency Adapters to
build a service model
Objectives
236 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 1. External Service Dependency Adapter overview
Uempty
What this lesson is about In this lesson, you learn how ESDA rules differ from
incoming status rules and dependency rules. You learn
how to configure an ESDA child rule and how to test the
rule. You learn about the concept of transient and
permanent service definitions.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Describe when to use External Service Dependency
Adapters
Configure External Service Dependency Adapter rules
Demonstrate how to trigger External Service
Dependency Adapters to build a service model
238 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 1. External Service Dependency Adapter overview
Uempty
ESDA rules are used when the business service model services change frequently and when the
data that is used to build the services requires complex database queries. You can use
Netcool/Impact policy scripts to enhance the service instances for every level of a service model.
GetThereFast
Service
Template
ESDA rule
Incoming status rules and dependency rules can query only a single data source and track services
for a single level of a service model. ESDA rules can query multiple data sources and can build
services dynamically at all levels of a service model. ESDA rules can use Netcool/Impact policy
scripts, which provide a tool to enrich the service model information before the creation of the
services.
240 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 1. External Service Dependency Adapter overview
Uempty
ESDA operation
Service models are built at the following times:
When viewed in a console
When an event is received by a member service
Each ESDA rule is designed to use one service in the service
model as a seed service.
The seed service is an anchor point from which the other
service model instances are derived.
Each level of the model hierarchy is derived by multiple
database queries or with information obtained in previous
queries.
Data sources must be configured before starting the rule.
ESDA operation
Data fetchers are limited to a single database query to retrieve a data set. External Service
Dependency Adapter (ESDA) rules extend the function, supporting multiple database queries and
data enrichment. Service instances are created as needed, either by receiving a view request or in
response to a monitor event. ESDA rules are defined for all levels of a template model. ESDA rules
use a predefined seed template as a known anchor for deriving all other levels of the model.
Service instances can be created to operate in one of two modes: persistent or transient. All
service instances that are created in previous units of this course were created as persistent.
Persistent service instances are stored in the DB2 database in permanent tables. Transient
services are stored in temporary tables and are considered valid for 60 minutes (default). The
validation period is reset if a service is viewed or receives a monitor event. If a persistent child
service is redefined with a different parent, the service must be removed from the parent definition
and then associated with the new parent. For a transient service, the parent-child relationship can
be dynamically rebuilt as needed. By default, all services that are created with ESDA rules are
transient.
242 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 1. External Service Dependency Adapter overview
Uempty
Seed services
Every ESDA needs a seed service to anchor the service
model.
The seed service should be persistent.
The seed service is used as the anchor point for deriving all
other service instances.
It can be configured for any level of the service model.
Seed services
To derive all elements of a service model on demand, one service instance is designed as a seed.
The rule configuration is designed to expect the seed service to be consistently available. The seed
is used as an anchor point for all queries and calculations throughout the rule. Any level of the
service model can be the seed. The choice is dependent on the data model used.
For this example, a four-level template model is configured. The top level is designed as the seed
for the model. Develop the rule to create child services, starting at the top. A complete ESDA rule
also contains rules to create all parent services when any child service is known. You create all
parent and child rules in the seed template.
244 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 1. External Service Dependency Adapter overview
Uempty
For this example, a database contains customer and contract information for router and port
telecommunication services. Other tables contain information that is related to either the
CUSTOMER column or the CONTRACT column. For this example, the service seed instance is
directly related to the CUSTOMER field. All other services in the service model are derived from
this value.
11
ESDA rules are created in the Service Editor portlet. You create the ESDA rule in the CUSTOMER
seed template by clicking the Create ESDA rule icon in the rule toolbar.
246 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 1. External Service Dependency Adapter overview
Uempty
The ESDA rule form consists of multiple Child rule and Parent rule definitions for each level of the
template model. Child rules create child services for a template parent, and Parent rules create
parent services for a template child. Child rules are listed to the left of the form as a vertical stack of
tabs. Parent rules are listed to the right of the form as a vertical stack of tabs. The center section of
the form changes, depending on the Child rule or Parent rule selected.
For each Child rule, variable values are available for use in the data query that is used to determine
the child services. Variable names are bracketed with two underscore characters.
__displayname__
__description__
These variables are for the name that is defined for the parent service instance, display name, or
description. For example, for the Customer Child rule, __serviceinstancename__ is the Customer
seed instance name.
Any parameters that are defined in the Additional tab for a service are also available as variable
names. The names are passed to the rule in the form __AdditionalParameterName__. In addition
to the variable name, the data set that is returned with the SQL Query value is available for child
service creation.
248 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 1. External Service Dependency Adapter overview
Uempty
In this example, you create the ESDA rule in the Customer template. All Child rules and Parent
rules are defined in this form. Using the previously shown database table, you query the table to
return all CONTRACT records where the CUSTOMER field matches the __serviceinstancename__
value. You create a seed service instance that is called IBM and assign it to the Customer template.
To trigger an ESDA rule, you complete the Child rule configuration. You trigger the rule to process
data by viewing all levels of the service model, starting with the seed instance.
250 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 1. External Service Dependency Adapter overview
Uempty
When the example IBM seed service tree entry is expanded, the Customer child rule is triggered.
The rule queries the defined data source with the following query:
Return all CONTRACT records where CUSTOMER = __serviceinstancename__ = IBM
For each record returned, you create a transient service instance with the value of the CONTRACT
record.
Instructor demonstration
Instructor demonstration
252 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 1. External Service Dependency Adapter overview
Uempty
Student exercises
Student exercises
What this lesson is about In this lesson, you learn how to expand the scope of the
ESDA rule by configuring a child rule for the next level of
the template model. The child services at the next level of
the service model are derived from a SQL query to a
second table in the target database.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Configure External Service Dependency Adapter rules
Demonstrate how to trigger External Service
Dependency Adapters to build a service model
254 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 2. Expanding ESDA rules
Uempty
References SC23-6041-09 Business Service Manager Version 6.1.1
Service Configuration Guide
Child rules are defined for every parent level of the template
model.
Parent rules are defined for every child level of the template
model.
To continue the ESDA rule definition, define the Contract Child rule. This Child rule creates
Connection child services for every defined Contract parent service. Open the ESDA rule in the
Customer template.
256 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 2. Expanding ESDA rules
Uempty
For this level of the template model, you use related tables in the database to determine which child
services to create. In this example, the parent service, the contract is a key field in the
TBSMDEMO.TRAINESDA_CONNECTIONS table. You must determine a connection service for
any related contract service. A connection is a logical name that indicates the port and router pairs
for a telecommunication service. It is created by concatenating related ANODE, APORT, BNODE,
and BPORT records.
To create a contract child rule, you click Contract in the Child rules column. You create the query to
determine the components of a Connection name and then create a concatenation expression for
the instance name and display name.
258 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 2. Expanding ESDA rules
Uempty
You invalidate the previous child services that are created by clicking the seed service and clicking
Invalidate in the Service Editor.
To view the contract Child rule operation, you expand the Customer and Contract levels of the
service model. Each parent expansion creates corresponding child services.
260 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 2. Expanding ESDA rules
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
262 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 3. Using policy scripts
Uempty
What this lesson is about In this lesson, you learn how to use a Netcool/Impact
policy script in an ESDA rule to build the child services.
Policy scripts provide greater flexibility when evaluating
the data used to build the child services. In this example,
the parent service name contains the information that is
required to derive the child service names. Parsing the
parent rule name for the child service names eliminates
the requirement to query a database to find the
information.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Use policies in External Service Dependency Adapter
rules to build child services
Demonstrate how to trigger External Service
Dependency Adapters to build a service model
264 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 3. Using policy scripts
Uempty
The example service model uses two Port child services for every Connection parent service. By
default, only one child service can be created for every parent service. Using a policy in the
Connection child rule solves the limitation. A policy can complete complex calculations, more
database queries, and data enrichment to determine child services.
2. Click Edit Policy to define the policy operation. For this example, pass the parent service name
to the policy by entering __serviceinstancename__ in the SQL Query field. Using the parent
instance name eliminates an extra SQL query in the ESDA rule.
266 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 3. Using policy scripts
Uempty
The parent service name in the __serviceinstancename__ variable is referenced in the policy with
the name ExternalFilter. The ESDA data source name is referenced in the policy with the
ExternalQueryDataType variable name.
The policy passed the Contract service instance name from the __serviceinstancename__ variable
in the Child rule SQL Query field. The variable is assigned to the ExternalFilter array in the policy.
The value is then passed to a regular expression function. The function extracts the parts of the
parent service name that are used to create the child Port services.
268 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 3. Using policy scripts
Uempty
The Connection instance name is derived from the concatenation of data from a database query.
The policy parses the name for the Port name values, rather than creating another database query.
A policy regular expression is used to extract the text strings.
Passing parameters
NextLevelOrgNodes: This parameter is required. Each member
of this array is used by the ESDA rule to create an instance.
For each member of the array, the object attributes can be
used in the Results section of the ESDA configuration.
AttributesList: This parameter is required. It sets additional
instance parameters with the following properties:
_TagList: A list of templates to add to an instance
_PrimaryTag: The primary template for the instance
_RemoveTagList: A list of templates to remove from an instance
AttributesList and NextLevelOrgNodes are coordinated by the
index number for each array of objects.
Passing parameters
All ESDA policies must return service instance data in an array called NextLevelOrgNodes. Each
service is created as each element in the array is processed by the rule.
270 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 3. Using policy scripts
Uempty
The last section of the policy uses a looping construct to assign the Port template to each entry in
the NextLevelOrgNodes array.
To save the policy script, you click the Check Syntax icon before closing the policy editor. You are
prompted for a policy name when saving the file.
272 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 3. Using policy scripts
Uempty
Invalidate the seed service and expand all levels of the model, starting with the seed service. The
multiple Port instances are shown at the lowest level of the service model.
The Log() command is used to print runtime values during policy processing. More logging levels
can be enabled to add processing detail.
274 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 3. Using policy scripts
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
276 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
6 External Service Dependency Adapter rules
Lesson 3. Using policy scripts
Uempty
Summary
Now that you have completed this unit, you can perform the
following tasks:
Describe when to use External Service Dependency Adapters
Configure External Service Dependency Adapter rules
Use policies in External Service Dependency Adapter rules to build
child services
Demonstrate how to trigger External Service Dependency Adapters to
build a service model
Summary
Uempty
What this unit is about In this unit, you learn several methods of automatically
creating service models. You learn how to use incoming
events and data fetchers with automatic population rules.
You learn how to create services with the Discovery
Library Toolkit and structured discovery data. Services
that are created with discovery data are created in the
Service Component Repository (SCR) database. Finally,
you learn how to analyze the SCR and use the Business
Service Composer tool to enhance and create service
models from discovered services.
How you check your progress You can check your progress in the following ways:
Student exercises
References SC23-6041-09 Business Service Manager Version 6.1.1
Service Configuration Guide
Business Service Composer Version 1.1 Users Guide
Objectives
When you complete this unit, you can perform the following
tasks:
Describe how to use automatic service model development techniques
Create services with event-based automatic population rules
Create services with data fetcher-based automatic population rules
Create services with ESDA rules
Use the Discovery Library Toolkit to create service models with Tivoli
Monitoring discovered resources
Demonstrate launch-in-context with services in the Service
Component Repository
Use the Component Registry tool and Business Service Composer to
create service models with Service Component Repository services
Objectives
What this lesson is about In this lesson, you learn how to create automatic
population rules. Automatic population rules are attached
to incoming status rules. The automatic population rule is
triggered as data is received by the incoming status rule.
The incoming event fields are used with the automatic
population rule to build new business services.
280 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 1. Automatic service population overview
Uempty
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Describe how to use automatic service model
development techniques
Create services with event-based automatic
population rules
This unit explores the following methods of automatically populating service models:
Event-based: Use incoming events.
Discovery Library Toolkit: Uses IdML books or connects with a Change and Configuration
Management Database, such as the Tivoli Application and Dependency Discovery Manager.
Note: You can also create service models with command-line tools. A review of the
command-line tools is in Command line administration on page 438.
282 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 1. Automatic service population overview
Uempty
Tivoli Business Service Manager supports two service model types: persistent and transient.
Persistent models remain in the internal DB2 database tables. Transient models are built when
required, such as when activated by an incoming event or shown in the Tivoli Business Service
Manager console.
This chart shows the tools that are available to build service models in Tivoli Business Service
Manager. Each tool supports a different method of service model creation. Choosing which tool to
use typically depends on the source of the data or events. All of these tools are described in more
detail in the remainder of this unit.
284 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 1. Automatic service population overview
Uempty
Automatic population rules create services that are based on events that are received by the
OMNIbus event server. You can set up the event feed so that different fields in the event are used
to define service object relationships. Tivoli Business Service Manager automatically creates the
service model with those fields and automatic population rules. For example, if the Node field
indicates the WebServer to which the event is applied, the Manager field indicates the associated
WebFarm. The Agent field determines the WebApplication for which the event is applied. These
instances are automatically created, even if they never previously existed.
In this example, you create a rule that populates web servers, web farms, and web applications.
You use the Node, Manager, and Agent field values from the incoming event to determine which
templates are used to automatically create the associated services. The Node field value is used
as the name for the web server that is created. The Manager field value is used to create or identify
the associated web farm. The Agent field value is used to create or identify the associated web
application.
Automatic population rules must be associated with an incoming status rule. In the WebApplication
template model example, the WebServer template contains the incoming status rules.
To open the rule form, edit the WebServer template and click the Create Auto Population rule
icon.
286 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 1. Automatic service population overview
Uempty
Configuration form
Map the automatic population rule to an existing incoming
status rule.
Fill out the form for all levels of the template hierarchy.
The template hierarchy that is available is based on the templates that are
associated with the incoming status rule.
Copyright IBM Corporation 2013 9
Configuration form
You must choose an incoming status rule from one of the rule sets in the template. This rule is the
entry point for creating the services. When the event matches an incoming status rule, the attached
automatic population rule is processed first. In this example, the WebServerStatusRule rule is
selected in the Incoming Status Rule menu.
Next, you create the Instance Name Expression. For this example, use the Node field value as
the Instance Name. Use the combination of the Node and AlertKey field values as the Display
Name. You can use any valid Tivoli Netcool/Impact regular expression in these fields.
You assign an SLA value for the created service. In this example, leave the service level agreement
as Standard.
Define the restriction filter. This value determines whether an instance is created with that section of
the auto population rule. You can use the filter to create instances only if a matching value in the
event is defined. For this example, setting the restriction filter to true creates a service instance if
the Node field is not equal to an empty string.
Parent configuration
Parent configuration
If you want the service instance relationships to be automatically created, you must configure the
form for each parent level also. Each tab of the form corresponds to the parent template in the
hierarchy. The WebServer template is a child of multiple template parents. Select the parent
template from the Incoming Status Rule menu and click the Instance Name Expression field to
refresh the form.
288 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 1. Automatic service population overview
Uempty
Test the automatic population rule by generating events manually with nco_sql. The laboratory
exercise test events use script files with the nco_sql commands already configured. This table
shows the event fields to send with test events.
This image shows the WebServer services that are created from the monitor events that are sent to
the ObjectServer. The services are also assigned the status, which is based on the incoming event
data.
290 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 1. Automatic service population overview
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
292 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 2. Data fetchers and automatic population rules
Uempty
What this lesson is about In this lesson, you learn how to configure automatic
population rules for incoming status rules that are
configured to respond to data that is received from a data
fetcher.
What you should be able to do After completing this lesson, you should be able to
perform the following task:
Create services with data fetcher-based automatic
population rules
294 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 2. Data fetchers and automatic population rules
Uempty
Creating the automatic population rule is like the previous event-based example. However, you
select the dat fetcher as the source, rather than the ObjectServer. You must also ensure that the
data fetcher returns all the fields necessary to configure the parent services.
This example populates the same hierarchy as the previous automatic population example. For this
example, the automatic population rule starts every time a data fetcher retrieves data from an
external database. When the data fetcher retrieves data from the database, new services are
created if the data does not match existing services.
296 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 2. Data fetchers and automatic population rules
Uempty
This screen image shows the WebServer instances that are created from the fetched data. Instance
status is set with information that is included in the data.
Instructor demonstration
Instructor demonstration
298 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 2. Data fetchers and automatic population rules
Uempty
Student exercises
Student exercises
What this lesson is about In this lesson, you learn how to use the Discovery Library
Toolkit to process discovery data and automatically build
business services. The Discovery Library Toolkit can
process discovery data files or discovery data from a
change and configuration management database.
Services that are created with the Discovery Library
Toolkit are stored in the service component repository.
300 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Use the Discovery Library Toolkit to create service
models with Tivoli Monitoring discovered resources
Demonstrate launch-in-context with services in the
Service Component Repository
The Discovery Library Toolkit provides tools to import discovered resource information to
automatically populate business models. You can import this resource information from two
sources:
Tivoli Application Dependency Discovery Manager: This application automatically creates
and maintains application infrastructure maps. The Discovery Library Toolkit connects to a Tivoli
Application Dependency Discovery Manager server and queries the resource and dependency
information. This information then maps to templates in Tivoli Business Service Manager.
Discovery Library Adapter: The Discovery Library Adapter creates a discovery file. The
Discovery Library Toolkit can process DLA books.
The toolkit also supports a mechanism for monitor event mapping. A unique identifier, called
BSM_Identity, is created for each discovered resource that is processed by the toolkit. The
BSM_Identity is the default service identifier for each service created. You must configure monitor
probes on the physical systems that are modeled by the discovered services to send events with a
corresponding BSM_Identity field value.
302 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
This screen capture shows a logical view of the Discovery Library Toolkit. Discovery data is
transformed and applied against the Service Component Repository templates. These templates
are used to map imported IdML books or Tivoli Application Dependency Discovery Manager data to
business services and templates.
SCR
The services that are displayed in the Service Component Repository (SCR) section of the
Service Navigation portlet are required for the Discovery Library Toolkit to function properly. The
SCR templates are imported during the toolkit installation. The default SCR templates are used to
process discovery data with the Discovery Library Toolkit.
Important: Do not alter the services that are defined under the SCR tab, and do not alter any
service template with a prefix of SCR or BSM. Altering these services and templates can cause
the Discovery Library Toolkit to malfunction. Toolkit upgrades might overwrite customizations.
304 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
A portion of the sample IdML book is shown in this screen capture. Note the XML tag
cdm:sys.ComputerSystem, which starts the node definition for a computer system. More tags
provide further information about the system. This information is then used with the SCR templates
to automatically create complicated discovered service models.
The Discovery Library Toolkit runs as a daemon under UNIX or Linux and as a service under
Windows. If configured to read IdML books, the toolkit continuously monitors the directory that is
specified during installation. After processing, the services that are created are available in the
Service Component Repository.
306 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
All monitor events that are processed by Tivoli Business Service Manager come through a
Netcool/OMNIbus ObjectServer. Monitor events that are related to service models can come from
various Systems Management monitors. Events that are not directly sent from a Netcool probe
must be translated before the ObjectServer can process them. The Netcool Event Integration
Facility (EIF) probe provides event translation services and event processing for events that are not
sent from a Netcool probe.
The EIF probe receives events from an event source, such as Tivoli Monitoring. The event is
parsed and translated based on the tivoli_eif.rules file. The EIF probe then inserts the translated
event into the ObjectServer. The translated BSM_Identity field is applied against the discovered
services.
OMNIbus
Monitor events that originate from discovered service instances must include an event identifier
field that maps to the discovered resource. The default event identifier field is the BSM_Identity
field.
308 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
Event identifiers
When the Discovery Library Toolkit creates a service, it assigns
one or more event identifiers to the service.
The default event identifier for discovery data services is
BSM_Identity.
Event identifiers
Creation of a service instance includes the creation and assignment of one or more event
identifiers. Event identifiers are service attributes under the Identification Fields tab of the
Service Editor. By default, the Discovery Library Toolkit creates an event identifier that is called
BSM_Identity. This event identifier is mapped to the ComponentRawTemplateStatus rule.
310 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
The Tivoli Event Integration Facility (EIF) probe processes monitor events from several different
event sources. The events are parsed with event rules and then sent to the ObjectServer.
This diagram shows a high-level architectural view of the Tivoli EIF probe. Depending on the event
load, one probe forwards events to Netcool/OMNIbus for multiple event sources. Event sources
include Tivoli Enterprise Console and IBM Tivoli Monitoring. The event source forwards events to
the probe. They are then translated and inserted into the ObjectServer alerts.status table. The
default port for the probe is 5530.
312 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
Mainframe monitor events can be sent to an ObjectServer with either Tivoli NetView for z/OS or
OMEGAMON XE or ITCAM for z/OS. In this configuration, the events are centralized at a
distributed Tivoli Enterprise Monitoring Server and then forwarded to the ObjectServer.
The tivoli_eif.props file has the ObjectServer host, port number, and name information.
314 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
To start the EIF probe, use the nco_p_tivoli_eif command that is in the
<Data_Server_Home>/netcool/omnibus/probes directory. You can also configure this probe to
start automatically with the OMNIbus process control agent.
$OMNIHOME/probes/<platform>/tivoli_eif.props
Stop and start the EIF probe. The probe sends event data to
the location that is specified in the StreamCaptureFile
parameter.
To verify that the EIF probe is receiving and processing events, edit the tivoli_eif.props file in the
$OMNIHOME/probes/<platform> directory. Send test events. After you stop and start the probe,
any received events are saved to the local file specified in the tivoli_eif.props file.
316 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
When the Discovery Library Toolkit creates services from discovered data, application information
is included in the service definition. The application information is stored with the service instance
as one or more attributes, which you can find in the Additional tab of the Service Editor. An
example is the IBM_Tivoli_Monitoring_Services_sourceContactInfo attribute. This attribute is a
web address that links to the Tivoli Monitoring web console. These attributes are used to provide
launch-in-context (LIC) connections from the Tivoli Integrated Portal to another application console.
The source application provides context information about discovered resources. The context
information is automatically included when the Discovery Library Toolkit uses the data to create
service models. The LIC tool passes the source application information to the secondary console
when the tool creates the remote console connection.
318 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
This screen capture shows the context information for a service instance that is created from an
IdML book. Use a right-click Launch tool from the service tree or service viewer. These menus
automatically include the context information to open the remote application console with focus on
the resource.
The LIC target is available only if context reference attributes are defined in the service instance
properties.
320 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
The Tivoli Enterprise Portal client opens to the workspace that is referenced
in the monitor event.
In this screen capture, a Tivoli Monitoring service instance is selected from the Tivoli Integrated
Portal server. Right-clicking and selecting Launch to > Show Managed System (TEP) starts a
browser connection to the Tivoli Monitoring web console. After entering the authorized Tivoli
Monitoring user name and password, the console is started, showing the ManagedSystemName
workspace.
Instructor demonstration
Instructor demonstration
322 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 3. Creating services from discovered resources
Uempty
Student exercises
Student exercises
What this lesson is about In this lesson, you learn how to build and enhance
business services with services that are contained in the
service component repository. You learn how to use the
component registry viewer tool to examine the common
data model classes that form the basis for the discovered
services. You then learn how to use the business service
composer tool to create business service models and
place them in the Imported Business Services section of
the service tree.
324 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 4. Building services in the Service Component Repository
Uempty
What you should be able to do After completing this lesson, you should be able to
perform the following task:
Use the Component Registry tool and Business Service
Composer to create service models with Service
Component Repository services
The Service Component Repository contains business services that are created as discovery data
is processed by the Discovery Library Toolkit. The discovery data includes Common Data Model
classes that are mapped to business service templates that are installed with the Discovery Library
Toolkit. Discovery data that includes one of the following common data model classes are also
shown in the Imported Business Services section of the service navigation tree:
The cdm:sys.BusinessSystem class is used to create BSM_BusinessService
template-based services.
326 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 4. Building services in the Service Component Repository
Uempty
This screen image shows the top level of several business services that were created from
discovery data. The DayTrader application is expanded to show the complexity of the automatically
created business service.
The Component Registry viewer is a software tool that is installed with the Discovery Library Toolkit.
The tool is used to browse the tables and data in the Service Component Repository. The tool is
useful for examining the common data model classes that form the basis for the business service
models.
328 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 4. Building services in the Service Component Repository
Uempty
Search for a
CDM class.
Select a specific
instance.
Review instance
attributes.
Copyright IBM Corporation 2013 48
In this example, the Component Registry tool is used to review common data model classes that
are used to create the DayTrader application. The complete class list is shown in the Class List
section of the tool. When you select the application class name, cdm:app.Application, the instance
list is populated with all corresponding instances. You select the DayTrader instance name to show
the attribute list for the Daytrader instance. The application name is identified with the cdm:Name
class.
The Business Service Composer is a tool in the Component Registry viewer tool. You use the
Business Service Composer to enhance service models in the Service Component Repository.
Services that are created from discovery data can be complex and include several levels of
services. You can use the Business Service Composer to create a more simplified business
service. In this example, the network bridge services that are shown are five levels below the top of
the DayTrader application. The Business Service Composer project has reconfigured the bridge
services in a NetworkBridges container that is one level down from the top of the application.
330 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 4. Building services in the Service Component Repository
Uempty
A business service composer project consists of one or more static definitions and policy patterns.
Static definitions are used to contain the services that are created from the policy pattern
configuration. Static definitions can be one of three types of business templates:
BSM_BusinessService
BSM_BusinessApplication
BSM_LogicalGrouping
Policy patterns are filters that are configured to match data that is contained in the Service
Component Repository.
The business service composer is composed of five sections. The Project View section shows a
summary of the defined project elements. The Static Definition section defines one or more static
definitions for the project. Static definitions are services that are created to contain business
services that match classes that are defined in the policy patterns. The policy pattern section is
used to define one or more common data model classes and attributes that match defined criteria.
The classes that match the defined policy pattern are used to create corresponding business
services. The business services that match the policy pattern are created as dependent services in
the static definition. The policy pattern section includes two more sections that are used to define
the criteria for matching the class information that is contained in the Service Component
Repository.
332 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 4. Building services in the Service Component Repository
Uempty
You create a static definition to contain business services that match a policy pattern. Static
definitions must use one of three different common data model classes. The classes map to the
BSM_BusinessService template, the BSM_BusinessApplication template, or the
BSM_ApplogicalGrouping template.
Policy patterns consist of filters that are configured to search the service component repository. The
database classes that match the configured filter are used to create business services. The original
services that are created with discovery data are not modified.
334 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 4. Building services in the Service Component Repository
Uempty
In this example, the service component repository contains several hundred DB2 database
services in the Service Component Repository. The services are spread across many different
parent services. For this example, you must organize the DB2 instances by geographical region. A
fictitious company, called GetThereFast Travel, has two data centers. One data center is in Austin,
Texas, and the second data center is in San Jose, California. You must use the Business Service
Composer to create a new service model.
To create a static definition, right-click the Static Definitions icon. You select one of the three
classes, which is mapped to a business service template. Assign a name and label for the static
definition.
336 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 4. Building services in the Service Component Repository
Uempty
To configure a Policy Pattern, right-click the Policy Pattern icon. Select the Policy Pattern that is
used to search the Service Component Repository. For this example, the PlaceByLabel pattern is
used. This pattern searches the DB2 instance class labels. You define matches to contain either
sanjose or austin. If a match is found, place the instance in the service that is defined for the
corresponding static definition.
Business service composer project files are stored in XML format. A project file must be applied to
the Service Component Repository from the command line.
338 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 4. Building services in the Service Component Repository
Uempty
The business services that are created with the business service composer project are not
immediately processed if the Service Component Repository database is large. There can be a
several minute delay before the business services are seen in the service tree. You should not use
the console tools to remove a business service from the service component repository. To remove
the effect of a Business Service Composer project, you must use a command with the project file.
Instructor demonstration
Instructor demonstration
340 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
7 Automatic service model creation
Lesson 4. Building services in the Service Component Repository
Uempty
Student exercises
Student exercises
Summary
Now that you have completed this unit, you can perform the following
tasks:
Describe how to use automatic service model development techniques
Create services with event-based automatic population rules
Create services with data fetcher-based automatic population rules
Create services with ESDA rules
Use the Discovery Library Toolkit to create service models with Tivoli
Monitoring discovered resources
Demonstrate launch-in-context with services in the Service
Component Repository
Use the Component Registry tool and Business Service Composer to
create service models with Service Component Repository services
Summary
342 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
8 Security
8 Security
How you check your progress You can check your progress in the following ways:
Student exercises
References GI11-8054-08 Business Service Manager 6.1.1
Installation Guide
SC23-6040-09 Business Service Manager 6.1.1
Administrators Guide
344 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Uempty
Objectives
When you complete this unit, you can perform the following
tasks:
Describe the user authentication and authorization services that are
used in Tivoli Business Service Manager
Configure the dashboard server to use an LDAP user and group
repository
Configure SSL communications between the dashboard server and an
LDAP server
Manage users, groups, and roles in a Tivoli Business Service Manager
deployment
Use authorization roles to control access to Tivoli Business Service
Manager 6.1.1 objects
Objectives
What this lesson is about In this lesson, you learn the basic security concepts of
authentication and authorization that are used in the Tivoli
Business Service Manager dashboard server. The
dashboard server uses the WebSphere Application
Server security services. You learn about the different
user repositories that are supported by WebSphere. You
also learn about the concept of a federated repository.
The federated repository combines multiple physical
repositories into a single logical repository.
346 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 1. Security overview
Uempty
What you should be able to do After completing this lesson, you should be able to
perform the following task:
Describe the user authentication and authorization
services that are used in Tivoli Business Service Manager
Authentication is the process of ensuring that a user name and password are valid for an
application. Authorization is the process of mapping authenticated user roles against roles that are
assigned to elements within an application. If the user roles allow access, the user can use the
application element.
348 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 1. Security overview
Uempty
Security services
Tivoli Business Service Manager security provides
authentication services through one or more user and group
repositories.
Authorization to Tivoli Business Service Manager objects is
controlled through combinations of user, group, and role
assignments.
External LDAP user repositories can be managed through the
dashboard server web console.
Secure HTTP is used for communication between a browser
and the dashboard server by default.
Tivoli Business Service Manager supports single sign-on
(SSO) when connecting to or from a supported application.
Security services
The Tivoli Integrated Portal 2.2 server uses the authentication and authorization architecture that is
provided by embedded WebSphere Application Server version 7. Authentication uses one or more
supported user and group repositories. Authorization is managed with roles applied to data server
objects.
Hint: The Jazz for Service Management version 1.1 server uses WebSphere Application Server
version 8.5. The security principles that are reviewed in this unit apply to Tivoli Integrated Portal
version 2.2 and to Jazz for Service Management version 1.1.
Authentication overview
Tivoli Business Service Manager can be configured for one of
the following user and group repositories during the initial
installation:
File-based
OMNIbus
LDAP
After installation, you can combine one or more repository
types into a single logical entity called a federated repository.
The file-based repository is always available as an internal data
store within the dashboard server.
Authentication overview
When Tivoli Business Service Manager 6.1.1 is installed with the Simple Installation option, it
uses the internal file-based repository by default. The internal repository is not intended for
production use. With the Advanced Installation option, you can specify one of the three supported
repository types. With the OMNIbus or LDAP options, the file-based option is always available. The
administrative account, tipadmin, is stored in the Tivoli Integrated Portal file-based repository. You
can combine the supported repositories to function as a single logical user and group repository.
350 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 1. Security overview
Uempty
An advantage of the file-based user repository is that it does not require configuration after
installation. It is intended for simple testing and proof-of-concept environments, but it is not useful
for production.
Disadvantages of the file-based user repository are that it does not support SSO and it is not
scalable. Tivoli Business Service Manager supports multiple dashboard servers. Sites large
enough to benefit from multiple dashboard servers use centralized user management. Each
dashboard server file-based repository is isolated to the host server and cannot span multiple
dashboard servers.
Tivoli Integrated
Portal
Consoles
Authentication/User &
Group Management
File
Repository
In this diagram, the dashboard and data servers are installed on the same host. For this
environment, the file-based user repository is acceptable if the total number of users and groups
remains relatively small.
352 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 1. Security overview
Uempty
Tivoli Business Service Manager can read user and group information from multiple repositories.
However, you can configure only one repository for user and group management through the Tivoli
Integrated Portal server. The Supported Entity Types parameter determines where, within the
configured repository, you create, modify, or delete users and groups.
You must use the Advanced Installation option to select the ObjectServer as the default
repository. You cannot manage the ObjectServer users and groups through the Tivoli Integrated
Portal console; they are used as a read-only repository. You must manage any changes to the
users or groups with ObjectServer tools.
354 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 1. Security overview
Uempty
LDAP overview
The Lightweight Directory Access Protocol (LDAP) provides
structured storage of user and group data.
LDAP also provides authentication services for user and group
entries.
LDAP is scalable for large numbers of users.
LDAP is required to support single sign-on (SSO) and console
load balancing.
LDAP overview
Lightweight Directory Access Protocol (LDAP) is a standard that provides a structured and secure
lookup service. User and group names, passwords, and other information are stored for fast
retrieval of information by any application that supports the LDAP client standard.
All supported LDAP servers support Secure Sockets Layer (SSL) encrypted communications
between the Tivoli Integrated Portal and LDAP servers. Single sign-on is only available with an
LDAP user and group repository.
If you have an LDAP product other than Tivoli Directory Server, select the Simple Install option.
After installation, configure for your LDAP server.
TBSM Dashboard
TBSM Consoles Server
TBSM Profile
TBSM
Consoles
TBSM Data
Server
LDAP or
High Central User
OMNIbus
Availability Repository
Role Replication
Two dashboard servers are shown in this diagram. The central user repository allows them both to
access the same information. Because role information is not stored in the user repository, it is
replicated in the high-availability component. The high-availability component keeps the association
of roles to both users and groups that are synchronized across multiple dashboard servers.
356 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 1. Security overview
Uempty
Examples:
uid=jsmith, o=tipRealm
uid=whill, o=defaultWIMFileBasedRealm
uid=student1, o=netcoolObjectServerRepository
You can add an LDAP repository to the federated repository with the WebSphere command
interpreter wsadmin or the Tivoli Integrated Portal console. After entering the configuration
information, you change the Tivoli Integrated Portal Entity Type definitions. This information is
used when adding, deleting, or modifying users or groups with the Tivoli Integrated Portal console.
You can manage only one repository with the console, although it can read user and group
information from multiple repositories.
A federated repository combines multiple physical repositories into a single logical repository. When
a user authenticates, the user ID and password are tested against the users that are defined in
each physical repository. A WebSphere property that is called the Supported Entity Types
controls the physical repository that is used to manage users and groups with the console. The
Supported Entity Types also control how a user or group name entry is stored and accessed in the
managed repository.
358 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 1. Security overview
Uempty
o=defaultWIMFileBasedRealm uid=tipadmin
o=netcoolObjectServerRepository uid=user3
When user1 logs in, the product searches the default file-based
repository. If it finds no match, it searches the LDAP repository.
When it finds a match, it compares the entered password with
the password stored with uid=user1. If the passwords match, the
user is authenticated.
Copyright IBM Corporation 2013 15
In this example, a federated repository consists of the default file-based repository, an LDAP
repository, and a Netcool/OMNIbus repository. For this example, the Entity Types are configured to
point to the internal file-based repository.
When user1 enters a user name and password, the file-based repository is searched, starting at
o=defaultWIMFileBasedRealm. Because no match is found, the LDAP repository is searched,
starting at dc=ibm, dc=com. The user name and password match. The ObjectServer repository is
searched, starting at o=netcoolObjectServerRepository, to ensure that no duplicate names exist.
The authentication passes, and the user is logged on to the Tivoli Integrated Portal console.
What this lesson is about In this lesson, you learn how to configure the dashboard
server to use an LDAP directory. You learn how to use the
WebSphere administrative console to change the
configuration of the federated repository.
What you should be able to do After completing this lesson, you should be able to
perform the following task:
Configure the dashboard server to use an LDAP user and
group repository
360 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 2. Configuring LDAP authentication
Uempty
References GI11-8054-08 Business Service Manager 6.1.1
Installation Guide
SC23-6040-09 Business Service Manager 6.1.1
Administrators Guide
Configuring LDAP
You configure LDAP through the WebSphere administrative
console.
You create a base entry in the federated repository realm.
The base entry must map to a physical repository.
The physical repository must minimally include the following
information:
LDAP server host name
LDAP server port
Authorized LDAP user and password, in distinguished name format
LDAP search criteria for users and groups
Configuring LDAP
An authorized LDAP user name and password. The user must have authorization to retrieve
user and group information from the LDAP server.
The starting point in the LDAP directory tree to search for user and group matches.
If the repository supports management through the Tivoli Integrated Portal, modify the Entity Types
to point to the LDAP server.
362 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 2. Configuring LDAP authentication
Uempty
The Tivoli Integrated Portal uses the WebSphere console for security and other administrative
functions.
To define an LDAP repository, click the Security > Secure configuration, applications, and
infrastructure task. Click Configure.
364 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 2. Configuring LDAP authentication
Uempty
To add the LDAP repository, you must first create a base entry in the WebSphere security realm.
This base entry provides the pointer to the search entry point of the LDAP server.
LDAP servers can support separate multiple directory trees. You must complete the Distinguished
name of a base entry that uniquely identifies this set of entries within the realm field to
identify the realm in the federated repository. The Distinguished name of a base entry in this
repository field is the starting point to search for users or groups in the LDAP directory.
For this example, the repository is not yet defined. Within the General Properties section of the
Configuration form, click Add Repository. After completing the connection information, add the
base entry points for the Federated and LDAP repositories.
366 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 2. Configuring LDAP authentication
Uempty
The repository identifier is a string that WebSphere uses internally to uniquely identify the LDAP
definition. After selecting the LDAP server type, enter the host name and communication port. The
default nonsecure port is 389.
In the Security section, you must enter an administrative user on the LDAP server for the Bind
distinguished name and password. This administrator must have authority to search and modify
the LDAP directory.
When prompted to save configuration changes to the WebSphere server, click the Save link. After
completing the remainder of the configuration, you must stop and start the dashboard server.
368 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 2. Configuring LDAP authentication
Uempty
After you define the LDAP repository, complete the realm definition by defining the starting point for
searches of the federated and LDAP repositories. This example uses the following definitions:
Distinguished name of a base entry that uniquely identifies this set of entries within the realm:
o=tiprealm
Distinguished name of a base entry in the repository: dc=ibm, dc=com
The realm entry, o=tiprealm, is a logical designation in the federated repository. The base entry,
dc=ibm, dc=com, designates the starting point of a user name search in the physical repository.
You use entity types to define the initial realm search point
when you identify users and groups.
You also use entity types to define where and how you create,
modify, and delete users or groups in the federated repository.
You cannot create, delete, or modify users in the Jazz for
Service Management console.
If you plan to create, modify, and delete LDAP users from the Tivoli Integrated Portal console, you
must change the supported entity types for the LDAP repository. The values that are entered for
Group, OrgContainer, and PersonAccount are used when updating the LDAP directory.
370 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 2. Configuring LDAP authentication
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
372 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 3. Configuring SSL authentication
Uempty
What this lesson is about In this lesson, you learn how to configure the dashboard
server to use secure sockets layer communications (SSL)
when authenticating with an LDAP server. You learn how
to add an LDAP server signer certificate to the dashboard
server truststore.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Configure SSL communications between the dashboard
server and an LDAP server
374 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 3. Configuring SSL authentication
Uempty
If the LDAP repository is not configured to use Secure Sockets Layer (SSL) protocols, any user and
password information that is sent between the Tivoli Integrated Portal and an LDAP server is not
encrypted. This situation presents a security risk. To secure communications, Tivoli Business
Service Manager supports SSL protocols.
The minimum configuration to establish SSL communications with an LDAP server requires
receiving a certificate authority (CA) from the LDAP server. This certificate is then stored in the
Tivoli Integrated Portal keystores. After importing the CA, the LDAP repository definition is modified
to use SSL. This type of configuration is known as client authentication, where the Tivoli
Integrated Portal server acts as a client to LDAP.
Another type of configuration, which is known as server authentication, is also supported. With
server authentication, a Tivoli Integrated Portal CA is imported into the LDAP truststore. You then
configure the Tivoli Integrated Portal and LDAP to establish server-to-server trust before
transferring data.
CAs are self-signed or provided by a known trust authority. Self-signed certificates are inherently
less secure.
Both NodeDefaultKeyStore and NodeDefaultTrustStore are software objects that securely store
cryptographic key information. This information is stored in a standardized way so that one
computer can establish a secure trust relationship to safely encrypt communications. Importing the
LDAP CA into the truststore provides the mechanism that ensures the Tivoli Integrated Portal can
trust the LDAP server identity. If the LDAP server configuration requires trusted connections with
clients, you create a CA for the Tivoli Integrated Portal server. The Tivoli Integrated Portal server
CA is stored in the keystore. The LDAP server must import the CA into the LDAP truststore. After
the target server trust is established, all communications between LDAP and the Tivoli Integrated
Portal server are then encrypted according to the SSL protocols.
376 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 3. Configuring SSL authentication
Uempty
You can use the SSL certificate and key management > Key stores and certificates task to
retrieve the LDAP certificate authority. To implement client trust with the LDAP server, import the
LDAP CA into the Tivoli Integrated Portal truststore, select the Signer certificates link. From this
form, click Retrieve from port.
After clicking Retrieve from port, you are prompted for the LDAP server configuration information,
including the server name and communication port. Enter a text string in the Alias field to uniquely
identify the LDAP server. Click Retrieve signer information to complete the CA retrieval.
378 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 3. Configuring SSL authentication
Uempty
After the LDAP certificate of authority is stored in the Tivoli Integrated Portal truststore, edit the
LDAP repository configuration to require SSL communications. Change the communication port to
the secure listening port of the LDAP server.
Instructor demonstration
Instructor demonstration
380 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 3. Configuring SSL authentication
Uempty
Student exercises
Student exercise
What this lesson is about In this lesson, you learn how to use the Tivoli Integrated
Portal server console to create Tivoli Business Service
Manager users and groups. You learn how authorization
roles are assigned and how they control access to Tivoli
Business Service Manager objects and resources.
382 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 4. Managing users, groups, and authorization roles
Uempty
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Manage users, groups, and roles in a Tivoli Business
Service Manager deployment
Use authorization roles to control access to Tivoli
Business Service Manager 6.1.1 objects
Authorization roles control the Tivoli Business Service Manager functions that are available to a
user. You should manage the assignment of authorization roles with groups. The organization of
groups simplifies user and group administration. You assign roles to groups according to job
function and then assign users to appropriate groups.
384 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 4. Managing users, groups, and authorization roles
Uempty
Tivoli Business Service Manager supports the creation of users and groups directly from the
administrative console. A WebSphere property that is called the Supported Entity Types controls
the repository that is used to modify users and groups. Jazz for Service Management does not
support direct modification of users and groups. The creation of users and groups must be
managed with the repository administration tools. You use the Jazz for Service Management
console to manage authorization roles for users and groups that are defined in a repository.
If you use federated repositories, you must assign a user to a group that is in the same repository.
For example, you cannot define a user in a file-based repository and assign that user to a group
that is defined in an LDAP or ObjectServer repository.
You select the Users and Groups > Group Roles task to modify the roles that are assigned to a
group. Users that are assigned to a group inherit the roles that are assigned to the group. Roles are
cumulative. For example, a user is assigned to two groups, Group 1 and Group 2. Group 1 is
assigned the tbsmReadOnlyUser role. Group 2 is assigned the tbsmAdminUser role. If a Tivoli
Business Service Manager object is only available to users with the tbsmAdminUser role, the
Group 2 role takes precedence over the more restrictive Group 1 role.
386 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 4. Managing users, groups, and authorization roles
Uempty
Click the Users and Groups > Group Roles task. Search for the name of the group. Select the
check box to the left of one or more role names and click Save.
Instructor demonstration
Instructor demonstration
388 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security
Lesson 4. Managing users, groups, and authorization roles
Uempty
Student exercises
Student Exercises
Summary
Now that you have completed this unit, you can perform the
following tasks:
Describe the user authentication and authorization services that are
used in Tivoli Business Service Manager
Configure the dashboard server to use an LDAP user and group
repository
Configure SSL communications between the dashboard server and an
LDAP server
Manage users, groups, and roles in a Tivoli Business Service Manager
deployment
Use authorization roles to control access to Tivoli Business Service
Manager 6.1.1 objects
Summary
390 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
9 Custom dashboards and page
management
What this unit is about A new feature of Tivoli Business Service Manager 6.1.1 is
the addition of the Jazz for Service Management version
1.1 technology. Jazz for Service Management includes
visualization services that are used to create and manage
business dashboards. This unit includes an overview of
the Jazz for Service Management services and reviews
methods for creating and managing custom dashboards
with the Jazz for Service Management visualization
services. You also learn how to use authorization roles to
control user access to dashboards.
How you check your progress You can check your progress in the following ways:
Student exercises
References SC23-6040-09 Business Service Manager 6.1.1
Administrators Guide
Jazz for Service Management Version 1.1 Administration
Guide
Jazz for Service Management Version 1.1 Users Guide
https://www.ibm.com/developerworks/servicemanageme
nt/jazzsm/index.html
Jazz for Service Management developerWorks
community
392 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Uempty
Objectives
When you complete this unit, you can perform the following
tasks:
Describe the major functions of the Jazz for Service Management
visualization services
Describe how dashboard widgets access business data
Use Jazz for Service Management DASH server processes and tools
to build custom dashboards
Use Jazz for Service Management DASH server tools to manage
dashboards
Objectives
What this lesson is about In this lesson, you learn about the services that are
provided with Jazz for Service Management version 1.1.
You learn how dashboard widgets use the registry
services and Open Services for Lifecycle Collaboration
(OSLC) data to retrieve data from an application. You also
learn how dashboard widgets are configured on a
business dashboard to provide a targeted business view.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Describe the major functions of the Jazz for Service
Management visualization services
Describe how dashboard widgets use business data
394 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 1. Dashboard tools overview
Uempty
References SC23-6040-09 Business Service Manager 6.1.1
Administrators Guide
Jazz for Service Management Version 1.1 Administration
Guide
Jazz for Service Management Version 1.1 Users Guide
Jazz for Service Management contains five major components. The registry services provide a
centralized data resource locator database. This database contains an indexed set of pointers to
application data. The visualization services are a set of tools that are used to organize and show
data from multiple applications. The primary visualization components, called widgets, are
combined on a dashboard page to present customized data views. The administrative services
provide the means to automate application management from the Jazz for Service Management
console. The reporting services provide a common reporting infrastructure to create reports from
multiple data sources. The security services provide the authentication mechanism for user access
to application data. A major component of the security services is support for a concept that is
known as single sign-on, or SSO. With SSO, a user authenticates to an application by entering a
user name and password. If the user links to a subsequent application, the connection to the
second application console is automatically authenticated.
396 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 1. Dashboard tools overview
Uempty
The common widget library that is provided with the Jazz for Service Management visualization
services is the core mechanism that is used to build dashboard pages. Widgets that are placed on
a dashboard page are connected with other widgets and other pages to create interactive
dashboard pages. The dashboard pages can be created, configured, and customized by any
authorized Jazz for Service Management user. WebSphere Application Server security and single
sign-on create a unified security model for dashboard user and data authentication.
DASH Server
JDBC
Service provider Service provider Service provider
Lotus
Tivoli Directory
Application Application
Integrator/Impact
CSV
This diagram shows a high-level view of the main components of the visualization services
architecture. Data applications that support Jazz for Service Management include a software
component that is known as a service provider. The service provider provides the standardized
interface between the dashboard server and the application data. The widgets on a dashboard are
configured to retrieve application data through data connections and service providers. Dashboard
pages are created for mobile and desktop clients with the same development tools.
398 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 1. Dashboard tools overview
Uempty
Dashboard pages that are designed for mobile devices are viewed and used differently from
desktop dashboards. Mobile dashboards cannot contain images on the login page. To maximize
the screen space that is available for the dashboard, the taskbar is replaced with a navigation icon.
On mobile devices, you can view only the dashboard pages that are designated for mobile devices.
The default page that is configured for the default view for a user is used as the dashboard home
page. Mobile dashboards are currently supported for Android, iPhone, and iPad devices.
Navigation from one dashboard page to another with mobile devices is done by closing the current
page and replacing it with the selected page. Selecting the back arrow from the navigation icon
replaces the current page with the previous page contained in the browser history.
400 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 2. Data connections
Uempty
What this lesson is about In this lesson, you learn how to configure data
connections between the Jazz for Service Management
registry services and an application. The connections
provide a standardized method for locating and retrieving
application data.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Describe how dashboard widgets access business data
402 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 2. Data connections
Uempty
Service provider
Application
This diagram shows the function of a Jazz for Service Management connection object. A
connection establishes how dashboard widgets communicate with an application to retrieve data.
Jazz for Service Management connection objects can be created only with applications that include
an OSLC service provider.
Dashboard widgets are used with data from various application data sources. Widgets retrieve data
through a Jazz for Service Management tool that is known as a data connection. Data connections
are software objects that define a link between the dashboard server the service provider on the
remote application. The service provider must be registered with the Jazz for Service Management
registry services.
Creating connections
Use the Connections management widget in the Console
Settings folder.
Existing connections are managed in the console workspace.
Click the Create new remote provider icon to create a new
connection.
Creating connections
To create a data connection, you click the connections widget icon. The icon is in the Console
Settings folder in the taskbar on the left of the console. When the connections widget starts,
existing connections are listed in the console workspace. Click the Create new remote provider
icon to start the connection creation process.
404 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 2. Data connections
Uempty
Configuring a connection
Enter the service provider target connection information.
Click Search to see available service providers.
Select the connection authentication method.
Configuring a connection
Enter the host name of the target application, communication port, and the type of protocol that is
used by the service provider. Choose either HTTP or secure socket HTTP. The user must be
authorized to interact with the remote application. Applications can include more than one service
provider. Clicking the search icon returns a list of available service providers. You then choose how
to manage authentication credentials when a user interacts with the application through the data
connection.
Connection authentication
Configure service provider authentication in one of two ways:
Use the configured connection credentials for every dashboard user.
Use SSO:
The LTPA authentication cookie for the console user is sent with every data
provider request for authentication.
The data provider must be part of the same WebSphere Application Server
SSO domain for the LTPA credentials to be accepted.
Connection authentication
There are two ways to configure how a widget interacts with the remote application service
provider. By default, the user name and password that are entered in the connection configuration
is used for every data request with the remote application. If you select the option to use the
credentials of the user, the remote application must be configured to interact with the dashboard
server with single sign-on. Single sign-on is a standard method for passing encrypted user
authentication credentials between servers.
406 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 2. Data connections
Uempty
Tivoli Directory Integrator, which is included with Jazz for Service Management, is used to create a
service provider for applications that do not include a service provider component. When the
application service provider is created with Tivoli Directory Integrator, data is then available for
interaction with dashboard widgets.
Instructor demonstration
Instructor demonstration
408 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 2. Data connections
Uempty
Student exercises
Student exercises
What this lesson is about In this lesson, you learn how to use the visualization
services to create a multipage linked business
dashboard. You learn how to add and configure widgets
on a page and how to link pages with dashboard wires.
You learn how to retrieve and show business service data
from the Tivoli Business Service Manager server.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Use Jazz for Service Management DASH server
processes and tools to build custom dashboards
410 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 3. Creating dashboard pages
Uempty
References SC23-6040-09 Business Service Manager 6.1.1
Administrators Guide
Jazz for Service Management Version 1.1 Administration
Guide
Jazz for Service Management Version 1.1 Users Guide
There are three methods for creating dashboard pages. The first method uses the Pages task in
the Console Settings folder. You click the Pages task and then click New Page. The second
method is to click the plus symbol, which is located in the upper right of the console. The third
method uses a link in the console Welcome page. Position the cursor over the Get started Arrow
and select build a page.
412 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 3. Creating dashboard pages
Uempty
Fluid
Proportional
Freeform
Copyright IBM Corporation 2013 19
Before you add widgets to a dashboard page, you must select the page layout style. The layout
style controls how widgets and elements are added to a page. The three available layout styles are
proportional, freeform, and fluid.
The proportional layout style allows widgets to be placed anywhere on the dashboard page and
overlaid with other widgets. If the page is resized, the widgets proportionally change size to adapt to
the new page size.
The freeform layout style also allows widgets to be placed anywhere on the page and overlaid with
other widgets. However, if the page is resized, the widgets are not proportionally adjusted.
The fluid layout style is designed primarily for creating mobile dashboards. Widgets that are placed
on the page cannot be overlaid with other widgets. The widgets are automatically arranged in a tiled
pattern when added to the page.
Page and
} widget
controls
} Palette
} Canvas
You use the dashboard workspace to create dashboards. The workspace consists of three
sections. The top section contains a menu bar that you use to control page and widget functions.
The middle section contains an object palette that shows a list of available widgets. The bottom
section is the page canvas, where you place and configure the widgets. A grid is shown on the
canvas to help adjust the arrangement of the widgets.
414 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 3. Creating dashboard pages
Uempty
Not all widgets are designed to work with mobile devices. To see the list of widgets that are
designed for mobile devices, click the Mobile option next to the search field above the palette. Click
Search to filter mobile-supported devices. The mobile-supported widgets are text, refresh timer, list,
topology, table, tree table, and four gauge types. The gauge widgets that are available for mobile
devices are status, value status, volume bar, and analog.
Each data widget is designed to show either scalar or list values. Scalar widgets show columns
from only one row of the retrieved data set from a data connection. Examples of scalar widgets are
the status gauge, value status gauge, volume bar, and analog gauge widgets. List widgets are
designed to show data for multiple rows that are returned in the data set. List widgets include the
list, topology, table, and tree table widgets. The text and refresh widgets are not designed to show
data from the data set. They are not scalar or list widgets.
416 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 3. Creating dashboard pages
Uempty
When you place a widget onto the dashboard canvas, you configure the widget to show data from a
data connection. Depending on the widget, the configuration fields vary. The data configuration
choices also vary depending on the source of the data set. This slide shows an example of the
configuration of an analog gauge widget. The analog gauge is a scalar widget, which is designed to
show data from a single row of a data set. Each widget includes a menu icon in the upper right of
each widget. When you click the menu icon and select the Edit menu, the configuration window
opens.
The first step in configuring a widget on a dashboard page requires selecting the data to be shown
in that widget. The data that is selected is referred to as a data set. To see a list of all available data
sets from all service providers, click Search or click Show All. You can also enter filter strings in the
Search field. Then, you select a data set from the returned list.
418 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 3. Creating dashboard pages
Uempty
The data that is returned in the data set includes information about the type of data in the list. You
customize how the widget shows the selected data by configuring the visualization settings. You
then select how to map the data to the available attributes in the widget. Some widgets provide
extra visualization properties that can be shown in the widget. If the data set contains multiple rows
of data, and the widget type is scalar, you create filter criteria to specify which row of data to use. If
you do not specify a filter, scalar widgets use the first row in the data set.
To create interactive dashboards, you create software objects referred to as wires. Wires define
communication connections between widgets and pages. Widgets generate and respond to events
that indicate a state change in the data. For example, clicking a widget generates an event that can
be sent to another page or widget in another page. The source event includes contextual
information that is used to update a target page or widget, which is based on the supplied context.
420 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 3. Creating dashboard pages
Uempty
1
A B C
This diagram shows three examples of the effect of different types of wires. In the first example, a
wire is configured to send a NodeClickedOn event from a source widget to widget C. Widget C is on
the same dashboard page. When the source widget is clicked, widget C is updated based on the
context that is transmitted from the source. The state of widgets A and B are unchanged.
In the second example, a wire is configured between the source widget and widget D, in Sample
Page A. The wire is also configured to open and switch to Sample Page A. When the source widget
is clicked, Sample Page A is opened, with the data shown in widget D based on the context that is
sent from the source widget. Widget E on Sample Page A is unchanged.
In the third example, a wire is configured between the source widget and Sample Page B. The wire
is also configured to open and switch to Sample Page B. When the source widget is clicked,
Sample Page B is opened, with the data shown in widget F and widget G, based on the context that
is sent from the source widget.
Event transformations
Event transformations provide a tool to intercept and modify a source
event. This tool changes the event that is delivered to a target.
For example, clicking a source widget generates a NodeClickedOn event.
The target widget is a Web widget.
The Web widget requires a DisplayURL event.
An event transformation can be configured to change the NodeClickedOn event
to an equivalent DisplayURL event before deliver to the Web widget.
Transformations require customization of an XML and JavaScript file.
Event transformations
Wires can be configured to include a transformation of the source event before delivery to the
target. For example, a NodeClickedOn event does not include information in a format that is used
by a web widget. The transformation reformats the NodeClickedOn event to a DisplayURL event.
The DisplayURL event is used by the web widget to open an HTML connection. A Jazz for Service
Management administrator must create the transformation and customization of an XML file and a
corresponding JavaScript file.
422 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 3. Creating dashboard pages
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
424 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 4. Managing dashboards
Uempty
What this lesson is about In this lesson, you learn how to manage user access to
custom dashboards with views and custom profile
preferences. Views contain links to one or more pages.
Console preference profiles control the views that are
available to a console user.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Use Jazz for Service Management DASH server tools to
manage dashboards
426 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 4. Managing dashboards
Uempty
Managing dashboards
The interaction of authorization roles that are assigned to users
and Jazz for Service Management objects control user access
Resources
Users
Widgets
Widget
Roles
Managing dashboards
Users interact with dashboard pages based on authorization roles that are assigned to the user and
assigned to the Jazz for Service Management console objects. If the user has the appropriate
authorization role, they are allowed access to the object. Access to widgets, pages, views, and
preference profiles are controlled with authorization roles. If the user does not have an appropriate
authorization role, they do not see the object or are not able to interact with the object.
Dashboard pages are organized into related collections by assigning the pages to a view. If a user
connects to the Jazz for Service Management environment from a mobile device, a view must be
configured to accept mobile device connections. Console preference profiles control how the user
uses pages and views when connected to the Jazz for Service Management console. You use
console preference profiles to define a default view, which is based on an assigned authorization
role. You also use console preference profiles to select the color theme that is used in the console
connection. There are currently two available themes. The IBM design signature uses white page
backgrounds and dark text, and Tivoli Dark consists of dark page backgrounds and white text.
428 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 4. Managing dashboards
Uempty
Authorization roles
Every widget, page, view, and preference profile must be assigned one or
more authorization roles.
You can create custom roles to simplify page and view management.
Access levels provide additional access control for a role.
RoleA
Desktop users
RoleA
RoleA
Authorization roles
Every widget, page, view, and preference profile must be assigned one or more authorization roles.
The authorization settings that are assigned to a user control the objects that the user sees.
You create custom roles with the Roles task in the Console Settings folder. Provide a name for the
role and assign the role to existing users, groups, pages, or views.
To assign the role to an object, expand the appropriate section, and then click the plus icon and
select the corresponding user, group, page, or view. Select the target role object from the returned
list.
430 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 4. Managing dashboards
Uempty
Managing views
You use views to define a list of folders and page links.
You create views with the Console Settings > Views task.
Mobile devices can use only views with the Enable for
Mobile option selected.
You can add pages and assign view authorization.
Managing views
Views are collections of pages. They are used to organize the pages into related collections. To
create a view, select the Views task in the Console Settings folder. Assign a name to the view. If
mobile devices use the page, select to enable the view for mobile device connections.
To automatically open pages in a view, you expand the Pages in This View section of the form and
select the pages for the view. After assigning pages to the view, you select which pages in the view
must automatically open when the user opens the view. If there is more than one page in the view,
you can select one of the pages to be the default page that is shown when the view is opened. If the
view contains multiple pages that are set to automatically open, each page opens in tabbed window
in the console.
432 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 4. Managing dashboards
Uempty
Console preference profiles are used to control user navigation and the page color theme. To
create a console preference profile, select the Console Preference Profiles task in the Console
Settings folder. You configure the views that are available to a user.
The console preference profile controls the views and pages the user sees when they connect with
the console. The users that are affected by a console preference profile are controlled by assigning
a role to the console preference profile. When a user authenticates to the console, the roles that are
assigned to the user are checked against the roles that are assigned to a console preference
profile. The user is assigned the first console preference profile that matches the configured
authorization role. The views that are assigned in the console preference profile determine the
pages that are available to the user.
434 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 4. Managing dashboards
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
436 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
9 Custom dashboards and page management
Lesson 4. Managing dashboards
Uempty
Summary
Now that you have completed this unit, you can perform the
following tasks:
Describe the major functions of the Jazz for Service Management
visualization services
Describe how dashboard widgets access business data
Use Jazz for Service Management DASH server processes and tools
to build custom dashboards
Use Jazz for Service Management DASH server tools to manage
dashboards
Summary
Uempty
What this unit is about The RAD shell command interpreter provides a simple
approach to creating components in Tivoli Business
Service Manager. All data server functions available
through the graphical user interface are also available
with the command interpreter. You can use commands
with scripts to automatically update service models that
are based on dynamic data. This unit expands service
model creation with the RAD shell to create new service
instances. This unit also reviews commands to manage
customization artifacts that are used to back up and
restore deployment configurations.
How you check your progress You can check your progress in the following ways:
Student exercises
References SC23-6040-09 Business Service Manager 6.1.1
Administrators Guide
Objectives
When you complete this unit, you can perform the following
tasks:
Describe and use the RAD shell API features
Build and manage service models with the RAD shell API
Describe the command-line tools that are used to manage deployment
customizations
Objectives
What this lesson is about In this lesson, you learn how to start and use the RAD
shell command-line interface. You learn how to combine
RAD shell commands to create and configure business
services.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Describe and use the RAD shell API features
Build and manage service models with the RAD shell
API
440 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration
Lesson 1. Managing services with the command line
Uempty
References SC23-6040-09 Business Service Manager 6.1.1
Administrators Guide
You can use the RAD shell to create and configure service models with a command-line prompt,
rather than a Tivoli Integrated Portal configuration page. The RAD shell provides a complete
solution to creating elements with a command line. This solution can be useful in these
circumstances:
When you build large models
The RAD shell commands issue SOAP calls to the data server. The RAD shell can create and
update service instances with data not available through a database or from monitor events. An
example of such data is data from a log file.
442 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration
Lesson 1. Managing services with the command line
Uempty
Enter this command at the prompt to see the list of available commands:
help();
A list of some of the commands that are available with RAD shell is shown on the slide. Detailed
information about these commands is in the Reference unit of the Tivoli Business Service
Manager 6.1.1 Administrators Guide.
444 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration
Lesson 1. Managing services with the command line
Uempty
The combination of scripting languages and the RAD shell command interpreter provides a useful
tool to manipulate data from various sources. You can then use that information to create complete
service models and templates.
The general form of the RAD shell command to create a service instance is as follows:
addServiceInstance(templateName, instanceName,Description,slaName);
The example on the slide, is a command that creates a WebServer99 service instance. This
command tags the instance with the WebServer template. The slaName in this example is set to
Standard, but you can modify it with other SLA definitions. To create a new model, you create the
following instances for the new objects at all levels:
WebServers
WebFarms
WebApplications
446 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration
Lesson 1. Managing services with the command line
Uempty
This example creates a WebFarm instance and assigns a WebServer service instance.
Instructor demonstration
Instructor demonstration
448 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration
Lesson 1. Managing services with the command line
Uempty
Student exercises
Student exercises
What this lesson is about In this lesson, you learn about the artifacts database that
is installed on the data server. The artifacts database
stores information about Tivoli Business Service Manager
customizations. The database is used to back up or
migrate customizations from one environment to another.
You also learn how to use commands to export
configuration information from a Tivoli Business Service
Manager deployment.
450 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration
Lesson 2. Exporting and importing deployment customizations
Uempty
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Describe the command-line tools that are used to manage
deployment customizations
You can use the RAD shell interface to save complex service configurations in a text format. You
can use this information to restore a service definition or move service definitions from one Tivoli
Business Service Manager environment to another. You can use variations of the export command
to complete several actions:
The export command sends definition information to a file called
<DATA_SERVER_HOME>/tbsm/export/export.radsh. Multiple invocations of the command
append information to this file.
The exportCSV command creates the definition information in comma-separated value (CSV)
format to the following two files:
<DATA_SERVER_HOME>/tbsm/export/radexport_instances.csv
<DATA_SERVER_HOME>/tbsm/export/radexport_dependencies.csv
452 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration
Lesson 2. Exporting and importing deployment customizations
Uempty
Many customizations that are not controlled by the RAD shell API are managed from the artifacts
database. This database is maintained in the same DB2 environment that is used to store service
and template data. The artifacts are imported and exported with the Discovery Library Toolkit.
Artifacts are used as runtime values for the data server. To manage customization artifacts, you
export the artifacts, edit the exported file, and import the modifications into the database. You use
the putArtifact command to import modifications to the database. This command designates the
artifact as a customization, to differentiate artifacts that are stored as part of a standard installation.
454 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration
Lesson 2. Exporting and importing deployment customizations
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
456 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration
Lesson 2. Exporting and importing deployment customizations
Uempty
Summary
Now that you have completed this unit, you can perform the
following tasks:
Describe and use the RAD shell API features
Build and manage service models with the RAD shell API
Describe the command-line tools that are used to manage deployment
customizations
Summary
458 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
11 Maintenance and troubleshooting
What this unit is about Tivoli Business Service Manager uses DB2 to store
operational and historical data. In this unit, you review the
database schema that are used in Tivoli Business Service
Manager. You also learn the high-level tasks that are
required to implement backup components for the
ObjectServer, data server, and dashboard server. You
learn about the files and tools that are used to
troubleshoot Tivoli Business Service Manager operations.
Finally, you learn how to tune the Java virtual machine
settings for the dashboard server.
How you check your progress You can check your progress in the following ways:
Student exercises
References GI11-8054-08 Business Service Manager 6.1.1
Installation Guide
SC23-6040-09 Business Service Manager 6.1.1
Administrators Guide
GI11-8057-09 Business Service Manager 6.1.1
Troubleshooting Guide
http://www.ibm.com/developerworks/servicemanagemen
t/bsm/tbsm/index.html
DeveloperWorks-Tivoli Business Service Manager
460 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Uempty
Objectives
When you complete this unit, you can perform the following
tasks:
Describe the backup and restoration principles for the DB2 data server
database
Describe the Tivoli Business Service Manager server failover
configuration
Describe the support resources that are available to troubleshoot
deployment problems
Describe the Tivoli Business Service Manager application server log
files that are used to troubleshoot server problems
Tune the Tivoli Integrated Portal server Java Virtual Machine
parameters
Objectives
What this lesson is about In this lesson, you learn how to do the high-level tasks that
are required to maintain the Tivoli Business Service
Manager DB2 database. You also learn the high-level
tasks that are required to provide redundancy for the
major components of a Tivoli Business Service Manager
deployment.
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Describe the backup and restoration principles for the
DB2 data server database
Describe the Tivoli Business Service Manager server
failover configuration
462 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 1. Deployment administration
Uempty
References SC23-6040-09 Business Service Manager 6.1.1
Administrators Guide
Tivoli Business Service Manager uses DB2 to support management and storage of operational
service, template, historical, and customization data. Backing up all data regularly is critical.
464 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 1. Deployment administration
Uempty
For a production environment, follow documented backup and restoration guidelines. DB2 supports
high availability tools for critical databases.
You can implement failover for Tivoli Business Service Manager by running a primary and backup
data server in parallel. If the primary server stops, the backup server resumes as the primary
server. Additionally, you can configure the dashboard server to operate with multiple dashboard
servers for redundancy and load balancing.
466 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 1. Deployment administration
Uempty
Shown here is a logical diagram for a Tivoli Business Service Manager 6.1 failover configuration.
After you configure it, primary data server failover to the backup data server is automatic. Also
shown in this diagram is redundancy for the ObjectServer. Any probes that provide monitoring
events to the ObjectServer can also be configured to send events to a backup ObjectServer.
468 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 1. Deployment administration
Uempty
The backup data server must be installed as a backup server. You cannot convert a primary data
server installation to be used as a backup data server.
470 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 1. Deployment administration
Uempty
You can configure two or more dashboard servers to provide redundancy. The addition of a
specially configured instance of DB2 9.7 and IBM HTTP Server can provide automatic load
balancing. All dashboard servers must exchange Certificates of Authority to implement
server-to-server trust for security.
The dashboard servers must efficiently switch to a backup data server if a failure occurs. Both data
servers must use identical keystores. The default internal file-based user and group repository is
local to each dashboard server. The internal repository cannot be used in a failover configuration.
You use the IBM HTTP Server to provide a load-balancing front end to multiple dashboard servers.
You must configure all participating dashboard servers for trust and connection information. The
HTTP Server plug-in that is provided with the Tivoli Business Service Manager 6.1 installation
media provides the load-balancing software.
472 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 1. Deployment administration
Uempty
You must configure the data server for failover during installation. The installation program prompts
you to choose whether to configure the server as part of a failover scheme. The primary and
backup can be installed separately, but you must initially configure them during installation. The
database administrative user name and password must be identical for both the primary and
backup servers.
Control port (RMI port) of the backup server. This port must match the control port that is
configured on the backup server.
Database port of backup server. This port must match the port that is configured on the backup
server.
Control port (RMI port) of the primary server. This port must match the control port that is
configured on the primary server.
Database port of the primary server. This port must match the database port that is configured
on the primary server.
The failover configuration file automates the final setup of your failover environment. Record the
configuration information for each server in your failover environment. Then, use the file with the
fo_config command to complete failover setup. To create a sample configuration file that lists all
required settings, run fo_config with no options and redirect the output to a file, like the following
one:
$TBSM_HOME/bin/fo_config > failoverconfig.txt
474 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 1. Deployment administration
Uempty
When configuration data or the service state is changed, changes must be replicated in the
database and critical XML files of the primary and backup servers. When you start the servers for
the first time, you must start the primary data server first. When the backup data server starts, it
checks to see whether the primary data server is started. The backup data server quits the start
process if the primary server is not started. When the primary server starts, it sends a message that
the backup must be started so that the primary can complete its own startup. When the backup
starts, it then directs synchronizing of databases with the primary server.
When synchronization is complete, the backup instructs the primary to enter operational mode. The
primary server then loads its configuration, processes, and events that occurred offline. It begins
processing in real time. When the primary server starts real-time processing, the backup server
finishes its startup and goes into standby mode.
If both servers are running and the acting primary server stops, the backup detects this event. The
backup server then enters primary mode. The backup server loads its state from the database,
starts all services, and begins real-time processing.
What this lesson is about In this lesson, you learn about different support tools that
are available to troubleshoot Tivoli Business Service
Manager problems. Some tools provide general
reference information, and some tools provide analysis of
your deployment. You also learn which log files are
produced by the major Tivoli Business Service Manager
components.
476 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 2. Troubleshooting and support resources
Uempty
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Describe the support resources that are available to
troubleshoot deployment problems
Describe the Tivoli Business Service Manager
application server log files that are used to
troubleshoot server problems
Troubleshooting tools
All Tivoli Business Service Manager components generate log
files. These files are essential for investigating and analyzing
problems.
In addition to log file review, several software tools are
available:
IBM Support Assistant
Tivoli Business Service Manager Information Center
Tivoli Business Service Manager wiki
IBM developerWorks
Tivoli software user communities
Troubleshooting tools
System logs for key areas of the software track operational aspects of Tivoli Business Service
Manager 6.1. Consult these files when troubleshooting a problem with system operation.
478 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 2. Troubleshooting and support resources
Uempty
Audit logging
Audit logging
Audit logging is enabled by default. This data is useful for generating change reports and locating
system problems. The data is stored in the DB2 database.
Log files that are related to the data server operation are in these directories:
$TIP_HOME/profiles/TBSMProfile/logs/tbsm
$TIP_HOME/profiles/TBSMProfile/logs/server1
Log files that are related to the Tivoli Integrated Portal, or dashboard, server operation are in this
directory:
$TIP_HOME/profiles/TIPProfile/logs/server1
480 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 2. Troubleshooting and support resources
Uempty
For any problem under investigation, the log files might not contain sufficient information to pinpoint
the problem. You can set the logging detail to contain increased logging information.
This screen capture shows the procedure for increasing the log level from Normal to Detailed.
Increase this level only during the troubleshooting phase of problem resolution. After the problem is
resolved, return the logging level detail to Normal to reduce the load on the server.
Note: Always disable the policy log after you finish the troubleshooting.
When you troubleshoot Impact policies that are related to Tivoli Business Service Manager 4.2.1,
you must increase the logging detail specifically for Impact policies. The screen capture shows the
procedure. You must disable the additional log information when the problem is identified.
482 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 2. Troubleshooting and support resources
Uempty
Configure the Tivoli Integrated Portal logs with the administrative console. Click the
Troubleshooting > Logs and Trace task. Click server1 to configure trace and message log detail.
To set the change log detail levels, you use these steps:
1. Click Change Log Detail Levels.
484 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 2. Troubleshooting and support resources
Uempty
For each of the elements that require a change in the log level, complete the following tasks:
1. Right-click the name of the element.
2. Click Message and Trace Levels and choose the required minimum severity level to write to
the log files.
3. Click OK.
IBM developerWorks
IBM developerWorks
To use some of the tools in IBM developerWorks, use the following options:
Click Business service management in the Tivoli Solutions section to review solution white
papers.
Click Submit an article or idea in the Community section to share a solution, white papers, or
other ideas.
486 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 3. Tuning the dashboard server
Uempty
What this lesson is about In this lesson, you learn the procedure to test and
configure the Java Virtual Machine garbage heap
parameters. You learn the impact of the memory
configuration on server performance.
What you should be able to do After completing this lesson, you should be able to
perform the following task:
Tune the Tivoli Integrated Portal server Java Virtual
Machine parameters
The IBM Support Assistant (ISA) provides a software framework to support troubleshooting multiple
IBM software products. Application-specific plug-in modules are designed to gather log and
operational data and bundle the information in a format that can be electronically submitted to IBM
Support. Through the Internet, the ISA provides links to product and support data.
488 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 3. Tuning the dashboard server
Uempty
The ISA client provides three major functions to support troubleshooting software problems:
Find Information: Provides a centralized way to search the Internet for product information and
training.
Analyze Problem: Provides several tools to automate data collection and analysis.
Collect and Send Data: Provides tools to gather system data and automate the creation of an
electronic service request with IBM Support. Tools are also provided to track and update any
submitted electronic service request.
After the client is started, click Update > Find new > Product Add-ons to see a list of available
product plug-in modules. If provided with the plug-ins, you might also be prompted to select one or
more analysis tools. After you select the products, complete the installation wizard to finish the
installation.
490 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 3. Tuning the dashboard server
Uempty
The data and dashboard servers use the Java virtual machine (JVM) environment in the
WebSphere Application Server. Tuning is critical to server performance. Too little memory that is
allocated to JVM garbage collection can cause application failure. Too much memory wastes
system resources and reduces performance.
JVM tuning requires controlled trials with different initialHeapSize and maximumHeapSize values
for the server JVM. Analysis of the garbage collection log files is required to determine the optimal
configuration.
492 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 3. Tuning the dashboard server
Uempty
You can use the following method for evaluating the tuning configuration:
Turn on verbose garbage collection for the JVM.
Use a tool to create a repeatable, representative workload on the server.
Evaluate the log data to find the optimal operating values.
Use the IBM Support Assistant diagnostic tools.
The IBM Support Assistant provides several tools for analyzing general log files and JVM log files.
The server must be configured to generate JVM garbage collection logs for analysis. Setting the
initialHeapSize and maximumHeapSize to the same values is more efficient for testing.
494 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 3. Tuning the dashboard server
Uempty
You can use the IBM Support Assistant tool to see multiple
views of the garbage collection log data.
The summary data indicates relatively short, but frequent,
garbage collection cycles.
Copyright IBM Corporation 2013 33
The tools that are provided with the IBM Support Assistant workbench provide graphical and
tabular analysis tools. This screen image shows a graphical view of the heap size versus the
amount that is used before and after garbage collection.
To create consistent tests, you should use a tool that can consistently simulate a server workload
that represents typical server load for your environment. To test the load, run tests with default
values, increase and decrease operational values, and evaluate the effects on server performance.
496 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 3. Tuning the dashboard server
Uempty
Instructor demonstration
Instructor demonstration
Student exercises
Student exercises
498 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting
Lesson 3. Tuning the dashboard server
Uempty
Summary
Now that you have finished this unit, you can perform the
following tasks:
Describe the backup and restoration principles for the DB2 data server
database
Describe the Tivoli Business Service Manager server failover
configuration
Describe the support resources that are available to troubleshoot
deployment problems
Describe the Tivoli Business Service Manager application server log
files that are used to troubleshoot server problems
Tune the Tivoli Integrated Portal server Java Virtual Machine
parameters
Summary
500 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
12 Single sign-on and application
integration
What this unit is about This unit describes the major tasks that are involved in
configuring Tivoli Business Service Manager to support
single sign-on. You also learn how to configure and use
launch-in-context for supported Tivoli Business Service
Manager applications.
How you check your progress You can check your progress in the following ways:
Student exercises
http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/index.jsp
?topic=/com.ibm.tip.doc/ttip_install_sso.html
Configuring Single Sign-on for Tivoli Integrated Portal 2.2
http://www.ibmsystemsmag.com/ibmi/administrator/secu
rity/A-Single-Sign-On-Primer/
A Single Sign-on Primer
502 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
12 Single sign-on and application integration
Uempty
Objectives
When you complete this unit, you can perform the following
tasks:
Describe the major tasks involved in configuring Tivoli Business
Service Manager to support single sign-on (SSO)
Describe how the federated repository in the dashboard server
supports user and group authentication
Describe how launch-in-context (LIC) is used to connect to
applications that support SSO
Configure the dashboard server to participate in an SSO domain
Objectives
What this lesson is about In this lesson, you learn the technical principles of single
sign-on security between applications. You learn how to
configure single sign-on in the dashboard server. You also
learn how launch-in-context is implemented from one
application to another.
504 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
12 Single sign-on and application integration
Lesson 1. Managing single sign-on
Uempty
What you should be able to do After completing this lesson, you should be able to
perform the following tasks:
Describe the major tasks that are involved in
configuring Tivoli Business Service Manager to
support single sign-on (SSO)
Describe how the federated repository in the
dashboard server supports user and group
authentication
Describe how launch-in-context (LIC) is used to
connect to applications that support SSO
Configure the dashboard server to participate in an
SSO domain
506 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
12 Single sign-on and application integration
Lesson 1. Managing single sign-on
Uempty
4
2
LTPA token is
generated and SSO application 2
1 stored in user
browser.
LTPA token
LTPA token is
User logs on to https://localhost:16311/ibm/console evaluated. If
Tivoli Business valid, user is
Service Manager automatically
3 LTPA token
console. authenticated.
This diagram shows a high-level view of the SSO process. A user authenticates to the first
application by supplying a user name and password. An LTPA authentication token is encrypted
and stored as a cookie in the user browser. A second console connection request passes the token
to the second application. The token is decrypted, and the user is authenticated without manually
providing the user name and password.
This slide shows the tasks that must be completed to configure SSO for Tivoli Business Service
Manager. All applications must share a common user and group repository, such as an LDAP
server.
508 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
12 Single sign-on and application integration
Lesson 1. Managing single sign-on
Uempty
SSO is configured with the WebSphere administration console. First, you click the Security >
Global Security task in the console. Then, you click the Web security > Single sign-on (SSO)
link to enable and configure the SSO IP domain scope. Only server connections in the same IP
domain can use SSO.
Each participating SSO application must generate and share a server key. The key is used to
securely decrypt a user LTPA token.
510 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
12 Single sign-on and application integration
Lesson 1. Managing single sign-on
Uempty
When a user completes a console connection, both console sessions are validated with the LTPA
token. Logging off the second connection invalidates the initial console connection. The user is
required to authenticate to the initial console.
Configuring launch-in-context
Right-click a service instance to see a list of context menus .
The LIC menus depend on the properties that are assigned to
the service instance.
For example, service instances that are created with IBM Tivoli
Monitoring DLA include the following service parameters:
IBM_Tivoli_Monitoring_Services_sourceContactInfo
IBM_Tivoli_Monitoring_Service_sourceToken
Configuring launch-in-context
Right-click action menus are configured for several service objects in Tivoli Business Service
Manager. Information that is supplied in the service instance configuration is used to connect to
another application console. The connection is made with the context information in the service
object.
512 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
12 Single sign-on and application integration
Lesson 1. Managing single sign-on
Uempty
This screen image shows a launch menu that is available with a service instance, which is created
with the Discovery Library Toolkit. The remote console and service instance information are passed
to the application with service instance context information.
Instructor demonstration
Instructor demonstration
514 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
12 Single sign-on and application integration
Lesson 1. Managing single sign-on
Uempty
Student exercises
Student exercises
Summary
Now that you have finished this unit, you can perform the
following tasks:
Describe the major tasks involved in configuring Tivoli Business
Service Manager to support single sign-on (SSO)
Describe how the federated repository in the dashboard server
supports user and group authentication
Describe how launch-in-context (LIC) is used to connect to
applications that support SSO
Configure the dashboard server to participate in an SSO domain
Summary
516 IBM Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Back pa
Authorized
Training
ibm.com/training
Printed in Ireland
CT4QDEN
CT4QDEN