Chapter 1. Certification overview
3.4 Verification
3
3.1 Preparation
We discuss the preparation for Windows and UNIX/Linux separately.
3.1.1 Windows preparation
The installation process in Windows requires:
The installation must be done by an administrator or someone whose permissions include:
– Act as part of the operating system – Logon as a service
The user performing the installation must have network access and have the sharing and security model for local accounts set to Classic - local users authenticate as themselves. To verify or set this policy setting:
– Select Start→ Control Panel→ Administrative Tools→ Local Security Policy.
– Browse to Security Settings→ Local Policies→ Security Options.
– Locate the policy Network Access: Sharing and security model for local accounts and change the setting to Classic - local users authenticate as themselves.
The user ID that IBM Tivoli Business Services Manager V4.1.1 is installed under cannot be a domain user ID.
Ensure that the Secondary Logon service is running.
Ensure that the Server service is running.
Ensure that the computer is on a network and that it has a valid IP address.
If a firewall is running on the computer, installation issues could occur. Stop the firewall before installing IBM Tivoli Business Service Manager and then restart the firewall after installing IBM Tivoli Business Service Manager.
The PostgreSQL user must have Log on locally rights. This occurs
automatically if the user is created on a local computer. This does not occur automatically if the user is created on a domain and has Run as Service rights.
IBM Tivoli Netcool/OMNIbus ObjectServer is started using a command line and it runs in a minimized window. Closing this minimized window causes IBM Tivoli Netcool/OMNIbus to stop running and the IBM Tivoli Business Service Manager program to stop working.
Do not use Terminal Services to install the IBM Tivoli Business Service Manager program. The installation must have the console, or Terminal Services installations could fail.
3.1.2 UNIX/Linux preparation
Before starting the installation of IBM Tivoli Business Service Manager V4.1.1, you must perform these steps:
1. Create an IBM Tivoli Business Service Manager user. In UNIX, this is a local non-root user ID with shell capabilities. In Windows, this is a user that is a member of the local administrator group, not a user that is a member of the domain administrator group. The creation of the user is shown in
Example 3-1.
Example 3-1 IBM Tivoli Business Service Manager user ID creation on Linux [root@localhost /]# useradd tbsmadm
[root@localhost /]# groupadd ncoadmin [root@localhost /]# vi /etc/group ncoadmin:x:501:root,tbsmadm
2. Create the installation directory, as shown in Example 3-2.
Example 3-2 IBM Tivoli Business Service Manager installation directory on Linux [root@localhost /]# mkdir /opt/netcool
[root@localhost /]# chown -R tbsmadm:ncoadmin /opt/netcool
3. Modify the user ID profile (UNIX/Linux only) and add the lines in Example 3-3 to the non-root user .bash_profile file.
Example 3-3 Edit user ID profile on Linux NCHOME=/opt/netcool/
OMNIHOME=/opt/netcool/omnibus/
LANG=C
PATH=$PATH:$OMNIHOME/bin:$NCHOME/install:$NCHOME/bin/
LD_LIBRARY_PATH=$NCHOME/platform/linux2x86/lib/:$LD_LIBRARY_PATH
Note: The LD_LIBRARY_PATH variable may have different directories, depending on the operating system.
3.2 Installation
This section explains the installation process for IBM Tivoli Business Service Manager V4.1.1. The discussion is described in the following sections:
3.2.1, “Running the installation wizard” on page 48
3.2.2, “Silent installation” on page 67
3.2.3, “Uninstallation” on page 68
3.2.1 Running the installation wizard
The installation wizard is invoked as follows:
1. Run the installation program. In UNIX/Linux, run launchpad.sh, and in Windows, use launchpad.exe. After running the launchpad program, the Welcome window opens, as shown in Figure 3-1.
Figure 3-1 Welcome window
2. In the IBM Tivoli Business Service Manager Welcome window, select Install IBM Tivoli Business Service Manager 4.1.1. Then click Run the Tivoli Business Service Manager 4.1.1 installation program, as shown in Figure 3-2.
Figure 3-2 Install Tivoli Business Service Manager V4.1.1 window
3. The installation process starts. Select the language for the installation program, as shown in Figure 3-3, and click OK.
Figure 3-3 Language selection menu
4. The Welcome page for the IBM Tivoli Business Service Manager installation wizard opens, as shown in Figure 3-4. Read the information and click Next.
Figure 3-4 Welcome window for IBM Tivoli Business Service Manager installation wizard
5. Read the License Agreement shown in Figure 3-5, Click Read non-IBM terms to read the non-IBM terms in the license agreement. Click Print if you want to print the license agreement. Select I accept both the IBM and the non-IBM terms and click Next to continue.
Figure 3-5 License Agreement
6. Figure 3-6 shows the installation directory path. If NCHOME is already set, you cannot change the destination path; otherwise, specify the installation path. The default paths are /opt/netcool (UNIX/Linux) or C:\IBM\Netcool (Windows). Make sure that the user you are running the installation as has write access to the directory. Click Next to continue.
Figure 3-6 IBM Tivoli Business Service Manager installation path
7. Choose the installation type. There are two installation types: Simple and Advanced, as shown in Figure 3-7.
Figure 3-7 Installation type selection
– The simple installation installs all the prerequisite software and uses the default ports and default configuration values. Refer to the “Simple installation” on page 52 for more information.
– The advanced installation installs the IBM Tivoli Business Service Manager V4.1.1 program and asks for all configurable parameters. We recommend this installation option for a production system, as we also recommend installing IBM Tivoli Business Service Manager in a multiple machine setup. Refer to “Advanced installation” on page 54 for more information.
For the setup, the sequence or order that you install the prerequisite software features in is important. Always install the software features in the following order:
1. License Server
2. IBM Tivoli Netcool/OMNIbus ObjectServer 3. Security Manager
4. IBM Tivoli Business Service Manager V4.1.1
Simple installation
The simple installation provides the default values for many different parameters.
It assumes that all software components are installed on a single machine. To use a simple installation, click Next and then consider the following items:
1. If you install on Windows, the installation process asks you to create a Windows user for the postgreSQL service, as shown in Figure 3-8 on page 53. The considerations are:
– The Windows Username is required, and the default is pgservice.
– The Windows Password is optional. The password must conform to password rules set up on the computer for the local user account to be created.
– This Windows user cannot be a user who has administrator rights.
– If an existing account is to be used, the existing account must be local and must have Log on locally and Log on as a service rights.
– Network access: The sharing and security model for local accounts must be set to Classic - local users authenticate as themselves. To verify or set this policy setting:
i. Select Start→ Control Panel→ Administrative Tools→ Local Security Policy.
ii. Browse to Security Settings→ Local Policies→ Security Options.
iii. Locate the policy Network Access: Sharing and security model for local accounts and change the setting to Classic - local users
authenticate as themselves.
– The user must have permission to write to %NCHOME%.
Figure 3-8 IBM Tivoli Business Service Manager Windows user ID creation
2. The installation summary window is shown in Figure 3-9. Click Install to begin the simple installation, using the default configuration values.
Figure 3-9 Summary information window
3. When the installation is completed, check whether there is any error by reviewing the summary information window shown in Figure 3-10, and click Finish.
Figure 3-10 Summary information window
Advanced installation
To follow the advanced installation path, perform the following:
1. After selecting the Advanced installation and clicking Next, choose the components that you want to install, as shown in Figure 3-11 on page 55.
Note: The values in the screen shots in this section are default values that would also be in effect when you use the simple installation. The advanced installation path allows you to modify these values.
Figure 3-11 IBM Tivoli Business Service Manager Advanced installation products
2. If you are installing on a Windows platform, you are prompted to specify a Windows Username and Password for the database service, similar to the Simple installation in “Simple installation” on page 52. The default host name and port in Figure 3-12 are localhost and 5435, respectively.
Figure 3-12 Windows user database creation
3. You can use an existing license server or you can install a license server as part of this installation. Provide the requested license server information in Figure 3-13. The host name default value on UNIX platforms is localhost. The default value on Windows platforms is the name of the computer. License Server Port must be in the range 1241 – 65535. The default port is 27000.
Figure 3-13 License Server configuration
4. You can use the Tivoli Enterprise Console (TEC) product for synchronization between the IBM Tivoli Netcool/OMNIbus ObjectServer in Figure 3-14 on page 57. Provide your Tivoli Enterprise Console Server’s host name. If the Tivoli Enterprise Console server is running on a Windows platform, the default port is 5529; on a UNIX platform, you can use 0 to get the port number from portmapper.
Figure 3-14 Tivoli Enterprise Console Server configuration
5. You must provide the Security Manager Server information for the window shown in Figure 3-15. The default value on UNIX platforms is localhost. The default value on Windows platforms is the name of the computer. All port numbers must be between 1241 - 65535.
– The Security Manager server port default is 1275.
– The Security Manager HTTP port default is 8077.
– THe Security Manager Port Database port default is 5600.
Figure 3-15 Security Manager server configuration
6. There are three authentication sources for Security Manager to use, as shown in Figure 3-16:
– IBM Tivoli Netcool/OMNIbus, the ObjectServer.
– Lightweight Directory Access Protocol (LDAP).
– Active Directory®.
Figure 3-16 Types of authentication sources for Security Manager
7. Depending on the authentication, you can choose:
– The ObjectServer authentication is the default option. To define the ObjectServer authentication, you must supply the name of ObjectServer (NCOMS), server host name, and the access port (default is 4100). See Figure 3-17 on page 59.
Figure 3-17 ObjectServer configuration
– For LDAP authentication, it is necessary to complete the next steps using the information below:
i. Figure 3-18 requests the host name of the LDAP server (it should be configured and running), the port used by the LDAP server (the default is 1275), and the user name and password used to access the LDAP server.
Figure 3-18 LDAP configuration part 1
ii. Figure 3-19 prompts you for the LDAP user and group search patterns.
They must be supplied according to your installation. The values shown are the default values.
Figure 3-19 LDAP configuration part 2
– For Active Directory authentication, it is necessary to complete the following steps:
i. Figure 3-20 on page 61 prompts you for the host name of the Active Directory server, communication port (the default is 389), Global Catalog Host and Port (the default values are gchost and 3268, respectively), Active Directory user ID, and password.
Figure 3-20 Active Directory configuration part 1
ii. Enter the User Search Base information in the fields shown in Figure 3-21. The default is ub. The Group Search Base information default is gb.
Figure 3-21 Active Directory configuration part 2
8. In Figure 3-22, provide the ObjectServer settings that IBM Tivoli Business Service Manager will interface with: ObjectServer Name, ObjectServer host name, and ObjectServer port. The defaults are shown.
Figure 3-22 ObjectServer information
9. In Figure 3-23, provide the Web server information: Web Server Port, Internal Port Used by Server, and Internal Database Port. All ports must be between 1241 - 65535; the default values for the ports are shown.
Figure 3-23 Web server configuration
10.In Figure 3-24, select the role of the Web server that is configured:
– Standalone – Primary – Backup
The Standalone role is the default value selected, and is it must be selected if there is no failover configuration. If there is a failover scenario, you can configure the server as Primary or Backup.
11.The next options are based on the server type.
– For the Primary Web server role, you must provide the Backup Hostname, Backup Web Server Port, Backup Internal Port, and Backup Database Port, as shown in Figure 3-24.
Figure 3-24 Backup Web server information
– For the Backup Web server role, you must provide the primary server host name, Primary Web Server Port, Primary Internal Port used by Server, and Primary Database Port, as shown in Figure 3-25.
Figure 3-25 Primary Web server information
12.Figure 3-26 is where you configure the internal communication port used between the primary and backup servers. This port is also used for utilities such as rad_discover_schema to connect to IBM Tivoli Business Service Manager V4.1.1.
Figure 3-26 Internal communication port
13.Figure 3-27 defines the backup ObjectServer. The information you enter includes the Backup Name, Backup Hostname server, and Backup ObjectServer port.
Figure 3-27 ObjectServer backup information
Note: If you use localhost, you must use it for both the primary ObjectServer and the backup ObjectServer.
14.If you select the Historical Reporting feature, you must provide information about the IBM Tivoli Monitoring Data Warehouse database server. The database type is either DB2 or Oracle®, as shown in Figure 3-28.
Figure 3-28 Historical Reporting configuration
15.In Figure 3-29 on page 67, provide the Warehouse database information. For DB2, the necessary information is:
– Host name and port number (the default is 50000).
– User name and password to access the Warehouse database.
– The database name (the default is WAREHOUS).
– Schema name for data tables (This is case sensitive and is stored in KSY_WAREHOUSE_SCHEMA in the KSYENV file on the ITM server).
Figure 3-29 Tivoli Data Warehouse database configuration
3.2.2 Silent installation
Silent installation is used for automated installation and unattended installation.
To install IBM Tivoli Business Service Manager silently, perform the following steps:
1. Generate the silent installation option file using the command setup -options-template <filename>, in which the file name is the output file, or you can record your wizard options in a response file using the
-options-record parameter.
2. Customize the options in the output file generated in the previous step, or you can use a sample, pre-filled response file from the installation media. There are three pre-filled response files:
tbsminst.rsp Installation response file migrate.rsp Migration response file
probe.rsp EIF probe installation response file 3. Invoke the installation using the option file with the command:
setup -options <filename> -silent
3.2.3 Uninstallation
To uninstall IBM Tivoli Business Service Manager components in your server, perform the following steps:
1. Stop all IBM Tivoli Business Service Manager related processes.
2. In a Windows platform, click Add/Remove Programs in the Control Panel to invoke the IBM Tivoli Business Service Manager uninstallation program; in UNIX/Linux, run uninstaller.bin under the $NCHOME/_uninst directory. Run this command using the user ID that was used to install IBM Tivoli Business Service Manager previously.
3. When all IBM Tivoli Business Service Manager components have been uninstalled, remove the $NCHOME directory. If you are just uninstalling the IBM Tivoli Business Service Manager server, these directories must be removed manually:
3.3 Post installation customization
There are several post installation actions that can be done:
You can set up the UNIX/Linux service for IBM Tivoli Business Service Manager using the createservice.sh command under
$NCHOME/InstallTBSM/service_util. It uses the property file RAD_Service.props in the same directory. You must modify
RAD_Service.props to define the user to start IBM Tivoli Business Service Manager. The contents of RAD_Service.props are shown in Example 3-4.
Example 3-4 RAD_Service.props
# The user ID of the IBM Tivoli Business Services Manager Administrative user.
# This is the user that installed IBM Tivoli Business Services Manager and will be used to
# start all required IBM Tivoli Business Services Manager processes.
TBSM_ADMIN_USER=netcool
# The ObjectServer name. It is currently set to the default,
# but would need to be modified if it has been changed or
# if this is the backup ObjectServer in a failover configuration OBJECTSERVER_NAME=NCOMS
The result of defining the service is shown in Example 3-5 (run from root).
Example 3-5 Running createservice.sh
# $NCHOME/InstallTBSM/service_util/createservice.sh $NCHOME
running: ln -s /etc/rc.d/init.d/tbsm /etc/rc.d/rc0.d/K10tbsm running: ln -s /etc/rc.d/init.d/tbsm /etc/rc.d/rc1.d/K10tbsm running: ln -s /etc/rc.d/init.d/tbsm /etc/rc.d/rc2.d/K10tbsm running: ln -s /etc/rc.d/init.d/tbsm /etc/rc.d/rc3.d/S90tbsm running: ln -s /etc/rc.d/init.d/tbsm /etc/rc.d/rc4.d/S90tbsm running: ln -s /etc/rc.d/init.d/tbsm /etc/rc.d/rc5.d/S90tbsm running: ln -s /etc/rc.d/init.d/tbsm /etc/rc.d/rc6.d/K10tbsm installService returning 0
Starting the IBM Tivoli Business Service Manager suite in UNIX or Linux can be performed by using the script start_tbsm_suite.sh under
$NCHOME/InstallTBSM/service_util. It will start all the installed IBM Tivoli Business Service Manager components in the correct order. To stop them, use stop_tbsm_suite.sh. The execution of these scripts are shown in Example 3-6.
Example 3-6 Start and stop
[netcool@localhost service_util]$ ./start_tbsm_suite.sh Running: /opt/netcool//license/bin/nc_start_license &
Number of License Server processes found = 2 License Server is running, continue...
Enter the name of the ObjectSever to start:
Setting LANG based on platform, before starting OMNIbus Running: /opt/netcool//omnibus/bin/nco_objserv -name NCOMS &
IBM Tivoli Netcool/OMNIbus ObjectServer - Version 7.1
Copyright (C) 1994 - 2005, Micromuse Ltd. All rights reserved.
Server 'NCOMS' initialised - entering RUN state.
Number of ObjectServer processes found = 1 ObjectServer is running, continue...
Number of Security Manager processes found = 2 Security Manager is running, continue...
Running: /opt/netcool//bin/rad_server &
JAVA_HOME is /opt/netcool//platform/linux2x86/jre_1.5.0 JAVA_OPTS is -Dnchome=/opt/netcool/
-Dngfhome=/opt/netcool//guifoundation
-Dncw.home=/opt/netcool//guifoundation/webapps/sla . ..
Starting IBM Tivoli Business Service Manager Server process...
[netcool@localhost service_util]$ ./stop_tbsm_suite.sh Shutting down TBSM server
Stopping IBM Tivoli Business Service Manager Server....
Database on HOST localhost PORT 5435
waiting for postmaster to shut down.... done postmaster stopped
Done!
Stopping ASA server...
Using wait time of 60 seconds
Adaptive Server Anywhere Stop Engine Utility Version 9.0.1.1965
Please wait until the shutdown is completed...Stopped
Done!
Shutting down security service Shutdown completed
Shutting down ObjectServer runtime version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03) Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
(0 rows affected)
Shutting down license service
lmdown - Copyright (c) 1989-2003 by Macrovision Corporation. All rights reserved.
Port@Host Vendors
1) [email protected] netcool
All lmgrds selected...
1 FLEXlm License Server shut down
3.4 Verification
After the installation is finished, use the schema script to verify if IBM Tivoli Business Service Manager alerts are appearing in ObjectServer and you can log into the IBM Tivoli Business Service Manager Web interface. You must have ObjectServer and IBM Tivoli Netcool GUI Foundation Server running. Perform these steps:
1. Run $NCHOME/bin/rad_discover_schema ObjectServer, as shown in Example 3-7. The resulting ObjectServer schema is stored in the
$NCHOME/guifoundation/webapps/sla/install directory as SQL files.
Example 3-7 Running ad_discover_schema ObjectServer
[netcool@localhost]$ /opt/netcool/bin/rad_discover_schema ObjectServer Received 5 parameters
ServerName: blah Username: NULL Policy: DiscoverSchema
|TypeName| -> |'ObjectServer'|
Connecting to server: RAD
DynamicBinding: using url http://localhost:8080/registry/services.
usehttps is null
Trying to connect to server RAD on host 127.0.0.1 on port 1284 Looking up RMI service ...
Connecting to RMI server 127.0.0.1:1284 ...
Connecting to RMI server 127.0.0.1:1284 ...