version 6.2.0 business service manager - ibm...provides reference information about the optional...

Business Service ManagerVersion 6.2.0

Exploring TBSM

IBM

SC27-8785-02

Note

Before using this information and the product it supports, read the information in Appendix A,“Notices,” on page 73.

Edition notice

This edition applies to IBM® Tivoli Business Service Manager Version 6 Release 2.0 and to all subsequent releases andmodifications until otherwise indicated in new editions.© Copyright International Business Machines Corporation 2008, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

Contents

Chapter 1. About this publication...........................................................................1Audience.......................................................................................................................................................1Publications..................................................................................................................................................1

TBSM library........................................................................................................................................... 1Prerequisite publications....................................................................................................................... 1Related publications...............................................................................................................................2Accessing terminology online................................................................................................................ 2Accessing publications online................................................................................................................2Ordering publications ............................................................................................................................ 3

Accessibility................................................................................................................................................. 3Tivoli technical training................................................................................................................................3Support information.....................................................................................................................................3Conventions used in this publication ..........................................................................................................3

Typeface conventions ............................................................................................................................3

Chapter 2. Introduction to IBM Tivoli Business Service Manager............................. 5

Chapter 3. What's new in TBSM Version 6.2.0 ........................................................ 7

Chapter 4. Technical overview of TBSM................................................................ 11TBSM architecture..................................................................................................................................... 11TBSM components.....................................................................................................................................11Integrated applications............................................................................................................................. 13Operating system variables and paths......................................................................................................15Java support...............................................................................................................................................16

Chapter 5. Planning............................................................................................. 17Charting web service considerations........................................................................................................ 17System requirements................................................................................................................................ 17Installing prerequisite software................................................................................................................ 18TBSM installation user...............................................................................................................................18Failover considerations..............................................................................................................................19IBM Tivoli Netcool Impact Considerations............................................................................................... 19IBM Tivoli Netcool OMNIbus Considerations........................................................................................... 19User registry considerations......................................................................................................................21

Dashboard server LDAP configuration.................................................................................................23Data server LDAP configuration .......................................................................................................... 23Netcool/OMNIbus user registry........................................................................................................... 23Use Netcool/OMNIBus to access LDAP server....................................................................................23Multiple user registry warnings............................................................................................................23TBSM users, user groups, and roles.................................................................................................... 24

Chapter 6. Installing TBSM.................................................................................. 27Installation types....................................................................................................................................... 27Installation order....................................................................................................................................... 27Installing TBSM interactively.....................................................................................................................27

Installing the Database Configuration Utility...................................................................................... 27Installing the Data Server component.................................................................................................31Installing the Dashboard server component.......................................................................................43Tivoli Event Integration Facility Probe Installation............................................................................. 48

iii

Uninstalling TBSM......................................................................................................................................51Uninstalling TBSM Data Server............................................................................................................ 51Uninstalling TBSM Dashboard Server..................................................................................................51

Chapter 7. Service Model Overview...................................................................... 53

Chapter 8. TBSM service model configuration overview........................................ 551 Plan your service model......................................................................................................................... 552 Create service templates........................................................................................................................553 Create structural dependencies.............................................................................................................564 Identify data sources..............................................................................................................................565 Create incoming status and numerical rules......................................................................................... 566 Create services....................................................................................................................................... 577 Create custom service trees and views................................................................................................. 578 Create SLAs.............................................................................................................................................579 Set permissions...................................................................................................................................... 58

Chapter 9. TBSM console overview.......................................................................59

Chapter 10. Service Navigation portlet................................................................. 63Services...................................................................................................................................................... 63Templates.................................................................................................................................................. 64Service Component Repository................................................................................................................. 65Data............................................................................................................................................................ 65Data Fetcher...............................................................................................................................................66

Chapter 11. Service Editor................................................................................... 69Edit tabs..................................................................................................................................................... 69Edit tab editors...........................................................................................................................................69

Chapter 12. Charting Summary portlet................................................................. 71

Appendix A. Notices............................................................................................ 73Trademarks................................................................................................................................................ 74

Index.................................................................................................................. 75

iv

Chapter 1. About this publicationThis guide contains information how to operate, maintain, and configure the product.

AudienceThis publication is for administrators and system programmers who need to use, install, maintain, orconfigure TBSM.

PublicationsThis section lists publications in the TBSM library and related documents. The section also describes howto access Tivoli® publications online and how to order Tivoli publications.

TBSM libraryThe following documents are available in the TBSM library:

• Installation Guide, GI11-8054-10

Provides information about installing the product.

• Quick Start, GI11-8055-04

Provides overview information about TBSM.

• Exploring IBM Tivoli Business Service Manager, GI11-8056-10

Provides an overview of the product features.

• Administrator's Guide, SC23-6040-10

Provides information about managing and configuring TBSM.

• Service Configuration Guide, SC23-6041-10

Provides information on how to use the features of the product console.

• Customization Guide, SC23-6042-10

Provides information on how to customize select features of the product.

• Troubleshooting Guide, GI11-8057-10

Provides information about resolving common problems with the product.

• Release Notes,

Provides latest information about the product discovered late in the test cycle that cannot beincorporated into the other publications.

Prerequisite publicationsTo use the information in this publication effectively, you must have some prerequisite knowledge, whichyou can obtain from the publications listed here.

These publications are available on the Tivoli Netcool/OMNIbus Knowledge Center:

https://www.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/common/reference/omn_ref_PDFbooks.html

• IBM Tivoli Netcool/OMNIbus User Guide

© Copyright IBM Corp. 2008, 2019 1



Provides an overview of Netcool/OMNIbus components, as well as a description of the operator tasksrelated to event management using the desktop tools. TBSM uses Netcool/OMNIbus as its eventmanager.

• IBM Tivoli Netcool/OMNIBUS Administration Guide

Provides information about how to perform administrative tasks using the Netcool/OMNIbusAdministrator GUI, command line tools, and process control. It also contains descriptions andexamples of ObjectServer SQL syntax and automations.

• IBM Tivoli Netcool/OMNIBUS Probe and Gateway Guide

Provides information contains introductory and reference information about probes and gateways,including probe rules file syntax and gateway commands. For more information about specific probesand gateways, refer to the documentation available for each probe and gateway.

• IBM Tivoli Netcool/OMNIBUS Probe for Tivoli EIF

Provides reference information about the optional Probe for Tivoli EIF that is included with TBSM.

Related publicationsThe following documents also provide useful information and are included in the TBSM InformationCenter.

These publications are available on the IBM Tivoli Business Service Manager Knowledge Center:

https://www.ibm.com/support/knowledgecenter/SSSPFK

• IBM Tivoli Netcool/Impact Administration Guide

Provides information about installing, configuring and running Netcool/Impact and its related softwarecomponents. TBSM uses Netcool/Impact policies to parse events and other data.

• IBM Tivoli Netcool/Impact User Interface Guide

Provides information about using the Netcool/Impact user interface.

• IBM Tivoli Netcool/Impact Policy Reference Guide

Provides reference information about the Netcool/Impact Policy Language (IPL). It contains completeinformation about policy language syntax, data types, operators and functions.

• IBM Tivoli Netcool/Impact Solutions Guide

Provides information about implementing Netcool/Impact in your environment.

• IBM Tivoli Netcool/Impact DSA Reference Guide

Provides reference information about Netcool/Impact data source adaptors (DSA).

Accessing terminology onlineThe IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenientlocation. You can access the Terminology Web site at the following Web address:

http://www.ibm.com/software/globalization/terminology.

Accessing publications onlineThe format of the publications is PDF, HTML, or both.

IBM posts publications for this and all other Tivoli products, as they become available and whenever theyare updated, to the Tivoli Knowledge Center at https://www.ibm.com/support/knowledgecenter/SSSPFK

Note: If you print PDF documents on other than letter-sized paper, set the option in the File → Printwindow that allows Adobe Reader to print letter-sized pages on your local paper.

2 IBM Tivoli Business Service Manager: Exploring TBSM


http://www.ibm.com/software/globalization/terminology


Ordering publicationsAccording to e-Business strategy, IBM Publications Center no longer supports ordering publications. Thepublications are made available in electronic format to be viewed or downloaded free of charge.

For documentation related to TBSM, go to https://www.ibm.com/support/knowledgecenter/en/SSSPFK.

AccessibilityThis guide contains information how to operate, maintain, and configure the product.

Accessibility features help users with a physical disability, such as restricted mobility or limited vision, touse software products successfully. In this release, the TBSM console does not meet all accessibilityrequirements.

Tivoli technical trainingFor Tivoli technical training information, refer to the IBM developerWorks Website at https://www.ibm.com/developerworks.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBM provides the followingways for you to obtain the support you need:Online

Access the IBM Software Support site at https://www.ibm.com/support/home/.IBM Support Assistant

The IBM Support Assistant is a free local software serviceability workbench that helps you resolvequestions and problems with IBM software products. The Support Assistant provides quick access tosupport-related information and serviceability tools for problem determination. To install the SupportAssistant software, go to https://www-01.ibm.com/software/support/isa/.

Troubleshooting GuideFor more information about resolving problems, see the problem determination information for thisproduct.

Conventions used in this publicationThis publication uses several conventions for special terms and actions, operating system-dependentcommands and paths, and margin graphics.

Typeface conventionsThis publication uses the following typeface conventions:

Bold

• Lowercase commands and mixed case commands that are otherwise difficult to distinguish fromsurrounding text

• Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, listboxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs,property sheets), labels (such as Tip:, and Operating system considerations:)

• Keywords and parameters in text

Chapter 1. About this publication 3

https://www.ibm.com/support/knowledgecenter/en/SSSPFK

https://www.ibm.com/developerworks

https://www.ibm.com/developerworks

https://www.ibm.com/support/home/

https://www-01.ibm.com/software/support/isa/

Italic

• Citations (examples: titles of publications, diskettes, and CDs• Words defined in text (example: a nonswitched line is called a point-to-point line)• Emphasis of words and letters (words as words example: "Use the word that to introduce a

restrictive clause."; letters as letters example: "The LUN address must start with the letter L.")• New terms in text (except in a definition list): a view is a frame in a workspace that contains data.• Variables and values you must provide: ... where myname represents....

Monospace

• Examples and code examples• File names, programming keywords, and other elements that are difficult to distinguish from

surrounding text• Message text and prompts addressed to the user• Text that the user must type• Values for arguments or command options


Chapter 2. Introduction to IBM Tivoli BusinessService Manager

This information can help you understand IBM Tivoli Business Service Manager (TBSM), including itsbusiness value and key technologies.

TBSM delivers the real-time information that you need in order to respond to alerts effectively and in linewith business requirements, and optionally to meet service-level agreements (SLAs).

The TBSM tools enable you to build a service model that you integrate with IBM Tivoli Netcool/OMNIbusalerts or optionally with data from an SQL data source. TBSM includes optional components that let youaccess data from other IBM Tivoli applications such as IBM Tivoli Monitoring, and IBM Tivoli ApplicationDependency Discovery Manager. TBSM processes the external data based on the service model data youcreated in the TBSM database and returns a new or an updated TBSM service event to Netcool/OMNIbus.

The TBSM console provides a graphical user interface (GUI) that allows you to logically link services andbusiness requirements within the service model. The service model provides an operator with a view ofhow, second by second, an enterprise is performing at any given moment in time or how the enterprisehas performed over a given time period.


Chapter 3. What's new in TBSM Version 6.2.0This documentation applies to TBSM version 6.2.0 and all fix packs, unless indicated otherwise. TBSMVersion 6.2.0 contains support for Jazz for Service Management as the new Dashboard for TBSM andNetcool/Impact 7.1.0.

Jazz for Service Management

TBSM has been updated to use the IBM Dashboard Application Services Hub as its new UI. In order to usethese new features, you also need to have Jazz® for Service Management and the IBM DashboardApplication Services Hub installed as part of your environment.

For more information see Administration Guide > TBSM and IBM Dashboard Application Services Hub.

IBM Dashboard Application Services Hub

The IBM Dashboard Application Services Hub provides user interface and dashboard services in Jazz forService management. This new self-service dashboard capability enables you to combine a variety ofvisual widgets such as gauges, tables, charts, lists or topology views into custom dashboards using aguided work flow. These dashboards can also include management data from sources such as:

• Service status and metrics from TBSM• Third-party data from Netcool/Impact• Performance metrics from IBM Tivoli Monitoring

Mobile Support: The self-service dashboard enable you to view business dashboards on mobile devicesincluding tablets and phones. This enables access to both information technology and business dataanytime / anywhere and gives you the ability to support your customers more effectively.

New functionality in TBSM 6.2

The following functionality is new in TBSM 6.2:

• TBSM widgets and DASH sidget can communicate with each other without needing to create a separateconnection.

• Since TBSM Portlet is installed on JazzSM, all the CURI TBSM datasets are available locally without theneed for a remote connection.

• The dashboard provides the following types of widgets that can be used by custom pages to buildresponsive and interactive pages:

– Status gauge– Area chart– Bar chart– Line chart– Topology

Features modified in, or removed, from TBSM

The following features have been either modified or removed in TBSM 6.2:

• Tivoli Integrated Portal (TIP) and its components (Graphs, Custom Canvas, Service viewer Applet code,Birt charts) have been removed.

• TBSM portlets and pages throughout DASH have been ported to DASH.• TBSM has been upgraded to support the latest version of Java (JDK 1.8).• Packaging method changed from Install Anywhere to Installation Manager.


• Obsolete features and functionality (Custom Canvas, JViews, and Birt charts) have been removed.• Prerequisite stack (for example Netcool and Netcool Impact) moved from embedded to stand alone.• Impact runs in the Liberty server and DASH server runs in WAS 8.5 Service Navigation.• Custom canvases have been removed• Birt charts have been removed but COGNOS reports are available as is.

Service Editor

The following changes have been made to the Service Editor:

• Tabs have been removed and the Edit view is now the default in the Server Editor portal. The View tabhas been removed as it was based on Applet and now you can use DASH Topology widgets to create asimilar topological view of services.

• Clicking on the service now opens the corresponding Service view in the Service Editor• The Invalidate button and the button related to ESDA have been hidden by default and can be enabled if

you wish by enabling the flag defined in property file. To enable it on the screen, go to JazzSM directorywhere TBSM Deployable Artifact has been installed: ./opt/IBM/JazzSM/profile/installedApps/JazzSMNode01Cell/isc.ear/sla.war/etc/RAD_ sla.props and change the key ‘impact.esda.enable=false’value to true and restart the JazzSM Server.

• The Policy Editor communication protocol has been changed from SOAP to Rest API.• SSO between JazzSM and Impact is now a prerequisite for the TBSM Policy editor• Run functionality in the Policy Editor has been disabled.

Service Availability

The following changes have been made to Service Availabilty:

• Events/Node graphs have been implemented using Rave based on the policy.• Service Viewer has been removed because it was Applet based.

Change to TBSM Admin pages, to be within JazzSM

The following changes have been made to the TBSM admin pages to be within JazzSM:

• TBSM admin pages have been put under the catalog listing of Business Service Management.• You can create custom pages using TBSM widgets by choosing from the Business Service Management

catalog.

Changes to the use of TBSM widgets

The following changes have been made to the use of TBSM widgets:

• The pre-existing TBSM widget remains functional as it was in the earlier version.• TBSM widgets can communicate with DASH widgets. Clicking on any row on the Service Tree can render

respective topology.

What's new in Netcool/Impact

TBSM Data Server integrates with Netcool/Impact version 7 release 1.0.13. The new version includesthese enhancements:

New visualization: The new visualization include Operator View customization enhancements and UIServices provided by Jazz for Service Management. These will enable clients to link their own dataaccessed through Impact's proven data access methods with visual widgets such as gauges, tables, orlists to create dashboards.

Linked data integration: Netcool/Impact can also use the Jazz for Service Management registry servicesthat follow the Open Services for Lifecycle Collaboration (OSLC) standards.


Service Level Objective (SLO) Reporting: Enables you to establish and report on service level objectivesbased on their own measures (for example, incidents, tickets, and availability).

Consumability: Continued improvements to enhance the user experience, including MWM clusterreplication and e-mail reader enhancements.

Enhanced Web Services Integrations and Wizards: Enhances and simplifies access to web servicesdata sources.

Chapter 3. What's new in TBSM Version 6.2.0 9

Chapter 4. Technical overview of TBSMThis section contains topics about the product architecture and the main software components.

TBSM architectureThis section describes the basic architecture of the IBM Tivoli Business Service Manager (TBSM).

TBSM archictecture shows the basic architecture for TBSM. The TBSM Data server analyzes IBM Netcool/OMNIbus ObjectServer events or SQL data for matches against the incoming-status rules you configuredfor your service models. If the matching data changes the service status, the status of the TBSM servicemodel changes accordingly. When a services status changes, TBSM sends corresponding service eventsback to the ObjectServer.

You can also use data from an external database or an ObjectServer to drive custom views and charts.The Discovery Library Toolkit lets you create TBSM service objects using data from Discovery LibraryAdaptor (DLA) books or from the IBM Tivoli Application Dependency Discovery Manager.

The TBSM users and group permissions are managed by the Dashboard Application Service Hub, whichcan authenticate users internally, or use data from an external source such as an ObjectServer or LDAPserver.

TBSM componentsThis topic describes the components included on the product DVD.

The applications IBM Tivoli Netcool/Omnibus, Netcool/Omnibus WebGUI, IBM Tivoli Netcool/Impact andJazzSM/Dashboard Application Service Hub are not included on the TBSM product DVD. Theseapplications must be installed as pre-requisite products on a host that is accessible by the TBSM server.

TBSM has the following components included in the Installer package or DVD:

• TBSM Dashboard server• TBSM Data server• TBSM DBConfig• Discovery Library Toolkit

Note: In TBSM 6.2, Netcool/OMNIbus, Netcool/OMNIbus WebGUI and Netcool/Impact products are notincluded in the installer. These products are prerequisites and must be installed separately beforeinstalling TBSM.

Tivoli Netcool/OMNIbus

TBSM monitors the Tivoli Netcool/OMNIbus ObjectServer for incoming events. The ObjectServer collectsevents from probes, monitors, and other applications such as IBM Tivoli Monitoring. You use TBSM tocreate service models that respond to the data received in the incoming events. For example, theincoming event data can change the status of a service or start the tracking of a potential SLA violation. Inshort, if you can set up a probe or other application to forward data to the TBSM ObjectServer, you canuse that data to build and monitor your service models. The TBSM installation package includes Netcool/OMNIbus. If you want to use the Discovery Library toolkit, or the IBM Tivoli Event Integration Facility (EIF)probe you need version 7.1 or higher.

Note that Tivoli Netcool/OMNIbus V8.1.0.x should be installed as a pre-requisite before installing TBSM.

For more information see: IBM Tivoli Netcool/OMNIbus documentation


http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/OMNIbus

Netcool/OMNIBus Web GUI

The Web GUI is the browser console for Netcool/OMNIbus and TBSM uses Web GUI components todisplay events related to service models. The Active Event List (AEL) and Service Details portlet in TBSMare Web GUI components, and are required to be installed as part of the pre-requisite products beforeinstalling TBSM on the server where JazzSM is installed.

For more information see: IBM Tivoli Netcool/OMNIbus Considerations in the IBM Tivoli BusinessService Manager Installation Guide .

TBSM Dashboard server

The TBSM Dashboard server manages the TBSM console display. You can have multiple dashboardservers for a single data server. The dashboard server enhances the scalability, performance, andavailability of TBSM.

The TBSM Dashboard server communicates with the TBSM Data server to support the creation andvisualization of service models through connected TBSM consoles. As console users view portions of theservice model, the dashboard server will acquire and maintain status of services from the data server.

TBSM Data server

The TBSM Data server monitors the ObjectServer and external databases for data that affect the status ofthe services you configured in the TBSM console or with the RAD shell command line tool. The servercalculates the status of these services by applying rules to the external data. Your service models and therules are stored in the TBSM database.

TBSM DB2 database

The TBSM DB2® database stores all the information on the service models you created in the TBSMconsole. This data includes rules that determine how your service model changes in relation to data inexternal data sources. This database also includes tables for the metrics and markers used in the TimeWindow Analyzer and demo data. A Metric History database, which has a default name of TBSMHIST, isalso included to store the historical metric data,

Discovery Library Toolkit

The Discovery Library Toolkit enables TBSM to discovery resources and to automatically build servicemodels from Discovery Library data sources. These sources include:IBM Tivoli Application DependencyDiscovery Manager , Discovery Library books conforming to the common data model, Discovery Librarybooks containing objects for an alternate namespace, the Discovery Library toolkit API, or auto-popobjects.

Data discovered through the toolkit can be enriched through notifications sent to Impact. This enricheddata can then be used in the automatic building of the service model.

Netcool/Impact

Netcool/Impact is the automation, correlation, and integration engine for the IBM Tivoli Netcool suite ofsoftware products. You can use Netcool/Impact to automate event management tasks, to correlate eventinformation with other information in your environment, and to integrate Netcool products with a widevariety of third party systems and applications.

TBSM 6.2 does not include the Netcool/Impact as part of the Data Server. You need to install Impact7.1.0.13 prior to installing TBSM.

As a consequence of this integration, you can now take advantage of these Netcool/Impact capabilities:

• You can use Netcool/Impact services and policies to acquire, enrich, and pass data to TBSM to use forservice status determination or visualization.


• TBSM uses the same policy functions and policy language as Netcool/Impact. Javascript is supportedas a policy language in addition to IPL (Impact Policy Language).

• Event enrichment is supported as an out-of-box function. Impact policies enrich events before TBSMreads these same events for status determination and propagation.

• The Impact User Interface is installed separately as prerequisite along with Impact Server and SSOconfiguration between Dashboard Application Service Hub and Impact. This provides a common userinterface for administration of both TBSM and Impact policies and services.

• The Data server package includes a name server that enables you to access Netcool/Impact serverclusters.

For more information about Netcool/Impact, see the Tivoli Netcool/Impact publications at: Netcool/Impact Documentation.

Integrated applicationsThis section is an overview of the optional external applications you can integrate with TBSM.

The following applications either forward data to TBSM, or receive data from TBSM:

• Using the IBM Tivoli EIF probe, you can forward data from IBM Tivoli Monitoring version 6 release 1 andabove, Tivoli Enterprise Console® version 3 release 9 or later, IBM Tivoli Netview version 3 release 7 orlater.

• IBM Tivoli Application Dependency Discovery Manager version 7 release 1.2 or later• IBM Tivoli Change and Configuration Management Database (CCMDB) version 7 releases 1 and 1.1• Discovery Library Adapters including those from the following products:

– IBM Tivoli Monitoring (6.2.3 or higher is recommended)– IBM Tivoli Composite Application Manager for SOA– IBM Tivoli Composite Application Manager for WebSphere®

– IBM Tivoli Composite Application Manager for Transaction Tracking– IBM Tivoli Network Manager– IBM Tivoli NetView® for z/OS®

– IBM Tivoli Storage Productivity Center version 4, release 1.1

You can launch to or from the following applications from TBSM:

• Tivoli Monitoring 6.2 with fix pack 1 or later• Tivoli Application Dependency Discovery Manager 7.1 or later• CCMDB version 7.1 or later• Netcool/OMNIbus Web GUI component.• IBM Tivoli Network Manager IP Edition version 3 release 8• IBM Tivoli Composite Application Manager for Transactions version 7 release 1.0.2• IBM Tivoli TotalStorage Productivity Center (TPC)

Note: For launch support, the supported product versions may be more restrictive than those specifiedfor data exchange above.

Jazz for Service Management

TBSM uses Dashboard Application Service Hub as its UI component in 6.2 instead of Tivoli IntegratedPortal. In order to use these new features, you also need to have Jazz for Service Management and theIBM Dashboard Application Services Hub installed as part of your environment.

Chapter 4. Technical overview of TBSM 13

http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Impact

http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Impact

Jazz for Service Management employs a new deployment pattern and mechanism that helps youintegrate shared components such as your User Interface, Linked Data Registry, Reporting, Security, andAdministrative Services. This new mechanism helps you speed up delivery cycles for clients and simplifydeployments.

For more information see Administration Guide > TBSM and IBM Dashboard Application Services Hub.

IBM Dashboard Application Services Hub

The IBM Dashboard Application Services Hub provides user interface and dashboard services in Jazz forService management. This new self-service dashboard capability enables you to combine a variety ofvisual widgets such as gauges, tables, charts, lists or topology views into custom dashboards using aguided work flow. These dashboards can also include management data from sources such as:

• Service status and metrics from TBSM• Third-party data from Netcool/Impact• Performance metrics from IBM Tivoli Monitoring

Mobile Support: The self-service dashboard enable you to view business dashboards on mobile devicesincluding tablets and phones. This enables access to both information technology and business dataanytime / anywhere and gives you the ability to support your customers more effectively.

Tivoli Event Integration Facility (EIF) probe

You can set up the optional IBM Tivoli Event Integration Facility (EIF) probe to access the event data fromapplications such as IBM Tivoli Monitoring, Tivoli Enterprise Console, and Tivoli Netview. The probeforwards the event data to the TBSM Netcool/OMNIbus ObjectServer. You can use TBSM to create servicemodels based on the event data from the Event Pump for z/OS, Tivoli Monitoring (and Tivoli Monitoringagents), Tivoli Enterprise Console, and Tivoli NetView.

IBM Tivoli Netcool/Impact

Netcool/Impact is the automation, correlation, and integration engine for the IBM Tivoli Netcool® suite ofsoftware products. You can use Netcool/Impact to automate event management tasks, to correlate eventinformation with other information in your environment, and to integrate Netcool products with a widevariety of third party systems and applications.

You can configure Netcool/Impact to forward events to the Netcool/OMNIbus ObjectServer monitored byTBSM and use those events to update your service model. Netcool/Impact is designed for Netcooladministrators who want to enhance, customize, and extend the capabilities of the Netcool suite. Formore information, see the Netcool/Impact publications.

Change and Configuration Management Database

TBSM can launch into a Change and Configuration Management Database (CCMDB) associated with aTivoli Application Dependency Discovery Manager. If you create service models with the TBSM DiscoveryLibrary integration, these services can contain data about a Tivoli Application Dependency DiscoveryManager server. If a service contains data about a Tivoli Application Dependency Discovery Managerserver, you can launch the Tivoli Application Dependency Discovery Manager and CCMDB consoles fromthe TBSM console. Likewise, you can also launch TBSM from the Tivoli Application Dependency DiscoveryManager console.


Operating system variables and pathsOn both the Data server and the Dashboard server a script is provided that allows you to set environmentvariables for quick access to the TBSM directory structure. If you do not set the variables, you cansubstitute directories with full path names when you run commands.

You must run the script that applies to the servers that you installed. If you installed both servers on thesame system, you must run both scripts.

The locations of these setup scripts on UNIX systems are as follows:

• installdirectory/tbsm/bin/setupTBSMData.sh for the Data server• installdirectory/tbsmdash/bin/setupTBSMDash.sh for the Dashboard server

where installdirectory is the directory in which you installed the server. The default directoryis /opt/IBM/tivoli.

The syntax used to run the UNIX scripts is:

. installdirectory/tbsm/bin/setupTBSMData.sh

The locations of these setup scripts on Windows systems are as follows:

• installdirectory\tbsm\bin\setupTBSMData.bat for the Data server• installdirectory\tbsmdash\bin\setupTBSMDash.bat for the Dashboard server

where installdirectory is the directory in which you installed the server. The default directory isC:\Program Files\IBM\tivoli.

The setupTBSMDash script sets the following variables:

TBSM_HOME=/opt/IBM/tivoli/tbsmdashJAZZ_HOME=/opt/IBM/JazzSMTBSM_DASHBOARD_SERVER_HOME= /opt/IBM/JazzSM/profile/installedApps/JazzSMNode01Cell/isc.ear/sla.warDASHBOARD_PROFILE=JazzSMProfileJAVA_HOME=/opt/IBM/tivoli/tbsmdash/_jvm/jre

The setupTBSMData script sets the following variables:

TBSM_DATA_SERVER_HOME=/opt/IBM/tivoli/impact/wlp/usr/servers/TBSM/apps/TBSM.ear/TBSM_HOME=/opt/IBM/tivoli/tbsmTBSM_LIBS=/opt/IBM/tivoli/impact/lib3pHOSTNAME=<hostname of the installed server>HTTPSPORT=<https port of the Impact GUI server>HTTPPORT=<http port of the Impact GUI server>

Variables used in TBSM Publications

For many of the commands and paths specified in this publication, both the UNIX and Windowsequivalents are provided. However, in instances where only the UNIX convention has been specified,follow these directions for Windows systems.

When using the Windows command line, replace $variable with % variable% for environment variablesand replace each forward slash (/) with a backslash (\) in directory paths. The names of environmentvariables are not always the same in the Windows and UNIX environments. For example, %TEMP% inWindows environments is equivalent to $TMPDIR in UNIX environments.

Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions.

Chapter 4. Technical overview of TBSM 15

Java supportThis topic describes the Java™ runtime Environment (JRE) plug-in versions that are required for the IBMTivoli Business Service Manager user interface in a web browser.

Supported Java runtime versions: The most up-to-date information about supported hardware,software, browsers and operating systems is provided by the IBM Software Product Compatibility Reportsat:

https://www.ibm.com/software/reports/compatibility/clarity/prereqsForProduct.html

1. In the Full or partial product name: field, type Business Service and click the search button.2. From the Search Results, select Tivoli Business Service Manager.3. From the Version field, select 6.2.0.4. From Mandatory capabilities:, select Java.5. Click Submit.

Note: The Java Runtime Environment that is being used should be updated to the most recent fix level.

Important: These web browser settings are required:

• JavaScript is enabled in the browser.• Set your browser to allow pop-up windows. If you block pop-up windows, you will disable features of

TBSM that require pop-up windows.• Set your browser to accept third-party cookies.


https://www.ibm.com/software/reports/compatibility/clarity/prereqsForProduct.html

Chapter 5. PlanningThis section details preinstallation considerations, such as supported hardware, software, and operatingsystems.

Tivoli monitoring Charting web service changesThe charting Web Service was made available as of Tivoli Monitoring 6.2.2 FP2. In TBSM 4.2.1, thecharting web service was part of the TBSM installation, in TBSM 6.2.0, you install and configure the webservice on your Tivoli Monitoring Tivoli Enterprise Portal Server (TEPS).

For information on migrating your pre-existing policy-based data fetchers, see the Migration section ofthis guide.

System requirementsYour environment must meet these software requirements.

Software Product Compatibility Reports

The most up-to-date information about supported hardware, software, browsers and operating systemsis provided by the IBM Software Product Compatibility Reports at:

http://pic.dhe.ibm.com/infocenter/prodguid/v1r0/clarity/index.html

For more information about running the Software Product Compatibility Reports, see the Overview andPlanning section of the TBSM Wiki.

Preparing operating systems for installationTBSM is built on the WebSphere Application Server and you need to review information on how to preparesystem before you install TBSM.

For information on preparing your operating system, see:

http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.installation.base.doc%2Finfo%2Faes%2Fae%2Ftins_prepare.html

Tuning your operating system

TBSM is built on the WebSphere Application Server and you need to review information on how to tuneyour system before you install TBSM.

For information on tuning your operating system, see:

https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/as_ditamaps/was900_welcome_ndmp.html

Installer temp file space requirement

The TBSM requires a minimum of 500 MB of temporary space to run on all operating systems. Otherwise,the installer will fail.

Note: You must install one of the 2016 versions of Windows Server because other versions are notsupported.




https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Business%20Service%20Manager1





Installing prerequisite software

About this taskTBSM requires IBM Netcool/Impact, IBM Netcool/OMNIbus , OMNIbus WebGUI, JazzSM and IBM DB2products as prerequisites. You install the TBSM databases on the DB2 instance and specify the host, port,and user information during the TBSM installation.

Software Product Compatibility Reports:

The most up-to-date information about supported hardware, software, browsers and operating systemsis provided by the IBM Software Product Compatibility Reports at:

https://www.ibm.com/software/reports/compatibility/clarity/index.html

For more information about running the Software Product Compatibility Reports, see the Overview andPlanning section of the TBSM Wiki.


The order in which the software is installed is important. Install the software in the following order:

1. DB2 Database Configuration utility2. TBSM Data Server / Discovery Library Toolkit3. TBSM Dashboard Server

Note: If you are installing TBSM in a failover environment, see the failover information in the Configuring:post installation section of this guide.

TBSM installation user

About this task

The installation user is the person who installs products in the TBSM program suite. The installation usermust install every TBSM product as the same system user.

Note: The user installing TBSM should be the user who installed the prerequisite software.

On Windows platforms, the TBSM installation user can be any user on the system that is a member of theAdministrators group.

Restriction: You cannot install TBSM, DB2, or configure the DB2 databases for TBSM whenyou are logged in with a user id containing non-English characters. DB2 does not recognize a user id withnon-English characters, such as Russian. For example, the Windows Administrator userid on a Russianoperating system has Russian characters in the name. Typically, you do not have these problems in UNIXbecause the user names have English characters.

To install DB2, rename the user id and Administrators group to have English characters only. Log in withthe renamed Administrator user id. Install DB2 while logged in with the renamed Administrator id. Youalso need to run the TBSM Database Configuration utility with the same renamed Administrator user id.

You must use the port used for DB2.

However, to install TBSM, you must log in with a user id with English characters that is a member of theAdministrators group. The user id cannot be the renamed non-English Administrator id. You must log inwith a user id that was originally created with English characters. One example is to use the db2adminuser id that is normally created during a DB2 installation.

TBSM database user name restriction: The TBSM database does not recognize a user id containing thefollowing dash/hyphen character: "-".



https://www.ibm.com/software/reports/compatibility/clarity/index.html




Failover considerationsThere are a few additional considerations before performing the advanced installation.

• The primary and backup server must be running the same version and release of TBSM and the sameoperating system.

• Use the same non-root user ID to install TBSM on the primary and backup server to ensure that the userID and password are the same for both machines. On Windows, choose the same user ID and passwordwhen prompted for the account.

• The primary and backup TBSM installation must use the same authentication method, either LDAP orTivoli Netcool OMNIbus. The file-based authentication method is not supported for failoverconfigurations.

• If you change any of the default port values during installation, use the same values for bothinstallations.

• If you use the Netcool/OMNIbus ObjectServer for authentication and the ObjectServer is set up forfailover, you need replicate the security information in the ObjectServer bi-directional gateways asdescribed in the Configuring failover section of this guide.

For additional information about failover configuration see the Configuring: Post Installation > Configuringfailover in this guide.

Failover and ObjectServer authentication considerations

If you intend to use IBM Tivoli Netcool OMNIbus ObjectServer authentication and you intend to use theTivoli Netcool OMNIbus ObjectServer you are installing with TBSM as the authentication source, specifythis during installation.

The TBSM failover configuration procedures and scripts do not modify the authentication configuration ofTBSM nor do they arrange for replication of authentication information between the primary and backupObjectServers. If you are using ObjectServer authentication, consult the OMNIbus documentation forinformation about setting up replication of such information using the bidirectional gateway.

IBM Tivoli Netcool Impact ConsiderationsIn TBSM 6.2, Netcool/Impact 7.1.0.13 is prerequisite software and is not included in the TBSM installer.

The Netcool/Impact server that is required by TBSM must have server name TBSM for primary, orTBSM_B for secondary and cluster name TBSMCLUSTER.

IBM Tivoli Netcool OMNIbus ConsiderationsTBSM supports Tivoli® Netcool® OMNIbus version 8.1.0.5 and later. TBSM users are recommended toupgrade their TBSM's OMNIbus to its latest fix pack to continue receiving software support for problemspertaining the ObjectServer.

It is recommended for users to also upgrade the WebGUI component to the same version as the TBSMOMNIbus to maintain product synchrony.

Note: If you are installing Tivoli Netcool OMNIbus on Red Hat Enterprise Linux® AS, ES, or WS 5, you mustensure that the following files are available on your system before the installation:

• compat-libstdc++-33-3.2.3-61.i386.rpm• libXp-1.0.0-8.i386.rpm• openmotif22-2.2.3-18.i386.rpm• libXmu-1.0.2-5.i386.rpm

Chapter 5. Planning 19

• libXpm-3.5.5-3.i386.rpm• compat-libstdc++-296-2.96-138.i386.rpm

These files should be available on the installation CDs for the operating system.

Adding the TBSM schema to the Object Server

Before installing TBSM Data server, you need to add the TBSM schema and have the ObjectServerrunning before you install TBSM .

You must know the host name and port number because you will be asked to provide them when you areinstalling TBSM .

Before you install TBSM, you have to modify the Netcool OMNIbus ObjectServer schema. The commandand schema files are located in the TBSM install image in the directory:

\omnibus\schema_files

To update an existing Netcool OMNIbus ObjectServer schema for TBSM:

1. Copy the entire of the \omnibus\schema_files directory to the host where Netcool/OMNIbus isinstalled.

2. Open a command or shell window.3. Change to the directory where you copied TBSM\omnibus\schema_files.

Note: Before running the ./import_schema_ksh.sh and ./import_schema.sh scripts on UNIX inthe next step, you must ensure that the permissions set for them include execute. If they do not haveexecute permission set, run the following commands to add it now:

chmod +x import_schema_ksh.shchmod +x import_schema.sh

4. Run the import_schema command with the schema file tbsm_db_update.sql as a parameter.

On Windows, run the following command:

.\import_schema.bat %NCHOME% tbsm_db_update.sql RAD ObjectServerName user password

On UNIX, run the following command:

./import_schema.sh $NCHOME tbsm_db_update.sql RAD ObjectServerName user password

On AIX, run the following command:

./import_schema_ksh.sh $NCHOME tbsm_db_update.sql RAD ObjectServerName user password

Where:

• NCHOME is the value of the installation directory for Netcool/OMNIbus• tbsm_db_update.sql is the name and location (if needed) of the schema file to read• RAD is the schema validation string• ObjectServerName is the name of your ObjectServer• user is the user name for the ObjectServer• password is the value of the ObjectServer password

In this example, $NCHOME is /opt/ibm/netcool, ObjectServerName is NCOMS, user is root, andpassword is mypass, resulting in the following line:

./import_schema.sh /opt/ibm/netcool tbsm_db_update.sql RAD NCOMS root mypass


Note:

You may receive error messages similar to the following when running tbsm_db_update.sqlcommand:

ERROR=Object exists on line 83 of statement '----------------------------------------------------------------...', at or near 'BSM_Identity' (0 rows affected) (0 rows affected) (0 rows affected) ERROR=Object not found on line 15 of statement '----------------------------------------------------------------------...', at or near 'service_deps' (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected)

These messages can be ignored. The ObjectServer will return an error if a user tries to add a columnthat already exists, which explains the error on BSM_Identity. It will also return an error if a userdrops a table that doesn't exist, which explains the second error.

5. Run the import_schema command again, but specify ClearServiceDeps.auto as the schema fileparameter as follows:

On Windows, run the following command:

.\import_schema.bat %NCHOME% ClearServiceDeps.auto RAD ObjectServerName user password

On UNIX, run the following command:

./import_schema.sh $NCHOME ClearServiceDeps.auto RAD ObjectServerName user password

On AIX, run the following command:

./import_schema_ksh.sh $NCHOME ClearServiceDeps.auto RAD ObjectServerName user password

User registry considerationsThe configuration options you have when you set up IBM Tivoli Business Service Manager for an externaluser registry.

If you are using a Lightweight Directory Access Protocol (LDAP) product, you must select the file-basedrepository option during the installation of the Impact server and then manually configure the LDAPrepository by referring the Impact Administration guide. Also, you must configure JazzSM with LDAP userrepository manually before installing TBSM Dashboard Server..

Users and user groups in external repositories

When you use an external repository for TBSM, all the users and user groups must be unique across thelogical, federated repository in WebSphere. WebSphere provides the concept of a "Federated Repository"which is a single logical view of potentially multiple physical repositories that could all be connected to atthe same time - LDAP, OMNIBus, and file registry.

You cannot have the same user or group name in both an external repository and the internal file-basedrepository. Otherwise, the user or members of the duplicated user groups cannot access TBSM.WebSphere cannot determine the correct login if the same user ID is defined in more than one userrepository. For example, you cannot have a user ID tbsmadmin in both the file registry and also in yourNetcool/OMNIbus repository.


When a user signs in to TBSM for the first time, the system looks up the user and the users groupassignments in the external repository.

You assign user roles to an individual user or to a user group from the Dashboard Application Service Hubconsole or command-line tools. The user roles control the access privileges for each user and user group.

Manually configuring TBSM for external user repositories

For detailed information on configuring external user repositories. see the TBSM Administrator's guidehere:

Administrator's Guide > Configuring TBSM > Manually configuring TBSM for external userrepositories

Servers, failover, and external authentication

When you configure an external user registry, you need to configure the registry for each server in yourconfiguration. For example, if you manually configure an LDAP server in a failover environment, you needto configure each of these servers to use the LDAP server:

1. Primary Dashboard server2. Backup Dashboard server3. Primary Data server4. Backup Data server

Secure Sign-On and LDAP with other applications

If you configure Single Sign On between TBSM, and IBM Tivoli Change and Configuration ManagementDatabase (CCMDB) and Tivoli Monitoring, the, wasadmin user must not be an LDAP user. If thewasadmin user is in LDAP, you cannot configure the WebSphere Application Server for TBSM.

Uninstalling TBSM and the user registry

If for any reason you need to uninstall TBSM or Netcool/Impact, do not uninstall the external registry,unless you are sure no other applications need that user registry. The TBSM Data server, Dashboardserver, and Netcool/Impact servers can all use the same user registry. For example, if you use a Netcool/OMNIbus ObjectServer as your user registry for a TBSM dashboard server and Netcool/Impact, you willdisable Netcool/Impact if you uninstall the ObjectServer when you uninstall a TBSM server. Use the samecaution if you use an LDAP server as your user registry.

Managing Netcool/OMNIbus events

If you are using another user registry such as LDAP, you do not need to set up the Netcool/OMNIbusObjectServer as an external user registry to enable users to manage events. You cannot have the sameuser in two user registries, but you can add users to the ObjectServer without configuring it as an externaluser registry.

If you want to enable a user to manage ObjectServer events from Dashboard Application Service Hub, youmust create a matching user in the ObjectServer that is configured for TBSM. The user names must matchexactly in both the external user registry and in the ObjectServer. The ObjectServer user needs to haveprivileges equivalent to the default Normal user group in Netcool/OMNIbus.

For example, if you have a user named jdoe1 in your LDAP user registry and jdoe1 needs to manageObjectServer events, you also need to have a user named jdoe1 in your ObjectServer.

Use the Netcool Suite Administrator tool to create users for your ObjectServer. For more information oncreating ObjectServer users, see Using Netcool/OMNIbus Administrator to configure ObjectServers in theinformation center for your version of Netcool/OMNIbus at:.




Dashboard server LDAP configurationIf you want to use an LDAP repository, you should configure the LDAP user repository in DashboardApplication Service Hub manually and then install TBSM Dashboard server.

Data server LDAP configurationYou need to install Netcool/Impact as a Filebased user repository and then manually configure the LDAPuser repository using the available scripts before installing the TBSM Data Server.

Netcool/OMNIbus user registryIf you want to use Netcool/OMNIbusObjectServer as your external user registry, you can install it from theIBM Tivoli Business Service Manager installer. If you are familiar with the ObjectServer as a user registry,you may want to use this option.

You can configure ObjectServer as your external user registry from the TBSM installer. The installerprompts you for the ObjectServer information.

If you selected the file-based repository option during the installation, you can manually configure TBSMData and Dashboard servers to use the ObjectServer repository.

Use Netcool/OMNIBus to access LDAP serverYou can configure the Netcool/OMNIbusObjectServer to use an LDAP server as external user registry. Ifyou are familiar with using LDAP as an external repository for an ObjectServer, you may want to use thisoption.

In this configuration, you configure your TBSM data and dashboard servers to use the ObjectServer asyour user registry.

In Netcool/OMNIbus, you configure the Pluggable Authentication Module (PAM) for the LDAP server youwant to access. When the ObjectServer is configured for LDAP, TBSM has access to LDAP data through theconnection with the ObjectServer. The Websphere Application Server component of TBSM sees only asingle authentication source.

Multiple user registry warningsIt is possible to use multiple user registries for a given TBSM server, but this method can causeauthentication errors if you have the same user or user group in multiple user registries.

You can use more than one LDAP server or a combination of LDAP servers and a Netcool/OMNIbusObjectServer. If you have multiple user registries, each user registry must have a unique set of users anduser groups. The set of users and groups has to be unique across all repositories you configure for TBSM.That is, you cannot have the same user in two different user registries.

For example, if the user jdoe exists in two separate LDAP user registries (or in LDAP and an ObjectServer),the user jdoe cannot log in to TBSM or any other application installed in your Dashboard ApplicationService Hub instance.

Similarly, if you have a user group called managers in two separate user registries, users from in thisgroup cannot authenticate to TBSM. Each registry's user group needs to have a unique set of users andthese users need to be in the same registry as the user group.

Tivoli Monitoring and Change and Configuration Management Database user warning

If you set up a single user registry for TBSM, Tivoli Monitoring, and the Tivoli Change and ConfigurationManagement Database (CCMDB), do not put special users such as tbsmadmin or wasadmin in the LDAPor Netcool/OMNIbus user registries. These users need to be authenticated within the application and theapplications do not function if you put these users in an external user registry.

For example, if you have the wasadmin user in both CCMDB file-based repository and in LDAP, theWebsphere Application Server cannot authenticate the wasadmin user.


TBSM users, user groups, and rolesIBM Tivoli Business Service Manager includes predefined users and user groups. Each of these groupsassigns certain roles to members of the group.

Users and user groups

Two users, tbsmadmin and tbsmuser, are created by TBSM Dashboard Server when it is installed. Thedefault password for these users is the same as the password of the impactadmin user which wascreated as part of Netcool/Impact installation. Use these users or tbsmadmin to log in to TBSM for thefirst time. If you are installing the TBSM Data Server before installing the TBSM Dashboard Server, youneed to create the tbsmadmin user with the same password as the impactadmin user password in theexternal User repository or the ObjectServer, whichever is configured as the TBSM user repository.

Important: The default login tbsmadmin is not defined in external repositories, such as LDAP or Netcool/OMNIbus, even though this default login is created during installation when an external repository isspecified.

Users with a blank password cannot log in to the TBSM Dashboard server. The default password for theOMNIbus ObjectServer root user is null; therefore, if you want to log in as root and you haveObjectServer authority, you must specify a non-null password for the root user in the ObjectServer. Ifyou need to change the ObjectServer password, use the procedure Configuring TBSM > Changing theTBSM configuration > Changing the Netcool/OMNIbus ObjectServer password or user ID.

The TBSM users and groups are created in the repository that you select during the installation for anadvanced installation or in the Netcool/OMNIbus repository during a simple installation. For moreinformation, see the TBSM Installation Guide.

You can assign users to the following predefined groups to define their level of access and authority inTBSM:tbsmAdmins

Use this group for administrators. The roles assigned to this user group enable the group members toview and modify all TBSM objects in the graphical user interface (GUI).

tbsmUsersUse this group for users who need to view all templates that are defined in the model.

tbsmViewAllServicesUsersUse this group for users who only need to view all services that are defined in the model.

tbsmReadOnlyUse this group for users who you want to have only read-only access. By default, roles are assigned tothis group that provide view-only capabilities. Users assigned to this group are restricted to theService Availability page. These users cannot access administrative tasks.

By default, the tbsmadmin is assigned to the tbsmAdmins group and also to the WebGUINetcool_OMNIbus_Admin group. The tbsmuser is assigned to the tbsmUsers group and also to theWebGUI Netcool_OMNIbus_Users group. If you perform an advanced installation and select the fileregistry as the file repository, the tbsmadmin user is also added to the tbsmAdmins, WebGUINetcool_OMNIbus_Admin, and Netcool_OMNIbus_Users groups.

You can also manage user and group permissions for each service or service template in the TBSM GUI.For more information, see the TBSM Service Configuration Guide.

For information about changing the default service and template privileges for users and groups, seeModifying the default service and template privileges in the Administrator's Guide.

User roles

You can assign any of the following roles to users or groups. These roles specify the authority that usersor groups have to view, modify, or administer TBSM settings.


Table 1. TBSM user roles

Role Authority assigned to user or group

tbsmAdminUser Access to both the Service Availability and ServiceAdministration pages in TBSM

tbsmSLAChartViewVisible Assigned automatically by TBSM to the necessary users andgroups. This role does not display in the list roles for users andgroups. Do not assign this role manually.

tbsmViewRawEvents View ObjectServer event lists.

Note: This role is no longer used.

tbsmTemplateAdmin Add, edit, delete, or view templates.

tbsmServiceAdmin Add, edit, delete, or view services.

tbsmCreateTemplate Add, edit, or view templates.

tbsmEditTemplate Edit or view templates.

tbsmViewTemplate View templates.

tbsmCreateService Add or view services.

tbsmEditService Edit or view services.

tbsmViewService View services.

tbsmDataSourceAdmin Add, edit, delete, or view data sources.

tbsmCreateDataSource Add, edit, or view data sources.

tbsmEditDataSource Edit or view data sources.

tbsmViewDataSource View data sources.

tbsmDataFetcherAdmin Add, edit, delete, or view data fetchers.

tbsmCreateDataFetcher Add, edit, or view data fetchers.

tbsmEditDataFetcher Edit or view data fetchers.

tbsmViewDataFetcher View data fetchers.

tbsmChartAdmin Add, edit, delete, or view charts.

tbsmCreateChart Add, edit, or view charts.

tbsmEditChart Edit or view charts.

tbsmViewChart View charts.

tbsmViewDefinitionAdmin Edit or delete view definitions.

Note: The default view definitions are read-only and cannot beedited or deleted.

tbsmReadOnlyUser Access to the Service Availability page only. This role is assignedby default to the tbsmReadOnly group; users assigned to thatgroup automatically have this role.


Chapter 6. Installing TBSM

About this task

The TBSM 6.2.0 Base release package comes with IBM Installation Manager version 1.8.x. If installingTBSM 6.2.0 on an environment with IBM Installation Manager 1.9.x, please note that the TBSM 6.2.0Base release installation should be done using only the Console or Silent installers. Do not use the GUIinstaller scripts.

This section details a number of installation topics and scenarios.

Installation typesTBSM 6.2 supports only Advanced installation, this allows for the configuration of multiple servers.

You are provided with two separate installers, one for the TBSM Data Server and the other for the TBSMDashboard Server which can be installed in any sequence in different servers, provided the prerequisitesare already installed on those servers.

Installation orderThe order in which you install the TBSM components is significant.

Always install the software features in the following order:

1. Set up your database schema with the TBSM Database Configuration utility. You need an instance ofDB2 installed before you can run the Database Configuration utility.

2. Make sure that Netcool/Impact, Netcool/OMNIbus, JazzSM with DASH and WebGUI are installedbefore installing TBSM.

3. IBM Tivoli Business Service Manager Data server and Discovery Library Toolkit and IBM Tivoli BusinessService Manager Dashboard server(s).

Note: TBSM Data and Dashboard server can be installed in any sequence, provided the pre-requisitesare met. Each installer must be installed separately, one at a time.

Installing TBSM interactivelyTBSM has an installation program that you can use to install the application interactively. TBSM 6.2provides three separate installers to install the Database Configuration Utiity, TBSM Data Server, andTBSM Dashboard Server.

Installing the Database Configuration UtilityThe IBM Tivoli Business Service Manager Database Configuration utility creates the files needed toconfigure the Data Server, Metric Marker, Metric History and Demo databases for TBSM. If the schema isnot created, then TBSM will not work until the tbsm_db script has been run.

Before you begin

This procedure has the following prerequisites:

• The database configuration utility must be run on the DB2 host (DB2 v11.1 or above) to create theTBSM 6.2 database.

• The TBSM schema contains several user-defined functions (UDFs) and jar files that must reside on theDB2 host.


• The DB2 port (default 50000), host name, username and password for the instance will be required forthe TBSM Data Server install.

• If Installation Manager (IM) not installed on the DB2 host machine, it will be installed from the installerpackage as part of the install. IM installer must have been installed by the DB2 user installing thedatabase configuration utility, otherwise it will attempt to install IM when the script is run. To create theTBSM database schema during the installation, the DB2 user must have permissions to create databasetables (SYSADM or SYSCTRL). Optionally, the installer can create the configuration files, and thetbsm_db script can be run to create the tables after the installation. TBSM will not work until schema iscreated.

• Login as DB2 instance user db2inst1.• The installer must be run from a terminal window.

Procedure

1. Create a directory on DB2 host machine to download and unzip the installation media:

mkdir -p /TBSM6.2/DBConfig2. Obtain the platform specific TBSM 6.2 Database Configuration installation media (dbconf_OS.zip)

and copy it into the TBSM6.2 directory.3. Change to the media directory:

cd /TBSM6.24. Unzip the media:

unzip dbconfig_<OS>.zip -d DBConfig5. Change to the install directory:

cd /TBSM6.2/DBConfig6. Execute install_gui_dbconfig.sh.7. If an older version of Install Manager (IM) is present in the server, the packaged IM (version 1.8.8) is

installed. Once the IM upgrade is complete, IM will launch8. Click Install.9. Select Database Configuration Utility and then click Next.

10. In the Software License Agreement window, click I accept the terms in the license agreement andclick Next.

11. In the Location window, in the Installation Directory field, click Browse to change to the location ofthe install directory and click Next.

Note: The TBSM directory must have the same parent path as Impact. The install will not continue ifthe impact install is not detected.

12. In the Features to Install window, click Next.13. In the TBSM Data Server Database Configuration window, enter the required details.

Database User ID must match the user running the script (for example, db2inst1). The passwordmust be the password associated with this user. Click Next.

14. In the TBSM TWA Metric Marker DB Config Panel window, enter the required details and click Next.15. In the TBSM TWA Metric History DB Config Panel window, enter the required details and click Next.16. In the TBSM Sample Database Configuration window, enter the required details and click Next.17. In the Review Summary Information window, click Install.18. The installation progresses and takes few minutes to complete based on selections in the panels.

Upon completion click Finish. Click View Log File.

What to do next

Note for users installing TBSM XMLToolkit and APM on the same remote DB2 server


Both TBSM XMLToolkit and APM and use Java UDFs in DB2. The jar files are cataloged at the server level(not the database level). If both TBSM and APM are installing the jars with the same DB2 name, the jarinstalled last replaces the one installed first. Since the TBSM jar is a subset of the functions defined in theAPM jar, some of APM functions will be missing and APM will not be able to work.

If you run the TBSM Database Configuration Tool after APM, when it has run you must then run thefollowing script from the APM configuration tool to copy back the jars from APM back into DB2:

tbsm_db.sh -s sc -U db2inst1 -f j

If you fail to run the script, some APM functions will be missing and APM will be unable to run.

For details of the APM interim fix related to this issue, see https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/APM%20and%20XMLToolkit%20UDF%20conflict

Database Configuration Utility connection informationThis section describes the information you need when running TBSM Database configuration utility.

For each database install, you need to supply the information described in this topic. You are promptedfor the following databases information used by TBSM. The information is saved in the followingproperties files.

Data server database

This is the primary database for TBSM service configuration. The configuration information for thisdatabase is stored in the files:

<install directort>\tbsmdb\sql\tbsm_db.properties

<install directort>\tbsmdb\sql\tbsmudf_db.properties

Metric history database

The Time Window Analyzer metric history database. The configuration information for this database isstored in the file:

<install directort>\tbsmdb\sql\tbsmhist_db.properties

Database Name

The name of the database. By default, this is set to TBSM for all the databases, except for the MetricHistory database, which has a default name of TBSMHIST.

Database Hostname or IP address

The host name of the system where the DB2 is installed. By default, this is set to the host name of thelocal system.

Database Port

The database port number for DB2. The default is 50000.

Database User ID

The database user ID for DB2. This user must have permission to add and drop database tables.

Database password

Database user’s password. Confirm this in the Confirm password field.

Should the installer create the schema for this database

If you select Yes, the installer configures the tables, tablespaces, and views in your DB2 instance.

Chapter 6. Installing TBSM 29

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/APM%20and%20XMLToolkit%20UDF%20conflict



If you select No, the installer creates the configuration files for the tables, tablespaces, and views, andyou install the configuration on your DB2 instance using the tbsm_db command.

Database path

The path used to create the database. The value <default> or a null value specifies the default databasepath specified by the database manager configuration.

If you want to use multiple paths, the first path must contain the database, and the paths must beseparated by commas.

Table space configuration

Specify the 16K and 32K table space names for the database. .

Table 2. Default table space names

Database Default table space names

Data server TBSM16KTS and TBSM32KTS

Metric History THM16KTS

Buffer pool configuration

Specify the 16K and 32K (data server only) buffer pool names and sizes for the database.

Table 3. Default buffer pool names

Database Default table space names

Data server TBSM16KTS and TBSM32KTS

Metric History THM16KTS

Demo/Sample DEM16KBP

Transaction log configuration

Specify the transaction log configuration for the database. This includes the log buffer size, log file, size,number of primary logs, number of secondary logs, and the log file path. The default values will be basedon the number of services you will have. You can view the default values for medium size installations(between 5000 and 20000 services) in the response file, dbconfig-installer.properties).

If the transaction log file size is too small, an error is generated:

SQL0964C the transaction log for the database is full. SQLSTATE=57011

This error is displayed in the TBSM trace log file or the Discovery Library Toolkit log. To update thetransaction log size to an appropriate value, open the DB2 command window using the db2cmd commandand execute the command:

UPDATE DATABASE CONFIGURATION FOR TBSM USING LOGSECOND <size>

Where <size> is the new transaction log file size that you require.

To further optimize the configuration of the database, please estimate the expected number ofservice instances that will be managed

The database is configured according the size you specify here.


Table 4. Service instance estimates

Size Number of services Disk space reserved

Large More than 25,000 10 GB

Medium 5,000 to 25,000 6 GB

Small Up to 5,000 3 GB

Uninstalling TBSM Database Configuration Server

Before you begin

You must be logged in as the DB2 instance user db2inst1. The installer must be run from a terminalwindow.

Procedure

1. Start Installation Manager:

/home/db2inst1/IBM/InstallationManager/eclipse/IBMIM

Installation Manager opens.2. Click Uninstall.3. Select IBM Tivoli Business Service Manager Database Configuration Utility 6.2.0 and click Next.4. In the Review Summary Information window, click Uninstall.5. The uninstallation progresses and takes several minutes to complete based on the selections in the

panels.6. Click on View Log File.

Dropping TBSM databases after uninstall

Before you begin

You must be logged in as the DB2 instance user db2inst1 on a terminal window.

Procedure

1. Logon to command or terminal window.2. Check the TBSM databases available:

db2 list db directory | grep "alias"3. Drop the TBSM databases identified from by the above command:

a. db2 drop db TBSMb. db2 drop db TBSMHIST

Installing the Data Server componentYou can use the installation program to install only the Data Server component, which includes theDiscovery Library Toolkit. This is recommended in a production environment, where you want to installthe Data Server component on a separate system from the other TBSM components.

In TBSM 6.2.0, the TBSM Data Server uses a separate installer with the name data_<platform>.zipwhich is available in a platform specific installer zip. Copy this zip to the server where the TBSM DataServer will be installed. Note, that the TBSM Data Server must have the Netcool/Impact server installedon the same system.


Before you beginYou need to do the following before install and configure these components:

• Configure the TBSM databases on a DB2 instance. You need to know the connection information for thedatabase.

• Install IBM Tivoli Netcool/OMNIbus ObjectServer and configure the TBSM schema on an existingObjectServer as described in the Planning section of this guide. The ObjectServer must be runningbefore you install the Data Server. You need to know the connection information for the ObjectServer.

• Install Impact 7.1.0.13 with TBSM as the server name and TBSMCLUSTER as the cluster name andconfigure the required user repository (LDAP or Objectserver). The Impact Server and the Impact GUIServer should be running before installing Data Server.

• When installing Impact for the backup TBSM server, the server name must be TBSM_B and the clustername TBSMCLUSTER.

• Read the sections that describe all the information you need to complete each screen in the installationprogram. Once you obtain all the information you need, fill out the Data Server installation worksheetand run the installer, using the worksheet as your guide.

Data server informationSpecify the communication settings with the Data server.

PurposeTo successfully install the server, you need supply information that the Dashboard server needs tocommunicate with the Data server.

Restriction:

You cannot install a Backup Data Server and a Data Server at the same time. See Configuring postinstallation > Configuring IBM Tivoli Business Service Manager for failover for instructions aboutconfiguring a failover environment.

Choices

You can choose from the following options:

Communication portThe port number that the Dashboard Server components will use for communication with the DataServer component.

By default, this is set to 17542. The valid range for the port number is 1241–65535.

Impact Server Command Line PortThe port for the Netcool/Impact command line interface. The default value is 2000.

If failover is set up and this Data Server will be the backup server, select the following check box.If you are designating this host as the backup server in a failover environment, select the Designatedbackup server option.

Note: If failover is selected and this server is used as the backup server, please ensure that theImpact server name is given as TBSM_B during installation of the Impact component for the backupTBSM server.

TBSM Dataserver user registry informationSelect the type of user management and authentication.

Purpose

To successfully install the server, you need supply information about your user registry. During theinstallation, choose one of the user registry options listed in the TBSM DashServer User RegistryInformationpanel.


If the Impact Server is configured to use LDAP or the OMNIbus ObjectServer as the user repository, in theinstallation panel, you will not have any option to enter the user registry details. Instead a radio buttonwill be auto selected to use the exiting user repository. If Impact is configured to use file-based userrepository, then this panel will give the option to change to the OMNIbus ObjectServer user repository byentering the OMNIbus server details.

Note: You will not be given the option to change to the LDAP user repository during the Data Serverinstallation.

Database informationSpecify information about the TBSM databases in this window.

Purpose

For each TBSM database you need to know the name, host, port, and user information. This databasemust be configured with the TBSM database configuration utility before you install TBSM.

To successfully install the server, you need supply information on the databases that was installed forTBSM using the database configuration utility.

Choices

You need to know this information for each database.

TBSM Database InformationFor each TBSM database you need to know the name, host, port, and user information. This databasemust be configured with the TBSM database configuration utility before you install TBSM.

In many cases, all the TBSM databases share the same configuration. By default, the option Use thesame database as the TBSM Data Server is selected for the Metric Marker and Metric Historydatabases. If separate databases have been configured, de-select this option and enter theinformation for each database.

The Data Server database stores information such as services, templates, and the service componentrepository.

The Metric Marker database stores metric markers configured for overlaying historical values in theTime Window Analyzer.

The Metric History database stores the history of values for metrics that are collected for the TimeWindow Analyzer.

You need to know this information for each database.

Database nameThe name for the database. The default is TBSM.

Database HostnameThe host name where the Data Server database is installed.

Database port NumberThe default is 50000.

Use the port number for the instance of DB2 where the TBSM database was configured.

Important: The TBSM installation program does not check if the port number is valid. As a result,you must validate the port number manually.

Database UsernameThe name of a user that has permission to update tables in the database.

Database passwordThe database user password.

Confirm Database passwordConfirm the database user password.


Dashboard Application Service Hub InformationThe user and password information for the administrative user who creates the DashboardApplication Service Hub profile in the Websphere Application Server. The default user name istbsmadmin.

JazzSMNote down the port number of JazzSM console.

Impact Server details

You need to enter the details of the Impact server where the TBSM Data Server is installed and the TBSMData Server should be up and running, if not you will get a warning message and installation can becontinued.

ObjectServer configurationSpecify information about the Netcool/OMNIbus ObjectServer in this window.

PurposeTo successfully install the server, you need supply information the ObjectServer that sends events toNetcool/Impact. By default, the ObjectServer name is set to the host name of the system where you arerunning the installation program.

Important: You need to apply the TBSM schema changes before proceeding with the installation, See thePlanning section for more information on Netcool/OMNIbus considerations.

Restriction: You can not specify the same ObjectServer for more that one TBSM Data server. Otherwise,your event data will be incorrect for both servers. The only time you can use the same ObjectServer is forthe primary and backup Data servers in a failover environment.

Choices


ObjectServer host

The host name of the system where the ObjectServer is installed.

By default, this is the name of the local host where you are running the installer.

ObjectServer portThe port number for the ObjectServer.

By default, this is set to 4100. The valid range for the port number is 1024–65535. This port numbermust not be in use by another application.

ObjectServer UserThe user name.

The default, this is set to root.

ObjectServer PasswordThe ObjectServer user password.

Note: TBSM can be installed with the default ObjectServer user as root and a null password, but userscannot use a null password to log in to the TBSM Dashboard Server. This is because the IntegratedSolutions Console does not allow blank passwords.

Confirmation PasswordEnter the ObjectServer password here again. If this does not match the ObjectServer Password, youare prompted to enter the password again.


Discovery Library Toolkit informationSpecify information about the Discovery Library Toolkit installation in the Dataserver DatasourceInformation panel of the installer.

Requirements

To use the Discovery Library Toolkit, you must install IBM Tivoli Business Service Manager 6.2.0.

To import business applications from Tivoli Application Dependency Discovery Manager 7.3, ensure thatthe com.ibm.cdb.serviceinfrastructure.earlier.ver.compatibility property in thecollation.properties file is set to true. For Tivoli Application Dependency Discovery Managerservers that were upgraded to 7.3, the property is set to true by default.

In new installations of Tivoli Application Dependency Discovery Manager 7.3, the property is set to falseby default. If you change the property from false to true, you need to generate the business applicationsagain. You can wait for the scheduler to process all the grouping patterns or you can manually run thegrouping patterns from the Tivoli Application Dependency Discovery Manager UI or command-lineinterface.

Purpose

Use the Discovery Library Toolkit to import data from:

• Tivoli Application Dependency Discovery Manager 7.2.2 or later.

Note: If you want to integrate the Discovery Library Toolkit with Tivoli Application DependencyDiscovery Manager 7.3, you must use TBSM 6.1.1 Fix Pack 1. You also need to use the migration utilityto migrate your classfilters.xml and NamingRules.xml files. Discovery Library Toolkit alsosupports data import from Tivoli Application Dependency Discovery Manager 7.1.2 and above, howevernote that versions below 7.2.2 shall no longer be supported by the support team. If you decided to useTivoli Application Dependency Discovery Manager 7.2 afterward, you need to use the same utility torevert the files to their previous versions. For more information about the utility and how to use it, seethe TBSM developerWorks page at:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/TBSM%20Discovery%20Library%20Toolkit%20Configuration%20-%20Integrating%20with%20TADDM%207.3

• IBM common data model Discovery Library (IDML) books• alternate name space books• Discovery Library toolkit API• Autopopulation rules.

During the Data server installation you can choose whether Tivoli Application Dependency DiscoveryManager and/or books will be accepted. The API is enabled by default, but can be disabled afterinstallation through a property.

TADDM warning: If you are installing the Discovery Library Toolkit with a Tivoli Application DependencyDiscovery Manager server as a data source, you need to make sure that you have only one DiscoveryLibrary Toolkit connection to the Tivoli Application Dependency Discovery Manager server. Otherwise, youwill get incorrect data from the Tivoli Application Dependency Discovery Manager .

Note: If there is already a TBSM Discovery Library toolkit installed on this machine and it is installed into anon-standard location, this copy of the toolkit should be shutdown. A non-standard location is defined asnot being in ../tivoli/tbsm/XMLtoolkit. If a copy already resides at this location, the TBSM Dataserver install will skip the toolkit portion of the installation.

You also specify information to enable the toolkit to export Discovery Library books from TBSM.

Choices

You need to specify the data source information for the toolkit.





Please select the data source(s) that will be used.Discovery Library books

The toolkit searches a directory you specify for new Discovery Library books (DLA files) andprocesses any files in that directory.

Tivoli Application Dependency Discovery ManagerIf you are going to use Tivoli Application Dependency Discovery Manager as the source for yourdata, select this option. If you select this option, the installer prompts you for the serverconnection information.

Enter the naming service RMI registry portThe port number for the naming server RMI registry port.

The default is 12315.

Discovery Library Book Import ConfigurationConfiguration of the book import file system. Enter the directory name that the toolkit will monitor fornew book files. When a new book file is detected in the directory you specify, the toolkit reads andprocesses the file.

Default: $TBSM_HOME/tbsm/discovery/dlbooks

TADDM Connectivity ConfiguationIf you selected the Tivoli Application Dependency Discovery Manager as a data source, the installerprompts you for the server information.Enter the TADDM User ID

The Tivoli Application Dependency Discovery Manager user ID. Specify a user ID with at leastsupervisory authority.

Enter the TADDM passwordThe password associated with the user ID

Confirm the TADDM passwordRe-enter the password.

Enter the TADDM server hostname or IP addressThe host name or IP address of the system where the server is running. If the server is running ona private network and the TBSM server is not, then specify the external IP address of the TADDMserver.

Enter TADDM portThe RMI port that Tivoli Application Dependency Discovery Manager (TADDM) is listening on.TADDM defines the RMI port in the taddmInstall/etc/collation.properties file. ForTADDM versions earlier than 7.2.2, the property is com.collation.api.port. For TADDMversions 7.2.2 or later, the property is com.ibm.cdb.service.registry.public.port.

The default value is 9433.

Enter the SSL port that TADDM is listening onThe SSL RMI port that Tivoli Application Dependency Discovery Manager (TADDM) is listening on.TADDM defines the port in the taddmInstall/etc/collation.properties file. For TADDMversions earlier than 7.2.2, the property is com.collation.api.ssl.port. For TADDMversions 7.2.2 or later, the property is com.ibm.cdb.service.registry.public.port.

The default value is 9433.

Use SSL on the connection that TADDM is listening onSpecify whether you are using TADDM SSL listening port.

If you select SSL, you must copy the certificate jssecacerts.certs from the TADDM host to the Dataserver in this directory:

$TBSM_HOME\XMLtoolkit\sdk


You can do this after the installation is complete, but you need to copy the file before you start thetoolkit.

TADDM Database ConfigurationThis set of prompts let you specify configuration definitions for the TADDM database.Select database type

Specify IBM DB2 or Oracle.

If you select IBM DB2, the JDBC files are found automatically in the TBSM installation package.

If you specify the Oracle database, the installer prompts you for the location of the directorycontaining the Oracle JDBC drivers. Check if the $TBSM_HOME/dsalib directory has the correctdriver for your version of Oracle.

If you do not have this file on the Data server host, find the file and copy it to your system.

These files are typically provided by the database vendor with the database or the database clientpackage. For example, you can find this file on your Oracle host system or as part of your Oracleclient installation.

The installer looks in the directory you specify and collects the names of the jars that begin with"o" and end with ".jar" and adds these to the toolkit's classpath. If either ojdbc6_g.jar,ojdbc6.jar or ojdbc5.jar is found, it is added to the classpath; if not then all jars matchingthe pattern are added.

The reason for the additional checking on Windows is because problems have been seen with the11.2.0.2.0 version of ojdbc6.jar. If this version of the JDBC driver is being used, it may be bestto use object6_g.jar instead of ojdbc6.jar. The problem manifests itself on Windows withthe following exception:

Exception in thread "main" java.lang.NoClassDefFoundError: oracle.dms.console.DMSConsole at oracle.jdbc.driver.DMSFactory.<clinit> (DMSFactory.java:51) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:200) at oracle.jdbc.driver.PhysicalConnection.createDMSSensors(PhysicalConnection.java:3821)

Enter the database User ID:The TADDM database user id.

Note: The TADDM database user that TBSM is using needs only read authority on the TADDMdatabase with two exceptions.

1. TBSM needs read/write/analyze permission on the tbsm_change_history_table. If thistable has not yet been created, the DDL in .../XMLtoolkit/sql/taddm_schema_setup_oracle.sql or taddm_schema_setup_db2.sql can be used tocreate the table. TBSM uses this table during delta imports.

2. If the customer was using an older version of the toolkit that used the generated relationships(taddm explicitrel script) in TADDM, these relationships must be deleted. After installing,run the .../XMLtoolkit/bin/purgeexplicitrel script to delete these relationships. Theuser used for this script needs write authority since it is deleting from the relation,persobj, and cmdb_guid_alias tables. Depending on the number of relationships that needto be deleted, this process can be lengthy. This is a one time process, so the user andpassword used by purgeexcplicitrel can be different than that provided to TBSM forgeneral use.

Note: On Oracle, the database user that TBSM uses requires read/write/analyze/truncateprivileges to the table tbsm_change_history_table during delta import. Using the schemaowner as the user is preferable to avoid table authorization issues during the toolkit importprocess. However, users who do not wish to use the schema owner but still want to enable deltaimport may use the property DL_TADDM_DBManager.Schema_TCHT to obtain access to the table


instead. For more information please refer to the property description in the toolkit property filexmltoolkitsvc.properties.

Enter the database password:The password for the user id

Confirm database passwordEnter the password again to confirm.

Enter the database hostname:The host name for the TADDM database

Enter the port used by the databaseThe default is 50000.

Enter the database name:The default name is CMDB.

Enter the database schemaThe defalut schema is dbinst1.

Discovery Library Book Export ConfigurationSpecify the toolkit export configuration settings on this screen.Enter the directory name:

The directory where the toolkit writes book files created from the TBSM service models. This canbe the same directory as import book directory where the toolkit reads books files.

Default: $TBSM_HOME/tbsm/discovery/dlbooks

Enter dashboard server hostname or IP addressEnter the Dashboard server host name you want in the book files generated by TBSM. Otherproducts use this information to enable a launch back to TBSM in context. That is, the otherapplications can launch a TBSM page from the specified Dashboard server.

If load balancing is set up for your Dashboard servers, specify the load balancer host.

If you enter the host name, enter the fully qualified name.

The default value is the Data server host IP address.

Enter the Dashboard server port:The Dashboard sever HTTP port.

The default is 16310

Installation worksheet: Data ServerThis worksheet helps guide you through the Data server installation.

PurposeFill out the worksheet before you run the installation program for the Data server. Save this worksheet forfuture reference.

Worksheet

You need to specify these settings:

Table 5. Data server installation information

Prompt title Default value Installed value

Installation Directory /opt/IBM/tivoli/tbsm

C:\ProgramFiles\IBM\tivoli\tbsm

Data Server Information


Table 5. Data server installation information (continued)


Communication port 17542

Impact Server Command Line Port 2000

Designated backup server Not selected.

Data Backup Information Required for failoverconfiguration

Backup Data Server host

Backup Data Server HTTP port 17310

Backup Data Servercommunication port

17542

User Registry Selection ObjectServer

TBSM Data Server DatabaseInformation

Database Name TBSM

Database Hostname

Database Port Number 50000

Database User Name

Database Password

TBSM Metric Marker DatabaseInformation

Use the same database as theTBSM Data Server

Selected

Database Name TBSM

Database Hostname


Database User Name

Database Password

TBSM Metric History DatabaseInformation

Use the same database as theTBSM Data Server

Not selected

Database Name TBSMHIST

Database Hostname


Database User Name

Database Password

Impact port information

Starting port number provided 17310


Table 5. Data server installation information (continued)


Modified port value file (optional)

ObjectServer Configuration

ObjectServer host Local host name whereinstaller is running.

ObjectServer port 4100

ObjectServer User root

ObjectServer Password

Discovery Libray ToolkitConfiguration

Discovery Library books datasource

Selected

Tivoli Application DependencyDiscovery Manager data source

Not Selected

Naming service RMI registry port 12315

Discovery Library Book ImportConfiguration

$TBSM_HOME/tbsm/discovery/dlbooks

TADDM User ID None

TADDM password None

TADDM server hostname or IPaddress

None

TADDM port 9443

SSL port that TADDM is listening on 9433

Use SSL on the connection thatTADDM is listening on

Not selected.

TADDM database type IBM DB2

Database User ID None

Database password: None

TADDM Database hostname None

TADDM database port 50000

TADDM database name: CMDB

TADDM database schema db2inst1

Book Export directory $TBSM_HOME/tbsm/discovery/dlbooks

Dashboard server hostname or IPaddress

Data server IP address

Dashboard sever HTTP port. 16310

Running the Data Server installer in GUI modeThis section describes how to start and run the Data Server installation program.


Before you begin


• The TBSM 6.2 Database Configuration Utility has been run and the TBSM database and schema havebeen created successfully.

• TBSM 6.2 Data Server must be installed on the same machine as Impact 7.1 and by the same user whoinstalled Impact.

• IBM Netcool/Impact Base 7.1.0 with Fix Pack 13 set up with the server name TBSM and the clustername TBSMCLUSTER.

• Jazz for Service 1.1.3 with Cumulative Pack version 5.• The TBSM 6.2 schema has been applied to the event listener: ObjectServer. The schema files are in the

OMNIbus directory of the installation media.• The OMNIbus Web GUI has been configured to add TBSM users to the OMNIbus users group. For details

see the Netcool/OMNIbus Knowledge Center.• Users root, impactadmin and tbsmadmin are present in Netcool/OMNIbus ObjectServer (this is

required if the TBSM Data Server is to be installed with Netcool/OMNIbus specified as the usermanagement repository).

• SSO has been configured between Impact and JazzSM. This is a prerequisite for the console integrationbetween DASH and Impact. SSO configuration enables you to verify functionality such as policy editorand TBSM system status. For details, see the Netcool Impact Knowledge Center.

Note the following information from the above installations (you will need it when performing the DataServer installation:

• DB2 Hostname or IP and port number where the Database Configuration Utility is installed• DB2 username• DB2 TBSM, TBSM Metric Marker, and TBSM Metric History database names• Netcool/OMNIbus Hostname and Port• Netcool/OMNIbus ObjectServer users (root, impactadmin, tbsmadmin) and their passwords• Netcool/Impact hostname, impactserver port, impactGUI port• JazzSM hostname, port number, admin username, and password• TADDM details like ost name, port, username, and password

To install the Data Server, use the following steps:

Procedure

1. Create a directory on Impact host machine to download and unzip the installation media:

mkdir -p /TBSM6.2/DataServer2. Obtain the platform specific TBSM 6.2 Data Server installation media (data_<OS>.zip) and copy it

into the TBSM6.2 directory.3. Change to the media directory:


unzip data_<OS>.zip -d DataServer5. Change to the install directory:

cd /TBSM6.2/DataServer6. Execute install_gui_data.sh as the user who installed Impact.

If an older version of Install Manager (IM) is present in the server, the packaged IM (version 1.8.8) isinstalled. Once the IM upgrade is complete, IM will launch.

7. Click Install.


8. Select IBM Tivoli Business Service Manager Data Server and then click Next.

The Prerequisite screen is displayed showing all the prerequisites that must be met.9. Click Next.


11. In the Location window, in the Installation Directory field, click Browse to change to the location ofthe TBSM install directory and click Next.

Note: The TBSM directory must have the same parent path as Impact. The install will not continue ifthe impact install is not detected.

12. In the Features to Install window, click Next.

In the Impact Server Details window, the Impact host, directory, ports and user are displayed.13. Provide the Impact User Password and click Next.

14. In the Data Server Information Panel window, review the default communication port, edit it ifrequired, and click Next.

15. In the TBSM Data Server Database Information window, review the default values, edit them ifrequired. Complete the Database Password and Confirm Password fields, and click Next.

16. In the TBSM Metric Marker Database Information window, review the default values provided.Complete the Database Password and Confirm Password fields, and click Next.

17. In the TBSM Metric History Database Information window, review the default values provided.Complete the Database Password and Confirm Password fields, and click Next.

18. In the ObjectServer Details window, review the default values, edit them if required. Enter theObjectServer User Password and Confirm Password fields, (initially, root user does not have apassword). Click Next.

IM displays a warning message to prompt you to ensure that the TBSM schema is applied beforestarting the Data Server installation.

19. In the TBSM Data Server User Registry Details panel, select User Registry Already Configured ifImpact is already configured to use the OMNIbus User Registry. If Impact is configured with theBasic User Registry you can continue to use it that way, but must select ObjectServer.

Note: If Impact is configured to use ObjectServer as the user repository and the tbsmadmin user isalready created in ObjectServer, you will not be shown the ObjectServer option. The tbsmadmin usershould exist in the in ObjectServer before installing the Data Server.

20. In the TBSM Data Server User Registry Details panel, select ObjectServer if Impact is alreadyconfigured to File-based repository. When you select the ObjectServer radio button, IM displaysvarious ObjectServer fields.

Ensure that the ObjectServer ID exists in Netcool/OMNIbus or create the ID manually beforeproceeding further. Enter the ObjectServer User Password and Confirm Password fields, (initially,root user does not have a password). Click Next.

Note: The TBSM schema must be applied to the ObjectServer before proceeding with the Data Serverinstallation.

21. In the Jazz for SM Server Details window, review/edit the default values provided. Ensure that theJazzSM is up and running on the given host/port and click Next.

22. In the DataServer Data Source and DB Selection window, select the data sources to be used. IfTADDM is selected, then TADDM details needs to be provided in the next two windows (TADDMConnectivity Configuration and TADDM Database Configuration), else the details in the two TADDMwindows will be disabled. Click Next.


23. In the TADDM Connectivity Configuration window, the information is disabled as TADDM is notselected in the DataServer DataSource and DB Selection window. Click Next.

24. In the TADDM Database Configuration window, the information is disabled as TADDM is notselected in the DataServer DataSource and DB Selection window. Click Next.

25. In the Discovery Library Book Import Configuration window, review the default values provided.Click Next.

26. In the Discovery Library Book Export Configuration window, review the default values provided.Click Next.

27. In the Review Summary Information window, click Install.28. The installation progresses and takes several minutes to complete based on the selections made in

the various panels.29. Click View Log File.

Adding JDBC drivers to the shared libraryUse this procedure to add a JDBC driver to the TBSM shared library.

About this task

Tivoli Business Service Manager supplies the following database JDBC drivers with this release:

• DB2• HSQL• Informix• ObjectServer

If you want to use other databases as data sources, you need to obtain these drivers from the databasemanufacturer and copy them to your TBSM host.

These files are typically provided by the database vendor with the database or the database clientpackage. For example, you can find the Oracle file on your Oracle host system or as part of your Oracleclient installation.

Procedure

1. Obtain the appropriate JDBC driver according to the DSA specification.

2. Stop the server.3. Copy the JDBC driver to the $TBSM_HOME/impact/dsalib directory.

This directory is created during the installation, and initially it is empty.4. Restart the TBSM server.

What to do next

In a multi-host configuration you have to repeat this procedure for each server because JDBC drivers arenot replicated between the servers. Stop the server while you are performing this procedure.

Installing the Dashboard server componentIn TBSM 6.2, a separate IIM based installer for TBSM Dashboard server is provided. This installation isuseful in a production environment, where you want to install the Dashboard server component on aseparate system from the other IBM Tivoli Business Service Manager (TBSM) components.

Before you begin

Before you install the Dashboard server:


1. If TBSM Data Server is not installed before installing the Dashboard Server, you will get a warning forTBSM Data Server port not being active during the installation. But you can continue with theinstallation.

2. Install JazzSM with the Dashboard Application Service Hub.3. Install OMNIbus WebGUI on JazzSM and configure it to use the proper ObjectServer (which is used as

the Events server by TBSM Data Server).

Refer to the following link for details about OMNIbus WebGUI configuration using the config tool:https://www.ibm.com/support/knowledgecenter/en/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/webtop/wip/task/web_ins_im_configuimode.html

4. If you are planning to use LDAP as the user repository, make sure LDAP is configured as a userrepository for JazzSM before installing the TBSM Dashboard server.

5. Complete the Dashboard server installation worksheet to help guide you through the installation.

OS Agent restriction: If the Tivoli Monitoring Agent for Windows OS is installed and runningon the same system as the Dashboard Application Services Hub server, it may lock certain WebsphereApplication Server dll files and cause the install to fail.

To avoid this problem, stop the agent before installing the server. To stop the agent:

1. In the Manage Tivoli Enterprise Monitoring Services application, select the Monitoring Agent forWindows OS service.

2. Select Actions->Stop.

You can also stop the Windows service for the agent:

In the Windows Services applet, stop both the "Monitoring Agent for Windows OS - Primary" and"Monitoring Agent for Windows OS - Watchdog" services

After the install has completed, you may restart the agent.

TBSM Dataserver user registry informationSelect the type of user management and authentication.

Purpose

To successfully install the server, you need supply information about your user registry. During theinstallation, choose one of the user registry options listed in the TBSM DashServer User RegistryInformationpanel.

If the Impact Server is configured to use LDAP or the OMNIbus ObjectServer as the user repository, in theinstallation panel, you will not have any option to enter the user registry details. Instead a radio buttonwill be auto selected to use the exiting user repository. If Impact is configured to use file-based userrepository, then this panel will give the option to change to the OMNIbus ObjectServer user repository byentering the OMNIbus server details.

Note: You will not be given the option to change to the LDAP user repository during the Data Serverinstallation.

Dashboard server configurationSpecify the communication settings with the Data server.

PurposeTo successfully install the server, you need to supply information that the Dashboard server needs tocommunicate with the Data server.

Restriction: You cannot install a Dashboard Server to connect to the Data Server that has beendesignated as a backup Data server. Please direct this dashboard server to connect to the primary Dataserver.


https://www.ibm.com/support/knowledgecenter/en/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/webtop/wip/task/web_ins_im_configuimode.html

https://www.ibm.com/support/knowledgecenter/en/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/webtop/wip/task/web_ins_im_configuimode.html

You cannot install a Backup Data Server and a Dashboard Server at the same time. See the Configuringpost installation: Configuring failover and Load Balancing section of the TBSM Installation guide forinstructions on configuring a failover environment.

Choices


Dashboard Server communication portThe port number that the Dashboard Server component uses for communication with the Data Servercomponent.

By default, this number is set to 17543. The valid range for the port number is 1241–65535.

Data Server Host

The host name of the system where the Data Server is installed.

By default, this value is set to the host name of the local system.

Data Server HTTP PortThe port number for the Data server.

By default, this port is set to 17310. The valid range for the port number is 1241–65535.

Data Server communication portThe port number that the Data Server component uses for communication with the Dashboard Servercomponent.

By default, this port is set to 17542. The valid range for the port number is 1241–65535.

Data Server HA/FailOver configuredIf you have a failover environment, select this option and you will be prompted for information on thebackup Data server.

Dashboard Backup InformationIf you select the Data Server HA/FailOver Configured option, you need to provide this host and portinformation for the backup Data server on the next screen:Backup Data Server host

The host name of the backup Data Server.Backup Data Server HTTP port

Accept the default, or enter a port number.


Backup Data Server communication portAccept the default, or enter a port number.


Data server Failover setup , Loadbalance configuration InformationWhen the Data Server HA/FailOver Configured checkbox is selected, you will be provided withone more checkbox options Is Impact UI load balancing configured/planned for HA. Whenchecked, you need to enter the hostname and port of the IBM HTTP server which is used for loadbalancing.

Impact Server details

You should enter the impactadmin user password in this section of the installer. Other Impact serverdetails will be pre-populated based on your environment.

Warning: If Impact GUI is installed on a different machine than Impact Server, you will see awarning that the HTTP port is not responding. You can ignore this warning. There are additionalsteps required in this scenario. See the known issues section


ObjectServer configurationSpecify information about the Netcool/OMNIbus ObjectServer in this window.

PurposeTo successfully install the server, you need supply information the ObjectServer that sends events toNetcool/Impact. By default, the ObjectServer name is set to the host name of the system where you arerunning the installation program.

Important: You need to apply the TBSM schema changes before proceeding with the installation, See thePlanning section for more information on Netcool/OMNIbus considerations.

Restriction: You can not specify the same ObjectServer for more that one TBSM Data server. Otherwise,your event data will be incorrect for both servers. The only time you can use the same ObjectServer is forthe primary and backup Data servers in a failover environment.

Choices


ObjectServer host

The host name of the system where the ObjectServer is installed.

By default, this is the name of the local host where you are running the installer.

ObjectServer portThe port number for the ObjectServer.

By default, this is set to 4100. The valid range for the port number is 1024–65535. This port numbermust not be in use by another application.

ObjectServer UserThe user name.

The default, this is set to root.

ObjectServer PasswordThe ObjectServer user password.

Note: TBSM can be installed with the default ObjectServer user as root and a null password, but userscannot use a null password to log in to the TBSM Dashboard Server. This is because the IntegratedSolutions Console does not allow blank passwords.

Confirmation PasswordEnter the ObjectServer password here again. If this does not match the ObjectServer Password, youare prompted to enter the password again.

Running the Dashboard Server installer in GUI modeThis section describes how to start and run the Dashboard Server installation program.

Before you begin


• The TBSM 6.2 Database Configuration Utility has been run and the TBSM database and schema havebeen created successfully.

• TBSM 6.2 Data Server must be installed on the same machine as Impact 7.1 and by the same user whoinstalled Impact.

• TBSM 6.2 Dashboard Server must be installed on the same machine as Jazz for Service and by the sameuser that installed Jazz for Service.

• The list of ports should be kept the same, not changed to match the Data Server.• IBM Tivoli Netcool/OMNIbus 8.1.0 (8.1.0.5)• IBM Tivoli Netcool/OMNIbus Web GUI 8.1.0 + Fix Pack 4


• IBM Netcool/Impact Base 7.1.0 with Fix Pack 13.• Jazz for Service 1.1.3 with Cumulative Pack version 5.• The OMNIbus Web GUI has been configured to add TBSM users to the OMNIbus users group. For details

see the Netcool/OMNIbus Knowledge Center.• Users root, impactadmin and tbsmadmin are present in Netcool/OMNIbus ObjectServer (this is

required if the TBSM Data Server is to be installed with Netcool/OMNIbus specified as the usermanagement repository). The same Netcool/OMNIbus must be used as the user registry for TBSMDashboard server.

• The TBSM 6.2 schema has been applied to the event listener: ObjectServer. The schema files are in theOMNIbus directory of the installation media.

Note the following information from the above installations (you will need it when performing the DataServer installation:

• DB2 Hostname or IP and port number where the Database Configuration Utility is installed• DB2 username• DB2 TBSM, TBSM Metric Marker, and TBSM Metric History database names• Netcool/OMNIbus Hostname and Port• Netcool/OMNIbus ObjectServer users (root, impactadmin, tbsmadmin) and their passwords• Netcool/Impact hostname, impactserver port, impactGUI port• JazzSM hostname, port number, admin username, and password

To install the Dashboard Server, use the following steps:

Procedure

1. Create a directory on the JazzSM host machine to download and unzip the installation media:

mkdir -p /TBSM6.2/DashServer2. Obtain the platform specific TBSM 6.2 Dashboard Server installation media (dash_<OS>.zip) and

copy it onto the TBSM6.2 directory.3. Change to the media directory:


unzip dash_<OS>.zip -d DashServer5. Change to the install directory:

cd /TBSM6.2/DashServer6. Run install_gui_dash.sh.7. Select Install on Installation Manager.8. Select IBM Tivoli Business Service Manager Dashboard Server and click Next.

The Prerequisite screen is displayed showing all the prerequisites that must be met.9. Click Next.


11. In the Location window, in the Installation Directory field, click Browse to change to the location ofthe TBSM dashboard install directory and click Next.

12. In the Features to Install window, click Next.

In the Jazz for SM Details window, the JazzSM directory, port, user and NCO-WebGUI are displayed.13. Complete the JazzSM Password and Confirm Password fields, and click Next.


14. In the Dashboard Server Configuration window, review the default communication port and clickNext.

In the Impact Server Details window, the Impact host directory, port, and user are displayed.15. Review the default information.16. Complete the Impact Password and Impact Confirm Password fields, and click Next.17. In the ObjectServer Details window, review the default values provided.18. Complete the ObjectServer User Password and Confirm Password fields (initially, root user does

not have a password). Click Next.19. In the TBSM Dashboard Server User Registry Details window, select the User Registry option that

is used by JazzSM.20. If ObjectServer is selected, complete the ObjectServer User Password and Confirm Password

fields. Click Next.21. In the Review Summary Information window, click Install.

The installation progresses and takes several minutes to complete based on the selections made inthe various panels.

22. . View the log files for errors. Click Finish.

Tivoli Event Integration Facility Probe Installation

About this taskThe Probe for Tivoli EIF can receive Event Integration Facility (EIF) events sent from any Tivoli devicesand sends them to the ObjectServer. This topic outlines the steps required to install and configure theTivoli EIF Probe.

Procedure

1. Install the EIF Probe on the TBSM server. See:

https://www.ibm.com/support/knowledgecenter/en/SSSHTQ/omnibus/probes/all_probes/wip/concept/install_intro_install.html

2. Install the ITM Event Synchronization Component on the Netcool/OMNIbus ObjectServer. See:

https://www.ibm.com/support/knowledgecenter/en/SS3JRN_7.2.1/com.ibm.itm.doc_6.3/install/inst_itmsynch_comp.htm

3. Update the ObjectServer database for ITM events, and to start and stop the Situation UpdateForwarder. See:

https://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.1/com.ibm.itm.doc_6.3/install/inst_config.htm

4. Configure the Netcool/OMNIbus ObjectServer to receive events from ITM:

https://www.ibm.com/support/knowledgecenter/en/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/install/omnibus_install.htm

5. Update the rules files to receive the events from ITM through probe:

https://www.ibm.com/support/knowledgecenter/SS3JRN_7.2.0/com.ibm.itm.doc_6.2.3/itm623_install876.htm#config_omni2_probe

Verifying installation of the Tivoli Event Integration Facility probeErrors in the debug output of the Tivoli Event Integration Facility probe (EIF probe) or the failure of the EIFprobe to run are indications that the probe is not installed correctly.

About this task

Note: If the probe is running as a Windows service, stop the service before beginning the verificationprocedure. Start the service after verification is complete.












Procedure

1. Change to the directory where the probe was installed.The default directories are as follows:

/opt/IBM/tivoli/netcool/omnibus/probes

C:\Program Files\IBM\tivoli\netcool\omnibus\probes\win322. Edit the tivoli_eif.props file.

a) At the end of the file, remove the comment symbol (#) from the beginning of each of the followinglines:

MessageLevel : ‘debug'MessageLog : ‘stdout'

b) Save the file.3. Start the probe with the command:

nco_p_tivoli_eif.bat

nco_p_tivoli_eif.sh4. View output in the console of the probe running.

Typical output looks like this:

D:\IBM\Netcool\omnibus\probes\win32>nco_p_tivoli_eif.bat Netcool/OMNIbus NON NATIVE - Version 7.1 Copyright (C) 1994 - 2005, Micromuse Ltd. All rights reserved.Information: Requested to execute in CONSOLE mode 2007-01-12 13:53:13 Service starting in console mode01/12/2007 01:53:16 PM: Information: I-UNK-000-000: Connecting ... 01/12/2007 01:53:16 PM: Debug: D-UNK-000-000: Reading D:\IBM\Netcool\omnibus\ probes\win32\tivoli_eif.rules 01/12/2007 01:53:16 PM: Debug: D-UNK-000-000: Plain text rules file detected. 01/12/2007 01:53:16 PM: Debug: D-UNK-000-000: End of D:\IBM\Netcool\omnibus\ probes\win32\tivoli_eif.rules 01/12/2007 01:53:16 PM: Information: I-UNK-000-000: Using targets specified by properties 01/12/2007 01:53:16 PM: Debug: D-UNK-000-000: Setting default target server to 'NCOMS'. 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: Attempting a connection to server 'NCOMS'. 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: Checking for backup ObjectServer. 01/12/2007 01:53:29 PM: Information: I-UNK-000-000: 'NCOMS' is a primary server. Polling disabled. 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: Server Verification Starting. 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: Server Verification Complete. 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: Checking for svc update support. 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: Server SUPPORTS services.01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: svc update SUPPORTED 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: Heartbeat mode is: standard 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: Heartbeat mode is standard, probe will function as normal without heartbeating 01/12/2007 01:53:29 PM: Debug: D-BASE-004-049: THREAD MGR: started thread failover-thread (00DC0E48) 01/12/2007 01:53:29 PM: Debug: D-BASE-004-050: THREAD MGR: thread failover-thread (00DC0E48) 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: NSProbe - Reentrant Version 01/12/2007 01:53:29 PM: Information: I-UNK-000-000: Probewatch: Running ... 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: Inactivity-> 600 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: PortNumber-> 5530 01/12/2007 01:53:29 PM: Debug: D-UNK-000-000: EIFCacheFile-> C:\Program Files\ Netcool\OMNIbus\var\tivoli_eif.cache 01/12/2007 01:53:30 PM: Debug: D-UNK-000-000: EventCopies-> 1

5. Stop the probe.6. Remove the two property lines that you added.7. Start the probe.


Uninstalling the Tivoli Event Integration Facility probeEIF Probe can be uninstalled independently of TBSM as it was not installed along with TBSM

About this taskSee https://www.ibm.com/support/knowledgecenter/en/SSSHTQ_7.3.0/com.ibm.netcool_OMNIbus.doc_7.3.0/omnibus/wip/install/task/omn_ins_unixuninstallingprobesgtwys.html

TBSM extensions directoryThis directory contains EIF Probe rules files that are specific to TBSM functionality.

PurposeThe majority of these files are related to z/OS event flow support for TBSM. There is also a rules file tohelp you filter events from ITCAM for SOA. For more information on using and customizing these files, seethe TBSM Customization and Scenarios guides.

LocationsThis directory can be found in the root directory of TBSM installation image:

/tbsm_extenstions

These files are also available in the following locations if the Tivoli EIF probe is installed using the TBSMinstaller.

Windows

C:\%OMNIHOME%\probes\win32\tbsm_extensions

Note: When you use the command window, you may get a path not found error for %OMNIHOME%. If thepath for the OMNIHOME variable contains spaces, put the variable name in quotes as follows:"%OMNIHOME%"

UNIX

$OMNIHOME/probes/arch/tbsm_extensions

TBSM probe rules files

The tbsm_extensions directory contains these files.

kd4_tbsm.rulesITCAM for SOA BSM_Identity setting rules.

tivoli_eif_zos_tbsm.rulesTBSM z/OS lookup table reference rule file.

zos_classid.lookupTBSM z/OS lookup table by class id.

zos_identity.rulesTBSM z/OS BSM_Identity rule file.

zos_objectid.lookupTBSM z/OS lookup table by oject id id.

zos_objectid.low.lookupTBSM z/OS lookup table by object id example of minor behavior.

zos_objectid.medium1.lookupTBSM z/OS lookup table by object id example 1 of major behavior.

zos_objectid.medium2.lookupTBSM z/OS lookup table by object id example 2 of major behavior.


https://www.ibm.com/support/knowledgecenter/en/SSSHTQ_7.3.0/com.ibm.netcool_OMNIbus.doc_7.3.0/omnibus/wip/install/task/omn_ins_unixuninstallingprobesgtwys.html



Uninstalling TBSMThis section describes procedures for uninstalling the Data Server and Dashboard Server.

About this task

The uninstall procedure is only used to remove an installation that completes successfully.

Uninstalling TBSM Data Server

Before you begin

Procedure


/opt/IBM/InstallationManager/eclipse/IBMIM

Installation Manager opens.2. Click Uninstall.3. Scroll the list of Installed Packages. Select IBM Tivoli Business Service Manager Data Server 6.2.0

and click Next.

Note: If the Impact server is not running during uninstall, you will get an error message suggesting tostart the Impact server before uninstalling.

4. In the Review Summary Information window, click Uninstall.5. The uninstallation progresses and takes several minutes to complete based on the selections in the


7.

Uninstalling TBSM Dashboard Server

Procedure


/opt/IBM/InstallationManager/eclipse/IBMIM

Installation Manager opens.2. Click Uninstall.3. Scroll the list of Installed Packages. Select IBM Tivoli Business Service Manager Dashboard Server

6.2.0 and click Next.4. In the Review Summary Information window, click Uninstall.5. The uninstallation progresses and takes several minutes to complete based on the selections in the



Chapter 7. Service Model OverviewThis topic is an overview of IBM Tivoli Business Service Manager version 6.2.0 service models andterminology.

You use TBSM to create models of the services that you monitor for your organization. These models arecalled service models.

When you configure TBSM, you first step will be to create a service-dependency model that logically mapsthe relationships between the services and sub-services you want to monitor. There are two maincomponents in a service-dependency model:

• Service templates define a service type and how services of this type respond to incoming events orother data. You can think of a service template as a class of service.

• Services (or service instances) contain the details of a specific occurrence of a given service template,such as the name of the service and the other services it depends on.

Service templates

For each type of service you want to monitor, you create a service template in TBSM. These templatesdefine the common behavior for a given service type.

You can tag a service instance with multiple service templates, but you must specify a primary templateas the default. The primary template defines the icon and SLA settings for the service.

The TBSM Service Viewer shows the service template in relation to other service templates. This sectiondescribes the settings you configure for service templates.

Rules

Rules control how the services instances tagged with the template respond to incoming external dataand the status of other services. You can create the following types of rules:

Incoming status rulesThese rules control how a service responds to incoming ObjectServer events or other data. You canchange a service's status and extract numerical or text from the incoming data.

Aggregation rulesThese rules control how a given service instance responds to other supporting service instances.These rules combine data from multiple child services to determine the aggregate status of a parentservice. The child services support the parent services.

Numerical aggregation rulesThese rules are used by TBSM to aggregate rule output values of the same type across a set of childservice instances.

Numerical formula rulesThese rules are used by TBSM to combine rule output values of different types within the sameservice instance.

Autopopulation rulesThese rules let you configure services automatically based on event data from ObjectServer or an SQLdata source.

External service dependency adapters rules (ESDA rules)These rules let TBSM dynamically import service hierarchies from any data source you can configurefor use with TBSM.

Tagged servicesWhen you assign a template to a service, you tag the service with the template rules. Tagged serviceare services that behave according to the rules and other attributes configured in a given servicetemplate. For example, if you are creating a template for Web servers, you can tag the serviceinstances webserver1 and webserver2 with the Webserver service template.


Output expressionsOutput expressions allow you to combine the results of multiple rules to determine the overall statusof a service. For example, you configure the status to turn bad if two separate event rules have amarginal status using boolean operators. By default, the service status matches the status of the rulewith the worst status.

Service level agreement settingsWith the Service Level Agreement (SLA) settings, you can define when a given service instanceviolates the parameters of an SLA. The cumulative-time SLA settings help you measure the reliabilityof a given service against outage parameters you specify for a given time period, such as a day.You can also set SLA parameters that measure the duration and frequency of service outages. Eachtemplate has its own service level agreements. If a service is tagged with multiple templates, TBSMuses the SLA settings for the primary template.

Additional settingsThese settings allow you to create special attributes for a service template. You can set an hourly SLApenalty in a service template.

Security settingsThese settings allow you to assign user and group privileges needed to view, edit, or create servicetemplates. You only see this tab if you have TemplateAdmin privileges for a given service template orif you have the TemplateAdmin role for all templates. You can set the permissions so that onlyassigned groups or users can view or edit a specific service template.

Service instances

Each unique occurrence of a given service template is represented by a unique service instance in theTBSM Service Viewer. In the dependency view, each service instance displays as a service image inrelation to other service instances. This section describes the settings you configure for service instancesin TBSM.

Templates settingsThese settings let you tag a service instance with one or more service templates which control howthe service instance’s status responds to ObjectServer events or other data. If you tag the serviceinstance with multiple service templates, you also need to specify a primary service template. Theprimary template determines which icon to display for the service and the SLA settings to use for theservice.

Identification FieldsThese settings let you specify external data source field values used to uniquely identify the serviceinstance. For example, the value of the Node field can be the service’s name. You can also set TBSMto use multiple identification-field values for a single service.

Dependents settingsThese settings let you specify the service instance’s dependencies. You select the service templateand then the child service instance the parent service instance depends on. For example, if the parentservice is webfarm1, you specify a dependency on the child services webserver1, webserver2, andwebserver3.

Additional settingsThese settings let you specify GIS coordinates, sort order for the service instances and customparameters. These parameters can be values selected from an external data source.

Security settingsThese settings let you assign user and group privileges needed to view, edit, or create serviceinstances. You only see this tab if you have InstanceAdmin privileges for a given service template or ifyou have the InstanceAdmin for all services. You can set the permissions so that only assigned groupsor users can view or edit a specific service instance.


Chapter 8. TBSM service model configurationoverview

TBSM lets you create models of the services required to monitor your organization. In TBSM, thesemodels are called service models. The sequence of the stages is a general guideline, since you canperform some of these stages out of sequence. .

For more information about each stage see:

• “1 Plan your service model” on page 55• “2 Create service templates” on page 55• “3 Create structural dependencies” on page 56• “4 Identify data sources” on page 56• “5 Create incoming status and numerical rules” on page 56• “6 Create services” on page 57• “7 Create custom service trees and views” on page 57• “8 Create SLAs” on page 57• “9 Set permissions” on page 58

1 Plan your service modelBefore you start to configure a service model in TBSM, it is important to develop a plan that includesinformation about the services and service dependencies you want TBSM to monitor. Identify distinctservice types that have common characteristics.

To help you identify the common service types, create a draft model of this service hierarchy in TBSM thatincludes the following information:

• What do you monitor in your environment now with the applications such as IBM Tivoli Monitoring,Netcool/OMNIbus, and other applications? How would you visualize this incoming data for your clients?

• What business units or customers do you want to create dashboards for? The dashboard for the ITdepartment is different from a dashboard for an executive. What data sources do you need to accessand filter for your dashboards?

• What are the key performance indicators and other data you want to highlight on your dashboards.• What are the highest level services you want to monitor on your dashboard? Do these services

represent customers, business departments, or a business? You can map out services to representthem and their dependencies.

• What are the applications, devices–and so on–that support the high-level services? That is, what are thedependencies for the high-level services? You can map out child services to represent these items.

• How do the child services affect the high-level or parent services at the top of the service hierarchy?• What are the Netcool/OMNIbus events and other data that affect each service type?

2 Create service templatesWhen you have figured out the service hierarchy, create service templates for services that sharecommon behavior. For example, if you want to monitor multiple web servers, you create a web servertemplate that defines the attributes common to all the web servers. When you create services, you assignthese service instances to a given service template.


3 Create structural dependenciesIn service templates, you define the relationships between the various services to set the structure for agiven service model. These rules aggregate the overall service status based on the rule-output values formultiple child services and are called dependency-aggregation rules. These rules are based on statusvalues such as Bad or Marginal that are passed from child service templates.

4 Identify data sourcesIdentify the data sources that contain information about the services you want to create. You use thisdata to build your service model structure, and to monitor the status of the services in the model. TBSMuses the default ObjectServer that is installed with TBSM as a data source for your service models. Youcan also configure SQL databases as data sources and select data with SQL queries.

Also, you must configure Netcool/OMNIbus or database queries so that a single event or row shows thestatus of a given service.

5 Create incoming status and numerical rulesIn TBSM, three types of rules determine the status of a given service or calculate a numerical rule-outputvalue based on external data:

• Incoming status rules• Numerical aggregation rules• Numerical formula rules

Incoming status rules

TBSM service templates have the following types of incoming status rules:

• Good, Marginal, and Bad rules• Numerical rules

TBSM uses Good, Marginal, and Bad incoming status rules to obtain the general state of a service from anincoming ObjectServer event or other data. The general service state is determined by comparingthreshold values set in the rule definition to event field values or field values in other incoming data. Whenthis type of rule is processed, TBSM obtains a general service state of Good, Marginal, or Bad and assignsthis value to the service instance.

TBSM uses numerical incoming status rules to obtain a numerical value from fields in ObjectServer eventsor other data and then to associate this value with a service instance as a rule-output value. The resultingrule-output value is stored in memory and identified by the rule name where referenced elsewhere inTBSM.

TBSM uses numerical and text incoming status rules to obtain a value from fields in ObjectServer eventsor other data and then to associate this value with a service instance as a rule-output value. The resultingrule-output value is stored in memory and identified by the rule name where referenced elsewhere inTBSM.

Numerical aggregation rules

TBSM uses numerical aggregation rules to combine rule-output values of the same type across a set ofchild service instances. This type of rule is defined as part of the parent service template. The rule-outputvalues combined by a numerical aggregation rule can be generated by incoming numerical-status rules orby other aggregation and numerical formula rules.


Numerical formula rules

TBSM uses numerical formula rules to combine rule-output values of different types within the sameservice instance. These output values can be generated by incoming numerical-status rules or bynumerical aggregation rules. When a numerical formula rule is processed, the resulting combined outputvalue is assigned to the same service instances where the original output values existed.

6 Create servicesWhen you have defined the rules for service templates in your model, then you create the serviceinstances for your service model. A service instance, or service, is a unique instance of a given servicetemplate. For example, if you have an E-mail Server service template, you can assign services called e-mail1, e-mail2, and e-mail3 to the service template.

Optionally, you can automatically create the services by creating auto-population rules, External ServiceDependency Adaptor (ESDA) rules or with the Discovery Library Toolkit.

Service name restrictions

Important: TBSM checks the Service Name field for invalid characters. The Name field for services mustnot contain these special characters:

" < > \ * ? | ;

TBSM will not create a service when the Name field contains any of these invalid characters. If the objectdoes not save, remove any special characters from the name field.

Service names longer than 127 characters can cause display and performance issues.

Service names longer than 127 characters will be truncated in the Service Details portlet display. Thisdoes not affect the functioning of TBSM, but the truncated service name will appear in the Service Detailsportlet.

If you use the Node column in Netcool/OMNIBus to create or match your service name: The nodecolumn is limited to 64 characters. If the service name is greater than 64 characters, it will be truncatedand TBSM will not receive any events for the service.

You can either change the incoming status rule to use different service instance naming fields, or you canchange the identification fields for a service with a long name. The identification field or fields can bedifferent than the service naming field or fields. For example, if you have a service name that uses theNode column for its name, and the name is longer than 64 characters, the service will not receive events.To fix this, you can specify another field, such as a field that contains the IP address as the Identificationfield for the service.

7 Create custom service trees and viewsWhen you configure your numerical rules, you can display the rule-output values in the Services tree(Service Availability) or in the Service Editor (Service Configuration or Service Administration).

8 Create SLAsOptionally, you can define service level agreement (SLA) settings for the service templates in your model.You can measure the downtime and the number of outages over a given time period in relation to theSLAs for your organization. For more information about SLA rules, see the TBSM Service ConfigurationGuide.

Chapter 8. TBSM service model configuration overview 57

9 Set permissionsFor users and user groups, you can define the view and edit permissions for a given service template orservice instance. For example, if you have 10 service models, you can set user group permissions to viewand edit only two of the models. You use the Dashboard Application Service Hub Users and Groups tasksto manage permissions for pages and portlets. To manage object level permissions, use the Security tabin the service and template editors.


Chapter 9. TBSM console overviewThis topic describes the TBSM default pages and common portlet buttons.

In the left navigation pane, the default IBM Tivoli Business Service Manager (TBSM) console consists ofdefault pages: Service Administration, Service Configuration, Service Availability, and the Time WindowAnalyzer page. Your permissions control which page you can view and use.

The default Service Administration page has the following portlets:

Note: The Service Administration page will not be part of subsequent TBSM releases. Use the ServiceConfiguration page to configure your services models.

• Service Navigation portlet on the upper left side shows summary information about service templates,service instances, views, and data. The templates and services are listed in trees.

• Service Editor on the upper right side shows a graphical service-dependency model and custom viewdefinitions and lets you configure your service templates and service instances.

• TBSM Charting portlet on the lower left side under the Service Navigation portlet shows a chart thatsummarizes the events that affect a given service model. This feature will not be part of subsequentTBSM releases.

• Service Details portlet on the lower right side under the Service Editor shows detailed informationabout the events that affect a service model, as well as data on service level agreements and templaterules.

The default Service Availability page has the following portlets:

• Service Tree portlet on the upper left side shows summary information about the service instances thatare listed in trees.

• Urgent Services portlet on the lower left side under the Service Tree portlet shows a list of servicesthat have a status defined as urgent.

• Service Details portlet on the lower right side under the Service Viewer shows detailed informationabout the events that affect a service model as well as data on service level agreements and templaterules. This feature will not be part of subsequent TBSM releases.

The default Service Configuration page has two portlets:

• Service Navigation portlet on the left side shows summary information about service templates,service instances, views, and data. The templates and services are listed in trees.

• Service Editor on the right side shows a graphical service-dependency model and custom viewdefinitions. Use the Service Editor to configure your service templates and service instances.

Note: If you are building services or configuring templates, this page is more efficient because it loadsfaster than the Service Administration page.

The default Time Window Analyzer page can be used to show service trends over time. It can comparetrends between different services or compare trends for a service against recent historical data for thesame service. The Time Window Analyzer can also show service affecting events in relation to the servicetrends. When you configure the view you select the following options:

• One or more services where you want to show key performance indicator (KPI) values for a given timeperiod

• A KPI value you want to plot over time. This value is a numeric rule that is part of the service's template.• An Overlay that shows when the service status changed over the time period.• Other recent time periods showing the same data. The chart plots the data for the recent time period on

top of the chart for the most recent time period. The Time Window Analyzer contains two elements:

– The Compare frame lets you select the services you want to view in the chart, and history for thoseservices.


– The Chart frame lets you select the KPI you want to plot and an Overlay you want to display in thechart.

From the left navigation pane, expand Troubleshooting and Support > Tivoli Business Service Manager,there are three default TBSM Troubleshooting pages:

• System Status• Audit Log Records• Audit Log Configuration

For more information, see the "Getting started with diagnosis" section in the IBM Tivoli TroubleshootingGuide.

These portlets are explained in more detail in the sections that follow.

Common portlet buttons

This section describes the common refresh and navigation buttons for portlets in the TBSM console.

Clicking the Expand button at the top right of the four portlets exposes the buttons that control how theseportlets display.

Table 6 on page 61 describes the common refresh and navigation buttons.

Note: Not all buttons will be available on every portlet.


Table 6. Common Refresh and Navigation Buttons

Button Button name Description

Edit Options Clicking the Edit Options button opens amenu with the options to Restore,Minimize,and Maximize.

Clicking the Maximize button maximizes theportlet to the size of the page. ClickingRestore will return the portlet to normalsize.

Clicking Minimize hides the portlet'scontents. Clicking Restore returns theportlet to normal.

Note: If you click Minimize in a maximizedview, the portlet returns to normal size andits contents will be hidden. If you clickMaximize in a minimized view, the portletexpands to the size of the page, showing itscontents.

Important: Save all changes before clickingRestore or any changes you made will belost.

On some portlets, the Edit options menuhas two additional options: Personalize orEdit Shared Settings. Personalize onlychanges settings for the current user. EditShared Settings changes settings for allusers.

Note: After you have set your ownpreferences by selecting Personalize, anyfuture changes to the Default Preferenceswill no longer apply. If you want similarpreferences as those made by theAdministrator after configuring yourpreferences, you will have to manuallyPersonalize to make the correspondingchanges.

For more information see the IBMDashboard Application Services HubAdministration Guide and the IBM TivoliBusiness Service Manager: CustomizationGuide.

Chapter 9. TBSM console overview 61

Table 6. Common Refresh and Navigation Buttons (continued)

Button Button name Description

Refresh Clicking this button reloads the display for agiven portlet. For example, whenever youchange your service instances or templatesin the Service Editor, click the Refreshbutton in the Service Navigation portlet toshow the changes. Also, clicking this buttonreturns the portlet to the default view. Forexample, in the Services tree, if you haveexpanded elements of the tree, clicking thisbutton closes them.

Note: If you click the Refresh button in theService Editor, it refreshes to the defaultview. If you did not set a starting instance, itreturns to the splash screen.

Help Clicking this button allows you to accesshelp for the portlet.


Chapter 10. Service Navigation portletThis topic describes the drop-down menu in the Service Navigation portlet.

The Service Navigation portlet, on the upper left of either the Service Administration or the ServiceConfiguration page contains a drop-down menu with the objects:

• Services• Templates• Service Component Repository• Data• Data Fetcher

Templates is open by default.

Right-click menus are accessible from the Service Navigation portlet. The menus give you quick accessto many of the editing functions in TBSM.

ServicesThis topic describes the elements in Services in the Service Navigation portlet.

Services in the Service Navigation portlet contains trees of service-dependency models that have beenconfigured for TBSM. The service instances you see depend on your user and group permissions.

To see the full tree, click the plus symbols to the left of the services. To see a view of a service ortemplate in the Service Editor, click the name of the service or template.

Table 7 on page 63 describes the Services elements.

Table 7. Services elements

Services element Element type Description

Create NewService button

Click this button to create a service. When you clickthis button, a blank Edit Service tab opens in theService Editor. Enter the parameters for the newservice instance and click the Save button.

Delete Servicesbutton

Click this button to select the services you want todelete. When you click this button, the DeleteInstances tab opens in the Service Editor.

In the Service Editor, select the services you want todelete and click the Delete button.


Table 7. Services elements (continued)

Services element Element type Description

Search button Click this button to search for services. When youclick the Search button, a new window opens. Entera string in this field and click the Search button tosearch for services that contain the string youentered. The system displays the search resultsalphabetically by display name and service name.

For example, if you want to find all the services withnames like webserver1, enter webs in the Searchfield.

Important: Only services that are persisted willreturn as search results. The search function will notfind services that are not persisted.

Tree TemplateEditor button

Click this button to open an editor where you cancreate, design, and edit tree templates.

Help button Click this button to access help.

TemplatesThis topic describes the elements in Templates in the Service Navigation portlet.

Templates in the Service Navigation portlet contains a tree of service templates that have beenconfigured for TBSM. The service templates you see and the actions you can perform depend on your userand group permissions.

To see the full tree, click the plus symbols to the left of the templates. A list of templates is displayed. Todisplay a template in the Service Editor, click the template name in the tree. These buttons are disabled ifyou do not have permission to use them.

Table 8. Templates elements

Template element Element type Description

Create NewTemplate button

Click this button to create a service template. When youclick this button, a blank Edit Template tab opens inthe Service Editor. Enter the parameters for the newservice template and click the Save button.

Delete Templatesbutton

Click this button to select the templates you want todelete. When you click this button, the DeleteTemplates tab opens in the Service Editor. In theService Editor, select the templates you want to deleteand click the Delete button.

Configure EventEnrichment button

Click this button to configure Event Enrichment. EventEnrichment allows you to monitor an event source fornew events. Impact "catches" new and updated alertsas they are sent to the ObjectServer, and then goes toone or more external data sources to correlateinformation in the alerts with business data. For moreinformation, see the topic in the Tivoli® Netcool/ImpactSolutions Guide.


Table 8. Templates elements (continued)

Template element Element type Description


Service Component RepositoryThis topic describes the Service Component Repository in the Service Navigation portlet.

The services in the Service Component Repository (SCR) are required for the optional Discovery LibraryToolkit. When you import the SCR services and templates, TBSM creates a set of services and servicetemplates. The default SCR services and service templates enable TBSM to discover and create newservices from Discovery Library data retrieved by the Toolkit. The discovered services display in theService Component Repository, accessed from the Service Navigation drop-down list. To monitor theseservices, you must create a dependency between the SCR service and one of the services in the Servicestree.

Note: The information that is displayed for the Service Component Registry in the Services tree reflectsthe last validation of top level resources such as AppServers, Oracle, and CICS. The Service ComponentRegistry does not update the Services tree in the same way as it updates the resources that are displayedthe Services tab.

CAUTION: Do not alter these services. Do not alter any of the service templates with a prefix ofSCR or BSM. Altering these services and templates may cause the Discovery Library Toolkit tomalfunction. For more information about setting up the Discovery Library Toolkit and working withSCR services, see the IBM Tivoli Business Service Manager: Administrator's Guide and the IBMTivoli Business Service Manager: Customization Guide.

DataThis topic describes the elements in Data in the Service Navigation portlet.

Data in the Service Navigation portlet shows a list of data sources that provide data for your servicemodel. You can only configure data sources if you have administrator permissions for TBSM. When youedit or add a data source, the Edit tab for data sources is displayed in the Service Editor. The tab forcreating or editing data sources opens when you click the 'Create New Data Source' button in the ServiceNavigation portlet or click on an existing data source.

Table 9 on page 65 describes the Data elements.

Table 9. Data elements

Data element Element type Description

Refresh button Click this button to refresh the listof data sources. If you created adata source in the Edit tab for datasources, click the Refresh buttonin Data to update the display toshow the new data source.

Create New Data Sourcebutton

Click this button to create a datasource. When you click this button,a blank New Data Source tabopens in the Service Editor. Enterthe parameters for the new datasource and click the Save button.

Chapter 10. Service Navigation portlet 65

Table 9. Data elements (continued)

Data element Element type Description


Table 10 on page 66 describes the Data right-click menus. These options are disabled if you do not havepermission to use them.

Table 10. Right-click menu options for Data Sources

Right-click menu option Description

Edit This right-click option opens the Edit tab in theService Editor, where you can edit a data fetcher.

Delete This right-click menu option deletes the datasource.

Data FetcherThis topic describes the elements in Data Fetcher in the Service Navigation portlet.

The Data Fetcher in the Service Navigation portlet shows a list of data fetchers that have beenconfigured to deliver data periodically from databases. The Data Fetcher allows you to query a databaseand use the data to affect the status of a service model. The data can also be used to auto-populate theservice model.

You can define a data fetcher for the following types of databases:

• Oracle• Sybase• MS-SQL• MySQL• Informix• DB2

Table 11 on page 66 describes the Data Fetcher elements. These buttons are disabled if you do nothave permission to use them.

Table 11. Data Fetcher Elements

Data Fetcher element Element type Description

Refresh button Click this button to refresh thelist of data fetchers. If youcreate a data fetcher in theData Browser, click theRefresh button in the DataFetcher to update the displayto show the new fetcher.

Create New Data Fetcherbutton

Click this button to open theNew Data Fetcher tab in theService Editor, where you canconfigure a new data fetcher.

Help button Click this button to accesshelp.


Table 12 on page 67 describes the Data Fetcher right-click menus. These options are disabled if you donot have permission to use them.

Table 12. Right-click options for Data Fetchers

Right-click menuoption

Description

Edit This right-click option opens the Edit tab in the Service Editor, where you canedit a data fetcher.

Fetch Now This right-click option runs the data fetcher and the resulting events areprocessed by the server.

Show log This right-click option opens a log for the data fetcher activity in the ServiceEditor.

Enable/Disable This right-click option disables/enables the data fetcher.

Delete This right-click option deletes the data fetcher.

The Status column indicates the status of the data fetcher. For example, a green status indicates a datafetcher is working correctly.

Chapter 10. Service Navigation portlet 67

Chapter 11. Service EditorThis topic describes the Service Editor portlet.

When you click a service, service template, data source, or data fetcher in the Service Navigation portlet,a detailed display opens in the Service Editor, either a graphical view or an editor depending on what youselected. Some of these options have no graphical view.

The toolbar for each view or editor contains tools appropriate for that tab.

Note: If you click the Refresh button in the Service Editor, it refreshes to the default view. If you did notset a starting instance, it displays the "No service currently selected" message. Select an instance, and itwill display in the Service Editor.

Right-click menus are accessible from the Service Editor. The menus give you quick access to many of theediting functions in TBSM.

Note: By default, the Service Editor portlet, which has only edit options, is featured on the ServiceConfiguration and Administration pages.

Edit tabsThis topic describes the Edit tab in the Service Editor.

The Edit tab let you configure your service templates, service instances, service component repository,data sources, and data fetchers in TBSM.

Edit Service tab toolbar

Table 13 on page 69 describes the Edit tabs' tools.

Table 13. Edit tab toolbar

Button Name Description

Save button Click this button to save the information that you entered inone of the tabs in an editor. You must save your entries ineach tab before continuing to the next one.

Help button Click this button to access help for the tab.

Refresh button Click this button to reload the last saved values for a giventab. (Not applicable to every editor.)

Edit tab editorsThis topic describes the Edit tab editors in the Service Editor.

The Edit tab contains one of the editors, depending on what you selected from the Service Navigationportlet. These tabs are described in the following sections.

Edit Service tab

When you click a service or view, or create a service or view, the Edit Service tab is displayed. Youconfigure template assignments, dependent services, and other attributes for the selected service in thistab.


Edit Template tab

Service templates define how services respond to external data and the status of other services. You canassign (or tag) a service with a template or templates. When you select a service template or create atemplate, the Edit Template tab is displayed. You configure rules, output expressions, and otherattributes for the selected service template in this tab.

Edit Data Source tab

When you click a data source or create a data source, the tab for creating or editing data sources isdisplayed in the Service Editor. You set up a data source to access additional data about your services.You can only configure data sources if you have administrator permissions for TBSM. In the Edit DataSource tab, you enter the information you need to access the data in a database such as an ObjectServeror an SQL database.

Edit tab for Data Fetcher

When you click a data fetcher or create a data fetcher, the Edit Data Fetcher tab opens in the Edit tab ofthe Service Editor. You set up data fetchers to query external databases and use the returned data toaffect the status of the service model.

Delete tab

When you click a Delete button for services or templates, the appropriate Delete tab is displayed in theService Editor. Select the item or items you want to delete from the Delete tab and click the red Deletebutton in the Delete tab toolbar.


Chapter 12. Charting Summary portletThis topic describes the Charting Summary portlet.

The Charting Summary portlet under the Service Navigation portlet shows a chart that displaysinformation about events related to your service model. By default, it shows a summary for all the eventsin the ObjectServer. If you click a service in the Services tree, the chart shows a summary of events for allchild services of the selected item.

Note: This portlet is featured on the Service Administration page, not on the Service Availability.


Appendix A. Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer theproducts, services, or features discussed in this document in other countries. Consult your local IBMrepresentative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility 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 thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions 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 APARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade 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 thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part ofthe 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 withoutincurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.


Such information may be available, subject to appropriate terms and conditions, including in some casespayment of a fee.

The licensed program described in this document and all licensed material available for it are provided byIBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or anyequivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, theresults obtained in other operating environments may vary significantly. Some measurements may havebeen made on development-level systems and there is no guarantee that these measurements will be thesame on generally available systems. Furthermore, some measurement may have been estimatedthrough extrapolation. Actual results may vary. Users of this document should verify the applicable datafor their specific environment.

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

All statements regarding IBM's future direction or intent are subject to change or withdrawal withoutnotice, and represent goals and objectives only.

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

If you are viewing this information in softcopy form, the photographs and color illustrations might not bedisplayed.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks 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.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks ortrademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a 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 theUnited States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other product and service names might be trademarks of IBM or other companies.


Index

Aadding JDBC drivers 43administrator

default user 24advanced installation 27architecture 11authentication

user registry 21

Bbooks, See publications

CCharting

Event Summary portlet 71common portlet buttons 60conventions

typeface 3core library 1Creation Planning

Service 55

DDashboard server

LDAP configuration 23data 65data fetcher

Delete tab 70elements 66right-click menus 66

Data serverinstallation worksheet 38

data sourceselements 65identifying 56right-click menus 65

DB2install TBSM schema 29installing on UNIX 29

default groups 24

EEdit Data source tab 70Edit Service tab 69Edit tab

editors 69toolbar 69

Edit Template tab 70education, See Tivoli technical trainingEIF probe

installing 48

environment variables, notation 15Event Summary portlet 71events

user permissions 24

Ffeatures

new for 6.2.0 7

GGraphical User Interface 59groups

default 24user 24

IIncoming Status Rules

creating 56installation

advanced 27notes 18simple 27

installation user 18

LLDAP

Dashboard server 23

Mmanuals, See publications

NNetcool/Impact

install on TBSM host 19notation

environment variables 15path names 15typeface 15

Numerical Aggregation Rulescreating 56

Numerical Formula Rulescreating 56

OObjectServer

permissions for viewing events 24online publications

accessing 2

Index 75

ordering publications 3

Ppermissions

setting for user and groups 58users and groups 24

product library 1publications

accessing online 2ordering 3

Rregistry

user authentication 21requirements

system 17roles

user 24

SService Component Repository 65Service Level Agreement (SLA)

creating 57service model

configuration overview 55structure and templates 56

Service Navigation portlet 63service templates

creating 55service trees

creating custom service trees 57creating custom service views 57

servicescreating 57elements 63names: invalid characters 57planning 55Service Editor 69

simple installation 27SLA 57SQL database DSA 43

TTBSM

core library 1overview of the graphical user interface 59

Templates tab 64terminology 2Tivoli

integrated applications 13Tivoli Directory Server

installing 23LDAP configuration 23

Tivoli Documentation Central 2Tivoli Event Integration Facility probe

uninstalling 50verifying installation 48

Tivoli technical training 3training, Tivoli technical 3

typeface conventions 3

Uuninstall

TBSM Dashboard Server 51TBSM Data Server 51TBSM Database Configuration Server 31

UNIXDB2 installation 29

useradministrator default 24groups and roles 24

usersexternal authentication 21registry 21

Vvariables, notation for 15


IBM®

Part Number:Product Number:

SC27-8785-02

(1P) P

/N:

version 6.2.0 business service manager - ibm...provides reference information about the optional...

Documents