Skip to main content

Test 000-574: IBM Tivoli Business Service Manager V6.1

Tab navigation

Section 1:Planning

  1. Given access to stakeholders, technical personnel, and end users, gather customer requirements so that a document of customer requirements is available.
    With emphasis on performing the following tasks:
    1. Determine, in writing, in detail, the scope of the engagement in terms of the goals, objectives, expectations, deliverables, timeline, etc.
    2. Determine the expected outcomes of the project (money saved, efficiency gained, increased visibility, controlling costs, etc).
    3. Determine who will assess whether the expected outcomes are met, or will be after a given time.
    4. Determine the key use case scenarios are for each identified audience.
    5. Determine who will interact with the solution (How will it be used? How will they assess value, usefulness, return on investment?)
    6. Determine how the solution will be used when fully deployed, if different than initial deployment
    7. Determine how many services the customer needs to monitor and do they have SLAs to be met.
    8. Determine which KPIs should be monitored.
    9. Document the customer requirements.
  2. Given access to software support team, operating system architect, hardware deployment team, Tivoli architectural layout and database management team, define software requirements so that a document of software requirements is available.
    With emphasis on performing the following tasks:
    1. Verify which architecture the hardware team is deploying
    2. Obtain proper installation media for IBM Tivoli Business Service Manager (TBSM) whether DVD or downloads.
    3. Assess supported Web browsers and Java at "said" company.
    4. Review future TBSM architectural layout and dependencies once placed into current Tivoli deployment.
    5. Review historical database needs with database management team.
    6. Document software requirements.
  3. Given a list of supported platforms, minimum hardware requirements and access to the customer's environment, review the customer's environment so that it is verified that the minimum hardware requirements are met.
    With emphasis on performing the following tasks:
    1. Review the list of supported platforms and determine if the appropriate platform is available.
    2. Review the minimum hardware requirements.
    3. Run the appropriate OS system commands to determine if the minimum hardware requirements are met (CPU, memory, disk space).
    4. Determine if there are multiple systems and how many.
    5. Document available hardware.
  4. Given the TBSM Config file for the operating system, run the Prerequisite Scanner so that it is validated that TBSM can be configured and installed on the System.
    With emphasis on performing the following tasks:
    1. Copy the Config file from TBSM installation package
    2. Run the Scanner.
    3. Receive output from the Scanner.
      1. If Pass-system ready for installation
      2. If Fail-Verify Libraries exist.-Check environment variables.-Check permissions for directory issues.-Etc.
  5. Given a list of systems that will be part of the services being modeled in TBSM, determine the scale of the implementation requirements for a stand alone or full system so that the design of the system shows that a stand alone or full system will be deployed.
    With emphasis on performing the following tasks:
    1. Determine the reliability requirements for the system.
    2. Determine the hardware and OS platform for the system.
    3. Determine the number of concurrent users of the system.
    4. Explore with administrators if they would like a stand alone or multiple system architecture.
    5. Determine hardware requirements for each software component of the deployment.
  6. Given access to appropriate technical teams and company standards, gather existing requirements and options so that an architectural document of infrastructure components is available.
    With emphasis on performing the following tasks:
    1. Gather customer hardware information such as available CPU, Memory, and Disk Space.
    2. Document required port information and verify firewall rules are in place.
    3. Gather sizing estimates based on monitored resources and the number of included environments.
    4. Determine the intended audience of the tool as well as their access rights and roles.
    5. Determine product SLA requirements for failover and load balancing.
    6. Gather any existing infrastructure components that should be integrated.
    7. Determine operating system requirements and options.
    8. Prepare and document multiple deployment architectures for review.
    9. Document and present the final architecture.
  7. Given the many TBSM supported operating systems, database types, and software integration possibilities, review current skills and missing/needed skills based on the TBSM system installation and deployment plans required by the customer so that all database and software integration skills are identified.
    With emphasis on performing the following tasks:
    1. Identify current software and database skills levels.
    2. Identify operating system(s) used in TBSM system implementation.
    3. Determine if there are plans to use additional database types, other than OMNIbus and DB2. (For example data sources for data fetchers)
    4. Identify the TBSM system's User repository (File Base, OMNIbus, or LDAP)
    5. Determine if the optional Business Service Management Agent component will be installed.
    6. Determine if the optional Historical reporting component will be implemented.
    7. Determine all data sources the Discovery Library toolkit will discover resources through (IDL books and/or IBM Tivoli Application Dependency Discovery Manager).
    8. Determine If IBM Tivoli Netcool/Impact will be used to automate event management tasks, or to correlate event information, or to integrate Netcool products with a third party systems.
    9. Determine if TBSM will receive ISM events from an ObjectServer, IBM Tivoli Composite Application Manager for Internet Service Monitoring.

Section 2:Installation

  1. Given customer requirements, DB2 Admin staff if available, and Technical Staff, Install DB2 so that the DB2 instance is ready for the new DB2 Schema.
    With emphasis on performing the following tasks:
    1. As Administrative user, Run DB2 Installation program - varies by OS - DB2setup.xxx
    2. Click Install a Product
    3. Click Install for "DB2 Workgroup Server Edition Version 9.7 - this will install all components needed including Tools,Client,Runtime.
    4. Allow the installation to create the users if this is possible and they have not been created already for the DB - set the password.
    5. Choose Defaults or a different name for the DB instance.
    6. Once DB2 is installed it should be running - to verify this, change to the DB instance owner Example db2inst1.
    7. Set environmental variables by using db2profile.
    8. Verify DB2 is started "db2start".
    9. run the evaluation program to make sure everything installed correctly "db2val"
    10. Review the log created by the evaluation program in the %tmp% folder if there were issues.
  2. Given the IBM Tivoli Business Service Manager (TBSM) architecture, OMNIbus architecture, authentication sources, and user configurations, configure OMNIbus so that an integrated TBSM/OMNIbus system is achieved.
    With emphasis on performing the following tasks:
    1. Review TBSM architecture to determine where the ObjectServer is to be installed
    2. Install OMNIbus server if not already available.
    3. Review OMNIbus architecture so that Fields and Type of ObjectServer to be installed.
    4. Validate authentication sources for TBSM and OMNIbus.
    5. Check user configurations for Installation so that the event sources can be configured.
  3. Given the DB2 instance that will be used with the TBSM deployment, install the TBSM schema for DB2 instance so that the DB2 database has the proper schema.
    With emphasis on performing the following tasks:
    1. Log in as the proper DB2 user.
    2. Change to the appropriate directory for the script that ends with tbsmdb.
    3. Insert the TBSM media.
    4. Run Launchpad or the DB2 Schema utility from the DB2 command window.
    5. Answer questions until you get to the install DB2 Schema.
    6. Specify the installation directory.
    7. Select Simple.
    8. Specify Database.
    9. Select pick a directory for the scripts or execute the create schema option.
    10. Review installation.
  4. Given access to OMNIbus ObjectServers and gateways, update the ObjectServers by using the appropriate scripts and update any affected gateway configurations so that the Netcool OMNIbus environment is ready to accept and properly process TBSM events.
    With emphasis on performing the following tasks:
    1. Determine which ObjectServer(s) and gateways will process TBSM data fields.
    2. Back up existing ObjectServer schema.
    3. Back up existing Gateway configurations.
    4. Run appropriate commands to update Schema on all affected ObjectServers.
    5. Update and recycle gateways.
    6. Ensure appropriate fields are available and functioning.
  5. Given access to DB2, the operating system, previous versions of Impact and TBSM prepare for a migration so that TBSM V6.1 is ready for migration.
    With emphasis on performing the following tasks:
    1. Verify the appropriate access to the system(s).
    2. Verify that the hardware meets or exceeds the minimum requirements for implementation.
    3. Verify that the database and operating system match the installation prerequisites.
    4. Verify access to the existing environment.
    5. Verify that the TBSM database setup / configuration tasks have been performed.
  6. Given an existing pre-6.1 TBSM environment and a fresh installation of TBSM 6.1, migrate data from the source system to the target 6.1 system so that all data and services available in the source system are available on the target system.
    With emphasis on performing the following tasks:
    1. Back up the target 6.1 TBSM system.
    2. On the source system
      1. Stop all data fetchers, log off any users, stop the XML toolkit (if running), and any other data manipulating inputs to the data server.
      2. Run the export utility provided with TBSM 6.1.
    3. Update the target OMNIbus server schema (If required).
    4. On the target system
      1. Stop the Data server.
      2. Copy any required JDBC Jars for existing data sources to be migrated.
      3. Edit the Data server import properties file if required.
      4. Run the import utility.
    5. Update any data sources (if required).
    6. Verify Data server migration was successful.
    7. Ensure source Dashboard server is available and users are logged off (recommended).
    8. Run the pre-upgrade export script provided with TBSM 6.1.
    9. Run the upgrade.sh import script with the correct arguments.
    10. Verify the new Dashboard system has all changes migrated.
  7. Given prerequisites are complete and installation information has been determined, perform the Data server installation so that the Data server is successfully installed.
    With emphasis on performing the following tasks:
    1. Review installation guide and complete the worksheet needed during Data server installation:
      1. Identify Data server ports: one for Impact command line interface and Dashboard server communication with Data server.
      2. Determine user registry selection (LDAP, OMNIbus, or local file base).
      3. Specify TBSM database information (database name, hostname, username, password).
      4. Specify IBM Tivoli Integrated Portal (TIP) administration information (TIP user ID, TIP password).
      5. Specify WebSphere profile port information.
      6. Define name server-port pairs, for Name Server to provide registration functionality for the deployment components.
      7. Specify information about the Netcool/OMNIbus ObjectServer information (ObjectServer name, Host, port, User, password).
      8. Specify information about the Discovery Library Toolkit installation.
    2. Run the Data server installer.
  8. Given prerequisites are complete and installation information has been determined, perform the Dashboard server installation so that the Dashboard server is successfully installed.
    With emphasis on performing the following tasks:
    1. Verify the Data server is installed. The Netcool/Impact server for TBSM is installed as part of the Data server.
    2. Complete the failover configuration (if necessary).
    3. Review installation guide section which describes the installation information required to complete the Dashboard server steps and complete the Dashboard server installation worksheet.
      1. Determine user registry selection (LDAP, OMNIbus, or local file base).
      2. Specify the communication settings with the Data server.(database name, hostname, username, password).
      3. Specify TIP administration user information (TIP user ID, TIP password).
      4. Specify WebSphere profile port information.
      5. Define Name server-port pairs, for Name Server to provide registration functionality for the deployment components.
      6. Specify information about the Netcool/OMNIbus ObjectServer information (ObjectServer name, Host, port, User, password).
      7. Specify information about the Tivoli Enterprise Console® in this window.
    4. Run the Dashboard server installer.
  9. Given Access to the proper hardware and OS access, configure DB2 to handle load balancing and TIP High Availability (HA) so that TIP clustering is operational.
    With emphasis on performing the following tasks:
    1. Designate separate servers for Load balancing, DB2, and TIP clusters.
    2. Configure TIP HA/Load balancing post TIP installation.
      1. a Copy installation image directory from TIP machine to DB2 machine.
    3. Run Create DB commands.
    4. Connect Server A and Server B to the database.
    5. Run the Select WAS Admin commands.
    6. Modify the ssl.client.props files on both servers.
    7. Enable Server-to-Server trust.
    8. Verify load balancing is working.
      1. Log in to TIP through Server A.
      2. Create a new page on Server A.
      3. Log in to TIP through Server B.
      4. Verify the new page created on Server A is available on the Server B dashboard.
  10. Given a functioning ITM infrastructure with TEMS, TEPS and TDW, install the Tivoli Common Agent so that TBSM can be monitored and service history can be collected.
    With emphasis on performing the following tasks:
    1. Validate Tivoli Monitoring is running.
    2. Review Connection Details into ITM for the agent.
    3. Install the agent.
    4. Re-configure the agent by using one of the 3 preferred methods.
    5. Start and stop the agent to validate the configuration is working.
    6. Configure the historical collection for the ITM agent.

Section 3:Configuration

  1. Given access to technical personnel, gather customer requirements for failover, and install failover capability if required by customer so that the failover environment is installed for Tivoli Business Service Manager (TBSM).
    With emphasis on performing the following tasks:
    1. Itemize which servers will be primary and secondary. The server processes can be broken down as follows into their own individual server:
      1. ObjectServer, primary and secondary.
      2. Data server, primary and secondary.
      3. Dashboard server, primary and secondary.
    2. Determine failover requirements prior to installation:
      1. Primary and backup servers must be running same operating systems and the same version release of those operating systems.
      2. Installation by the root user is not supported.
      3. Primary and secondary systems must use same authentication method.
      4. Backup server should not have any data present, as it will be deleted during failover installation.
      5. For failover, the same encryption keystore must be used by both the primary and backup TBSM Data servers.
    3. Install the base packages, assuming separate installations for OMNIbus, Data server, and Dashboard servers:
      1. Install OMNIbus on primary and backup server from launchpad.
      2. Install TBSM Data servers on primary and backup servers from launchpad.
      3. Install TBSM Dashboard servers on primary and backup servers from launchpad.
    4. Prepare the fo_config script for failover:
      1. If ObjectServers are running separately from the dashboards, the fo_config script cannot be used to configure OMNIbus failover that must be completed manually.
      2. The fo_config script will be used to create a template to generate a configuration file.
      3. The fo_config script will be used for both the TBSM data and Dashboard servers.
  2. Given ID information for LDAP configure authentication source LDAP so that TBSM connects to LDAP.
    With emphasis on performing the following tasks:
    1. Obtain the LPAP Sever IP address, user id, and password and port number.
    2. Log in to the TBSM console as tipadmin.
    3. Add the new LDAP connection info in the Federated repositories.
    4. Add the LDAP connection information obtained above and click okay.
    5. Restart the Dashboard server.
    6. Log in to the TBSM console and verify that LDAP Users and Groups are showing up under Manage Users.
  3. Given running TBSM and IBM Tivoli Application Dependency Discovery Manager (TADDM) systems, requirements for custom template structure if needed and jar files, configure TBSM Discovery Library Toolkit with TADDM as a data source so that TADDM resources show up as TBSM services.
    With emphasis on performing the following tasks:
    1. Ensure Discovery Library Toolkit is installed.
    2. Ensure that the BSM_Templates.radsh file was installed with the Data server installation.
    3. Copy needed jar files based on TADDM version.
    4. Create the change_history_table on the TADDM database.
    5. Restart TADDM.
    6. Grant TBSM connection user the Authorization to change_history_table.
    7. If toolkit was an upgrade, copy customized XML files to the …XMLtoolkit/xml directory.
    8. Customize filtering, labeling, evenit identifiers ,and mapping.
    9. Run Discovery.
    10. Verify the changes within the TBSM services.
  4. Given customer requirements, data access information, database schemas, SQL queries,database team, event sources, authentication and security personnel, log in to each data source, perform SQL queries and verify data results so that valuable service data can be obtained.
    With emphasis on performing the following tasks:
    1. Review customer requirements and validate the data exists within the available data sources.
    2. Build and review the Query for the data source to verify it is using key values when available.
    3. Review the fetcher log upon activation and validate data.
    4. Talk with DB team to verify query times and Select Statements.
    5. Determine the highest polling time for the DB.
    6. Set the fetcher multiplier in accordance with the DB Admin.
  5. Given that TBSM is installed and working properly,configure data sources that are required for the system so that data sources are properly installed on the TBSM server.
    With emphasis on performing the following tasks:
    1. Review data source and data fetcher commands.
    2. Review Data Library Toolkit commands.
    3. Determine the type of data source.
    4. Verify supported data sources.
    5. Ensure correct jar files for TBSM are available.
    6. Determine the data model that will be used.
    7. Determine the SQL queries that will be used.
    8. Ensure connectivity to source database.
    9. Verify permissions with database admin.
    10. Set up data source failover if available and required.
  6. Given access to the appropriate technical personnel and planned service dependencies, configure rules with ESDA so that a working dynamic service model is created.
    With emphasis on performing the following tasks:
    Determine the service template structure is complete.
    1. Determine the seed template.
    2. Verify the data source being queried contains the correct data.
    3. Create queries to name both parent and child services. (If both are required).
      1. Child rules discover and name children of the seed service template.
      2. Parent rules discover and name the parent of the seed service instance template.
      3. Queries can be created by hand or by using the query builder.
    4. For each level of the service templates, create a query in an ESDA rule.
    5. Create custom policies by using additional properties from ESDA queries.Configure ESDA at each level to define basic attributes for the services discovered.
      1. Unique service names
      2. Display names
      3. Descriptions
      4. These names and descriptions can be combined from various returned values and text.
      5. Ensure the proper event identifiers are created (if required).
    6. Determine how ESDA rules should be triggered on demand.
      1. Either manually or automatically based on new data.
    7. Determine persistence or transience of ESDA rules.
    8. Change the persistence by using templates containing custom properties if needed.
      1. Force validation when invalidated.
      2. Import all descendants automatically.
    9. Configure incoming status rule to properly display incoming status.
    10. Verify ESDA rules are working properly.
  7. Given access to installed TBSM system and administrative template access, configure autopopulation rules so that service instances created from events are configured..
    With emphasis on performing the following tasks:
    1. Create services automatically based on incoming events.
    2. Understand addESDARule function and related syntax.
    3. Determine which rule names, services, queries to add to autopopulation.
    4. Understand addToAutoPopulation rule as it relates to parent relationships in an autopop rule.
    5. Understand createAutoPopulationRule command to configure new rule which creates new service instances based on Netcool/OMNIbus events.
  8. Given access to OMNIbus architecture and configuration, related monitoring tools, event sources, security personnel, and hardware team, verify functioning EIF probe so that an accurate event forwarding from event source products is available.
    With emphasis on performing the following tasks:
    1. Review Tivoli architecture and locate where the probe is to be installed or if already installed.
    2. Review probe properties file, tivoli_eif.props.
    3. Verify with security team that all the proper ports are open and available for the EIF probe.
    4. Obtain the rules file for the product you are receiving events from.
    5. Identify OMNIbus installation location and required information, port, server.
    6. Verify that the events from the source product are showing up in the Active Event List .
  9. Given services are discovered using the discovery toolkit library, and user has the appropriate roles assigned, right-click a service to enable launch options, and a "launch to" or "show" menu option is selected, then a separate browser window opens the other application and displays data about that service so that TBSM launches to another application displaying data about the service.
    With emphasis on performing the following tasks:
    1. Review list of supported application launches.
    2. Compare the list of supported applications with customer's requirements.
    3. Discover services by using Discovery Library Toolkit to obtain "additional attributes" which provide TBSM the required information about the application host which will t receive the URL request.
    4. Assign tbsmReadOnly or tbsmAdminUser role to a user who needs to launch to another application.
    5. Right click on a service to set the context for launch and display the "show" and "launch to" menu options.
    6. Select a launch option, to open a separate browser window into the other application and display data about that service.

Section 4:Administration

  1. Given system design document or list of end users and their associated roles, configure users, groups and roles so that functional users, groups and roles which implement desired access or view Dashboards are created.
    With emphasis on performing the following tasks:
    1. Log in to IBM Tivoli Integrated Portal.
    2. Ensure users and groups are created and associated.
    3. Assign the roles required by the users and groups from the ObjectServer or LDAP
    4. Verify that users and groups have appropriate roles.
    5. Log in as user to verify appropriate access.
  2. Given that IBM Tivoli Business Service Manager (TBSM) is installed and configured determine what user, role and group definitions are going to be required so that users, groups and roles are defined in the TBSM systems.
    With emphasis on performing the following tasks:
    1. Identify and create the users and groups for TBSM.
    2. Identify and create the rules that will be used for TBSM.
    3. Determine which users will have tbsmAdmin, tbsmUsers,tbsmViewAllServicesUsers, and tbsmReadOnly
    4. Assign roles to users.
    5. Assign users to groups.
    6. Set up roles to access Netcool/OMNIbus as needed.
  3. Given a working TBSM 6.1 system, create a custom view so that a working filtered list of objects is available to a target audience.
    With emphasis on performing the following tasks:
    1. Create the appropriate role and assign it to the correct list or group of users requiring access to the new view.
    2. Create the view and give it a name.
    3. Select the appropriate roles that should have access to the new view.
    4. Select the pages to be assigned to the view
    5. Save the view.
    6. Ensure the view is working properly by logging in as a user with the appropriate roles.
  4. Given a working TBSM system and a user assigned to an administrator role, create pages and portlets so that creation of a new page with portlets is available.
    With emphasis on performing the following tasks:
    1. Create a new work page.
    2. Enter the name the Page Name Field.
    3. In the page location field, click the location to browse for the folder where store the page.
    4. Select the Freeform option under Page Layout.
    5. Expand the Optional Settings. Click Add to view a list of users that can access this page.
    6. Use the navigation arrows at the bottom of the portlet palette to find and select the portlet wanted, or use the search filter to find the portlet wanted.
    7. Drag the portlet into the empty space below the portlet palette. Drag the portlet to wherever wanted on the page. Resize the portlet by pulling the lower-right corner.
    8. Resize a portlet to fill the entire page without border with Fill Work Page.
    9. Select Events to view event settings for the portlet.
    10. Click Done when finished adding portlets, customizing, and arranging.
  5. Given customer required views defined at service template and service instance level, select creator, create canvas so that custom static cavasses are displayed as a view in the service viewer based on assigned user group.
    With emphasis on performing the following tasks:
    1. Determine and plan Custom canvas creator, because by default permissions can only be given to member of groups the crater is a member of.
    2. Create a canvas with one of the following methods:
      1. Press the Create Custom Canvas button in the Service Viewer or View tab in the Service Editor (if this method is used files for the custom canvases are immediately created).
      2. Select Custom Canvases from the drop-down menu from the Service Navigation portlet, (if this method is used, files for the custom canvas are not created until you first save the canvas and you are prompted for the name for the custom canvas).
    3. Name the new canvas and save it, before adding any visual elements to the new custom canvas.
    4. Configure visual elements in the canvas as needed, with the "Select Tool", using Indicators tab
      1. Drag and drop visual element to Custom Canvas.
      2. Select the service instance to display as the selected visual elements
      3. Configure the properties of the visual elements as required using view-> Inspector.
      4. Close inspector, and Click Save on the Custom Canvas toolbar.
    5. Add Decorations as needed with the "select tool", using the Decorations Tab.
      1. Drag and drop decoration to Custom Canvas.
      2. Configure the properties of decoration as required using view-> Inspector.
      3. Close inspector, and Click Save on the Custom Canvas toolbar.
  6. Given a working TBSM service, customer requirements, customer event data, technical staff, information and inventory databases, define and implement event enrichment needs for services so that valuable service data can be viewed.
    With emphasis on performing the following tasks:
    1. Validate enough information exists in the Events being displayed within TBSM to act upon.
    2. If not, where this data could be obtained from, if yes, are the proper fields being displayed to show this information.
    3. Determine which fields to use for enrichment based off of actual inventory or informational data, example: Location, SubService, Application.
    4. Perform data reduction exercise - ensure "deduplication" and "generic clear"of events is functioning correctly.via the Trigger/procedure - AIM : Is the event unique enough , yet specific enough for @Identifier.
    5. Ensure generic clear procedure is successfully operating to make correct problem V resolver ( Type=1 events (problem) and Type=2 events ( resolution ) pair up - AIM : To ensure that the level of AlertGroup and AlertKey fields are specific enough to match problem V resolver.
    6. Ensure that the tokens in the event fields that are present, are set appropriate i.e. sending events required to the ObjectServer - and discarding statements for non required events.
    7. Create filters and view based on user roles, for the data set that has been configured and events being received.
  7. Given that TMSM is installed and ready for post-installation, Create, add, or modify custom Impact policies so that policies will operate properly.
    With emphasis on performing the following tasks:
    1. Go to the System Configuration -> Event Automation -> Policies.
    2. Select Project.
    3. Edit specific policy or create a new policy.
    4. Optimize and run the policy.
    5. Save the policy.
  8. Given a requirement and appropriate command line access, use the RAD shell to execute appropriate commands so that the requirement can be satisfied quickly and efficiently via the command line.
    With emphasis on performing the following tasks:
    1. Display all possible commands along with their usage statements and parameters.
    2. Export a service model.
    3. Import a service model.
    4. Create a service template.
    5. Export metadata.
    6. Rename a service instance.
  9. Given a working TBSM system and a user assigned to an administrator role, create new or edit existing template tree to build new score cards so that data is populated into a custom score card.
    With emphasis on performing the following tasks:
    1. Open Service Template Tree Editor.
    2. Create New Service Template Tree or work with Existing.
    3. Edit Column Names as needed.
    4. Associate templates in the list to the Template Tree.
    5. Specify which incoming status rules for the Selected Template gets associated to the Columns.
    6. Assign the new Service Template Tree to the Proper ScoreCard Portlet.
  10. Given an installed TBSM system, start and stop server components so that components are started and stopped.
    With emphasis on performing the following tasks:
    1. Stop the TBSM Data server - TIPHOME/bin/stopServer.sh server1 -profileName TBSMProfile -user tipadmin -password 'pass'.
    2. Start the TBSM Data server - TIPHOME/bin/startServer.sh server1 -profileName TBSMProfile.
    3. Stop the TBSM Dashboard server - TIPHOME/bin/stopServer.sh server1 -profileName TIPProfile -user tipadmin -password 'pass'.
    4. Start the TBSM Dashboard server- TIPHOME/bin/stopServer.sh server1 -profileName TIPProfile.
    5. Stop the ObjectServer - recommended stop and start through PAD.
    6. Start the ObjectServer.
    7. Stop the EIF probe.
    8. Start the EIF probe.
    9. Stop the Discovery Library toolkit daemon.
    10. Start the Discovery Library toolkit daemon.
    11. Stop the Tivoli Common Agent.
    12. Start the Tivoli Common Agent.
    13. Or use modified tbsm_suite.sh on UNIX/Linux systems if desired.
  11. Given access to technical personnel, SLA and an installed TBSM system, define and configure a maintenance schedule for TBSM services so that the TBSM maintenance schedule is defined and configured for a service.
    With emphasis on performing the following tasks:
    1. Determine which services will be affected by specific Maintenance windows.
    2. Review SLA documents to verify maintenance being held within SLA means.
    3. Ensure Maintenance windows do not overlap.
    4. Verify maintenance schedule with Change Procedures.
    5. Implement maintenance schedule through Templates section.
  12. Given SLA definitions and documentation, review and configure SLA definitions so that SLAs are implemented in Service Templates
    With emphasis on performing the following tasks:
    1. Review SLA documentation obtained from stakeholders.
    2. Validate service is compatible with given SLA.
    3. Match SLAs to appropriate SLA type.
    4. Edit SLAs in Service templates as required.
    5. Update maintenance schedules if needed.
    6. Verify implemented SLAs meet the requirements in the SLA documents.
    7. Activate SLAs in TBSM templates.
  13. Given a running TBSM V6.1 system and configured Tivoli Common Reporting, create, run and convert report from Business Intelligence and Reporting Tool (BIRT) to Cognos so that reports are available in Tivoli Common Reporting.
    1. Review the Tivoli Common Reporting Information Center.
    2. Create reports.
    3. Import reports with the TRCMD command.
    4. Use conversion assistance to convert BIRT reports into Cognos.

Section 5:Performance Tuning and Problem Determination

  1. Given an IBM Tivoli Business Service Manager (TBSM) problem requiring IBM assistance, collect TBSM troubleshooting logs so that generic TBSM logs are available when opening a support trouble ticket.
    With emphasis on performing the following tasks:
    1. Evaluate the problem.
    2. Review appropriate logs for issue.
    3. Gather troubleshooting logs from the TBSM data and Dashboard server(s) and send to IBM support.
      1. Either run the log collection tool ($TBSM_HOME/collect_logs) to gather troubleshooting logs.
      2. or manually collect sub-directories and files from the following directories:/tip/profiles/TBSMProfiles/logs/tip/profiles/TBSMProfiles/logs/server1
    4. Increase tracing if directed by IBM support.
  2. Given a functional TBSM system and access to TBSM, collect metrics from numeric status rules so that metrics collection is enabled for TBSM data.
    With emphasis on performing the following tasks:
    1. Determine information related to data collection, maintenance, and access of metric data.
    2. Determine which metrics provide the most benefit to the analysis tasks enabled by Time Window Analyzer.
    3. Determine which relational database metrics will be stored, on TBSM db or separate relational database.
    4. Determine which numerical rule attributes will be stored as metrics
    5. Setting controls for the way Metric Collection process works independent of particular metrics collected.
    6. Define which template rules to capture as metrics.
    7. Define which service instance overall state will be captured and stored as a metric
    8. Control Metric collection process through props file.
    9. Define and enable individual metric collection
    10. Understand default configuration attributes
    11. Understand important metric data storage issues (space determination)
    12. Determine number of connections to data store and allowed to external DB or DB2 instances
    13. Understand collection tuning, database performance tuning for db collection.
  3. Given a functional TBSM system and PMAT tool, review system performance and perform system tuning to achieve a Fine Tuned TBSM Database and Dashboard System.
    With emphasis on performing the following tasks:
    1. Review Data server and Dashboard server trace logs and correct errors as required.
    2. Review garbage collection logs with PMAT tool and increase maximum heap size as required.
    3. Increase service tree refresh interval as required.
    4. Increase canvas update interval multiplier as required.
    5. Increase client JVM as required.
    6. Review DB2 performance with DB2 Admin if available and take appropriate actions.
    7. Enable TBSM status change marker (enableMetricMarkers) to help tune status-propagation rules.
    8. Review hardware performance data and upgrade hardware as required.
    9. Evaluate XMS and XMX values for the startup script for the Data server and Dashboard server. Increase as necessary.
  4. Given access to database team, and event sources, tune data fetchers, so that valuable service model metrics are available in an efficient and timely manner.
    With emphasis on performing the following tasks:
    1. Review all data sources available.
    2. Analyze stakeholder, model sources and service component data.
    3. Ensure data fetchers return data within the appropriate windows.
    4. Check the cache settings of the data fetchers in the props file, and modify if needed.
    5. Enable and Disable the data fetcher(s)
    6. Monitor the TBSM system during fetch operations to ensure data is pulled appropriately and efficiently.
    7. Review data fetcher logs.
  5. Given a working TBSM system and appropriately backed up files, restore TBSM database from backup so that the TBSM system has been restored.
    With emphasis on performing the following tasks:
    1. Stop TBSM.
      1. Stop and start DB2 if needed.
    2. Disconnect from the database you want to restore.
    3. Restore the database using the DB2 restore command or from DB2 Control Center.
    4. Receive a message that the database has been restored successfully.
    5. Start TBSM.
  6. Given a functional TBSM system and Dashboard service, validate false positives in the dashboard, update event rules by using live or historical events so that dashboards provide an accurate representation of outages.
    With emphasis on performing the following tasks:
    1. Validate from customer if there have been any false positives showing up in the Dashboard - identify where and access the Template section.
    2. Open the rules for these services and review the customer event data with any historical event data to view how to limit the amount of events
    3. Update the Rules Classes,Filter,ServiceIdentifier,Severity event discrimnators and add any additional Filter that would help limit to the specific needs of events.
    4. Save the rules and continue to validate false positives within the dashboard.
  7. Given a functional TBSM system and Dashboard service, trouble shoot a problem by enabling specific tracing so that correct tracing is enabled to help troubleshoot errors experienced during runtime.
    With emphasis on performing the following tasks:
    1. Implement appropriate eWAS log trace levels.
    2. Use wildcards for logger groups.
    3. Use trace specifications such as info, finer, finest in appropriate syntax.
    4. Identify default TBSM trace specification.
    5. Set log levels by using Console GUI, setTraceLevel CLI, server.xml.
    6. Enable special performance tracing.

Register for a test

Register for an IBM Certification test at Prometric and take a step into your future.

IBM at Prometric