Beruflich Dokumente
Kultur Dokumente
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
iv Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
Contents
vi Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
About these exercises
The lab environment consists of three Linux virtual images using the SUSE Linux Enterprise Server
11, 64-bit operating system. The images and installed components are summarized in the following
table:
The following diagram lists the applications that are installed on each of the virtual images in the
laboratory exercise environment. The SSO Realm is a logical entity that is configured on each
application server to support single sign-on and application launch-in-context.
The primary user names and corresponding passwords that are used with each virtual image are
listed in the following table:
The jazz01 and itm01 images show several task launch icons on the desktop of the primary logon
user. These icons are labeled to correspond to scripts or applications that are started by double-
clicking the icon. Custom desktop menus are installed on the tbsm01 image. You click the Start
button, in the bottom left of the desktop, to access the menu list. The launch tasks are provided to
simplify laboratory steps that otherwise require the student to enter lengthy commands from a
command line. This laboratory guide assumes that the virtual images, but not all virtual image
applications, are started before beginning the first exercise. The images are started with separate
instructions provided to the student, depending on the virtual image host environment.
viii Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
There are no student exercises for this chapter.
In these exercises, the host name of the Tivoli Business Server Manager 6.1.1 virtual server is
tbsm01. The primary user account name is tivoli, with a password of object00. The tivoli user
account was used to install all software. You must be logged on to the image with the installation
user ID to control all Tivoli Business Service Manager processes.
ObjectServer
Data server
Dashboard server
Uempty Verify the ObjectServer, data server, and dashboard server are operational.
Log on to the Tivoli Business Service Manager console. Verify that the environment is
functional.
Log off the console, stop the dashboard server, data server, and ObjectServer.
a. Use the information in the following table to complete the logon process:
2. Open a command window. Click Start at the lower left corner of the tbsm01 desktop and select
Terminal.
Note: The previous command forces the ObjectServer to run as a background process, using
the ampersand (&) symbol. The command-line prompt is not automatically returned in the
command window. Click the window and press the Enter key.
4 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 1. Controlling and using Tivoli Business Service Manager components
8. You are prompted to enter the user ID and password for a user with administrative privileges on
the data server. Enter the user ID and password shown in the following table:
10. You are prompted to enter the user ID and password for a user with administrative privileges on
the dashboard server. Enter the user ID and password that is shown in the following table:
6 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 1. Controlling and using Tivoli Business Service Manager components
Uempty The command output indicates that the dashboard server is operational.
12. The browser is configured to start with a blank page. Enter the Tivoli Business Service Manager
console address:
https://tbsm01.tivoli.edu:16311/ibm/console
13. When prompted for a user ID and password, use the values in the following table.
14. Click the View menu to show the available task lists, or views.
8 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 1. Controlling and using Tivoli Business Service Manager components
Uempty Views are configured to show groups of administrative or operational tasks. The default view is the
All tasks view. The tasks in a view are shown in a tree format in the pane on the left side of the
console. You can collapse, resize, or expand this pane. A default Tivoli Business Service Manager
6.1.1 installation has five views that are defined:
All tasks (the default)
My Tasks
Tivoli Netcool/Impact
Tivoli Business Service Manager
15. Verify that the Tivoli Business Service Manager environment is functional. Click Administration
> Service Configuration in the All tasks list.
The Service Navigation and Service Editor portlets are shown in the console workspace.
Note: The Service Navigation portlet shows a list of several service model templates. The
Service Editor portlet shows no data because no service is selected in the Service Navigation
template. This behavior is normal.
Logging off the console, stopping the dashboard server, data server, and
ObjectServer
16. Log off the console. Click Logout in the upper right of the console window. Do not close the
web browser application.
17. Stop the dashboard server. Enter these commands in a command window on the tbsm01 virtual
image:
cd /opt/IBM/tivoli/tipv2/profiles/TIPProfile/bin
./stopServer.sh server1
When prompted for a user ID and password, use the values in the following table.
10 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 1. Controlling and using Tivoli Business Service Manager components
19. Stop the OMNIbus ObjectServer. Determine the process identification (PID) number under
which the ObjectServer was started. Enter this command:
cat /opt/IBM/tivoli/netcool/omnibus/var/NCOMS.pid
20. Use the Linux kill command to stop the PID shown in the previous step. The number that is
shown on your virtual machine is different from this example. Enter this command to stop the
ObjectServer, using your PID number:
kill 7390
2. Click the command window and press the Enter key when the script completes.
3. Open the Firefox web browser. Click the Start > Firefox 17 ESR desktop menu or use the
browser instance that you opened in the previous exercise.
12 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 2. Creating templates
Uempty 4. Connect to the Tivoli Integrated Portal (dashboard) server console. Click Bookmarks > Tivoli
Integrated Portal Console.
5. Start the template creation process. Click Administration > Service Configuration in the All
tasks view.
6. In the Service Navigation portlet, verify that the Templates menu is selected.
7. Create a template.
a. Click the Create New Template icon.
b. Enter the Template Name and Description fields as shown in the following table:
Important: You must enter the template name using the letter case that is shown in this step. In
subsequent exercises, you start simulated monitor event scripts. The event scripts require the
event field letter case to match incoming event field values.
c. Click Browse to assign an icon to this template. The selected icon is associated with all
service instances based on this template. The icon is shown in both the service tree and
14 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 2. Creating templates
Uempty service viewer portlets. The icon provides a visual indication of the template that is assigned
to a service.
d. Click an icon. This icon is a visual reference only. The icon that is selected has no effect on
the way a service instance tracks the service status. After clicking, the window closes.
Hint: Administrators can add custom icons to the default list shown in the previous screen
image. The procedure for adding custom icons is detailed in the Adding custom display icons
section of the Custom Settings unit of the Business Service Manager 6.1.1 Customization Guide.
8. Create a template to model a database server, using the same procedure that is used to create
the WebServer template.
a. Click the Create New Template icon.
b. If you did not save the WebServer template, you see a warning message. Click Cancel and
save the WebServer template.
Important: You must click the Create New Template icon in the Service Navigation portlet for
each new template. For this example, the template information from the WebServer template that
you created is still shown in the Service Editor. If you do not click the Create New Template icon,
saving the Database template information overwrites the previously saved WebServer template.
c. Enter the Template Name and Description fields exactly as shown in the following table:
16 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 2. Creating templates
Uempty f. Save the Database server template definition. Click the Service Editor portlet Save icon.
The Templates section in the Service Navigation portlet updates to show a list similar to this
screen image.
9. From the Templates list in the Service Navigation portlet, click the WebServer template. If not
already selected in the Service Editor portlet, click the Edit Template WebServer tab.
b. You create a rule that evaluates an incoming ObjectServer event and determine the state of
the service instance. Select Based on a Good, Marginal, and Bad Threshold for the type
of rule to create.
18 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 2. Creating templates
h. The service instance name is based on the value of the Node field of the incoming event.
Leave Node in the Selected Instance Name Fields.
i. The AlertGroup and Severity field values from the incoming event are used to evaluate the
rule status. Remove AlertKey from the Selected Filter Fields list.
20 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 2. Creating templates
Uempty j. Click AlertKey in the Selected Filter Fields list. Click << to move AlertKey to the
Available Filter Fields list.
k. Add AlertGroup to the Selected Filter Fields list. Click AlertGroup in the Available Filter
Fields list. Click >> to move the field to the Selected Filter Fields list.
Note: The contents of the Threshold Filter section of the form automatically refresh as the
fields in the Available Filter Fields list changes.
When completed, the Selected Filter Fields list looks like this screen image.
l. By default, two rows are contained in the Threshold Filters section. Add a third threshold
filter row. Click the Add a Threshold Filter icon.
Configure the threshold filters so that the output status of the rule evaluation uses the following
criteria:
If AlertGroup=WebServerStatus AND Severity = 5, set status to Bad
Hint: The Severity field in a Netcool/OMNIbus event is an integer value between 0 and 5.
Netcool/OMNIbus internally maps the integer value to a named value. For example, a Severity
value of 0 is mapped to Clear, a severity value of 3 is mapped to Minor, and a severity value of 5 is
mapped to Critical. Tivoli Business Service Manager tracks the status of a service instance or
service model. The status of a service is the result of template rule evaluation. Event severity is
one of many criteria that Tivoli Business Service Manager can use to determine a business
service status.
22 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 2. Creating templates
Uempty 11. Configure the threshold filters as shown in the following screen image.
a. Select the equal (=) logical operator from the AlertGroup menu.
b. Select the equal (=) logical operator from the Severity menu.
c. Configure the first threshold filter. Enter WebServerStatus in the AlertGroup column.
f. Configure the second threshold filter. Enter WebServerStatus in the AlertGroup column.
i. Configure the third threshold filter. Enter WebServerStatus in the AlertGroup column.
n. Save the updated template definition. Click the template Save icon. The icon is at the upper
left of the Service Editor portlet.
12. Create an incoming status rule that evaluates a Database service instance that is based on
matching incoming monitor events.
a. Click Database in the Templates section of the Service Navigation portlet.
b. Click the Incoming Status Rule icon in the Service Editor portlet.
f. The service instance name is based on the value of the Node field of the incoming event.
Leave Node in the Selected Instance Name Fields.
24 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 2. Creating templates
Uempty g. The AlertGroup and Severity field values from the incoming event are used to determine
the rule status. Click AlertKey in the Selected Filter Fields list. Click << to move AlertKey
to the Available Filter Fields list.
h. Click AlertGroup in the Available Filter Fields list. Click >> to move the field to the
Selected Filter Fields list.
When completed, the Selected Filter Fields list looks like this screen image.
i. Add a third threshold filter. Click the Add a Threshold Filter icon.
13. Configure the threshold filters as shown in the following screen image.
a. Select the equal (=) logical operator from the AlertGroup menu.
b. Select the equal (=) logical operator from the Severity menu.
c. Configure the first threshold filter. Enter DatabaseStatus in the AlertGroup column.
d. Select Critical from the Severity column menu.
f. Configure the second threshold filter. Enter DatabaseStatus in the AlertGroup column.
g. Select Minor from the Severity column menu.
i. Configure the third threshold filter. Enter DatabaseStatus in the AlertGroup column.
26 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 2. Creating templates
Uempty n. Save the updated template definition. Click the template Save icon. The icon is at the upper
left of the Service Editor portlet.
DatabaseStatusRule is summarized under the Rules tab in the template editor.
Create a DBCluster template that is based on the aggregated status of service instances that
are based on the Database template.
Create a WebApplication template, the status of which is based on the aggregation of both the
DBCluster and WebFarm template status.
b. Click the Create New Template icon in the Service Navigation portlet.
28 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 3. Creating templates with dependencies
Uempty g. Dependency rules are created in the Rules tab in the Service Editor. Click the Create
Good, Marginal, Bad Aggregation Rule icon.
h. Enter a name for the rule. Enter the following value in the Rule Name field:
WebFarmStatusRule
i. Select a child service for which the status is aggregated. For this exercise, the WebServer
template is the child template of the WebFarm template. Select WebServer from the Child
Rule/Mapping list.
l. Configure the rule to evaluate the aggregate status of all child WebServer services to
determine the status of the parent WebFarm service. Select % of children for the
Condition Type.
m. Leave the Weight Property (Optional) and Weight Default fields at their default values.
n. Select the child service state that is aggregated for the WebFarm evaluation. Configure the
rule to aggregate all child WebServer services in a Bad state. Select Bad from the Child
Status menu.
o. Configure the Output Severity Threshold values. Configure the rule to evaluate the status
according to the following logic statements:
Set the WebFarm instance status to Bad when at least 70% of the children WebServer
instances are in a Bad state.
Set the WebFarm instance status to Marginal when at least 30% of the children
WebServer instances are in a Bad state.
30 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 3. Creating templates with dependencies
Uempty
Creating a DBCluster template
Create the DBCluster template using the WebFarm template creation process. For the DBCluster
template, configure the dependency rule so that if any child service instance status is Bad, the
DBCluster-based service is considered Bad.
f. Click an icon to represent the DBCluster template in Service Tree or Service Viewer
portlets.
g. Create a dependency rule using the toolbar icon that is located under the Rules tab in the
Service Editor. Click the Create Good, Marginal, Bad Aggregation Rule icon.
h. Enter a name for the rule. Enter the following value in the Rule Name field:
DBClusterStatusRule
i. Select a child service for which the status is aggregated. For this exercise, the Database
template is the child template of the DBCluster template. Select Database from the Child
Rule/Mapping list.
k. Configure the rule Condition section. Configure the rule so that the status of any child
service that is based on the Database template is aggregated to determine the status of the
DBCluster parent. Select Child template for the Propagation Type.
l. Configure the rule to set the DBCluster status to the worst status of any contained
Database child service. Select Any child for the Condition Type.
32 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 3. Creating templates with dependencies
c. Create a Good, Marginal, Bad Aggregation Rule. This rule is dependent on the status of
DBCluster template services. Create the rule as outlined in this table:
4. Create a second Good, Marginal, Bad Aggregation Rule in the WebApplication template. This
rule is dependent on the status of WebFarm template services. Create the rule as outlined in
this table.
f. In the Service Editor portlet, save the new template. Click the Save icon. The
WebApplication template lists the two summarized dependency rules.
34 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 3. Creating templates with dependencies
Uempty The Templates section of the Service Navigation portlet shows the complete
WebApplication template hierarchy.
Create all WebFarm service instances and assign dependent WebServer instances.
Create all DBCluster service instances and assign dependent Database instances.
Create WebApplication instances and assign dependent WebFarm and DBCluster instances.
36 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 4. Creating and testing service instances
Uempty
Creating all WebServer service instances
1. Create a WebServer service instance called WebServer1.
a. Select the Services menu of the Service Navigation portlet. Click the menu to the right of
Templates, and click Services.
c. Enter a Service Name of WebServer1. Maintain the case of the service name as written.
d. Leave the Service Level at the default setting.
2. Assign the WebServer template to the WebServer1 definition. The service instance behavior is
based on the assigned template. The list of available templates is in the Templates tab.
a. Click WebServer in the Available Templates column. Click >> to move WebServer to the
Selected Templates column.
b. Click the Save icon to save the service instance definition. The WebServer1 instance is
shown in the Service Navigation portlet, similar to the following screen image.
Hint: The Services view in the Service Navigation portlet refreshes every 60 seconds, by
default. The portlet does not provide a refresh icon to force a view update. Click the Service
Navigation menu and select Services to force a portlet view refresh.
3. Create four more WebServer service instances, using the information in the following table.
Assign the WebServer template to each service instance.
38 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 4. Creating and testing service instances
Uempty
Service instance name Template assigned
WebServer3 WebServer
WebServer4 WebServer
Important: You must click the Create New Service icon for each instance. Saving a service with
a new name without clicking the Create New Service icon renames the most recently created
service.
b. Enter a Service Name of Database1. Maintain the case of the service name as written.
5. Assign the Database template to the Database1 definition. The service instance behavior is
based on the assigned template. The list of available templates is the Templates tab.
a. Click Database in the Available Templates column. Click >> to move Database to the
Selected Templates column.
b. Click the Save icon to save the service instance definition. The Database1 instance is
shown in the Service Navigation portlet. Refresh the Service Navigation portlet view if the
Database1 instance is not immediately shown.
Hint: The Services view in the Service Navigation portlet refreshes every 60 seconds, by
default. The portlet does not provide a refresh icon to force a view update. Click the Service
Navigation menu and select Services to force a portlet view refresh.
6. Create three more Database service instances using the information in the following table.
Assign the Database template to each service instance.
40 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 4. Creating and testing service instances
Uempty The WebServer and Database instances in the Service Navigation portlet look similar to the
following image. The icons that are used during template creation provide a quick way to
visually verify that the services are based on the appropriate templates.
b. Enter a Service Name of DBCluster1. Maintain the case of the service name as written.
8. Assign the DBCluster template to the DBCluster1 definition. The service instance behavior is
based on the assigned template. The list of available templates is shown in the Templates tab.
a. Click DBCluster in the Available Templates column.
c. Click Search.
d. Move the following Database service instances from the Available Services column to the
Selected Services column:
Database1
42 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 4. Creating and testing service instances
Uempty Database2
e. Save the DBCluster1 service definition. Click the Save icon in the Service Editor portlet.
10. The DBCluster1 service instance is now listed in the Service Navigation portlet, showing a plus
symbol (+), indicating that a service hierarchy exists. Click the plus symbol to show the
dependent services.
11. Create the DBCluster2 service instance. Use the previous procedure that you used to create
DBCluster1. DBCluster2 uses Database2 and Database3 as dependent services. Use the
information in the following table to configure the service.
Template Dependent
Instance name assigned services
DBCluster2 DBCluster Database2,
Database3
Note: Database2 is a dependent service for both DBCluster1 and DBCluster2. Tivoli Business
Service Manager allows services to be dependencies to more than one parent service.
b. Enter a Service Name of WebFarm1. Maintain the case of the service name as written.
44 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 4. Creating and testing service instances
Uempty 13. Assign the WebFarm template to the WebFarm1 definition. The service instance behavior is
based on the assigned template. The list of available templates is the Templates tab.
a. Click WebFarm in the Available Templates column.
14. Assign the dependent WebServer services to the WebFarm1 service instance.
a. Click the Dependents tab
b. Move the following WebServer service instances from the Available Services column to
the Selected Services column:
WebServer1
WebServer4
c. Save the WebFarm1 service definition. Click the Save icon in the Service Editor portlet.
15. The WebFarm1 service instance is now listed in the Service Navigation portlet. The plus symbol
(+) next to the service indicates that a service hierarchy exists. Click the plus symbol to see the
dependent services.
16. Create the WebFarm2 service instance. Use the previous procedure that you used to create
WebFarm1. WebFarm2 uses WebServer2, WebServer3, and WebServer5 as dependent
services. Use the information in the following table to configure the service.
b. Enter a Service Name of InetBanking. Maintain the case of the service name as written.
46 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 4. Creating and testing service instances
Uempty 18. Assign the WebApplication template to the InetBanking definition. The service instance
behavior is based on the assigned template. The list of available templates is the Templates
tab.
a. Click WebApplication in the Available Templates column. Click >> to move
WebApplication to the Selected Templates column.
b. Add the dependent WebFarm1 and DBCluster1 services to the InetBanking service
instance. Click the Dependents tab and add the following server instances as dependents:
WebFarm1
DBCluster1
c. Save the InetBanking service definition. Click the Save icon in the Service Editor portlet.
19. The InetBanking service instance is now listed in the Service Navigation portlet. The plus
symbol (+) next to the service indicates that a service hierarchy exists. Expand all levels of the
service model to see the dependent services.
20. Create the AlliedSteel service instance. Use the previous procedure that you used to create
InetBanking. AlliedSteel is based on the WebApplication template. WebFarm2 and DBCluster2
are dependent services. Use the information in the following table to configure the service.
21. Change the default list order for InetBanking and AlliedSteel in the Service Navigation portlet.
By default, alphanumeric rules list AlliedSteel before InetBanking. Change the view order by
setting a value for the Order parameter for the InetBanking service instance.
a. Click InetBanking in the Services view of the Service Navigation portlet.
d. Save the InetBanking service modification. Click the Save icon in the Service Editor portlet.
48 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 4. Creating and testing service instances
Uempty 22. Refresh the Services view in the Service Navigation portlet. The InetBanking service instance
is listed before the AlliedSteel service instance.
23. Test the effects of status changes for WebServer service instances. Click the InetBanking
service in the Service Navigation portlet.
24. The Service Editor portlet contains two tabbed pages. You used the Edit Service page tab to set
and modify service and template parameters. To see a visual representation of the service
state, click the View Service InetBanking page tab.
A Java applet is downloaded from the Tivoli Business Service Manager data server and the full
service model is shown.
50 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 4. Creating and testing service instances
Uempty 25. All test event scripts must be started on the tbsm01 virtual image. Send a Severity 5 test event
to the Database1 service instance.
a. Select the Start > TBSM Exercises > Unit02 > Exercise 04 > Database1Down desktop
menu.
The Database1 status color changes to red, indicating the service instance is in a Bad state.
The DBCluster and WebApplication dependency rules cause the Database1 state change
to be propagated, changing DBCluster1 and InetBanking to a Bad state.
Hint: The Service Viewer contents are refreshed on a timed basis. To force an update to the
view, click the Refresh icon on the Service Viewer toolbar.
52 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
2 Service model basics exercises
Exercise 4. Creating and testing service instances
Uempty 26. Set the Database1 service instance state to Good. Select the Start > TBSM Exercises >
Unit02 > Exercise 04 > Database1Up menu on the tbsm01 virtual image.
A Database1 status event, with a Severity of 0, is sent to the ObjectServer. You see the
state of Database1 change to Good. The Good state is propagated to DBCluster1 and
InetBanking.
27. Select any of the test monitor scripts in the Start > TBSM Exercises > Unit02 > Exercise04
menu folder. Observe the status change results for all levels of InetBanking and AlliedSteel.
DatabaseDown, DatabaseUp, WebServerDown, and WebServerUp events create different
effects on the service model hierarchy. These different effects are based on the rules that are
associated with each template and service model combination.
28. Set all service models to a Good state. For any WebServer or Database service instance in a
Bad state, select the corresponding WebServer or Database Up script. For example, if
WebServer4 is in a Bad state, select Start > TBSM Exercises > Unit02 > Exercise 04 >
WebServer4Up.
54 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
3 Expanding service model functions
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.
b. Click WebServer in the list of templates. WebServer is the lowest-level template in the
WebApplication template hierarchy.
3. Modify the Instance Name section to evaluate both the AlertKey and Node fields to determine
the unique service name identifier for a web server.
a. Click the AlertKey field in the Available Instance Name Fields column.
b. Click the double arrow (>>) icon to move the AlertKey field selection to the Selected
Instance Name Fields pane. The result looks like the following screen image.
56 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Updating web server templates
Uempty c. Save the updated WebServerStatusRule. Click OK at the lower right of the rule form.
4. Save the updated template definition. Click the Save icon in the Service Editor portlet.
All WebServer template-based service instances are updated to use the additional AlertKey
field value.
5. Update all WebServer service instances to respond to incoming events with an AlertKey value
of 80. The AlertKey value is used in this example to represent the listening port of the web
server application. Modify the WebServer1 service instance configuration.
a. Select the Services menu in the Service Navigation portlet.
b. Click WebServer1. WebServer1 is at the bottom level of the InetBanking service model.
d. In the Field Values column, change the AlertKey value from WebServer1 to 80. Leave the
Node field value at WebServer1.
The WebServer1 service instance matches any incoming monitor event where the Node
field is set to WebServer1 and the AlertKey field is set to 80.
e. Save the modified service instance definition. Click the Save icon.
6. Use the previous procedure to modify the WebServer2, WebServer3, WebServer4, and
WebServer5 service instance configurations. Use the information in the following table:
Original Modified
Identification Field Identification Field
Service instance AlertKey value AlertKey value
WebServer2 WebServer2 80
WebServer3 WebServer3 80
WebServer4 WebServer4 80
WebServer5 WebServer5 80
58 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Updating web server templates
Uempty 8. Send a test event for WebServer1. Select the Start > TBSM Exercises > Unit03 > Exercise01
> WebServer1Down desktop menu.
9. Verify that the WebServer1 status color changes to red, indicating a Bad state. View the status
in the Service Editor portlet on the right side of the console.
10. Review the values for the AlertKey and Node event fields in the ObjectServer. Click the
Availability > Events > Active Event List (AEL) task in the All Tasks view. The Active Event
List opens in a tabbed window in the console.
11. A custom event view for this course is configured for the Active Event List portlet. Select
TBSMAdminTraining in the Views menu.
Two Critical severity events for WebServer1 are shown. The event sent by the event script
shows an AlertGroup value of WebServerStatus and the AlertKey value is 80.
Hint: The two events with the class value of SLAM were generated internally as part of the rule
evaluation process within the WebServer and WebFarm templates.
60 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Updating web server templates
Uempty 12. Change the WebServer1 service instance state to Good. Select the Start > TBSM Exercises >
Unit03 > Exercise01 > WebServer1Up desktop menu.
b. Click the Edit Service WebServer4 tab in the Service Editor portlet.
c. Click the Identification Fields tab in the service configuration form.
d. Click the Add Alternate Filter icon. Enter values for the second filter with the information in
the following table:
e. Save the modified WebServer4 service configuration. Click the Save icon in the Service
Editor portlet.
14. Test the modified WebServer4 configuration. Select the Start > TBSM Exercises > Unit03 >
Exercise01 > 19216811Down desktop menu.
15. Verify that the WebServer4 status color changes to red in the Service Navigation or Service
Viewer portlet.
16. Look at the events in the Active Event List window. Verify that the monitor event has a Node
value of 192.168.1.1 and an AlertKey value of 80.
17. Change the WebServer4 status to Good. Select the Start > TBSM Exercises > Unit03 >
Exercise01 > 19216811Up desktop menu.
62 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Modeling multiple WebServer instances on the same Node
Uempty
Set the Display Name to differentiate this instance from the first WebServer1 instance
Configure the Identification Field to match with an AlertKey value equal to 8080 and a Node
value equal to WebServer1
Send test events to verify that the service instance responds as designed
b. Enter values for the Service Name and Display Name fields from the following table:
2. Assign the WebServer template to the WebServer18080 definition. The service instance
behavior is based on the assigned template.
a. Click WebServer in the Available Templates column.
64 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Modeling multiple WebServer instances on the same Node
Uempty 3. Configure the Identification Fields to match for an AlertKey event field value of 8080.
a. Click the Identification Fields tab.
c. Save the service definition. Click the Save icon in the Service Editor portlet.
4. Add WebServer18080 as a dependent service of WebFarm1.
a. Click WebFarm1 in the Service Navigation portlet.
d. Click Search.
e. Select WebServer18080 in the Available Services column. Click >> to move it to the
Selected Services column.
f. Save the modified WebFarm1 service configuration. Click the Save icon in the Service
Editor portlet. The WebServer18080 service instance is shown in the Service Navigation
portlet as a dependent service of the WebFarm1 service.
5. Test the WebServer18080 service instance. Select the Start > TBSM Exercises > Unit03 >
Exercise02 > WebServer18080Down desktop menu.
66 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Modeling multiple WebServer instances on the same Node
Uempty 6. Verify that the WebServer18080 status color changed to red in the Service Navigation portlet.
7. Examine the ObjectServer events. Look at the events in the Active Event List window. The
event contains a Node field value of WebServer1 and an AlertKey value of 8080.
8. Change the WebServer18080 service instance status to Good. Select the Start > TBSM
Exercises > Unit03 > Exercise02 > WebServer18080Up desktop menu.
9. Verify that the status color for WebServer18080 changed to green in the Service Navigation
portlet.
c. The two WebApplication dependency rules are listed in the Rules section of the template
configuration form. Click WebApplicationStatusDBClusterRule.
d. Select Any child in the Condition Type section of the rule. The rule forces the
WebApplication service instance to the status of the worst child state. For example, assume
68 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating output expressions and testing with sample events
Uempty a WebApplication instance contains five dependent services. If any one dependent service
is in a Bad state, the parent WebApplication service is set to a Bad state.
d. Save the updated WebApplication template. Click the Save icon in the Service Editor
portlet.
3. Test the WebApplication template rule operation. Select the following desktop menus:
Start > TBSM Exercises > Unit03 > Exercise03 > Database1Marginal
70 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating output expressions and testing with sample events
Uempty b. Click the View Service InetBanking tab in the Service Editor portlet.
The InetBanking icon is set to a Marginal state. The WebApplication template rules, by
default, set the InetBanking state to the worst state of WebFarm1 and DBCluster1.
5. Change the WebApplication template behavior so that the InetBanking state changes to Bad
when WebFarm1 and DBCluster1 are both Marginal or Bad. To combine the effects of the
WebFarm and DBCluster status changes, define an output expression for the WebApplication
template. Click the WebApplication template in the Service Navigation portlet.
6. Use the output expression builder to set the status to Bad if the DBCluster and the WebFarm
services are Marginal or DBCluster and WebFarm are Bad. The final Bad Output Expression
must look like the following statement:
((WebApplicationStatusWebFarmRule.Value = Marginal) AND
(WebApplicationStatusDBRule.Value = Marginal)) OR
((WebApplicationStatusWebFarmRule.Value = Bad) AND
(WebApplicationStatusDBRule.Value = Bad))
a. Click the Output Expressions tab in the Service Editor portlet.
b. The output expression builder reduces typographical errors in the expressions. You click the
value that you want in the expression from one of the menus above the entry field. Then
click the icon to the right of the menu. This selection places the text into the expression.
Select WebApplicationStatusDBClusterRule in the rule menu.
c. Insert the first rule name string in the Output Expression field. Click the down-arrow icon to
the right of WebApplicationStatusDBClusterRule.
d. Continue this process for each element of the output expression until the first half of the
expression is complete.
(WebApplicationStatusDBRule.Value = Marginal) AND
(WebApplicationStatusWebFarmRule.Value = Marginal)
7. Use your keyboard to manually add parentheses around the entire expression.
72 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating output expressions and testing with sample events
Uempty 9. Add the second Bad condition to the Bad Output Expression field. The second condition should
evaluate as TRUE when WebApplicationStatusWebFarmRule and
WebApplicationStatusDBClusterRule both evaluate as Bad.
a. Enter the second condition manually or with the expression builder tools.
12. Configure the Marginal Output Expression so that no rule combinations are allowed. Enter
False in the Marginal Output Expression field.
13. Save the WebApplication template changes. Click the Save icon in the Service Editor portlet.
b. Click the View Service InetBanking tab in the Service Editor portlet.
Hint: The InetBanking service status is unchanged. The state is unchanged because the
simulated monitor events for the DBCluster1 or WebFarm1 service instance are unchanged. Tivoli
Business Service Manager evaluates monitor events in template rules when the events are first
received by the ObjectServer or when the Severity of a received event changes.
15. Set all InetBanking service instances to a Good state. Select the following desktop menus:
Start > TBSM Exercises > Unit03 > Exercise03 > Database1Up
Start > TBSM Exercises > Unit03 > Exercise03 >WebServer1Up
16. Set the WebFarm1 and DBCluster1 service instances to Marginal status. Select the following
desktop menus:
Start > TBSM Exercises > Unit03 > Exercise03 > Database1Marginal
As the DBCluster1 service state changes to Marginal, the InetBanking service state remains
Good. As the WebFarm1 service state changes to Marginal, the InetBanking service changes to
a Bad status.
17. Do not set the InetBanking service status to Good. Do not send any WebServer1Up or
Database1Up events.
c. Select Report Unknown Severity if no Events after the following number of seconds.
74 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating output expressions and testing with sample events
e. Save the template. Click the Save icon in the Service Editor portlet.
b. View the InetBanking service in the Service Editor portlet. Click InetBanking in the Services
section of the Service Navigation portlet.
c. Click the View Service InetBanking tab in the Service Editor portlet.
The WebServer1 and InetBanking services remain in a Bad state. WebServer1:8080 and
WebServer4 are set to an Unknown state. A purple status color indicates that the service is
in an Unknown state.
Note: Only the WebServer-based instances in a Good state change to an Unknown state.
WebServer instances in a Marginal or Bad state do not change to an Unknown state. This
template behavior preserves the last worst state.
b. Click the Edit Template InetBanking tab in the Service Editor portlet.
c. Click the Output Expressions tab in the Service Editor portlet.
76 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating output expressions and testing with sample events
Uempty d. Clear the selection for Report Unknown Severity if no Events after the following
number of seconds.
e. Save the updated template definition. Click the Save icon in the Service Editor portlet.
21. Set the Database1 and WebServer1 services to a Good state. Select the following desktop
menus:
Start > TBSM Exercises > Unit03 > Exercise03 > Database1Up
Start > TBSM Exercises > Unit03 > Exercise03 > WebServer1Up
b. Click the Edit Template WebServer tab in the Service Editor portlet.
78 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 4. Creating measuring response rules
3. Modify the Instance Name section to evaluate both the AlertKey and Node fields to determine
the unique service name identifier for a web server.
a. Click the AlertKey field in the Available Instance Name Fields column.
b. Click the double arrow (>>) icon to move the AlertKey field selection to the Selected
Instance Name Fields pane.
c. Configure the rule to respond to incoming events when the AlertGroup field is set to
WebServerResponseTime. Set the AlertGroup logical operator menu to equals (=). Enter
WebServerResponseTime in the filter field.
d. Configure the numerical rule output value. The incoming event field ITMTime is used. Enter
ITMTime in the Output Expression field.
Enter the field value directly or select the field from the menu and click the < icon.
5. Configure the rule to evaluate the ITMTime field value to determine the rule status.
a. Select the Status (Optional) box.
b. Enter 15 in the Marginal input field and 20 in the Bad input field.
WebServer services are assigned a status of Marginal when the response time reported by
an incoming event exceeds 15 milliseconds. WebServer services are assigned a Bad status
when the response time exceeds 20 milliseconds.
c. Click OK to save the WebServerResponseTime rule. You see the rule summarized in the
Rule Settings column.
d. Save the template. Click the Save icon in the Service Editor portlet.
80 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 4. Creating measuring response rules
Uempty
Customizing the service tree
A tree template controls the data that is shown in a service tree portlet. By default, three columns
are shown, labeled State, Time, and Events. Customized tree templates, or scorecards, are
created with the Tree Template Editor. For this task, you create a column that is called Response
Time. You then assign the output of the WebServerResponseTimeRule to be shown for any
WebServer-based service in the Response Time column.
6. Start the Tree Template Editor. The Tree Template Editor is started in the Services section of
the Service Navigation portlet.
a. Select the Services menu in the Service Navigation portlet.
b. Click the Tree Template Editor icon in the Service Navigation portlet. The tree template
form opens in a new browser window.
7. Add a column to the default service view tree template. All tree templates are available in the
Tree Template Editor. The ServiceInstance tree template controls the default service tree portlet
service view.
a. Select ServiceInstance in the Tree Template Name menu.
b. Create the Response Time column. Click the Add new Tree Column icon in the Column
Configuration section. The new column is to the right of the Events column.
c. Assign the heading label to the new column. Enter Response Time in the heading field.
d. Change the column order so that the Response Time column is between the Time and
Events columns. Select the Response Time column and click the left arrow icon.
82 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 4. Creating measuring response rules
Uempty e. Add the WebServer template to the list of templates for which the customized tree template
applies. In the Service Template Selection section, click the WebServer template in the
Available Templates column. Click the >> icon to move it to the Selected Templates column.
The Available Attributes section of the form shows all available view values for the
WebServer template.
g. Select the check box in the Display column to the left of @WebServerResponseTimeRule.
h. Click the Column Display Name field in the @WebServerResponseTimeRule row. Select
Response Time in the menu.
i. Save the updated tree template. Click OK at the bottom of the Tree Template form.
8. Refresh the Service Navigation portlet to show the Response Time column. Select Services in
the menu.
9. Test the updated tree template. Send WebServer response time events to the ObjectServer.
Select the following desktop menus:
Start > TBSM Exercises > Unit03 > Exercise04 > WebServer1Response-12
Start > TBSM Exercises > Unit03 > Exercise04 > WebServer2Response-16
Start > TBSM Exercises > Unit03 > Exercise04 > WebServer3Response-20
Start > TBSM Exercises > Unit03 > Exercise04 > WebServer4Response-24
Start > TBSM Exercises > Unit03 > Exercise04 > WebServer5Response-28
84 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 4. Creating measuring response rules
Uempty The number at the end of each menu name represents the monitor response time value, in
milliseconds, of the ITMTime field.
12. Expand the InetBanking and AlliedSteel service models to show all WebServer instances. The
Services section of the Service Navigation portlet looks similar to this screen image.
Note: The simulated response time events are sent with a Severity value of 1, or
Indeterminate. The Events column icon changes to a purple diamond to reflect the Indeterminate
event. If the events are sent with a Severity of 0, they are removed from the ObjectServer after a
5-minute period. This action is part of the normal ObjectServer internal maintenance. The event
scripts are configured specifically for the laboratory environment.
86 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating average response rules for a web farm
Uempty
d. This rule aggregates a numerical value from the WebServer child template. Select
WebServer in the Child Template menu.
e. There are several rules that are defined in the WebServer template. For this exercise, the
response time value that is calculated for each child WebServer is used. Select
WebServerResponseTimeRule as the Child Metric.
h. No metric collection data is generated with this rule. Do not select any option in the Metric
Collection (Optional) section.
j. Save the template. Click the Save icon in the Service Editor portlet. The rule is shown in the
rule summary section of the Service Editor portlet.
88 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating average response rules for a web farm
Uempty 2. The metric produced by this rule is not displayed in the Response Time column, by default. Add
the metric calculated by the WebServerResponseTime rule to the Services view in the Service
Navigation portlet. Use the Tree Template Editor to modify the service view.
a. Select the Services view in the Service Navigation portlet.
b. Click the Tree Template Editor icon in the Service Navigation portlet. The tree template
form opens in a new browser window.
c. Verify that ServiceInstance is the template name that is selected in the Tree Template
Name menu.
d. Add WebFarm to the list of selected templates. In the Service Template Selection section,
select WebFarm in the Available Templates column. Click >> to move WebFarm to the
Selected Templates column.
e. Map the WebFarm rule to the service view. The Active Template list is in the Service
Template Rule Mapping section of the form. Select WebFarm in the Active Template list.
f. Select the check box in the Display column for the @AverageResponseTimeMetricRule
row.
g. Assign the rule metric to the Response Time column. Click the Column Display Name field
in the @AverageResponseTimeMetricRule row. Select Response Time in the menu.
3. Refresh the service view in the Service Navigation portlet. Select Services in the Service
Navigation portlet.
4. Expand the InetBanking and AlliedSteel service trees to show the updated average
Response Time value for WebFarm1 and WebFarm2.
90 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 6. Using weighted averages in aggregation rules
Uempty
For this exercise, WebFarm1 is the primary WebFarm used to support a critical business service.
WebFarm2 is used for staging new updates and provides overflow capacity when WebFarm1 is
heavily loaded. The primary processing responsibility means that poor user response times on
WebFarm1 have a larger impact on overall business service health. To account for the processing
impact in the average response time calculation, you create a weighting factor. The weighting factor
is assigned to each WebFarm, according to the supported processing load. You then show the
weighted average in the Response Time column of the service tree.
2. Create a weight parameter for the WebFarm template. The parameter is set in the Additional
tab in the Service Editor portlet. Click the Additional tab in the Service Editor portlet.
b. Enter WebFarmWeight in the Parameter column. Enter the number 1 in the Default Value
column.
c. Save the updated template definition. Click the Save icon in the Service Editor portlet. All
WebFarm service instances immediately inherit the default WebFarmWeight parameter,
with a value of 1.
92 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 6. Using weighted averages in aggregation rules
Uempty 4. Change the default WebFarmWeight value for WebFarm1. Edit the WebFarm1 service
instance.
a. Click WebFarm1 in the Services section of the Service Navigation portlet.
d. Save the updated WebFarm1 service instance definition. Click the Save icon in the Service
Editor portlet.
d. Select an icon to associate with the template and services. Click Browse.
e. Click an icon. The selection window automatically closes.
94 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 6. Using weighted averages in aggregation rules
b. Use the following table to complete the rule. Leave all parameters not included in the table
at the default value.
96 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 6. Using weighted averages in aggregation rules
c. In the Service Editor portlet, enter AllWebFarmServices in the Service Name field.
d. Assign the template to the service in the Templates tab. Move AllWebFarms from the
Available Templates column to the Selected Templates column.
e. Assign the dependent services in the Dependents tab. Enter WebFarm in the Search the
Available Services field. Click Search.
f. Move WebFarm1 and WebFarm2 from the Available Services column to the Selected
Services column.
g. Save the service definition. Click the Save icon in the Service Editor portlet.
b. Verify the ServiceInstance tree template is selected in the Tree Template Name field.
c. Add AllWebFarms to the list of Selected Templates in the Service Template Selection
section.
98 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 6. Using weighted averages in aggregation rules
Uempty d. Map the rule output to a column in the service view. Select AllWebFarms in the Active
Template field of the Service Template Rule Mapping section.
e. Select the check box in the Display column for the @AllWebFarmsWeightedAverageRule
row.
f. Assign the rule metric to the Response Time column. Click the Column Display Name field
in the @AllWebFarmsWeightedAverageRule row. Select Response Time in the menu.
10. Examine the services in the Service Navigation portlet. Compare the Response Time column
values for WebFarm1, WebFarm2, and AllWebFarmServices. The value that is shown for
AllWebFarmServices is 18.833. A standard average for the WebFarm1 and WebFarm2
response time values is 19.667. The extra weighting factor for WebFarm1 shifts the calculated
value closer to the WebFarm1 response time.
100 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
4 Service level agreements exercises
In these exercises, you configure and test the three types of Service Level Agreement (SLA) that
are available with Tivoli Business Service Manager. You also configure and test maintenance
windows, which provide a mechanism for temporarily removing SLA tracking on a service.
You can configure and enable one or more SLAs in a template. All templates must contain at least
one defined SLA, even if the SLA is not enabled. The default SLA for a template is called Standard.
When enabled, all service instances that are tagged with the template inherit the SLA configuration.
You can create multiple SLA configurations in a template and apply the SLAs on a per-service
basis.
Tivoli Business Service Manager tracks three types of Service Level Agreements:
Duration: A service instance is tracked for a continuous length of time in a Bad state. The
threshold is calculated as an absolute time period. When the threshold is exceeded, the SLA
state is set to Bad. The SLA state is tracked separately from the overall service state. For
example, for a threshold of 3 minutes, the SLA tracks the time period from the transition to a
Bad state. After the instance state is Bad for 3 minutes, the SLA state is set to Bad.
Incident count: This type of SLA tracks a threshold value of incidents for a service instance.
The incident threshold count is tracked within a configured, moving time window. An incident is
calculated one of two ways:
Each time the service instance changes to a Bad state (regardless of the duration).
Incident count
(30-minute Tracked time
Clock time Service state window) window SLA violation
0900 Good 0 0830-0900 No
0901 Bad 1 0831-0901 No
0902 Good 1 0832-0902 No
0932 Good 0 0902-0932 No
0936 Bad 1 0906-0936 No
Incident count
(30-minute Tracked time
Clock time Service state window) window SLA violation
0937 Good 1 0907-0937 No
1005 Bad 2 0935-1005 Yes
1007 Good 1 0937-1007 No
Cumulative duration: Each time a service instance state changes to Bad, the state is tracked
until a transition to a Marginal or Good state. The violation threshold is calculated as the total
accumulated time a service is in a Bad state, within a configured window of time.
For any SLA, a warning threshold is defined and tracked. The warning threshold exception changes
the SLA state to Warning. SLA warnings provide an opportunity to fix a problem before an SLA
violation occurs.
In the first exercise for this unit, you configure duration, incident, and cumulative-duration SLAs for
the WebApplication template. You then assign the SLA configuration to the InetBanking service
instance.
In the second exercise, you send outage events and observe the behavior of each of the defined
SLAs.
In the third exercise, you create and apply maintenance windows to the InetBanking service and
observe the effect on the SLA calculations.
When a WebApplication is in a Bad state for more than 30 seconds, set the SLA status to a
Warning.
All SLA configurations in this exercise apply to the WebApplication template. All templates have a
set of default SLA conditions defined. The default conditions are stored with the name Standard
102 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements exercises
Exercise 1. Creating service level agreements
Uempty and are not enabled. In this exercise, you create a second set of SLA conditions, which are saved
with the name Gold.
1. Edit the WebApplication template. Click WebApplication in the Templates section of the
Service Navigation portlet.
Note: The new service level definition labels change to Gold when the template is saved, or
when the form is dynamically updated. Before saving the template or updating the form data, the
new service level entries are labeled with NewServiceLevel.
4. Continue to the next task in the exercise. You save the template when all SLA types are
configured.
Set the SLA state to Warning when one Bad service status event is received within any
30-minute window.
104 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements exercises
Exercise 1. Creating service level agreements
b. Configure the SLA to track any change to a Bad service state for WebApplication services.
Select All bad-status incidents in the Include in Calculation list.
d. Configure the violation and warning thresholds for counting Bad service state transitions.
Enter 2 in the Violation Number field. Enter 1 in the Warning Number field.
Set the SLA state to Warning when the service state is Bad for more than one minute in a one
hour window.
6. Configure and enable the Gold cumulative duration SLA criteria for the WebApplication
template.
a. Select Calculate cumulative duration SLA violations.
b. Set the time window for one hour. Select Hour in the Track Service Status Each section of
the form.
Note: Selecting a change in the cumulative duration SLA time window forces the SLA form to
refresh. All of the SLA entries change to show the Gold label.
d. Configure the violation and warning thresholds. Enter 2 in the Violation Time field. Enter 1
in the Warning Time field.
7. Save the updated WebApplication template. Click the Save icon in the Service Editor portlet.
8. By default, both InetBanking and AlliedSteel are assigned the Standard SLA criteria. Assign
InetBanking the Gold SLA criteria.
a. Select the Services menu in the Service Navigation portlet.
b. Edit the InetBanking service properties. Click InetBanking in the Service Navigation portlet.
c. Change the assigned SLA set. Select Gold in the Service Level menu.
d. Save the updated service configuration. Click the Save icon in the Service Editor portlet.
106 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements exercises
Exercise 2. Testing and analyzing SLA operation
Uempty
2. Click the Edit Service InetBanking tab in the Service Editor portlet.
Note: For the purposes of this exercise, a penalty of 3600 is used to simplify the penalty
evaluation. The SLA violations are tracked as a value of seconds. The HourlySLAPenalty value is
calculated as a percentage of one hour, or 3600 seconds. The value 3600, in this exercise,
corresponds to $1 per second.
c. Save the updated InetBanking service configuration. Click the Save icon in the Service
Editor portlet.
4. Show all levels of the InetBanking service model. Click the View Service InetBanking tab in
the Service Editor portlet.
5. Send test events to change the InetBanking service state. Send Database1Down,
WebServer1Down, WebServer18080Down, and WebServer4Down events. Select the following
event menu scripts:
Start > TBSM Exercises > Unit04 > Exercise 02 > Database1Down
Start > TBSM Exercises > Unit04 > Exercise 02 > WebServer1Down
108 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements exercises
Exercise 2. Testing and analyzing SLA operation
Uempty Start > TBSM Exercises > Unit04 > Exercise 02 > WebServer18080Down
Start > TBSM Exercises > Unit04 > Exercise 02 > WebServer4Down
The following list summarizes the sequence of changes to the InetBanking service model:
6. Verify that the following changes occur in the InetBanking service model:
The icon color for the InetBanking service is set to red, indicating a change to a Bad status.
After 30 seconds, the duration SLA state changes to Warning, and the cumulative
duration SLA state remains Good. The service viewer in the Service Editor portlet is
configured to refresh the data every 30 seconds. Click the Refresh icon to force a portlet
data update before the default time period.
After one minute, the duration SLA state changes to Violation, and the cumulative duration
SLA state changes to Warning.
7. Review the SLA events that are generated for the InetBanking service.
a. Click the Active Event List (AEL) tab in the console browser window.
Hint: If the AEL is not open, open it by clicking Availability > Events > Active Events List
(AEL) in the All tasks view.
b. A custom event view is created as part of the virtual image configuration. Select
TBSMAdminTraining in the AEL View menu.
110 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements exercises
Exercise 2. Testing and analyzing SLA operation
Uempty b. Scroll through the data in the Fields tab. The RAD_WebtopTool1 field corresponds to the
calculated penalty cost of the cumulative duration violation.
The penalty cost is calculated for services in violation of an SLA, with the following field
values:
9. Switch back to the Service Configuration page. Click the Service Configuration tab in the
console.
d. Send a clearing test event for Database1. Start the following event menu script:
Start > TBSM Exercises > Unit04 > Exercise 02 > Database1Up
11. Verify that the InetBanking service status changes to green, indicating a status of Good.
Hint: The cumulative duration SLA status is still set to Violation, and the incident-count SLA
status is still set to Warning. The cumulative and incident-count SLA states are measured against
a rolling time window. For example, the cumulative duration is configured as: any accumulated
Bad service state over 5 minutes within a one hour time window. Assume that the duration SLA
violation occurred from 0900 - 0906. At 0906, the service state changed to Good. The cumulative
duration SLA violation time window is in effect until 1006.
12. The incident SLA is configured as: change to a Warning SLA state when one incident is
detected within a one hour time window. You generated the first incident in the previous task.
Create a second InetBanking Bad service status incident. Change InetBanking to a Bad status.
a. Send a Database1Downevent. Start the following event menu script:
Start > TBSM Exercises > Unit04 > Exercise 02 > Database1Down
112 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements exercises
Exercise 2. Testing and analyzing SLA operation
Uempty 13. Verify that the incident count is set to two and the SLA incident-count state changes to red,
indicating a change to a Violation state.
14. Change the status of all InetBanking services to a Good state. Send clearing events for
Database1, WebServer1, WebServer18080, and WebServer4.
a. Start the following event menu scripts:
Start > TBSM Exercises > Unit04 > Exercise 02> Database1Up
Start > TBSM Exercises > Unit04 > Exercise 02 > WebServer1Up
Start > TBSM Exercises > Unit04 > Exercise 02 > WebServer18080Up
Start > TBSM Exercises > Unit04 > Exercise 02 > WebServer4Up
15. Clear the SLA state timers for the WebApplication template.
a. Edit the WebApplication template definition. Click WebApplication in the Templates
section of the Service Navigation portlet.
b. Click the SLA tab in the Service Editor portlet. Scroll to the bottom of the SLA configuration
form. Click Clear, to the right of Clear SLA Engine State.
c. Save the template configuration. Click the Save icon in the Service Editor portlet.
c. Click the View Service InetBanking tab. All of the SLA indicators are reset to a Good SLA
state.
114 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements exercises
Exercise 3. Creating maintenance schedules in service definitions
Uempty
b. Click the Edit Service DBCluster tab in the Service Editor portlet.
2. Create a maintenance schedule. All maintenance schedules are available to all service
instances.
a. Click New in the Maintenance Schedule row in the Service Properties section of the
Service Editor portlet.
c. A maintenance schedule must have a defined time window. Time windows can be recurring
or absolute. Click the Create New Absolute Time Window icon. The icon is to the right of
the Select Absolute menu.
d. By default, the time window form is configured for one hour from the current time. Create a
one hour time window. Click OK.
116 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements exercises
Exercise 3. Creating maintenance schedules in service definitions
b. Save the modified service instance. Click the Save icon in the Service Editor portlet.
4. Show the InetBanking service model in the service viewer section in the Service Editor portlet.
a. Click InetBanking in the Service Navigation portlet.
b. Click the View Service InetBanking tab in the Service Editor portlet. The DBCluster1
icon is blue, with a traffic-cone icon next to the status indicator icon.
Start > TBSM Exercises > Unit 04 > Exercise03 > WebServer1Down
Start > TBSM Exercises > Unit 04 > Exercise03 > WebServer18080Down
Start > TBSM Exercises > Unit 04 > Exercise03 > WebServer4Down
Without the maintenance schedule in effect, the received events force the status of
DBCluster1 to a Bad state. The InetBanking rules are configured to change the service to a
Bad state when both children services are in a Bad state. With the maintenance schedule in
effect for DBCluster1, the InetBanking status change is suppressed.
Start > TBSM Exercises > Unit 04 > Exercise03 > WebServer1Up
Start > TBSM Exercises > Unit 04 > Exercise03 > WebServer18080Up
Start > TBSM Exercises > Unit 04 > Exercise03 > WebServer4Up
118 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements exercises
Exercise 3. Creating maintenance schedules in service definitions
b. Select the This service and all descendents option in the Scope section.
120 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
4 Service level agreements exercises
Exercise 4. Creating maintenance windows from the Service Viewer
Uempty The status for all InetBanking service instances change to Maintenance.
Start > TBSM Exercises > Unit 04 > Exercise04 > WebServer1Down
Start > TBSM Exercises > Unit 04 > Exercise04 > WebServer18080Down
Start > TBSM Exercises > Unit 04 > Exercise04 > WebServer4Down
3. Verify that the SLA and service status does not change for any of the services.
a. Examine the maintenance events that are generated for the service instances. Click the
Active Event List (AEL) tab in the browser window.
b. Click the blue summary filter at the bottom of the AEL portlet.
The events that are related to each InetBanking service instance show that the service state
is set to Maintenance.
Start > TBSM Exercises > Unit 04 > Exercise04 > WebServer1Up
Start > TBSM Exercises > Unit 04 > Exercise04 > WebServer18080Up
Start > TBSM Exercises > Unit 04 > Exercise04 > WebServer4Up
5. Remove the maintenance schedule from all services in the InetBanking service model.
a. Right-click InetBanking in the Service Editor portlet.
b. Select the following menu option:
Maintenance window tools > Remove from maintenance
122 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
5 Data fetchers exercises
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.
Create a data fetcher. A data fetcher establishes a structured data query of a connected
database. The database contains simulated data from a trouble ticket database.
Create an incoming status rule for the WebServer template to analyze the fetched data. The
rule determines the number of open trouble tickets for each WebServer service. Use the
fetched data to track WebServer status, and, as a service key performance indicator (KPI).
Modify the tree template to show the fetched data as a KPI in the service tree in the Service
Navigation portlet.
c. Assign the data source target type. Select DB2 from the SQL Type menu.
d. Assign a name to the data source. Enter troubleTicketsDataSource in the Data Source
Name field.
e. Enter the name of an authorized user of the target database. Enter db2inst1 in the
Username field.
f. Enter the password for the authorized database user. Enter object00 in the Password field.
g. Enter the host name of the target database server. Enter tbsm01.tivoli.edu in the Host
Name field.
h. Enter the listening port of the target database server. Enter 50000 in the Port field.
i. Enter the name of the target database. Enter TBSM in the Database field.
124 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers exercises
Exercise 1. Showing business data on the service navigation tree
Uempty
Field Name Value
SQL Type DB2
Data Source Name troubleticketsDataSource
Username db2inst1
Password object00
Host Name tbsm01.tivoli.edu
Port 50000
Database TBSM
k. Save the data source definition. Click the Save icon in the Service Editor portlet.
3. Validate access to the data source. Click OK when you see the following message.
c. Assign a name to the data fetcher. Enter troubleticketsDataFetcher in the Data Fetcher
Name field.
d. Select the data fetcher type. Select SQL from the Type menu.
126 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers exercises
Exercise 1. Showing business data on the service navigation tree
5. Create the data fetcher SQL query string with the Query Builder wizard.
a. Click Query Builder.
c. Select the query table. Select TICKETS in the Available Tables column. Click the single >
icon and move TICKETS to the Selected Tables column.
d. Click Next.
e. Select the table fields used in the query. Select LOWLEVELSERVICEID and STATUS in the
Available Fields column. Click the single > icon to move LOWLEVELSERVICEID and
STATUS to the Selected Fields column.
f. Click Next.
g. Filter for the field data to match only those records where the STATUS field is Open. Select
STATUS in the Field menu.
i. Verify the WHERE clause. Click Apply. Only records with a status of Open are shown.
j. Click Next.
k. Create a metric value for the filtered data. The column consists of a sum, or count, of
STATUS = Open records for each LOWLEVELSERVICEID record. Select COUNT in the
Function menu. Leave the default selection to include all records (*) in the count.
128 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers exercises
Exercise 1. Showing business data on the service navigation tree
Uempty m. Verify the open ticket count. Click Apply. You see each LOWLEVELSERVICEID record with
an associated NUMOPENTICKETS value.
Hint: Not all LOWLEVELSERVICEID records that are returned in the query data set are
WebServer instances. These data records are discarded when they are evaluated with the
incoming status rule filter. The incoming status rule filter is defined in a subsequent step of this
exercise.
n. Click Next.
o. Group the query data set by LOWLEVELSERVICEID and STATUS. Click the >> icon to
move LOWLEVELSERVICEID and STATUS to the Group By column.
p. Click Next.
q. Do not change the default order the data set. Click Next.
r. Verify that the Preview Query matches the following query string:
select LOWLEVELSERVICEID, STATUS,COUNT(*) as NUMOPENTICKETS from
TBSMDEMO.TICKETS where STATUS = Open group by LOWLEVELSERVICEID,
STATUS
t. Save the data fetcher definition. Click the Save icon in the Service Editor portlet.
130 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers exercises
Exercise 1. Showing business data on the service navigation tree
Uempty 6. Verify the data that is returned with the SQL query. Click View in the Service Editor portlet.
8. The troubleticketsDataFetcher is shown in the list of available data fetchers. The green status
icon indicates that the data fetcher is working properly.
9. Edit the WebServer template. Click WebServer in the Templates section of the Service
Navigation portlet.
b. Configure the incoming status rule to calculate a numerical value. Select Based on
Numeric Value.
c. Click OK.
d. Assign a name to the incoming status rule. Enter OpenTicketsRule in the Rule Name field.
e. Assign the data set evaluated by the incoming status rule. Select
troubleticketsDataFetcher in the Data Feed menu.
Note: When you change the Data Feed value, the form is updated to use the data that is defined
in selected data feed. For example, the Available Instance Name Fields list in the Instance Name
section of the form changes to show LOWLEVELSERVICEID, NUMOPENTICKETS, and
STATUS.
132 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers exercises
Exercise 1. Showing business data on the service navigation tree
g. Match service instance names to the value of the LOWLEVELSERVICEID field. Select
LOWLEVELSERVICEID in the Available Instance Name Fields column. Click >> to move
LOWLEVELSERVICEID to the Selected Instance Name Fields column.
Hint: The Event Discriminators section contains no form fields. The Event Discriminators
section is only available when the data feed is set to ObjectServer.
11. Configure how the data set is filtered. Configure the filter to match for all records where the
NUMOPENTICKETS value is greater than or equal to 1.
a. Select NUMOPENTICKETS in the Available Filter Fields column in the Filter section.
12. Configure the numerical value and status that is calculated with this rule.
a. Enter NUMOPENTICKETS in the rule output field.
b. Enable the rule to evaluate the service status. Configure the rule to evaluate a Marginal
status for three open tickets. Evaluate a Bad status for nine open tickets. Select the Status
(Optional) check box. Enter 3 in the Marginal field. Enter 9 in the Bad field.
f. Save the updated template definition. Click the Save icon in the Service Editor portlet.
134 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers exercises
Exercise 1. Showing business data on the service navigation tree
Uempty 13. Update the tree template to show the number of open tickets that are assigned to each
WebServer instance. Start the Tree Template Editor.
a. Click the Tree Template Editor icon in the Services section of the Service Navigation
portlet.
b. Select the ServiceInstance tree template in the Tree Template Name menu.
c. Create a column that is called Open Tickets on the Service Navigation tree to display the
number of open tickets. Click the Add New Tree Column icon.
e. Shift the Open Tickets column position so that it is to the right of the Time column and to the
left of the Response Time column. Move the Open Tickets column by clicking the left arrow
icon.
f. Map the Open Tickets column to the output value of OpenTicketsRule. Select WebServer in
the Active Template list.
g. Select the check box in the Display column in the OpenTicketsRule row.
h. Click the Column Display Name column in the OpenTicketsRule row. Select Open Tickets
in the menu.
i. Save the updated tree template. Click OK at the bottom of the form.
j. Refresh the Services view in the Service Navigation portlet to show the Open Tickets
column. Select Services in the Service Navigation portlet menu.
k. Expand the InetBanking and AlliedSteel service models to show the WebServer
instances. The Service Navigation portlet view looks similar to the following screen image.
136 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers exercises
Exercise 2. Using the Sum function in a numerical aggregation rule
Uempty
Create a numerical aggregation rule in the AllWebServers template. This rule establishes a
dependency relationship with the WebServer template. The rule also calculates the sum of all
open WebServer tickets.
Modify the tree template to show the sum of all open tickets as a KPI in the Service Navigation
portlet.
b. Click the Create new template icon in the Service Navigation portlet.
c. Assign a name to the template. Enter AllWebServers in the Template Name field.
b. Assign a name for the rule. Enter AllWebServersOpenTicketsSumRule in the Rule Name
field.
d. Assign the child template relationship in this parent template. Select WebServer in the
Child Template menu.
e. Assign the child rule value that is used in this parent rule calculation. Select
OpenTicketsRule in the Child Metric Rule menu.
f. Configure the rule to calculate the sum of all open tickets. Select Sum in the Aggregation
Function section.
138 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers exercises
Exercise 2. Using the Sum function in a numerical aggregation rule
i. Save the AllWebServers template configuration. Click the Save icon in the Service Editor
portlet.
b. Click the Create New Service icon in the Service Navigation portlet.
g. Assign the AllWebServers template to the service. Click the Templates tab.
h. Select AllWebServers in the Available Templates column. Click >> to move the template to
the Selected Templates column.
j. Search for all WebServer instances. Select WebServer in the Show Services For
Template menu. Click Search.
140 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers exercises
Exercise 2. Using the Sum function in a numerical aggregation rule
Uempty k. Select all WebServer services that are listed in the Available Services column. Click >> to
move them to the Selected Services column.
l. Save the service definition. Click the Save icon in the Service Navigation portlet.
c. Add AllWebServers to the list of available templates. Select AllWebServers in the Available
Templates column in the Service Template Selection section. Click >> to move the
template to the Selected Templates column.
d. Click AllWebServers in the Active Template list in the Service Template Rule Mapping
section.
g. Save the updated tree template. Click OK at the bottom of the editor form.
5. Refresh the Service Navigation portlet service tree. Select Services in the Service Navigation
portlet menu.
142 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
5 Data fetchers exercises
Exercise 2. Using the Sum function in a numerical aggregation rule
Uempty 6. Expand the AllWebServersOpenTickets service in the Service Navigation portlet. The sum of
all WebServer open tickets is shown in the Open Tickets column.
The data that is used to create child or parent services comes from any available data source.
However, each set of Child rules and Parent rules requires a single fixed reference point within the
ESDA rule. The reference point is called the seed service. The term is generally used to indicate
the template, within a template hierarchy, which is used as the single point of reference. The term
also indicates the service instance that is associated with a seed service template. The seed
template can be defined at any level of the template hierarchy, depending on the data available to
the ESDA rule. Generally, the rule operation is more efficient if the seed service is associated with
the highest level template of the template hierarchy.
A generally efficient method is to create the ESDA to build the services from the top of the service
model down to the lowest service instances. For the exercises in this unit, a template hierarchy is
already configured as part of the laboratory setup. The four-level template model represents a
simplified view of monitored telecommunication equipment. The template configuration is
summarized in the following table:
Uempty
Template name Level Description
Customer 1 The seed service is
created at this level.
This template
represents a
customer with
monitored
equipment. There is
one customer per
service model.
Contract 2 This template
represents a
customer contract
that is dependent
on the status of
communication port
services on a router.
There are multiple
contracts per
customer.
Connection 3 This template
represents the
status of the
monitored
connection
between connected
ports on two
communications
routers.
Port 4 This template
represents the
status of a router
port at the end of a
connection
between two
routers. There are
two tracked ports
per connection.
Note: In the exercises for this unit, you create only Child rules in the ESDA rule. You create a
Parent rule in the exercise Creating business services from discovered resources on page 178.
The Parent rule builds the service model in response to a child service monitor event. When
developing ESDA rules, the general practice is to define all Child rules; then define the Parent
rules.
The form in the center changes based on the context of the selected Parent rule or Child rule. The
tabs in both columns are related to the template in which the ESDA rule is defined.
Define the Customer Child rule in the ESDA rule. The Customer Child rule defines how Contract
child services are created, based on the parent Customer service.
Note: The laboratory DB2 environment is configured with simulated customer data. The data
source used to connect to the sample database is already configured.
146 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Building children services from a seed
Uempty
Creating the ESDA rule in the Customer template
For this task, you create the ESDA rule in the Customer template. ESDA rules require a seed
service. The seed service is the anchor, or context, for creating all other services in the service
model. For the exercises in this unit, the seed service is the service that is tagged with the
Customer template at the top of the service model hierarchy. The rule queries the defined data
source and determines how to create all Customer child services.
1. Modify the Customer template. Click Customer in the Templates section of the Service
Navigation portlet.
2. Create an ESDA rule in the Customer template. Click the Create ESDA Rule icon in the
Service Editor portlet.
3. Assign a name to the ESDA rule. Enter customESDARule in the Rule Name field.
Important: Do not click the Delete icon in the Child rule tab. Clicking the Delete icon deletes
the child rule from the ESDA rule form.
5. Assign the data source for the child rule. Select TBSMDEMO in the Data Source menu.
6. Enter the following SQL query for the Customer Child rule in the ESDA form:
select CONTRACT,CUSTOMER from TBSMDEMO.TRAINESDA_CUSTOMER where CUSTOMER =
__serviceinstancename__
Important: You must use 2 underscore characters before and after serviceinstancename. The
2 characters are an indicator to the rule parser to expand the character string as a variable name
value. You must also enclose the __serviceinstancename__ string with single quotation marks,
not grave accent (sometimes called backtick) characters.
7. Configure the Instance Name Expression, Display Name Expression, and Description
Expression values. Use the information in the following table:
8. Configure the Child rule to be an active component of the ESDA rule. Select Enabled.
148 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Building children services from a seed
Uempty 9. The Primary Template selection assigns the designated template to each service as it is
created in the ESDA rule processing. Verify that Contract is selected in the Primary Template
menu.
10. Save the ESDA rule definition. Click OK. The rule customESDARule is shown in the Rule Name
column in the Service Editor portlet.
11. Save the updated template definition. Click the Save icon in the Service Editor portlet.
12. Create a seed service and assign it, or tag it, with the Customer template.
a. Select the Services menu in the Service Navigation portlet.
b. Click the Create New Service icon in the Service Navigation portlet.
c. Assign a customer name to the service. Enter IBM in the Service Name field.
d. Assign the Customer template to the service definition. Move Customer from the Available
Templates list to the Selected Template list.
150 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Building children services from a seed
Uempty e. Save the IBM service instance definition. Click the Save icon in the Service Editor portlet.
The seed service is shown in the Service Navigation portlet service tree.
13. Test the ESDA. Click the plus symbol (+) to expand the IBM service model in the service tree.
You see a list of child services in the form of Contract: <Contract Number>, similar to the
following screen image.
Each Contract service contains one or more Connection services. Each Connection service defines
two point-to-point communication router connections. The first router is designated in the database
with the field ANODE. The first router port is designated with the field APORT. The second router is
designated with the BNODE field. The second router port is designated with the field BPORT. The
following string shows the logical naming convention for each Connection service:
<ANODE>:<APORT>-<BNODE>:<BPORT>
The following table shows the relationship between the data that is contained in the
TBSMDEMO.TRAINESDA_CONNECTIONS table and the derived Connection name value.
1. Define how child services for a Contract parent service are created. Configure the Contract
Child rule in the customESDARule rule in the Customer template.
a. Modify the Customer template. Click Customer in the Templates section of the Service
Navigation portlet.
152 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Extending the ESDA rule scope
Uempty b. Modify the customESDARule rule. Click customESDARule in the Rule Name column in the
Service Editor portlet.
2. Define how the Connection child services are created. Connection is a child template to
Contract.
a. Click the Contract tab in the Child rules column.
c. Create the database query that is used to determine Contract and Connection relationship
data. Enter the following string in the SQL Query field:
select ANODE,APORT,BNODE,BPORT,CONTRACT from
TBSMDEMO.TRAINESDA_CONNECTIONS where CONTRACT = __serviceinstancename__
The query uses the parent Contract service name (__serviceinstancename__) to filter the
ANODE, APORT, BNODE, and BPORT query data.
d. Use the information in the following table to configure the Instance Name Expression,
Display Name Expression, and Description Expression fields:
Hint: To reduce typographical errors when entering concatenation strings, insert a space
between string elements. Blank spaces outside quotation pairs are ignored by the rule parser.
3. Test the updated ESDA rule. Select the Services menu in the Service Navigation portlet.
154 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Extending the ESDA rule scope
Uempty
Note: Services that are created by an ESDA rule are, by default, transient. If a monitor event or
console view request is not sent to the data server within a specified time period, transient
services are designated as invalid. When a service is marked as invalid and one of the two
previous conditions is in effect, the ESDA rule is triggered. The rule then dynamically creates the
child or parent services. If the service is designated as valid, the ESDA rule is not started.
4. By default, when an ESDA rule creates the child or parent service, the service is valid for 1
hour. After 1 hour, clicking the service in a service tree or service viewer forces the ESDA rule to
start and show the updated results. Use the service editor to force the invalidation of a service
before the default timeout period. Invalidate the IBM service model.
a. Click the IBM service in the Service Navigation portlet.
b. Click Invalidate in the Service Properties section in the Service Editor portlet.
5. Show the Contract services in the IBM service model. Expand the IBM service model in the
Service Navigation portlet.
6. Expand the Contract: 1 service model in the Service Navigation portlet. You see the
Connection service ny-rtr-1:01-lon-rtr-1:01.
This exercise uses the second method, using a custom policy script. You must complete the
following tasks:
Define a Connection Child rule in the customESDARule rule.
156 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Using policies in ESDA rules
Uempty
Defining the Connection Child rule
For this task, you define the basic configuration for the Connection child rule.
1. Modify the Connection Child rule in the customESDARule in the Customer template.
a. Click the Customer template in the Templates section of the Service Navigation portlet.
b. Modify the customESDARule rule. Click customESDARule in the Rule Name column in the
Service Editor portlet.
d. The Connection service name is parsed to create the Port A and Port B service names. You
do not need to query the data source. Enter __serviceinstancename__ in the SQL Query
field. Do not include quotation marks around the variable name.
e. You do not need to select anything in the Data Source menu. The data source is not queried
in this Child rule.
Important: Do not select the If checked, then no query will be made to get next level
children or parents check box.
f. The value that is used in the Expression fields is returned with the processing of the
Connection Child rule policy script. Use the information in the following table to configure
the Expression fields:
Description MyDescription
158 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Using policies in ESDA rules
Uempty i. Activate policy processing for the Connection Child rule. Select Use Policy.
The value of the ExternalFilter variable is parsed with a regular expression. The
component parts of the Connection service name are extracted.
The A Port name is stored in the policy data structure named AInstance.
The B Port name is stored in the policy data structure named BInstance.
The contents of AInstance and BInstance are assigned to the policy data structure named
NextLevelOrgNodes. NextLevelOrgNodes is a required data structure. The contents of the
data structure are used to create the services for the child or parent rule.
The contents of the NextLevelOrgNodes data structure are processed to add the Primary
Template information for each created service instance. This value is assigned with the
__TagList key word.
The values that are stored in NextLevelOrgNodes are passed to the Connection Child rule.
Note: The script commands are provided in a text file on the tbsm01 virtual image. To avoid
typographical errors, use a text editor to copy and paste the commands. The contents of the text
file is included in Appendix A on page 339.
2. Configure the policy script that is used to define the Port child services.
a. Click Edit Policy.
b. Tivoli Business Service Manager stores policy scripts in either the default Impact Policy
Language (IPL) or JavaScript format. Select IPL and click OK.
Hint: Resize the editor window by clicking and dragging the lower right corner of the window.
c. Open the pre-configured policy command file in a text editor. Select the following desktop
menu:
Start > TBSM Exercises > Unit06 > Exercise03 > Open ESDA Policy Text File
5. Minimize the editor. Click the minimize icon (_) in the upper right corner of the text editor.
160 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Using policies in ESDA rules
Uempty 6. The copied commands must be inserted on a blank line after the policy script default comments.
Switch to the Policy Editor window. Scroll to the bottom of the policy editor. Insert a blank line
after the end-of-comments characters (*/).
7. Place the cursor on the blank line. Paste the commands into the policy. Enter the key
combination Ctrl + V.
Note: The Tivoli Business Service Manager console with Linux Firefox does not support the Edit
> Copy menu.
8. Check the policy script syntax. Click the Check Syntax icon.
9. The Syntax check successful message is shown. Close the message window. Click OK.
11. Assign a name to the policy. Enter LabESDAPolicy in the Policy Name field. Click OK.
13. Save the updated Customer template. Click the Save icon in the Service Editor portlet.
15. Invalidate the IBM service instance. Click IBM in the Services service tree.
16. Click Invalidate in the Service Editor portlet.
162 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
7 Automatic service model creation
exercises
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.
Important: Tivoli Business Service Manager searches the service model database to find all
templates that are associated with the WebServer template. The first match is used to populate
the form. You update the rule form as you configure the automatic population rule for each level of
the WebApplication template model. In this laboratory environment, the AllWebServers template
model is used to initially populate the form.
3. The rule form consists of sections that correspond to each level of the template model.
Configure the automatic population rule for the WebServer level of the rule form.
a. Click the WebServer tab in the form.
b. Complete the WebServer section of the form with the information in the following table:
164 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Creating automatic population rules
Uempty
Input field Value
Rule Name: EventAutoPopulationRule
Incoming Status Rule: WebServerStatusRule
Instance Name Expression: Node + AlertKey
Display Name Expression: Node + : + AlertKey
Service Level Agreement: Standard
Restriction Filter: true
4. Force the rule form to use the WebFarm > WebServer parent-child relationship.
a. Click the AllWebServers tab.
b. Change the form data. Select WebFarm in the Template Name menu.
166 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Creating automatic population rules
Uempty 5. Click the WebServer tab. This action forces the automatic population rule form to use the
WebFarm template you selected.
6. The form updates and shows three tabs, corresponding to the AllWebFarms template model
hierarchy. The AllWebFarms template model is the first match that is found where the WebFarm
template is a parent to the WebServer template. This condition is normal. Continue the rule
configuration. Click the WebFarm tab.
7. Complete the automatic population rule form for the WebFarm template. Use the information in
the following table to complete the WebFarm section of the rule:
8. Force the rule form to use the WebApplication > WebFarm > WebServer parent-child
relationship.
a. Click the AllWebFarms tab.
b. Select WebApplication in the Template Name menu.
168 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Creating automatic population rules
11. Save the modified WebServer template. Click the Save icon in the Service Editor portlet.
Start > TBSM Exercises > Unit 07 > Exercise01 > WebServer9Down
Start > TBSM Exercises > Unit 07 > Exercise01 > WebServer10Down
Start > TBSM Exercises > Unit 07 > Exercise01 > WebServer8Up
Start > TBSM Exercises > Unit 07 > Exercise01 > WebServer9Up
Start > TBSM Exercises > Unit 07 > Exercise01 > WebServer10Up
170 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Using a data fetcher with automatic population rules
Uempty
Configure the rule to create services for all levels of the WebApplication template model. You
must filter any records that do not match WebServer resources.
b. Use the information in the following table to configure the WebServer section of the rule.
Note: The data that is returned in the OpenTicketsRule data set includes trouble ticket data for
several resource types, in addition to WebServer services. The WebServer section of the
automatic population rule must filter all retrieved records that do not correspond to WebServer
services. In the Restriction Filter field, the carat symbol (^) precedes WebServer. The beginning
of the filter string must start with WebServer. If you do not use the carat symbol, the
LOWLEVELSERVICEID values match on other strings that contain, but do not begin with,
WebServer.
172 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Using a data fetcher with automatic population rules
Uempty 4. Update the rule form to show the WebFarm template as the parent template for WebServer.
a. Click the AllWebServers tab.
b. Select WebFarm in the Template Name menu.
5. Configure the rule to create WebFarm services that are based on the data that is returned in the
OpenTicketsRule data set. Use the information in the following table to configure the WebFarm
section of the rule.
6. Update the rule form to show the WebApplication template as the parent template for
WebFarm.
a. Click the AllWebFarms tab.
174 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Using a data fetcher with automatic population rules
7. Configure the WebApplication section of the rule. Configure the rule to create WebApplication
services automatically. For this exercise, configure the rule to use the service name
BobsBooks. The service BobsBooks was created in the previous exercise in this unit.
a. Use the information in the following table to configure the WebApplication section of the
rule.
9. Save the updated template. Click the Save icon in the Service Editor portlet.
176 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Using a data fetcher with automatic population rules
12. Examine the service model changes in the Service Navigation portlet. Select Services in the
Service Navigation portlet menu.
13. Expand the BobsBooks service instance in the Service Navigation portlet.
14. Expand the WebFarm Unknown service. The created WebServer services are shown. Open
ticket sums for each of the created services are also shown in the Open Tickets column.
Import and process the IdML book with the Discovery Library Toolkit. Verify that the services are
created.
178 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating business services from discovered resources
Uempty
Generating the Discovery Library Adapter resource file
The Tivoli Enterprise Monitoring Server and the Tivoli Enterprise Portal Server must be running to
complete the DLA queries.
1. Switch to the itm01 virtual machine.
3. Start the DLA to generate Tivoli Monitoring discovery data. Enter the following command:
/opt/IBM/ITM/bin/itmcmd execute cq tmsdla.sh
The command window looks similar to the following screen image.
managed by the application. Because the laboratory environment is limited to three virtual
servers, only the itm01 virtual image information is contained in the IdML file.
Hint: The target directory for the IdML file that is created with the tmsdla.sh command varies
across Tivoli Monitoring releases. Review the product documentation and the command window
when running this DLA outside this laboratory environment.
4. Verify that the Discovery Library Toolkit is configured to process IdML data files.
a. Switch to the tbsm01 virtual machine.
180 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating business services from discovered resources
c. Click Find.
The parameter value must be set to books:
DL_ImportSource=books
Note: The menu command opens a command window in which the file,
$TBSM_HOME/XMLtoolkit/log/msgGTM_XT.log.0, is scanned for a message that indicates the
IdML file is successfully processed. The data that is shown in the window changes when the
Discovery Library Toolkit reader processes the resource data.
b. Close the command window when the toolkit is started. Click the window and press the
Enter key.
Hint: The desktop menu starts a script that starts the toolkit with the command,
$TBSM_HOME/XMLtoolkit/bin/tbsmrdr_start.sh. In a production environment, the Discovery
Library Toolkit is configured to start automatically after the data server starts.
10. Copy the generated IdML file from itm01 to tbsm01. A command script is configured to copy the
IdML book from itm01:/opt/IBM/ITM/li6263/cq/tmsdla to
tbsm01:/opt/IBM/tivoli/tbsm/discovery/dlbooks.
a. Select the following desktop menu:
Start TBSM Exercises > Unit 07 > Exercise03 > Get IdML book from itm01
b. You are prompted for the itm01 root user ID password. Enter object00.
c. When the IdML file copy is complete, click the command window and press the Enter key to
close the window.
11. Examine the command window in which you are showing the contents of the msgGTM_XT.log
file. Messages that are related to the processing of the IdML file are shown. You see a message
that indicates that the processing was successfully completed. Processing the IdML takes 10 -
20 seconds.
12. Close the command window in which the log file is scanned. Click the window and press the
Ctrl + C key combination.
13. Verify that the service instance is created with the data in the IdML book. Select Service
Component Repository from the Service Navigation portlet menu.
182 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating business services from discovered resources
Uempty
Note: The Service Component Repository contains services that were created with TADDM
resource data. The services were created during the setup of the laboratory environment.
b. The servers are listed in alphabetical order. Scroll down the list and click itm01.
15. The discovery data that is generated by tmsdla.sh and processed by the Discovery Library
Toolkit reader is based on Tivoli Monitoring agent data. For this exercise, the Linux OS agent
provided the data. Review the instance identification information for the discovered service.
Click the Identification Fields tab in the Service Editor portlet.
184 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 4. Exploring the Service Component Repository with the Component Registry Viewer
Uempty
The purpose of this exercise is to familiarize you with the operation and functions of the Component
Registry Viewer tool. You find and examine an instance of the Common Data Model (CDM) class
cdm:app.db.db2.Db2Instance. This CDM class is used to map the creation of discovered DB2
database service models. You examine the class attributes that are used in the exercise, Creating
service models that are based on geographical location on page 191.
1. Start the Component Registry Viewer tool.
a. Select the following desktop menu:
Start > TBSM Exercises > Unit07 > Exercise04 > Start Component Registry Viewer
Tool
Hint: The Component Registry Viewer and Business Service Composer tool is installed on the
tbsm01 image. The tool is installed in the default directory,
$TBSM_HOME/XMLtoolkit/tools/crviewer. The menu script starts the tool with the command,
$TBSM_HOME/XMLtoolkit/tools/crviewer/CRC-Start.sh
The Component Registry Viewer starts with a title view that has the following two links:
Start here
Close
Hint: Click Start here to start a Component Registry Viewer tutorial in a separate window.
The Component Registry Viewer provides a tool to view the Service Component Repository
database. To view the database, you must configure and establish a connection to the Service
Component Repository on the tbsm01 image. The connection is configured as part of the
laboratory environment setup.
3. Establish a connection to the Tivoli Business Service Manager database. Select
tbsm01.tivoli.edu in the Connect To menu.
You are prompted to provide a password for the Service Component Repository database
instance owner.
The Component Registry Viewer workspace comprises four sections, or views. The following
table provides a name and description of each of the sections.
186 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 4. Exploring the Service Component Repository with the Component Registry Viewer
Uempty
Section Name Description
Class List A view of all CDM classes in the SCR database. A Filter field is used to
search the database and modify the list of classes shown. Clicking an
entry in the list drives a context change in the Instance List section.
Instance List A view of all occurrences of the selected class. A filter field is used to
modify the list of instances shown. Clicking an entry in the list drives a
context change in the Attribute List section.
Attribute List A list of attributes that are associated with a selected class instance.
More information about a selected class instance is shown in the Details
section.
Details This section contains several tabbed entries that show information that is
related to the Discovery Library Toolkit operation. The information that is
shown in each tab is dependent on the data available for the selected
class instance.
Hint: The class list is filtered as you type, and the search is case independent.
188 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 4. Exploring the Service Component Repository with the Component Registry Viewer
Uempty 7. Filter the instance list to show all instances that contain the text string austin.
a. Enter austin in the Filter field in the Instance List section.
8. Show the attributes for r2lpar8.tivlab.austin.ibm.com:r2lpar4.
a. Click r2lpar8.tivlab.austin.ibm.com:r2lpar4 in the Instance List section.
Important: The text string austin is in the cdm:DisplayName attribute value, not the
cdm:Name attribute value. The value that is entered in the Filter field searches all attributes in a
class instance.
Tivoli Business Service Manager uses CDM class and attribute discovery data to create
corresponding service models. Part of the service model creation process includes assigning
corresponding service templates.
10. Verify that BSM_DB2DatabaseServer is the primary template that is assigned to the
r2lpar8.tivlab.austin.ibm.com:r2lpar4 Tivoli Business Service Manager service instance.
a. Click the Templates tab in the Details section.
190 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating service models that are based on geographical location
Uempty
Laboratory scenario
Your company, GetThereFast Travel, uses several DB2 server instances that are managed by IBM
to support your business applications. The DB2 instances span applications and physical computer
systems. You are tasked with creating a service model that organizes all DB2 instances by
geographical location. The data centers are in Austin, Texas, and San Jose, California. You must
organize the database instances by the data center location.
The Business Service Composer is a component of the Component Registry Viewer tool. You
switch to the Business Service Composer workspace by clicking the Open Business Service
Composer icon in the upper left of the Component Registry Viewer.
Hint: The Business Service Composer workspace is also started with the Tools > Business
Service Composer menu. You switch between the Business Service Composer and Component
Registry Viewer views with the Window menu.
The Business Service Composer workspace comprises two sections. The left section shows a list
of available project files. The right section is the project workspace. Multiple projects can be opened
simultaneously. Each project is shown in a tab in the workspace.
The project workspace is divided into five sections. The following table describes each section.
192 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating service models that are based on geographical location
Uempty
Section name Description
Project View This section contains a summary listing of all Static Definitions and Policy
Patterns that are defined in the project.
Static Definition One or more rules that define service models that are used as targets of
the policy. Static Definitions are also referred to as touch points. If the
Static Definitions do not correspond to existing service models, the
service models are created when the project is loaded. Static definitions
must be defined as one of the following classes:
cdm:sys.BusinessSystem
cdm:app.Application
cdm:core.Collection
194 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating service models that are based on geographical location
Uempty 3. Complete the Add new project form. The values that are entered must contain alphanumeric
characters and should include an indication of the services that are enriched.
a. Use the information in the following table to complete the form.
Hint: Static resources and service relationships that are managed by a Business Service
Composer project must be uniquely associated with a Common Data Model source. The product
name, manufacturer name, and product version are combined to build source identification
information for this project. The Common Data Model refers to the name combination as the
management software system (MSS).
You then create two Static Definitions that are dependencies of the top-level Static Definition. The
first child Static Definition is used to place all DB2 instances that are maintained in the Austin data
center. The second child Static Definition is used to place all DB2 instances that are maintained in
the San Jose data center. The child services that are created with the Static Definitions must be
assigned the BSM_AppLogicalGrouping template. The final Static Definition hierarchy is shown
in the following screen image.
b. Complete the Static Definition form. Use the information in the following table.
Hint: When the Discovery Library Toolkit processes cdm:sys.BusinessSystem classes, the
corresponding service is assigned the BSM_BusinessService template.
196 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating service models that are based on geographical location
b. Complete the Static Definition form. Use the information in the following table.
Hint: When the Discovery Library Toolkit processes cdm:core.Collection classes, the
corresponding service is assigned the BSM_AppLogicalGrouping template.
b. Complete the Static Definition form. Use the information in the following table.
198 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating service models that are based on geographical location
Uempty
Defining the Policy Pattern
For this task, you configure a Policy Pattern to search for all DB2 instances. Use the server domain
name to determine the geographical context of the instance. If the server name contains the text
string austin, place all matching DB2 instances in the Austin Static Definition. If the server name
contains the text string sanjose, place all matching DB2 instances in the San Jose Static
Definition.
You examined the class structure for DB2 instances in the exercise Exploring the Service
Component Repository with the Component Registry Viewer on page 185. Fully qualified
domain names are used in the cdm:DisplayName attribute of the
cdm:app.db.db2.Db2Instance class. The display name is sometimes referred to as the
class label.
d. Select the source CDM class that is placed in a Static Definition. Click the Class of
resource to be placed row and select cdm:app.db.db2.Db2Instance.
e. Configure how the source class list is searched. Wildcard character matching symbols are
allowed in this field. Search for all instances that contain the text string austin. Click the
Placement Label Pattern row and enter the following text:
%austin%
f. Use the Static resource column value to assign the target for matching class instances.
Place all instances that contain the string austin in the gtfDB2InstancesAustin Static
Resource. Click the Static resource row and select or enter gtfDB2InstancesAustin.
g. Create a second set of matching criteria for placing resources that contain the text string
sanjose. Click the plus symbol (+) to the left of the Class of resource to be placed
column.
Hint: If the plus symbol is not visible, increase the width of the workspace by clicking and
dragging the lower right corner of the Business Service Composer tool.
h. Define the source class. Select the cdm:app.db.db2.Db2Instance class in the Class of
resource to be placed column.
200 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating service models that are based on geographical location
Uempty i. Configure how the class list is searched. Search for all class instances that contain the text
string sanjose. Click the Placement Label Pattern row and enter the following text:
%sanjose%
j. Use the Static resource column value to assign the target for the matching instance list.
Place all instances that contain the string sanjose in the gtfDB2InstancesSanJose Static
Resource. Click the Static resource row and select or enter gtfDB2InstancesSanJose.
k. The Add icon is activated when an Input Values row is complete. Complete the Policy
Pattern configuration. Click Add.
9. Expand the Policy Patterns tree in the Project View section to verify the PlaceByLabel_1.0
entry was created.
In this task, you load the Exercise5_Project.xml project file with a command-line tool and verify
that the target service model is created and populated. To eliminate typographical errors in this
laboratory, a command script to load the project file is provided on the virtual image. Select the
following desktop menu:
Start > TBSM Exercises > Unit07 > Exercise05 > Load Exercise 5 Project File
12. Close the command window after the script completes. Click the command window and press
the Enter key.
Important: Services that are created with static definitions are created immediately after
processing the project file. With the large number of services in the Service Component
Repository in the tbsm01 image, the service definitions that are defined by the policy patterns take
several minutes to complete. The time delay is required to minimize the impact to the database
performance. Stopping and starting the data server forces the rebuilding of the Service
Component Repository with the updated services.
13. Log off the Tivoli Business Service Manager console. Click Logout in the upper right of the
console.
14. Stop and start the data server to force the Service Component Repository changes.
a. Stop the data server. Select the following desktop menu:
Start > TBSM Utilities > Stop Data Server
b. When the data server is stopped, close the command window. Click the window and press
the Enter key.
d. When the data server is started, close the command window. Click the window and press
the Enter key.
202 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating service models that are based on geographical location
204 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating service models that are based on geographical location
Uempty 16. Examine the service properties for the GetThereFast DB2 Instances service.
a. Click GetThereFast DB2 Instances in the Service Navigation portlet.
b. Verify that the BSM_BusinessService template is the primary template that is assigned to
the service.
c. Expand the Austin and San Jose service trees and verify that the geographically
appropriate DB2 instance services are listed in each container.
206 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating service models that are based on geographical location
Uempty 17. Examine the service properties for the Austin service.
a. Click Austin in the Service Navigation portlet.
b. Verify that the BSM_AppLogicalGrouping template is the primary template that is
assigned to the service.
The LDAP server is preconfigured with user and group information. The security configuration is
administered with the WebSphere Administrative Server administration console.
1. Examine the users that are defined in the tbsm01 virtual server. Click Users and Groups >
Manage Users in the All tasks view.
The name in the Unique Name column includes the user repository designation. The dashboard
server internal repository designation is o=defaultWIMFileBasedRealm.
3. Start the procedure to add a user and group repository. Open the WebSphere Application
Server administrative console.
a. Click Settings > WebSphereAdministrative Console in the All tasks view.
Note: The WebSphere Application Server administrative console opens in a tabbed window in
the browser. The tab label is Integrated Solutions Console. SSO is automatically configured on
the tbsm01 image during the Tivoli Business Service Manager installation. You are not prompted
to log on to the administrative console.
d. Repository configuration forms are in the User account repository section. Verify that
Federated repositories is selected in the Available realm definitions menu.
210 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security exercises
Exercise 1. Configuring Tivoli Business Service Manager to use LDAP users and groups
Uempty e. Click Configure, to the right of the Available realm definitions menu.
4. Do not change the Realm name value, jazzRealm. The realm name was configured for the
laboratory environment.
6. Add and configure an LDAP repository and base entry in the realm. A realm is a mapping of all
physical repositories into a single logical repository.
a. Click Add Base entry to Realm in the Repositories in the realm section.
b. To complete the realm definition, you must first create the LDAP repository definition. You
complete the General Properties section after adding the repository definition. Click Add
Repository.
c. Use the information in the following table to complete the LDAP server configuration. Do not
change any other values.
212 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security exercises
Exercise 1. Configuring Tivoli Business Service Manager to use LDAP users and groups
Uempty
You return to the General Properties configuration page for a base entry in the realm. The
LDAP1 repository label is shown in the Repository menu.
8. A Messages section is shown at the top of the console page, indicating that the configuration
changes must be saved. Click Save in the Messages section.
10. Save the federated repository base entry definition. Click OK.
214 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security exercises
Exercise 1. Configuring Tivoli Business Service Manager to use LDAP users and groups
Uempty 11. Save the configuration changes. Click Save in the Messages section.
The LDAP base entry is listed in the Repositories in the realm section.
12. Stop and start the dashboard server to update the dashboard server operations. Log off the
WebSphere administrative server.
a. Click Logout in the upper right corner of the server console.
b. Log off the dashboard server console. Click the Tivoli Integrated Portal Server tab in the
browser.
d. Stop the Tivoli Integrated Portal server. Select the following desktop menu:
Start > TBSM Utilities > Stop TBSM TIP Service
e. When the server is stopped, close the script window. Click the window and press the Enter
key.
f. Start the Tivoli Integrated Portal server. Select the following desktop menu:
Start > TBSM Utilities > Start TBSM TIP Service
g. When the server is started, close the script window. Click the window and press the Enter
key.
13. Log on to the console, with the user ID tipadmin. Use the password object00.
14. Verify that the dashboard server is successfully communicating with the LDAP server.
a. Click the Users and Groups > Manage Users task.
b. Click Search in the WIM User Management page. Users from all physical repositories in the
federated repository are shown. Entries in the Unique Name column include users defined
in the o=jazzrealm base entry. The o=jazzrealm entries indicate successful communication
with the LDAP server.
Important: For the remainder of the course exercises, the jazz01 virtual image must remain
operational and communicating with the Tivoli Integrated Portal server. The security model of the
underlying WebSphere Application Server requires that all defined repositories must be available.
If the LDAP server is down, no user can log on, even if they are defined in the internal file
repository.
216 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security exercises
Exercise 2. Configuring secure sockets layer communications
Uempty
Configure the Tivoli Integrated Portal server to use only SSL communication with the LDAP
server.
Verify that the SSL communications between the Tivoli Integrated Portal server and the LDAP
server are functional.
218 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security exercises
Exercise 2. Configuring secure sockets layer communications
Uempty c. Click Security > SSL certificate and key management in the All Tasks view of the
WebSphere Administrative Server console.
2. Modify the Tivoli Integrated Portal server keystore and certificate configuration.
a. Click Key stores and certificates, in the Related Items section.
b. Open the Tivoli Integrated Portal server default truststore. The truststore contains trusted
server signer certificates. Click NodeDefaultTrustStore.
c. Add the LDAP server signer certificate. Click Signer certificates, in the Additional
Properties section on the right side of the page.
b. Configure the information that is required to securely retrieve the signer certificate. Use the
information in the following table to configure the General Properties section of the page.
220 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security exercises
Exercise 2. Configuring secure sockets layer communications
The certificate information is shown in the Retrieved signer information section of the
page.
d. Finish the certificate retrieval process. Click OK. The entry for the ldapsslkey certificate is
shown in the NodeDefaultTrustStore list of certificates.
4. In the Messages section at the top of the configuration form, click the Save link to save the
changes to the dashboard server master configuration.
5. Complete the next task in the exercise before stopping and starting the Tivoli Integrated Portal
server.
222 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security exercises
Exercise 2. Configuring secure sockets layer communications
Uempty 6. Modify the LDAP configuration that you completed in the task, Configuring Tivoli Business
Service Manager to use LDAP users and groups on page 208.
a. Click Security > Global security in the All Tasks view in the administrative console.
9. Modify the repository configuration to communicate with the LDAP server SSL port.
a. Change the Port field value to 636.
b. Select Use specific SSL alias and use the default value of NodeDefaultSSLSettings.
13. Log off the Tivoli Integrated Portal server console. Click the Tivoli Integrated Portal tab in the
web browser. Click Logout.
14. Stop and start the Tivoli Integrated Portal server on tbsm01.
a. Stop the Tivoli Integrated Portal server. Select the following desktop menu:
Start > TBSM Utilities > Stop TBSM TIP Service
224 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security exercises
Exercise 2. Configuring secure sockets layer communications
Uempty b. When the server is stopped, close the script window. Click the window and press the Enter
key.
c. Start the Tivoli Integrated Portal server. Select the following desktop menu:
Start > TBSM Utilities > Start TBSM TIP Service
d. When the server is started, close the script window. Click the window and press the Enter
key.
15. Log on to the Tivoli Integrated Portal server console. Use the information in the following table
to complete the logon process:
User ID Password
tipadmin object00
c. The LDAP repository is configured to use only SSL. Verify users that are defined in the
LDAP server (o=jazzrealm) are shown.
Customer scenario
You, as the senior administrator for the GetThereFast Travel Corporation, are asked to configure
your Tivoli Business Service Manager infrastructure to manage the following user type:
Top-level executives who track high-level business applications: Executives require
access to service level agreement reports, top-level service model charts, and custom business
dashboards. Executives do not need access to low-level information, such as monitor events.
A summary of the user, group, and user functions, are listed in the following table:
executiveManagementGroup
Authorization
Member name description Group roles needed
whill: William Hill View all top-level chartViewer
(LOB) service ncw_user
models, custom ncw_gauges_viewer
dashboards,
netcool_ro
top-level business
tbsmLaunchISMServiceReportViewer
reports, and Service
tbsmReadOnlyUser
Level Agreement
reports. tbsmSLAChartViewVisible
tbsmViewChart
tbsmViewService
226 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
8 Security exercises
Exercise 3. Assigning authorization roles
Uempty by job-functional groups simplifies administration. The user and group is configured as part of
the laboratory setup.
Verify user access to the Tivoli Integrated Portal server: Verify that the user who belongs to
the group can log on to the Tivoli Integrated Portal server.
17. Add roles to each group, with the information described in Customer scenario on page 226.
a. Click Users and Groups > Group Roles in the All tasks list.
b. Assign the roles. Select the check box to the left of each of the following roles:
chartViewer
ncw_gauges_viewer
ncw_user
netcool_ro
tbsmLaunchISMServiceReportViewer
tbsmReadOnlyUser
tbsmSLAChartViewVisible
tbsmViewChart
tbsmViewService
c. Save the role assignments. Click Save.
Note: Adding roles does not require stopping and starting the Tivoli Integrated Portal server for
the roles to take effect.
19. Log on to the Tivoli Integrated Portal server console as the user jsmith. Log off the current
console connection.
a. Click Logout.
20. Log on as the executiveManagementGroup member, whill. Use the information in the following
table to complete the logon process:
User ID Password
whill object00
a. Verify that the user has access to a limited set of tasks in the All tasks view. Expand the
tasks in the All tasks view.
228 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
9 Custom dashboards and page
management exercises
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.
Each exercise in this laboratory completes a high-level task that is required to build the desktop
dashboard page structure that is shown in the following diagram.
Exercise 2: You create the second-level desktop dashboard page that is shown in the logical
diagram at the beginning of Creating the second-level tickets detail page on page 233. This
page uses two Analog Gauge widgets to show the total number of open high-severity and
critical-severity tickets, by region, for the GetThereFast Travel company. The page also includes
three Volume Bar widgets. One volume bar widget is configured to show open Web
server-related tickets, one volume bar widget shows open DB-related tickets, and one volume
bar widget shows open network-related tickets. Only one page is required to support three
GetThereFast regions. The contextual region information that is passed from the top-level page
drives the data that is shown in the second-level page.
Exercise 3: You create the top-level desktop dashboard page that is shown in the logical
diagram in Creating the top-level service summary page on page 268. This page uses three
Status Gauge widgets to show the open trouble ticket status for the three GetThereFast Travel
regions.
Exercise 4: You create the event wire connections between the top-level and second-level
page widgets. The wires establish the contextual connection between the dashboard pages.
Exercise 5: You create and populate a desktop dashboard view to contain the desktop
dashboard top-level page. You assign an authorization role to control access to the desktop
dashboard pages and view.
Exercise 6: You create and configure a console preference profile for a desktop user. You add
the view that you created in Exercise 5, "Creating views" and configure the profile to use the
Tivoli Dark console color theme.
Exercise 7: You log in with an executiveManagementGroup user ID and password and test the
dashboard page functions and navigation.
230 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Starting the Jazz for Service Management applications
Uempty
Note: Several task start icons are shown on the left side of the desktop. Each icon represents
the automation of scripts or commands that are used in these exercises.
Hint: The script starts all installed Jazz for Service Management components with the following
command: /opt/IBM/JazzSM/profile/bin/startServer.sh server1
b. When the Jazz for Service Management components are started, close the command
window. Click the window and press the Enter key.
232 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty
The following logical diagram shows the basic arrangement and types of widgets used on the
second-level page:
The basic elements of the Jazz for Service Management dashboard creation workspace are shown
in the following screen image.
The top section of the workspace contains page and widget control icons.
The middle section provides a widget palette, providing a horizontally arranged list of
available widget objects.
You place widget instances on the canvas by clicking a widget type in the palette and dragging it to
the canvas. You arrange the canvas widgets by clicking and dragging the widget title bar. You
resize canvas widgets by clicking and dragging a widget corner. You collapse the palette view to
provide more visible canvas space.
Task 1: Reviewing the Tivoli Business Service Manager service model: Jazz for Service
Management provides tools to visualize data from multiple applications and business data sources.
You review, at a high level, how Tivoli Business Service Manager tracks and provides data that is
used in the dashboard pages.
Task 2: Creating the second-level GtFTicketDetailPage page: You create the second-level
dashboard page and configure the page widgets to show Tivoli Business Service Manager service
data.
234 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty calculate the business service status or some key performance indicator (KPI). The service model
that is used in these exercises track the trouble tickets in a problem management application.
1. Log on to the Tivoli Integrated Portal server console on the tbsm01 virtual image.
a. Double-click Firefox 17 ESR on the desktop.
c. Log on to the console. Use the information in the following table to complete the console
logon process:
c. The GetThereFast business service information is based on templates and rules that are
defined in the Online_Services template model. Review the configuration of the
Online_Services template. Click the plus symbol (+) to expand the Online_Services and
OSRegion portions of the template.
3. Review the data rules that are defined for the OSRegion template.
a. Click OSRegion in the Service Navigation portlet.
The details of the OSRegion template are shown in the Service Editor portlet. Two of the
rules are configured to count open high and critical severity trouble tickets. The following
two rules are used in this exercise:
236 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty RegSumHigh: This rule calculates the total number of open High severity trouble tickets
for a region of the company.
RegSumCritical: This rule calculates the total number of open Critical severity trouble
tickets for a region of the company.
Note: This exercise is a review of template rules that were created during the laboratory
configuration setup. Do not change the configuration or select these rules in this exercise. You
select the rule names in the Jazz for Service Management console in subsequent exercises in this
unit.
These rule names are used to configure dashboard widgets in the DASH server dashboard
pages.
4. Log off the Tivoli Integrated Portal console. Click Logout. Do not close the browser application.
a. Log on to the console. Use the information in the following table to complete the console
logon process:
238 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty 2. Create the executiveManagementRole authorization role. You use this role to control access to
the dashboard pages.
a. Select the Console Settings > Roles menu in the All Tasks list on the left of the console. A
gear-shaped icon represents the Console Settings folder. The icon is on the left side of the
console.
b. Click New.
d. Assign the role to an authentication group. Members of the group inherit the authorization
role. Click to expand Users and Groups.
e. Add a group to the role configuration. Click the plus symbol (+) in the Groups section.
f. The Jazz for Service Management installation on the jazz01 image is configured to use the
LDAP repository you configured in the Exercise 1, Configuring Tivoli Business Service
Manager to use LDAP users and groups on page 208. Show a list of all groups that are
defined in the federated repository. Click Search.
g. Scroll down the list and select the check box to the left of executiveManagementGroup.
h. Complete the group assignment. Click Add.
240 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty i. You see executiveManagementGroup listed in the Groups section. Complete the role
creation process. Click Save.
3. Start the page creation process for the second-level GtFTicketDetailPage page.
a. Select the Console Settings > Pages menu in the All Tasks list on the left of the console.
A gear-shaped icon represents the Console Settings folder. The icon is on the left side of
the console.
c. Assign the page name. Enter GtFTicketDetailPage in the Page name field.
d. Dashboard pages are maintained in a page object tree. By default, new pages are stored in
the Default folder. Do not change the value console/Default in the Page location field.
e. Define the page layout mode. Select Proportional in the Page Layout options.
4. Create and assign authorization roles to the page. Only members of the
executiveManagementGroup group are allowed to access this page.
a. Click to expand the Optional setting section of the Page Settings form.
b. Add a role assignment to the page. Click Add.
242 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty c. Scroll down the list of available roles. Select the check box to the left of
executiveManagementRole and click Add.
d. The selected role is shown in the Role Name column. The Access Level is an extra level of
object access control. The User access level prevents a user from modifying page settings.
Use the default access level. Click OK to save the page settings.
The page settings workspace is replaced with the page creation workspace.
5. The page palette section shows two folder icons. Each icon represents a widget catalog. A
catalog is a customizable container that you use to organize and group widgets. Open the
catalog to show the available dashboard widgets. Click Dashboard Widgets in the page
palette.
Important: Because of a known bug in the Jazz for Service Management 1.1 release, you
should not resize and move any widget that you add to the page until you configure the properties
for each widget.
6. Locate the Analog Gauge widget in the palette. The analog gauge widget is used to show a
single value within a range of configured minimum and maximum values. Click Analog Gauge
in the palette and drag the widget to the canvas.
244 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty 7. Add the second analog gauge widget to the dashboard page. Click Analog Gauge in the
palette and drag the widget to the canvas.
8. Add more visual information about the regional trouble tickets. Use three Volume Bar widgets to
show a count of tickets that are related to Web servers, databases, and networks. Add and
configure the first Volume Bar widget.
a. Locate the Volume Bar widget in the palette. The widgets are arranged in alphabetical
order, from left to right. Click the arrow icons in the lower center of the palette to scroll
through the widget list.
b. Click and drag the first instance of the volume bar widget from the palette to the canvas.
246 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty 9. Add a second volume bar widget to the page. This widget is configured to show the total
regional ticket count for all open database server tickets.
a. Locate the Volume Bar widget in the palette. Click and drag a second instance of the
volume bar widget from the palette to the canvas.
10. Add a third volume bar widget to the page. This widget is configured to show the total regional
ticket count for all open network-related tickets.
a. Locate the Volume Bar widget in the palette. Click and drag a third instance of the volume
bar widget from the palette to the canvas.
12. Configure the first analog gauge widget to show the open high severity trouble ticket count for a
GetThereFast region.
a. Click the Edit options icon in the upper right of the widget.
Hint: If another widget covers the Edit options icon, click the target widget and select the
Widget > Edit menu. The Widget menu is above the widget palette section. Do not move the
target widget to the foreground. You resize and arrange the widgets in the section, Arranging the
widget layout on the page on page 263.
c. Select the widget data set. Tivoli Business Service Manager provides the data with a
template rule in the OSRegion template. Enter OSRegion in the Select a Dataset Search
field. Click Search.
Important: The console may indicate that no data sets are found the first time you search the
available data sources. This condition happens because of a small delay in establishing the
persistent connections. Click the Search icon again. The data sets are then listed. Subsequent
requests do not show any error indications.
248 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty d. The Tivoli Business Service Manager service provider tool is queried and the list of
matching service templates is shown. Click OSRegion in the TBSM Primary Templates
section.
e. Select the OSRegion template rule data in the Map Visualization Attributes to Dataset
Columns section. For this exercise, use the data in the Tivoli Business Service Manager
RegSumHigh rule in the OSRegion template. Select RegSumHigh in the Value menu.
f. Configure the Optional Settings section of the form. Click to expand the Optional Settings
section.
g. Configure the data that is shown in the analog gauge widget. Enter High Ticket Count in
the Title field.
h. The context for the analog gauge data is provided when a widget in the top-level page is
clicked. Use the Tivoli Business Service Manager Display Name attribute in the OSRegion
template to show the regional context information. Select Display Name in the Label
above Gauge menu.
j. Configure threshold information for the gauge. The thresholds are shown on the widget to
provide more visual information. Use the information in the following table to set the
threshold values:
Threshold Value
Normal 0
Minor 30
Critical 50
Note: Setting threshold values are optional. You do not have to specify a threshold value for all
threshold fields.
k. Configure the widget to show a color-coded threshold strip on the outer edge of the gauge.
Select Show Threshold Strip.
250 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty l. Use the default values for the Minimum Value, Maximum Value, Major Ticks Separation,
and Minor Ticks Separation fields.
m. The RegSumHigh value corresponds to a calculated number of open high severity tickets in
the region. The Unit field provides information about the type of numerical value that is
shown in the gauge. Enter Tickets in the Unit field.
n. Do not change the default settings for the Configure Optional Dataset Parameters
section. This section is optionally used to specify a data set row. A top-level page event
provides the service name. You send the event when a top-level status gauge widget is
clicked.
The widget is shown in the page canvas. Because no service was specified in the
Configure Optional Dataset Parameters section, the widget uses the first service that
matches the configured parameters. You configure the mechanism to pass contextual
information to this widget in Exercise 4, Linking pages with wires on page 282.
252 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty 13. Configure the second Analog Gauge widget to show the open critical severity trouble ticket
count for a selected GetThereFast region.
a. Click the Edit options icon in the upper right of the widget.
14. Select the widget data set. Tivoli Business Service Manager provides the data with a template
rule in the OSRegion template.
a. Enter OSRegion in the Select a Dataset Search field. Click Search.
b. The Tivoli Business Service Manager service provider tool is queried and the list of
matching service templates is shown. Click OSRegion in the TBSM Primary Templates
section.
c. Configure the source of the Tivoli Business Service Manager data to be shown in the
widget. For this exercise, use the Tivoli Business Service Manager RegSumCritical rule
value in the OSRegion template. Select RegSumcritical in the Value menu.
d. Configure the analog gauge widget to show more visual information. Enter Critical Ticket
Count in the Title field.
e. The context for the Analog Gauge is provided when a regional status widget in the top-level
page is clicked. Use the Tivoli Business Service Manager Display Name attribute from the
OSRegion template to show the regional context information. Select Display Name in the
Label above Gauge menu.
254 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty f. Configure threshold information for the gauge. The thresholds are shown on the widget to
provide more visual information. Use the information in the following table to set the
threshold values:
Threshold Value
Normal 0
Minor 30
Critical 50
g. Configure the widget to show a color-coded threshold strip on the outer edge of the gauge.
Select Show Threshold Strip.
h. Use the default values for the Minimum Value, Maximum Value, Major Ticks Separation,
and Minor Ticks Separation fields.
j. Do not change the default settings for the Configure Optional Dataset Parameters
section.
256 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty 15. Edit the first volume bar widget properties. Configure the first volume bar widget to show the
number of open tickets that are related to web servers and web farms in a GetThereFast region.
a. Click Edit options and select the Edit menu.
16. Select the widget data set. Tivoli Business Service Manager provides the data with a template
rule in the OSRegion template.
a. Enter OSRegion in the Select a Dataset search field. Click Search.
b. The Tivoli Business Service Manager service provider is queried and the list of matching
service templates is shown. Click OSRegion in the TBSM Primary Templates section.
e. Enter a descriptive title for the widget. Enter Web Server Ticket Count in the Title field.
f. The TotalWebTickets_Sum_OSWebFarm_to_OSRegion value corresponds to a Tivoli
Business Service Manager rule that calculates the number of open Web server-related
tickets in the region. Configure the threshold information for the gauge. The value that is
shown is a subset of the total open tickets for the region. The thresholds are shown in the
widget to provide more visual information. Use the information in the following table to set
the threshold values:
Threshold Value
Normal 0
Minor 15
Critical 25
g. Show a color-coded threshold strip on the gauge. Select Show Threshold Strip.
h. Use the information in the following table to set the minimum, maximum, and the distance
between graduation marks for the gauge.
Parameter Value
Minimum Value 0
Maximum Value 50
Major Ticks 10
Separation
i. Do not change the default settings for the Configure Optional Dataset Parameters
section.
258 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
17. Edit the second volume bar widget properties. Configure the second volume bar widget to show
the number of open tickets that are related to database servers in a GetThereFast region.
a. Click Edit options and select the Edit menu.
18. Select the widget data set. Tivoli Business Service Manager provides the data with a template
rule in the OSRegion template.
a. Enter OSRegion in the Select a Dataset search field. Click Search.
b. The Tivoli Business Service Manager service provider is queried and the list of matching
service templates is shown. Click OSRegion in the TBSM Primary Templates section.
b. Enter a descriptive title for the widget. Enter Database Ticket Count in the Title field.
Threshold Value
Normal 0
Minor 15
Critical 25
d. Configure the widget to show a color-coded threshold strip on the widget. Select Show
Threshold Strip.
e. Set the minimum and maximum number range that is shown on the widget. Use the
information in the following table to set the minimum, maximum, and the distance between
graduation marks in the gauge.
260 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty
Parameter Value
Minimum Value 0
Maximum Value 50
Major Ticks 10
Separation
f. Do not change the default settings for the Configure Optional Dataset Parameters
section.
20. Edit the third volume bar widget properties. Configure the third volume bar widget to show the
number of open tickets that are related to network devices in a GetThereFast region.
a. Click the Edit options icon and select the Edit menu.
b. Select the widget data set. Enter OSRegion in the Select a Dataset search field. Click
Search.
c. The Tivoli Business Service Manager service provider is queried and the list of matching
service templates is shown. Click OSRegion in the TBSM Primary Templates section.
b. Enter a descriptive title for the widget. Enter Network Ticket Count in the Title field.
Threshold Value
Normal 0
Minor 15
Critical 25
d. Configure the widget to show a color-coded threshold strip on the widget. Select Show
Threshold Strip.
e. Set the minimum and maximum number range that is shown on the widget. Use the
information in the following table to set the minimum, maximum, and the distance between
graduation marks in the gauge.
262 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty
Parameter Value
Minimum Value 0
Maximum Value 50
Major Ticks Separation 10
f. Do not change the default settings for the Configure Optional Dataset Parameters
section.
23. Set both analog gauge widgets to a size of six grid units wide by nine grid units tall. Hover the
mouse in a corner of the widget until the cursor icon changes to a resize icon. Click the corner
and drag to adjust the size. Right-click the widget to save the sizing changes.
24. Arrange the Analog Gauge widgets so that the High Ticket Count widget is vertically stacked
above the Critical Ticket Count widget. Place the widgets on the left side of the canvas, one grid
block away from the left edge. Place the High Ticket Count widget 1 grid block below the top
edge of the grid. Include a minimum of one grid block distance between the two widgets.
Hint: To move a widget, hover the mouse over the title bar area of the widget until the cursor
shape changes to a closed hand. Click and drag the widget. Right-click the widget to remove focus
from the widget and save the location change.
264 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty
25. Adjust the size of each volume bar widget. Click and drag the corner of a widget. Set the widget
size to nine grid units wide x six grid units tall.
26. Arrange the three volume bar widgets in a vertical, non-overlapping stack on the right side of
the page.
27. Set all widgets to not show the widget background. For each widget, click the Edit options icon
and select Skin > Transparent.
28. Save the page configuration. Click Save and Exit, in the menu bar above the palette.
29. The final page should look similar to the following screen image:
266 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Creating the second-level tickets detail page
Uempty
Note: The Proportional layout mode that is used to build this page dynamically resizes
dashboard objects. If scrollbars are shown on a widget, increase the console size. Click and drag
a browser window edge to change the size.
You configure the page authorization for users who are assigned the executiveManagementRole
authorization role. The authorization role is created during the laboratory environment setup.
1. There are multiple ways to start the page creation process. You used the Console Settings >
Pages task in Exercise 2, Creating the second-level tickets detail page on page 233. You use
a second method in this exercise.
a. Click the plus symbol (+) in the upper right of the console.
268 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating the top-level service summary page
c. Select the page layout mode. For this exercise, select Proportional in the Page Layout list.
3. Assign authorization roles to the page. Only users or group members that are assigned the
matching role can access the page.
a. Click to expand the Optional setting section.
c. Scroll down the list of available roles. Select executiveManagementRole and click Add.
d. The selected role is shown in the Role Name column. Click OK to save the page settings.
The page settings workspace is replaced with the page creation workspace.
5. Locate the Status Gauge widget in the palette. The widgets are arranged in alphabetical order,
from left to right. Click the arrow icons in the lower center of the palette to scroll through the
widget list.
270 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating the top-level service summary page
Uempty 6. Add a Status Gauge widget to the page canvas. Click and drag the widget to the page canvas.
9. Add a company logo and background image to the page. Locate the Image widget icon in the
widget palette.
a. Click and drag the Image widget icon from the palette to the page canvas.
10. Add a Text widget to the canvas. Locate the Text widget icon in the widget palette.
a. Click and drag the Text widget from the palette to the page canvas.
12. Configure the first status gauge widget to show the overall trouble ticket status for the Asia
GetThereFast geographic region.
a. Click the Edit options icon in the upper right of the widget.
Hint: If another widget covers the Edit options icon, click the target widget and select the
Widget > Edit menu. The Widget menu is above the widget palette section. Do not move the
target widget to the foreground. You resize and arrange the widgets in the section, Arranging the
widget layout on the page on page 263.
272 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating the top-level service summary page
13. Select the widget data set. Tivoli Business Service Manager provides the data with a template
rule in the OSRegion template.
a. Enter OSRegion in the Select a Dataset search field. Click Search.
b. The Tivoli Business Service Manager service provider is queried and the list of matching
service templates is shown. Click OSRegion in the TBSM Primary Templates section.
c. Configure the data set value that is used to evaluate the region status. Use the Tivoli
Business Service Manager status evaluation. Select TBSM Status in the Status menu.
d. Configure optional settings for the Status Gauge widget. Click to expand the Optional
Settings section.
e. Add a title to the widget. Enter Asia Region in the Title field.
f. Do not select values for the Label above Gauge and Label at leading edge menus.
274 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating the top-level service summary page
Uempty 14. Complete the Configure Optional Dataset Parameters section. This section is optionally used
to specify a Tivoli Business Service Manager service or a subset of services. Configure the
widget to use the AsiaGetThereFast regional service.
a. Enter AsiaGetThereFast in the TBSM Service field.
15. Configure the second Status Gauge widget to show the overall trouble ticket status for the
GetThereFast Europe region.
a. Click the Edit options icon or click the widget and use the Widget menu.
16. Select the widget data set. Tivoli Business Service Manager provides the data with a template
rule in the OSRegion template.
a. Enter OSRegion in the Select a Dataset search field. Click Search.
b. The Tivoli Business Service Manager service provider is queried and the list of matching
service templates is shown. Click OSRegion in the TBSM Primary Templates section.
c. Configure the data set value that is used to evaluate the region status. For this exercise, use
the Tivoli Business Service Manager status evaluation. Select TBSM Status in the Status
menu.
d. Configure optional settings for the Status Gauge widget. Click to expand the Optional
Settings section.
e. Add a title to the widget. Enter Europe Region in the Title field.
f. Do not select values for the Label above Gauge and Label at leading edge menus.
17. Complete the Configure Optional Dataset Parameters section. This section is optionally used
to specify a Tivoli Business Service Manager service or a subset of services. Configure the
widget to use the EuropeGetThereFast regional service.
a. Enter EuropeGetThereFast in the TBSM Service field.
276 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating the top-level service summary page
18. Configure the third status gauge widget to show the overall trouble ticket status for the
GetThereFast US region.
a. Click the Edit options icon or click the widget and use the Widget menu.
19. Select the widget data set. Tivoli Business Service Manager provides the data with a template
rule in the OSRegion template.
a. Enter OSRegion in the Select a Dataset search field. Click Search.
b. The Tivoli Business Service Manager service provider is queried and the list of matching
service templates is shown. Click OSRegion in the TBSM Primary Templates section.
c. Configure the data set value that is used to evaluate the region status. Use the Tivoli
Business Service Manager status evaluation. Select TBSM Status in the Status menu.
d. Configure optional settings for the Status Gauge widget. Click to expand the Optional
Settings section.
f. Do not select values for the Label above Gauge and Label at leading edge menus.
20. Complete the Configure Optional Dataset Parameters section. This section is optionally used
to specify a Tivoli Business Service Manager service or a subset of services. Configure the
widget to use the USGetThereFast regional service.
a. Enter USGetThereFast in the TBSM Service field.
b. Do not select Gather Contained Services.
21. Configure the text widget to show title information for the page.
a. Click the Edit options icon or click the Text widget and use the Widget menu.
g. Enter GetThereFast Global Trouble Ticket System in the text entry section of the
configuration window.
278 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating the top-level service summary page
Uempty h. Save the Text widget configuration. Click OK at the bottom of the configuration form.
Note: The directory and file names are case-sensitive. Enter the file name exactly as shown.
280 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 3. Creating the top-level service summary page
Uempty 24. Configure the image widget to proportionally fill the available page canvas. Click the Image
widget Edit options icon and select Fill Work Page.
25. Configure the Image widget to be the page background image. Click the Image widget and
select the Widget > Send to Back menu, above the widget palette section.
26. Set the Status Gauge and Text widgets to not show the widget background. For each widget,
click the Edit options icon and select Skin > Transparent.
27. Arrange and resize the widgets so that they are similar to the following screen image:
28. Save, but do not exit, the page. You save and exit the page configuration workspace after you
configure navigational event wires in Exercise 4, Linking pages with wires on page 282.
2. Click the Show Wires icon in the page and widget control menu bar, above the page palette
section.
3. You configure the event wire to pass selected context information in the
GtFRegionalTicketStatusPage to the GtFTicketDetailPage page. By default, no wires are
defined. Create the first wire definition.
a. Click New Wire in the Summary of wires table.
b. Select the source event for the wire. Click to expand Asia Region in the Available source
events column. Click NodeClickedOn.
282 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 4. Linking pages with wires
d. Select the event wire target. Click to expand the Default folder.
e. Send context information from the source widget to all elements of the target page. Select
the GtFTicketDetailPage.
Note: Do not select a GtFTicketDetailPage widget as the wire target. The page is selected to
send the source event to all elements of the page. You select a specific widget if you want the
source event to apply to only that widget.
f. Configure the wire to automatically open and show the target page. Select the Load the
selected target page and Switch to the selected target page options.
h. Do not select an event transformation option. Click None in the Available transformation
column.
Note: Transformations can be used to intercept and modify a source event before deliver to a
target object. Transformations are beyond the scope of this laboratory.
4. Add a second event wire. Use the Europe Region status gauge as the event source.
a. Click New Wire in the Summary of wires table.
b. Select the source event for the wire. Click to expand Europe Region in the Available
source events column. Click NodeClickedOn.
284 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 4. Linking pages with wires
d. Select the event wire target. Click to expand the Default folder.
e. Send context information from the source widget to all elements of the target page. Select
GtFTicketDetailPage.
f. Configure the wire to automatically open and show the target page. Select the Load the
selected target page and Switch to the selected target page options.
h. Do not select an event transformation option. Click None in the Available transformation
column.
5. Add a third event wire. Use the US Region status gauge as the event source.
a. Click New Wire in the Summary of wires table.
b. Select the source event for the wire. Click to expand US Region in the Available source
events column. Click NodeClickedOn.
c. Click OK.
d. Select the event wire target. Click to expand the Default folder.
e. Send context information from the source widget to all elements of the target page. Select
GtFTicketDetailPage.
f. Configure the wire to automatically open and show the target page. Select the Load the
selected target page and Switch to the selected target page options.
286 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 4. Linking pages with wires
h. Do not select an event transformation option. Click None in the Available transformation
column.
i. Complete the event wire configuration. Click OK. The three event wires are shown in the
Summary of wires table.
6. Close the Summary of wires table. Click the X icon in the upper right of the table. Do not close
the page.
7. Save the GtFRegionalTicketStatusPage page. Click Save and Exit in the page and widget
control menu bar, above the page palette section.
288 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating views
c. Do not enable the view for mobile devices and do not select to hide any open pages that are
not part of the view.
3. Assign authorization roles to the view. Only users or group members assigned the matching
role can access the view.
a. Click to expand the Roles with Access to This View section.
5. Scroll through the list of available roles and select executiveManagementRole. Click Add.
6. Do not change the default User Access Level setting for the role.
7. Add the top-level GtFRegionalTicketStatusPage page to the view. Click to expand the Pages
in This View section.
8. Click Add.
9. Scroll through the list of pages and select Default > GtFRegionalTicketStatusPage.
290 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 5. Creating views
Note: The event wires that you configured in Exercise 4, Linking pages with wires on
page 282, send context information to the second-level page, GtFTicketDetailPage. Without
context information, the data that is shown in the analog gauge and volume bar widgets is based
on the first data set entry that matches the widget configurations. To prevent the
GtFTicketDetailPage page from being opened without context information, the page is not
included in the view.
11. Configure the view to automatically open the GtFRegionalTicketStatusPage page when the
view is opened. In the Pages in This View section, click to expand the Default folder.
12. Select Launch in the GtFRegionalTicketStatusPage row. With only one page in the view,
Default is automatically selected.
13. Save the view configuration. Click Save, at the bottom of the page.
292 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 6. Creating console preference profiles
Uempty
2. Click New.
b. Configure the profile to use a color theme with dark backgrounds and white text. Select
Tivoli Dark in the Theme menu.
c. Use default values for all other fields and selections in the form.
4. Assign the executiveManagementRole authorization role to the profile. Adding this role
ensures that only users assigned the role use this profile.
a. Click to expand Roles Using This Preference Profile.
b. Click Add.
294 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 6. Creating console preference profiles
Uempty c. Scroll down in the list and select executiveManagementRole. Click Add.
5. The selected role is shown in the Role Name column. Configure the profile to use the view you
created in Exercise 5, "Creating views," on page 288. Select executiveManagementView in
the Default console view menu.
296 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 7. Verifying the desktop dashboard
Uempty 3. The executiveManagementView you created in Exercise 5, "Creating views," on page 288 is
automatically opened. This view is the only desktop view that is defined for this user. Test the
navigational configuration between dashboard pages.
a. Click the US Region widget in the page.
Hint: Several folders that are available for the jazzadmin user ID are not shown in the task bar
in the left edge of the console. The folders are not shown because they were not explicitly added
to the view or the user ID is not assigned the required authorization roles.
b. Verify that the second-level page is shown, showing US region open ticket counts. The US
region should show 36 high severity open tickets in the High Ticket Count widget and 12
critical severity open tickets in the Critical Tickets Count widget. The volume bar widgets
should show 15, 14, and 19 open tickets for web servers, database servers, and network
services.
4. Switch back to the top-level page. Click the GtFRegionalTicketsStatusPage tab at the top of
the console.
5. Click the other region widgets in the GtFRegionalTicketStatusPage page. Verify that the
widget totals change for each region.
298 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
10 Command line administration
exercises
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.
In these exercises, you use command-line tools to complete the following tasks:
Create and verify a WebServer and WebFarm instance.
Assign authorization roles to the WebFarm service model to restrict user access to the services.
Export and import service models
Hint: All RAD Shell commands are case-sensitive. Quotation marks (" ") enclose most
parameters. Look carefully at the commands if you receive an error.
radshell>
4. Create a service instance called WebServer99. The instance is based on the WebServer
template.
a. Enter the following command:
addServiceInstance("WebServer", "WebServer99", "A new WebServer
instance", "Standard");
5. Create a service instance called WebFarm5. The instance is based on the WebFarm template.
a. Enter the following command:
addServiceInstance("WebFarm", WebFarm5", "A new WebFarm instance",
"Standard");
6. Use the Tivoli Integrated Portal console to verify the WebFarm5 and WebServer99 service
instances are created.
a. Log on to the Tivoli Business Service Manager console. Use the information in the following
table to complete the logon process:
300 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration exercises
Exercise 1. Creating and verifying a WebFarm service model
Uempty The WebServer99 and WebFarm5 instances are at the bottom of the service tree. No
dependency exists between the two services.
2. Verify the dependency creation. Refresh the Services view in the Service Navigation portlet.
302 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration exercises
Exercise 2. Exporting and importing service models
Uempty
export(): This command writes all service model, template, data fetcher, and data source
configuration commands to a file.
exportCSV(): This command produces service instance and service dependency data in
comma-separated value (CSV) files.
exportMeta(): This command writes all template, data fetcher, and data source configuration
commands to a file. It does not produce service instance or service dependency data.
The data file contains the RAD Shell commands that are used to re-create the exported Tivoli
Business Service Manager object.
1. Create an export file for the AlliedSteel service model. Enter the following command to export
the AlliedSteel service model.
exportFromStartingInstance(AlliedSteel);
3. Use the Tivoli Business Service Manager console to delete the AlliedSteel service model.
a. Click the Delete icon in the Services section of the Service Navigation portlet.
b. Select services to delete with the list in the Service Editor portlet. Select the check box to
the left of the following service instances:
AlliedSteel
DBCluster2
WebFarm2
304 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration exercises
Exercise 2. Exporting and importing service models
Uempty 4. Verify that the services are removed in the service tree.
a. Refresh the service tree in the Services section of the Service Navigation portlet.
b. Use the exported data file to re-create the AlliedSteel service model. Enter the following
commands in the Linux command window:
cd /opt/IBM/tivoli/tbsm/export
cat export.radsh | /opt/IBM/tivoli/tbsm/bin/rad_radshell
Note: The export.radsh file contains commands to re-create objects that are not deleted. As
these commands start, exception errors are shown in the command window. These errors can be
ignored.
c. Log off the Tivoli Integrated Portal server console. Click Logout.
306 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
10 Command line administration exercises
Exercise 3. Viewing Tivoli Business Service Manager customizations
Uempty The Artifact Name, Category, and Subcategory column values are used with getArtifact,
putArtifact, tbsm_export, and tbsm_import commands. The following screen image is not
from a deployment with customizations. Your file contains extra data.
3. Close the text editor. Select the File > Quit menu.
You configure verbose JVM garbage collection in the Tivoli Integrated Portal server server.xml file.
The server.xml file is in the following directory on the tbsm01 virtual image:
$TIP_HOME/profiles/TIPProfile/config/cells/TIPCell/nodes/TIPNode/servers/ser
ver1
Uempty The following text is a sample of the garbage collection log file output:
<af type="tenured" id="1" timestamp="Sep 20 18:19:40 2010" intervalms="0.000">
<minimum requested_bytes="8208" />
<time exclusiveaccessms="1.705" />
<tenured freebytes="6712776" totalbytes="13421772" percent="5">
<soa freebytes="1992" totalbytes="127506944" percent="0" />
<loa freebytes="6710784" totalbytes="6710784" percent="100"/>
</tenured>
<gc type="global" id="1" totalid="1" intervalms="0.000">
<classloadersunloaded count="0" timetakenms="1.325" />
<refs_cleared soft="1" threshold="32" weak="67" phantom="0"/>
<finalization objectsqueued="141" />
<timesms mark="82.260" sweep="6.612" compact="0.000" total="90.384" />
<tenured freebytes="113970720" totalbytes="134217728" percent="84" >
<soa freebytes="107259936" totalbytes="127506944" percent="84" />
<loa freebytes="671078" totalbytes="671078" percent="100"/>
</tenured>
</gc>
<tenured freebytes="113962512" totalbytes="134217728" percent="84" >
<soa freebytes="1072517" totalbytes="1275069" percent="84"/>
<loa freebytes="6710784" totalbytes="6710784" percent="100"/>
</tenured>
<time totalms="93.281" />
</af>
The garbage collection log file, is written in XML format. The log file is analyzed in this exercise with
the IBM Monitoring and Diagnostic Tools for Java - Garbage Collection and Memory Visualizer and
the IBM Support Assistant workbench.
The tool does not analyze the log file in real time. For parts of this exercise, you start scripts that
copy the native_stderr.log file to files that correspond to the tested heap size. The copied file
name is saved in the form native_stderr_<heapsize>.log. The native_stderr.log file is then
cleared of data, in preparation for the next heap size test.
The following list describes several of the output values in the log file:
<af> </af>: This XML tag contains all of the data that is related to each garbage collection cycle.
intervalms=value: The intervalms is an attribute in the <af> tag. It indicates the interval
between garbage collections. This attribute and value are repeated in the <gc> tag.
id=value attribute: The id is an attribute in the <gc> tag. It is incremented for each new
garbage collection entry in the log file. This attribute value is especially useful when the garbage
collection is happening on a short interval, causing the log file output to change frequently. This
counter is reset to 1 when the Tivoli Integrated Portal server is stopped and started.
totalms=value attribute: The totalms value is an attribute in the <time> tag. It indicates the
duration of the garbage collection.
Analyze the JVM garbage collection log file. The log file is examined with an IBM Support
Assistant tool.
Restore the heap size parameters to the original JVM heap size configuration.
Analyze and compare the JVM garbage collection log files. Evaluate the effect of each heap
size on the garbage collection operation.
Start the Tivoli Business Service Manager shutdown script. Select the following desktop
menu:
2. Enable verbose garbage collection and edit the heap size parameters for the Tivoli Integrated
Portal server. Open a file browser. Double-click the tivolis Home icon on the desktop.
310 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting exercises
Exercise 1. Tuning the Tivoli Integrated Portal Server Java virtual machine heap size
Uempty 3. Locate the Tivoli Integrated Portal server server.xml file. Browse to the following directory:
/opt/IBM/tivoli/tipv2/profiles/TIPProfile/config/cells/TIPCell/nodes/TIPNode/servers/server1
4. Create a copy of the server.xml file. Right-click the server.xml file and select Copy.
5. Right-click any white space in the server1 directory listing and click Paste. The backup file
name is automatically set to server(copy).xml.
6. Edit the server.xml file. Right-click the server.xml icon in the server1 directory listing and
select Open with gedit.
312 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting exercises
Exercise 1. Tuning the Tivoli Integrated Portal Server Java virtual machine heap size
Uempty 7. Search for the XML element called jvmEntries. Select the Search > Find menu.
a. Enter jvmEntries in the Search for field.
b. Click Find.
Note: The XML element that is called jvmEntries contains several attribute definitions that are
related to JVM garbage collection. The following table lists three of the attribute names and
laboratory configuration values used by the Tivoli Integrated Portal server on the virtual image:
Hint: Setting the initialHeapSize and maximumHeapSize to the same value generally
improves performance. Using the same values for both parameters prevents the heap from being
compacted, which impacts performance. It also makes testing results more consistent. A potential
performance impact is the server startup time.
b. Save the modified server.xml file. Select the File > Save menu, but do not close the editor.
b. Close the command window when the script completes. Click the command window and
press the Enter key.
b. List all users that are defined in the federated repository. Click Users and Groups >
Manage Users in the All tasks view.
c. Click Search.
d. Click the Administration > Service Configuration task in the All tasks view.
314 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting exercises
Exercise 1. Tuning the Tivoli Integrated Portal Server Java virtual machine heap size
Uempty e. Select the Service Component Repository menu in the Service Navigation portlet.
f. Expand the service tree. Click to expand the plus symbol (+) next to the following services:
Component Registry > Servers > All
b. Create a copy of the native_stderr.log file. You use the copied file later in this exercise to
examine the effects of the JVM heap size values. A script is configured to copy
native_stderr.log to a file named native_stderr_2048m.log. Select the following desktop
menu:
Start > TBSM Exercises > Unit11 > Exercise01 > Copy 2048M Heap Size Log
c. After the file copy is complete, close the command window. Click the command window and
press the Enter key.
c. Start the memory analysis tool. Scroll down in the Tools Catalog list and select IBM
Monitoring and Diagnostic Tools for Java - Garbage Collection and Memory
Visualizer.
316 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting exercises
Exercise 1. Tuning the Tivoli Integrated Portal Server Java virtual machine heap size
My Computer > LocalAgent > Unix Root > opt > IBM > tivoli > tipv2 > profiles >
TIPProfile > logs > server1 > native_stderr_2048m.log
h. Click OK.
i. Click Next to load the file in the IBM Support Assistant workbench tool.
318 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting exercises
Exercise 1. Tuning the Tivoli Integrated Portal Server Java virtual machine heap size
Uempty j. The log file data is initially shown in a graph under the Data set 1 tab. Click the Structured
data tab to see a summary of the log information.
Note: The specific values that are shown in your log file are similar to this screen image. The
actual values are dependent on the laboratory environment.
b. Save the updated server.xml file. Select the File > Save menu, but do not close the file
editor.
d. Click Search.
e. Click the Administration > Service Configuration task in the All tasks view.
320 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting exercises
Exercise 1. Tuning the Tivoli Integrated Portal Server Java virtual machine heap size
Uempty f. Select the Service Component Repository menu in the Service Navigation portlet.
g. Expand the service tree. Click to expand the plus symbol (+) next to the following services:
Component Registry > Servers > All
17. Create a copy of the native_stderr.log file. A script is configured to copy native_stderr.log to
native_stderr_1200m.log.
a. Select the following desktop menu:
Start > TBSM Exercises > Unit11 > Exercise01 > Copy 1200M Heap Size Log
b. After the file copy is complete, close the command window. Click the command window and
press the Enter key.
b. Open /opt/IBM/tivoli/tipv2/profiles/TIPProfile/logs/server1/native_stderr_1200m.log.
Select the File > Open File menu.
322 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting exercises
Exercise 1. Tuning the Tivoli Integrated Portal Server Java virtual machine heap size
21. The IBM Support Assistant workbench shows the two files as Data set 1and Data set 2. Switch
to the Structured data view for Data set 2.
22. Using your laboratory results, fill out the fields in this table.
Number of collections
23. Select the optimal heap size, which is based on your results and the following criteria:
Lowest garbage collection pause value
b. Close the file editor. Select the File > Quit menu.
b. When the command script is completed, close the command window. Click the command
window and press the Enter key.
324 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V7.0
11 Maintenance and troubleshooting exercises
Exercise 1. Tuning the Tivoli Integrated Portal Server Java virtual machine heap size
Uempty
There are extra requirements specific to each product, but certain general guidelines must be
followed when configuring SSO:
Common User Authentication: There must be a single user and group repository, providing
common authentication information for any user of a participating SSO application. A common
authentication repository must use the Lightweight Directory Access Protocol (LDAP). You
configured LDAP authentication for your Tivoli Business Service Manager system in the exercise
Assigning authorization roles on page 226.
Each application must create and exchange single sign-on trust keys: The Tivoli Integrated
Portal server and IBM Tivoli Monitoring use WebSphere Application Server technology to provide
authentication and visualization services. WebSphere Application Server supports an
authentication mechanism that is called a Lightweight Third-party Authentication (LTPA) token.
LTPA software tokens provide trust and authentication information across multiple applications. You
create the trust relationship between the application servers. Each application must create and
exchange an SSO key with all other application servers in the SSO domain.
Configure all server components to use fully qualified domain names: SSO configuration
includes defining the scope of the SSO domain. Only application servers that are part of the same
Internet Protocol domain or subdomain can participate in the same SSO domain. For example, if
the IP domain scope is defined as tivoli.edu, both image1.tivoli.edu and image2.austin.tivoli.edu are
eligible to participate.
Authorization must be configured for users of all applications: SSO provides seamless
authentication across application consoles, but authorization must still be configured for each user
Uempty of each application. For example, a user that is initially defined as an IBM Tivoli Monitoring system
administrator would not be able to view any page on a Tivoli Integrated Portal server. The IBM Tivoli
Monitoring administrator also needs the assignment of appropriate Tivoli Integrated Portal
authorization roles.
All participating application servers must synchronize clocks. Each time an LTPA token is
issued, it is valid for a specific time period. Differences in system clocks can invalidate an LTPA
token. For example, assume the system clock for server1 was set to 8:40 AM, but the system clock
for server2 drifted, and is set to 8:55 AM. Assume also that the token is configured to be valid for 10
minutes. If a user authenticates to server1 and then tried to access server2 with launch-in-context,
the SSO authentication would fail. This failure occurs because server2 considers any token from
server1 to be 15 minutes old.
Verify Tivoli Monitoring on the itm01 image: You log on to the itm01 image and verify all Tivoli
Monitoring processes are started.
Transfer the SSO key from the itm01 virtual image: Each server that participates in an SSO
environment must share a common SSO key. Any server in the SSO realm creates the key. The
key is used to generate a trusted token that is included in any connection request from one product
console to another. The common SSO key was generated on the itm01 image during the laboratory
configuration. This task transfers the itm01 key file to the Tivoli Integrated Portal server.
Import the SSO key into the Tivoli Integrated Portal server: This task imports the SSO key that
is generated by the Tivoli Enterprise Portal Server into the Tivoli Integrated Portal server.
c. Review the status of the Tivoli Monitoring Services. Double-click Manage ITM Services on
the desktop.
Note: The Manage Tivoli Enterprise Monitoring Services tool takes approximately 10 seconds to
start. Do not double-click the icon multiple times.
Warehouse Proxy
e. If a service is not started, click the service name, then right-click and select Start Service.
328 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Configuring single sign-on
Uempty
Transferring the SSO key from the itm01 virtual image
An SSO key was created on the itm01 image during the laboratory setup. The SSO key is used to
establish security trust between SSO applications. In this task, you transfer the key to the tbsm01
server. It is imported into the tbsm01 Tivoli Integrated Portal server in a subsequent task.
1. Transfer the exported key from itm01 to the Tivoli Integrated Portal server. You start a script that
uses a secure copy command to transfer the key to the Tivoli Integrated Portal server on
tbsm01.
a. Switch to the tbsm01 image desktop.
c. You are prompted for a password to complete the file transfer. Enter object00.
d. When the transfer is complete, close the command window. Click the command window and
press the Enter key.
2. Log on to the Tivoli Integrated Portal server console on the tbsm01 image.
a. Use the information in the following table to complete the logon process:
c. Click Security > Global security in the task list at the left side of the console.
b. Set the LTPA token validity duration value. Enter 1440 in the LTPA timeout field.
c. Enter the key file password. Enter object00 in the Password and Confirm password
fields.
d. Enter the file name for the imported key file. Enter /opt/ssokeys/itm_sso_key.txt in the
Fully qualified key file name field.
330 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 1. Configuring single sign-on
5. A message is shown, indicating that the keys were successfully imported. Save the updated
server master configuration.
a. Click Save
6. Set the LTPA scope. SSO servers accept only authentication requests from SSO servers that
are in the same domain or subdomain. Set the tbsm01 SSO domain scope.
a. Expand the Web Security link in the Authentication section of the page.
c. SSO is automatically enabled during the Tivoli Business Service Manager installation, but
no domain name is configured. Enter tivoli.edu in the Domain name field.
e. Save the changes to the master configuration. Click Save in the Messages section.
f. Log off the Tivoli Integrated Portal WebSphere server administrative console. Click Logout.
g. Log off the Tivoli Integrated Portal server console. Click Logout.
b. Close the command window. When the script is completed, press the Enter key.
c. Start the Tivoli Integrated Portal server. Select the following desktop menu.
Start > TBSM Utilities > Start TBSM TIP Service
d. Close the command window. When the script is completed, press the Enter key.
332 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Configuring launch-in-context: Tivoli Integrated Portal to IBM Tivoli Monitoring
Uempty
The launch tool is available from a service viewer or service tree portlet. When selected, a second
browser window is opened and automatically connects to the Tivoli Enterprise Portal Server
console. The console opens to a contextual workspace view of the service instance. A second
interactive authentication with the Tivoli Enterprise Portal Server is not required.
Using LIC to a Tivoli Monitoring console resource requires that the following attributes are defined
for the source service model:
IBM_Tivoli_Monitoring_Services_sourceContactInfo: This attribute is the web address that
points to the Tivoli Enterprise Portal Server. The host name is defined as a fully qualified
domain name. The target host name must include the domain that is defined in the SSO scope.
b. Open the Firefox 17 ESR browser that you used in Chapter 9, "Custom dashboards and
page management exercises," on page 229.
c. Clear the browser cache data. This step ensures that there are no browser cookies that are
stored in the browser. Select the Tools > Clear Recent History menu. Click Clear Now.
Username Passsword
tipuser2 object00
334 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Configuring launch-in-context: Tivoli Integrated Portal to IBM Tivoli Monitoring
Uempty IBM_Tivoli_Monitoring_Service_sourceToken
These attributes are automatically defined for service instances that are created from IBM
Tivoli Monitoring discovered resources. Discovered resources require either data from a
Tivoli Monitoring Discovery Library Adapter or through IBM Tivoli Monitoring resources that
are discovered by Tivoli Application Dependency Discovery Manager.
A second browser window is automatically opened with the web address built from the
service instance attributes. The Tivoli Enterprise Portal console is started and focused on
the source managed node, itm01.
c. You are prompted to accept a security certificate. Select Accept this certificate
permanently.
d. Click OK.
e.
336 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
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 exercises
Exercise 2. Configuring launch-in-context: Tivoli Integrated Portal to IBM Tivoli Monitoring
Uempty
Note: The first SSO application to which a user logs on creates an LTPA token. The LTPA token
is stored as a cookie in the users browser. Connecting to another application console uses the
original LTPA token authentication. When either application console is closed, the browser LTPA
token is invalidated for security reasons. The remaining console connection is then also
invalidated. Any attempts to use the console session results in errors and the console session is
automatically closed.
6. Show the LTPA cookie information in the browser preferences. Select the Edit > Preferences >
Privacy menu.
7. Review the browser cookie list. Click remove individual cookies. The LTPA token is listed
below the name of the defined SSO domain scope. Expand tivoli.edu in the Site column.
338 Tivoli Business Service Manager 6.1.1 for Administrators Copyright IBM Corp. 2013, 2014
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
APPENDIX A ESDA policy script
The script commands are provided in a text file on the tbsm01 virtual image. To avoid typographical
errors, use a text editor to copy and paste the commands. The contents of the text file is included in
this appendix.
Elements = rextractall(ExternalFilter,"(.*\-rtr\-.*:.*)\-(.*\-rtr\-.*:.*)");
AInstance.MyInstanceName = Elements[0];
AInstance.MyDisplayName = Port A: + Elements[0];
AInstance.MyDescription = "Created in ESDA Policy";
BInstance.MyInstanceName = Elements[1];
BInstance.MyDisplayName = Port B: + Elements[1];
BInstance.MyDescription = "Created in ESDA Policy";
NextLevelOrgNodes = {AInstance,BInstance};
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
Appendix A ESDA policy script
Uempty i=0;
while (NextLevelOrgNodes[i] <> NULL) {
NextLevelOrgNodes[i]._TagList = "Port";
i = i + 1;
}
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.
More
Back pa about Cloud & Smarter Infrastructure
You can find the latest information about IBM Cloud & Smarter Infrastructure education offerings online at
the following location:
www.ibm.com/software/tivoli/education/
Also, if you have any questions about education offerings, send an email to the appropriate alias for your
region:
Americas: tivamedu@us.ibm.com
Asia Pacific: tivtrainingap@au1.ibm.com
EMEA: tived@uk.ibm.com
Certification
All IBM certifications are based on job roles. They focus on a job a person must do with a product, not just
the products features and functions. Online certification paths are available to guide you through the
process for achieving certification in many IBM Cloud & Smarter Infrastructure areas. See
ibm.com/tivoli/education for more information about certification.
Special offer for having taken this course: Now through 31 December 2013: For completing this course,
you are entitled to a 15% discount on your next examination at any Thomson Prometric testing center
worldwide. Use this special promotion code when registering online or by telephone to receive the
discount: 15CSWR. (This offer might be withdrawn. Check with the testing center.)
Authorized
Training
ibm.com/training
Printed in Ireland
CT4QDEN
CT4QDEN