Chapter 2. Components and functions 39
2.2.2 Installation directory structure
IBM Tivoli Business Systems Manager installed on Windows machines provides
the directory structure shown in Figure 2-3. This directory structure typically is
created under TivoliManager and shared as Access1$ for easy access by other
IBM Tivoli Business Systems Manager servers.
Figure 2-3 IBM Tivoli Business Systems Manager Windows directory structure
Some of these directories will not be present on all servers. The component
installed influences the directories installed. The following are used in the
directories:
Autotrace Configures automatic tracing for Common Listener and
Console Server java processes.
bin Main executable path for IBM Tivoli Business Systems
Manager. This must be in the system path.
CommonListener Common listener installation directory.
ConsoleServer Console server installation directory.
Data Data directory used for Tivoli Information Management for
z/OS integration.
Dataproducts Directories where Tivoli Manager for products definition is
stored.
40 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
DataQueues Queue files directory where the enqueue proxy server
writes files.
DataRules Rule directory that is used by the ASIMVSUploadRule
server. Rule files have the .clp extension.
Lang Language-specific locale for character translation tables.
Logs Main log directory, shared as Logs$
man Not used.
Mgmt Directory for health monitor program and output files. This
directory is shared as Mgmt$
sql Directory for storing SQL queries.
TDS Topology Display Services: the installation path for event
enablement and task server.
xdfparser Parser script for decoding Application management
instrumentation definitions into IBM Tivoli Business
Systems Manager.
2.2.3 Windows registry structure
Most of the settings for IBM Tivoli Business Systems Manager services are
stored in the Windows registry under the following key:
HKEY_LOCAL_MACHINESoftwareAccessible Software, Inc.Access11.0
A sample registry tree is shown in Figure 2-4 on page 41.
Chapter 2. Components and functions 41
Figure 2-4 Registry tree
The main folders in this registry structure are:
Components Where most of the services’ settings are stored; however,
the setting for services from the propagation servers are
not located here.
Settings The location of the global settings for this server’s IBM
Tivoli Business Systems Manager in this server.
SetupDefaults The values of the installation parameters that we enter
from the installation dialogs.
The Settings folder has a hierarchical design, so all information is retireved from
a branch’s innermost folder. If it does not exist there, it will be retrieved from the
folder that is in the next level. As an example, we will find the log file prefix, log
level, and log directory from the registry tree for the MVS IP OS Listener for
SC66, as shown in Figure 2-5 on page 42. All registry paths are relative to
HKLMSOFTWAREAccessible Software, IncAccess11.0:
? The log file prefix (MVSL_SC66) is retrieved from
ComponentsASIMVSIPOSListenerSvcInstancesSC66SettingsLog, as that
42 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
is the innermost setting with that value. If the listener has not been associated
with any instance, it will use the setting in
ComponentsASIMVSIPOSListenerSvcSettingsLog, which is MVSIP.
? The LogLevel information for all MVS IP OS Listeners is retrieved from
ComponentsASIMVSIPOSListenerSvcSettingsLog, as it cannot be found
on the innermost Setting in
ComponentsASIMVSIPOSListenerSvcInstancesSC66SettingsLog.
? The Log directory is not present in either
ComponentsASIMVSIPOSListenerSvcInstancesSC66SettingsLog or
ComponentsASIMVSIPOSListenerSvcSettingsLog; therefore it is retrieved
from SettingsLog path.
Figure 2-5 Hierarchical setting
Another important setting is the database setting in SettingsDB, as shown in
Figure 2-6 on page 43. It contains the database access information that is used
Chapter 2. Components and functions 43
by some programs to gain access to the database. This key contains the
database system administrator (sa) password.
Figure 2-6 Database setting
2.2.4 Log files
Log files for the IBM Tivoli Business Systems Manager processes are very
important for understanding how these processes work and for debugging if a
problem occurs. Each process in IBM Tivoli Business Systems Manager
generates log files. Most of these files are stored under TivoliManagerlogs, and
their settings are stored in the registry, as shown in Figure 2-5 on page 42.
The list of standard log files is provided in Table 2-2.
Table 2-2 TBSM services log files
Process name Log prefix
ASIDBValidater
Tivoli BSM Database Validater
-
ASIPADispatcher
Tivoli BSM Propagation Agent Dispatcher
PD
ASIEnqueueProxyServer
Tivoli BSM Enqueue Proxy Server
EPS
ASIRemoteExecution Server
Tivoli BSM Remote Execution Server
RX
PAgent.exe PA
ASIApplicationSvc
Tivoli BSM Application Server
AS
ASINotificationSvc
Tivoli BSM Notification Server
NS
ASIMVSIPOSListenerSvc
Tivoli BSM MVS IP Listener
MVSIP
MVSL_nnnn_
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.