Ibm tivoli business service manager v4.1 redp4288

Front cover

IBM Tivoli Business
Service Manager V4.1
Next generation of business system
management

Includes TBSM V3.1 feature
comparison

Cover migration from
Netcool/RAD V3

Budi Darmawan
Daniel Peacock
Gary Kalatucka

ibm.com/redbooks Redpaper

International Technical Support Organization

IBM Tivoli Business Service Manager V4.1

September 2007

REDP-4288-00

Note: Before using this information and the product it supports, read the information in
“Notices” on page v.

First Edition (September 2007)

This edition applies to Version 4, Release 1, Modification 0 of Tivoli Business Service Manager
(product number 5724-C51).

Note: This book is based on a pre-GA version of a product and may not apply when the
product becomes generally available. We recommend that you consult the product
documentation or follow-on versions of this book for more current information.

© Copyright International Business Machines Corporation 2007. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
The team that wrote this IBM Redpaper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. Introduction to business service management . . . . . . . . . . . . . 1
1.1 Business service management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Tivoli management portfolio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Redpaper environment and organization . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2. Tivoli Business Service Manager concepts and architecture . 5
2.1 Business service management concepts . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Tivoli Business Service Manager architecture . . . . . . . . . . . . . . . . . . . . . . 8
2.2.1 Netcool OMNIBus object server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.2 Netcool license server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.3 Netcool security server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.4 Netcool GUI Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2.5 Tivoli Business Service Manager server . . . . . . . . . . . . . . . . . . . . . . 14
2.3 Interfaces and integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3.1 Tivoli EIF event interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3.2 Discovery interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3.3 ESDA interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4 Services Manager or Systems Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.1 Terminologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.2 Function differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 3. Installation and migration consideration for Tivoli Business
Service Manager V4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.1 Installation process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2 Installation planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3 Typical full installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.4 Migration process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.4.1 License server considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.4.2 Security manager considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.4.3 Netcool OMNIbus considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.4.4 Migrating Tivoli Business Service Manager data . . . . . . . . . . . . . . . 37

© Copyright IBM Corp. 2007. All rights reserved. iii

3.4.5 Manual modifications required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 4. Working with Discovery Library toolkit . . . . . . . . . . . . . . . . . . 41
4.1 Introduction Discovery Library toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.2 Installation of the Discovery Library toolkit . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2.1 Verify the xmltoolkitsvc.properties is correct . . . . . . . . . . . . . . . . . . . 48
4.2.2 Verify Tivoli BSM Discovery Library toolkit service . . . . . . . . . . . . . . 49
4.2.3 Verify that default templates have been installed . . . . . . . . . . . . . . . 49
4.2.4 Test discovery using the sample provided . . . . . . . . . . . . . . . . . . . . 50
4.3 IBM Tivoli Discovery Library Adapter for z/OS . . . . . . . . . . . . . . . . . . . . . 51
4.3.1 Discovery features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.3.2 Installing z/OS DLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.3.3 Running z/OS discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.3.4 Running Discovery Library toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.4 Tivoli Application Dependency Discovery Manager . . . . . . . . . . . . . . . . . 62
4.4.1 Integration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.4.2 Integration prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.4.3 Integration in action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 5. Operational aspects of Tivoli Business Service Manager . . . 71
5.1 Startup and shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.2 Backup and recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.3 Performance optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.4 Failover consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.4.1 Setting up security server for failover . . . . . . . . . . . . . . . . . . . . . . . . 75
5.4.2 Setting up OMNIbus for failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.4.3 Setting up Tivoli Business Service Manager for failover . . . . . . . . . . 76
5.4.4 Finalizing failover configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
IBM Redbooks Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
How to get IBM Redbooks Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

iv IBM Tivoli Business Service Manager V4.1

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s) described in this publication at
any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on
the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the
sample programs are written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

© Copyright IBM Corp. 2007. All rights reserved. v

Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:

Redbooks (logo) ® IBM® RACF®
z/OS® IMS™ Tivoli Enterprise™
zSeries® MQSeries® Tivoli Enterprise Console®
AIX 5L™ Netcool® Tivoli®
AIX® NetView® WebSphere®
CICS® OMEGAMON®
DB2® Redbooks®

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.

Other company, product, or service names may be trademarks or service marks of others.

vi IBM Tivoli Business Service Manager V4.1

Preface

This IBM® Redpaper leads you through the new Tivoli Business Service
Manager V4.1 that is based on Netcool/Realtime Active Dashboard (RAD),
instead of the previous Tivoli Business Systems Manager V3.1.

This paper describes Tivoli Business Service Manager V4.1 components and
architecture. It also discusses function comparison of Tivoli Business Systems
Manager V3.1 and Netcool/RAD to Tivoli Business Service Manager V4.1.

It documents the installation and migration of Tivoli Business Service Manager
V4.1 in our environment. Migration is currently only available for Netcool/RAD 3.0
users.

This paper also discusses integration with IBM Tivoli® Service Management
framework that allows Tivoli Business Service Manager to integrate with Tivoli
Change and Configuration Management database (CCMDB) using Discovery
Library toolkit. This function is also available for z/OS® configuration.

Finally, Tivoli Business Service Manager operational consideration is discussed,
including backup and recovery process, maintenance schedule, and
performance tips.

The team that wrote this IBM Redpaper
This IBM Redpaper was produced by a team of specialists from around the world
working at the International Technical Support Organization (ITSO), Austin
Center.

Budi Darmawan is Project Leader at the International Technical Support
Organization, Austin Center. He writes extensively and teaches IBM classes
worldwide on all areas of Tivoli systems management product. Before joining the
ITSO eight years ago, Budi worked in IBM Global Technology Services as lead
implementer and solution architect. His current interests include business
management, application management, and Java™ programming.

Daniel Peacock is a Field Technical Sales Specialist from IBM United States. He
previously worked in Micromuse which was acquired by IBM. His speciality is the
Tivoli business automation field.

© Copyright IBM Corp. 2007. All rights reserved. vii

Gary Kalatucka is a Senior Consultant for the SWAT team worldwide team
specializing in Availability and Business Service Management from IBM United
States.

Thanks to the following people for their contributions to this project:

Allen Sofley, Editor
International Technical Support Organization

Douglas McClure, Daniel Kitay, Rod Bowman
IBM Software Group

Become a published author
Join us for a two- to six-week residency program! Help write an IBM Redbooks
Publication dealing with specific products or solutions, while getting hands-on
experience with leading-edge technologies. You will have the opportunity to team
with IBM technical professionals, Business Partners, and Clients.

Your efforts will help increase product acceptance and customer satisfaction. As
a bonus, you will develop a network of contacts in IBM development labs, and
increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and
apply online at:
ibm.com/redbooks/residencies.html

viii IBM Tivoli Business Service Manager V4.1

Comments welcome
Your comments are important to us!

We want our IBM Redpapers to be as helpful as possible. Send us your
comments about this IBM Redpaper or other IBM Redbooks® Publications in
one of the following ways:
Use the online Contact us review form found at:
ibm.com/redbooks
Send your comments in an e-mail to:
redbooks@us.ibm.com
Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400

Preface ix

x IBM Tivoli Business Service Manager V4.1

1

Chapter 1. Introduction to business
service management
This chapter describes business service management as the primary objective
for managing IT resources. The topics include general background information
relevant for managing business service.

The discussion in this chapter includes:
1.1, “Business service management” on page 2
1.2, “Tivoli management portfolio” on page 3
1.3, “Redpaper environment and organization” on page 4

© Copyright IBM Corp. 2007. All rights reserved. 1

1.1 Business service management
From the Web site of Office of Government Commerce (OGC), the glossary of IT
infrastructure library in http://www.best-management-practice.com, a business
service is defined as:
A Service that is delivered to Business Customers by Business Units. For
example delivery of financial services to Customers of a bank, or goods to the
Customers of a retail store. Successful delivery of Business Services often
depends on one or more IT Services.

Based on that definition, the business service has the following attributes:
Business customer, consumer of service that wants the service to be
available so they can accomplish their needs
Business unit, delivers the service, also requires the service to be available
for the business unit so they can satisfy their consumer and get repeat
interaction
IT services, a primary prerequisite to be able to have a successful delivery of
the business service

Business service management is primarily concerned with the ability to manage
IT services rather than just IT systems. IT services should be managed in the
context that they enable business services to function. This includes the following
contexts:
Individual IT components are inter-related to provide service for a business
service. These interactions must be clearly defined and understood to
successfully build the business service definition.
Some IT components might affect more than one business service. The more
business services it affects, the more important the component is. The
importance of the components is needed for prioritizing the work to ensure its
availability.
Some business services might have components that are redundant to
ensure that the services are still in good health even though one or more
components fail.

The ability to tie in IT component availability with a more abstract entity such as
business service is the primary premise of business service management. The
business service can be any entity abstraction that is needed by an enterprise to
conduct its business, such as:
Departmental application health: for example, finance system, human
resource system, purchasing department, warehouse system
Geographical office status: for example, Texas regional office, Asia Pacific
branch status, France marketing department

2 IBM Tivoli Business Service Manager V4.1

Platform based grouping (which might only be of interest to the IT
department): for example, Windows® servers, UNIX® machines, mainframes
Any other combination or decomposition of an entity that needs to be
managed

The availability of a business service would be the most important aspect for
Service Level Agreement (SLA). In SLA, the service provider commits certain
measurement for services to satisfy the service consumer. In IT service SLAs, it
is important to harness the user’s view of the service status instead of the IT
department’s view of it. The abstraction of different components that build into a
business service provides a framework to measure the net impact of business
service availability affected by different combination of outages and failures.

1.2 Tivoli management portfolio
The system management portfolio of IBM Tivoli consists of a systems
management suite to manage your entire IT infrastructure.

The IBM Tivoli product suite is in line with the Information Technology
Infrastructure Library (ITIL®) specification. With the launch of the IBM Tivoli
Service Management suite of products, the overall IBM Tivoli Portfolio can
conceptually be shown in Figure 1-1.

IBM Service Management
IT CRM & Service
Service Information Business
Business Delivery &
Deployment Management Resilience
Management Support

Process Management

Service Management
Platform
Change and Configuration Management Database

Operational
Management
Business
Server, Network & Storage Security
Application
Best Practices Management
Device Management Management Management

Figure 1-1 IBM Tivoli product portfolio

In Figure 1-1, the business service management product resides in the business
application management discipline. For more information on other Tivoli product
suites, visit the Tivoli homepage at:
http://www.ibm.com/tivoli

Chapter 1. Introduction to business service management 3

The business service management function is primarily managed using the
products:
IBM Tivoli Business Service Manager: manages business service entities
because they are affected by the health and status of the underlying IT
components
IBM Tivoli Service Level Advisor: collects and maintains service level
information from various sources for reporting and analysis

This paper discusses the IBM Tivoli Business Service Manager Version 4.1. This
product evolved from Netcool/Real-time Active Dashboard (RAD) Version 3.0.
The product will merge with the existing IBM Tivoli Business Systems Manager
Version 3.1 in the next release.

1.3 Redpaper environment and organization
This redpaper was written in the IBM International Technical Support
Organization (ITSO) Austin center. The project is primarily performed on a set of
Windows 2003 and a Red Hat Enterprise Linux® Advanced Server 4 that we
used as the base environment.

The discussion in this redpaper is divided into the following chapters:
Chapter 1, “Introduction to business service management” on page 1
introduces the redpaper content and puts business service management in
context.
Chapter 2, “Tivoli Business Service Manager concepts and architecture” on
page 5 explains IBM Tivoli Business Service Manager concepts and
architecture. We also compare terminology and concepts related to IBM Tivoli
Business Systems Manager V3.1.
Chapter 3, “Installation and migration consideration for Tivoli Business
Service Manager V4.1” on page 25 describes installation and migration
activities related to IBM Tivoli Business Service Manager.
Chapter 4, “Working with Discovery Library toolkit” on page 41 discusses the
Discovery Library Adapter (DLA) interface to z/OS systems and IBM Tivoli
Application Dependency Discovery Manager.
Chapter 5, “Operational aspects of Tivoli Business Service Manager” on
page 71 covers some operational considerations for IBM Tivoli Business
Service Manager, including performance tips, backup and recovery, and
failover concepts.


2

Chapter 2. Tivoli Business Service
Manager concepts and
architecture
In this chapter, we introduce Tivoli Business Service Manager concepts and
architecture. The discussion in this chapter is divided into:
2.1, “Business service management concepts” on page 6
2.2, “Tivoli Business Service Manager architecture” on page 8
2.3, “Interfaces and integration” on page 15
2.4, “Services Manager or Systems Manager” on page 18


2.1 Business service management concepts
Tivoli Business Service Manager allows us to define business service objects in
a tree view. Each service object has a color coded state associated with it. These
states are calculated either from the state of its descendants or from the effect of
an external event.

The service object can represent an actual IT resource or an abstract entity. A
typical abstract entity can depict a geographical region, business function,
application system, or a collection of items.

Tivoli Business Service Manager can be used as a:
Operational tool for alerting operators of impending problems regarding a
specific function or business process
Prioritization tool for understanding the business impact of an IT resource
outage
Executive tool that shows the state of a certain business function for a quick
check
Service level analysis tool that calculates the net effect of different outages
and failures to the overall service level objective.

This chapter introduces you to how Tivoli Business Service Manager
accomplishes those functions.
In 2.2, “Tivoli Business Service Manager architecture” on page 8, we discuss
the components that make up Tivoli Business Service Manager.
Mechanisms on how events and information enter Tivoli Business Service
Manager is discussed in 2.3, “Interfaces and integration” on page 15.
Finally, we draw some comparisons of Tivoli Business Service Manager V4.1
against Tivoli Business Systems Manager V3.1 in 2.4, “Services Manager or
Systems Manager” on page 18.

The processing of Tivoli Business Service Manager is summarized in Figure 2-1
on page 7.


SQL query
Service templates Service instances

Auto population rules

event
event
event
Figure 2-1 Processing summary

Tivoli Business Service Manager service management function is defined as a
set of service templates and rules.
Service templates can be regarded as a class definition. Service templates
are created in a tree like structure. A service template is an instance
generator which defines how the service objects are created. Service objects
creation is based on:
– Events from Netcool/OMNIbus
– External SQL query from a repository table
Rules are definitions changing service instance definition and its attributes.
There are several different types of rules in Tivoli Business Service Manager,
such as:
– Service object creation rules
• Auto population rule: determines how an event can create service
instances
• Data fetcher rule: creates service objects based on data on a relational
database
• Enhanced Service Dependency Adapter (ESDA) rule: dynamic service
object creation based on an external relational database query. Service
objects that are created using ESDA rules can be persistent or
non-persistent. Their statuses are calculated at runtime using a
database query.
– Status calculation rules

Chapter 2. Tivoli Business Service Manager concepts and architecture 7

• Incoming status rule: defines how an event or data query changes the
status of a service object, can be based on the event state or a
numerical computation
• Status aggregation rule: calculating a status of a service object based
on the collective status of its children
• Numerical rule: defines a computational value that can be used to
show a new attribute of an instance (numerical formula rule) or an
aggregated status of an instance (numerical aggregation rule)
– SLA rules: defines Service Level Agreement status computation
• Cumulative SLA rule: SLA is based on the time a service object has a
good status.
• Duration cumulative SLA rule: SLA is based on availability on a specific
duration (for example: 1 hour of down time in a day).
• Incident based SLA rule: SLA is measured from the number of
detected outages.

The user interface for Tivoli Business Service Manager is Web browser based. It
is based on the Netcool® GUI Foundation. The following are some user interface
objects that can be customized in the Web interface:
Custom view. There are several view types in Tivoli Business Service
Manager, such as:
– Basic relationship tree with only color coded status
– Relationship tree view with SLA information and event count information
– Concentric with the root node as the center
– Grid for all the children without relations
– Geographical Information System (GIS) map
Custom canvas. The canvas provides a visualization method for a service
object. The canvas is useful when combined with the appropriate view to
quickly present business status.
Context menu or action items
Custom icon for newly defined template or service object

2.2 Tivoli Business Service Manager architecture
The overall architecture of Tivoli Business Service Manager is depicted in
Figure 2-2 on page 9.


Tivoli Enterprise IBM Tivoli
NetView
CCMDB Console Monitoring
OMEGAMON
C
Relational Discovery Library ITCAM
databases Books

Data fetcher xml files
ESDA
Optional Tivoli EIF probe
XML Toolkit
components
Tivoli Service
Level Advisor JDBC

TBSM processes
SLA events TBSM
postgreSQL

Netcool GUI Foundation Netcool OMNIbus
TBSM Console TBSM ObjectServer
TBSM Server
events

Netcool Webtop
launch

user data user data license

Tivoli Enterprise
Portal
Netcool Security Manager Netcool License Server

Figure 2-2 Overall architecture of Tivoli Business Service Manager

In Figure 2-2, the components in the TBSM processes box must exist and can be
installed using the Tivoli Business Service Manager installation wizard. These
are the central components that make up the Tivoli Business Service Manager
server. The optional components are distributed with Tivoli Business Service
Manager but can be installed separately. These components are primarily used if
you want to interface Tivoli Business Service Manager with external systems.
The items in Figure 2-2 that are not shown in the boxes are external components
that interface with Tivoli Business Service Manager.

The discussion in this section primarily regards the mandatory components in
the TBSM processes box in Figure 2-2. The optional components and external
interfaces are discussed in 2.3, “Interfaces and integration” on page 15.


2.2.1 Netcool OMNIBus object server
The Netcool OMNIbus object server is a high speed event processing engine
from which Tivoli Business Service Manager collects events. OMNIbus object
server processes events in memory, with a relational database for persistent
event storage. The database in OMNIbus only contains active events. Active
events means events that are not yet closed, thus preserving its performance
and size.

OMNIbus has the ability to perform event processing, correlation, and
automation. The alerts are stored in a table called alerts. The table can be
extended to accommodate additional attributes. This ensures that the
performance of OMNIbus is consistent even with additional attributes, compared
to a SQL join operation that is required to access additional slots in Tivoli
Enterprise™ Console.

The OMNIbus object server requires access to:
Netcool license server for product license information
Netcool security manager for user ID authentication

The OMNIbus object server runs in its own processes that access an embedded
Sybase SQL Anywhere database server. This process can be started separately
using the command $NCHOME/InstallTBSM/start_omni.sh NCOMS.

Netcool OMNIbus collects events from the probes. Probes can connect directly to
the OMNIbus server or can connect through a gateway process. Probes can
collect data directly from the monitored system or act as an event converter. One
example of a probe is the Tivoli Event Integration Facility (EIF) probe. The Tivoli
EIF probe is a Java process that converts Tivoli Enterprise Console® events into
Netcool OMNIbus events.

As Tivoli Business Service Manager gathers status information from events, it
taps into OMNIbus events. Sometimes it is necessary to see what events are in
OMNIbus, or to manage the OMNIbus definition for problem determination or
configuration. The OMNIbus software distributed with Tivoli Business Service
Manager is a restricted version of OMNIbus. It does not have the full
administration and client function to access OMNIbus. You might want to
purchase a separate full function OMNIbus license to work with these advanced
customization needs.

OMNIbus configuration interface is started with the command
$NCHOME/omnibus/bin/nco_config. The interface is shown in Figure 2-3 on
page 11.


Figure 2-3 Netcool configuration

The OMNIbus events can be accessed using the utility called
$NCHOME/omnibus/bin/nco_event. The login page is shown in Figure 2-4 on
page 12.

Note: We have to modify $NCHOME/platform/linux2x86/locales/locales.dat
under the [linux] section to define out locale. The $LOCALE definition in our
Red Hat Enterprise Linux is en_US.UTF-8, while the definition is en_US.utf8.


Figure 2-4 Login to event browser

The event browser is shown in Figure 2-5.

Figure 2-5 Event browser

When you click View, for example in the All Events area, the detailed event list is
displayed. See Figure 2-6 on page 13.


Figure 2-6 Event list

2.2.2 Netcool license server
The Netcool/OMNIbus requires a license to know the features that are enabled
for a particular installation. This license is managed by the Netcool license
server. The server serves as a license repository that the product checks and
validates.

The license server is installed as a separate directory structure under
$NCHOME/license. It runs on its own process, either as a UNIX daemon or a
Windows service. Licenses are stored as files under the $NCHOME/license/etc
directory. Tivoli Business Service Manager V4.1 uses two license files:
netcool_omni_anyhost_keys.lic
netcool_tbsm_anyhost_keys.lic

2.2.3 Netcool security server
The Netcool security server authenticates the user ID with its password. It runs in
a Java process that reads authentication requests from a network port. The
password authentication can be performed against a local repository or against
an LDAP directory server.

Both Netcool/OMNIbus and Netcool GUI Foundation use the security server to
authenticate users. However, each uses their own mechanism for determining
what are the authority of the users once their passwords are authenticated.


The security manager is installed as a separate directory structure under
$NCHOME/security.

The user and group IDs in the security manager are stored in a separate
database under $NCHOME/security/db directory. For UNIX or Linux based
platforms, the command ncsm_db can be used to maintain the database.

Another option for using the security manager is to interface authentication to an
external Light-weight Directory Access Protocol (LDAP) server. This allows user
management to be performed integrated with other user authentication
processes outside of the Netcool suite.

2.2.4 Netcool GUI Foundation
The Netcool GUI Foundation is a custom used J2EE™ server based on the
Apache Tomcat server. The Tivoli Business Service Manager server process is
actually an application running in the Java process. The Netcool GUI Foundation
also hosts the Netcool Webtop, which provides another layer of Web navigation
for Tivoli Business Service Manager.

Netcool GUI Foundation resides in $NCHOME/guifoundation. The Netcool GUI
Foundation allows Web applications to be deployed into it. The Web applications
are deployed in the webapps path. The Web application for Tivoli Business
Service Manager is called sla. The name is derived from the original purpose of
the application which is calculating and managing Service Level Agreements.

2.2.5 Tivoli Business Service Manager server
As discussed in 2.2.4, “Netcool GUI Foundation” on page 14, the Tivoli Business
Service Manager server is a Web application residing inside Netcool GUI
Foundation. This section discusses the server processing in more detail. The sla
Web application has the following functions:
Serve the graphical interface, in coordination with Netcool GUI Foundation
and Webtop functions
Apply filters for the incoming events from Netcool/OMNIbus to match them
with the service templates, and create service instances for events that match
service templates
Run ESDA interface to work with external relational database access as
discussed in 2.3.3, “ESDA interface” on page 16
Change service instances status based on existing aggregation or status
rules


The Tivoli Business Service Manager Web application uses a separate
postgreSQL relational database as its repository. The postgreSQL database runs
on its own process. The Netcool GUI Foundation uses JDBC™ to access the
postgreSQL database.

2.3 Interfaces and integration
As discussed in 2.2, “Tivoli Business Service Manager architecture” on page 8,
Tivoli Business Service Manager receives events from Netcool/OMNIbus. Events
go in to Netcool OMNIbus from the OMNIbus probes. For IBM Tivoli Enterprise
Console events, there is a specialized probe called Tivoli Event Integration
Facility (EIF) probe to get the IBM Tivoli Monitoring and Tivoli Enterprise Console
events into OMNIbus. There are other optional methods of data baing used to
populate the service instance hierarchy in Tivoli Business Service Manager,
those are for the discovery interface using the XML toolkit. The methods are
discussed in this section. Another major component in Tivoli Business Service
Manager interface is ESDA.

2.3.1 Tivoli EIF event interface
Events from Tivoli Enterprise Console or IBM Tivoli Monitoring come through the
Tivoli EIF probe. The probe listens to incoming events that are forwarded to it
from the Tivoli Enterprise Console or the IBM Tivoli Monitoring interface. The
probe then inserts the event into the Netcool/OMNIbus event repository.

Tivoli Business Service Manager is notified regarding the events, and the
following happens:
Auto population rule reads the events and defines any newly discovered
service instances.
Incoming status rule applies status changes to the service instances.

This interface is similar to and meant to replace the Tivoli Business Systems
Manager V3.1 generic event interface using the ihstttec exit.

2.3.2 Discovery interface
The discovery interface uses the Discovery Library adapter. The Discovery
Library adapter is often called the XML toolkit. The Discovery Library adapter
reads Discovery Library books that are generated by other applications,
especially IBM Tivoli Application Dependency Discovery Manager. The
Discovery Library book is an XML file that conforms to the idML specification.


The discovery interface allows service instance creation based on the object
structure from the XML files. The service instances are created in the SCM
tables. The actual instances are created from the SCM instances.

The discovery interface can also be used to create resources from the z/OS
Discovery Library adapter.

The Discovery Library adapter is discussed in Chapter 4, “Working with
Discovery Library toolkit” on page 41.

2.3.3 ESDA interface
The ESDA interface allows dynamic instance and status display in the Tivoli
Business Service Manager Web console. The ESDA interface retrieves the
service instance information from a relational database table. The ESDA rules
define how a child connects to its parent and also how parents connect to their
children.

ESDA definitions are completely dynamic. They are not stored in the Tivoli
Business Service Manager database structure. The objects and their
relationships are queried on the fly at the time you expand a service instance.
This can be viewed as a just-in-time dynamic configuration, or as another
additional performance requirement for running all these functions.

An example of ESDA function is illustrated in Figure 2-7 on page 17.


Hostname Software Event no Enterprise

abc.north.abc.com DB2 0

abc.north.abc.com WebSphere 4
Location
def.north.abc.com DB2 2

def.north.abc.com Tomcat 2
Machine
def.north.abc.com Apache 1

ghi.south.abc.com WebSphere 19
Software
ghi.south.abc.com Domino 2

Figure 2-7 Sample ESDA processing

In Figure 2-7, the source data is a single table. From the table, we define the
hierarchy of Enterprise - Location - Machine - Software component. The mapping
of the hierarchy would be similar to Table 2-1.

Table 2-1 Hierarchy mapping
Component Source data

Enterprise ABC Corp

Location substr(hostname, pos(‘.’,hostname), length(hostname))

Machine hostname column

Software sw column

Based on that hierarchy, the service instances are then defined similar to
Figure 2-8 on page 18.


ABC Corp

north.abc.com

abc

DB2

WebSphere

def

Apache

DB2

south.abc.com

Tomcat

ghi

Domino

WebSphere

Figure 2-8 Service instance hierarchy

2.4 Services Manager or Systems Manager
This section compares Tivoli Business Service Manager V4.1 against the
functionality in Tivoli Business Systems Manager V3.1. Because the products
are derived from different sources, they have completely different concepts and
functionality. This section provides a generic comparison of these products.

Both Tivoli Business Systems Manager V3.1 and Tivoli Business Service
Manager V4.1 provide a generic tree interface for providing the status of a
business context entity as reflected from a set of conditions based on IT
resources. These business entities can be used for operational monitoring or
service level measurement.


2.4.1 Terminologies
This section provides a summary of terminologies translation. The translation is
performed loosely based on the apparent functions that they provide. The
definitions that we provide here are for comparing the functionality of the
products, not a formal translation.
Physical resource SCM resource
Only resources from the Discovery Library adapter would
appear in this tree. This is the closest that Tivoli Business
Service Manager V4.1 has regarding physical resources.
For service instances defined directly from auto
population rules based on events, there is no concept of
physical resources.
Resource Service instance
There is no concept of physical resources in Tivoli
Business Service Manager V4.1. All definitions are
related to business system resources and business
system folder. There is no distinction between them.
Class Service template
This is a loosely related definition of the class object to be
the template for the instances. The classes in Tivoli
Business Systems Manager V3.1 are formally related to
physical resource type, however the service template
defines the hierarchy of the business system tree. The
business system tree is not structured rigidly, but the
service tree hierarchy is defined by the template structure.
The same resource can appear in different tree branches,
but this might require a different template being defined.
Alerts and messages Events
There is no distinction on the types of events nor its
source in terms of processing. All events are treated
equally from Netcool/OMNIbus or an external data
calculation.
Child event Numerical rules
The events are not propagated based on the incoming
events, such as in Tivoli Business Systems Manager
V3.1. The status of aggregate objects or containers are
calculated based on the numerical rules from the children
status.
Event enablement Tivoli EIF probe
The event enablement interface allows events to be
retrieved from the Tivoli Enterprise console. The function


is performed by the Tivoli EIF probe. There is no
comparable function for common listener, because it can
perform both topology discovery and alerting functions.
The discovery must be ported to the Discovery Library
adapter, while a new probe might be needed to receive its
events.

There are some functions in Tivoli Business Systems Manager V3.1 that have no
comparable functions in Tivoli Business Service Manager V4.1. They are just
inherently not needed. Some of them are:
Business systems building tools
Business systems building tools, such as Automated Business Systems
(ABS) or XML interface, are not needed as the service instance structure
must be predefined using service templates. The templates define the
structure of the discovered instances and also determine the containment
hierarchy of the instances. The ESDA interface can be used to accommodate
service instance hierarchy that is totally dynamic based on external relational
data for both placement and status.
Critical resource list
There is no critical resources list in Tivoli Business Service Manager V4.1.
Custom views can be created for operators that provide quick access to
critical resources for the operator.
Executive dashboard
Because the Web interface is very adaptable and versatile, custom views can
be created to accommodate the executive dashboard function. There is only a
single Web console for Tivoli Business Service Manager V4.1, as opposed to
the three options for accessing Tivoli Business Systems Manager V3.1 from a
Java console, Web console, or executive dashboard (or four options with the
reporting system).

2.4.2 Function differences
Detailed function comparison between Tivoli Business Systems Manager V3.1
and Tivoli Business Service Manager V4.1 is listed in Table 2-2. The prerequisite
column indicates what other component or product is needed to provide the
listed function in Tivoli Business Service Manager V4.1. Products marked with an
* are included as part of the Tivoli Business Service Manager V4.1 distribution.

Table 2-2 Function comparison
Function V3.1 V4.1 Prerequisite

Discovery of Distributed Resources using Events X X



Discovery of Distributed Resources using TADDM X X

Discovery of Distributed Resources using Discovery X X
Library adapters

Discovery of Distributed Resources using Data Fetcher X
(query)

Discovery of z/OS Resources using Events X X

Discovery of z/OS Resources using TADDM X

Discovery of z/OS Resources using batch process X

Discovery of z/OS Resources using Discovery Library X
adapters

Discovery of z/OS Resources using Data Fetcher X
(query)

Automatic Business System Rules (ABS) X

Automatic Business Service Population X
(Auto-Population Rules, DataFetcher, ESDA,
Composite Objects using Discovery)

Resource and Business System Creation (import file) X X

Resource and Business System Creation (manually X X
from console)

Dynamic Resource and Business System Creation from X
External Data Source (using ESDA)

Event Management Infrastructure/Event Respository X
- Internal database structure

Event Management Infrastructure/Event Respository X Netcool OMNIbus*
- OMNIbus provides the Event Management
Infrastructure

Counter Based Status Propagation (Threshold) X X
- Defined at Object Level in v3.1
- Defined at event rule level in v4.1

Percentage Based Status Propagation X X

Worst Case Status Propagation X X

Java Console X



Web Console X X

Executive Dashboard X X

Visualization - Console consolidation point X X

Visualization - Custom workspace per user X X

Visualization - Canvas View Definitions (view X X
customization)

Visualization - All Resource View X

Visualization - Business System View X X
- Service Navigation Panel in V4.1

Visualization - Tree View X X
- Service Navigation Panel in V4.1

Visualization - Service Navigator Scorecard X

Visualization - Topology View X X
- Service Viewer in V4.1

Visualization - Event Detail View X X
- Service Affecting Events View and Active Event List in
V4.1

Visualization - Events Summary Panel X

Visualization - HyperView X

Visualization - Table View X

Visualization - Business Impact View X X
- Service Viewer in V4.1

Visualization - z/OS Systems Specific Views - CICS®, X
IMS™, DB2®, Batch

Visualization -GIS Map-based View X

Active Metric Retrieval from External Data Sources X

Numerical Formula Based Calculations (for status & X
metrics)

Role-based User Authentication and Authorization X X Netcool Security
Manager*

Right-Click Task Integration from Business Service X X
- URL Launch only for V4.1



Right-Click Task Integration from event X X Netcool OMNIbus*
Netcool Webtop AEL*

Tivoli Management Framework Integration X

NetView® for z/OS Command Integration X

System Automation for z/OS Command Integration X

Policy Based Actions (clear events, send email, execute X X
external commands, scripts and applications, and so
on)

Alert Workflow X X Netcool Webtop AEL*

Historical Reporting X

Problem Ticket Interface X

Self-Management (Health Monitor) X X

Maintenance Mode Support X X

Real-time SLA Integration X
- Configure real-time SLA against defined business
services

Historical SLA Integration X X Tivoli Service Level
Advisor

Failover X X Netcool OMNIbus*
Netcool OMNIbus
ObjectServer Gateway


3

Chapter 3. Installation and migration
consideration for Tivoli
Business Service Manager
V4.1
This chapter documents our experiences in installing and migrating to Tivoli
Business Service Manager V4.1. The discussion consists of:
3.1, “Installation process overview” on page 26
3.2, “Installation planning considerations” on page 27
3.3, “Typical full installation” on page 27
3.4, “Migration process” on page 33


3.1 Installation process overview
The installation process of the Tivoli Business Service Manager V4.1 lays out the
necessary components of the installation, including:
Netcool OMNIbus
Netcool License Server
Netcool Security Server
Tivoli Business Service Manager server application, including Netcool
Webtop, embedded Netcool Impact, and Netcool GUI Foundation

The installation is performed from a DVD disk or a disk image. The image
contains all the components’ installation images. There are two installation
options:
The typical installation method installs all the required components on a
single machine.
The custom installation method provides more installation options and allows
you to choose which required components to install.

Additionally you can install additional components such as the TEC event
adapter probe and the Discovery Library toolkit (XML toolkit). These components
are installed using separate installation wizards.

Figure 3-1 shows the installation DVD image directory structure.

Figure 3-1 DVD image structure


As shown in Figure 3-1 on page 26, the DVD image contains the installation
wizard for all the components.

The installation also gives the option of performing migration. Migration is only
supported from Netcool Real-time Active Dashboard V3.0. We discuss migration
in 3.4, “Migration process” on page 33.

3.2 Installation planning considerations
Before you start installing, the following are the important prerequisites:
Processor Two or more CPUs with minimum 1 GHz SPARC or 2 GHz
Intel® speed
Memory 2 GB minimum RAM, with 4 GB preferred
Disk space 40 GB local disk space
Operating system The supported platforms are:
Sun Solaris™ 9 and 10
IBM AIX® 5L™ 5.2 and 5.3
Red Hat Enterprise Linux ES 3.0, 4.0, and 5.0
Microsoft® Windows 2003 Server and Windows XP
Web browser Microsoft Internet Explorer® 6.x or Mozilla Firefox 1.5x

The installation of Tivoli Business Service Manager must be performed by a user
ID other than root or Administrator. You can define the user ID using:
Computer Management application in Windows, go to Local users and
groups → Users and select Add.
The command smitty user in AIX would take you to user administration
functions.
The command adduser in Linux would add a user and its associated
attributes.

3.3 Typical full installation
This section provides a screen-by-screen typical full installation of the required
Tivoli Business Service Manager components. This installation type is suitable
for a small scale environment or a demonstration system. You can consult the
IBM Tivoli Business Services Manager V4.1 Installation Guide, Gl11-8054 for
more information on the options and other types of installations.

Chapter 3. Installation and migration consideration for Tivoli Business Service Manager V4.1 27

Installation is started from the launch pad. You must start this using a non-root
user ID. The launch pad is started automatically when the DVD is inserted;
otherwise you can invoke the launchpad using the launchpad or ./launchpad.sh
commands. The launchpad window is shown in Figure 3-2.

Figure 3-2 Tivoli Business Service Manager launchpad

From the launch pad in Figure 3-2, click Install IBM Tivoli Business Service
Manager V4.1 link, and start the installation wizard. You can use the default
options for the installation. The installation options window on a Linux platform
are shown in Figure 3-3 on page 29. It basically requires only the home directory
of where to install the product. The default directory in Linux is /opt/IBM/Netcool.
This directory would be called $NCHOME.


Figure 3-3 Installation options for simple install in Linux

Figure 3-4 shows the list of products and options for this installation.

Figure 3-4 The installation summary window


After the install, Tivoli Business Service Manager processes are started
automatically, and the default service templates are defined. If Tivoli Business
Service Manager is not started you can start it using the sequence shown in
Figure 3-5.

[TBSMadmin@tbsmsrv ~]$ $NCHOME/InstallTBSM/bin/start_licsvr.sh
Running: /opt/IBM/Netcool/license/bin/nc_start_license &
Number of License Server processes found = 2
License Server is running, continue...

[TBSMadmin@tbsmsrv ~]$ $NCHOME/InstallTBSM/bin/start_secmgr.sh
Running: /opt/IBM/Netcool/security/bin/ncsm_server &
Starting Server ...
Logging to file: log/SM_server.log
... Server Started.
Number of Security Manager processes found = 2
Security Manager is running, continue...

[TBSMadmin@tbsmsrv ~]$ $NCHOME/InstallTBSM/bin/start_omni.sh NCOMS
Running: /opt/IBM/Netcool/omnibus/bin/nco_objserv -name NCOMS &
Netcool/OMNIbus Object Server - Version 7.1
Copyright (C) 1994 - 2005, Micromuse Ltd. All rights reserved.
Server 'NCOMS' initialised - entering RUN state.
Number of ObjectServer processes found = 1
ObjectServer is running, continue...

[TBSMadmin@tbsmsrv ~]$ $NCHOME/InstallTBSM/bin/start_tbsm.sh
Running: /opt/IBM/Netcool/bin/rad_server &
JAVA_HOME is /opt/IBM/Netcool/platform/linux2x86/jre_1.5.0
JAVA_OPTS is -Dnchome=/opt/IBM/Netcool -Dngfhome=/opt/IBM/Netcool/guifoundation
. . .
Starting IBM Tivoli Business Service Manager Server process...

Figure 3-5 Starting Tivoli Business Service Manager processes

You can verify that processes are running as shown in Figure 3-6 on page 31.

Using the ps -ef command. It shows the following processes:
Netcool GUI Foundation Adaptive Server Anywhere database
Tivoli Business Service Manager progreSQL database processes
License manager processes
Security manager processes
Netcool OMNIbus object server
Netcool GUI Foundation Tivoli Business Service Manager server


5738 1 /opt/IBM/Netcool/guifoundation/asa/unix/dbsrv9 -o /opt/IBM/Netcool/guifoundatio
5957 1 /opt/IBM/Netcool/platform/linux2x86/pgsql8/bin/postmaster -B 35 -N 15 -i
5960 5957 postgres: writer process
5961 5957 postgres: stats buffer process
5962 5961 postgres: stats collector process
6088 1 /opt/IBM/Netcool/license/platform/linux2x86/bin/lmgrd -c $NCHOME/license/etc/
6089 6088 netcool -T tbsmsrv 9.2 3 -c /opt/IBM/Netcool/license/etc/ --lmgrd_start
6099 1 /bin/sh /opt/IBM/Netcool/security/bin/ncsm_server
6107 6099 /opt/IBM/Netcool/platform/linux2x86/jre_1.4.2/bin/java -Dapp=SM_ncsm_server
6161 1 /opt/IBM/Netcool/omnibus/platform/linux2x86/bin/nco_objserv -name NCOMS
6203 1 /opt/IBM/Netcool/platform/linux2x86/jre_1.5.0/bin/java -Dnchome=/opt/IBM/Netcool

Figure 3-6 Checking Tivoli Business Service Manager processes

You can get into the Tivoli Business Service Manager console using a Web
browser to connect to port 8080 of your machine. The default user ID is admin
with the password netcool. Figure 3-7 shows the login panel.

Figure 3-7 Login to Tivoli Business Service Manager


Inside the Tivoli Business Service Manager interface, you can see the predefined
service templates using the Service Administration desktop. The templates are
shown in the Service Component Repository tree. These templates are defined
from the $NCHOME/guifoundation/webapps/sla/install/BSM_Templates.radsh
file. If you are using an Advanced installation and want to load the templates, you
can run the $NCHOME/bin/rad_radshell and pipe the radsh file to the command.
Figure 3-8 shows the service templates definition.

Figure 3-8 Service templates

This concludes our installation discussion. The migration process in 3.4,
“Migration process” on page 33 should be run only if you have an existing
Netcool Real-time Active Dashboard (RAD) V3.0.


3.4 Migration process
The migration process of Netcool RAD V3.0 is not an inplace migration. You
would transfer Netcool RAD V3.0 templates and definitions into a freshly installed
custom installation of Tivoli Business Service Manager V4.1 and reapply the
configuration.

Note: Although the migration tools create and define all templates, rules, and
objects from inside RAD 3.0 definitions; some manual intervention might be
needed. The manual actions would be required for items that are manually
changed, such as custom canvasses, impact policies, and other files that are
edited in RAD 3.0.

Before you migrate to a Tivoli Business Service Manager environment, you must
also consider the migration path that you would take for all components of Tivoli
Business Service Manager. See Table 3-1 for migration consideration.

Table 3-1 Migrating Tivoli Business Service Manager components
Components Inplace Data Comments
migration migration

Netcool OMNIbus Yes Yes

License Server Yes Yes

Security Server Yes Yes

Netcool Webtop N/A Yes Has to be migrated

Netcool GUI N/A Yes Has to be migrated
Foundation


The migration process is illustrated in Figure 3-9.

RAD 3.0 environment TBSM 4.1 environment

License Server License Server

Security Server Security Server

OMNIbus OMNIbus

RAD 3.0 TBSM 4.1

Figure 3-9 Migration process

The migration process would be:
1. Install a new custom installed Tivoli Business Service Manager server (or
servers) according to the desired configuration. You may preserve the options
that you have for the existing Netcool RAD environment, such as a separate
OMNIbus or failover implementation. The Tivoli Business Service Manager
installation type must be custom. The custom installation does not create the
default service templates.
2. Migrate prerequisite software if needed, or prepare for inplace migration.
Actions include:
– Expand the existing OMNIbus schema for Tivoli Business Service
Manager V4.1 processing or apply schema modifications from the existing
OMNIbus.
– Add new Tivoli Business Service Manager V4.1 licenses to the existing
license server, or migrate other Netcool licenses to the new license server.
– Use existing security, or migrate security manager user ID and groups.
3. Stop Netcool RAD processing, by disabling probes to the OMNIbus. Generate
an export file for Tivoli Business Service Manager definitions.
4. Apply migrated Netcool RAD definitions into an empty Tivoli Business Service
Manager system.


5. Perform manual changes for additional Tivoli Business Service Manager
features.

3.4.1 License server considerations
License server uses license files stored under the etc sub-directory of the
installation path. If you decided to use a new license server, all license files from
the old license server located under $NCHOME/license/etc must be copied over.
For using an existing license server, you must make sure that Tivoli Business
Service Manager license files are there:
netcool_omni_anyhost_keys.lic
netcool_tbsm_anyhost_keys.lic

3.4.2 Security manager considerations
Existing security manager users and groups can readily be used for the new
installation of Tivoli Business Service Manager. No additional tasks are required
to use an existing security manager.

However, if you decide to use a new security manager installation, you must
restore all the users and groups definitions. The migration utility preserves the
object IDs of the Tivoli Business Service Manager objects, therefore all
authorization definitions are preserved. The simplest way to transfer over the
security manager definition is by restoring a backup copy of the security manager
database.
For UNIX and Linux platforms, you can run the ncsm_db command to backup
and restore the database.
For Windows platform, you must copy the database inside
%NCHOME%securitydbsecurity.script while the security server is stopped.

3.4.3 Netcool OMNIbus considerations
The OMNIbus migration is the most complex migration process because it is the
heart of the event processing mechanism. Tivoli Business Service Manager only
supports OMNIbus V3.6 or V7. The OMNIbus installed with Tivoli Business
Service Manager is version 7.

You can reuse an existing OMNIbus or migrate an existing OMNIbus to a new
installation.


Usage of existing OMNIbus
For an existing OMNIbus, an additional Tivoli Business Service Manager 4.1 data
model must be supplied to make it functional. The Tivoli Business Service
Manager V4.1 data model update for OMNIbus is located in
$NCHOME/InstallTBSM/sql/tbsm_db_update.sql. This SQL file must be run
against the existing OMNIbus database.

To run the SQL file into OMNIbus database, invoke the isql command
(Windows) or nco_sql command (UNIX/Linux), and pipe the SQL file into it. The
command would be similar to:
$NCHOME/omnibus/bin/nco_sql -S NCOMS -U root -P password

or
%NCHOME%omnibusbinisql.bat –S NCOMS –U Administrator –P password

Migrate to a new OMNIbus
If you want to move your existing OMNIbus to a new OMNIbus, you must decide
whether you want to have the event data preserved or you want to build the
events over time. The event data migration is only supported over the same
OMNIbus version running on the same platform.

If you do not want to move the event data, you can just apply any schema
changes from your existing OMNIbus into your new OMNIbus using either the
isql or nco_sql commands. Using the same interface, you can also perform
backup of your OMNIbus database. You backup the OMNIbus database using
the ALTER SYSTEM BACKUP command as shown in Figure 3-10.

[TBSMadmin@tbsmsrv omnibus]$ ./bin/nco_sql -S NCOMS -U root
Password:
1> ALTER SYSTEM BACKUP '/home/TBSMadmin/OMNIbackup'
2> go
(0 rows affected)
1> exit
[TBSMadmin@tbsmsrv omnibus]$ ls /home/TBSMadmin/OMNIbackup/
master_store.tab table_store.tab
Figure 3-10 Backup OMNIbus database

The database files (*.tab) will be stored on the directory that you choose. You can
copy these files into the new OMNIbus while it is not running. The OMNIbus
database called NCOMS is stored in $NCHOME/omnibus/db/NCOMS.


After the OMNIbus database is restored, you must update the Tivoli Business
Service Manager V4.1 data model from
$NCHOME/InstallTBSM/sql/tbsm_db_update.sql similar to “Usage of existing
OMNIbus” on page 36. Furthermore, you must also run the following SQL
command using the interactive SQL prompt:
“UPDATE alerts.status SET RAD_FilterIDList = ’’, RAD_RawInputLastValue = 6;”

3.4.4 Migrating Tivoli Business Service Manager data
The migration of Tivoli Business Service Manager data can be performed using
the migration wizard or manually using the RAD shell command line interface.
The service objects and templates are recreated preserving its object ID. The
migration utility only supports automatic migration for UNIX to UNIX or Windows
to Windows platforms.

Note: Because the object ID is preserved, this would assume that the target
Tivoli Business Service Manager database is empty. If you already have the
templates defined, the migration process would fail.

Before running the migration tool, the following must be performed in the RAD
3.0 system:
Install RAD 3.0 Fix Pack 1. The patch package is called
3.0.0-TIV-RAD-FP0001. It can be downloaded from:
http://www-1.ibm.com/support/docview.wss?rs=0&q1=RAD+3.0+Fix+Pack&ui
d=swg24014299&loc=en_US&cs=utf-8&cc=us&lang=en2
Modify some files in the RAD 3.0 from the installation DVD:
web.xml copy $platform/TBSM/migration/web.xml to
$NCHOME/guifoundation/webapps/sla/WEB-INF/web.
xml
ncs200*.jar remove existing ncs200*.jar from
$NCHOME/guifoundation/webapps/sla/WEB-INF/lib;
and copy $platform/TBSM/migration/ncs200*.jar to
$NCHOME/guifoundation/webapps/sla/WEB-INF/lib
ncsSoapClient200*.jar remove existing ncsSoapClient200*.jar from
$NCHOME/guifoundation/webapps/sla/WEB-INF/lib;
and copy
$platform/TBSM/migration/ncsSoapClient200*.jar to
$NCHOME/guifoundation/webapps/sla/WEB-INF/lib

The migration wizard windows are shown in Figure 3-11 on page 38.


Figure 3-11 Migration wizard

The migration wizard performs the following steps:
1. Invoking rad_radshell for command line access to Tivoli Business Service
Manager. This is performed from the Tivoli Business Service Manager V4.1
server.
2. Running the radshell command exportForMigration(host, port) that is
targeted to the RAD 3.0 host and port. This would invoke SOAP access to the
RAD 3.0 server. This creates export.radsh script under
$NCHOME/guifoundation/webapps/sla.
3. Piping the export.radsh file into the rad_radshell command. This creates the
objects while preserving the object IDs.
4. Copying files using the radshell command getfile(radhost, radport,
radNCHOME, tbsmNCHOME, path, user, password). Additions to these files are


applied to the new files in the Tivoli Business Service Manager V4.1 server.
The files are:
– Maintenance schedule:
$NCHOME/guifoundation/webapps/sla/xml/scheduleTime.xml
– Custom view definitions and custom service tree:
$NCHOME/guifoundation/webapps/sla/av/xmlconfig
– Custom static view: $NCHOME/guifoundation/webapps/sla/av/canvas
– Custom dashboard changes:
$NCHOME/guifoundation/webapps/sla/dashboard/chartconfig and
$NCHOME/guifoundation/webapps/sla/dashboard/chartcss

3.4.5 Manual modifications required
There are several manual modifications that must be performed:
Custom actions, modified service tree, or view definition in
$NCHOME/guifoundation/webapps/sla/av/xmlconfig must be reapplied
manually.
Netcool GUI Foundation configuration changes, including changes in Webtop
must be applied manually:
a. Export configuration changes from RAD 3.0 Web console’s Administration
window. In the Layout tab, expand the pages list and select the modified
pages. For each page, click the export button and specify an output file.

Figure 3-12 Netcool GUI Foundation pages list


b. From the Tivoli Business Service Manager V4.1 Web console’s
Administration window, Layout tab, select the pages list. Click the Import
button to indicate the source files as exported from step a. Figure 3-13
shows the import page.

Figure 3-13 Import window

Icon files must be migrated from:
– $NCHOME%/guifoundation/webapps/sla/icons
– $NCHOME%/guifoundation/webapps/sla/icons/svg
Property files migration from:
– $NCHOME/etc/rad/RAD_av.props
– $NCHOME/etc/rad/RAD_chart.props
– $NCHOME/etc/rad/RAD_server.props
– $NCHOME/etc/rad/RAD_sla.props


4

Chapter 4. Working with Discovery
Library toolkit
This chapter discusses Discovery Library toolkit. This toolkit provides integration
to CCMDB and z/OS discovery process. The discussion consists of:
4.1, “Introduction Discovery Library toolkit” on page 42
4.2, “Installation of the Discovery Library toolkit” on page 43
4.3, “IBM Tivoli Discovery Library Adapter for z/OS” on page 51
4.4, “Tivoli Application Dependency Discovery Manager” on page 62


4.1 Introduction Discovery Library toolkit
This section provides an overview of the Discovery Library toolkit. The Discovery
Library toolkit is an optional component of Tivoli Business Service Manager that
has the ability to access data using Tivoli Application Dependency Discovery
Manager API or reading Discovery Library books. The Discovery Library toolkit
can only accept data from one of these sources at any one time based on its
configuration.

Figure 4-1 shows the Discovery Library toolkit architecture with Tivoli Business
Service Manager.

TBSM 4.1 server
IBM Tivoli Application
Dependency Discovery TBSM Service
Manager templates objects

TADDM
API
Bulk load
`
ESDA

TBSM database
Discovery Library
Books read
XML toolkit
(files) Discovery Library Reader
SCR tables

Figure 4-1 Discovery Library toolkit architecture

The Discovery Library toolkit acts as a Windows service or UNIX daemon that
monitors the data source and adds data to the Service Component Registry
(SCR) tables. Tivoli Business Service Manager uses ESDA rule to query these
tables and build the service object hierarchy based on these tables.

Discovery library books are idML files that are created by Discovery Library
adapter (DLA) programs. There are various IBM DLAs output that are supported
by Tivoli Business Service Manager V4.1, including:
IBM Tivoli Monitoring Services
IBM Tivoli Discovery Library Adapter for z/OS
IBM Tivoli Composite Application Manager for SOA
IBM Tivoli NetView for z/OS


Discovery Library books from the DLAs can be either loaded directly in Tivoli
Business Service Manager 4.1 or can be loaded into Tivoli Application
Dependency Discovery Manager into the Configuration Manager Database
(CMDB). We recommend that if Tivoli Application Dependency Discovery
Manager is deployed, the DLAs should be loaded into Tivoli Application
Dependency Discovery Manager and then imported to Tivoli Business Service
Manager 4.1 using the Tivoli Application Dependency Discovery Manager API.

More information about the DLAs can be found on the IBM OPAL website at
http://catalog.lotus.com/wps/portal/tccmd. Generally Tivoli Business
Service Manager 4.1 supports all DLAs that conform to version 2.3 of the
Common Data Model (CDM) specifications. The processing of Discovery Library
books by Tivoli Business Service Manager 4.1 are similar for all Discovery
Library adapters.

This chapter discusses:
4.2, “Installation of the Discovery Library toolkit” on page 43 which shows the
installation and verification of the Discovery Library toolkit.
4.3, “IBM Tivoli Discovery Library Adapter for z/OS” on page 51.
4.4, “Tivoli Application Dependency Discovery Manager” on page 62 which
discusses the integration with IBM Tivoli Application Dependency Discovery
Manager.

4.2 Installation of the Discovery Library toolkit
This section discusses the installation of the Discovery Library toolkit. We are
installing on Windows 2003 server and installing to read Discovery Library books.
The installation of the Discovery Library toolkit must be performed on the Tivoli
Business Service Manager 4.1 server. The install media we use is on a mapped
drive and the install is performed using the Launchpad.exe found in the root
directory of the install media.
1. Open the Launchpad as shown in Figure 4-2 on page 44 and select the
Install Discovery Library. From the Install Discovery Library Support panel,
click Run the Discovery Library Installation program link.

Chapter 4. Working with Discovery Library toolkit 43

Figure 4-2 Launchpad for Discovery Library support

2. Figure 4-3 shows the Welcome window. Click Next.

Figure 4-3 Welcome to the InstallShield window


3. The license agreement panel is launched.
4. Figure 4-4 shows the installation target directory. Although the panel suggests
that you can change this installation directory, you should not change this.
The toolkit uses $NCHOME location to get the JDBC driver for the
PostgreSQL database. The directory will default to the
$NCHOME/XMLToolkit. Click Next.

Figure 4-4 Installation directory window

5. Figure 4-5 shows the Tivoli Business Service Manager connection
information window. The Discovery Library toolkit connects to the Tivoli
Business Service Manager using SOAP connection from the information in
this window. Click Next after filling in the values.

Note: The userid and password are not validated during the install. The
default userid and password on the Tivoli Business Service Manager 4.1
install is admin and netcool.

Figure 4-5 HTTP information panel

6. Figure 4-6 on page 46 shows the window for configuring the Discovery
Library toolkit data source. We selected Discovery Library books. This setting
can be modified after the install by updating the
$NCHOME/XMLToolkit/bib/xmltoolkitsvc.properties file. The userid and


password must be entered for access to the Tivoli Business Service Manager
PostgreSQL database. Click Next.

Note: The PostgreSQL userid is not validated during the install.

Figure 4-6 Data source for toolkit and database user information

7. Figure 4-7 on page 47 shows the postgreSQL connection information. All of
the values are populated with the defaults. We accept all the default values.
Click Next.


Figure 4-7 Database connection information

8. Figure 4-8 prompts for the location of the Discovery Library books. This
directory is the location where the books will be read. This directory can be
modified to any directory accessible to the Tivoli Business Service Manager
server. The default is $NCHOME/discovery/dlbooks. Click Next.

Figure 4-8 Discovery Library books directory

9. Figure 4-9 on page 48 shows the summary of the installation. Click Next.


Ibm tivoli business service manager v4.1 redp4288

Ibm tivoli business service manager v4.1 redp4288

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (15)

Andere mochten auch

Andere mochten auch (9)

Ähnlich wie Ibm tivoli business service manager v4.1 redp4288

Ähnlich wie Ibm tivoli business service manager v4.1 redp4288 (20)

Mehr von Banking at Ho Chi Minh city

Mehr von Banking at Ho Chi Minh city (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Ibm tivoli business service manager v4.1 redp4288