Test 000-436: IBM Tivoli Business Service Manager V4.1.1 Implementation

Section 1 - Planning

1. Given vendor documentation, customer documentation, and requirements, validate customer environment, so that customer requirements are fulfilled and TBSM is ready to install.
1. Verify Operating Systems
2. Verify OS patches
3. Verify DNS
4. Identify non root login
5. Determine disk space
6. Determine memory
7. Determine failover configuration
8. Determine authentication types


2. Given business service information, determine which services to monitor, service dependencies, service-affecting events and data, and create a diagram so that all service dependencies are shown.


With emphasis on performing the following tasks:

1. Determine the highest-level services to monitor
2. Determine what applications, devices, etc. that support the high-level services
3. Determine how the lower-level services affect the higher-level services
4. Determine what events and/or data affects each service type


3. Given TBSM prerequisites, server information, and expected product load information, verify the prerequisites are met, create a deployment plan, so that business objectives are met.


With emphasis on performing the following tasks:

1. Ensure the prerequisites for TBSM product are met
2. Determine TBSM installation plan (simple or advanced; 1 host, 2 hosts, or 4 hosts)

Section 2 - Installation

1. Given the installation media and prerequisites for TBSM, install TBSM using the installation program so that all TBSM components are installed.


With emphasis on the following steps:

1. Create TBSM user. (Unix: local non root user id with shell capabilities, Windows: user that is a member of the local administrator group, not a user that is a member of the domain administrator group)
2. Obtain installation media
3. Ensure prerequisites for TBSM product are met
4. Run installation program using launchpad.sh (Windows: launchpad.exe)


2. Given a running ObjectServer and TBSM server, discover the ObjectServer schema so that TBSM events appear in the ObjectServer.


With emphasis on the following steps:

1. Run $NCHOME/bin/rad_discover_schema ObjectServer
2. Run $NCHOME/bin/rad_discover_schema OutputObjectServer
3. Verify that TBSM events are appearing in ObjectServer

Section 3 - Configuration

1. Given the customer requirements, service model requirements, product manuals, maintenance schedules, edit log levels and maintenance schedules, verify OMNIbus connection, and configure properties, so that a TBSM server settings are configured.


With emphasis on the following steps:

1. Edit log detail levels (RAD_server.props, RAD_policylogger.props, and log4j.properties)
2. Edit maintenance schedules using the GUI
3. Edit scheduleTime.xml file to delete a maintenance schedule
4. Configure properties (Servicetree refresh interval, service model timeout, discriminator field, default

service viewer type) in RAD_sla.props and RAD_av.props.


2. Given a Data Source type and the correct Data Source connectivity information, and assuming they exist and work, create a Data Source mapping within TBSM so that external information can affect the status of services in a service model.


With emphasis on the following steps:

1. Login to TBSM
2. Switch to Service Administration Page
3. Click the Data tab
4. Click the New button
5. Enter the Data Source Settings and connectivity information
6. Click Test Data Source
7. Save


3. Given the query data, a timing interval, and an existing data source name, create a Data Fetcher so that results are returned to TBSM.


With emphasis on the following steps:

1. Login to TBSM
2. Switch to Service Administration Page
3. Click the Data Fetcher tab
4. Click the New button
5. Enter unique name for data fetcher
6. Select the Data Source
7. Enter the SQL Query
8. Enter the expression for the SQL query
9. Set up interval
10. Click the View button


4. Given access to TBSM, service template and service instance information, configure a service template and service instance so that a service model is displayed.


With emphasis on the following steps:

1. Login to TBSM
2. Switch to Service Administration Page
3. Select Templates tab
4. Click New button
5. Enter the template settings
6. Create template rules
7. Save service template
8. Switch to Service Administration Page
9. Select Services tab
10. Click New button
11. Enter the service instance settings
12. Select service template
13. Click on Identification field tab
14. Enter field value
15. Save service instance


5. Given the SSL certificate was created or purchased, TBSM installed, server login information, create SSL Secured Access to the TBSM server so that customer data is protected.


With emphasis on the following steps:

1. Security Manager SSL Authentication:
1. Login to the SecurityManager server
2. Create SecurityManager Server Certificate
3. Add the certificate properties to SM_servletservice.props
4. Encrypt the keypass password
5. Configure SM_server.props
2. TBSM SSL Authentication
1. Login to the TBSM server
2. Create SecurityManager Server Certificate (if different from NCSM)
3. Add the certificate properties to server.props
4. Configure server.xml


6. Given access to TBSM and an existing and configured Data Source, Data Fetcher, and service template, create AutoPopulation rules in a template so that a Service is created automatically.


With emphasis on the following steps:

1. Login in to TBSM
2. Switch to Service Administration Page
3. Click on Templates tab
4. Edit the template
5. Click Create Auto-Population Rules button
6. Enter unique rule name
7. Select incoming status rule
8. Enter Auto-Population information
9. Repeat step 8 for any parent configuration
10. Save service template


7. Given an existing template and access to TBSM, create rules so that an enriched event can be displayed on the service model.


With emphasis on the following steps:

1. Edit template
2. Create dependency rule by clicking on Rule tab
3. Select outage information
4. Save
5. Edit template
6. Create incoming status rule by clicking on Rule tab
7. Determine whether to create good/marginal/bad rule or numerical rule
8. Enter the rule settings
9. Save
10. Edit template


8. Given an existing service template, data sources, and product documentation, create a service using ESDA so that the ESDA rule is configured.


With emphasis on the following steps:
1. Edit template
2. Create ESDA rule by clicking on Rule tab
3. Determine whether the ESDA is a child or parent rule
4. Select Data Source
5. Enter SQL query
6. Enter expressions field information
7. Verify selected template
8. Click Enabled


9. Given an existing service instance and existing user or group, add security permissions to service instance so that access to view or edit the server instance is restricted.


With emphasis on the following steps:

1. Edit service instance
2. Click the Security tab
3. Select users or groups
4. Select privilege
5. Save service instance

Section 4 - Customization

1. Given the customer page template was verified, product documentation, TBSM installed, and admin user defined, create a custom page using customer specified layouts and viewpoints so that a custom page is properly displayed.


With emphasis on the following steps:

1. Login to the TBSM GUI with admin user
2. Switch to the Adminstration page
3. Switch to the layout tab
4. Click the add button
5. Type in the page name and page title
6. Select correct category name and value
7. Click add
8. Edit the page from the designated view
9. Select layout (menu pane, one column, tab pane, three columns, two columns, state-maintained tab pane)
10. Select Security ID ( user only, default, admin view only, admins only, user view only)
11. Add designated viewpoint (active event list, chartview, iframe example, lightweight event list, mapview, service details, service tree, service viewer, table view, urgent service, version information, end of viewpoints), pane, or view
12. Organize viewpoints as specified by the template
13. Select decoration as specified by the template
14. Save the page


2. Given a TBSM install, Admin user defined, service model, product documentation, and canvas template, create a custom canvas in the appropriate way, add and organize indicator icons and decorations, select the background color, and save the canvas so that the custom canvas can be displayed.


With emphasis on the following steps:

1. Login to TBSM install with admin user
2. Switch to the Service administration page

If the canvas should be tied to an instance:
3. Display the instance in the service viewer
4. Click the create canvas button from the service viewer

If the canvas shouldn't be tied to an instance:
5. Click the Custom canvases selector
6. Click the Create custom canvas button
7. Add the indicator icons as specified by the predefined canvas template
8. When adding indicator icons, specify correct rules for each value
9. Organize icons on the canvas
10. Add and organize decorations
11. Select background color
12. Save canvas

If canvas is not tied to a service instance, supply name as defined by client


3. Given a TBSM install, admin user defined, existing custom page, templates, metric rules, data sources, data fetchers, and product documentation, create a new tree template which defines the templates to be used and data to be displayed so that a custom scorecard is created to display external data.


With emphasis on the following steps:

1. Login to the TBSM GUI with the admin user
2. Switch to the Service administration page
3. From the services selector, click the tree template editor button
4. Create a new tree template
5. Select the new tree template
6. Change sizing for columns to be displayed
7. Create the columns to be displayed on the custom scorecard
8. Select templates to be used
9. For each template, select the user defined metric/incoming status rule or system defined rule
10. Relate each rule that is selected to a column on the tree
11. Edit the policy to customize what is displayed in the column, such as value being received, or custom icon
12. Save the Tree template
13. Switch to the custom page where the custom service tree should be located
14. Edit the service tree viewpoint
15. Select the new tree template and the starting service instance


4. Given the client's custom images, customize the TBSM page header and viewpoint header, as well as the custom service tree icons, so that TBSM displays the customer's header images. and custom service tree icons.


With emphasis on the following steps:

1. Place all custom background header images in the appropriate directory
2. Edit the background-image for the file: $NCHOME/guifoundation/webapps/desktop/css/ngf/ngf.css to point TBSM to display new header images in the following sections:

Table.netcool-topheader
Td.netcool-topheader-left
Td.netcool-topheader-right
3. Edit the background-image for the file:

- $NCHOME/guifoundation/webapps/desktop/css/viewpoint.css to point TBSM to display new viewpoint header images in the following sections:
table.vp_header td.vp_header_left
table.vp_header vp_header_title
table.vp_header td.vp_header_right


5. Given the custom icons and defined service model, customize TBSM, so that the client service tree displays custom icons.


With emphasis on the following steps:

1. Place all custom icon images in the following directory: $NCHOME/guifoundaiton/webapps/sla/images
2. Edit the following policy to change the icon based on the current column by using the tree template

editor in the TBSM GUI.
@Change the VALUE variable for each icon that should display if the column name is customized,
based on the icon that would normally be displayed
3. Save policy

Section 5 - Operations

1. Given the dependencies between all four TBSM components, perform correct starting order (1.License Server 2.Omnibus 3.Security Manager 4.TBSM) and stopping order (1.TBSM 2.Security Manager 3.Omnibus 4.License Server) of all four components so that all four components will function properly and will allow for a login to the tbsm console.


With emphasis on the following steps:

1. The order of starting TBSM components are:
1. Start IBM Tivoli Netcool Common License Server

Unix - $NCHOME/license/bin/nc_start_license
Windows net start NCO Flex License Manager or can start from services panel
2. Start IBM Tivoli Netcool OMNIBus

Unix - $OMNIHOME/bin/nco_objserv &
Windows net start Netcool/OMNIbus Object Server
3. Start IBM Tivoli Netcool Security Manager

Unix - $NCHOME/security/bin/ncsm_server &
Windows net start Netcool Security Manager Server
4. Start TBSM

Unix - $NCHOME/bin/rad_server
Windows - net start Netcool Postgres Database
net start Netcool GUI Foundation Server
2. The order of stopping TBSM components are:
1. Stop TBSM

Unix - $NCHOME/bin/rad_shutdown
Windows - net stop Netcool GUI Foundation Server,
net stop Netcool Postgres Database
2. Stop IBM Tivoli Netcool Security Manager

Unix - $NCHOME/security/bin/ncsm_shutdown
Windows net stop Netcool Security Manager Server
3. 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
4. Stop IBM Tivoli Netcool Common License Server

Unix - $NCHOME/license/bin/nc_stop_license
Windows - net stop NCO Flex License Manager or can stop from services panel


2. Given that you have configured a service model, use the rad_sendevent utility to send test events to the TBSM ObjectServer so that one can confirm that the services in the model respond to service-affecting ObjectServer events properly.


With emphasis on the following steps:

1. Issue the rad_sendevent command using the following syntax:

rad_sendevent <ObjectServer host> <ObjectServer port> <ObjectServer userid>
<ObjectServer Password or "">
where:
ObjectServer host - Name of host machine running the ObjectServer monitored by TBSM
ObjectServer port - Port number for the ObjectServer monitored by TBSM
ObjectServer userid - The user name needed to access the ObjectServer
ObjectServer Password - Password for the Userid. Enter "" for no password
2. After issuing the rad_sendevent command, a READY prompt will appear and then type the field name
3. Press the enter key
4. Type the field value pair on the next line
5. Press the enter key again
6. When finished typing the field name and value pairs for an event, press the enter key twice.
7. Then either send another event, or press the Ctrl-C keys to exit rad_sendevent.


3. Given TBSM 4.1.1 is installed and object server is running, modify the OMNIbus schema using the tbsm_db_update.sql file so that the additional fields are now imported to the alerts.status table and an additional table called alerts.service_deps is also added into the schema of the object server.


With emphasis on the following steps:

1. Verify the tbsm_db_update.sql file is located in the appropriate directory.
2. Modify the OMNIbus Object server 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>
where:
servername is the name of the ObjectServer you want to create for Netcool/RAD.
username is the Objectserver user name.
password is the Objectserver password.


4. Given that a file is manually edited in the $NCHOME/guifoundation/webapps/sla/av/xmlconfig and $NCHOME/guifoundation/webapps/sla/av/css directories, issue the rad_reinitcanvas script so that you see the changes from the tbsm gui without having to restart the RAD server.


With emphaiss on the following steps:

1. Edit any file manually within the following directories: $NCHOME/guifoundation/webapps/sla/av/css and $NCHOME/guifoundation/webapps/sla/av/xmlconfig
2. Execute $NCHOME/bin/rad_reinitcanvas (Windows: %NCHOME%/bin/rad_reinitcanvas.bat)
3. View the service tree to see changes


5. Given the desired services, templates, data fetchers, data sources are configured on another TBSM server, perform the exporting and importing of service configuration using radshell function so that services are configured successfully without having to manually create them again.


With emphasis on the following steps:

1. On the TBSM server with existing services configured, use the radshell export function

@execute $NCHOME/bin/rad_radshell
@When the prompt changes to radshell>, type export ();
@Press enter
@When finished exporting, then type exit ();
@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.)
2. Copy the export.radsh file into the $NCHOME/guifoundation/webapps/sla directory of the

TBSM server you want to import the services to
3. Import the file into that TBSM server, enter the command: cat export.radsh | $NCHOME/bin/rad_radshell

Section 6 - Troubleshooting

1. Given Statement: Given a TBSM 4.1.1 install failure on Windows platform with MSIEXEC error 1603 in install logs and a console error �Insufficient space in Javaheap to satisfy allocation request', first uninstall TBSM including removing the %NCHOME% directory and when reinstalling TBSM make sure the pgservice user is created using the correct guidelines so that the TBSM install will not fail due to the rights of the pgservice user.


With emphasis on the following steps:

1. Make sure failed install is cleaned up.
2. Stop all Netcool Services (must have rebooted since original installation).
3. Start > Control Panel > Add or remove programs; select IBM® Tivoli® Business Service Manager (TBSM) and the Change/Remove button.
4. Read the information on the Welcome panel and click Next.
5. On this panel, all the features that have been installed are selected by default. Select the

features to uninstall and click Next.
6. Read the listing of features that will be removed. Click Uninstall.
7. Read the post-uninstallation summary information and click Finish.
8. Reboot the computer after the uninstallation process finishes.
9. If all components have been uninstalled, remove the %NCHOME% directory


2. Given a TBSM 4.1.1 install failure on Unix platform, and subsequent installation attempts also fail with 'Import of the schema failed', uninstall TBSM using the �uninstaller.bin', delete the file /var/tmp/locknetcool , login as a non-root user and reinstall TBSM so that a successful install is achieved.


With emphasis on the following steps:

1. cd $NCHOME/_uninst and run ./uninstaller.bin
2. Delete the file: /var/tmp/locknetcool (/var/tmp/locknetcool file remains from a previous installation attempt. License server fails to start and as a result, the OMNIbus Object Server installation also fails (failure to import

schema into the Object Server).
3. Installation must be done by someone with a non-root userid. The TBSM 4.1.1 installation

program does not support logging in as root and then switching from root to a different userid. If you are logged in as root, logout and then login using a non-root userid.
4. Re-install TBSM 4.1.1.


3. Given an upgrade from TBSM 4.1 to TBSM 4.1.1 on Windows with the TBSM Reports component, out of memory errors occur after you view a few reports and TBSM server stops running, set the registry entries for JVM options for the NCGFServer service executable so that the server should continue running when reviewing reports.


With emphaiss on the following steps:

1. Set the registry entries for JVM options for the NCGFServer service executable as follows:
2. If it is running, stop the Netcool GUI Foundation Server service.
3. To open the Registry Editor, select: Start->Run-> and enter regedit in the window that opens.
4. From the Registry Editor, select:

HKEY_LOCAL_MACHINE
-> SOFTWARE
-> Apache Software Foundation
-> Procrun2.0
-> NCGFServer
-> Parameters
-> Java
5. To see the JVM options, double click on Options in the right-hand column.
6. In the Edit Multi-String window, add these parameters:

-XX:MaxPermSize=128m
-XX:+DisableExplicitGC
7. Start the Netcool GUI Foundation Server service.