TEC Installation

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):

1. Installing the Tivoli Management Framework
2. Configuring the event database
3. Installing components in a Tivoli environment
4. Installing the Web console component
5. Installing the NetView component

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:

1. Install and configure Oracle database

2. Configure Oracle client
3. Install the Tivoli Management Framework
4. Install patches
5. Configure the event database
6. Set up Tivoli roles and resources in the Tivoli desktop
7. Start the event server
8. Configure default event groups and consoles

9. Deactivate unnecessary default rule sets

10. Install the Web console component
11. Install the NetView component

Install and configuring Oracle

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.

• The database server hosts the event repository schema. Consider the following when you determine which computer is to be your database server:
  • This computer must have a TCP/IP connection to the RIM host (event server)
  • This computer does not need to be a managed node in the Tivoli region, but it must be on the same subnet as the Tivoli region.
  • This computer must have enough available disk space to support the amount of information that you plan to store in the event repository.
• The RIM host provides communication with the database database in a common, database-independent manner. In most Tivoli environments using the Tivoli Enterprise Console product, the most efficient place for the RIM host is on the event server. That means that you need to install Oracle client of the event server.

Oracle prerequisites

For an Oracle database, the following prerequisites must be met before using the installation wizard:

1. Because it utilizes an existing instance to run, an Oracle instance must be created before running the installation wizard.
   
2. If you install the event database from an Oracle client, the client must be configured to communicate with the existing Oracle instance. For more information about configuring the Oracle client and the database instance, see the Oracle 9i Net Service Reference Guide.
   
3. [Optional] If you need to support multiple languages, you should create the required Oracle database instance using the UTF-8 character. For more information about UTF-8 support, see Enabling language support for Oracle.
   

4. Oracle considerations

   • Because the Oracle database is often installed using the Oracle installation to create the event database, you must use unique names for all table spaces within the database. If more than one event server is installed on the Oracle server, you must assign unique table space names for each database
   • The Install Database Objects and Remove Database Objects options are not available for Oracle in the installation wizard. Unlike other operating systems, the Oracle database installation uses an existing database instance for event data and does not change settings in the existing instance. Options for other databases are available because they create new databases for the event data.
   • Installing or removing the Oracle database does not cause the Oracle instance to be stopped and restarted, as with other databases.

Install the Oracle database and SQL*Plus on the database server. For installation details, refer to your Oracle documentation.

Configure Oracle client

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.

1. Install the Oracle client software, which includes SQL*Plus, on the RIM host.
2. If the Oracle server is on a separate computer than the client, copy the tnsnames.ora file from the

   %ORACLE_HOME%\network\admin

   directory on the database server to the %ORACLE_HOME%\network\admin directory 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.
   

3. Verify that the tnsnames.ora file is properly updated to reflect your configuration. In other words, check that the host name of the server, the Oracle instance ID, the port SQL*Plus is connected to, and the communication protocol are accurate.

Install SNMP

• Install SNMP and run it.
• Enable the SNMP community name public for read access on devices in the local subnet.

Install Tivoli Management Framework

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

Install patches

1. Review the IBM Tivoli Enterprise Console Release Notes for the list of required patches and download them.
   
2. Extract the files to a temporary directory.
   
3. From the Tivoli desktop, select Desktop --> Install --> Install Patch. The Install Patch window is displayed.
   
4. If the Select Product to Install list contains the correct patch, go to step 8; otherwise, continue to step 5.
   
5. Click Select Media. The File Browser dialog box is displayed.
   
6. Navigate to the directory that contains the installation image. The installation directory contains the product index (.IND) file.
   
7. Click Set Media & Close to save the new media path and return to the Install Patch dialog box.
   
8. Select the patch.
   
9. Click Install & Close and Continue to Install. Messages are displayed in the window indicating the status and completion of the installation.
10. Repeat this procedure for each required patch.
11. Restart the oserv process with the odadmin reexec command.

Envoke TEC Installation Wizard to Install TEC

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:

ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_3.9.0/3.9.0-TIV-TEC-FP0007

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:

• To run commands in the Tivoli environment
• To create and work with databases

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.

• You need to invoke it from TEC installation CD or directory where you untared the files. 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 (aka RIM host). The latter should has the database client software installed.

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.

This strange term "RIM object" and how it is abused in TEC documentation

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:

The following items should be considered for Oracle before beginning your event database configuration:

• You must source your database environment to use any of the following options offered by the installation wizard:
  • The Simple option
  • The Custom-Generate and execute option.
  • The Custom-Execute only option
  For more information, see Sourcing the database environment for the installation wizard.

Generating Installation Scripts Using TEC Installation Wizard

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:

1. Get the latest version of TEC Installation Assistant from
2. Move to the directory were you untarred TEC Installation Assistant and launch the tec_install.sh script
   
3. When the welcome window appears, click Next.
   
4. Specify a temporary location to copy the installation files to, and click Next. Default is /tmp and ususally it is OK. The wizard copies several Java-related files to this temporary directory.
   
5. After the wizard copies the files, click Next. the wisard will automatically restart from the temporary location.
   
6. Accept to the required terms of the license agreement, and click Next.
   
7. Select Configure the event database (default option) and click Next.
   
8. Select custom and click Next.
   
9. Click Generate only and click Next.
   
10. Type the directory where you want to store or read generated scripts (for example, /opt/tecscripts, and click Next.
    
11. Fill in the fields that specify the location of the events database and the user that should be used to access it and click Next.
    

    Field	Action
    Database Home	Type the full path to the directory were Oracle client software is installed.
    Database Name	Type a unique alias name of the event database used by TEC Default: tec
    Database User ID	Type a user name of the instance owner for the event database. Default: tec
    Database Password	Type the password for the database user.
    Verify Password	Retype the password for the database user.
    Database Server ID	The name of the Oracle listener service in the tnsnames.ora file. Example: TIVOLI_DEVL
    Instance Home	Not requred for Oracle (DB2 only)

    
    
12. To accept the default values, click Next.
13. Select size of the database in megabytes (for example, 100)
14. accept default in the screen
    • Type of Undo management: auto
    • Type of application profile name: tec_profile
    • role_name: tec_app
      
15. Specify information for each table space. Accept defaults
17. After you have reviewed the summary window, click Finish (if you , click Next. The main installation window appears and you need to click cancel to exit)

Running the wdbconfig.sh script

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 :

• You are root.
• You have generated the event database installation scripts, as outlined in Generate scripts only
• You are able to run SQL scripts via Oracle client.

Examining error logs

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.

DbInstall2002-07-12-57_03PM.log

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.

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.

Installation notes:

• The event database must be configured before you install this component.
• You must install the Tivoli Enterprise Console JRE before installing 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 install using the installation wizard, as part of the installation process you are given the opportunity to deactivate any of the default active rule sets. When you install 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 installation. For more information, see the IBM Tivoli Enterprise Console Rule Set Reference.

  Note:
  

  The dependency rule set is 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.

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.

Set up Tivoli roles and resources in the Tivoli desktop

1. From the Tivoli desktop, double-click the Administrators icon.
2. Right-click the Root_TMRServerName-region icon (where TMRServerName is the name of the Tivoli server) and click Edit TMR Roles.
3. Move all roles from Available Roles to Current Roles.
4. Click Change & Close.
5. Right-click the Root_TMRServerName-region icon and click Edit Resource Roles.
6. For each resource, select and move all roles from Available Roles to Current Roles. Each time you move roles, click Change, otherwise your change is not saved. Click Close after you move all the roles for each resource.
7. Right-click the TMRServerName-region icon and click Managed Resources.
8. Select and move all resources from Available Resources to Current Resources.
9. Click Set & Close.
10. Exit the Tivoli desktop.

Start the event server

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.

Configure default event groups and consoles

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]

where:

• hostname: Specifies the host where the UI server is installed.
• [operator] Optionally designates an operator as the owner of the console. This operator must be a Tivoli root Administrator and must not own any other consoles. If an operator is not specified, the current user is automatically designated as the owner of the console.
• user Specifies the user ID of the system.
• password Specifies the password of the user.

For more information on wcrtteccfg, see IBM Tivoli Enterprise Console Command and Task Reference.

Deactivate unnecessary default rule sets

When you install or upgrade the event server, the following rule sets in the default rule base are activated by default:

• maintenance_mode
• netview
• ebusiness
• heartbeat
• cleanup

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 

where:

rulesets

Specifies the names of the rule sets to be deactivated. If you want to deactivate more than one rule set, insert blank spaces between the names.

For example, to deactivate the netview and heartbeat rule sets, type the following:

wrb_default_rb -inactivate netview heartbeat

Installing the Web console component

1. Click Install the Web console component, and click Next.
2. When a message appears explaining that the WebSphere Application Server will be restarted during installation, click Continue.
3. Click Install IBM Tivoli Enterprise Console Web component, and click Next.
4. Click Install the IBM WebSphere Application Server now, and click Next.
5. After reviewing your selections, click Next.
6. When prompted, insert the WebSphere Application Server installation CD, and click OK.

   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.
7. Select the language you want to use, and click OK.
8. Accept to the required terms of the license agreement, and click Next.
9. Click Custom installation and complete the WebSphere Application Server installation, by clicking Next and accepting the default values.
10. When you complete installation of the WebSphere Application Server, you are asked if the installation was successful. Click The IBM WebSphere Application Server was successfully installed, and click Next.
11. Click Add to add a Tivoli region.
12. Type acadia for Host name, Administrator or root for User name, and the password for that user. Then click Next.
13. Click all of the managed nodes (only acadia appears in this deployment), and click Finish.
14. Click Next to proceed.
15. After reviewing your selections, click Next.
16. When prompted, insert the CD containing the Web console installation image, and click OK to install the Web console.
17. After reviewing the installation messages, click Next. The main installation window appears.

Installing the NetView component

1. Click Install components in a non-Tivoli environment, and click Next.
2. Click Install one of the following IBM Tivoli NetView components.
3. Click IBM Tivoli NetView server and console, and click Next.
4. Click Discover only the local subnet, and click Next.
5. Leave the SNMP community names blank, and click Next.
6. Type acadia for Host name of the event server.
7. Type 0 for a UNIX event server or 5529 for a Windows event server for Listening port of the event server.
8. Click the appropriate operating system of the event server, and click Next.
9. To proceed without configuring the NetView server further, click Next.
10. To proceed without selecting language packs, click Next.
11. After reviewing your selections, click Next.
12. When prompted, insert the CD containing the NetView server installation image, and click OK to install the NetView server.
13. After reviewing the results, click Finish.
14. To exit, click Yes.

Starting the Web console

To start the Tivoli Enterprise Console Web console and view events, complete the following:

1. Start a browser and go to http://acadia:9080/TecConsoleWeb.
2. Type Administrator or root for User name.
3. Type the password for that user.
4. Select the managed node acadia.
5. Click OK.

You can then view events.

NEWS CONTENTS

• 190313 : Installing and Configuring Tivoli Enterprise Console 3.9 Feature Option 1 ( Installing and Configuring Tivoli Enterprise Console 3.9 Feature Option 1, )

Old News ;-)

Installing and Configuring Tivoli Enterprise Console 3.9 Feature Option 1

This is windows oriented presentation but some slides are interesting for Unix admin audience.

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.

Recommended Links

Softpanorama Recommended

Top articles

Sites

TEC Installation Guide

IBM Redbooks TEC Implementation Examples

Installing TEC

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.html

To install TEC, follow the steps mentioned below:

1. Ensure that you have Java™ 1.3.1 installed and that the path is set correctly.
2. Untar the TEC CD1 and unzip the CD2. Also, untar the TEC Fix Pack 4 to FP4 directory.
3. 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.
   1. The Welcome to InstallShield Wizard screen displays.
   2. At the Select an item to install screen, select the default Configure the event database and click Next.
   3. Specify the temporary directory and click Next.
   4. Click Next to close the installation wizard.
4. A new window displays.
   1. The Software License Agreement screen displays. Select I accept the terms in the license agreement. Click Next.
   2. 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.
   3. A screen displays that prompts to you select the type of installation. Select the default Custom and click Next.
   4. 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.
   5. Ensure that the option Generate and Execute Script is selected.
   6. A screen displays that allows you to install, upgrade, or remove a event database. Select New Install and click Next.
   7. 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.
   8. 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.

Etc

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

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