Tag Archives: ITM

ITM/TEPS – How to fix excessive Navigator tree rebuilding – Agents appearing/disappearing constantly

I have recently run into this problem. The navigator tree was rebuilding/changing constantly resulting the TEPS Console to be nearly unusable. To fix this I set the following variables in cq.ini ( TEPS ini file location under $CANDLEHOME/config/)

KFW_CMW_DETECT_AGENT_ADDR_CHANGE=N

The Navigator function detects when the IP address for an agent is discovered. If the agent environment is constantly changing or has improper configurations that generate excessive Navigator tree rebuilding, consider adding this environment variable to have any discovery of changes or additions of IP address ignored.

KFW_CMW_DETECT_AGENT_HOSTNAME_CHANGE=N

This variable is like the one for detect agent address change except that it prevents the Navigator rebuilding if an agent hostname is changed.

KFW_CMW_DETECT_AGENT_PROPERTY_CHANGE=N

This is like the detect agent address change except that it prevents the Navigator rebuilding if an agent affinity or affinity version changes.

References/Documentation on TEPS environment variables:

http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=/com.ibm.itm.doc_6.2.fp1/itm_admin52.htm

[ad#Google Adsense-1]

ITM Unix installation – Notable directories

The table below lists some of the most important directories used by ITM. This is far from being complete. I will add new information to this whenever I find an other directory worth mentioning 🙂

Number	Location	Description	NodeType
1	$CANDLEHOME/logs	ITM log files	ALL
2	$CANDLEHOME/bin	ITM binary files	ALL
3	$CANDLEHOME/config	ITM ini files. Constructing additonal product configuration values using the environment variable and product specific settings.	ALL
4	$CANDLEHOME/config/.ConfigData	ITM environment variables. contains values set at configuration time.	ALL
5	$CANDLEHOME/tables/[tems name]/ATTRLIB	ITM Attribute files. If you have a seeding problem you can check if the required attr file is in this directory. If it is not the seeding wasn’t successful.	TEMS
6	$CANDLEHOME/tables/cicatrsq/ATTRLIB	Historical data and attrib files ready to be seeded. Once you install TEMS support for a new product the attrib and historical data files are being copied here first. Once you do the seeding it all being copied over to the directory shown above this entry.	TEMS
7	$CANDLEHOME/tables/[tems name]/depot	In this directory there is a parent directory called PACKAGES Sub-directories contain all the packages in that depot.	TEMS
8	$CANDLEHOME/[architecture type]/iw/profiles/ITMProfile/logs	Embedded WebSphere log files	TEPS
9	$CANDLEHOME/[architecture]/ui/jars/resources	TEPS server resource files. If you have teps support problems check if the relevant .jar file is in this directory	TEPS
10	$CANDLEHOME/[architecture]/cw/classes	TEPS Browser client resource files, If you have teps support problems check if the relevant .jar files are in this directory	TEPS Browser Client
11	$CANDLEHOME/tables/[tems name]	Location for historical data collection files if the collection is enabled on TEMS level	TEMS
12	$CANDLEHOME/[architecture]/[agentcode]/hist	Location for historical data collection files if the collection is enabled on TEMA level	TEMA
13	$CANDLEHOME/tmaitm6/agentdepot	Latest installation logs. This directory keeps details of the latest ITM product installation	ALL
14	$CANDLEHOME/[architecture]/cw/classes/candle/[agencode]/resources/advice/[lang]	Location for Expert Advice HTML files	TEPS

How to force ITM agents to specific network adapters when using HACMP

When you install ITM agents on a HACMP solution you need to make sure that the OS agents are running on both Physical nodes and the application agents are running on the active one. The application agent has to be installed on the shared volume group so when a takeover happens it moves with the application. The OS agents to the local filesystem on the physical nodes this way you have both nodes ( Active/Passive ) monitored.

After installation you have to modify the monitoring agent’s .ini file that is located in the [itmroot]/config directory. For example if you try to configure the Unix OS Agent you need to modify the ux.ini.

Set/Modify the following values:

KDEB_INTERFACELIST=!10.10.10.1 This instructs the product to bind to ONLY the 10.10.10.1 interface
attached to the system and publish IP address 10.10.10.1 for the Tivoli service.

CTIRA_HOSTNAME=[hostname]
CTIRA_SYSTEM_NAME=[hostname]

Repeat this step for all agents in scope then restart the agents and after a while they should show up on the TEPS Console under the correct hostname.

References:

http://www-01.ibm.com/support/docview.wss?uid=swg21328735