Test 594: IBM Tivoli Enterprise Console V3.9 Implementation

Section 1 - Tivoli Architecture and Databases

1. Given a customer without an understanding of the Tivoli Enterprise Console architecture, describe how TEC works so that the customer can identify the various components of TEC and diagram how they interact.

With emphasis on performing the following steps:
1. Describe the TEC architecture.
2. Explain how adapters collect information.
3. Explain how adapters deliver events.
4. Describe the architecture of the TEC server and the tec_server process.
5. Explain the tec_reception process.
6. Explain the tec_rule process.
7. Explain the tec_dispatch process.
8. Explain the tec_ui_server process.
9. Explain the tec_task process.
10. Explain the tec_gateway process.
11. Explain RIM layer.
12. Describe the JAVA and Web event consoles.
13. Explain State Based Correlation.


2. Given database administrator (DBA) access to an RDBMS, TEC V3.9 media, appropriate Tivoli Administrator privileges, and an installed managed node, install TEC V3.9 server functionality validated by the appropriate commands showing that the Tivoli Enterprise Console server is running.

With emphasis on performing the following steps:
1. Create and verify RDBMS prerequisites.
2. Get and mount the TEC V3.9 CD-ROM.
3. Understand the implementation order of all TEC components.
4. Install the TEC V3.9 server product on one managed node by specifying RIM parameters.
5. Verify RIM setup.
6. Install the TEC V3.9 console. With the Java console, this can be a managed node or a non-Tivoli node (done manually).
7. Run the Installation Wizard.
8. Start the Server.


3. Given Tivoli administrator privileges, verify the ability to connect to the TEC RDBMS server using the TEC RIM object, so the event server successfully connects to the database.

With emphasis on performing the following steps:
1. Run the Tivoli environment setup scripts.
2. Verify existence of RIM object.
3. Confirm ability to connect.


4. Given the need to integrate IBM Tivoli Data Warehouse (TDW) with TEC, configure TEC/TDW integration.

With emphasis on performing the following steps:
1. Install ETL1.
2. Create the ODBC connection.
3. Install and schedule the ETL.
4. Extend the database.
5. Enable the ETL extraction.


5. Given an understanding of the proposed TEC architecture, determine recommended installation methods in order to obtain a functional TEC installation in a TME environment.

With emphasis on performing the following steps:
1. Determine method of installation (Installation Wizard, standard install).
2. Install TMR.
3. Install TEC .
4. Install managed node, gateway, and endpoints.

Section 2 - Tivoli Events, Event Groups, and Event Consoles

1. Given an event group name and a set of filters, create an event group and filters so that the appropriate events are displayed in the view.

With emphasis on performing the following steps:
1. Create an event group.
2. Add filters to an event group.
3. Verify filters exist in an event group.
4. Verify creation of default event groups and console(s).
5. Verify the additional filters that can be used in TEC V3.9.


2. Given a valid Tivoli administrator account with senior privileges, a defined event group, a Tivoli event console, Tivoli Web Console, and a set of roles to be given on that group to that console, assign the event group with those roles so that event console or Web Console, validated by the administrator of that console, will be able to appropriately access events in that event group.

With emphasis on performing the following steps:
1. Assign event groups and roles.
2. Assign event group filters.
3. Assign TEC console administrator role.
4. Create TEC operator.
5. Set configuration options for the Java and Web console.


3. Given an installed and functional TEC and NetView environment, configure the integration between NetView and TEC so that network status can be monitored from the TEC Console.

With emphasis on performing the following steps:
1. Select the appropriate NetView rule.
2. Select the appropriate TEC destination.
3. Configure appropriate TEC filters.
4. Import appropriate NetView event rules and classes.
5. Configure TEC to launch NetView features (Submap Explorer, Object Properties, Diagnostics).
6. Install NetView Web Console.

Section 3 - Tivoli Adapter Implementation

1. Given that ACF is installed on all gateway machines, deploy a Tivoli adapter to the target and verify that the configuration files exist and the adapter is running on the target.

With emphasis on performing the following steps:
1. Create and configure Profile Managers and Profiles.
2. Open ACF Profile.
3. Set before actions.
4. Set after actions, run gencds and restart adapter.
5. Customize adapter to use custom format files.
6. Set target location, user and group ownership and configuration file name.
7. Set target machine and push Profile.


2. Given TEC V3.9 media, appropriate privileges, a development directory, a list of install targets and a TEC server TCP/IP name, configure and deploy a non-TME event adapter and validate the successful reception of events based on test conditions on one of the install targets.

With emphasis on performing the following steps:
1. Install the non-TME adapter.
2. Modify the appropriate configuration files.
3. Package/create the adapter install image.
4. Deploy the adapter to the destination machines.
5. Generate an event condition and test for reception.


3. Given adapter information, appropriate privileges, a distribution list, adapter documentation, and knowledge of modifications to be made, modify adapter configurations validated by successful updates to adapter functions.

With emphasis on performing the following steps:
1. Identify the adapter information.
2. Identify which configuration files need to be changed.
3. Update configuration information.
4. Update and deploy the adapter profile.
5. Start and stop adapter(s).
6. Test adapter modifications.


4. Given the name of an adapter configuration file, appropriate access to the adapter machine, and a list of attribute/value pairs on which to filter, configure filtering for a TEC adapter, and test the new filtering configuration by confirming that an event with attributes to filter is either forwarded or discarded.

With emphasis on performing the following steps:
1. Shut down the adapter.
2. Utilize regular expressions for filtering.
3. Add/edit filter clauses.
4. Employ other configuration parameters to further control event flow.
5. Start the TEC adapter.


5. Given the TEC media and a TME, install, configure, and start adapter(s) such as HPOV and SNMP so that the configuration files exist and the adapter is running on the target.

With emphasis on performing the following steps:
1. Install the adapter from the Tivoli Desktop.
2. Edit the .conf file to activate filtering, if needed.
3. Verify the adapter daemon is running.
4. Edit the necessary files to enable new traps.


6. Given the name, process identifier, location of an installed TEC event adapter, appropriate privileges, adapter documentation, and installed TEC server functionality, test the ability of the specified adapter to detect, format, and send events by verifying whether a test condition results in the matching test event being received.

With emphasis on performing the following steps:
1. Make sure the adapter is running.
2. Make sure the TEC server is running.
3. Identify the particular event class to use as testing item for this adapter. (e.g., su failure for logfile adapter).
4. Create a raw event or condition on the node that has the adapter running.
5. Test reception of the event.


7. Given open ports on the firewall, access to TEC media, appropriate privileges, a development directory, a remote node, an adapter name, and privileged access to the remote node, deploy the non-TME version of the adapter on the remote node, validated by generation of a test condition resulting in successful reception of the event on the TEC server.

With emphasis on performing the following steps:
1. Determine the port used to communicate with the node.
2. Update the adapter configuration files.
3. Create and deploy the adapter image to the desired external node.
4. Generate an event and verify reception condition (depending on type of adapter) on the external node.


8. Given a TEC gateway, test the ability of the TEC gateway to process duplicate events using the State Based Correlation Engine so that duplicate events are dropped.

With emphasis on performing the following steps:
1. Verify TEC gateway SBC is running.
2. Verify appropriate gateway and SBC configuration file settings.
3. Use the State Based Correlation Engine to filter duplicate events.
4. Manage tec_gateway throttling.


9. Given that the Tivoli Framework is installed and policy regions exist, create Profile Managers and assign subscribers to match customer requirements.

With emphasis on performing the following steps:
1. Create profile managers hierarchy.
2. Create profiles within the profile managers.
3. Subscribe managed resources to profile managers.
4. Set distribution options.
5. Set dataless or database profile manager functions.


10. Given the TEC V3.9 media, install the EIF toolkit and necessary libraries so that custom adapters can be created.

With emphasis on performing the following steps:
1. Extract the necessary files for adapter creation.
2. Become familiar with the APIs involved in building a custom adapter.

Section 4 - Tivoli Tasks, Jobs, and Scripts

1. Given a running event console and event conditions under which a given list of tasks should be run, create an automated task so that the tasks will be run upon reception of an event meeting the conditions.

With emphasis on performing the following steps:
1. Start the event console and open an event group.
2. Configure automated task(s).
3. Send test event which matches input conditions.


2. Given a policy on which events to keep or clear from the database and the maximum number of events to clear per interval, create a scheduled job to enforce the given policy.

With emphasis on performing the following steps:
1. Estimate the event load.
2. Verify and adjust the TEC configuration to match policy.
3. Restart the TEC server.
4. Create a task to clean the database, using the Clean Database task in the TEC tasks library as a template.
5. Create a job and schedule it for the determined maintenance interval.
6. Confirm the database is being cleared according to policy.


3. Given a routine task or job and a group of endpoints, create a Tivoli task or job so that it can be executed against the endpoints or subscribers from a single location without errors.

With emphasis on performing the following steps:
1. Create the task library.
2. Create the task to automate.
3. Decide what platform the task will run against.
4. Supply the appropriate authentication roles, user IDs, group IDs, and source host path to the script.
5. Create the job.
6. Execute the task or job.

Section 5 - Rulebases

1. Given the host name of a destination TEC server and a local TEC server, set up event forwarding so that certain events are forwarded to the destination TEC server.

With emphasis on performing the following steps:
1. Write a rule to forward events.
2. Test the rule.


2. Given a TMR without TEC that is connected to one or more TMRs with TEC, configure the TMR without TEC to access the TEC resources of the other TMRs.

With emphasis on performing the following steps:
1. Exchange necessary resources.
2. Update necessary resources.
3. Send events from the TMR with no TEC to the TMR with TEC.


3. Given a customer business problem, and appropriate privileges, write rules and classes so that they successfully address and solve the customer business problem.

With emphasis on performing the following steps:
1. Break down business problem into events and responses.
2. Determine relationships/common attributes of different events.
3. Determine unique/specialized event information.
4. Design event class definitions and event class hierarchy.
5. Modify and activate event class definitions.
6. Subdivide/break up responses to lowest common form (e.g. if event A; do event B).
7. Differentiate responses into if/then and causal/cancel responses and write these in pseudo-code format.
8. Create a rule base.
9. Write rules to satisfy these responses.
10. Enable rules.
11. Test event class and rule executions.


4. Given class and rules files, import the files into a rule base and activate it so that the rule base uses the new classes and rules.

With emphasis on performing the following steps:
1. Create a new rule base if needed.
2. Determine the order for class and rules files.
3. Import BAROC files in order.
4. Import rule files.
5. Import rule files into the rule base target.
6. Compile the rule base.
7. Load the rule base.
8. Stop and restart the TEC server.
9. Test new classes and rules by sending events.


5. Given the class information to be modified, a rule base, and appropriate Tivoli privileges, modify the appropriate BAROC event class definition file, activate the changes, and validate by testing reception of a posted event with the new class information.

With emphasis on performing the following steps:
1. Update a BAROC file.
2. Add that BAROC file to the rules base.
3. Compile and load that rules base.
4. Send a test event.
5. Verify the event was received.


6. Given a specification of what a rule base should do and a report of what it is really doing, debug the rules so that the rule base matches the specification.

With emphasis on performing the following steps:
1. Identify events required to reproduce the problem.
2. Turn on rule tracing around necessary rule(s).
3. Reproduce the problem by sending events.
4. Turn off rule tracing around necessary rule(s).
5. Analyze the Trace Log output.
6. Correct the rule base.
7. Verify the rule base modifications correct the problem by sending the same problem events.


7. Given a set of event relationships, write correlation rules to match and process those events.

With emphasis on performing the following steps:
1. Write a rule using the appropriate predicates.
2. Distinguish between cause effect and related events using appropropriate rule predicates.


8. Given the creation of a new prolog predicate or fact files, determine how to make this available to the TEC server.

With emphasis on performing the following steps:
1. Configure the environment variables in the system to ID the prolog compiler.
2. Load and activate as required.

Section 6 - Troubleshooting

1. Given appropriate privileges, a valid administrator's event console name, and event information to be modified, view and modify events using the appropriate commands.

With emphasis on performing the following steps:
1. Use appropriate CLI to view desired event(s).
2. Modify appropriate event(s).
3. View modified events.


2. Given administrator privileges and desired level of tracing, enable RIM and OSERV tracing so that corrective action can be taken, RIM connections can be established, and the OSERV and other Tivoli components can be traced.

With emphasis on performing the following steps:
1. Decide the level of tracing.
2. Configure the environment with Tivoli environment variables.
3. Run the appropriate commands and verify output.
4. Configure RIM tracing and determine the level of tracing required.
5. Configure OSERV tracing and determine the level of tracing required.


3. Given a running TEC server, turn rule tracing on or off for the current rule base so that a new rule trace file is created and updated with trace information when tracing is turned on and so that no trace information is written when tracing is turned off.

With emphasis on performing the following steps:
1. Look up the trace file location.
2. Identify the current rule base.
3. Compile rule base with tracing.
4. Load the rule base.
5. Reconfigure TEC with trace file.


4. Given a particular adapter, appropriate Tivoli privileges, and the name and location of the diagnostic configuration file, start (stop) the event adapter and verify that diagnostic output is being written to the appropriate log file.

With emphasis on performing the following steps:
1. Identify and modify the appropriate adapter configuration file.
2. Enable the updated configuration file on all relevant targets.
3. Turn a particular adapter off and on.