|
Home | Switchboard | Unix Administration | Red Hat | TCP/IP Networks | Neoliberalism | Toxic Managers |
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix |
|
Tivoli Enterprise Console (TEC) was an old flagship of the Tivoli product line because it is the focal point of collecting events from several other Tivoli products.
|
Functionality is OK but the quality of the interface (TEC console which is a very primitive Java application) is low. For the last 5 years it can be called extremely low quality and I am wondering about IBM inability to adapt to TEC a much better interface which is readily available in Lotus Notes.
Now with Netcool/Omnibus considerably overlapping functionality (and Micromuse acquisition providing a completely different SQL-style correlation engine) IBM was forced to chose sides. And it did. TEC is scheduled to be discontinued in September 2012 but probably will exist for several more years and key functionality (Prolog engine) might some day migrate to some open source software.
I will not be surprised if because of migration difficulties and complains they will provide some level of support after this date too. Defection are also possible: IBM multiple acquisitions of widely different product with overlapping and incompatible correlations capabilities (candle and Netcool) has left enterprise customers vary about the consistency of IBM's long-term vision. Migration from TEC to any of those is not an easy task to say the least. For complex ruleset migration to BMC Event Manager might be much easier as it shares more with TEC (being common descendant of the original TEC) and uses prolog as a correlation engine and BAROC for event structure descriptions. See Migrating_to_BMC_Event_Manager.doc
TEC is not very user friendly as it uses pretty obscure language (Prolog), but at least it is programmable. Semantic is complex and can be learned only gradually. Some things in TEC still look strange even after several years of experience. For example rules for closing rules via messages is one such example -- it looks like it closes the last opened message of the same type, not the first (oldest) one). Complex tasks generally requires either consultants or bright people among staff. Unfortunately, often a simple task requires the same :-).
TEC was really an innovative solution at the time it was released (around 1996 or more then fifteen years ago) and while definitely outdated still contains several interesting implementation ideas. Among them:
Internal architecture was pretty innovative in 1994-1996 when it was designed (at this time servers have on average 64 megabytes of memory, CPU speed was around 0.1GHz and 1G drive was a pretty large and expensive drive. ) It many ways TEC defined the field of large enterprise event processing.
Now many architectural decision look old, the structure of the events with fixed length field looks somewhat ugly and with scripting languages and HTTP protocol CORBA became meaningless in this particular domain...
The TEC event server architecture consists of five processes:
Process Name | Description | Log File | |
---|---|---|---|
tec_server | The master process | /tmp/tec_master | |
tec_reception | The reception engine process | /tmp/tec_reception | |
tec_rule | The rule engine process | /tmp/tec_rule | |
tec_dispatch | The dispatch engine process | /tmp/tec_dispatch | |
tec_task | The task engine process | /tmp/tec_task |
An additional process, the UI server process, plays an integral part in the overall Tivoli Enterprise Console architecture. The UI server is not a part of the event server, although it communicates with the event server. Each process has its own log file.
The most prominent feature of TEC is the usage of Prolog interpreter for writing rules and performing correlation. While it was probably fashion-based solution (Prolog was all-scream, top fashion thing in 80th) in retrospect the decision to use Prolog interpreter as the correlation engine looks like a mixed blessing.
On the plus side we need to admit that:
On the minus side non-procedural programming does not give it much advantages and Prolog does not have the power of modern scripting languages. To be fair we need to admit that Prolog was extended by IBM in a rather clumsy way to allow some level of procedural programming. But still this is programmable (which is better then open) solution as Prolog is a established standardized programming language. It also makes TEC a very rare example of a widely deployed expert system (although most Tivoli users does not utilize advanced capabilities of the Prolog engine). Prolog can be a good query language but only for top-level specialists.
If used by highly skilled Prolog programmer such an engine is a powerful tool. But most Tivoli administrators are not Prolog programmers and have difficulties using the rules engine. It is also rather difficult to use correctly as the number of documents and number of pages in each document are large but useful information is very scarce (IBM docs contain 66% or more of fluff).
An important caveat here is the phrase "to use correctly". TEC is an expensive platform that requires (as many complex systems do) expert developers and system architects to build true world-class solutions. Those costs are non-productive costs which IT department needs to bear. Moreover without a proper understanding of the underlying architecture of TEC and Prolog, it is possible to develop only a primitive event tracking applications which might be done quickly with much less effort and expense by using any open source monitoring package like mon, Zabbix, Nagios, etc. that's why the return on investment in a typical TEC shop is low to marginal -- the complexity eats all the benefits. for simpler envirments But with experts the TEC platform brings can be a competitive advantage to the company as you can do things that other companies cannot...
The first rule of TEC deployment is to offload Prolog engine from the most basic processing, like duplicates removal. A cleaner architectural solution is to use two level event filtering with the gateway-based filtering (non-Prolog based) performing routing filtering tasks and aggregating events and Prolog processing on Tivoli server level devoted only to really important and reasonably rare "derivative' events (two level solution might also necessary from the availability point of view as Prolog engine is incapable to withstand even a mild "event storm" ).
The second rule of TEC deployment is to structure TEC rule base in such way that each rules set process only specific type of messages or several closely related types. That permits to implement a "master select statement" in event processing and use pretty complex rule-bases without fear that the engine becomes too overloaded.
TEC uses BAROC as the events structure definition language and as such the description has the flexibility limited to C structures programming. In other words the structure of the message is fixed and types of the fields are fixed too. This proved to be less limitation that one might think.
Minimum configuration TEC is just $3K and using Linux-based deployment and logadapters you can monitor any number of servers you wish without breaching the license. Essentially using endpoints on log-aggregation servers and converting events from some open source monitoring solution into TEC event via some kind of bridge permits using TEC correlation engine at minimum additional costs. That means that TEC might make sense even for mid-side corporations who have IT specialists that can learn Prolog and which have need and desire to do complex correlation of events to minimize noise and make event processing more useful for the corporation.
See also
SG245013 Maintaining Your Tivoli Environment Chapter 4. Maintaining the Tivoli availability environment
- 4.1 Tivoli Enterprise Console (TEC)
- 4.1.1 Understanding TEC
- 4.1.2 Maintaining TEC
- 4.1.3 Troubleshooting TEC
- 4.1.4 Optimizing TEC
- 4.1.5 Self monitoring TEC
- 4.2 Rule base
- 4.2.1 Understanding rule base
- 4.2.2 Maintaining rule bases
- 4.2.3 Troubleshooting rule bases
- 4.2.4 Optimizing rule base
|
Switchboard | ||||
Latest | |||||
Past week | |||||
Past month |
IBM Tivoli Enterprise Console InformationIBM Tivoli Enterprise Console Newsletter (click http://www.ibm.com/support/docview.wss?rs=643&uid=swg27011895&tcss=PUSHTEC )
and the
TEC Technical Support Information Update
http://www.ibm.com/support/docview.wss?rs=643&uid=swg27013878&tcss=PUSHTECThe key new information in these editions includes:
Updated "Portal - General" Section -Tivoli Information and Support Assistance Portal
IBM Press books - Implementing ITIL Change and Release Management by Larry Klosterboer
Support Hints and Tips updated
Support Hints and Tips has been updated with actions to take Before contacting SupportTop 3 Technotes are:
- TEC 3.9 and Framework RIM: Some Important Concepts
http://www.ibm.com/support/docview.wss?rs=643&uid=swg27014405&tcss=PUSHTEC- Featured Documents for IBM Tivoli Enterprise Console version 3.9
http://www.ibm.com/support/docview.wss?rs=643&uid=swg27011986&tcss=PUSHTEC- Fixes by Versions for IBM Tivoli Enterprise Console 3.9
http://www.ibm.com/support/docview.wss?rs=643&uis=swg27012023&tcss=PUSHTECNew Technical Support Information Updates Section
A new Technical Support Information Updates section has been added. This section is designed to help you derive maximum value from your software by providing the most up-to-date technical information, answers to frequently asked questions, and links to other key information. See Contents section above or click Technical Support Information Update
Tivoli Knowledge at your Fingertips
Have you seen the Software Support Handbook lately? Did you know that, among other things, this handbook can help you effectively utilize the Knowledge content available from IBM on the web? If you've got questions about a product or are looking for an APAR fix but aren't sure where to get it, look no further.By going to the Software Support Handbook and selecting Client self-assist tools, you can chose to search specific areas for information, such as downloads, troubleshooting information, documentation, or planning. Alternately, you can do a global search through IBM Support's Knowledge Database, downloads, redpapers, publications, etc. simply by choosing Support and downloads: Search. From here, you have the choice of limiting your search to a specific product area. Regardless of your approach, you will be amazed at the information you will find right at your fingertips.
Redbooks, Field Guides, etc
Other sites for general news A Netcool OMNIbus Primer for IBM Tivoli Enterprise Console Administrators
Do You Want More Value Out of Your Tivoli Products and Experience?
Netcool + Tivoli: delivering service management innovation.
Migrating from IBM Tivoli Risk Manager to IBM Tivoli Security Operations Manager 3.1
Best Practices for IBM Tivoli Enterprise Console to Netcool/OMNIbus Upgrade
For more information, about the community, click on Tivoli User Group
Using Framework 4.1.1 Commands with Tivoli Enterprise Console 3.9
This STE will be a discussion of helpful Framework commands such as idlattr, idlcall, objcall, wchdep, wdepset, bdbe, etc., related to TEC 3.9 Framework objects.Configuring the SMTP Client to work with TEC
This is STE will cover steps that are required to set up the smtp_client executable to work with TEC.Configuring TEC 3.9 to use MSSQL 2005 as the Database Server
This STE will cover a step-by-step demonstration of what is required to set up a MSSQL 2005 Database for use with the TEC Server.Installing the Tivoli Enterprise Console Web Console with WAS in Network Deployment Mode
This STE will cover installing the Tivoli Enterprise Console Web Console in a Network Deployment Environment.Using TSM Server Instrumentation for Performance Tuning
This STE will cover instrumentation tracing available for the TSM server and client to assist in diagnosing performance problems. Topics will include instrumentation traces, hints and tips for what to look for in the instrumentation traces, and examples of traces from sample performance problems.Tivoli Enterprise Console Integration with IBM Support Assistant Workbench Version 4
This STE will cover the IBM Support Assistant Version 4 new features and the TEC plugin.What's new in 3.9.0-TIV-TEC-FP0008 ( Fixpack 8 for TEC )
This STE will cover any new enhancements for TEC as well as apars fixed in this release.Using DB2 UDB for Tivoli Enterprise Console 3.9: Hints and Tips for Maintenance
This STE will be a discussion of helpful SQL and db2 database commands for maintaining TEC db2 database.TEC Logfile Adapters - Creation, Distribution, Adapter Identifiers
This STE will cover the steps required to set up multiple instances of a TEC Logfile adapter in order to balance the load on the system so that one Logfile adapter is not doing all of the work.IBM Support Assistant- IBM Tivoli Enterprise Console v3.9 add-on available
ISA v4 product add-on is available for TEC v3.9Tivoli fix pack Strategy Update
Tivoli fix pack delivery schedule for 2008 and changes to the fix pack process.Upgrade steps for TEC 3.9 WebConsole component
Procedure to upgrade TEC 3.9 Web Console component3.9.0.8-TIV-TEC-LA0093 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This limited availability interim fix provides an update to the maintenance_mode.rls file.3.9.0.8-TIV-TEC-LA0092 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This interim fix provides an update to the TEC Java Console.3.9.0.5-TIV-TEC-LA0050 IBM Tivoli Enterprise Console Version 3.9 LA Interim Fix
This limited availability interim fix provides files that resolve a problem with the wsetemsg command.3.9.0.6-TIV-TEC-LA0060 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This limited availability interim fix updates the IBM Tivoli Monitoring for Tivoli Enterprise Console agent on 64-bit AIX. Updated 2007/08/233.9.0.8-TIV-TEC-LA0090 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This limited availability interim fix provides files that update the TEC Web Console since the release of 3.9.0-TIV-TEC-FP0008.TEC 3.9.0 Feature Option 1 Interim Fix 4 (3.9.0-TIV-TEC_FO1-IF0004)
This interim fix provides an update to the TEC Feature Option 1.3.9.0.5-TIV-TEC-0052 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This interim fix provides files to enable running of the IBM Monitoring Agent for the Tivoli Enterprise Console.3.9.0-TIV-TEC-FP0008 IBM Tivoli Enterprise Console Version 3.9 Fix Pack 8
IBM Tivoli Enterprise Console Version 3.9 Fix Pack 8 will include all APAR solutions completed since the release of Fix Pack 7.FRWCB0218E Distribute failed for subscriber . acpEp Error: 512
FRWCB0219E Distribute failed for some subscribers: -> FRWCB0300E Distribute of profile 'MON_Ext_Allgemein@SUB_Ext_OPSYS_AC_W2K3' failed for some subscribers: -> FRWCB0218E Distribute failed for subscriber 'sw2-vie-57': -> ACP endpoint command failed (exit code 512) Profile MON_Ext_Allgemein@SUB_Ext_OPSYS_AC_W2K3, Endpoint sw2-vie-57, Type tecad_OMNIbus_tec.rls update_omnibus_events rule does not close event
Event of type OMNIbus_Update sent from Omnibus to TEC via the eif gateway Changes the severity of the event but does not close the event.$DBDIR/tl_rules.err and $DBDIR/tl_rules.out grow in size
The rulesets ebusiness.rls, dependency.rls and netview.rls call tl_init() and if a call is made to this then output is put to the above files even if debug tracing is set to off.ACP distribution fails with CreateFile Failed, Error: 3
Distribution of a TEC adapter fails with the error below:wstartesvr error 38 Database module failed
After installing TEC for the first time get error message: Error::FRWTE0017E 21/7/2008 15:17:37 (17): system problem: `ERROR: Process T/EC Reception exits with exit code 38: Initialization T/EC Database module failed' when trying to start the TECSending unencrypted event data from a tec_gateway to the tec_server
Why it is possible to send events from a tec_gateway with SSL config set to FORCE_SSL when SSL is not installed on the receiving tec_server and the tec_gateway is configured to send events in connectionless mode?Mapping RIM Agents to 3.7x TEC Consoles
We're using TEC 3.7x and need to link the RIM_DB2_Agent owned by nobody and db2agent owned by the RIM user ID to the TEC Administrator. This was possible in TEC 3.6x How can wconsole list administrators but cannot map RIM Agents to these users?ECO3111E Error
"ECO3111E File "/apps/tivoli/bin/aix4-r1/TME/TEC/Customer_RB/TEC_RULES/.load_rules.wic" is unwriteable." error occurs attempting to compile a rulebase.Possible problems with tec_gateway running with State based correlation
The tec_gateway will run if UseStateCorrelation is set to No but there is a problem if this parameter is set to YESJava console working with interconnected TMRs
There is not full documentation on how the java console works in interconnected TMRs if the following is not followed then some Tivoli ids may not be able to call up a TEC consoleReassign operators after unassigned with create operators.
tec_console using create operators unassigns other operators so that they have to be reassigned.Console changes show on Summary Chart View, but not on Event Viewer
In the Configuration option of TEC Java console, a constraint has been added to an Eventgroup.WASX7017E web console install assistant error with WAS 6
error message: WASX7017E: Exception received while running file "/tmp/tecwc_config.jacl"; exception information:TEC server crashes seconds after it is started.
TEC server crashes seconds after it is started, after there has been a previous crash. The tec_rule file reports a 211 error. Collect a rules trace and check if the last line of this file references a .wic fileWAS 6.0.2 and web console
There can be problems installing the web console at this version with the Install Assistant and then there can be connection problems once installed.ECOWSO001E when trying to connect web console.
Check the SystemOut.log from WAS, the error message could be J2CA0036ETEC Server showing umlauts as ? ?
Events sent from adapters are converted to question marks ?? on the TEC Server. The machine is running an Oracle database.'Empty' TEC adapter cache file length '0' or 54 bytes
An empty adapter cache sometimes has 0 bytes against and sometimes 54 bytes against it.Number of .wic files in ../TEC_RULES/$INTERP/"
Once a rulebase is compiled how many .wic files should be in "/BINDIR/TME/TEC/<rulebase-name>/TEC_RULES/$INTERP/"IWAE0037E error when installing TEC 3.9 Web Console
IWAE0037E Scripting Exception on tecra.rar file during the install of the web console on AIX 5.3 with WebSphere Application Server 6.0 using the Installation Assistant.Tivoli Enterprise Console Newsletter
The Tivoli Enterprise Console (TEC) Newsletter is for you, IBM Product Practitioners, to assist you and to enhance your skills in the management of your organization's TEC products.What's new in 3.9.0-TIV-TEC-FP0008 ( Fixpack 8 for TEC )
Audience: Level 2 support, Services, customers Abstract: This STE will cover any new enhancements for TEC as well as apars fixed in this release. Presented by: Sandi Comsudi Date: July 9, 2008Installing Tivoli Enterprise Consoles's Event Repository on AIX with Oracle 10g
Audience: Level 2 Support, Services, GTS, Business Partners, Customers Abstract: This STE will cover the steps involved in setting up and installing TECs Event Repository on AIX operating system using Oracle 10 as the Database on a separate sever. Presented by: Calvin Moody Date: May 6, 2008Featured documents for IBM Tivoli Enterprise Console Version 3.9
This page lists featured documents identified as valuable in helping answer your questions related to IBM Tivoli Enterprise Console Version 3.9. This list will be updated periodically to reflect new issues.2004_10_29 STE: Real World Usage of TEC V3.9 Event Correlation Rules
Presentation from the October 29, 2004 Support Technical Exchange (STE) call for IBM Tivoli Enterprise Console V3.9 focusing on the real world usage of ITEC V3.9 Event Correlation RulesHP OpenView Tivoli Enterprise Console (TEC) Adapter
STE for the Description of the HP OpenView TEC Adapter by Jerry Swan,Configuration Options for the Tivoli Enterprise Console V3.9 Gateway
Support Technical Exchange (STE) Presentation made by Jerry Swan on 2005_10_18 to show configuration options for the ITEC V3.9 GatewayTivoli Support Technical Exchange ( STE ) - ITEC 3.8
Tivoli Enterprise Console 3.8Tivoli Support Technical Exchange ( STE ) - TEC 3.8 UNIX Logfile Adapters
Presentation on TEC 3.8 UNIX Logfile adapters2004_11_08 STE: TEC Warehouse Enablement Packs (WEPs)
Presentation from the November 8, 2004 Support Technical Exchange (STE) call for Tivoli Enterprise Console Warehouse Enablement Packs (WEPs) for Tivoli Data Warehouse V1.xIZ22854: JAVA CONSOLE EXCEPTION WITH AUTOMATED TASK
On the Java Console, when creating a new automated task with selected event, I get a null pointer exception when adding aIZ29179: A CONNECTION PROBLEM WITH ONE OF THE CONNECTIONS PREVENTS THE OTHER CONNECTIONS FROM FUNCTIONING.
Problem Description: A connection problem with one of the connections prevents theIZ22844: UNABLE TO INSTALL TEC HEALTH AGENT USING DB2 9.1
Problem Description: .IZ26912: EVENT WITH SINGLE QUOTES NOT LOADED TO CACHE AFTER WSTARTESVR
Problem Description: Event with single quotes not loaded to cache after wstartesvrIZ24728: JAVA EXNOPERMISSION ERROR WHEN LOGGING INTO TEC JAVA CONSOLE
Problem Description: JAVA EXNOPERMISSION ERROR WHEN LOGGING INTO TEC JAVA CONSOLEIZ23388: TEC WAS CONSOLE DOESN'T UPDATE DISPLAY
Customer has various WAS consoles up displaying events after some time (sometimes a month, sometimes days) they notice thatIZ25322: KKAAGENT WILL NOT START UP AFTER INSTALLATION ITM 6.2 FP1 AND RUNNING OF WAGTINIT BINARY
Problem Description: .IZ24175: THE USER SPECIFY THE "NEWLOGBASEDON=MTIME" VARIABLE IN THE CONF FILE, "CHMOD NNN FILE" CAUSES TO FIRE THE EVENT.
Problem Description: When the customer specify the "NewLogBasedOn=mtime" variable inIZ22709: FILENAME KEYWORD FOR SUB_SOURCE AND SUB_ORIGIN DOES NOT SET DBCS FILE NAME PROPERLY
FILENAME keyword for sub_source and sub_origin deos not set DBCS file name properly.IZ23210: CLOSING EVENTS DOES NOT UPDATE EVENT STATUS IN SECOND EVENT VIEWER
If there are two event viewers open in the Java version of the TEC Event Console, and there are events in the event database
This interim fix provides files to enable running of the IBM Monitoring Agent for the Tivoli Enterprise Console.
Date: 8/31/2006
General Description: This interim fix provides critical updates to the TEC Server to support the enablement of the IBM Monitoring Agent for Tivoli Enterprise Console. This agent provides monitoring of the TEC server components and event flows as well as Situations, Workspaces, and Take Action commands in the IBM Tivoli Enterprise Portal (TEP). The TEP monitoring environment is provided to TEC customers by a limited use license of the IBM Tivoli Monitoring V6.1 components. The TEC Health Agent is provided to TEC Customers.
Please see the Patch Readme and Health Agent Readme for more information. Additionally, the Tivoli InfoCenter has been updated with the User's Guide for the Health Agent.
The Health Agent is available via Passport Advantage:
http://www-142.ibm.com/software/sw-lotus/services/cwepassport.nsf/wdocs/passporthomeCurrent TEC customers will go to the Passport Advantage site like they normally do and put in their subscription number and then be presented with their entitled products. The part numbers for the Health Agent images are: C944JML, C945XML, C945YML, C94MIML, C94MJML.
Refer to e-assemblies: CR0YQML (AP) and/or CR0YPML (non-AP).Additionally, there is a new "Tivoli Monitoring for TEC" User's Guide in the TEC InfoCenter:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.itec.doc_3.9/toc.xmlPrerequisites
IBM Tivoli Enterprise Console Version 3.9
IBM Tivoli Enterprise Console Version 3.9 Fix Pack 5 (3.9.0-TEC-FP05)
This tool is a command line utility which runs under UNIX and the BASH shell under Windows. It takes the command line arguments, validates them, builds an SQL query, runs the "wtdumper -w" command with the query, and formats the output based on command-line switches.
The command line arguments consist of sets of event attribute names, and the value to search for in the database. A display parameter is also required.
For example, the following command will search the event repository for all TEC_Notice events with a hostname of host1, and will display all matches:
./query_er.sh -class TEC_Notice -hostname host1 -da
Disclosed by International Business Machines Corporation
Whats New in 3.9.0-TIV-TEC-FP0007: Tivoli Enterprise Console Fixpack 7
Fixpack 7 was released on September 28, 2007 and there are some new features as well as fixes for known problems. In this STE, we will cover both those new features and troubleshooting those known problems.Installing the Tivoli Enterprise Console Web Console with WAS in Network Deployment Mode
This STE will cover installing the Tivoli Enterprise Console Web Console in a Network Deployment Environment.Warehouse Enablement Pack EC2 - Tivoli Enterprise Console
This web seminar will provide a detailed overview on how data is transferred from the TEC Database to the warehouse. Best practices for troubleshooting and recovery will be discussed.Installing Tivoli Enterprise Console V3.9 on Linux for System z.
This STE will explain the necessary steps to install the Tivoli Enterprise Console server components on SUSE 9 linux for System z. We will go through the install for the Framework and DB2 and answer any questions that you may have on the topics.Tivoli Enterprise Console 3.9 Windows Event Adapter Overview
This STE will cover the installation and configuration options for the Windows Event Log Adapter. The latest enhancements and function changes to the adapter will also be discussed.IBM Support Assistant - Tivoli Enterprise Console v3.9
This will discuss how ISA implemented w/ the TEC integration piece will allow users to search databases and learning materials to understand the product, and will provide a collection utility that contains information from where the ISA is installed. Prerequisite:TEC 3.9 w/ Fixpack 4 or Fixpack 5.Setting The Tivoli Enterprise Console Event Viewer Information button
We will discuss how to set up the Tivoli Enterprise Console (TEC) Java Console Information buttonURGENT: Daylight Saving Time changes will affect IBM Tivoli Enterprise Console
Information about the impact of recent Daylight Savings Time changes such as the US Energy Policy Act of 2005, which changes the effective dates of US Daylight Saving Time (DST) in 2007 for the US. Actions are required to address these issues in IBM Tivoli Enterprise Console.New Zealand Daylight Saving Time (DST) Changes: Information for IBM Tivoli Enterprise Console
New Zealand has extended Daylight Saving Time. DST will start one week earlier than usual on 30 September 2007 instead of the first Sunday in October and it will end two weeks later on 6 April 2008 instead of the third Sunday in March. Systems and applications that process dates and times will be affected by this change. If no action is taken, computers and applications that use local time will be off by one hour for the first week in October, the last two weeks in March, and the first week in April.Information about 3.8.0-TEC-ELFALA and what it provides
There is reference to a Limited Availability interim fix entitled 3.8.0-TEC-ELFALA that is available for download by contacting Tivoli Customer Support. 3.8.0-TEC-FP02 also delivered this code.3.9.0.6-TIV-TEC-LA0057 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This limited availability interim fix allows a tec_gateway profile to be distributed when the tec_gateway configuration directory does not exist.3.9.0.6-TIV-TEC-LA0058 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This limited availability interim fix provides an update to the TEC SNMP adapter.3.9.0.7-TIV-TEC-LA0080 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This limited availability interim fix provides a fix to TEC Gateway Receiver (tec_gwr) component.3.9.0.7-TIV-TEC-LA0078 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This limited availability interim fix provides a fix to tec_dispatch component.3.9.0.7-TIV-TEC-LA0079 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This limited availability interim fix provides a fix to the tec_rule component.3.9.0-TIV-TEC-FP0007 IBM Tivoli Enterprise Console Version 3.9 Fix Pack 7
IBM Tivoli Enterprise Console Version 3.9 Fix Pack 7 will include all APAR solutions completed since the release of Fix Pack 6. Updated 2007/11/063.9.0-TIV-TEC-FP0008 IBM Tivoli Enterprise Console Version 3.9 Fix Pack 8
IBM Tivoli Enterprise Console Version 3.9 Fix Pack 8 will include all APAR solutions completed since the release of Fix Pack 7.3.9.0.7-TIV-TEC-LA0077 IBM Tivoli Enterprise Console Version 3.9 Interim Fix
This limited availability interim fix provides a fix to TEC endpoint adapters.Running "wtdbspace" command fails because of a heap size issue
Error message as follows: sql2310N The utility could not generate statistics. Error "-973" was returned. SQL0973N Not enough storage is available in the "<heap-name>" heap to process the statement. .Tivoli Enterprise Console Program Directory
Provide online copies of the available IBM Tivoli Enterprise Console program directories.TEC SNMP adapter fails to send events
The tecad_snmp adapter should be sending events to the TEC server based upon the traps that it reads and parses as according to the tecad_snmp.cds and tecad_snmp.oid definition files. Sometimes this fails.All TEC tablespaces are full
The "wtdbspace" output does not reflect it, there are not any error messages returned and everything seems to be working fine. But DB2 log shows that tablespaces are full and there are some warning messages when running "wtdbspace" or other DB2 commands.BIMprolog returns *** RUNTIME 600 *** message
./BIMprolog ProLog by BIM - release 4.0.10i - 25-Apr-1995 Copyright (c) 1985-1995 BIM Engineering Europe *** RUNTIME 600 *** File /var/tmp/prologI/interpreter/bin/lib/system.pro non-existent or not a regular file.ADM6017E;SQL0968C error on TEC 3.9 EC2_c05_s040_src_load
CDWEX8087E; ADM6017E; SQL0968C The file system is full. SQLSTATE=57011 TEMP_TWH32K container too small.rule does not trace after adding directive: trace
In trying to test a new rule, the directive: trace is added to the rule but there is nothing in the rules.trace file that is created.The file only contains the name of the ruleprevent UDP packets from being sent when using postemsg.exe
A configuration file is being used with the postemsg.exe and ServerPort (set to a valid port other than 0) and ServerLocation are specified. But UDP packets are still being sent and causing problems with firewall logs etcChanging the RIM database user ID
The TEC database was created by the db2inst1 user id in the db2inst1 instance, Now customer's site has a requirement to change the database useridConfiguration file associated with the windows adapter
What does the NewLogBasedOn value do in the tecad_win.conf file?Efficient Memory management within a rulebase
How can Prolog Heap Table utilization be monitored with the rulebase?Windows 2003 Server with SP1 on Tivoli Enterprise Console
Fixpack 4 for TEC 3.9 provides support for Windows 2003 with Service Pack 1 installed.Limitation of TEC 3.9 Install Assistant
The Web Console was updated in Fix Pack 4 to support WAS 5.1\6.0 and Fixpack 5 allowed for WAS 6.1 but the Install Assistant was not updated to support installing these versions of WebSphere.TEC adapters on Solaris 10 ix86 ?
3.9.0 FP06 Readme does not list if this is supported.CDWEX8087E SQL0530N ETL EC2_c05_s040_src_load
Running the EC2 reports for TDW reports, get the following error: SQL0530NTivoli Platform and Database Support Matrix
Platform and Database support for all Tivoli productsClose or Acknowledge events fail from the Java console
An attempt to modify events from the TEC 3.9 fixpack 4 Java console fails if there is operator inactivity for a certain period of time. Customer has tried the "tec_ui_server_conn_keepalive_interval" option in the ui_server to no avail.Removing additional Tivoli Regions from the TEC Web Console Menu
The procedure to remove unwanted Tivoli Regions from the TEC Web Console login pull down menuTEC install fails when using the Installation Assistant
Using the Tivoli root user, the following error occurs and the installation fails: (May 9, 2006 7:18:23 AM), Setup.product.install, com.tivoli.tec.install.wizard.actions.TMRUnixServerPreChecks, dbg, Current user is NOT within context of TMRThe wsetemsg command fails
Customer's custom script is being executed via a rule, but the wsetemsg in the script fails. Manual execution of the wsetemsg produces the following error: Error::ECO:0001:1473 Command TEC_DB_GET_EVENT failedInstalling the Tivoli Enterprise Console Web Console with WAS in Network Deployment Mode
Audience: TEC users and Administrators that utilize the TEC Web Console Abstract: Installing the Tivoli Enterprise Console Web Console in a Network Deployment Environment Presented by: Ted Douglas, L2 Support Engineer Date: November 12, 2007Part 2 of 2: IBM TEC with Netcool Omnibus - TEC to Omnibus Details
Audience: Any site which has both TEC and Omnibus, or is looking towards a first step in migration from TEC to Omnibus Abstract: This STE follows on from the previous overview presentation. It also is based on Omnibus being the 'master' system and looks in more detail at the TEC rules, Omnibus database definitions and TivoliEif probe rules used for this Integration. The presentation will cover the Initial forwarding from TEC to Omnibus and also subsequent updates made to events on TEC or OmnPart 1 of 2: IBM TEC with Netcool Omnibus - TEC to Omnibus Overview
Audience: Any site which has both TEC and Omnibus, or is looking towards a first step in migration from TEC to Omnibus Abstract: This STE provides an overview of Integration of TEC with Omnibus. The presentation is based on Omnibus as the 'master' system, with TEC forwarding events to Omnibus. Backwards synchronization are also covered. Presented by: David Leftwich, Technical Support Consultant Date: October 29, 2007What's new in 3.9.0-TIV-TEC-FP0007 TEC Fixpack 7
Audience: IT Staff supporting TEC product Abstract: Fixpack 7 was released on September 28, 2007 and there are some new features as well as fixes for known problems. This STE will cover both those new features and some fixes for known problems. Presented by: Sandi Comsudi, Tivoli Enterprise Console Support Engineer Date: October 25, 2007Redpaper - Creating EIF Events with Tivoli Directory Integrator for Tivoli Netcool/OMNIbus and Tivoli Enterprise Console
This IBM Redpaper describes a solution developed for IBM Tivoli Directory Integrator integration with the IBM event management offering products, IBM Tivoli Netcool/OMNIbus and IBM Tivoli Enterprise Console. This integration solution illustrates an integration scenario aimed toward improving Tivoli Directory Integrator's integration capabilities and leveraging these capabilities with IBM event management offering products. Along with examples, we discuss the architecture behind this approach. This document is divided into several sections. For those readers who are not familiar with the IBM products covered in this Redpaper, we provide a brief overview of Tivoli Directory Integrator, Tivoli Netcool/OMNIbus, and Tivoli Enterprise Console. We then cover the integration with Netcool/OMNIbus and describe an architectural overview and the implementation, installation, and configuration for Tivoli Directory Integrator integration with Netcool/OMNIbus. Similarly, we discuss the integration with Tivoli Enterprise Console and describe an architectural overview, and the implementation, installation, and configuration for Tivoli Directory Integrator integration with the Tivoli Enterprise Console. We discuss additional details about the EIF EventSender component, because it represents a key component that was developed as part of this Redpaper integration. Finally, we document the additional files that ship along with this Redpaper and links to various official documentation.Tivoli Enterprise Console 3.9 Windows Event Adapter Overview
Audience: Tivoli Administrators and Operators, Windows Administrators Abstract: This STE will cover the installation and configuration options for the Windows Event Log Adapter. The latest enhancements and function changes to the adapter will also be discussed. Presented by: Jerry Swan, TEC L2 Support Engineer Date: October 16, 2007Setting The Tivoli Enterprise Console Event Viewer Information button
This Tivoli Support Technical Exchange web seminar will cover how to set up the Tivoli Enterprise Console (TEC) Java Console Information button Presented by: Ted Douglas, Staff Software Engineer Date: August 21, 2007Installing Tivoli Enterprise Console 3.9 on Linux for z/OS
This STE will explain the necessary steps to install the Tivoli Enterprise Console server components on SUSE 9 linux for System z. We will go through the install for the Framework and DB2 and answer any questions that you may have on the topic. Presented by: Jerry Swan, Tivoli Americas TEC L2 Support Date: August 1, 2007Debugging Tivoli Enterprise Console 3.9 logfile adapter problems
This STE will present the various troubleshooting techniques available for TEC 3.9 when working with either the Windows logfile adapter or the unix logfile adapter. This will apply to both TME or non-TME installations. Presented by: Sandi Comsudi, L2 Customer Support Engineer. Date: June 21, 2007 You must prepare and perform a systems check at this location in order to attend the Virtual Classroom. http://asp22.centra.com/SiteRoots/main/SystemCheck/SystemCheck.jhtml?Installing and Configuring Tivoli Enterprise Console 3.9 Feature Option 1
This Web Seminar is intended for IBM customers and business partners interested in monitoring events using the Common Event Infrastructure and converting to those events to TEC - formatted events. It will describe IBM Tivoli Enterprise Console 3.9 Feature Option #1 with emphasis on installation and configuration. Presented by: Randy Hill, IBM Support Engineer Date: June 12, 2007IZ07722: TEC_GWR LEAKS MEMORY IN THE LCF UPCALL LOGIC
Problem Description: tec_gwr leaks memory in the lcf upcall logicIZ08699: TEC FP07 JRE UPDATE DOES NOT STOP THE TEC GATEWAY PROCESS ON MACHINES RUNNIGN MULTIPLE OSERV'S
ENV: WindowsIZ07909: TRANSLATE 3.9 FP07 FIXPACK READMES
fp7 translated readmes need to be publishedIZ06153: WSTARTMAINT.SH DOES NOT WORK WHEN THE DATE SPANS A MONTH
Problem Description:wstartmaint.sh does not work when the date spans a monthIY64197: THE START_MAINTENANCE TASK INCORRECTLY ADD A DAY TO THE DESIRED START DATE WHEN THE WDATE IS A DAY BEHIND THE LOCAL DATE.
The start_maintenance (wstartmaint.sh) task incorrectly add a day to the input start date when the wdate is a day behind theIZ07428: TECWINADAPTER GOES DOWN WITH DRWATSON ERROR WHEN FQDOMAIN=YES IS SET IN ADAPTER CONFIG.
Problem Description: TECWINAdapter goes down with Drwatson error when FQDomain=YES isIY99920: GARBLED CHARACTERS FROM AS400 LOGFILE ADAPTER WHEN MSGQ DATA HAS0X7D AS PART OF DOUBLE BYTE DATA (E.G 0X487D).
Problem Description: Garbled characters from AS400 Logfile adapter when MSGQIZ07237: VALUE OF INTEGER SLOT NOT CORRECT INTERPRETED AND REPLACED BY DEFAULT_VALUE
Problem Description: value of integer slot not correct interpreted and replaced by default_valueIY99731: EVENTS FROM NETVIEW ADAPTER PARSE_FAIL AT THE TEC SERVER
Problem Description: .IY95507: EC2 PERL SCRIPTS CREATE .POSTEDIT FILES WITH UNQUOTED ZERO, THAT ARE TRANSFORMED IN UNEXPECTED NULL WHEN LOADED
EC2 Perl scripts create a file .postedit where all the lines to be loaded in tables are written. These lines should have all the
This add-on to the Tivoli Enterprise Console 3.9.0 product adds support for event sources using the Web Services protocol and integration with the Common Event Infrastructure.
The Tivoli Enterprise Console 3.9.0 product supports a large number of event adapters and event sources, ranging from SNMP traps to events coming from products such as Tivoli Business Systems Manager.
The Tivoli Enterprise Console Feature Option introduces three major components:
- (1) an additional event adapter for event sources using Web Services invocations;
- (2) an extension to a Common Event Infrastructure event server running inside a WebSphere Application Server to enable event forwarding directly to a Tivoli Enterprise Console server; and
- (3) a Web Services event receiver for a Common Event Infrastructure event server running inside a WebSphere Application Server
The new event adapter is called the Enterprise Console Web Services Adapter: a standalone process that can receive events through Web Services invocations and forward these events to an Enterprise Console server. This adapter implements a subset of the Web Services Notification specification, which is promoted by the Organization for the Advancement of Structured Information Standards (http://www.oasis-open.org) and supported by other major software vendors. This new feature allows a Tivoli Enterprise Console operator to manage events produced by event sources using Web Services invocations, such as event sources based on the IBM Autonomic Computing Toolkit (http://www.ibm.com/developerworks/autonomic).
As background for users still not familiar with the Common Event Infrastructure, it is an integral part of the IBM WebSphere Process Server product (http://www.ibm.com/software/integration/wps) and also a key event integration technology within IBM next generation of products.
The event forwarding extension is called the EIF WebSphere JMS Provider and augments the WebSphere Application Server messaging capabilities with support for converting the event format used by the Common Event Infrastructure to the EIF (Event Integration Facility) format used by a Tivoli Enterprise Console event server. This new feature allows a Tivoli Enterprise Console operator to manage events produced by event sources such as the IBM WebSphere Business Monitor product (http://www.ibm.com/software/integration/wbimonitor).
The Common Event Infrastructure Web Services Receiver uses the same Web Services interface used by the Enterprise Console Web Services Adapter. When combined with the EIF WebSphere JMS Provider, this receiver allows a Tivoli Enterprise Console administrator to route events through a Common Event Infrastructure event server before forwarding a copy of the event to a Tivoli Enterprise Console event server. The combination of these two features enables event management through the Tivoli Enterprise Console graphical interfaces at the same time it also allows events to be used for business process monitoring in the IBM WebSphere Business Monitor product.
More information about Common Event Infrastructure can be found at http://www.ibm.com/software/tivoli/features/cei/.
The Tivoli Enterprise Console Feature Option requires TEC 3.9.0 with Fix Pack 4 or greater.
The Tivoli Enterprise Console Web Services, when running on a machine remote from the Tivoli Enterprise Console event server, requires Java (TM) Runtime Environment 1.4 and above.
The EIF WebSphere JMS Provider and the Common Event Infrastructure Web Services Receiver require the Common Event Infrastructure event server installed on WebSphere Process Server (WPS).
This article outlines a possible solution for both Tivoli Management Environment (TME) and non-TME utility agents to minimise the delay in delivering events to the Tivoli Enterprise Console (TEC) server. The aim is to facilitate normal operations, such as service level agreement (SLA) evaluation and timer rule execution, within the rule base.
It is always advisable to provide a highly available infrastructure for event management. This will result in delayed delivery of the TEC events as they are cached on the component that detected the failure.
If caching occurs at the gateway/tec_gateway, automatic flushing of the cached event (already built in the component) is initiated when the connection to the TEC server is re-established. This is the standard behaviour of the tec_gateway.
IntroductionWhen configured appropriately, the Tivoli Enterprise Console (TEC) server can provide a very strong event management infrastructure – even for the largest IT environment. One key aspect of such an environment is robust event delivery. TEC provides several features for such a fault-tolerant and resilient delivery, but it requires the affected components at the event source to be configured correctly.
Even with careful planning and configuration for event forwarding, have you ever wondered why TEC events are not seen at the TEC server when expected? Or why you experience a delayed delivery of the events?
This article discusses the reasons why delivery can be delayed and where TEC events are cached. Possible solutions to manage this – both for Tivoli Management Environment (TME) and non-TME events – are provided, as well as solutions for flushing cached events when standalone utilities (for example wpostemsg and postemsg) are used for event forwarding.
Did you know that IBM Tivoli Training offers free training every month? Did you know that you only have to visit one web page to find a list of all the training that is currently free? The list is sorted by product and currently lists over 70 free Web Based courses. For details on IBM Tivoli Training that is currently free go to: http://www.ibm.com/software/tivoli/edu cation/edu_prd_free.htmlCheck the above link and this web page at least once each month for special offers.
Free IBM Tivoli Training Roadmaps
Not sure which Tivoli course you should take? What about prerequisites or product certification? You need a Skills Roadmap. BM Tivoli Training has individual Skills Roadmaps available for a majority of our products. The roadmaps list the prerequisite requirements, classroom courses, Web Based Training courses, certification information and other education (white papers, RedBI). The Skills Roadmaps are in PDF format and can be downloaded individually or combined in a single . compressed file from: http://www.ibm.com/software/tivoli/edu cation/eduroad_prod.html
Check out the TOP 10 most recent downloads from the Tivoli Information Exchange:
1)
Best Practices on Monitoring 6.1 and more
2) ITM6 agent remote configuration
3) Tivoli Monitoring data sheet
4) "2006 - Takeaways- ITM and IT Process Mgrs tech pr
5) "2006 - Takeaways - TEC, Netview, TPM, TCM tech pr
6) Chicago TUG Endpoint Health scripts
7) Process events from wtdumprl
8) List running desktops
9) T/EC event hit report
10)"2006 - Takeaways - TDW,TBSM, TSLA, ITCAM tech pre
The intent of the paper is to address some of the more important aspects of design and implementation of a DB2 database system in a concise manner, while referring the reader to additional references for more detail.
While much of this material is applicable to DB2 on all available platforms, this paper specifically deals only with DB2 on distributed platforms, i.e. Windows, UNIX, and Linux. The material was obtained from readily available publications on DB2 and from over 18 years experience with designing, developing, and tuning DB2 systems. While DB2 specific, many of the concepts are applicable to Relational Databases in general, such as Oracle and Microsoft SQL Server.
Following the tuning advice in the document will improve the performance of any solution that utilizes DB2 as its backend database platform. This tuning information is extremely relevant for many of the Tivoli products and solutions that use DB2 databases; ITM, TEC, TPM, TCM, TSM, TSLA, TADDM, CCMDB, TDW, Monitoring, Provisioning, Identify, Storage, Discovery, Directory, Warehouse, etc.
By tuning the database, you will gain significant performance improvements. The document describes in detail many of the most important aspects of DB2 database design and implementation. It identifies techniques and parameters that have a significant impact on DB2 performance and helps the reader focus on the most important items.
This paper discusses the integration between IBM Tivoli Monitoring 6.1 and IBM Tivoli Enterprise Console 3.9 with them working in conjunction, yet exploiting their specific strengths, for the monitoring and event management spaces.
It describes a simple end-to-end scenario that can help someone get started. It also discusses different configurations of this integration based on different event loads, such that specific environments are properly configured to run smoothly and efficiently without interruptions to service. Some scenarios and their workarounds are also discussed in case of network connectivity failure between Enterprise Console and the Tivoli Monitoring 6.1 TEPS server.
Provider: IBM
NavCode: 1TW10TM2D
Right now, OpenESM has OpenESM for Monitoring v1.3. This release of the software is a combination of Zabbix, Apache, Simple Event Correlation and MySQL. Out of the box, we provide monitoring - warehousing of monitoring data - SLA reporting - correlation and notification. We offer the source code, but we also have a VMWARE based appliance.
This web seminar will provide a detailed overview on how data is
transferred from the TEC Database to the warehouse. Best practices
for troubleshooting and recovery will be discussed.
This STE will explain the necessary steps to install the Tivoli
Enterprise Console server components on SUSE 9 linux for System
z. We will go through the install for the Framework and DB2 and
answer any questions that you may have on the topics.
This will discuss how ISA implemented w/ the TEC integration piece will allow users to search databases and learning materials to understand the product, and will provide a collection utility that contains information from where the ISA is installed.
Prerequisite: TEC 3.9 w/ Fixpack 4 or Fixpack 5.
The Tivoli APAR notification page contains a list of some open or
recently closed APARs that may impact you. Please review the APAR
record to determine if there is an interim fix or fix pack you need
to apply.
There is reference to a Limited Availability interim fix entitled
3.8.0-TEC-ELFALA that is available for download by contacting Tivoli
Customer Support. 3.8.0-TEC-FP02 also delivered this code.
Tivoli fix pack delivery schedule for 2004 through 2008 and changes
to the fix pack process.
This limited availability interim fix is a consolidation of several
previous LA Patches (57, 58, 59, 63, 65, 68, and 70). It provides
fixes to TEC adapters for the APARs below.
This limited availability interim fix provides fixes to TEC adapters
for several APARs.
This add-on to the Tivoli Enterprise Console 3.9.0 product adds
support for event sources using the Web Services protocol and integration
with the Common Event Infrastructure.
IBM Tivoli Enterprise Console Version 3.9 Fix Pack 7 will include
all APAR solutions completed since the release of Fix Pack 6.
This limited availability interim fix provides an update to the
TEC logfile adapters.
This limited availability interim fix updates the JRE to 1.4.2-SR8
for all supported platforms.
This limited availability interim fix provides an update to the
TEC logfile adapters.
This interim fix provides an update to the Web Services Adapter
component of the Tivoli Enterprise Console 3.9.0 Feature Option
1.
Even if hostname and origin IP value are defined in the (w)postemsg
invocation, this still asks DNS to find the origin IP value
In large and small environments, it may be necessary to look at
how much time it takes for the tec_gateway process to receive an
event, pass it to state based correlation, get it back from state
based correlation and send it on to the TEC Server
If TME Communications fail to send an EVENT to the TEC Server, how
can that event be sent via NON-TME Communications instead of caching
the event.
Determining the length of time a single event enters and leaves
the State Based Correlation Engine
wrimtest fails with code ora 12154 TNSNAMES.
The default syslog on SLES 10 is syslog-ng, not the old BSD-based
syslogd
IBM Tivoli License Manager requires that each product provide an inventory signature file.
Procedure to set up TEC information button to connect to external
Webserver
Clicking Information button in TEC console event viewer returns
a blank http page
Using the tell_err predicate in Windows does not work, and failures
are seen in the rules trace file.
Platform and Database support for all Tivoli products
Using a script to obtain the current EPOCH value for the current
date and time
An example of a number specified pattern matcher that works is:
FORMAT EVENT %5s%1s END An example of a number specified pattern
matcher that does not works is: FORMAT EVENT %5sE END See "Full
Problem Description" below.
Running the TroubleTicket.sh from within a TEC rule, the script
runs as root; However, running the TroubleTicket from the TEC java
console, the script is executed as the user 'nobody'
The TEC Server will not process events in which the msg slot is
very large
The TEC Event Server will not process events through the rules engine
if they come in as closed.
If events come in as CLOSED to the TEC Server, they are not processed
the same through the rules engine as events that come in with a
status of OPEN or ACK
In some situations, the severity of an event needs to be escalated
through the State Based Correlation Engine
If several State Based Correlation Custom Actions are being used,
the ability to compile them all into one useable jar file is required
TEC server will not start and there are no /tmp/tec* logs in /tmp
This STE will explain the necessary steps to install the Tivoli
Enterprise Console server components on SUSE 9 linux for System
z. We will go through the install for the Framework and DB2 and
answer any questions that you may have on the topic. Presented by:
Jerry Swan, Tivoli Americas TEC L2 Support Date: August 1, 2007
This STE will present the various troubleshooting techniques available
for TEC 3.9 when working with either the Windows logfile adapter
or the unix logfile adapter. This will apply to both TME or non-TME
installations. Presented by: Sandi Comsudi, L2 Customer Support
Engineer. Date: June 21, 2007 You must prepare and perform a systems
check at this location in order to attend the Virtual Classroom.
http://asp22.centra.com/SiteRoots/main/SystemCheck/SystemCheck.jhtml?
This Web Seminar is intended for IBM customers and business partners
interested in monitoring events using the Common Event Infrastructure
and converting to those events to TEC - formatted events. It will
describe IBM Tivoli Enterprise Console 3.9 Feature Option #1 with
emphasis on installation and configuration. Presented by: Randy
Hill, IBM Support Engineer Date: June 12, 2007
Abstract: One of the most common challenges in a large event management
system is to determine where a received event should go. In small
TEC environments this is not a big problem, the event filtering
capability of the TEC console is sufficient to ensure the event
gets to the proper administrators. In larger environments, the event
filtering capability may not be the appropriate tool. Often the
event filter specifications become unmanageable and should there
be a need to reinstall or move the TEC.
This STE will cover configuring the Tivoli Enterprise Console 3.9
fixpack 6 SNMP Adapter to match traps specified in an SNMPv2 MIB
and verifying that the adapter matches these traps. Presented by
Randy Hill, IBM Support Engineer on April 11, 2007.
The IBM acquisition of Micromuse Inc. in 2006 marked a major milestone
for IBM Tivoli software because it significantly strengthened the
end-to-end IBM Service Management software portfolio. As new technologies
emerge, the ability to manage networks and provide very high network
availability has become increasingly important for most organizations.
While the IBM Tivoli NetView product has a long history of industry-leading
utility, the addition of Netcool/Precision extends our network management
capabilities to include enhanced layer2 network discovery and best-of-breed
topology-based root cause analysis. This provides our customers
with the most comprehensive, real-time understanding of their network
infrastructures and the fastest possible resolution of network problems.
While significant focus is being placed on enhancing the ease of
installation and use of coming versions of Netcool/Precision, IBM
will continue to protect our NetView customers' investments and
intends to provide a smooth upgrade path to a future converged network
management product offering. This IBM Redbook will help companies
determine if they should migrate now or wait. For those migrating,
it provides detailed instructions for planning and performing the
migration from IBM Tivoli NetView to Tivoli Netcool/Precision IP
V3.6.
The purpose of this field guide is to describe the functionality
of the IBM Tivoli Enterprise Console state correlation engine introduced
in ITEC version 3.8. It also outlines the configuration and design
aspects as well as gives hints for installing and troubleshooting.
Some case studies from different customers are discussed at the
end.
Support Technical Exchange delivered by Ted Douglas on August 17,
2006 to discuss the distribution and configuration of the Tivoli
Enterprise Console UNIX File Log Adapter.
Common customizations of the Notification and Escalation rulesets
shipped with Tivoli Enterprise Console 3.9 (TEC 3.9) can be done
quickly and efficiently. These can improve event management productivity.
Examples will be shown to illustrate customizations in a supported
fashion. Ralph Baldwin will present on these topics on January 9,
2007.
This STE is intended to provide an understanding of the supplied event_thresholds.rls ruleset. Areas covered will cover areas such as
It will be presented by David Leftwich on January 18, 2007.
Problem Description: FILENAME specified in adapter format file populates
wrong file
Problem is as follows, ITM 6.1 uses DM 3.7 classes to send TEC events.
After upgrading to TEC 3.9, it appears that the actions are not
the same for the tecad_logfile entry. Below is what is in the
The TEC Java console event viewer sometimes freezes when using the
Problem Description: TEC adapter fails to match correct class when
%s* is used
EC2 Perl scripts create a file .postedit where all the lines to
be loaded in tables are written.
Problem Description: .
TEC 3.9 fp6 readme needs to be updated to reflect that WAS 6.1 is supported
April 11, 2007 (www.gulfsoft.com)The State Based Correlation Engine (SCE) is a powerful tool for filtering and applying simple correlation rules to TEC events before TEC rules are applied, but a major deficiency is a lack of a general purpose action for manipulating events. In order to manipulate events in ways other than the simple methods provided by the supplied actions, one had to develop a new Java class.
Presented here is a general purpose SCE action that embeds the Rhino JavaScript engine that enables the use of JavaScript programs to manipulate events.
This article credit goes to IV Blankenship. Tivoli documentation says there is no way to send ITM events to multiple TEC servers, which is true. However, there is an intelligent workaround for this problem. This article gives you an idea of how to do it.
The idea is to forward the situation events to SCE and write a custom action to forward to multiple event servers. The following java class shows how to send events to single TEC server, which can be tweaked to send events to mulitple TEC servers by modifying the code to to accept multiple sender config files. If you have any questions on how to do it, please feel free to post your comments.
The Java code can be downloaded from <a href=http://www.gulfsoft.com/downloads/TECForwarder.java.zip>here
OK, now I'm treading on sacred ground...
Obviously hardware matters since both are CPU driven applications, but assuming we're dealing with like hardware, the answer is it depends...TEC
IBM has published benchmarking speeds of the TEC rule engine (a while ago with TEC 3.8 FP whatever running on AIX) at ~65 events per second.
How did they come to derive this number? They start a timer when events are flowing at TEC and stop the timer when the CPU on TEC goes below 5% used.
Is that a good measurement? Maybe, but IMHO not a good way to tell whether the rule engine is really done processing an event, that's for sure. It would be better to actually measure whether the event is PROCESSED in the reception log to really know when th TEC is around ~65 events per second. Of course that is without running any real rules against the incoming events. Another factor to consider is I.V., who as we all know has achieved 300+ events per second using his non-tme rule engine.
Netcool Omnibus
Based on what I've heard in the past from MicroMuse when asked how fast Omnibus processes events, I've heard "thousands of events per second". When we drilled deeper and asked more questions, we were told those were "raw" events and it's more like "hundreds of events per second". What is unclear is whether these events were acted upon by any rules (i.e. is this merely event reception speed). Unfortunately, I don't have any hard benchmarking numbers to share at this point until I get my hands on Netcool code.
So based on this, it really depends on a number of factors such as what kind of rules are you running against your events, how you tell when an event is "processed" by the rule engine, and whether or not you are I.V. ;-)
The Tivoli Enterprise Portal (TEP) provides rich visualization out of the box, and with the Enterprise Console workspace plug-in, network and other non-ITM events can be managed from one interface. With a combination Universal Agent and TEP ODBC query you can create a TEC centric workspace to view TEC events and monitor TEC itself.
Use the following instructions to upgrade the Web console component of the IBM Tivoli Enterprise Console (ITEC) Version 3.9 product. These instructions apply to all ITEC fix packs (These instructions use Fix Pack 3, 3.9.0-TEC-FP03, as an example.)
Use the files from the NON_TME/GENERIC/WC directory of the fix pack and perform the following steps:
1. Copy tecrimds.jar to the AppServer/TEC directory of the WebSphere Application Server installation, overwriting the existing file.
2. Update the TecConsoleEar.ear file from the WebSphere Administrative Console:
a. In the panel on the left, click the plus sign (+) next to Applications, and then select Enterprise Applications.
b. In the panel on the right, check the box next to TecConsoleEAR. Click Update.
c. Check Local path or Server path, depending on where the 3.9.0-TEC-FP03 version of TECConsoleEAR.ear is located. Enter the path to the 3.9.0-TEC-FP03 version of TECConsoleEAR.ear in the appropriate path field. Click Next.
d. At the "Preparing for the application update" panel, accept all defaults and click Next.
e. At steps 1, 2 and 3 of the "Install New Application" panel, accept all defaults and click Next. Please note that none of the options are checked in step 2, including the TecConsoleWeb option. This is the expected behavior, and there is no need to select the TecConsoleWeb option in this step.
f. At step 4 of the "Install New Application" panel, click Finish.
g. Once the application is installed, click the "Save to Master Configuration" link.
h. When prompted to "Click the Save button to update the master repository with your changes", click Save.3. Use the winrar utility to extract tecra.rar to the AppServer/InstalledConnectors/tecra.rar directory of the WebSphere Application Server installation, overwriting the existing files and folders.
The fix pack installation is complete. Restart WebSphere Application Server, the event server, the UI server, and all consoles.
3.9.0-TEC-FP05 IBM Tivoli Enterprise Console Version 3.9 Fix Pack 5 IBM Tivoli Enterprise Console Version 3.9 Fix Pack 5 will include all APAR solutions completed after the release of Fix Pack 4. This fix pack is scheduled to release on June 30, 2006.
Tivoli Enterprise Console can be rightly called the flagship of the Tivoli product line because it is the focal point of events from all Tivoli products. The new version of TEC will bring very important usability and performance enhancements such as Java-based TEC Console and Availability Intermediate Manager (AIM).
This redbook introduces the new Tivoli Enterprise Console V3.7, covering the installation, tailoring, and configuration of the console itself along with an overview of the new Availability Intermediate Manager (AIM) feature. Richly illustrated with examples and sample screens, Early Experiences with Tivoli Enterprise Console 3.7 is an invaluable resource for customers and Tivoli professionals, whether they will migrate to TEC 3.7 from a previous version or implement it from scratch.
This book will help you to use the new rules templates bundled with TEC V3.7 as well as the Tivoli Decision Support for Event Management Guide. It also provides an invaluable troubleshooting guide that provides both general and specific tips for debugging and optimizing the new console.
[PDF] Tivoli on Linux
This paper reviews the NetView / TEC integration capabilities that were available with NetView 7.1.3 and TEC 3.8. It then considers the new integration features added to each product with NetView 7.1.4 and TEC 3.9 respectively, and demonstrates solutions currently available out-of-the-box.
Although many NetView users seem to be upgrading to the latest version, upgrading TEC to the latest version appears to be moving far more slowly - it has far more implications; thus the latter half of the paper considers integration scenarios between NetView 7.1.4 and TEC 3.8
Below is a list of recent STE's, click on Support Technical Exchange to hear a replay of the session
06-May-09 TEC 3.9 Maximize Efficiency by Processing Only Necessary Events
19-May-09 Enabling SSL for use with TEC 3.9 and the TEC java console
03-Jun-09 TEC 3.9: Creating, Testing, and Using Event Group Filters
10-Jun-09 TEC 3.9 Maximize Efficiency by Processing Only Necessary Events
16-Jun-09 Avoid Software Problems and Solve the Tough Ones Fast! AM Session
17-Jun-09 A Comparative Analysis of SNMP MIB Conversion for TEC, Netview, and Netcool
24-Jun-09 Avoid Software Problems and Solve the Tough Ones Fast! AM Session
25-Aug-09 Utilization of software tool WireShark to Trouble shoot TEC issues
Google matched content |
TEC Information Center -- the list on major TEC documents. This link is very difficult to find via IBM site ;-)
SG245013 Maintaining Your Tivoli Environment Chapter 4. Maintaining the Tivoli availability environment
- 4.1 Tivoli Enterprise Console (TEC)
- 4.1.1 Understanding TEC
- 4.1.2 Maintaining TEC
- 4.1.3 Troubleshooting TEC
- 4.1.4 Optimizing TEC
- 4.1.5 Self monitoring TEC
- 4.2 Rule base
- 4.2.1 Understanding rule base
- 4.2.2 Maintaining rule bases
- 4.2.3 Troubleshooting rule bases
- 4.2.4 Optimizing rule base
Tivoli Software Global User Group Community
Early Experiences with Tivoli Enterprise Console 3.7 Published 20 November 2000
IBM Redbooks Maintaining Your Tivoli Environment
[PDF]
Aggregation and Correlation of Intrusion-Detection Alerts
File Format: PDF/Adobe Acrobat
-
View as HTML
... is implemented on top of the Tivoli Enterprise Console
... engine that sits inside the
TEC and processes ... However, given the complexity
of the processing required ...
perso.rd.francetelecom.fr/debar/papers/DebWes01.pdf
-
Similar pages
User Groups
FAQ
IBM Tivoli software training course - IBM Tivoli Enterprise Console 3.9
- How can I display a summary of event counts?
- How do I view % events by class
- How do I get summary counts of events in the last 10 minutes?
- How can you identify the Managed Node Hosting the TEC Server?
- How can you identify the Managed Node Hosting the TEC Server?
- What does the DB2 error SQL1224N mean when I try and start my TEC server?
- How do I test my RIM connection?
- How do I create a TEC User for use with TEC Console 3.7.x?
- How do I create an Event Console for TEC Console 3.7.x?
- How do you compile a prolog source file.
- Which file was an event generated from?
- Filtering events by date and time directly from the format file
- What does %t really mean in a format file
- How can I match on a specific number of characters in a format file
- How to remove the complete "Source Group" Display from TEC Console
- How to speed up startup of the Event Console
- How do I run a query against my RIM database?
- How do I create and load a new Rule Base?
- How do I delete all events quickly?
Etc
The following documents are available in the IBM Tivoli Enterprise Console library:
Provides information about supported adapters, including how to install and configure these adapters.
Provides details about IBM Tivoli Enterprise Console commands, predefined tasks that are shipped in the task library, and the environment variables that are available to tasks that run against an event.
Describes how to install, upgrade, and uninstall the IBM Tivoli Enterprise Console product.
Provides release-specific information that is not available until just before the product is sent to market.
Describes how to develop rules and integrate them for event correlation and automated event management.
Provides reference information about the IBM Tivoli Enterprise Console rule sets.
Provides an overview of the IBM Tivoli Enterprise Console product and describes how to configure and use the IBM Tivoli Enterprise Console product to manage events.
Describes how to install and configure the warehouse enablement pack for the IBM Tivoli Enterprise Console product and describes the data flow and structures that are used by the warehouse pack.
Describes how to develop your own event adapters that are tailored to your network environment and the specific needs of your enterprise. This reference also describes how to filter events at the source.
The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. TheTivoli Software Glossary is available, in English only, at the following Tivoli software library Web site:
http://www.ibm.com/software/tivoli/library/
Access the glossary by clicking the Glossary link on the left pane of the Tivoli software library window.
If you have a problem with any Tivoli product, refer to the following IBM Software Support Web site:
http://www.ibm.com/software/sysmgmt/products/support/
If you want to contact software support, see the IBM Software Support Guide at the following Web site:
http://techsupport.services.ibm.com/guides/handbook.html
The guide provides information about how to contact IBM Software Support, depending on the severity of your problem, and the following information:
User groups provide software professionals with a forum for communicating ideas, technical expertise, and experiences related to the product. They are located on the Internet and are available using standard news reader programs. These groups are primarily intended for user-to-user communication and are not a replacement for formal support.
Society
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
Quotes
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Bulletin:
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
History:
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
Classic books:
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|
You can use PayPal to to buy a cup of coffee for authors of this site |
Disclaimer:
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.
Last modified: March 12, 2019