Skip to main content

Test 000-572: IBM Tivoli Monitoring V6.2.3 Administration

Tab navigation

Section 1: Installation

  1. Given hardware, software, network, and platforms for IBM Tivoli Monitoring V6.2.3 (ITM) infrastructure components develop a planning checking list and download the software required so that planning checklist is completed.
    With emphasis on performing the following tasks:
    1. Develop a planning checklist.
    2. Verify the minimum required hardware.
    3. Download the software required for the ITM components.
  2. Given the High Availability (HA) business requirements and the ITM HA configuration options, determine the HA configuration options to be used at every ITM component so that a full HA deployment plan is ready.
    With emphasis on performing the following tasks:
    1. Determine the HA configuration at the Hub Tivoli Enterprise Monitoring Server (Hub TEMS) (most critical - SPOC).
    2. Determine the HA configuration at the Tivoli Enterprise Portal Server (TEPS).
    3. Determine the HA configuration at the remote Tivoli Enterprise Monitoring Server (RTEMS) if needed.
    4. Determine the HA configuration at the Monitoring Agents.
    5. Determine the HA configuration at the Warehouse Proxy agent.
    6. Determine the HA configuration at the Summarization and Pruning agent..
  3. Given the ITM documentation and deployment plan, list the detailed requirements for servers and warehouse so that there is a detailed capacity plan.
    With emphasis on performing the following tasks:
    1. Determine the desired platforms for the ITM V6.2.3 components.
    2. Determine if agentless agents will be used (additional servers).
    3. Complete the warehouse load Project Worksheet.
  4. Given a company's software distribution policies and the information from the ITM V6.2.3 Installation Guide, determine which method best suits the needs so that the Agent deployment plan is ready for implementation.
    With emphasis on performing the following tasks:
    1. Determine if agentless agents will be used.
    2. Determine if agent deployment by using the company software distribution tool is a good option.
    3. Determine if agent deployment by using local server image installation is a good option.
    4. Determine if OS agent deployment by using CLI is a good option.
    5. Determine if non-OS agent deployment by using Tivoli Enterprise Portal remote deployment is a good option.
    6. Determine if non-OS agent deployment by using CLI is a good option.
    7. Determine if scripting remote agent deployment by using CLI is a good option.
  5. Given the supported RDBMS, the company standards, OS support, network consideration, and disk space available, determine which data warehouse requirements are needed so the data warehouse requirements are documented.
    With emphasis on performing the following tasks:
    1. Check which RDBMS has to be installed (if supported).
    2. Check version of RDBMS (if supported).
    3. Check the operating system which supports the RDBMS.
    4. Check if there is firewall between warehouse and other components.
    5. Check which ports need to be opened (if there is a firewall).
    6. Check for admin rights to the user for data warehouse.
    7. Check for minimum disk space required to install RDBMS and for the data to be stored within.
  6. Given a data warehouse and agents, check the collection interval, location, and predicted amount of data that would be collected so that the considerations for the custom historical data are determined.
    With emphasis on performing the following tasks:
    1. Check which agent data has to be collected.
    2. Check which attribute group in the agent has to be collected.
    3. Check for collection location, collection interval, and warehouse interval.
    4. Check amount of data inserted into warehouse per unit time interval and projection of the data in near future.
    5. Create filters (if needed) for data collection.
    6. Check for which particular managed systems the data has to be collected.
  7. Given a company's requirements for alerting and ITM V6.2.3 documentation, verify if this can be covered with existing attributes or if a new agent should be built so that all required alerts can be created.
    With emphasis on performing the following tasks:
    1. Review the alerting requirements against the available monitored attributes.
    2. Determine if all alerts are covered.
    3. Determine if any critical alerts would require a new agent to be built by using Agent Builder.
  8. Given company requirements for custom views, determine the attributes required so that custom view requirements are defined.
    With emphasis on performing the following tasks:
    1. Meet with customer's department to determine their needs.
    2. Verify if attributes are available in the customer's environment.
    3. Determine if any custom views would require a new agent to be build by using Agent Builder.
  9. Given a firewall, component information, port information, hardware capacity, HA,and recovery, develop a project plan so that there is an installation strategy.
    With emphasis on performing the following tasks:
    1. Determine whether a firewall gateway is needed.
    2. Determine which optional, mandatory components will be installed.
    3. Determine additional IP ports assignment.
    4. size of hardware - processor, memory, and disk, Determine location.
    5. Configure for HA and disaster recovery.
    6. Develop detailed project plan for Tivoli components.
  10. Given hardware, software, and information needed, perform the installation tasks and prepare for event forwarding so that the software installation is complete.
    With emphasis on performing the following tasks:
    1. Determine required hardware and software.
    2. Determine database user and security specifications.
    3. Determine name of monitoring server.
    4. Determine hostname for computer where installing the product.
    5. Determine whether hub or remote.
    6. Determine Hub Monitoring Host Name.
    7. Determine Port number.
    8. Determine host names, user IDs, and passwords for the monitoring servers.
    9. Simple Object Access Protocol (SOAP or Web services) information.
    10. Establish installation order.
  11. Given ITM 6.x, plan the upgrade, back up the ITM environment, upgrade Event sync, Tivoli Data Warehouse, TEMS/RTEMS, TEPS, TEPS desktop clients, IBM Tivoli Performance Analyzer (ITPA), and Monitoring Agents so that ITM 6.x is upgraded to ITM V6.2.3.
    With emphasis on performing the following tasks:
    1. Plan upgrade.
    2. Back up ITM environment.
    3. Upgrade Event sync.
    4. Upgrade Tivoli Data Warehouse.
    5. Upgrade Hub TEMS.
    6. Upgrade RTEMS (if exists).
    7. Upgrade TEPS.
    8. Upgrade TEPS desktop client.
    9. Upgrade ITPA.
    10. Upgrade Monitoring Agents.

Section 2: Configuration

  1. Given installed IBM Tivoli Monitoring V6.2.3 (ITM) software, use root/administrator login ID to configure Tivoli Enterprise Monitoring Server (TEMS) with correct information so that TEMS is configured.
    With emphasis on performing the following tasks:
    1. Use root / Administrator login ID.
    2. Run ./itmcmdconfig -S -t tems_name where tems_name is name of monitoring server or use MTEMS- > TEMS -> Reconfigure on Windows.
    3. Check and correct information regarding TEMS.
    4. Choose type of protocol to use for communication and backup.
    5. Configure KDC_PARTITION, Auditing and, Hot Standby features.
    6. Configure Security Authentication.
    7. Configure forward situation event console.
    8. Configure SOAP server.
    9. Configure self-describing agent capability.
  2. Given installed ITM software and IBM Tivoli Enterprise Portal Server V6.2.3 (TEPS) is operational, use root/administrator login ID to stop and configure TEPS settings so that TEPS is configured and operational.
    With emphasis on performing the following tasks:
    1. Use root / Administrator login ID.
    2. Stop TEPS.
    3. Run ./itmcmdconfig -A cq or use MTEMS- > TEPS- > Configure on Windows.
    4. Configure ITM Connector Settings.
    5. Configure the connection between the portal server and the hub monitoring server.
    6. Configure the connection between the portal server and the portal server database.
    7. Configure Tivoli Data Warehouse and connection settings between the portal server and warehouse database.
    8. Start TEPS.
  3. Given information on users and how they will access the TEPS, determine which Tivoli Enterprise Portal (TEP) client will be deployed and if any firewalls have to be crossed so that an action plan to deploy the TEP client can be completed.
    With emphasis on performing the following tasks:
    1. Determine which TEP client will be deployed (full client, browser of Java Webstart).
    2. Determine if any firewalls will have to be crossed.
  4. Given the previously built warehouse plan, setup the DB, configure the Warehouse Proxy agents (WPA), configure the Summarization and Pruning agent (SPA) and define all history data collections settings on the TEP so that agents start collecting data and send these to the Tivoli Data Warehouse.
    With emphasis on performing the following tasks:
    1. Implement a DBMS server and/or allocate a DB in an existing DBMS.
    2. Configure the WPAs.
    3. Configure the SPA.
    4. Use the TEP client to define all history data collection settings.
  5. Given installed Tivoli Enterprise Monitoring Agent (TEMA) , use the Managed System window features or command line interface so that the configuration of TEMA is completed.
    With emphasis on performing the following tasks:
    1. Right-click the Navigator item for the agent to configure or upgrade.
    2. Click Configure to open the Configure Managed System window.
    3. Edit the fields to configure the agent, clicking Next and Back to move among the pages. Any pages besides Agent are specific to the agent type.
      1. Warehouse Proxy: See the "Install and configure communications for the Warehouse Proxy agent" topics under "Setting up data warehousing" in the IBM Tivoli Monitoring Installation and Setup Guide.
      2. Summarization and Pruning Agent: See "Configuring the Summarization and Pruning Agent (JDBC connection)" in the IBM Tivoli Monitoring Installation and Setup Guide.
      3. Performance Analyzer Warehouse Agent: See the IBM Tivoli Monitoring Installation and Setup Guide.
      4. Universal Agent: Specify the Metafile and Script files. These are described in the "New in this release".
      5. Non-base agents: See your product's installation guide in the IBM Tivoli Monitoring information center or on IBM developerWorks Tivoli Documentation Central.
    4. On the Agent page, establish the user ID that will be used to maintain the agent:
      1. Windows: Accept the default, Use local system account to use your TEP user ID. You can also select Allow service to interact with desktop to enable remote control. Or select Use this account and fill in the user name and password under which the agent will be controlled.
      2. Non-Windows: Enter the Username under which the agent will run and the Group name.
    5. Click Finish to complete the managed system configuration. If any of the information provided is invalid, you will receive an error message and be returned to the configuration window. Check your entries and edit as appropriate to configure correctly.
  6. Given a company network plan and the ITM V6.2.3 documentation, determine the exact requirements for the firewall gateway, build the XML files, and configure the agents so the firewall gateway is configured.
    With emphasis on performing the following tasks:
    1. Determine where Agents will have to cross firewall to reach their remote Tivoli Enterprise Monitoring Server (RTEMS) or the RTEMS to reach the Hub Tivoli Enterprise Monitoring Server.
    2. Check corporate network security policies if ports can be opened from the less to the more secure zone.
    3. Check if firewall gateway is required to comply with security policies.
    4. Determine which agents in each network zone will function as firewall gateway
    5. Determine if the firewall gateway will be used for TEMS traffic only or also for warehouse traffic.
    6. Build the XML definition files for all gateways.
    7. Set the selected agents variables to point to these XML files.
    8. Configure the agents to connect with their firewall gateway.
  7. Given a High Availability (HA) plan, implement the planned actions so that there is an HA environment operating according to requirements.
    With emphasis on performing the following tasks:
    1. Implement HUB Hot Standby or Cluster configuration.
    2. Implement spare RTEMSs.
    3. Implement WPA failover parameters so that agents can warehouse to a secondary WPA.
    4. Configure Agents to be able to connect to 2 RTEMSs.
    5. Configure spare TEPS with or without some kind of load balancer and/or cluster configuration.
    6. Implement a plan to quickly replace a failing SPA.
  8. Given agent data collection requirements, adjust the settings so that historical data, summarization, and pruning are configured in line with requirements.
    With emphasis on performing the following tasks:
    1. In TEP, open History configuration window.
    2. Select the Monitoring application.
    3. Create new/another collection setting.
    4. Select the warehouse interval, collection interval, collection location.
    5. Select the options for summarization and pruning of data.
  9. Given SPAs, configure the agents by using TEP client and TEMS to connect scheduling and pruning so that the SPAs are configured.
    With emphasis on performing the following tasks:
    1. ./itmcmdconfig -A syor use MTEMS-> TEMS- > Reconfigure on GUI
    2. Select TEMS to connect to (protocol and port included).
    3. Select Database Type.
    4. Select Data Sources (JDBC drivers) and enter DB admin credentials.
    5. Test connection.
    6. Enter scheduling details.
    7. Set pruning details for logs.
    8. Set details like worker threads, database compression etc.
  10. Given the need for a working IBM Tivoli Performance Analyzer (ITPA), select the database, database connection type, and user credentials so that ITPA can be configured.
    With emphasis on performing the following tasks:
    1. Start Manage Tivoli Enterprise Monitoring Services.
    2. Right Click -> Reconfigure.
    3. Select Database type.
    4. Enter the Database details.
    5. Enter Database admin credentials.
    6. Enter Advanced configuration details.
  11. Given a database server, create a database, create a warehouse user, and limit the authority of the warehouse user so that the warehouse database functions correctly.
    With emphasis on performing the following tasks:
    1. Create a database.
    2. Create a warehouse user.
    3. Limit the authority of the warehouse user.
  12. Given TEMS V6.2.3, TEC ,and OMNIbus, configure TEC, TEMS, and Netcool/OMNIbus so that event integration is established.
    With emphasis on performing the following tasks:
    1. Set event integration with TEC.
      1. Determine the ITM and TEC environment in terms of number of the TEMS and the TEC servers involved. .
      2. Install TEC if needed.
      3. Import the event synchronization class files and rule set.
      4. Install .baroc files on the TEC server.
      5. Start and stop Situation Update forwarder process.
      6. Change the configuration of the event synchronization component on the event server.
      7. Define additional monitoring servers to the event server.
      8. Customize event status processing behavior when agent switching is used or the agent goes offline.
      9. Change the TCP/IP timeout setting on your event server.
      10. Change TEC configuration for the event behavior for various scenarios.
      11. Upgrade the event synchronization by using wizard and command line.
    2. Set event forwarding to Netcool/OMNIbus.
      1. Determine the ITM and Netcool environment in terms of number of the TEMS and the OMNIbus servers involved.
      2. Install Netcool/OMNIbus server if needed.
      3. Change default deduplication trigger.
      4. Configure Event Integration Facility (EIF) probe.
      5. Configure TEMS to forward events.
      6. Verify installation and configuration.
      7. Customize Event Integration.
      8. Configure ITM Situation Update Forwarder error event flow to OMNIbus.
      9. Change the configuration values of the ITM Situation Update Forwarder.
      10. Update the ITM Situation Forwarder to forward event status updates to additional monitoring servers.
      11. Customize how the ITM OMNIbus triggers handle event status updates from the monitoring servers.
      12. Change the default acknowledgment timeout used when sampled events are deleted or cleared in Netcool/OMNIbus.
      13. Edit the configuration parameters that the hub monitoring server uses to forward events to the Netcool/OMNIbus Probe for Tivoli EIF and configure up to five failover EIF probes.
      14. Specify which situations forward events to Netcool/OMNIbus.
      15. Convert from unidirectional architecture to bidirectional architecture
      16. Customize event status processing behavior when agent switching is used or the agent goes offline.
      17. Create a Netcool/OMNIbus WebGUI tool to launch from WebGUI to the TEP.

Section 3: Performance Tuning, Problem Determination and Troubleshooting

  1. Given an IBM Tivoli Enterprise Portal (TEP) client connected to an IBM Tivoli Enterprise Portal Server (TEPS) V6.2.3, go to the MOSWOS workspaces and correct the errors so that Self-Monitoring (MOSWOS) Workspace is tuning the environment.
    With emphasis on performing the following tasks:
    1. Connect to TEPS by using your preferential TEP client.
    2. Select Workspace Gallery -> Manage Tivoli Enterprise Monitoring Servers workspace.
    3. Click a Link to open detailed workspace with data from monitoring server.
    4. Select one of those options you want to check:Installed Catalogs, Protocols, Situation Status, System Information
    5. Verify the color code for each item and correct the errors.
  2. Given a database, use the IBM Tivoli Monitoring V6.2.3 (ITM) Guide, Relational database design paper and SG24-7443 Redbook to tune the database so that it is operates at an optimal level.
    With emphasis on performing the following tasks:
    1. Refer to "Understanding the disk requirements for your database on page 442 ITM V6.2.3 installation guide" for information about disk requirements.
    2. Refer to the "Relational Database Design and Performance Tuning for DB2 Database Servers" Paper for information about design and performance.
    3. Refer to the "Tivoli Data Warehouse tuning" chapter from the Tivoli Management Services Warehouse and Reporting (SG24-7443) Redbook for information about tuning.
  3. Given logs, identify the types of logs that are used in ITM so that basic troubleshooting information can be gathered.
    With emphasis on performing the following tasks:
    1. Identify RAS1 logs and its path for each component.
    2. Identify Operational logs and its path for each component.
    3. Identify core files and drwatson dumps.
    4. Identify installation logs.
  4. Given ITM and the troubleshooting guide, set the trace option so that the trace file is configured for troubleshooting.
    With emphasis on performing the following tasks:
    1. Set trace option according to issuereferenced by the Troubleshooting guide.
    2. Check log files located under install_dir\logs\hostname_ms-HEXtimestamp-nn.log.
  5. Given TEPS V6.2.3, check all processes and logs, use FAQs and the IBM Support website so that troubleshooting TEPS V6.2.3 is completed.
    With emphasis on performing the following tasks:
    1. Ensure that all the TEPS processes are running.
    2. Check the TEPS operational and RAS1 logs.
    3. Check eWAS and IHS logs.
    4. Check FAQs.
      1. Performance impacts of the HTTP and HTTPS protocols
      2. Users who run the IBM HTTP Server do not have permission to the content directory.
      3. tacmdexportWorkspaces or importWorkspaces receives an out of memory error
      4. The portal server and Warehouse Proxy agent (WPA) fail to connect to the database on a 64-bit Windows system.
      5. Failed to log in as sysadmin with portal server LDAP enabled.
      6. On AIX systems, newly created users with auto-expire passwords cause installation failures.
      7. Linux portal server is unable to FTP catalog/attribute files.
      8. Upgrading the TEPS takes a long time.
      9. Run the Tivoli Management Services Discovery Library Adapter, results in a book that does not contain the fully qualified hostname.
      10. TEPS performance is slow.
      11. Cannot create a TEPS database.
      12. Receive a KFW error when a query is sent to more than 200 managed systems.
      13. Non-hub situations are not associated at the TEPS level.
      14. Start and stop the Eclipse Help Server.
      15. Non-root stopping or starting agents causes problems.
      16. Root password is not accepted during non-root TEPS configuration.
      17. Corba user exception is included in the TEPS log when creating situations.
      18. Stop or start the eWAS subcomponent of the TEPS.
    5. Check on the IBM support site for the latest fixes or known issues.
    6. Collect mustgather and send to IBM Support.
  6. Given ITM and the Agent User guide, set the trace option so that Tivoli Enterprise Monitoring Agent (TEMA) trace files are configured for troubleshooting
    With emphasis on performing the following tasks:
    1. Set trace option according to the issue referenced by the Agent user's guide.
    2. Check hostname_ux_program_timestamp-nn.log files located under install_dir\logs path.
  7. Given the pdcollect tool, perform the start command and review the output so that the pdcollect output will be completed.
    With emphasis on performing the following tasks:
    1. When running pdcollect, Ensure the following is in the output ‘Data collection is complete'.
    2. Review the manifest.txt file to ensure the necessary files are there.
    3. Ensure ‘exit' is entered when finished.
    4. Verify the following commands are used to start pdcollect - Windows: pdcollect.cmd pdcfilt.exe, UNIX/Linux: pdcollect, z/OS: pdcollect.clist
  8. Given ITM, a running checked database, a WPA configured and running, and historical data collection configured, set the trace option so that Warehouse trace files are configured for troubleshooting.
    With emphasis on performing the following tasks:
    1. Check if the Database is up and running.
    2. Check if the WPA is up and running.
    3. Check if the historical collection is configured and running.
    4. Set the trace levels according to the Warehouse Guide.
  9. Given agent logs, verify that communication errors do not exist and that NICs are properly configured so that component communication problems are resolved.
    With emphasis on performing the following tasks:
    1. Verify that there are no RUL11STM remote request communication failed or RUL11LID identify with Open Error 155 or ‘Endpoint unavailable' messages indicating communication failures.
    2. Verify that multiple NICs do not exist on the system. If multiple NICs exist on the system, determine which one is configured for the Tivoli Enterprise Monitoring Server (TEMS) and for the TEMA,
    3. Ensure that you specify the correct host name and port for communication in the ITM environment.
  10. Given IBM Tivoli Performance Analyzer (ITPA), check logs, FAQs, application support,domain support,and the IBM Portal site so that ITPA issues are resolved.
    With emphasis on performing the following tasks:
    1. Enable logging/tracing.
    2. Check Installation logs.
    3. Check if application support and domain support is installed.
    4. Check RAS1 and operation logs.
    5. Check for FAQs.
      1. After upgrading, the previous version of the Performance Analyzer is shown in the Performance Analyzer Configuration window, and task names are not displayed correctly.
      2. After upgrading, the names of workspace groups in the Performance Analyzer Warehouse Agent node in the Navigator view are not displayed correctly.
      3. ITPA graphical user interface for TEP fails when downloading tasks list.
      4. When tasks are started and when you should see data in the workspaces
      5. No data is displayed in the workspaces.
      6. The ITPA workspaces are not available or not displayed. No chart is visible on the Forecast Details workspace.
      7. The Performance Analyzer Agent Statistics workspace shows database errors indicating that some tables or views are missing.
    6. The TEMS does not restart after installation of Domain Support.
    7. Check IBM Support Portal for known issues and flashes.
  11. Given ITM documentation and customer support guidelines, set the components KBB_RAS1 variable either statically or dynamically so that the component is being traced correctly for debugging.
    With emphasis on performing the following tasks:
    1. Set the KBB_RAS1 variable by using either the Manage Tivoli Enterprise Monitoring Services Console or by modifying the component's environment or .ini file and recycle the component.
    2. Alternatively, use the components service console via its server port 1920 to start tracing dynamically.

Section 4: Administration

  1. Given an IBM Tivoli Enterprise Portal (TEP) client connected to an IBM Tivoli Enterprise Portal Server (TEPS) V6.2.3, take required actions so that the custom users can be configured.
    With emphasis on performing the following tasks:
    1. Connect to TEPS.
    2. Click on the Administer user's icon.
    3. Work on the Administer users windows as requested.
  2. Given a TEP client connected to a TEPS V6.2.3, create, modify and remove custom workspace so that Workspace is modified according to the requirements.
    With emphasis on performing the following tasks:
    1. Connect to TEPS by using your preferential TEP client with Workspace Author Mode permission ID.
    2. Select Workspace Gallery to choose other Workspace already defined.
    3. Open an undefined workspace.
    4. Use Split tool to modify workspace.
    5. Configure the view types and test the result.
    6. Use Save Workspace as to create a new Workspace.
    7. If it is necessary modify the properties, including its name, go to your new workspace created and edit properties.
    8. Use File -> Delete Workspace to delete the Workspace.
  3. Given the installation predefined situations, copy and change the predefined situations so that new, customized situations are created.
    With emphasis on performing the following tasks:
    1. Copy the predefined situations to change. (The predefined situations provided with this monitoring agent are not read-only. Do not edit these situations and save over them. Software updates will write over any of the changes that you make to these situations.).
    2. Use the Situation Editor, display the predefined situations or create situations.
    3. Alter the following tabs to create a new situation:
      1. Formula - Condition being tested
      2. Distribution - List of managed systems (operating systems, subsystems, or applications) to which the situation can be distributed
      3. Expert Advice - Comments and instructions to be read in the event workspace
      4. Action - Command to be sent to the system
      5. - Until - Duration of the situation
      6. Event Integration Facility - Whether to send a Tivoli Enterprise Console event and event severity
    4. When creating situations, choose from these types of predefined situations:
      1. Automatically installed and activated at startup
      2. Not automatically installed but activated at startup
      3. Automatically installed and not activated at startup
      4. Bottleneck analysis, not activated at startup
  4. Given a TEP client connected to a TEPS V6.2.3, create, modify and delete automation actions and responses, so that an automation policy is created or modified according to the requirements
    With emphasis on performing the following tasks:
    1. Connect to TEPS by using your preferential TEP client with Workspace Author Mode permission ID, View Policy permission ID or Both.
    2. Select Workflow Editor -> New Policy.
    3. Adjust setting at added row of the Policy Details area, edit the name and description
    4. The Select a Situation window opens for you to select a situation that, when true or in error, triggers the next activity in the workflow.
    5. Add other activities to the policy as needed.
    6. Draw connecting lines to direct the workflow.
    7. After finish workflow, Validate, Distribute, and Apply policy.
    8. Select Edit Workflow to open and Edit policy as needed.
    9. In case of copy and delete policy use Workflow Editor and select Copy or Delete Policy as needed.
  5. Given a TEP client connected to a TEPS V6.2.3 and workspaces, take required actions so that links between workspaces are created or modified according to the requirements.
    With emphasis on performing the following tasks:
    1. Connect to TEPS by using your preferential TEP client with Workspace Author Mode permission ID.
    2. Open the source workspace.
    3. Right-click one of the possible link source locations: The highlighted Navigator item for this workspace, An icon in a graphic view, An object in a Tivoli Management Services Infrastructure view, A row in a table view or situation event console view, A data point in a chart view.
    4. Select Link to -> Link Wizard,
    5. To create a new one, Select Create a new link and type the name and description.
    6. Select: Dynamic; Absolute; Relative link options.
    7. Select the navigation view of your target link.
    8. Configure setting of selected links options.
    9. Select finish to save the link.
    10. To modify link properties or delete a link, follow the steps 6.5.2; 6.5.3; 6.5.4; and select Modify an existing link or Delete one or more existing links.
  6. Given agents and the attribute groups, use the default queries with variables to run a query on Tivoli Enterprise Monitoring Server (TEMS) and a database so that a custom query is created.
    With emphasis on performing the following tasks:
    1. Review default queries and variables.
    2. Use of variables.
    3. Query TEMS tables.
    4. Query database.
    5. Assign query to workspace.
  7. Given the Agent Depot and Bundles, determine the agent deployment type and populate the agent depot so that the agents are deployed.
    With emphasis on performing the following tasks:
    1. Determine type of agent deployment - agent deployment from the installation image or using the tacmdcreateNode for OS agents or use the tacmdaddSystem or TEP Deploy for non-OS agents.
    2. Create and populate the agent depot with installable agent images.
    3. View and change the contents of the agent depot.
    4. Use one agent depot for all the monitoring servers in your monitoring environment.
    5. Deploy an OS agent.
    6. Deploy a non-OS agent.
    7. Deploy a group of agents simultaneously.
  8. Given a TEP client connected to a TEPS V6.2.3, configure the History data collectionwindows so that custom history is configured.
    With emphasis on performing the following tasks:
    1. Connect to TEPS.
    2. Click on the History Configuration icon.
    3. Configure the History data collection configuration windows according to needs,
  9. Given the predefined Navigator workspace, edit the workspace with the Navigator tools so that customized Navigator views are created.
    With emphasis on performing the following tasks:
    1. Edit the Navigator workspace and save with different name as predefined workspaces cannot be modified or deleted.
    2. Use the tools in the Navigator view toolbar to update the display when managed systems have come online or gone offline, to open another Navigator view, to edit custom Navigator views, and to collapse the view.
    3. Use the Edit Navigator view to open the Navigator editor for creating, deleting, and modifying Navigator views. If the tool is disabled (dimmed), your user ID does not have Modify permission for Custom Navigator Views.
    4. Use the down arrow icon to open a list that you can select a Navigator view from. The views available are those assigned to your user ID. When you select another Navigator view, a tab is added to the bottom of the Navigator so that you can quickly switch among the views by clicking the tab.
    5. Use the Find in the Navigator toolbar to look for a Navigator item by such criteria as managed system name or associated situation name. When the search has completed, any items that match the criteria are listed in the Find results table where you can switch to the default workspace for a found item or open it in a new window.
    6. Use the Apply pending updates tool to update the Navigator tree with the correct status of agents, in response to the count of agents that have been removed from or added to the TEMS. The counter is displayed next to the tool and in the status bar. Refresh is enabled when the Navigator view has been edited, such as a new item has been added, so that you can update the view with the changes. This tool is dimmed when no updates are required.
    7. Use the horizontal and vertical Split icon to split the Navigator horizontally or vertically to create a new workspace view .
  10. Given an installed Tivoli Common Reporting tool, determine that the necessary products are installed and report packages have been imported or created so that the common reporting tool is customized for reports.
    With emphasis on performing the following tasks:
    1. Ensure Tivoli Common Reporting and Framework Manager are installed and configured.
    2. Determine if you have the report packages ready, import the report packages:
      1. Import Cognos report packages.
      2. Import Business Intelligence and Reporting Tool report packages.
    3. Determine if you have to create a new report package:
      1. Configure the database connection.
      2. Create a data model in Framework Manager.
      3. Import the metadata from your data sources.
      4. Log in to the reporting interface and select Launch -> Query Studio to test your model and create simple ad hoc reports, or select Launch -> Report Studio to create more complex reports.
      5. Create a final package.
    4. Verify the following installation directories are available: Windows operating systems: C:\IBM\tivoli\tcrnon-Windows operating systems: /opt/IBM/tivoli/tcrTivoli Integrated Portal installation directory, referred to as TIP_install_dir: Windows operating systems: C:\IBM\tivoli\tipv2non-Windows operating systems: /opt/IBM/tivoli/tipv2
    5. Determine installation method - installation wizard, console mode or silent mode.

Register for a test

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

IBM at Prometric