IBM


IBM Professional Certification Program

Accelerate insight. Improve skills. Get certified now.

Test C2010-538: IBM Tivoli Monitoring V6.2.2 Implementation


Note: This test will be withdrawn on Feb 28 2014.
The replacement test is: (C2010-507) IBM Tivoli Monitoring V6.3 Implementation


Section 1: Planning


  1. Given the need to implement IBM Tivoli Monitoring V6.2.2 (ITM) in a production environment, having an understanding of ITM, and having knowledge of the corporate organization in which ITM will be implemented, describe some of the key business considerations that should be made, so the ITM implementation can be effectively planned to address business requirements and a solution architecture can be designed.
    With emphasis on performing the following tasks:

    1. Identify key project sponsors, participants, and stakeholders.

      1. Management sponsorship is important to ensure ongoing support of the initiative and leverage participation from disparate groups as required.

      2. Key participants may include departmental management and/or technical leads for business applications that will be included in the initial monitoring deployment.

      3. Critical stakeholders would include those that have responsibility for the success of the solution and personnel charged with the technical support of ITM.

    2. Define who the initial customers will be and what is required to be monitored (business requirements).

      1. As part of planning for an initial ITM implementation, one should clearly define what applications are to be included and who the customers will be of the monitoring services.-Defining the internal customers will play a major role in defining the scope of the initial implementation.

      2. In cooperation with the business application owners, determine what key metrics or indicators are required to be monitored.-For an initial monitoring deployment, start small to establish a degree confidence and build up to more complex monitoring requirements.

    3. Determine what degree of customization will be required.

      1. Although ITM's baseline capability is substantial, it is important to understand desired degree of customization and integration that will be required, so appropriate timing and resources can be planned.

    4. Define ITM support model (centralized or decentralized).

      1. Define who will be tasked as the ITM Subject Matter Experts(SMEs) with consideration for the two most predominant ITM support models.-A centralized ITM support model implies there will be one or more ITM SMEs dedicated to the end-to-end support and management of the monitoring solution. Although this typically indicates the ITM support personnel will have a deeper skill level, the ITM administrator(s) will also be required to have some insight into the applications being monitored. The cost of ITM ownership is more easily quantified.-A decentralized ITM support model implies there may not be any single department or person dedicated to the full time, end-to-end support of ITM. Although ITM skills tend to be at a higher level, the business application owners play a deeper role managing the ITM tools and the cost of ownership is distributed across several cost centers. The total cost of ownership for ITM is more difficult to define with a decentralized ITM support model.

      2. Determine if ITM education/training will be required for those tasked with supporting the solution.

    5. Determine historical data collection requirements.

      1. Historical data collection is not a requirement for monitoring but is typically desired and requires careful planning.

      2. Which metrics, frequency of collection, and size if the ITM deployment will have significance when planning for an ITM deployment.

    6. Determine availability requirements for ITM.

      1. There are many levels of availability that can be applied to ITM, but ultimately, there is required to be a justified business case which will determine the degree of availability required.

      2. ITM offers a Hot Standby function for the Hub Tivoli Enterprise Monitoring Servers and allows configuration for a primary and secondary Tivoli Enterprise Monitoring Server (TEMS) at the Tivoli Enterprise Monitoring Agent (TEMA) level to accommodate availability.

    7. Using gathered information, define a formal project plan.

      1. The risk of extended delays and failure for enterprise implementations of ITM will be greater if a detailed project plan is not followed.

  2. Given that the general monitoring requirements have been determined and documented during the project planning phase, define the interactions between the ITM components and non-ITM components so that a complete monitoring and project topology document can be completed.
    With emphasis on performing the following tasks:

    1. Identify the functions required to complete the monitoring solution that the native ITM infrastructure will not support.

    2. Identify the components, ITM or other products, that will deliver the functionality determined necessary.

    3. Determine the steps to enact or complete the integration defined. These actions could include the following but this is not meant to be a complete list (Take Actions, Polices, Event Forwarding configuration,etc).

    4. Update the project design or architecture document.

  3. Given a comprehensive understanding of ITM, documented business requirements for monitoring, and knowledge of the existing IT infrastructure and topology in which ITM will be deployed, design an ITM architecture, so that it accommodates the monitoring requirements while leveraging the customer's existing IT resources where possible.
    With emphasis on performing the following tasks:

    1. Determine the hardware and OS requirements.

      1. Use the ITM Installation and Setup Guide to determine what platforms and operating systems are supported.

      2. Alternatively, the Support Matrix spreadsheet can be used from IBM's public website.-http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

      3. A key consideration should also include a customer's skill level and resource availability for the platform(s) chosen to implement ITM.

    2. Determine the prerequisites for the installation (software, appropriate access).

      1. Check for appropriate patch levels and supporting library requirements for target infrastructure systems.-This information can be found in the ITM Installation and Setup Guide.-Determine database requirements for Tivoli Enterprise Portal Server (TEPS).

      2. Ensure access to entitled Tivoli software required for implementation.-Verify what Tivoli software has been entitled to customer.

      3. Ensure appropriate access and authority is available for installation.

    3. Determine which ITM components are best suited for meeting the business requirements.

      1. Use documented business monitoring requirements to determine what systems, components, and applications are required to be monitored. (see the previous Task A)

      2. Based on the monitoring requirements, existing environmental characteristics, and long-term monitoring strategy, decide which monitoring technique would be best suited for each requirement.

      3. Specific ITM monitoring components can then be identified as the best approach for a given monitoring need. (OS TEMA, application specific TEMA's, Agent Builder, Universal Agent, agentless monitoring, etc).

    4. Establish historical data collection and warehousing design.

      1. Business requirements from the planning phase should be the driver for determining what historical data should be required, frequency of collection, summarization, and data retention.

      2. Use the HDC Load Projection spreadsheet to determine the size and potential growth rate of the Tivoli Data Warehouse.

      3. Determine the most appropriate database to be used for the Tivoli Data Warehouse.-Reference the supported databases as listed in the Installation and Setup Guide.-Consider existing database support skills within the customer organization.

    5. Establish the high availability design for the ITM infrastructure.

      1. Based on business requirements determined in the planning phase, establish the method to be employed for ITM availability.-Hot Standby-Primary and secondary remote Tivoli Enterprise Monitoring Server (RTEMS) configured at the TEMA.

      2. Customers may wish to employ their own technique for availability.-Clustering, IP pooling/aliasing, replication, etc.

    6. Document the size and layout of the ITM infrastructure.

      1. Based on existing IT infrastructure, monitoring requirements, and ITM capabilities, design and document the following:-Physical location of ITM components (infrastructure and TEMA's, historical DB)-Quantity of ITM components (TEMA's, RTEMS, WPA's)-Sizing of required underlying hosts-Note where changes to the existing infrastructure are required to meet the ITM architectural objectives.

      2. Special attention should be given to:-Applications that may generate a high volume of event traffic-Network latency, network reliability, firewalls, data communication protocol-Historical data collection requirements and volume

  4. Given a basic knowledge of an ITM deployment, determine the most efficient and expedient method of installation so that an installation plan can be developed.
    With emphasis on performing the following tasks:

    1. The existing hardware and software resources in the customer environment must be studied to determine where the ITM components should be installed.

      1. The IT staff's familiarity and expertise level with each of the available platforms for the deployment should be considered.(i.e. For a shop with limited Windows expertise, Linux or AIX might be the best deployment platform)

    2. Identify the number and types of agents to be deployed (typically 3 per server to be monitored on average).

    3. Does the intended h/w deployment platform have the necessary resources? (CPU, MEM, DISK, NETWORK)

      1. Determine the amount of data to be warehoused as well as the summarization and pruning schedules.

      2. Refer to "sizing guidelines" in the ITM Installation & Deployment Guide Redbooks.

    4. Is the necessary access to the deployment platform available?

      1. A Windows deployment must be done with administrator privileges, and the monitoring components must run as a user with administrator privileges.

      2. If a UNIX deployment must be done as a non-root user due to security guidelines, there are some additional steps that must be performed during the installation.-Use the same user to install all components.-Some file permissions will be required to be changed for every agent installation.

    5. Determine if a firewall gateway exists and between which components meet with network administrators to discuss ports to be utilized.

    6. The installation of each of the ITM components must be done in a particular order.

      1. Hub Tivoli Enterprise Monitoring Server

      2. remote TEMS (if required)

      3. Tivoli Management Agent Framework

      4. TEPS

      5. Tivoli Enterprise Portal Desktop Client

      6. Tivoli Data Warehouse

    7. Determine how monitoring agents can best be deployed.

      1. In most cases the creation of an agent depot for remote deployment of agents will be sufficient.

      2. If an enterprise-class software distribution product (for example,Tivoli Configuration Manager or Tivoli Provisioning Manager,) is already being used, it might be more efficient to utilize it for distribution of agents and patches.

      3. If RTEMS will be installed, the use of an NFS share can minimize the amount of administrative overhead to maintain the agent depot.

    8. Insure all servers to be monitored meet the prerequisites for agent installation.

      1. Adequate disk space (500 MB for an agent & logs)

      2. User account to be used (Admin or root will make deployment easier.)

  5. Given experience and knowledge with ITM, describe the features and functions that allow ITM Agents to run independently of the TEMS, so that the features and functions of Agent Autonomy have been described.
    With emphasis on performing the following tasks:

    1. The TEMA:

      1. TEMA can run independently of the TEMS.

      2. Collects data, run situations and register events when they are disconnected from the TEMS.

      3. The TEMA is configured to run autonomously by default.

      4. The TEMA can use rules defined in an XML file so that:-Situations can be defined and run locally.-Events can be sent as SNMP alerts or Event Integration Facility (EIF) Events to a receiver.-Collect and save historical data locally.

      5. The TEMA will store situation events that will be forwarded to the TEMS upon reconnection.

      6. Situations that require evaluation at the TEMS are unable to run if there is no connection.

    2. The Tivoli System Monitor Agent:

      1. Is installed where there is no Tivoli Management Services or TEMA installed, except for Agent Builder Agents.

      2. Is an OS agent that never connects to a TEMS.

      3. Uses the same code as a TEMA .

      4. Does not use Java for installation.

      5. Has a smaller software footprint than a TEMA.

      6. Uses XML files for situation and SNMP alert definitions.

    3. Both Agents can run private situations.

  6. Given experience and knowledge with ITM, describe the features and functions provided by ITM that allow local monitoring of remote servers, so that features and functions of agentless monitoring have been described
    With emphasis on performing the following tasks:

    1. Provides the ability to monitor remote servers from a central location.

    2. Can monitor Windows, Linux, AIX, Solaris and HP-UNIX operating systems

    3. Does not require any software to be installed on the remote servers.

    4. Requires a network connection to the remote server.

    5. Requires a valid userid/password or SNMP community name and password on the remote server.

    6. Is an agent installed on a server other than the one to be monitored.

    7. A single agent can monitor more than a remote server.

    8. An agent can monitor a platform that is different to the one it is installed on.

    9. The agentless monitoring method does not provide as many metrics as a standard OS agent.

    10. Can be configured by using command line(Tacmd, itmcmd), Manage Tivoli Enterprise Monitoring Server or the Tivoli Enterprise Portal.

    11. Uses SNMP, WMI(Windows) or CIM(Solaris) as the methods for data collection.

  7. Given appropriate ITM knowledge and experience, describe the ITM KDE Gateway function so that a good understanding of the KDE Gateway features and operations can be obtained.
    With emphasis on performing the following tasks:

    1. Understand the function of KDE Gateway.

      1. The KDE Gateway is a feature of ITM Basic Services that allows traversal of complex firewall configurations. The service is provided by the OS agent at the service level and is configured with XML. The KDE Gateway feature in ITM enables additional end-to-end connectivity options for use in environments with specific TCP/IP connection management policies.

    2. Understand the operation, feature and components of KDE Gateway.

      1. The KDE Gateway is based on a new proxy component resident in the base ITM/OMEGAMON Platform processes: TEPS, TEMS, Warehouse Proxy, and TEMAs. The Gateway is implemented in the KDE Transport layer; it introduces a level of abstraction creating a socket-independent layer of "Monitor" calls. Monitor call operations replace native socket operations in the KDE Transport layer. Native socket operations, in turn, are used in the socket dependent layer to implement Monitor calls and KDE Gateway operations. Since these changes occur under the KDE Interface, there are no configuration or application changes required within the infrastructure to enable KDE Gateway support.

      2. The Firewall Gateway provides the following functionality:-Gateway instances interoperate over a single physical relay connection. Logical connections are multiplexed over the relay. The origination direction of the relay connection is configurable to match enterprise firewall transit requirements.-Relay support enables a logical connection to span multiple firewall zones. Each relay instance can optionally provide access to the upstream management network. Multiple relays can be chained to provide seamless hops across multiple zones.-Proxy support provides a transparent interface to ITM components. Server proxy components reside downstream and listen for inbound connections. Client proxy components reside upstream and make connections to services on behalf of downstream endpoints.-All ports used by gateway instances are configurable. Port pooling is available to constrain client proxy connections to designated port values.-Multiple failover addresses can be configured for all gateway connections.

    3. Understand the KDE Gateway topology.

      1. The gateway topology is described starting with the outer-most network interface and ending with the inner-most network interface. We call the outer-most the 'downstream' interface. We use the traditional model of application clients initiating requests on the downstream interface destined upstream to the application server. The application server resides on the upstream interface.

      2. A KDE Gateway is composed of one or more Gateway zones. Gateway zones are described starting with the downstream (or outer-most) zone and moving to the upstream (inner-most) zone. A Gateway zone contains one or more upstream Gateway interfaces and their associated downstream Gateway interfaces. The upstream Gateway interface is always defined first.

      3. A Gateway interface can assume one of three roles: listen, connect or proxy. (The proxy and relay functions discussed above are actually Gateway interfaces with specific upstream and downstream roles.) A Gateway interface defined with "role=listen" opens a physical port and listens on that port for incoming requests. A Gateway interface defined with "role=connect" obtains a physical port and issues a connection to the target IP address and port defined. (Another Gateway interface should have a "role=listen" defined as the target of this connect interface.)

      4. A gateway interface defined with "role=proxy" is a logical interface: it uses no physical network interface. "Role=proxy" functions as a server proxy if it is defined on the downstream interface. "Role=proxy" functions as a client proxy if it is defined on the upstream interface. A Gateway server proxy interface will capture all the connect requests within the physical process where the Gateway element is defined. These requests are routed across to the upstream Gateway interface defined.

    4. Understand how a KDE Gateway is activated.

      1. The gateway feature can be activated within any ITM process. The configuration variable "KDE_GATEWAY" is set to the XML configuration file name. A line of the form "KDE_GATEWAY=filename" must be added to the following configuration files, depending on your environment:-On Windows computers, configuration variables for the Windows OS agent are located in the ITMHOME/tmaitm6/KNTENV file.-On UNIX computers, configuration variables for the UNIX OS agent are located in the ITMHOME/config/ux.ini and ITMHOME/config/ux.config files. Add the entry to both files for reliable results.-On Linux computers, configuration variables for the Linux OS agent are located in the ITMHOME/config/lz.ini and ITMHOME/config/lz.config files. Add the entry to both files for reliable results.

      2. After you make these changes, stop and restart the monitoring agents.


Section 2-1: Installation


  1. Given installation media, and a target system, install and configure both the Hub Tivoli Enterprise Monitoring Server and remote Tivoli Enterprise Monitoring Server (RTEMS), so that both of them are operational.
    With emphasis on performing the following tasks:

    1. Installation of Windows Hub Tivoli Enterprise Monitoring Server

      1. Using installation media, launch installation wizard by double clicking ‘setup.exe'.

      2. Accept license agreement.

      3. Accept or set desired installation directory.

      4. Accept or set desired encryption key.

      5. On "Select Features" window, tick the check box for "Tivoli Enterprise Monitoring Server".

      6. Review installation summary details, and start the installation process.

      7. After installation has completed, configuration of Windows Hub Tivoli Enterprise Monitoring Server will start.-Choose Hub as the type of Monitoring Server or this instance.-If required, change the Tivoli Enterprise Monitoring Server (TEMS) name from the default.-If required, change or add the TEMS communication protocol(s).-Apply Application Support to the TEMS by starting the process. (This step is required to be repeated for any agent products).-Acknowledge results of Application Support seeding.-Click to finish the installation.

    2. Installation of Windows RTEMS

      1. Using installation media, launch installation wizard by double clicking ‘setup.exe'.

      2. Accept license agreement.

      3. Accept or set desired installation directory.

      4. Accept or set desired encryption key.

      5. On "Select Features" window, tick the check box for "Tivoli Enterprise Monitoring Server".

      6. Review installation summary details, and start the installation process.

      7. Configuration of Windows RTEMS-Choose REMOTE as the type of Monitoring Server or this instance.-If required, change the TEMS name from the default.-If required, change or add the TEMS communication protocol(s).-Set hostname or IP address of Hub Tivoli Enterprise Monitoring Server relevant to the appropriate protocol.-Apply Application Support to the TEMS by starting the process. (This step is required to be repeated for any agent products).-Acknowledge results of Application Support seeding.-Click to finish the installation.

    3. Installation of UNIX/Linux Hub Tivoli Enterprise Monitoring Server

      1. Using installation media, run the ./install.sh script.

      2. Accept, or set desired installation directory.

      3. Select option 1 "Install products to the local host".

      4. Accept or set desired encryption key.

      5. Select option 1 for new installation.

      6. Select option 5 for installation of binaries for current Operating System.

      7. Select option 1 to confirm choices and begin installation.

      8. Accept or set desired name for TEMS.

      9. Select option 2 to install additional products or product support.

      10. Do you want to seed product support on the TEMS? If so, select 1 which will install all Application Support by default.

      11. Enter 3 for new (default).

      12. Configuration of UNIX/Linux Hub Tivoli Enterprise Monitoring Server-Change to the /bin directory.-Run the following command : "./itmcmd config -S -t ", where is the name of the TEMS set in previous step.-Accept choice that this install will be for a Hub Tivoli Enterprise Monitoring Server (as defined by *LOCAL).-Accept or set desired hostname of the host if not correct.-Accept or set the desired communication protocol(s).-If required, enter partition file filename for firewall configuration.-If required, choose option 1 for Configuration Auditing, or 2 to turn this feature off.-Accept the default for no Hot Standby (it should be installed after install/config has been verified as successful).-Accept or set the Optional Primary Network name.-Accept or set whether Validation Security is required for the TEMS.-Select if Event forwarding to TEC/Netcool/OMNIbus is required (option 1).-Set Event Integration Facility (EIF) Server hostname.-Set EIF Port number.-Accept or set whether to enable Workflow Policy Activity.-Accept default SOAP configuration.-Configuration ends.

    4. Installation of UNIX/Linux RTEMS

      1. Using installation media, run the ./install.sh script.

      2. Accept, or set desired installation directory.

      3. Select option 1 "Install products to the local host".

      4. Accept or set desired encryption key.

      5. Select option 1 for new installation.

      6. Select option 5 for installation of binaries for current Operating System.

      7. Select option 1 to confirm choices and begin installation.

      8. Accept or set desired name for TEMS.

      9. Select option 2 to install additional products or product support.

      10. Do you want to seed product support on the TEMS? If so, select 1 which will install all Application Support by default.

      11. Enter 3 for new (default).

      12. Configuration of UNIX/Linux RTEMS-Change to the /bin directory.-Run the following command : "./itmcmd config -S -t ", where is the name of the TEMS set in previous step.-Accept choice that this installation will be for a RTEMS by entering "remote".-Accept or set desired hostname of the host if not correct.-Accept or set the desired communication protocol(s).-If required, enter partition file filename for firewall configuration.-If required, choose option 1 for Configuration Auditing, or 2 to turn this feature off.-Accept the default for no Hot Standby (it should be installed after install/config has been verified as successful).-Accept or set the Optional Primary Network name.-Accept default for No User Validation (option is valid only for Hub).-Accept default for No Event Integration (option is valid only for Hub).-Accept default for Workflow Policy forwarding (option is valid only for Hub).-Accept default for SOAP (option is valid only for Hub).-Configuration ends.

  2. Given the installation media and a host system, install and configure the Tivoli Enterprise Portal Server (TEPS), so that the users have a portal to which they can log in.
    With emphasis on performing the following tasks:

    1. Windows:

      1. Install phase-Locate the IBM Tivoli Monitoring V6.2.2 (ITM) Installation and Setup Guide and open the section on Installing the TEPS.-Extract the installation media.-Start the installation by clicking on setup.exe in the Windows sub-directory (where the installation media has been extracted).-Follow the prompts responding accordingly. Local customization will affect the answers for:-the location of the Hub Tivoli Enterprise Monitoring Server-the encryption key-LDAP configuration and credentials

      2. Configuration phase-Launch the Manage Tivoli Enterprise Services application.-Right-click on the Tivoli Enterprise Portal (TEP) line and select configure (or reconfigure).-Follow the prompts.-(Re)Start the Portal Server (note: the TEPS starts the Eclipse Help Server and thus may fail to start unless the TEPS and HelpServer processes are stopped).

    2. UNIX/Linux:

      1. Install phase-Extract the installation media.-Start the installation by clicking on install.sh script (where the installation media has been extracted).-Follow the prompts responding accordingly. Local customization will affect the answers for:-the location of the Hub Tivoli Enterprise Monitoring Server -the encryption key-LDAP configuration and credentials

      2. Configuration phase-Execute the ./itmcmd config -A cq command to configure the TEPS.-Follow the prompts.-(Re)Start the Portal Server (note: the TEPS starts the Eclipse Help Server and thus may fail to start unless the TEPS and HelpServer processes are stopped).-Use the ./itmcmd agent start cq command to start the TEPS.-Use the ./itmcmd agent stop cq,kf to stop both the TEPS and HelpServer processes.

  3. Given that the ITM Hub Tivoli Enterprise Monitoring Server and RTEMS and TEPS are installed, use either the itmcmd CLI or the Manage Tivoli Enterprise Services to add Application Support, so that the attributes are loaded to support the Workspaces, Queries, Situations and Help for the various installed Tivoli agents.
    With emphasis on performing the following tasks:

    1. Locate the section in the ITM Install Guide on Installing and enabling Application Support for reference.

      1. For ITM this can be located at: http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc_6.2.2fp2/agent_support.htm

    2. Download the installation files for each required agent/ product if they are not found on the ITM Media DVD. zOS, ITCAM, MQ Series are examples of files that are not on the DVDs.

      1. URL for Locating ITM Workspace Application Support Files for z/OS agents - this site contains Application Support files for most if not all Tivoli agents: http://www-01.ibm.com/support/docview.wss?rs=2045&context=SS2JNN&context=SSC6MLB&context=SSC6MLD&context=SSC6ML7&context=SSC6ML8&context=SSNU68&context=SSRJ5K&context=SSRHXC&q1=application+support&uid=swg21255545&loc=en_US&cs=utf-8&lang=en

    3. Extract the downloaded files (these can be placed into a temporary directory) and follow the install and enablement step below: (read the readme to determine the specific installation requirements).

    4. Adding Application Support for Windows TEMS and TEPS

      1. Execute the setup.exe file in the Windows sub-directory.

      2. Select the agent products for each of the display components (TEMS, TEPS, TEP Client). -Note: Next 4 steps require the user log in to the TEP.

      3. Open the product HELP and verify the agent/ product help has been loaded.

      4. Open the Situation Editor and verify that the agent/ product provided situations are loaded.

      5. Open the QUERY editor and verify that the agent/ product provided queries are loaded.

      6. If possible, NAVIGATE the PHYSICAL topology locate an agent instance and verify the agent/ product provided workspaces are loaded.

    5. Adding Application Support for non-Windows TEMS and TEPS

      1. Launch the install.sh script and follow the steps described in the ITM Install Guide by using the Installing and enabling Application Support section. A pass-through the script is required for each of the ITM components (TEMS, TEPS, and TEP Client).

      2. Execute the commands by using the ITM CLI depending on the ITM component:-For the TEMS: itmcmd support-For the TEPS and TEP Client: itmcmd config-Note: Next 4 steps require the user log in to the TEP.

      3. Open the product HELP and verify the agent/ product help has been loaded.

      4. Open the Situation Editor and verify that the agent/ product provided situations are loaded.

      5. Open the QUERY editor and verify that the agent/ product provided queries are loaded.

      6. If possible, NAVIGATE the PHYSICAL topology locate an agent instance and verify the agent/ product provided workspaces are loaded.

  4. Given the need to install and configure the Summarization and Pruning Agent, define the installation and configuration tasks, so that the S&P Agent is (running and connected to the TEMS and Tivoli Data Warehouse) installed and configured.
    With emphasis on performing the following tasks:

    1. Ensure the ITM Base Installation image for the platform to be installed upon is available.

      1. If the image is in a tar or zip format then it is required to be extracted.-UNIX / Linux - untar the image to a temporary location.-Windows - unzip the image to a temporary location.

      2. If the image is on DVD then it should be inserted into a DVD drive that is accessible to the server that installation will take place.

    2. Ensure the required prerequisites are in place to include.

      1. The Database that will store historical data is installed and configured.-The WAREHOUS database has been created as per the ITM Installation and Setup Guide.

      2. The TEMS and TEPS have been installed and configured as per the ITM Installation and Setup Guide.

      3. If the database is installed on a remote server to the S&P Agent that the required client/files to create an ODBC/JDBC connection are available on the S&P server.

      4. The userid that will be used to perform the install has root (UNIX/Linux) or Administrator (Windows) privileges.

    3. Installation and configuration

      1. UNIX/Linux -In a command line cd to the extracted image.-Run ./install.sh.-Enter an installation directory or accept the default, press enter.-If the installation directory does not exist you are asked if you want to create it, type y and hit enter.-At the prompt enter 1 to select ‘Install products to the local host'.-Press Enter to read the license agreement followed by 1 to accept the license.-Enter an encryption key or hit enter to accept the default.-Enter 1 to install ITM Components for this OS.-Enter to confirm.-Select 1 for the S&P Agent and hit enter twice.-Enter 2, do not install additional products.-Once the postprocessing has completed cd to the /bin.-Enter ./itmcmd manage.-In the Manage Tivoli Enterprise Management Services window, right click on the Summarization and Pruning Agent and select ‘configure'.-In the TEMS connection tab, enter the TEMS Hostname, leave all other options to default.-In the tab ‘Agent Parameters' in Configure Summarizing and Pruning Agent :-In JDBC drivers, click add and browse to the location of the required jar files :-DB2 - /java/db2jcc.jar and /java/db2jcc_license_cu.jar -Oracle - /jdbc/lib/ojdbc14.jar-In Warehouse URL:-DB2 - Jdbc:db2//:50000/WAREHOUS-Oracle - jdbc:oracle:thin:@:1521:WAREHOUS-In Warehouse User and Warehouse Password, enter the userid and password that was created in the WAREHOUS database, which has been created as per the ITM Installation and Setup Guide.-In TEPS Server Host, enter the hostname of the server the TEPS is installed on.-Click on ‘test database connection' to ensure the connection works.-Leave all other parameters to default, click save and close.-Right click on the Summarization and Pruning Agent and click start.

      2. Windows:-Cd to the Windows or WIA64(Itanium) directory of the extracted image.-Double click setup.exe.-Click next on Welcome Window.-Click to Accept the license agreement and click next.-Choose the directory to install the agent, or accept the default and click next.-Provide your own encryption key or accept the default, click next and then OK to accept the key.-Expand Tivoli Enterprise Monitoring Agent (TEMA) and select Summarization and Pruning Agent and click next.-Select the program folder or accept the default, click next.-Click next to start copying files, this will take a few minutes.-In the setup type configuration window, ensure both tick boxes are ticked, click next.-In the configuration defaults for connection to a TEMS, change the Hostname entry to that of the Hub Tivoli Enterprise Monitoring Server, leave all other options to default (port, protocol, entry options and use case as typed), click OK.-Click finish.-In the Manage Tivoli Enterprise Management Services window, right click on the Summarization and Pruning Agent and select ‘configure using defaults' and click Yes.-In the tab ‘Sources' in Configure Summarizing and Pruning Agent:-In JDBC drivers click add and browse to the location of the required jar files :-DB2 - \java\db2jcc.jar and \java\db2jcc_license_cu.jar -MS SQL - \sqljdbc_1.1\enu\sqljdbc.jar-Oracle - \jdbc\lib\ojdbc14.jar-In Warehouse URL:-DB2 - Jdbc:db2//:50000/WAREHOUS-MS SQL - jdbc:sqlserver//:1433;databaseName-WAREHOUS-Oracle - jdbc:oracle:thin:@:1521:WAREHOUS-In Warehouse User and Warehouse Password, enter the userid and password that was created in the WAREHOUS database, which has been created as per the ITM Installation and Setup Guide.-In TEPS Server Host, enter the hostname of the server the TEPS is installed on.-Click on ‘test database connection' to ensure the connection works.-Leave all other parameters to default, click OK, save and close.-Right click on the Summarization and Pruning Agent and click start.

  5. Given the need to install and configure the Warehouse Proxy Agent, define the installation and configuration tasks, so that the Warehouse Proxy Agent is (running and connected to the TEMS and Tivoli Data Warehouse) installed and configured.
    With emphasis on performing the following tasks:

    1. Ensure the ITM Base Installation image for the platform to be installed upon is available.

      1. If the image is in a tar or zip format then it is required to be extracted.-UNIX/Linux - untar the image to a temporary location.-Windows - unzip the image to a temporary location.

      2. If the image is on DVD then it should be inserted into a DVD drive that is accessible to the server that installation will take place.

    2. Ensure the required prerequisites are in place to include.

      1. The Database that will store historical data is installed and configured.-The WAREHOUS database has been created as per the ITM Installation and Setup Guide.-If the WAREHOUS database is on a remote server to the one the Warehouse Proxy Agent is installed it is required to be catalogued as per the ITM Installation and Setup Guide.-Define an ODBC connection.

      2. The TEMS and TEPS have been installed and configured as per the ITM Installation and Setup Guide.

      3. Ensure the required client/files to create an ODBC/JDBC connection are available on the Warehouse Proxy server.

      4. The User ID that will be used to perform the install has root (UNIX/Linux) or Administrator (Windows) privileges.

      5. Warehouse Configuration in a UNIX/Linux environment requires X11 GUI for configuration. Ensure appropriate libraries are installed and configured correctly to support this requirement.

    3. Installation and configuration

      1. UNIX/Linux:-In a command line cd to the extracted image.-Run ./install.sh.-Enter an installation directory or accept the default, press enter.-If the installation directory does not exist you are asked if you want to create it, type y and hit enter.-At the prompt enter 1 to select ‘Install products to the local host'.-Press Enter to read the license agreement followed by 1 to accept the license.-Enter an encryption key or hit enter to accept the default.-Enter 1 to install ITM Components for this OS.-Enter to confirm.-Select 5 for the Warehouse Proxy Agent and hit enter twice.-Enter 2, do not install additional products.-Once the post-processing has completed cd to the /bin.-Enter ./itmcmd manage.-In the Manage Tivoli Enterprise Management Services window, right click on the Warehouse Proxy Agent and select ‘configure'.-In the TEMS connection tab, enter the TEMS Hostname, leave all other options to default.-In the tab ‘Agent Parameters' in Configure Summarizing and Pruning Agent:-In JDBC drivers click add and browse to the location of the required jar files:-DB2 - /java/db2jcc.jar and /java/db2jcc_license_cu.jar -Oracle - /jdbc/lib/ojdbc14.jar-In Warehouse URL:-DB2 - Jdbc:db2//:50000/WAREHOUS-Oracle - jdbc:oracle:thin:@:1521:WAREHOUS-In Warehouse User and Warehouse Password, enter the User ID and password that was created in the WAREHOUS database, which has been created as per the ITM Installation and Setup Guide.-Click on ‘test database connection' to ensure the connection works.-Leave all other parameters to default, click save and close.-Right click on the Summarization and Pruning Agent and click start.

      2. Windows:-Cd to the Windows or WIA64(Itanium) directory of the extracted image.-Double click setup.exe.-Click next on Welcome Window.-Click to Accept the license agreement and then click next.-Choose the directory to install the agent, or accept the default and click next.-Provide your own encryption key or accept the default, click next and then OK to accept the key.-Expand TEMA and select Warehouse Proxy and click next.-Select the program folder or accept the default, click next.-Click next to start copying files, this will take a few minutes.-In the setup type configuration window ensure both tick boxes are ticked, click next.-In the configuration defaults for connection to a TEMS, change the Hostname or IP address entry to that of the Hub Tivoli Enterprise Monitoring Server, leave all other options to default (port, protocol, entry options and use case as typed), click OK.-Click finish.-In the Manage Tivoli Enterprise Management Services window, right click on the Warehouse Proxy Agent and select ‘configure using defaults' and click OK to the warning message.-Click Yes to configure the ITM Data source.-Select the database type and click OK.-Use the default settings for data source name and database name.-Enter the required passwords for the database admin user and ITM user.-Click OK twice.-Click YES to complete the configuration.-Right click on the Warehouse Proxy Agent and click start.


Section 2-2: Installation


  1. Given working knowledge of the ITM components, perform an install of OS agents on several hosts by using both local and remote deployment methods so that they can be monitored from the TEPS console.
    With emphasis on performing the following tasks:

    1. Local Install on the Linux host

      1. In the directory where you extracted the installation files, run the following command: ./install.sh

      2. When prompted for the ITM home directory, press Enter to accept the default directory (/opt/IBM/ITM) or type the full path to a different directory.

      3. If the installation directory does not already exist, you are asked if you want to create it. Type y to create this directory and press Enter.

      4. The following prompt is displayed. -Select one of the following:-Install products to the local host.-Install products to depot for remote deployment (requires TEMS).-Install TEMS support for remote seeding-Exit install.-Please enter a valid number:-Note: This prompt might vary depending on the installation image from which you are installing.

      5. Type 1 to start the installation and display the software license agreement.

      6. Press Enter to read through the agreement.

      7. Type 1 to accept the agreement and press Enter.

      8. You are prompted for a 32 character encryption key.-Type a 32 character encryption key (or accept the default) and press Enter. -This key should be the same as the key that was used during the installation of the monitoring server to which this monitoring agent connects.-Note: This step applies only to those agents that you install from the ITM installation image. Agents installed from the agent installation image isn't required to provide the encryption key.

      9. A numbered list of available operating systems is displayed.

      10. Type 1 to install the ITM support for your current operating system. Press Enter.

      11. A numbered list of available components is displayed.

      12. Type the number that corresponds to the monitoring agent or agents that you want to install.

      13. A list of the components to be installed is displayed.

      14. Type 1 to confirm the installation.-The installation begins.

      15. After all of the components are installed, you are asked whether you want to install additional products or product support packages.

      16. Type 2 and press Enter.

      17. Use the following steps to configure your monitoring agent:-Run the following command:./itmcmd config -A pc where pc is the product code for your agent. -For the UNIX Agent, use the product code "ux"; for Linux, use "lz" (Note - case sensitive).

      18. Ensure that the appropriate Application Support has been installed on the TEPS & TEMS host(s).-Run the cinfo -t command and verify that the Application Support components for tps, tpm, and tpw all appear.

      19. Log in to the TEPS and verify the new Linux host appears in the Navigator.

    2. Remote deployment to a Windows host

      1. In order to do a remote deployment, the agent must first be added to the TEMS agent depot and the Application Support for the agent must also be installed.

      2. The installation image cannot be used to populate the agent depot with agents for a platform other than the one the TEMS is running.-If the TEMS is running on AIX, the install image cannot be used to populate the agent depot with the NT agent required for monitoring a Windows host.-Instead, the ‘tacmd addbundles' command must be used to add monitoring agents for Windows.

      3. Mount the CD containing the Windows agents on /mnt/cdrom.-Locate the directory which contains the KNTWINNT.dsc file (should be /mnt/cdrom/WINDOWS/Deploy)

      4. Execute the command ‘tacmd listbundles -i /mnt/cdrom/WINDOWS/Deploy and verify the agents you want to install to the depot are listed.-Execute the command ‘tacmd addbundles -i /mnt/cdrom/WINDOWS/Deploy'.

      5. Execute the command ‘tacmd viewdepot' and verify the new agents have been added to the depot.

      6. Execute the command ‘tacmd createnode -h -u Administrator.-You will be prompted for the Administrator password.

      7. The request will be queued for deployment and tacmd will return a transaction ID.-Check the status of the remote deployment by using ‘tacmd getdeploystatus -g <transaction ID>.

      8. Verify the deployment request completes successfully.

      9. Log in to the TEPS and verify that the new Windows host appears in the Navigator.

  2. Given the need to implement high-availability monitoring servers, describe the steps required to install and configure the TEMS to operate in Hot Standby mode, so that Hot Standby is properly configured and a high availability environment is configured and operational for use..
    With emphasis on performing the following tasks:

    1. Install the TEMS software on two servers to act as Hubs/Hot Standby. Install the TEMS software on one or more servers to act as remote(s) if required.

      1. The ITM software on both hub monitoring servers must be at the same release and maintenance level.

      2. Application Support for all required applications must be installed on both monitoring servers.

      3. Ensure the Secondary Hub is not started when the Primary Hub is being configured.

    2. Complete the following steps to configure the Primary Hub to point to the Secondary Hub as its backup or standby server:

      1. On the Manage Tivoli Monitoring Services window, right-click the name of the monitoring server that you are going to use as the Primary Hub and click Configure.

      2. Click the Advanced Settings tab.

      3. Select Specify Hot Standby.

      4. Type the host name of the Secondary Hub in the Standby TEMS Site field.

      5. Select the type of protocol to use for Hot Standby. This must be the same protocol on both the Primary Hub and Secondary Hub.

      6. If you specified any backup protocols for the Primary Hub, specify identical protocols for the Secondary Hub.

      7. Click Save.

      8. Stop and restart the monitoring server.

    3. Configuring the Secondary Hub: Complete the following steps to configure the Secondary Hub to point to the Primary Hub as its backup or standby server.

      1. On the Manage Tivoli Monitoring Services window, right-click the name of the monitoring server that you are going to use as the Secondary Hub and click Configure.

      2. Click the Advanced Settings tab.

      3. Select Specify Hot Standby.

      4. Type the host name of the Primary Hub in the Standby TEMS Site field.

      5. Select the type of protocol to use for Hot Standby. This protocol must be the same protocol that is specified on both the Primary Hub and Secondary Hub.

      6. If you specified any backup protocols for the Secondary Hub, specify identical protocols for the Primary Hub.

      7. Click Save.

      8. Start the monitoring server.

    4. Configuring the Hot Standby feature for remote monitoring servers

      1. Complete the following steps to configure a remote monitoring server to switch to a standby hub when the active hub monitoring server becomes unavailable.

      2. Procedure

      3. On the Manage Tivoli Monitoring Services window, right-click the name of a remote monitoring server, and click Configure.

      4. Click the Advanced Settings tab.

      5. Select Specify Hot Standby.

      6. Type the host name of the Secondary Hub in the Standby TEMS Site field.

      7. Select the type of protocol to use for Hot Standby. This is the same protocol on both the Primary Hub and Secondary Hub.

      8. If you specified any backup protocols for the hub monitoring servers, specify identical protocols for the remote monitoring server.

      9. Click Save.

      10. Stop and restart the remote monitoring server.

  3. Given that ITM Agent deployment transactions are asynchronous (that is, they run in the background), describe how to retrieve the deployment status and the stages of deployment, so that how to query agent deployments for status and their meanings are understood.
    With emphasis on performing the following tasks:

    1. Get the monitoring deployment status via any of these methods.

      1. The tacmd getDeployStatus CLI command.

      2. The TEP's Deployment Status workspaces.

      3. Deployment attribute groups, and situations created by using the TEP that are based on these groups.

    2. Understand the status of the deployments.

      1. Pending - The transaction is waiting in the queue to begin processing.

      2. In-Progress - The transaction has begun the deployment process but has not yet finished.

      3. Success- The transaction has completed successfully.

      4. Failed Retrying - The transaction experienced a recoverable error during the deployment process and will be restarted periodically at the point of failure for a predefined number of iterations.

      5. Failed - The transaction has completed with an unrecoverable failure, or the number of retry attempts has been exhausted. Consult the status message included with the transaction status for more information about the failure.

  4. Given the authority to perform installations, install the Agent Builder tool so that is ready to be used for creating custom agents.
    With emphasis on performing the following tasks:

    1. Uninstall any previous version of the Agent Builder.

      1. Windows: Use Add or Remove Programs from the Windows Control Panel.

      2. UNIX/Linux: run /uninstall/uninstaller.

    2. Start Install:

      1. Windows: run setup.bat from the install directory.

      2. UNIX/Linux: run setup.sh from the install directory.

    3. Response to each question

      1. Select a language.

      2. Accept the terms in the license agreement.

      3. Specify an install directory.

      4. Verify information entered is correct and select next.

    4. Verify Agent Building installation by starting the user interface.

      1. Windows: Select START - Agent Builder

      2. UNIX/Linux: run /agentbuilder . (This requires a GUI for UNIX.)

  5. Given an installed TEMS and an ITM Fixpack, install the FixPack so that the existing TEMS is upgraded to the required level.
    With emphasis on performing the following tasks:

    1. Upgrade of Windows Hub Tivoli Enterprise Monitoring Server..

      1. Ensure the Hub Tivoli Enterprise Monitoring Server being upgraded has been properly backed up.

      2. Using installation media, launch installation wizard by double clicking ‘setup.exe'.

      3. Change the installation type to "Modify" to upgrade existing components.

      4. Accept license agreement.

      5. Accept or set desired installation directory.

      6. Accept or set desired encryption key.

      7. Accept already selected "Features" (as an upgrade this should not be changed).

      8. Review installation summary details, and start the installation process.

      9. After install has completed, configuration of Windows Hub Tivoli Enterprise Monitoring Server will start.-Choose Hub as the type of Monitoring Server or this instance.-If required, change the TEMS name from the default.-If required, change or add the TEMS communication protocol(s).-Apply Application Support to the TEMS by starting the process.-Acknowledge results of application support seeding.-Click to finish the installation.

    2. Upgrade of Windows RTEMS.

      1. Ensure the RTEMS being upgraded has been properly backed up.

      2. Using installation media launch installation wizard by double clicking ‘setup.exe'.

      3. Change the installation type to "Modify" to upgrade existing components.

      4. Accept license agreement.

      5. Accept or set desired installation directory.

      6. Accept or set desired encryption key.

      7. Accept already selected "Features" (as an upgrade this should not be changed).

      8. Review installation summary details, and start the installation process.

      9. Configuration of Windows RTEMS-Choose Remote as the type of Monitoring Server or this instance.-If required, change the TEMS name from the default.-If required, change or add the TEMS communication protocol(s).-Set hostname or IP address of Hub Tivoli Enterprise Monitoring Server relevant to the appropriate protocol.-Apply Application Support to the TEMS by starting the process.-Acknowledge results of application support seeding.-Click to finish the installation.

    3. Installation of UNIX/Linux Hub Tivoli Enterprise Monitoring Server

      1. Ensure the Hub Tivoli Enterprise Monitoring Server being upgraded has been properly backed up.

      2. Using installation media run the ./install.sh script.

      3. Accept, or set desired installation directory.

      4. Select option 1 "Install products to the local host".

      5. Accept or set desired encryption key.

      6. Select option 1 for new installation.

      7. Select option 5 for installation of binaries for current Operating System.

      8. Select option 1 to confirm choices and begin installation.

      9. Accept or set desired name for TEMS.

      10. Configuration of UNIX/Linux Hub Tivoli Enterprise Monitoring Server-Change to the /bin directory.-Run the following command: "./itmcmd config -S -t ", where is the name of the TEMS set in previous step.-Accept choice that this install will be for a Hub Tivoli Enterprise Monitoring Server (as defined by *LOCAL).-Accept or set desired hostname of the host if not correct.-Accept or set the desired communication protocol(s).-If required, enter partition file filename for firewall configuration.-If required, choose option 1 for Configuration Auditing, or 2 to turn this feature off.-Accept the default for no Hot Standby (it should be installed after install/config has been verified as successful).-Accept or set the Optional Primary Network name.-Accept or set whether Validation Security is required for the TEMS.-Select if Event forwarding to TEC/Netcool/OMNIbus is required (option 1).-Set EIF Server hostname.-Set EIF Port number.-Accept or set whether to enable Workflow Policy Activity.-Accept default SOAP configuration.-Configuration ends.

      11. Special considerations should be made when upgrading a Hot Standby environment.

    4. Upgrade of UNIX/Linux RTEMS.

      1. Ensure the RTEMS being upgraded has been properly backed up.

      2. Using installation media run the ./install.sh script.

      3. Accept, or set desired installation directory.

      4. Select option 1 "Install products to the local host".

      5. Accept or set desired encryption key.

      6. Select option 1 for new installation.

      7. Select option 5 for installation of binaries for current Operating System.

      8. Select option 1 to confirm choices and begin installation.

      9. Accept or set desired name for TEMS.

      10. Configuration of UNIX/Linux RTEMS-Change to the /bin directory.-Run the following command : "./itmcmd config -S -t ", where is the name of the TEMS set in previous steps.-Accept choice that this install will be for a RTEMS by entering "remote".-Accept or set desired hostname of the host if not correct.-Accept or set the desired communication protocol(s).-If required, enter partition file filename for firewall configuration.-If required, choose option 1 for Configuration Auditing, or 2 to turn this feature off.-Accept or set the Optional Primary Network name.-Accept default for No User Validation (option is valid only for Hub).-Accept default for No Event Integration (option is valid only for Hub).-Accept default for Workflow Policy forwarding (option is valid only for Hub).-Accept default for SOAP (option is valid only for Hub).-Configuration ends.


Section 3: Configuration


  1. Given the need to integrate a customer-written fault detection script into the IBM Tivoli Monitoring V6.2.2 (ITM) infrastructure, perform the required steps to create a custom agent on that will execute the script and return it's status to the Tivoli Enterprise Monitoring Server (TEMS) so that a working custom agent is ready to be deployed.
    With emphasis on performing the following tasks:

    1. Start the Tivoli Monitoring Agent Builder program on the Windows workstation.

      1. Select File -> New -> IBM Tivoli Monitoring Agent.

      2. Enter a Project Name (required input).

      3. Enter Copyright data (required input).

      4. Select the OS platforms where the agent will be deployed (All UNIX).

      5. Click "Next".

    2. Input Agent Product Code, versioning and company information.

      1. Verify the agent product code is not already in use (K00 is default the first time the Agent Builder is used).

      2. Input a Company identifier (required input).

      3. Determine if multiple instances of the custom agent must be supported (leave checkbox Unchecked).-If multiple instances is selected, configuration information MUST be added - otherwise "Error KQZ8120E" will appear in "Problems" frame.

      4. Select the minimum level of ITM Agent requires (V6.2 or V6.2.1).

      5. Click "Next".

    3. Define the Agent Initial Data Source.

      1. monitoring data category = "Command or Script" (choices are: A process, Data from a server, Network management data, Logged data, Command or script, Data source groupings)

      2. data source ="A command return code" (for each of the above categories there are a subset of data sources to select from - the two choices possible for the Command or script category are: A command return code, or Output from a script)

    4. Enter the information for the command return code.

      1. For every possible return code value from the customer program.-Assign a Return Code Type to each value. (SUCCESS, GENERAL_ERROR, ALREADY_RUNNING, NOT_RUNNING, PREREQ_NOT_RUNNING, WARNING, DEPENDENT_NOT_RUNNING)-Add a message text associated with each return code value.

      2. At least two return codes must be defined (success & failure).

    5. Specify the information for the customer program to run.

      1. Enter the name of the customer script (my_monitor.sh).

      2. Add the actual script program to the Agent Builder's project files.-Click "Add" and navigate to the \tmp directory.-Select "mymonitor.sh" and click "Open".-Click "OK".

    6. Determine if the agent should be monitored by Agent Management Watchdog Services - if yes, must provide the following info:

      1. frequency of checks

      2. number of restarts

      3. memory threshold information

    7. Determine any environment variables that must be set at agent runtime.

      1. Environment values can be defined for use within the script, and also can be selected from predefined values that cause the custom agent to behave in a specific way.

    8. Generate the agent.

      1. Select the "Generate Agent Wizard".

      2. A dialogue box will appear asking if the agent files should be created in an ITM installation on this machine (default).

      3. Must Select "create a compressed file so the agent can be installed on another system".

      4. Verify the output directory where the compressed files will be generated.

    9. Commit the agent.

      1. Once the agent has been successfully tested, it must be committed.

      2. There are a maximum of 12 versions that can be committed.

      3. Once committed, the Agent Builder insures that any future versions are downward compatible.

  2. Given a compressed custom agent file developed for a UNIX platform by using the Tivoli Monitoring Agent Builder, deploy the custom agent to the host named "aix_tdw" and verify it's operation, so that the custom agent is deployed and operational on the monitored host "aix_tdw".
    With emphasis on performing the following tasks:

    1. Copy the file K00.tgz to the target host(s).

      1. Using whatever mechanism is available. (ftp, scp, a CD containing the K00.tgz file, etc.)

    2. Extract the contents of the K00.tgz file to a temporary location.

      1. The directory /tmp/k00 must NOT be used as the install program will use that directory.

      2. Create a temporary directory in a file system with enough space to hold the contents of K00.tgz when uncompressed.-Assuming we have enough space in /tmp; copy K00.tgz to /tmp-Make a directory in /tmp called K00_inst (mkdir /tmp/K00_inst).-Cd to /tmp/K00_inst-Gunzip ../K00.tgz-Tar -xvf ../K00.tar

    3. Run the appropriate install script for each corresponding ITM host.

      1. installIraAgent/.sh - for the agent-only installation. (This would be run on aix_tdw.)

      2. installIraAgentTEMS.sh [[-h Hub_TEMS_] -u HUB_TEMS_ -p Hub_TEMS_] - installs the TEMS support. (This would be run on aix_tems.)

      3. installIraAgentTEPS.sh - installs the Tivoli Enterprise Portal Server (TEPS) and TEP support (This would be run on aix_teps.)

    4. Configure and Start the custom agent locally.

      1. On the AIX host named "aix_tdw", by using the command line interface (CLI) cd /bin and execute the following commands:-./Itmcmd config -A -h 00-./itmcmd agent start 00

    5. Verify the custom agent appears in the TEPS Navigator and is executing as expected.

      1. Below the name of the agent, there should be an attribute group labeled "Availability".

      2. Click on the "Availability" attribute group.-This will display a report in table format showing a timestamp for the last data returned by the agent.-One metric is labeled Functionality Test Status - this should show SUCCESS if things are working correctly.

    6. Create a situation to test for Functionality Test Status != to SUCCESS and trigger an alarm when true.

      1. Induce an error condition on the host aix_tdw and verify the situation fires.

  3. Given the need to build and manage an agent depot, describe how to add agent packages and their prerequisites to the depot and subsequent management of the depot.
    With emphasis on performing the following tasks:

    1. Ensure the required ITM images are available for the agents that will be added to the depot.

      1. If the image(s) is in a tar or zip format then it is required to be extracted.-UNIX/Linux - untar the image to a temporary location.-Windows - unzip the image to a temporary location.

      2. If the image is on DVD then it should be inserted into a DVD drive that is accessible to the server that installation will take place.

    2. Ensure the required prerequisites are in place to include.

      1. The TEMS and TEPS have been installed and configured as per the ITM Installation and Setup Guide.

      2. The userid that will be used to add the bundles has sufficient authority to run tacmd and access the agent images.

    3. Adding a bundle to the depot by using tacmd

      1. UNIX/Linux-In a command line cd to the itminstalldir/bin directory.-Log on to the TEMS, which is required before any bundles can be added.-Tacmd login -s tems_hostname -u sysadmin -p xxxxxx.-If required list the bundles available in the image.-Tacmd listbundles -i imagepath_platform Where imagepath_platform is the path to the directory containing the agent code in the extracted image such as image/unix.-Add a bundle to the depot.-Tacmd addBundles -i imagepath_platform -t xx -p yyyyyy -v zzz Where imagepath_platform is the path to the directory containing the agent code in the extracted image, xx is a product such as ud for the DB2 Database Agent, yyyyyy is the platform such as aix513 and zzzzzz is the version such as 062200000.-To view the contents of the depot, log in to the TEMS.-Tacmd login -s tems_hostname -u sysadmin -p xxxxxx-Tacmd viewdepot

      2. Windows-In a command line cd to the itminstalldir\bin directory.-Log on to the TEMS, which is required before any bundles can be added.-Tacmd login -s tems_hostname -u sysadmin -p xxxxxx.-If required list the bundles available in the image.-Tacmd listbundles -i imagepath_platform Where imagepath_platform is the path to the directory containing the agent code in the extracted image such as image\unix.-Add a bundle to the depot.-Tacmd addBundles -i imagepath_platform -t xx -p yyyyyy -v zzz Where imagepath_platform is the path to the directory containing the agent code in the extracted image, xx is a product such as ud for the DB2 Database Agent, yyyyyy is the platform such as aix513 and zzzzzz is the version such as 062200000.-To view the contents of the depot, log in to the TEMS.-Tacmd login -s tems_hostname -u sysadmin -p xxxxxx.-Tacmd viewdepot.

    4. A bundle would be removed from the depot when it is no longer required, if it is an old release of a product that is no longer supported or used. To remove the bundle by using tacmd follow the below steps.

      1. UNIX/Linux -In a command line cd to the itminstalldir/bin directory.-Log on to the TEMS, which is required before any bundles can be added.-Tacmd login -s tems_hostname -u sysadmin -p xxxxxx.-Remove a bundle from the depot.-Tacmd removeBundles -i depot_path -t xx -p yyyyyy -v zzz Where depot_path is the path to the depot such as /opt/IBM/ITM/tables/TEMS/Depot, xx is a product such as ud for the DB2 Database Agent, yyyyyy is the platform such as aix513 and zzzzzz is the version such as.

      2. Windows-In a command line cd to the itminstalldir\bin directory.-Log on to the TEMS, which is required before any bundles can be added.-Tacmd login -s tems_hostname -u sysadmin -p xxxxxx.-Remove a bundle from the depot.-removeBundles -i depot_path -t xx -p yyyyyy -v zzz Where depot_path is the path to the depot such as C:\IBM\ITM\CMS\Depot, xx is a product such as ud for the DB2 Database Agent, yyyyyy is the platform such as aix513 and zzzzzz is the version such as.

    5. Adding a bundle to the depot using the installation image.

      1. Windows-Cd to the Windows or WIA64(Itanium) directory of the extracted image.-Double click setup.exe.-Click next on Welcome window.-Click to Accept the license agreement and click next.-Choose the directory to install the agent, or accept the default and click next (if there is already an ITM installation this option will not appear).-Provide your own encryption key or accept the default, click next and then OK to accept the key (if there is already an ITM installation, this option will not appear).-On Select Features (Tivoli Enterprise Monitoring Agent TEMA) click next.-On Agent deployment select those agents to add to the depot, this will only include agents that can be installed on Windows. Click Next.-Click next (and then yes if ITM is already installed) to start copying files, this will take a few minutes.-In the setup type configuration window ensure both tick boxes are ticked, click next.-In configuration defaults for connection to a TEMS click OK.-Click Finish.-To view the contents of the depot, log in to the TEMS.-Tacmd login -s tems_hostname -u sysadmin -p xxxxxx.-Tacmd viewdepot

  4. Given knowledge of ITM, a documented ITM architecture, appropriate access to the ITM infrastructure, and a basic understanding of network protocols, configure protocol and connectivity for the TEMA's, so that agents properly communicate with management servers.
    With emphasis on performing the following tasks:

    1. Determine standardized protocol to be used throughout the ITM environment.

      1. The TEMA's must use one of the protocols configured at the management server.

      2. Considerations for network protocols:-IP.PIPE: The most reliable and usually the fastest protocol is IP.PIPE. The drawback with IP.PIPE are the additional system resources required to maintain the separate socket that each connected client requires.-Only 16 ITM processes on a single system can share the base listening port (default port 1918) on a single network interface when using the IP.PIPE protocol.-IP.UDP: Unreliable protocols such as IP.UDP are more likely to result in broken connections and the need for the client to retransmit data. For this reason, it is recommended IP.UDP is chosen as the communication protocol between agents and management server only if you have a reliable network and the resources required to support IP.PIPE are not available.-The IP.UDP protocol is a typically a poor choice for firewall configurations. The connectionless UDP protocol requires opening up multiple ports across firewalls-IP.SPIPE: The IP.SPIPE protocol behaves similarly to IP.PIPE, but uses Secure Socket Layer (SSL) encryption. This will have an associated impact on the speed of data transfer, and you should decide whether or not this is an important factor within your environment when choosing a communication protocol.-SNA: SNA is rarely used but still supported as a valid ITM protocol. To properly use and configure SNA support within ITM, the user will require the Net Name, LU Name, TP Name, Local LU Alias, and Log Mode.

      3. Use SKIP and COUNT as necessary to manage listening ports.-The COUNT:N parameter can be defined on the KDC_FAMILIES environment variable of TEMA. It is the mechanism for reserving IP.PIPE and IP.SPIPE listening ports. COUNT:N accommodates multiple monitored servers on a single host.-The SKIP parameter can be used with IP.PIPE and IP.SPIPE if other ITM components, such as the Universal Agent, portal server, and other components, are running on the same system. SKIP will instruct these components to skip some reserved ports.

      4. Consult with local network administrator to confirm ITM traffic can traverse the enterprise network where needed (firewalls, routing, etc).

    2. Determine if Optional Primary Network Name parameter will be required.

      1. When more than one Network Interface Card (NIC) exists in the computer on which the monitoring server is installed, you need to identify which NIC to use when specifying the monitoring server name and host name. Additionally, the host name of the system might not match the interface name, even when only one NIC exists. In either of these cases, to establish connectivity between the monitoring server and agents, you must specify an additional variable when configuring the monitoring server or agents. This variable is listed under the Optional Primary Network Name option in the configuration windows or during the installation.

      2. Find number of defined network interfaces:-Windows: from a command prompt, type ipconfig /all.-UNIX/Linux: from a shell prompt, type ifconfig -a.

    3. Determine where the ITM component being configured is located in relation to the architecture so connectivity to the appropriate TEMS can be identified.

      1. Using the ITM architecture design, note the hostname of the primary TEMS the TEMA should communicate with.

      2. If the architecture designates a secondary TEMS, note that server's hostname as well.

    4. Configure protocol and connectivity for the TEMA.

      1. Initial configuration of a TEMA is typically done at the time of installation. However, reconfiguration of an existing agent is very similar to what one sees at the time of installation.

      2. UNIX/Linux:-Configuration can be done after installation by using: ./itmcmd config -A pc where pc is the product code for your agent.-Press Enter when you are asked if the agent connects to a monitoring server (TEMS).-Type the host name for the monitoring server. -Type the protocol that you want to use to communicate with the monitoring server.-If you want to set up a backup protocol, enter that protocol and press Enter. If you do not want to use backup protocol, press Enter without specifying a protocol. -Depending on the type of protocol you specified, provide the appropriate information protocol, hostname and address information.-Specify the name of the secondary monitoring server if applicable, else press Enter.-Specify the Optional Primary Network Name if applicable. Else press Enter.

      3. Windows-Configuration can be done after installation by using the Manage Tivoli Enterprise Monitoring Services (MTEMS) GUI.-On the computer where the TEMA is installed, select Start -> Programs -> Tivoli Monitoring Services -> Manage Tivoli Enterprise Monitoring Services.-In the MTEMS window, select the agent whose connection you want to configure. You can select multiple agents by holding down the Shift key or Control key and selecting agents.-Click Actions -> Reconfigure.-Identify the communications protocol for communication with the monitoring server. You have four choices: IP.UDP, IP.PIPE, IP.SPIPE, or SNA. -Click OK.-Complete the fields with information applicable to the ITM environment and click OK.-If the agent was running when you began the configuration process, after the reconfiguration is complete, you are asked if you want the agent restarted. Reply with YES for the changes to be made active.

  5. Given a properly installed basic ITM environment and the ITM installation media, enhance the existing ITM installation so that certain degree of high availability for ITM servers can be achieved without using cluster technology.
    With emphasis on performing the following tasks:

    1. Install and configure Hot Standby Hub Tivoli Enterprise Monitoring Server .

      1. Install a second Hub Tivoli Enterprise Monitoring Server by following the standard TEMS installation procedures.

      2. Define one Hub Tivoli Enterprise Monitoring Server as the primary Hub Tivoli Enterprise Monitoring Server and the other Hub Tivoli Enterprise Monitoring Server as the secondary TEMS.

      3. Configure the primary Hub Tivoli Enterprise Monitoring Server to take the secondary TEMS as the Hot Standby Hub Tivoli Enterprise Monitoring Server.

      4. Configure the secondary Hub Tivoli Enterprise Monitoring Server to take the primary TEMS as the Hot Standby Hub Tivoli Enterprise Monitoring Server.

    2. Configure all remote TEMS to specify the primary Hub Tivoli Enterprise Monitoring Server and the secondary Hub Tivoli Enterprise Monitoring Server.

    3. Configure all monitoring agents that are connected directly to the Hub Tivoli Enterprise Monitoring Server by specifying the primary Hub Tivoli Enterprise Monitoring Server and the secondary TEMS.

    4. Configure the Warehouse Proxy Agent and the Summarization and Pruning Agent to connect to the primary Hub Tivoli Enterprise Monitoring Server and the secondary TEMS.

    5. After the active Hub Tivoli Enterprise Monitoring Server went down and the standby Hub Tivoli Enterprise Monitoring Server becomes the active TEMS, reconfigure the TEPS to connect to the new active Hub Tivoli Enterprise Monitoring Server.

    6. Certain degree of high availability for TEPS can be achieved by the following without using cluster technology.

      1. Install a second TEPS as a backup TEPS.

      2. Users are only allowed to update ITM objects on the primary TEPS.

      3. Develop some procedures to synchronize the primary and the backup TEPS databases.

      4. When the primary TEPS goes down, direct users to log in the backup TEPS.

  6. Given the need for ITM Agents to be highly available, describe how to configure ITM Agents to connect to a primary and backup monitoring server.
    With emphasis on performing the following tasks:

    1. On the Manage Tivoli Monitoring Services window, right-click a monitoring agent, and click either Reconfigure (on Windows systems) or Configure (on UNIX systems).

    2. Select Optional: Secondary TEMS Connection, and specify the protocol for the standby monitoring server.

    3. On UNIX Agents, click Protocols to display a separate window where you can configure the standby server (Secondary Hub).

    4. Click OK.

    5. Enter the host name or IP address of the primary Hub Tivoli Enterprise Monitoring Server or remote Tivoli Enterprise Monitoring Server (RTEMS) and the port number, and click OK.

    6. Enter the host name or IP address of the secondary Hub/backup RTEMS, and click OK.

    7. Restart the monitoring agent.

  7. Given a working ITM environment, installed and configured Warehouse Proxy Agent and Summarization and Pruning Agent and Application Support has been performed for the selected agents, configure Tivoli Data Warehouse so that the historical data can be collected and pruned correctly and the data can be viewed at ITM enterprise portal.
    With emphasis on performing the following tasks:

    1. Configure data collection.

      1. Start History Configuration tool from ITM Enterprise Portal.

      2. Create a new collection setting - Enter name, select Monitored Applications and Attribute Group.

      3. From the Basic tab, select Collection Interval, Collection Location and Warehouse Interval.

      4. From the Distribution tab, select the target system.

    2. Configure data summarization and pruning.

      1. Start History Configuration tool from ITM Enterprise Portal.

      2. Select a monitored application, say Windows OS -> select an Attribute Group.

      3. Select Summarization interval.

      4. Select Pruning interval.

  8. Given a working ITM environment, configure the Event Integration Facility (EIF) to enable events to be forward to one or more event receivers.
    With emphasis on performing the following tasks:

    1. Configure Hub Tivoli Enterprise Monitoring Server.

      1. Start MTEMS to configure Tivoli EIF settings for the Hub Tivoli Enterprise Monitoring Server.

      2. Enter hostnames or IP addresses and port numbers of target event management servers.

      3. Create, list, view and delete Event Destinations by using the tacmd command.

    2. Configure ITM Situations to used EIF Forwarding.

      1. Start the Situation Editor and configure the settings for EIF Forwarding.

      2. Assign the relevant EIF Receivers.

      3. Map the ITM Situation event severity to the severity of the event to be forwarded to the event management system.


Section 4: Problem Determination


  1. Given a failing installation of Tivoli Enterprise Monitoring Server(TEMS) and the problem determination guide, troubleshoot the issue, so that basic analysis has been performed to identify the issue.
    With emphasis on performing the following tasks:

    1. Review the installation guide to make sure all prerequisites have been met.

    2. Examine First Failure Data Capture log directory.

    3. Examine installation logs.

      1. Windows: \InstallITM\IBM Tivoli Monitoring date PID.log

      2. UNIX/Linux: /logs/candle_installation.log

    4. Some specific items to check prior to contacting support:

      1. Ensure file permissions are met.

      2. Windows 2008 Only : Disable Windows Firewall and Configure User Account Control.

      3. Windows Only : Reboot system if prompted due to locked files.

      4. SLES9 Only : "Resolve KCI1008E terminating... license declined" error through ensuring correct OS patches installed / correct JRE.

      5. UNIX Only : "Encryption key setting" ensure that encryption key is exactly 32 characters.

  2. Given a Tivoli Enterprise Portal(TEP) client is unable to log on to the Tivoli Enterprise Portal Server (TEPS), perform some basic problem determination steps, so that basic analysis has been performed to identify the issue.
    With emphasis on performing the following tasks:

    1. Confirm problem code, as displayed on TEP Logon screen.

      1. For KFWITM001W & KFWITM215E errors, examine kfw1ras.log for possible further error codes.-For both SQL1224N & SQL1226N, restart the TEPS Database and attempt to log on again.

    2. Confirm connectivity between TEP Client host and TEPS host by using ping, or other network tool.

    3. On TEPS host, launch Manage Tivoli Enterprise Monitoring Services (MTEMS), and confirm that TEPS is started.

      1. Confirm presence of "event ID 1: KFW0001 - TEPS startup complete" in Windows Event Log.

    4. For Browser TEP Client, if using hostname in the URL, change to the IP address of the TEPS in case of name resolution issues.

    5. Increase TEPS trace to examine connection problems in further detail. Suggested trace : KBB_RAS1=ERROR (UNIT:ctsql IN ER) (UNIT:ctdata IN ER) (UNIT:ctauth ALL)

      1. Windows : Edit \CNPS\KFWENV.

      2. UNIX/Linux : /config/cq.ini

    6. Examine TEP Client traces for signs of problems.

      1. TEP Java Web Start client : C:\Documents and Settings\Administrator\Application Data\\Java\Deployment\log

      2. TEP Browser client : C:\Documents and Settings\Administrator\Application Data\\Java\Deployment\log

      3. TEP Desktop client : \CNP\logs\kcjerror.log & \CNP\logs\kcjras1.log

  3. Given a Windows IBM Tivoli Monitoring V6.2.2 (ITM) user is unable to access the TEP with the browser client, describe how a user can determine if it is a Java Runtime Environment (JRE) problem and isolate its cause, so that a user can access the TEP.
    With emphasis on performing the following tasks:

    1. JRE Background information:

      1. The browser client provides access to the TEP with either Internet Explorer or Firefox.

      2. The TEP applet software requires that the browser have a JRE) loaded. There are 3 versions of the JRE that supported. -IBM JRE 1.5.0 (also know as Java 2 version 5 )-Sun JRE 1.5.0_nn (also know as JRE Version 5 with update nn)-Sun JRE 1.6.0_nn (also know s JRE Version 6 with update nn)

      3. Each JRE includes both a JRE and a Java plug-in. The Java plug-in also has a version and it is the same as the JRE.

      4. The Java plug-in is installed into the browser (Internet Explorer, or Firefox) as a "plug-in". When the plug-in is called, it will load the JRE.

      5. IBM JRE Installation: -If IBM JRE will be used and it is not installed on the client PC, then the installation of IBM JRE will occur the first time the client logs on the TEP by using the browser client. -If this installation fails due to authority reasons, the client may be required to log on by using a User ID with more administrator rights. Use that User ID to get through the first time to log in. Once installed, the user may use their normal User ID.

      6. Sun JRE Installation: If Sun JRE will be used and it is not installed on the client PC, the client must install it prior to attempting to log on to the TEP.

      7. It is possible to have one, two, or all three of the supported JRE's installed on the client PC. It is also possible to have unsupported JRE's installed on the client PC.

      8. One of the installed JRE's is referred to as the "System JRE" or default JRE. Usually the last JRE installed will become the default JRE.

      9. If the browser loads the SUN Java Plug-in, it is possible to control which JRE it will loaded using the Sun Java Control Panel. This control panel has JRE Settings. Here you can disable any versions you do not want to be loaded.

      10. If there are unsupported versions of the IBM JRE, they should be uninstalled.

      11. During troubleshooting, turn on the Java Console. Both the Sun and IBM Java Control Panels have an advanced tab with a console section, expand it and select the show console option.

    2. Verify if Java problem.

      1. Verify the user is using documented URL: http://hostname:1920///cnp/client

      2. Verify the user can use http://hostname:1920 , if they can not successfully from up this web page, it is not a JRE problem. This step will verify the TEPS is up and a network connection can be made.

      3. Verify if the user is able to enter in their User ID during the logon. If yes, then is likely not a JRE problem.

    3. Firefox problem-solving:

      1. When Firefox is used it will pick the system/default JRE.

      2. Verify that the system JRE is a supported JRE. -A quick way that works most of the time is to issue command Java -version.-Another more accurate method is to go one of many Java tester web sites that will display your JRE version. One example is http://www.Java tester.org/version.html -If the system JRE is not one of the three supported versions then:-install the needed version.-If the desired version is already installed but not the default, then uninstall and reinstall, this will make it the default.

    4. Internet Explorer problem-solving:

      1. Internet Explorer uses a file located on the TEPS called jrelevel.js to determine which version of the JRE should be loaded.-Windows: \itm_install_dir\CNB \jrelevel.js-UNIX and Linux: itm_install_dir/arch/cw/jrelevel.js

      2. This file contains one statement to indicate the JRE. There are 4 options. -jrelevel="1.5.0': Indicates all Internet Explorer Users will use IBM Java JRE 1.5.0-jrelevel='5.0': Indicates all Internet Explorer Users will use Sun Java 1.5.0_nn-jrelevel='6.0': Indicates all Internet Explorer Users will use Sun Java 1.6.0_nn-jrelevel='*': Indicates all Internet Explorer Users their Default JRE

      3. Verify the version from the jrelevel.js file is installed on the client PC.-On Windows: One way to verify is to use Windows Control Panel, Add or Remove Programs. Each installed JRE will have an entry.

      4. If the jrelevel="*', verify that the default version is one of the three supported versions. Determine the default version by: -Issue command Java -version. -A more accurate method is to go to a web site that will display your Java version such as http://www.Java tester.org/version.html.

      5. Verify the plug-in is enabled. Both Internet Explorer and Firefox have a "Manage add-ons" in their Tools. Select this option to view the plug-ins, look for the Java plug-in and check that it shows enabled.

      6. If using a Sun Java, Internet Explorer will use the most recently install version of a Sun plug-in to load the requested version of the JRE. This means if both Sun JRE V1.5 was installed, then Sun JRE V1.6 installed after, then the V1.6 Plug-in will be used to load either the JRE V1.5 or JRE V1.6.

      7. The first line written to the Java console is the version of the Plug-in; the second line written is the version of the JRE. Verify that the version of the JRE is the one specified in the jrelevel, or if ‘*' was specified, that it is one of the 3 supported versions.

      8. If the Java Plug-in is Sun V1.6.0, and are able to reach the logon panel, then get an error loading the first workspace in the TEP. You may be required to change the legacy_lifecycle value. If the Sun Plug-in version is 1.6.0 the legacy_lifecycle may be required to be set to true, for sun Plug-in V1.5.0 use a legacy_lifecycle of false.

  4. Given a TEPS, a TEMS believed to be in a working state, troubleshoot a workspace that is not displaying any data, so that the issue has been identified.
    With emphasis on performing the following tasks:

    1. Confirm the Agent which the query distributed is online.

    2. Confirm if any workspaces from the same agent are displaying data.

    3. Confirm if the same workspace from other agent is displaying data.

    4. Confirm that the Application Support has been installed at the TEMS.

    5. Examine TEP Client trace for signs of failure.

      1. TEP Java Web Start client: %USERPROFILE%\Application Data\IBM\Java\Deployment\log\javawsnnnnn.trace where 'nnnnn' is a unique, randomly generated numeric suffix

      2. TEP Browser client (IBM JRE) :%USERPROFILE%\Application Data\IBM\Java\Deployment\log\plugin150_xx.trace (Note: This may be a windows hidden file)

      3. TEP Browser client (SUN JRE) : %USERPROFILE%\Application Data\SUN\Java\Deployment\log\pluginxxxx.trace (Note: This may be a Windows hidden file) where xxxx is the JRE version.

      4. TEP Desktop client : \CNP\logs\kcjerror.log & \CNP\logs\kcjras1.log

    6. Increase TEPS trace (KBB_RAS1=ERROR (unit: ctsql ALL).

      1. Windows : Edit \CNPS\KFWENV

      2. UNIX/Linux : /config/cq.ini

  5. Given a managed system is offline and access to the TEP's Managed System Status workspace, describe how to isolate the failing component causing the managed system to be offline so that the problem will be isolated to either the agent, agent's server, the remote Tivoli Enterprise Monitoring Server (RTEMS), agent configuration, or Network.
    With emphasis on performing the following tasks:

    1. Verify the managed system is offline and if there is a reason code.

      1. In the TEP, go to physical view, right click on "Enterprise" navigational item and select workspace, then select "Managed System Status.

      2. Locate the managed system and verify that it has a status of Offline.

      3. Identify the reason code. If "FA", this indicates that the managed system is offline because it RTEMS is offline and the problem is likely with the RTEMS. The failing RTEMS is identified by the managed systems "Managing System" attributes.

      4. If the managed system does not appear in the Managed System Status view, then the agent likely has never connected. The failing component is the agent installation/configuration or network.

    2. Verify the server running the agent is operational.

      1. First identify the server by using the Managed System Status workspace. The Offline managed system's name and its "Host Address" attribute should provide information about the host name and/or IP address of the server running the agent.

      2. Use this information to find the server and determine the server's status. If it is not running, then the server is the failing component.

    3. Verify the agent's process is running.

      1. For agent on Windows:-Start "Manage Tivoli Monitoring Services".-Within the list of ITM components locate offline agent and check it has a status of Started.

      2. For agent on UNIX / Linux:-If the OS agent run ps -ef|grep kuxagent.-If non-OS agent run ps -ef | grep -i ‘/ibm/itm' (insert your correct install directory for /IBM/ITM).

      3. For an OS agent on Linux:-Run ps -ef | grep klzagent.-If non-OS agent run ps -ef | grep -i ‘/ibm/itm' (insert your correct install directory for /IBM/ITM).

      4. If the agent is not running then the failing component is the agent or the agent startup procedure/automation.

    4. Verify the TEMS is online.

      1. Locate the RTEMS by using the Managed System Status workspace, the offline managed system's attribute called "Managing System" identifies the TEMS to which the agent was last connected.

      2. If the managing system is the Hub Tivoli Enterprise Monitoring Server, the there is not a RTEMS problem.

      3. If the managing system is a RTEMS, check if the RTEMS is online. If the RTEMS is offline then the failing component is the RTEMS.

    5. Verify if there are other managed systems running on the same server and also offline.

      1. Use the Managed System Status Workspace, sort by "Host Address", and locate the offline managed system. Check if other managed systems have the same value for the "Host Address" attribute.

      2. If other agents with the same "Host Address" value are offline, then the failing component is likely in the network between the agent and the RTEMS.

      3. If other agents are online, then agent is the likely failing component.

    6. Verify that other managed systems are connected to the same RTEMS are online and operational.

      1. Use the Managed System Status workspace. Sort by "Managing System".

      2. Locate the RTEMS in the Managing System column. From this display determine if there are a higher then normal number of managed systems offline which are connected to the same RTEMS. If there are, then the problem is likely in the RTEMS.

  6. Given working knowledge of the ITM components (TEMS, TEPS, Tivoli Data Warehouse, and agents), perform the necessary steps to debug one of the components failing to start so that the issue has been analyzed and a resolution has been determined.
    With emphasis on performing the following tasks:

    1. Examine all relevant log files to try and determine the reason for the component not starting.

      1. The key components (TEMS,TEPS,Tivoli Data Warehouse) each have an associated product code that is part of the logfile name. All logfiles reside in the directory $CANDLEHOME/logs (/opt/IBM/ITM/logs is default).-For TEMS, the logfile name is: hostname_ms_timestamp.log-For TEPS, the logfile name is: hostname_cq_timestamp.log-For Tivoli Data Warehouse, the logfile name is: hostname_hd_timestamp.log and hostname_hd_java_timestamp.log

    2. If examination of the logs is inconclusive, enable tracing on the problem component and try to restart.

      1. Traces can be enabled by modifying the component's .ini file in $CANDLEHOME/config.-The variable in the .ini file that determines the trace level is called KBB_RAS1.-The syntax for enabling tracing is KBB_RAS1=ERROR (UNIT:filter trace_level).-Other variables for tracing that are common to ITM components are:-KDC_DEBUG Y or N Default is N. Diagnosing communications or connectivity problems between the TEPS to the TEMS. -KDH_DEBUG Y or N Default is N. Diagnosing connectivity problem with integrated web server. -KDH_SERVICEPOINT Determining the service point.-KBB_RAS1 Trace specification string See each specific environment variable section below. -KBB_RAS1LOG Determining the count limit and the max files settings. -TACMD_JVM_MAX_MEMORY 256 through to 2048 Increase the Java JVM memory size.

    3. Examine all relevant configuration files. Configuration files reside in $CANDLEHOME/config (/opt/IBM/ITM/config is default).

      1. Each ITM component has one or more associated configuration file(s) and there are several "global" configuration files.

      2. A corrupt or missing env.config can cause problems with components not starting.

    4. Verify network communications using ‘netstat -An | grep 1918' .

      1. ITM uses TCP/IP communications on specific ports (1918-1920, and 3660-3661 for Secure Socket Layer). If another process is using a port that an ITM component is required, that component will not be able to start.-These types of errors can usually be found in the component's log file.-An improper shutdown of ITM might leave an orphaned ITM process holding a port which could prevent a restart from succeeding.-Ensure there are no firewalls blocking access to these ports.

    5. Reference the information on the web or in IBM Redbooks for additional help.

      1. http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp

      2. Problem Determination Guide - GC32-9458-01

  7. Given an installed and functional ITM infrastructure and absence of desired historical data, troubleshoot Data Warehouse installation and configuration so that the historical data can be viewed in ITM Enterprise Portal.
    With emphasis on performing the following tasks:

    1. Verify Data Warehouse installation.

      1. Use appropriate mean to verify the required warehouse database is installed.

      2. Using appropriate database command or GUI tool to verify that database is running.

      3. Verify the Warehouse Proxy Agent is properly installed.-UNIX/Linux/Windows: Examine the existence of Warehouse Proxy Agent in the "Manage Tivoli Enterprise Monitoring Service" tool.-UNIX/Linux: Using command cinfo -i and examine the output.

      4. Verify if the Warehouse Proxy machine can communicate with Hub Tivoli Enterprise Monitoring Server, TEPS and the Warehouse database server.

    2. Verify Proxy Agent configuration.

      1. Windows - Using "Manage Tivoli Enterprise Monitoring Service" tool.-Start the "Manage Tivoli Enterprise Monitoring Service" tool by clicking the icon on the Windows desktop.-Select Warehouse Proxy -> Reconfigure.-Configure Primary TEMS Connection - Must be the Hub Tivoli Enterprise Monitoring Server. Verify the Protocol, Hub Tivoli Enterprise Monitoring Server hostname and port number is correct. -Configure ITM Warehouse ODBC data source - Verify the database type, data source and database information, as well as the user login information are correct.-Start the Warehouse Proxy Agent.

      2. UNIX/Linux - Using "Manage Tivoli Enterprise Monitoring Service" tool.-Using command: itmcmd manage to start the "Manage Tivoli Enterprise Monitoring Service" tool (requires a GUI).-Select Warehouse Proxy -> Configure.-Select the "TEMS Connection tab". Verify the Primary TEMS Connection. The TEMS must be the Hub Tivoli Enterprise Monitoring Server. Verify the Protocol, Hub Tivoli Enterprise Monitoring Server hostname and port number.-Select the "Agent Parameter" tab to verify the Warehouse database connection information - Verify the JDBC Drivers, Database Type, Warehouse Driver and Warehouse User information are all correct.-Ensure the database is running, and select "Test database connection".-Start the Warehouse Proxy Agent.

      3. UNIX/Linux - Use itmcmd config command to verify Warehouse Proxy Agent configuration.

    3. Examine trace log if Warehouse Proxy Agent does not start.

      1. Windows - Using "Manage Tivoli Enterprise Monitoring Service" tool-Start the "Manage Tivoli Enterprise Monitoring Service" tool by clicking the icon on the Windows desktop.-Right click Warehouse Proxy -> Advanced -> View Trace Log.

      2. UNIX/Linux - Review the log files related to agent "hd" $CANDLEHOME/logs.

    4. Verify the installation of related ITM component.

      1. Verify the related ITM agent is installed.-Windows/UNIX/Linux - Use "Manage Tivoli Enterprise Monitoring Service" tool.-UNIX/Linux only - Use command "cinfo -r"

      2. Verify the related agent support files appropriately installed.-Windows: using kincinfo -d-UNIX/Linux: using cinfo -i

    5. Verify History Collection Configuration.

      1. Start History Configuration tool from ITM Enterprise Portal.

      2. Verify data collection has been created for that Monitored Application.

      3. Select a data collection object.-From the Basic tab: verify the collection interval, collection location are defined.-From the Distribution tab: Verify the distribution target is set correctly.

      4. Select the Monitored Application. Verify the data collection tasks are in running status.

    6. Verify historical data Time Span for Query configuration.

      1. Push the "Specify Time Span for Query" button on the workspace that historical data is missing.

      2. Exam the Time Span configuration.

  8. Given an installed and working database, an installed Summarization and Pruning Agent, troubleshoot the failure to create the summarization tables within the Warehouse, so that the issue has been identified and can be corrected.
    With emphasis on performing the following tasks:

    1. At the time configured for the SPA to start, confirm the availability of the TEPS.

    2. For the summarization table(s) that are missing, confirm the presence of the relevant Agent's ODI files on the TEPS under the following directories:

      1. Windows: %CANDLE_HOME%\CNPS

      2. UNIX / Linux: $CANDLEHOME//cq/data

    3. Increase Summarization and Pruning agent trace, and examine trace for further signs of failure: KBB_RAS1=ERROR (UNIT:ksy1 ALL).

      1. Windows: %CANDLE_HOME%\tmaitm6\KSYENV

      2. UNIX/Linux: $CANDLEHOME/config/sy.ini

  9. Given the need to collect diagnostic information generated from traces and knowing specific trace parameters to be set, describe how to set tracing and manage the generated log files, so that problem determination can be performed while controlling log file size and retention.
    With emphasis on performing the following tasks:

    1. Setting traces for the TEMS

      1. UNIX / Linux - /config/ms.ini-Modify the line starting with KBB_RAS1=.

      2. Windows - Tracing for the TEMS running on the Windows platform can be set through the GUI.-On the computer where the TEMSis installed, select Start -> Programs -> Tivoli Monitoring Services -> Manage Tivoli Enterprise Monitoring Services.-Right-click the TEMS service.-Select Advanced -> Edit Trace Parms to display the Trace Parameters window.

      3. The TEMS must be restarted for traces to take effect.

    2. Setting traces for the TEPS

      1. UNIX/Linux - /config/cq.ini-Modify the line starting with KBB_RAS1=.

      2. Windows - Tracing for the TEPS running on the Windows platform can be set through the GUI.-On the computer where the TEPS is installed, select Start -> Programs -> Tivoli Monitoring Services -> Manage Tivoli Enterprise Monitoring Services.-Right-click the TEPS service.-Select Advanced -> Edit Trace Parms to display the Trace Parameters window.

      3. The TEPS must be restarted for traces to take effect.

    3. Setting traces for Tivoli Enterprise Monitoring Agent (TEMA)'s:

      1. UNIX/Linux - /config/.ini where pc = TEMA product code-Modify the line starting with KBB_RAS1=.

      2. Windows - Tracing for TEMA's running on the Windows platform can be set through the GUI.-On the computer where the TEMA is installed, select Start -> Programs -> Tivoli Monitoring Services -> Manage Tivoli Enterprise Monitoring Services.-Right-click the TEMA service.-Select Advanced -> Edit Trace Parms to display the Trace Parameters window.

      3. The TEMA must be restarted for trace setting to take effect.

    4. Dynamic tracing by using the ITM Service Console

      1. The Service Console is accessed by using a web browser. Access the utility by using the following link:-http://hostname:1920 where hostname is the hostname or IP address of the system where the ITM component is running.

      2. Select the link below the component for which you want to modify the trace settings.

      3. Enter a user ID and password to access the system. This is any valid user that has access to the system.

      4. Use the ras1 command for modifying the trace settings.

      5. An example would be ras1 set (UNIT:xxx ALL) (UNIT:yyy Detail). This command will enable full tracing for the xxx class of the component and low-level detailed tracing on the yyy class of the component.

      6. Turn dynamic tracing back off:-The option for turning the tracing off is to set the trace level to "ANY" for any trace that has been set by using the ITM Service Console.-For example you would use the following command to turn off tracing for the kbbcrcd class of the Windows OS agent:-ras1 set (UNIT:kbbcrcd ANY)

    5. Log file management as necessary

      1. UNIX/Linux-Specify log file management options in the install_dir/config/.ini file where pc = ITM product code.-Edit the line that begins with KBB_RAS1_LOG= to manage the generation of log files:-MAXFILES: the total number of files that are to be kept for all startups of a given program. Once this value is exceeded, the oldest log files are discarded. Default value is 9.-LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Default value is 5.-COUNT: the number of log files to keep in the rolling cycle of one program startup. Default value is 3.-PRESERVE: the number of files that are not to be reused in the rolling cycle of one program startup. Default value is 1.

      2. Windows-Open the MTEMS window.-Right-click the icon of the monitoring agent whose logging you want to modify.-Select Advanced -> Edit Trace Parms. The TEMS Trace Parameters window is displayed.-Modify the value for "Maximum Log Size Per File (MB)" to change the log file size (changes LIMIT value).-Modify the value for "Maximum Number of Log Files Per Session" to change the number of logs files per startup of a program (changes COUNT value).-Modify the value for "Maximum Number of Log Files Total" to change the number of logs files for all startups of a program (changes MAXFILES value).

  10. Given a working ITM environment describe the functions of Agent Management Services (AMS), so that it can be used to monitor and manage agents.
    With emphasis on performing the following tasks:

    1. The OS agent for Windows, UNIX, or Linux includes a feature called AMS. The main feature of AMS is the "Watchdog". AMS will watch any agent, if the agent terminates the agent will be restarted.

    2. If an agent is being watched, it is said to have a status of "Managed", if it is not being watched it has a status of "unmanaged".

    3. AMS components include:

      1. An "Agent Watchdog" running inside the OS agent -Runs inside the OS agent.-Can monitor non-OS agents running on the same server, if they have terminated they will be restarted. -AMS allows non-OS agents to be either managed or unmanaged. -AMS provides commands to turn on and off the management of an agent. -It will not restart agents that were manually stopped.-By default, non-OS agents are not managed.

      2. An "Agent Management Services Watchdog" running as a separate process:-Runs as a separate process.-Monitors only the OS agent on the same server, if the OS agent terminates it is restarted. -AMS provides commands to turn this off and on. -It will not restart the OS agent if it is manually stopped. -By default, the OS agent is managed.

      3. Commands to control the Agent Management Services Watchdog. This Watchdog only watches the OS agent. These commands are system commands and executed on the server. -Windows:-\tmaitm6\disarmWatchDog.bat-\tmaitm6\rearmWatchDog.bat-Linux-/bin/itmcmd execute lz disarmWatchdog.sh-/bin/itmcmd execute lz rearmWatchdog.sh-UNIX-/bin/itmcmd execute ux disarmWatchdog.sh-/bin/itmcmd execute ux rearmWatchdog.sh

      4. Commands to control the Agent Watchdog. This is the watchdog running inside the OS agent and monitors non-OS agents. These commands are executed by using the ITM Take Action facility. They can be run with a TEP "Take Action", by using the tacmd executation command, or as the action of a situation. Product provided take action commands will appear when the Application Support of the OS agent is installed. The Commands are: -AMS Start Management - Start managing any agent. -AMS Stop Management - Stop managing any agent.-AMS Start Agent instance - Start a non-OS agent.-AMS Stop Agent instance - Stop a non-OS agent.-AMS Recycle Agent instance - Cycle a non-OS agent-AMS Reset Agent Daily Restart Count - Reset the daily restart count to zero.-Security Caution: Any TEP user whose user ID has access to the OS agent and his/her user ID has view access for the "Action" permission, will be able to execute these commands.

      5. AMS has its own attribute groups, navigational items, workspaces, queries, and situations. These allow a TEP user to easily see the status of agents, their version, fix level, install directory, etc.-AMS attribute groups included within the OS agent are: -Agent Active Runtime Status-Agent Availability Management Status-Alerts Table-Configuration Information-Navigational items-Physical view for an OS agent now contains an AMS navigational item.-Additional items can be customized.-Workspaces. Within the Physical view, two workspaces are provided:-Agents Management Log-AMS-Situations: One situation called AMS Alert Critical monitors the Alerts Table attribute group. -Queries: One query is provided for each AMS attribute group.


Section 5: Administration


  1. Given that the IBM Tivoli Monitoring V6.2.2 (ITM) Infrastructure is installed and configured and ITM administrator User ID has been created, use the Tivoli Enterprise Portal Server (TEPS) user interface to validate the security authentication configuration and ITM user account entries, so that each User can access the portal and is assigned the appropriate rights and roles.
    With emphasis on performing the following tasks:

    1. Validating Users:

      1. Log on to the TEPS with a valid administrator ID.

      2. Open the Administer User Accounts Dialog.

      3. Select a user and validate (verify and update) the following:-Permissions - Validate each permission setting.-Applications - Validate the applications accessible by the user. -Navigator Views - Validate the Navigator views assigned to the user.-Member of - Validate the groups to which the user is a member.

      4. Select a User Group(s) and validate (verify and update) the following:-Permissions - Validate each permission setting. -Applications - Validate the applications accessible by the group.-Navigator Views - Validate the Navigator views assigned to the group.-Member of - Validate the groups to which the group is a member.-Members - Validate the Users and Groups assigned to the selected Group.

    2. Validating the TEPS LDAP authentication:

      1. Perform only if using LDAP for ITM user authentication.-Verify that the TEPS LDAP server is running -> log in to http://tepsserver.company.com:15205/ibm/console-Verify or Add the LDAP Repository: Reference materials for the TEPS LDAP configuration by using Active Directory can be found at: http://www-01.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10TM7R

  2. Given a working ITM environment and the authority to create situations describe how a user can create a simple situation and how a situation can impact the overhead of the agent and/or Tivoli Enterprise Monitoring Server (TEMS), so that an ITM implementer can create a situation and identify opportunities to reduce the overhead of existing situations.
    With emphasis on performing the following tasks:

    1. Creating a situation by using the Tivoli Enterprise Portal (TEP) Situation Editor. This is a situation for the Windows OS agent. It will check if there are any Windows Services that are not running that have a Start Type of Automatic. If there are, then it will issue a command to start the service.

      1. Once logged on the TEP with authority to Edit, Modify, and Start/Stop situations.

      2. Open the Situation Editor.

      3. Right-click on Windows OS in the left panel. Select "Create new Situation".

      4. Fill out the dialog window, for this example put:-Name = Windows_Restart_Service-Description= This Situation will restart any service that is not running and has a start type of Automatic-Monitored Application = Windows OS-Type - Standard Situation-Click OK.

      5. The "Select Condition" dialog box appears next.-First select the attribute group. Note: You are required to know which attribute group in which your situations attributes reside. This can often be guessed from the attribute group names. -Select Attribute Group "Services".-In the same window, select the needed attributes then click on OK: Multiple attributes can be selected by using the Ctrl or shift keys. -Current State-Start Type

      6. Now back on the Situation's main page, stay on the Formula tab.-Enter Conditions-In current status column, change operator to Not Equal and type in Running for the value to be compared.-In the Start Type column, leave operator as Equal. For this attribute, typing a value is not required, use the drop-down and select Automatic.-Select a sample interval, use 5 minutes.-Leave the Run at Startup checked.-Go to Distribution tab: -Decide which Windows managed systems which run this situation. Select a managed system, in the Available managed systems frame and then click on the appropriate arrow to put it in the Assigned frame.-Go to Action Tab:-This will be a system command. -In the System command area, type - sc start -Then use the insert attribute, select service name.-The command should look like this: sc start &{NT_Service.Service_Name}-Indicate "Take Action on each item".-Indicate "Execute Action at the Managed System (Agent)".-Indicate "Don't take action twice in a row…".-Click OK to save, distribute, start the situation, and exit the Situation Editor.

    2. Factors that affect Situation overhead (Sampled Situations)

      1. Distribution. Try to run the situation only at the managed systems where it is required.

      2. Interval - The interval determines how often the situation executes. A situation that runs once per minute will have about 10 times more overhear then one that runs every 10 minutes.

      3. Attribute Table Size.-When a situation run, a query is executed by the agent to create the attribute table. In the example created above this would be a table of all Windows Services. If 130 services are defined on this a server, then the table would have 130 rows. If one is aware of the size of the attribute table. This information should be considered when choosing the interval. Many attribute tables have one row, others could have 1000's.

      4. Stronger Conditions First -Make the first condition in your situation one that will eliminate the most rows. Perform the checks of numeric data before checking string data; ie check CPU % before checking for the process_name. In the sample above, the first condition is current state NE Running. On a random sample system, this eliminated 55 of the 130. This leaves the second condition a table of 75 to operate on. If I had used the second condition first, I may eliminate more rows with the first condition. Some awareness of your data can help improve the efficiency of the situation.

      5. Use of function such as substring and scan will cause some extra overhead, but using the grouping functions such as Count, Min, Max, and Avg., will cause the agent to have to send the attribute table up to the TEMS. The TEMS will take over and run the situation. If these functions were used on a large attribute table this could be a very high overhead on the agent, the TEMS, and the network connecting them.

    3. Considerations for Pure Event Situations

      1. A Pure Event situation is one that is checking for a event such as a log file message or a Windows Event log message. A pure event situation does not have an interval; it is always watching its data source i.e. log file. Each time a record is written to the file, the situation is executed. If there is a log file that has potential to be "flooded" with messages, this could cause high overhead on the agent. Even worse, it these messages match the condition of the situation then one agent could cause the TEMS it is connected to use very high CPU which could cause other agents to timeout or create other problems.

      2. Avoid using situations that could become true 100's or 1000's of times with a short amount of time.

      3. Consider using a policy to start when the pure event situation is true. The policy could stop the situation for a period of time. Even stopping it for 1 minute could prevent the problem of being flooded. The policy could stop the situation, wait one minute, and then restart it.

    4. Duper

      1. When multiple situations are created against the same attribute group, the ITM situation manager tries to look for ways to reduce overhead. If there are 2 or more situations which are using the exact same attribute group and they have the same interval (and a couple other conditions). Then instead of the agent collecting data for each situation, it will collect it once and let all the similar situations use the data from a single collection. For large attribute tables this could save a lot of resources.

      2. For a situation or a situation to qualify for the duper process, it must have these qualities:-Monitors the same attribute group on the same managed system and with the same monitoring interval as at least one other situation.-Uses only the VALUE formula function.-Does not specify persistence, a display item, reflex action, an Until clause, or dynamic thresholding with expression override.

      3. To exploit the Duper feature, try to use the same interval for situations against the same attribute group.

      4. When duper is in effect for some situations, those situations are no longer run by the agent. There is an additional internal situation (created with name starting _Z_) that the agent runs to gather the attribute data, the user created situations are then run by the TEMS.

      5. There may be cases where you rather have the agent incur the overhead instead of passing it up to the TEMS. If this is the case then DUPER can be disabled. This is done by This is done by adding this line to the KBBENV file:CMS_DUPER=NO.

  3. Given a working ITM environment and customer requirement, create a custom workspace so that the desired information can be displayed.
    With emphasis on performing the following tasks:

    1. Describe ITM workspace.

      1. A workspace consists of different views. The two major view categories are Query based views and Event views.

      2. Query based views include: Table, Pie chart, Bar chart, Plot chart, Circular gauge and Linear gauge.

      3. The most popular event views include: Situation event console view, Message log view, Graphic view, Tivoli Event Console view and Common event console view.

    2. Create or select a blank workspace.

      1. Select a monitoring resource from the Navigator.

      2. Select an existing blank workspace or create a new blank workspace by splitting an existing workspace.

    3. Create objects in the workspace.

      1. Select a graphic type.

      2. Assign a query.-Click assign a query button.-In Query Editor, select a default query.-Select the display columns.-Note: The larger the number of queries and/or the higher the number of managed systems for which data is retrieved from the higher the cost to the ITM infrastructure.

    4. Edit a workspace.

      1. Select the workspace to be edited -> Click the edit icon (pencil icon).

      2. In the Query tab: Assign a query.

      3. In the Filters tab: Select the columns to be displayed in the workspace.

      4. Note: Do not grab data or refresh your screen more than necessary.

  4. Given a working ITM environment and customer requirement, create custom queries so that the desired information can be displayed and performance is optimized.
    With emphasis on performing the following tasks:

    1. Describe ITM workspace.

      1. A workspace consists of different views. The two major view categories are Query based views and Event views.

      2. Query based views include: Table, Pie chart, Bar chart, Plot chart, Circular gauge and Linear gauge.

      3. The most popular event views include: Situation event console view, Message log view, Graphic view, Tivoli Event Console view and Common event console view.

    2. Create or select a blank workspace.

      1. Select a monitoring resource from the Navigator.

      2. Select an existing blank workspace or create a new blank workspace by splitting an existing workspace.

    3. Create objects in the workspace.

      1. Select a graphic type.

      2. Assign a query.-Click assign a query button.-In Query Editor, select a default query that is similar to the query you want.-Select create another query.-Create a name for the new query that is prefixed with your initials.-Modify the query to meet your requirements.-Select the display columns.-Note: The larger the number of queries and/or the higher the number of managed systems for which data is retrieved from the higher the cost to the ITM infrastructure.

    4. Edit a workspace.

      1. Select the workspace to be edited -> Click the edit icon (pencil icon).

      2. In the Query tab: Assign a query.

      3. In the Filters tab: Select the columns to be displayed in the workspace.

      4. Note: Do not grab data or refresh your screen more than necessary.

    5. Processing Queries. When creating queries consider the following: The query assigned to a chart or table view requests data from a particular attribute group. It executes when you open or refresh the workspace. Queries make up the processing load for on-demand data collection. You can reduce the frequency and amount of data sampling by:

      1. Customizing the query to filter out unwanted data. This reduces the number of selection criteria (rows) and attributes (columns) collected.

      2. Applying the same query to other views in the workspace. This reduces the number of data samples required: one query uses a single sample for multiple views.

      3. Disabling automatic refresh of workspace views or adjust the refresh rate to longer intervals. This causes Tivoli Enterprise Monitoring Agent data to be collected less frequently.

      4. Consider how you wish to display the data returned by a query. A graphical view workspace may require significantly less data compared to a table view, because it uses only the truly numeric data and leaves out the character data.

      5. Do not confuse custom queries with view filters from the Filters tab of the Query Properties editor. View filters fine-tune the data after it has been retrieved by the query and do not reduce network traffic, data collection processing, or memory demands.

    6. The following general recommendations and observations might be considered as well:

      1. Some attributes are more expensive to retrieve than others. One expensive column in a table will make any workspace view or situation that references that table more expensive. An example of an expensive attribute is one that must run long storage chains to determine its value, such as by using a process table to look for looping tasks. Where possible, ensure you only retrieve attributes that are required for the monitoring process.

      2. Column function (such as MIN, MAX, AVG, and so on) requires post processing of the query results set after data is returned to TEMS.

      3. Use more efficient data manipulating functions, such as substring instead of string scan. If you know the position of the string to search, do not scan the whole string to check for the value.

  5. Given a working ITM environment, backup ITM objects so that the objects can be restored if required.
    With emphasis on performing the following tasks:

    1. Understand what IBM objects are stored in what ITM servers.

      1. TEPS - User IDs, Navigator views, custom queries and custom workspaces, etc.

      2. Hub Tivoli Enterprise Monitoring Server - managed system list, Situations and Policies, etc.

    2. Backup and restore Workspaces.

      1. Backup: tacmd exportWorkspaces

      2. Restore: tacmd importWorkspaces

    3. Backup and restore situations.

      1. Backup: tacmd bulkExportSit

      2. Restore: tacmd bulkImportSit

    4. Backup and restore managed system list.

      1. Backup: -tacmd listsystemlist-tacmd viewsystemlist

      2. Restore:-tacmd createsystemlist-tacmd editsystemlist

    5. Backup and restore user group and users.

      1. Backup-tacmd listUserGroup-tacmd listUsers

      2. Restore-tacmd createUserGroup-tacmd createUser

    6. Backup and restore TEPS configurations.

      1. Windows:-Backup: migrate-export.bat-Restore: migrate-import.bat

      2. UNIX/Linux-Backup: itmcmd execute cq "runscript.sh migrate-export.sh"-Restore: itmcmd execute cq "runscript.sh migrate-import.sh"

  6. Given a working ITM environment and customer requirement, describe how Take Actions and Universal Message can be used to help the customer automate business rules, so that how Take Actions can benefit the customer have been described.
    With emphasis on performing the following tasks:

    1. Describe ITM Take Action.

      1. A Take Action consists of two different options. These two actions are execute a System command and Write a Universal Message.

      2. System commands include any command that can be executed on the appropriate system.

      3. A Universal Message is a message with a Category, Severity, and Message.

    2. Describe System command options.

      1. System command have conditions based upon if more than one monitored items become true.

      2. System command can be executed at the Agent or TEMS.

      3. System command have conditions based upon if true for multiple intervals.

    3. Describe Universal Messages.

      1. Universal Messages have conditions based upon if more than one monitored items become true.

      2. Universal Messages command have conditions based upon if true for multiple intervals.

    4. Understand Security features available for Take Action.

      1. Only Security feature available for System commands is to use Command Prefix.

      2. When using command prefix the agent passes the command to the application handler instead of executing the command, which attaches the TEP User ID to the command.



Promotions


Connect with Us