|(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix
|Tivoli Enterprise Console
|Oracle client installation
|Using Log Files to Troubleshoot Tivoli Environment
Note: The information below is mainly adapted from IBM TEC installation guide with relevant additional information from IBM Redbooks TEC Implementation Examples. The book is good but outdated
IBM TEC installation guide is extremely badly written even discounting for regular IBM documentation quality. The description of installation process is fuzzy and partially incorrect, but still this is a free book ;-). It contains the following sections (none of them can be believed as for accuracy):
To install all components on a single server you probably need 8G of RAM. Without database 4G of RAM might be sufficient. With small database 4G is also OK (I used to both TMF, TEC and database (DB2) on a single V240 server with 4G of RAM; the server had just a couple of endpoints and events were mainly flowing via logadapters).
Installation of all IBM Tivoli Enterprise Console components involves several tasks. The procedure below presuppose that all components except database are installed on the same server. That is actually the most typical deployment scenario in large enterprizes,
You need to be root to install TEC and Framework. The following steps are necessary to install TEC using Oracle database:
Install and configure Oracle database
Deactivate unnecessary default rule sets
There are two components of Oracle installation: Oracle database and Oracle client. Database usually should be installed on a separate server. Oracle client is usually installed on the event server. Tivoli component that communicates with database via client is called RIM host.
For an Oracle database, the following prerequisites must be met before using the installation wizard:
|Directory for generated scripts
|database user ID
|Database session identifier (SID)
|Is RIM host database client or server?
|Oracle home directory
|Oracle SYS password
|Directory names containing table spaces
Install the Oracle database and SQL*Plus on the database server. For installation details, refer to your Oracle documentation.
Complete the following steps to configure the event server as an Oracle client using SQL*Plus. You need to copy TNSNAMES.ORA which is a SQL*Net configuration file that defines databases addresses for establishing connections to them. This file is described at http://www.orafaq.com/wiki/Tnsnames.ora It resides in the $ORACLE_HOME\NETWORK\ADMIN directory.
directory on the database server to the
on the RIM host where ORACLE_HOME is the
environment variable equating to the path to the directory where your
Oracle server or client installation resides.
This part does not differ from installing TMF without TEC and actually documentation for TMF installation is better and more complete in TMF installation documents. See Installing the Tivoli Management Framework
To install TEC (and, simultaneously, to configure the event database), you must use the TEC installation wizard.
Note: Do not download TEC Installation Wizard from TEC product download area. Get the latest version of TEC Installation Wizard from:
See Installing, upgrading, and uninstalling using the installation wizard for information on starting the installation wizard.
The installation wizard should be run on the event server and can operate in several modes: Simple, Custom-Generate, or and Generate-and-execute.
Preferable mode is Generate only. Generated scripts are be edited if necessary and run using the wdbconfig.sh script, which is generated with the SQL scripts. For more information on this command, see the IBM Tivoli Enterprise Console Command and Task Reference.
To configure the event database, you must have the authority to do the following:
You must have authority to run commands in the Tivoli environment because the installation wizard creates the RIM object named tec, which is needed by the Tivoli Enterprise Console components. In the Custom-Generate only and Custom-Execute only modes, you have the option as to whether the RIM object should be created or not. If a RIM object named tec already exists in the system where the installation wizard is run, the installation wizard displays the default values associated with it.
See also: Configuring the TEC event database
The event server is a central server that handles all events. The event server write to database each incoming event and then evaluates these events against a set of rules to determine if it should respond to or modify the event automatically.
RIM is an abbreviation of "database Interface module" and like many IBM acronyms actually it neither necessary or have much of the value for structuring the TEC internals space; this is just a database connector but still for some reason it is stressed in TEC documentation.
Whenever some TEC component connects to a database, the RIM starts the RIM agent process. A RIM agent process uses the database client libraries to communicate with the database and issue SQL statements.
A RIM object is also referred to a Tivoli environment object that contains essential information about a specific database, such as the database name, database user ID. A term "RIM host" is a meaningless term that is equivalent to the event server for all practical purposes; more specifically this is a place were the database client libraries are installed.
The installation wizard creates a RIM object named tec, which contains database information for connecting to the event database. The following table list the database information needed for configuring the TEC event database. This information is also stored in the RIM object. When installing the event server component from the Install Options dialog, enter the following database values:
|Equates to the value in the $ORACLE_HOME environment variable.
|Type a unique alias name of the event database used by TEC. Usually tecdb
|Database User ID
|The database user that owns the application database. The default is tec.
|The password for the database user (tec)
|Database Server ID
|The name of the Oracle listener service in the tnsnames.ora file. Equates to the value in the $TWO_TASK environment variable for a client or $ORACLE_SID on the database server or client.
The following items should be considered for Oracle before beginning your event database configuration:
You should use the custom method. Selecting the custom installation gives you more configuration options to optimize database performance, such as maximizing memory usage and managing the physical layout of data on the disk. For additional information about configuration options, you can also use the field-level help available in each of the windows in the installation wizard.
To start the installation wizard, complete the following:
|Type the full path to the directory were Oracle client software is installed.
|Type a unique alias name of the event database
used by TEC
|Database User ID
|Type a user name of the instance owner for the event database. Default: tec
|Type the password for the database user.
|Retype the password for the database user.
|Database Server ID
|The name of the Oracle listener service in the
|Not requred for Oracle (DB2 only)
The wdbconfig.sh script is generated by the installation wizard and runs the SQL scripts generated by the installation wizard and determines the database type from the SQL scripts located in the generated script directory.
The wdbconfig.sh script must only be run from the directory where the scripts were generated on the RIM host.
The Oracle environment does not need to be sourced. The generated scripts set the ORACLE_HOME environment variable and add ORACLE_HOME/bin to the PATH.
See the IBM Tivoli Enterprise Console Command and Task Reference for more information about the wdbconfig.sh script.
Ensure the following prerequisites are met before running the wdbconfig.sh script :
The installation wizard generates SQL scripts and shell scripts required to create, upgrade, and remove the event database. A log file is automatically created in the same directory you designated for the generated scripts. If the generated event database scripts are run from the installation wizard, the log file also contains the output from running the scripts. You can examine the log file to view results.
The log file is named DbInstalltimestamp.log, as shown in the following example. The timestamp variable is replaced by the current system time when the log is generated.
You can also check for replies from the event database server to each configuration statement in the SQL scripts, as well as any error messages. Error messages can be seen in a file named similarly to the log file (with an .err ending) found in the same generated script directory. Examine both the log file and the error log for complete output from running the database scripts. For example, a file called DbInstall2002-07-12-57_03PM.err is also created that may contain error installation information.Note:
No error logs are generated if the wdbdconfig.sh script is used to perform an install, upgrade, or remove function. Instead the script output is returned to the command line from which the script was run and is visible as the script runs.
Upgrade notes: The event database must be upgraded before you upgrade this component. After you upgrade, you must reload your rule base because the .baroc files have been modified. You must install the Tivoli Enterprise Console JRE before upgrading this component. The installation wizard does this automatically. However, if you are using the Tivoli Management Framework tools, you must install the Tivoli Enterprise Console JRE manually.
When you upgrade using the installation wizard, as part of the upgrade process you are given the opportunity to deactivate any of the default active rule sets. When you upgrade using Tivoli Management Framework tools, you can deactivate any of the default active rule sets manually using the wrb_default_rb command. The default rule base contains many rule sets that you can customize after upgrading. For more information, see IBM Tivoli Enterprise Console Rule Set Reference.
If you used any customized parameters, you must preserve the file $BINDIR/TME/TEC/.tec_config file before you upgrade the event server. You must then reapply the customizations to that file after the upgrade is completed.
Uninstallation notes: It is recommended that you uninstall the event server after uninstalling all other components.
After you have installed or upgraded the event server, you must start the event server. To start the event server, right-click the Event Server icon on the Tivoli desktop and click Start-up.
You can also start the event server manually using the wstartesvr command.
In most situations, the user interface server configures default event groups and consoles automatically during installation. On the the AIX operating system, you must run the wcrtteccfg command on the system where the user interface server is installed.
To configure default event groups and consoles manually, use the following command format:
wcrtteccfg hostname user password [operator]
For more information on wcrtteccfg, see IBM Tivoli Enterprise Console Command and Task Reference.Note: If the automatic configuration fails, ensure that you have proper authorization, and configure the defaults manually.
When you install or upgrade the event server, the following rule sets in the default rule base are activated by default:
The dependency rule set is also active by default, but its activity is linked to the ebusiness rule set and can only be changed by changing the activity of the ebusiness rule set. In other words, when you deactivate the ebusiness rule set, you also deactivate the dependency rule set.
To deactivate any of these rule sets, use the wrb_default_rb command. For more information, see IBM Tivoli Enterprise Console Rule Set Reference.
To deactivate the rule sets of default rule base, use the following command format:
wrb_default_rb -inactivate rulesets
For example, to deactivate the netview and heartbeat rule sets, type the following:
wrb_default_rb -inactivate netview heartbeat
Note:If you are using Windows, the WebSphere Application Server installation program starts automatically. When this happens, close the WebSphere Application Server installation program, and click OK in the installation wizard. The installation wizard then starts the WebSphere Application Server installation program as part of its process. Running the WebSphere Application Server installation program independently may cause confusion and interfere with proper installation of the Web console.
To start the Tivoli Enterprise Console Web console and view events, complete the following:
You can then view events.
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
IY99595: TMR INSTALL IS BAD IF /ETC/TIVOLI/BIN OR /ETC/TIVOLI/LIB EXISTS PRIOR TO INSTALL. INSTALL DOES NOT FAIL BUT TMR IS BAD.TMR install is bad if either /etc/Tivoli/bin or /etc/Tivoli/lib DIRECTORIES exists prior to install.
Google matched content
TEC Installation Guide
IBM Redbooks TEC Implementation Examples
This section provides information about the Tivoli Enterprise Console® (TEC) 3.9 FP 4 installation.
Note: For detailed information about the Tivoli Enterprise Console (TEC) 3.9, see http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.itec.doc_3.9/welcome_nd.htmlTo install TEC, follow the steps mentioned below:
- Ensure that you have Java™ 1.3.1 installed and that the path is set correctly.
- Untar the TEC CD1 and unzip the CD2. Also, untar the TEC Fix Pack 4 to FP4 directory.
- From the CD1 folder, run the ./tec_install.sh script. At the dialog box that prompts you for temporary directory, specify the directory name and click Next.
- The Welcome to InstallShield Wizard screen displays.
- At the Select an item to install screen, select the default Configure the event database and click Next.
- Specify the temporary directory and click Next.
- Click Next to close the installation wizard.
- A new window displays.
- The Software License Agreement screen displays. Select I accept the terms in the license agreement. Click Next.
- A screen displays that prompts you to select an item to install, configure, upgrade, or uninstall. Select the default Configure the Event Database and click Next.
- A screen displays that prompts to you select the type of installation. Select the default Custom and click Next.
- A screen displays that prompts you to specify the directory to store or read generated scripts. Specify the same temporary directory as 3.2. Click Next.
- Ensure that the option Generate and Execute Script is selected.
- A screen displays that allows you to install, upgrade, or remove a event database. Select New Install and click Next.
- Select DB2® as the database vendor. Specify /home/db2inst1/ as database home, tcpip as database server, and /home/db2inst1 as the instance home. Also, specify database name, database user name, password (with verify). Click Next.
- Click Next to start the extraction and execution of the scripts. The log output displays stating that the installation assistant as finished installing the package. Click Finish to complete the installation. Click Yes when the installer prompts you to exit.
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
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
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
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
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
Last modified: March 12, 2019