Configuration export and import

6

6.1 Startup and shutdown

Starting and stopping IBM Tivoli Business Service Manager is a process that has to be performed in the correct order. This allows all four components to run and shut down properly.

򐂰 The order of starting the IBM Tivoli Business Service Manager components is:

a. Start IBM Tivoli Netcool Common License Server:

• UNIX: $NCHOME/license/bin/nc_start_license

• Windows: net start "NCO Flex License Manager"

b. Start IBM Tivoli Netcool/OMNIbus:

• UNIX: $OMNIHOME/bin/nco_objserv &

• Windows: net start "Netcool OMNIbus Object Server"

c. Start IBM Tivoli Netcool Security Manager:

• UNIX: $NCHOME/security/bin/ncsm_server &

• Windows: net start "Netcool Security Manager Server"

d. Start IBM Tivoli Business Service Manager:

• UNIX: $NCHOME/bin/rad_server

• Windows: net start "Netcool Postgres Database"

net start "Netcool GUI Foundation Server"

򐂰 To test the IBM Tivoli Business Service Manager components, use the following commands:

– License Server: Use the command nc_print_license under

$NCHOME/license/bin.

– Security Manager: Use the command ncsm_status under

$NCHOME/security/bin.

– IBM Tivoli Netcool/OMNIbus: Use the command nco_ping <name> under

$NCHOME/omnibus/bin.

– PostgreSQL database: Use the command rad_db status under

$NCHOME/bin.

򐂰 The order of stopping the IBM Tivoli Business Service Manager components are:

a. Stop IBM Tivoli Business Service Manager:

• UNIX: $NCHOME/bin/rad_shutdown

• Windows: net stop "Netcool GUI Foundation Server"

net stop "Netcool Postgres Database"

b. Stop IBM Tivoli Netcool Security Manager;

• UNIX: $NCHOME/security/bin/ncsm_shutdown

• Windows: net stop "Netcool Security Manager Server"

c. Stop IBM Tivoli Netcool/OMNIbus:

• UNIX: $OMNIHOME/bin/nco_sql -S NCOMS -U root -P ""

alter system shutdown go

Exit

• Windows: net stop "Netcool OMNIbus Object Server"

d. Stop IBM Tivoli Netcool Common License Server:

• UNIX: $NCHOME/license/bin/nc_stop_license

• Windows: net stop "NCO Flex License Manager"

6.2 Test event

The rad_sendevent command can be used to send test events to the IBM Tivoli Business Service Manager ObjectServer so that one can confirm that the services in the model respond to service-affecting ObjectServer events properly.

The command is located in $NCHOME/bin/ Issue the rad_sendevent command using the following syntax:

rad_sendevent <host> <port> <userid> <password>

The parameters are:

host Name of host machine running the ObjectServer monitored by IBM Tivoli Business Service Manager.

port Port number for the ObjectServer monitored by IBM Tivoli Business Service Manager.

userid The user name needed to access the ObjectServer.

password Password for the user ID. Enter "" for no password.

The process is:

1. After issuing the rad_sendevent command, a READY prompt will appear.

2. Enter the field name, press Enter, enter the field value on the next line, and press Enter again.

3. When you finish entering the field name and value pairs for an event, press the Enter key twice.

4. You can send another event immediately or press Ctrl-c to exit.

Example 6-1 shows the execution of the rad_sendevent command.

Example 6-1 SendEvent example

[Netcool@localhost bin] rad_sendevent localhost 4100 root ‘’

NOTE: rad_sendevent is to be used for testing purpose ONLY. It is not a substitute for the Generic Probe as it has no rules files and is not scalable

READY Summary

Ticket Bar Chart Dummy Event AlertGroup

sending: insert into alerts.status values (‘’,0,...

^C

6.3 IBM Tivoli Netcool/OMNIbus update

IBM Tivoli Business Service Manager modifies the IBM Tivoli Netcool/OMNIbus schema using the tbsm_db_update.sql file. Make sure that the additional fields are also imported into the alerts.status table and an additional table called alerts.service_deps is added to the schema of the ObjectServer. This update is being done by the installer at installation time, but can be run manually also.

򐂰 Verify that the tbsm_db_update.sql file is located in

$NCHOME/guifoundation/webapps/sla/install/tbsm_db_update.sql.

򐂰 Modify the IBM Tivoli Netcool/OMNIbus ObjectServer schema by issuing the following command:

cat $NCHOME/guifoundation/webapps/sla/install/tbsm_db_update.sql |

$OMNIHOME/bin/nco_sql -server <servername> -user <username>

-password <password>

The parameters are:

servername Name of the ObjectServer for IBM Tivoli Business Service Manager

username ObjectServer user name password ObjectServer password

6.4 XMLconfig and CSS modification

You can manually edit the XML and CSS files that are located in the

$NCHOME/guifoundation/webapps/sla/av/xmlconfig and

$NCHOME/guifoundation/webapps/sla/av/css directories. If you modify any of these files, you have to issue the rad_reinitcanvas command so that you see the changes in the IBM Tivoli Business Service Manager Web GUI without having to restart the RAD server.

To edit the files, perform the following steps:

1. Edit any file manually under the following directories:

$NCHOME/guifoundation/webapps/sla/av/css

$NCHOME/guifoundation/webapps/sla/av/xmlconfig 2. Execute the following commands:

– UNIX: $NCHOME/bin/rad_reinitcanvas

– Windows: %NCHOME%/bin/rad_reinitcanvas.bat 3. Open the service tree to see the changes.

6.5 Configuration export and import

You can export and import IBM Tivoli Business Service Manager configuration as follows:

1. IBM Tivoli Business Service Manager provides a command called

rad_radshell, which allows you to export or import a service configuration using a radshell function so that services are configured successfully without having to manually create them again. You can easily move a service configuration from one IBM Tivoli Business Service Manager server to another one.

2. To export data on the IBM Tivoli Business Service Manager server with the existing services configured, use the radshell export function, as shown in Figure 6-1.

Figure 6-1 Rad_radshell

Perform these steps:

a. Execute $NCHOME/bin/rad_radshell.

b. When the prompt changes to radshell>, enter export ();.

c. Press Enter.

d. When you are finished exporting, enter exit ();.

e. Press Enter.

All of the service templates, services, data fetchers, and data sources are now written to a file named export.radsh in the

$NCHOME/guifoundation/webapps/sla directory.

3. Copy the export.radsh file into the $NCHOME/guifoundation/webapps/sla directory of the IBM Tivoli Business Service Manager server to which you want to import the services.

4. Import the file into that IBM Tivoli Business Service Manager server and enter the following command:

cat export.radsh | $NCHOME/bin/rad_radshell

The export.radsh command only exports the database related objects. The user interface customization, such as custom canvases, icons, images, or viewpoints, must be exported manually from the file system. The export.radsh command also allows selective export for specific parts of the service tree by using the Service Instance name as the argument for the export.radsh command to export all the sub trees.