Chapter 9. IBM Tivoli NetView integration 293
9.3.2 Installing the TBSM part of the adapter
To process and integrate the data sent from NetView to IBM Tivoli Business
Systems Manager, the IBM Tivoli Business Systems Manager database server
requires some additional information. The IBM Tivoli Business Systems Manager
adapter package contains one single archive, nvlaunch.tar. On the IBM Tivoli
Business Systems Manager database server, untar the file into the
ivolimanager directory. Extracting nvlaunch.tar will place the following files
under yout ivolimanager directory:
? .in
vlaunchconfig.sh
? .sql
etviewlaunch.upg
? .sqlLookupNetViewURLs.sqi
? .sql\_LookupNetViewURLs.sql
The .in
vlaunchconfig.sh file needs some customization. Open the file with a
text editor and locate the lines shown in Example 9-5. Replace the XXXXX
placeholder with the correct values of your database server name, the SQL
username, and the SQL password. After making the chages, save the file. This
finishes the IBM Tivoli Business Systems Manager side configuration.
Example 9-5 nvlaunchconfig.sh customization
# Replace XXXXX with the name of the TBSM database server
SQLSERVER=ibmtiv5
# Replace XXXXX with the name of the SQL Server user account
SQLUSER=sa
# Replace XXXXX with the password for the SQL Server user account
SQLPWD=sa_ibmtiv5
9.4 NetView adapter configuration
Before the IBM Tivoli Business Systems Manager adapter is able to send any
information to NetView, a few configuration files must be customized on the
NetView server as they were on the IBM Tivoli Business Systems Manager
database server. You can find all the relevant configuration files under
/usr/OV/conf. The examples in this section contain only the relevant lines
requiring changes during the adapter configuration. For complete listings of the
configuration files, refer to “NetView adapter configuration files” on page 566.
1. Open /usr/OV/conf/nvid.conf. This file holds unique information about the
NetView site. This enables IBM Tivoli Business Systems Manager to work
with multiple NetView managers from different locations as well as with two
NetView managers per site in a fallover configuration. Table 9-1 on page 294
explains the keywords used in nvid.conf.
294 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
Table 9-1 nvid keywords
With the information provided in the table, we customized the nvid.conf file for
the NetView server being used in our lab environment as shown in
Example 9-6.
Example 9-6 nvid.conf
nvid=TI7043TBSM
networkid=NV0
primaryURL=capecod.itsc.austin.ibm.com.ibm.com:8080
secondaryURL=backupnetview.ibm.com:8080
contact=Peter Glasmacher
description=The coolest NetView on earth
2. The next file to change is called /usr/OV/conf/topxlistener.conf. For now,
specify your own address and the address of the node where the IBM Tivoli
Business Systems Manager common listener is executed. Later on in section
9.6, “Troubleshooting the environment” on page 305, we will access the file
again. Change entries in this file in two places:
a. Look for the section transport base properties and replace any
occurence of localhost with the fully qualified ip name of your NetView
server.
b. Then look for the section only for client and replace the localhost
entry in the transport.server.ip.address field with the fully qualified IP
name of the node where the IBM Tivoli Business Systems Manager
common listener gets executed.
Keyword Comment
NVID Reserved for future use. Must not exceed 15 characters. No
spaces allowed.
NetworkID This identifier is used by the IBM Tivoli Business Systems
Manager adapter. It is appended to all IBM Tivoli Business
Systems Manager object instances and uniquely identifies all
the objects from each side. The value should be significantly
shorter than NVID, for example NV0. It is limited to the
alphanumeric character set A-Z,a-z,0-9, no spaces.
PrimaryURL This is the IP host name and the port for the NetView Web
server running on this node. Must be entered in the form
<hostname>:port where hostname is the fully qualified host
name and port is the listener port of the Web server (normally
8080).
secondaryURL Specifies a backup NetView server that shares the same
nnid.conf file
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.