Tivoli Monitoring 5.1

Tivoli Monitoring 5.1 has an interesting extensible architecture which uses JavaScript as an extension language. Despite this advantage this is a typical IBM-style extremely over-engineered solution: too complex to be useful.

ITM used the Rhino JavaScript engine, so probes should be written in JavaScript with ITM API.

The default functionality of Tivoli monitoring is extremely primitive (functionality of provided file and security modules looks like shareware) and you need to learn Monitoring Resource Model Builder to extend it. The latter requires custom JavaScript modules, which are executed via Rhino JavaScript engine. The idea of extending application using JavaScript engine is a rather elegant architectural idea but proof of the pudding is in the eating and the way IBM did it was not well accepted in the marketplace. It's sad that it was executed IBM so badly (the Model Builder Debugger that was badly necessary was added much later) that it was later discarded it in favor of Omegamon (aka ITM 6.1) which paradoxically is a more closed, less flexible application with a very nice GUI not not much else.

Tivoli monitoring WEB site is a regular large corporation mess ;-). The list to ITM documentation is difficult to find and the correct link is (or was ;-) Tivoli - Support - Information Center. The format of the publications is PDF, HTML, or both.

The list of fixpacks can be found at Support (click on Download (Fixes, Patches) and click on Submit button, after that select the latest by date.

The following guides are available in the IBM Tivoli Monitoring Resource Model Builder library:

• IBM Tivoli Monitoring Resource Model Builder User's Guide, SC32-1391-00 Describes how to install and configure IBM Tivoli Monitoring Resource Model Builder.

• IBM Tivoli Monitoring Resource Model Builder ReadMe First, SC32-1390-00 Describes the location for the IBM Tivoli Monitoring Resource Model Builder documents.

• IBM Tivoli Monitoring Resource Model Builder Problem Determination Guide, SC32-1392-00 Provides the latest information about known product limitations and workarounds.

NEWS CONTENTS

• 20110117 : Manipulating ITM Tmw2kProfiles using the CLI ( Orb Data )
• 20090414 : IBM Tivoli Monitoring 5.1.2, fix pack 16, 5.1.2-TIV-ITM-FP16 ( IBM Tivoli Monitoring 5.1.2, fix pack 16, 5.1.2-TIV-ITM-FP16, Apr 14, 2009 )
• 20090414 : alphaWorks Resource Model Builder Debugger for UNIX Overview ( alphaWorks Resource Model Builder Debugger for UNIX Overview, )
• 20090414 : ITM Resource Model Creation: Putting Tivoli Monitoring to work for you ( ITM Resource Model Creation: Putting Tivoli Monitoring to work for you, )

Old News

[Jan 17, 2011] Manipulating ITM Tmw2kProfiles using the CLI

Orb Data

The most basic command is the -list option, which will display the resource models that are contained in the Tmw2kProfile. The output from this command will also show if the resource model is currently enabled or not.

For example, to list the resource models that are defined in the Tmw2kprofile 'base.os.linux.itm';

$ wdmeditprf -P base.os.linux.itm -list

Resource Model Enable

DMXCpu YES
DMXFileSystem YES
DMXMemory YES
DMXProcess YES

More detailed information about the components of a resource model are accessed by using the -print option along with one of the following sub-options [note that not all are list here];

-Tec This is equivalent to the Edit-->Properties menu option accessed in the Tmw2kProfile GUI via the desktop. It shows whether TEC events are enabled for this profile and if so, what the destination EventServer is.

-e This option displays the indication information, including the configured holes and occurrences and whether or not TEC or TBSM events should be generated.

-Log This options shows the logging configuration, whether it is enabled, the aggregation times etc

-par Use this option to display the parameters

-schedule This options displays any scheduling rules that are defined for this resource model

-t This option shows that thresholds that are defined

-c Use this option to display the cycle time information

The syntax to use these options is;

wdmeditprf -P <Tmw2kProfile> -print <ResourceModel> <sub option>

For example, to display the thresholds associated with the DMXCpu resource model;

$ wdmeditprf -P base.os.linux.itm -print DMXCpu -t

Thresholds:

Threshold Name Threshold Value

SysCPUTimeThr 80.000000
IdleCPUTimeThr 10.000000

To show the parameters defined for the Windows 'Parametric Services' resource model;

$ wdmeditprf -P base.os.win.itm -print TMW_ParamServices -par

Parameters:

services: Browser
EventLog
LanmanServer
LanmanWorkstation
lcfd
Netlogon
NtLmSsp

... ... ...

Examples

To display information about indications, including holes, occurrences, TEC events etc;

wdmeditprf -P <Tmw2kProfile> -print <ResourceModel> -e
wdmeditprf -P base.os.linux.itm -print DMXCpu -e

To alter the number of occurrences required for an indication to be triggered;

wdmeditprf -P <Tmw2kProfile> -edit <ResourceModel> -e <Indication> -o <occurrences>
wdmeditprf -P base.os.linux.itm -edit DMXCpu -e Low_IdleCPUUsage -o 15

To alter the number of holes allowed for an indication;

wdmeditprf -P <Tmw2kProfile> -edit <ResourceModel> -e <Indication> -o <occurrences>
wdmeditprf -P base.os.linux.itm -edit DMXCpu -e Low_IdleCPUUsage -o 15

To enable the sending of a TEC event for an indication;

wdmeditprf -P <Tmw2kProfile> -edit <ResourceModel> -e <Indication> -SendTec
wdmeditprf -P base.os.linux.itm -edit DMXCpu -e Low_IdleCPUUsage -SendTec

To change the severity of the TEC event for an indication;

wdmeditprf -P <Tmw2kProfile> -edit <ResourceModel> -e <Indication> -severity <TEC Severity>
wdmeditprf -P base.os.linux.itm -edit DMXCpu -e Low_IdleCPUUsage -severity CRITICAL

To disable the TEC event for an indiciation;

wdmeditprf -P <Tmw2kProfile> -edit <ResourceModel> -e <Indication> -NoSendTec
wdmeditprf -P base.os.linux.itm -edit DMXCpu -e Low_IdleCPUUsage -NoSendTec

To get the overall TEC configuration for the profile;

wdmeditprf -P <Tmw2kProfile> -print <ResourceModel> -Tec
wdmeditprf -P base.os.linux.itm -print DMXCpu -Tec

To configure the profile to send events to a TEC server;

wdmeditprf -P <Tmw2kProfile> -edit DMXCpu -Tec broadcast -S <EventServer>
wdmeditprf -P base.os.linux.itm -edit DMXCpu -Tec broadcast -S 192.168.1.100+5529 [Note non-TME events are used in this example]

To disable the sending of TEC events;

wdmeditprf -P <Tmw2kProfile> -edit DMXCpu -Tec no
wdmeditprf -P base.os.linux.itm -edit DMXCpu -Tec no

To add an additional parameter;

wdmeditprf -P <Tmw2kProfile> -edit <ResourceModel> -AddPar <Parameter> <Parameter Value>
wdmeditprf -P base.os.win.itm -edit TMW_ParamServices -AddPar services myservice

To delete a parameter;

wdmeditprf -P <Tmw2kProfile> -edit <ResourceModel> -DelPar <Parameter> <Parameter Value>
wdmeditprf -P base.os.win.itm -edit TMW_ParamServices -DelPar services myservice

To change a threshold;

wdmeditprf -P <Tmw2kProfile> -edit <ResourceModel> -t <Threshold> <Threshold Value>
wdmeditprf -P base.os.linux.itm -edit DMXCpu -t IdleCPUTimeThr 5

To enable RAW data logging;

wdmeditprf -P <Tmw2Profile> -edit <ResourceModel> -Log -LogEnable -RAW yes
wdmeditprf -P base.os.linux.itm -edit DMXCpu -Log -LogEnable -RAW yes

To change the amount of time for which historical data is retained (in this example setting it to 24 hours);

wdmeditprf -P <Tmw2Profile> -edit <ResourceModel> -Log -p 24:00
wdmeditprf -P base.os.linux.itm -edit DMXCpu -Log -p 24:00

To disable RAW data logging;

wdmeditprf -P <Tmw2Profile> -edit <ResourceModel> -Log -RAW no
wdmeditprf -P base.os.linux.itm -edit DMXCpu -Log -RAW no

To enable TEDW data logging;

wdmeditprf -P <Tmw2Profile> -edit <ResourceModel> -Log -LogEnable -TEDW yes
wdmeditprf -P base.os.linux.itm -edit DMXCpu -Log -LogEnable -TEDW yes

To disable all logging;

wdmeditprf -P <Tmw2Profile> -edit <ResourceModel> -Log -LogDisable
wdmeditprf -P base.os.linux.itm -edit DMXCpu -Log -LogDisable

[Apr 14, 2009] IBM Tivoli Monitoring 5.1.2, fix pack 16, 5.1.2-TIV-ITM-FP16

Readme Date: December 19, 2008

Section 6.2. Installation procedure
-------------------------------------------------------------
Installing the fix pack is an 10-step process:
1) Extract the fix pack.
2) [Optional] Apply the fix pack on the Warehouse Enablement Packs AMX and AMY.
3) Apply the fix pack.
4) Run the commands:
odadmin shutdown <disp>

wbbackup

odadmin start <disp>

where disp is related to the managed node just upgraded.

5) Optionally, install the resource models not selected during step 3

6) Update the active rulebase(s) used by TEC eventserver(s).

7) Update the binaries and the resource models on the endpoint.

8) Update the IBM Tivoli Monitoring Database

9) Promote the ETL processes to "production".

10) Update the Web Health Console resource models catalogs

*********************************************************************

1) To extract the fix pack, perform the following steps:

On a UNIX system:

Extract the content of the 5.1.2-TIV-ITM-FP16.tar file into a temporary directory:
# cd $PATCH
# tar xvf 5.1.2-TIV-ITM-FP16.tar

where:
- $PATCH is the temporary directory

1A) The untarred file builds the following directory structure:

- This README file named README

- 5.1.2-TIV-ITM-FP16, containing the images for English version. Its structure is:
5.1.2-TIV-ITM-FP16
- CFG
- .ind files
- .pkt files
- patches.lst file
- image_report file

- directory tedw_apps_etl, containing ETLs tedw_apps_etl
AMX containing the Warehouse Enablement Packs (a.k.a. Generic ETL1)
AMY containing the Warehouse Enablement Packs (for the Operating System resource models)

- directory RMB, containing the source of resource models in RMB 1.1.3 format.
Its structure is:
RMB
Samples
OS400 all .jrm files for OS400 platform
UNIX all .jrm files for UNIX platform
Windows all .vrm files for Windows platform
Generic all .jrm files for all the supported platform.

- directory WHC_Resources, contains the ITM_resources.jar for the resource models catalogs needed by Web Health Console.

- directory ITMWHC. It contains the Web Health Console package.

- directory Tools. It contains the suggested JREs.

2) Apply the fix pack on the Warehouse Enablement Packs AMX and AMY.

If the following steps have not been already run during the installation of the AMX/AMY components in
IBM Tivoli Monitoring 5.1.2 Fix Pack 03 or
IBM Tivoli Monitoring 5.1.2 Fix Pack 04,
you are required to perform them now.
These steps are needed to guarantee a general environment health check.

a) From the DB2 Control Center, open the Data Warehouse Center application.
b) Select "Warehouse" on the left side of the Window
c) From the "Selected" menu, "Export Metadata" -> "Interchange file..". The "Export Metadata" window opens.
d) Click "Browse" to select the destination directory for the tag file produced with this operation.
e) Move all the "Available Objects" on the "Selected Objects"
side using the ">>" arrows
f) Select "OK" to start the export of the
selected DWC objects. This operation might take a while.
At the end a pop-up appears.

If the export operation is successful, proceed applying the fix pack. If the operation fails, contact the IBM Software Support before proceeding.

- 2.1 - Tivoli Enterprise Data Warehouse 1.1
Before installing the AMX or AMY fixpacks in a TEDW
distributed environment, you must ensure that TEDW001 and
TEDW002 nodes exist in the database node directory.
You also need to ensure that TWH_CDW is attached to the
node TEDW001 and TWH_MART is attached to the node
TEDW002.

If the nodes do not exist or if the databases are not attached to the correct nodes, the patch installation can fail during the running of the later scripts. For more information about how to check and
change the database nodes configuration, refer
to section 3.6 of the AMX enablement document,
located in the doc directory of the installation bundle.
To install the fix pack on Tivoli
Enterprise Data Warehouse, the Tivoli Enterprise Data
Warehouse 1.1 fix pack 3 (1.1-TDW-FP03) has to be
installed.
Before installing this fix pack, it is highly recommended
to make backup copies of:
- the three Tivoli Enterprise Data Warehouse databases
(TWH_CDW, TWH_MD and TWH_MART);
- a backup of the %TWH_TOPDIR%\apps and
%TWH_TOPDIR%\apps_backup directories;
- export the tables AMY.F_MEMORY_HOUR, AMY.F_MEMORY_DAY,
AMY.F_MEMORY_WEEK, AMY.F_MEMORY_MOUNTH from TWH_MART
database in ifx files running the command:
db2 export to <filename.ixf> of ixf
"select * from <table name>"

To apply this patch, follow these instructions:

a) Before applying the fix pack on the Tivoli Enterprise
Data Warehouse you must demote to 'development' all the
processes belonging to the AMX and AMY warehouse
enablement packs.
You must also check if a twh_app_patcher.cfg
configuration file was left in the %TEMP% directory by
some previous fix pack installation and remove it,
before moving to the next point b).

b) Run %TWH_TOPDIR%\install\bin\tedw_wpack_patchadm.sh in
a bash shell to create the twh_app_patcher.cfg
configuration file into the %TEMP% directory. If this
file already exists, it will be used to get the
required configuration info, so, ensure that
it is applicable to the current Tivoli Enterprise
Data Warehouse environment before running the
tedw_wpack_patchadm.sh installation script.

c) Edit the %TEMP%\twh_app_patcher.cfg configuration file
to complete the "USER SUPPLIED SECTION" section.
The "APP_MEDIA_DIR" must refer to the directory of the
Fix Pack bundle where the twh_install_props.cfg is
located.
For this fix pack the APP_MEDIA_DIR must refer to the
%PATCH%\tedw_apps_etl\AMX directory.

d) Run the tedw_wpack_patchadm.sh script again to complete
the installation of the AMX component.

e) Edit the %TEMP%\twh_app_patcher.cfg configuration file
to complete the "USER SUPPLIED SECTION" section.
The "APP_MEDIA_DIR" must refer to the directory in the
fix pack bundle where the twh_install_props.cfg is
located.
For this fix pack the APP_MEDIA_DIR must refer to the
%PATCH%\tedw_apps_etl\AMY directory.

f) Run the tedw_wpack_patchadm.sh script again to complete
the installation of the AMY component

- 2.2 - Tivoli Data Warehouse 1.2 and 1.3 instructions.
To install the AMX and AMY fixpacks in a Tivoli Data
Warehouse 1.2 or 1.3 environment refer to: "Installing and
Configuring Tivoli Data Warehouse" -chapter 8- "Installing and
upgrading warehouse packs"

NOTE: To install the AMX or AMY fix pack
in a Tivoli Data Warehouse 1.3 environment,
1.3.0-TIV-TDW-LA0002 patch is required.

NOTE: After the installation of AMX component, it is
recommended that you ensure that the properties of
Warehouse Sources and Warehouse Targets are still
consistent.
In particular check that the User ID and Password
in the "Data Source" tab are correct.

NOTE: Keep the processes in the "development" state
until the new indexes are created in the ITM_DB.
See Tivoli Enterprise Data Warehouse documentation
for details regarding how to demote the processes.

*********************** IMPORTANT NOTICE ************************
In order to improve AMX performance, some DB2 administrative
operations are needed to update statistics of new tables and
indexes introduced with this fix pack.
When these operations are not performed, AMX takes a long time
to run. We strongly suggest performing the following procedure
between the amx_c05_s20_parsing and amx_c05_s30_exception steps.
If for any reason these operations are not performed during the
first AMX run, it is extremely important to issue them after AMX
has completed.

Issue the following commands from a DB CLP:

1) db2 connect to twh_cdw user <...> using <...>
2) db2 runstats on table amx.stage_metricsdata with distribution
and indexes all
3) db2 runstats on table amx.stage_inst_no_ex with distribution
and indexes all
4) db2 runstats on table amx.met_no_ex with distribution and
indexes all
5) db2 runstats on table amx.stage_metrics with distribution and
indexes all
6) db2 terminate
*****************************************************************

3) Apply the fix pack

To apply this fix pack in your environment, install it on the TMR Server first, and then on all the Managed Nodes that you want to upgrade. If you cannot upgrade all the Managed Nodes at the same time and you need to install the fix pack on one Managed Node at a time, you need to:
- install the fix pack on the identified Managed Node (refer to steps 3-4).
- upgrade the related endpoints (refer to step 7).
After doing so, you can use the upgraded endpoints, but you cannot work with the endpoints related to
the Managed Nodes that have not been upgraded, yet.

Note: To install this fix pack, you must have both the install_product and super authorization roles.

The installation of the components can be performed in ONE of the following ways:
3B) From the Tivoli desktop
3C) With the wpatch CLI

3B) To apply the fix pack from the Tivoli desktop, perform the following steps:

a) Select Install -> Install Patch from the Desktop menu, to display the Install Patch dialog.

b) Click Select Media to display the File Browser dialog.

c) In the Path Name field, type the path to the directory that contains the fix pack.

d) Click Set Media & Close to return to the Install Patch dialog. The patch install list now contains the names of the fix pack components to be installed:
o IBM Tivoli Monitoring, Version 5.1.2 - Fix Pack 16
o IBM Tivoli Monitoring - Tivoli Enterprise Data Warehouse Support, Version 5.1.2 - Fix Pack 16
o IBM Tivoli Monitoring - Gathering Historical Data Component 5.1.2 - Fix Pack 16

e) Select the "IBM Tivoli Monitoring, Version 5.1.2.- Fix Pack 16" component from the list. This is a prerequisite step to install the components below.

f) This fix pack stores and installs several operating system resource models. The installation of these resource models in the TMR database and the update of old profiles may take a while. You can install all or some of these resource models during the installation, or at a later time, after the installation is complete.

To defer the installation of some resource models, use the script 'createDefResModel.init', located in the $BINDIR/TME/Tmw2k directory. Run this script manually to upgrade all the modified resource models.

A dialog opens, asking which resource models you want to install.
The available options are:

All All resource models are installed in the TMR database and the old profiles (which include these resource models) are updated. This is the default.

None All resource models are loaded. Installation is deferred until the script createDefResModel.init is launched

Custom only the specified resource models are installed. The installation of the other resource models is
deferred until the script createDefResModel.init is launched.

If you select the Custom option, you must type the list of resource models, separated by blanks, in the text field
displayed in the option panel.

Warning: On Windows based TMR it is recommended that you choose "None" option because of an issue that has been seen in some Windows environment where the wtll command does not complete causing the installation to fail.

g) Select the managed nodes on which to install the fix pack.

h) Click Install.

i) Select the IBM Tivoli Monitoring - Tivoli Enterprise Data Warehouse Support, Version 5.1.2 - Fix Pack 16 component from the list. This is an optional step that you need to perform if you have previously installed IBM Tivoli Monitoring - Tivoli Enterprise Data Warehouse Support, Version 5.1.2 and you want to upgrade it to Fix Pack 16 level.

j) Select the managed nodes on which to install the fix pack.

k) Click Install.

l) Select IBM Tivoli Monitoring - Gathering Historical Data Component 5.1.2 - Fix Pack 16 from the list. This is an optional step that you need to perform if you have installed IBM Tivoli Monitoring - Gathering Historical Data Component 5.1.2 and you want to upgrade it to Fix Pack 16 level.

m) Select the managed nodes on which you want to install the fix pack.

n) Click Install.

3C) Each component can be installed via command line with the command wpatch, as follows:

wpatch -c <IMAGE_DIR> -i 512ITM16.IND [NODE1 NODE2 ...]

where IMAGE_DIR is the path to the directory that contains the fix pack images.
NODE1 NODE2 ... are the managed nodes where the fix pack is
installed; if no node is specified, the fix pack will be
installed on all managed nodes of the TMR.

wpatch -c <IMAGE_DIR> -i 512ITM16.IND [NODE1 NODE2 ...]

This installs the main component, "IBM Tivoli Monitoring, Version 5.1.2.- Fix Pack 16" wpatch can use installation variables to set the options for resource models conditional installation. In particular, you can use the following two installation variables:

@UPD@ that can have the value All, None, or Custom. It specifies the resource model installation option. If this variable is not used, or if it has a different value from those specified here, the default value of All is used.

@RMS@ that should have a custom list of resource models if Custom Option is selected. Otherwise this variable is ignored.

wpatch -c <IMAGE_DIR> -i 512TED16.IND [NODE1 NODE2 ...]

This installs the data warehouse component, "IBM Tivoli Monitoring - Tivoli Enterprise Data Warehouse Support, Version 5.1.2 - Fix Pack 16"

wpatch -c <IMAGE_DIR> -i 512TD16.IND [NODE1 NODE2 ...]

This installs the Tivoli Decision Support component, "IBM Tivoli Monitoring - Gathering Historical Data Component 5.1.2 - Fix Pack 16"

4) Run the command:
odadmin shutdown <disp>
odadmin start <disp>

where disp is related to the managed node just upgraded.

5) Optionally, install the resource models not selected during step 3

You need to perform it if both cases below apply:
- when you installed the fix pack, you chose to upgrade all the
resource models later (selecting the option None) or to
upgrade only a subset of them (selecting the option Custom)
- you want to use the updated resource models shipped with
this fix pack
If both of the previous cases apply, you need to install the
resource models.

This operation can be accomplished:
- automatically, running the createDefResModel.init script.
The script will load the resource models not already installed.
The script can be found in the directory
$BINDIR/TME/Tmw2k
- manually, running the command wdmrm -add <resource_model_name> for each resource model that you want to install.

If, instead, you want to use the old version of the resource models, you do not need to perform this step.
Later, if you want to use the updated resource models shipped with this fix pack, you will need to perform this step and upgrade the resource models on the endpoints.

6) Update the active rulebase(s) used by TEC eventserver(s).

Note that the baroc file must be installed (imported and compiled and loaded) before upgrading any IBM Tivoli Monitoring engine. This step can be accomplished in three different ways, as described below.
I

f you are using any other rulebase whose events inherit from TMW_event base class, it is strongly recommended that you re-create the rulebase with the same process used for its original creation.

Note that all the products in the "IBM Tivoli Monitoring for" family from version 5.1 define events inherited from TMW_Event base class and thus require that the rulebase is recreated.

It is recommended to save the old rulebase by creating a new rulebase and copying the old active rulebase contents before proceeding.

Refresh of all the IBM Tivoli Monitoring baroc files can be
accomplished in one of the following ways:

i) Run the task DMCreateRuleAndLoadBaroc from task library "IBM Tivoli Monitoring Tasks".
The task needs the following specifications:
- Rulebase name (if a rulebase with this name does not exist it will be created)
- Restart TEC Server option (valid values are true/false and default is set to true)
- TEC version specification: you need to select if you are using TEC 3.7 version or higher (default is set to 3.7
version or higher)

This task needs to be run on each managed node on which TEC Server is installed.
NOTE: It is possible that the timeout value for this task needs to be increased to run it successfully, accordingly to the environment you are working on.

A suitable value could be 1800 which can be set using -m option (-m 1800) if command wruntask is used, or
setting the field "Timeout" to 1800 in the GUI panel.

ii) Using the script dmae_tec_inst.sh provided with the installation. In this case the usage will be:
dmae_tec_inst.sh <rulebase> [-restartsvr] [-362]

iii) Manually upgrade the rule base using the TEC commands. In particular, this is the sequence of commands in case rulebase was populated using dmae_tec_inst.sh and in case they are issued from $BINDIR/TMNT_TEC:

wrb -delrbclass DMXCpu.baroc -force <rulebase>
wrb -delrbclass GenericScript.baroc -force <rulebase>
wrb -imprbclass DMXCpu.baroc -after Tmw2k.baroc <rulebase>
wrb -imprbclass GenericScript.baroc -after Tmw2k.baroc <rulebase>

This is an example and all the baroc files changed from the previous installation have to be manually added.
Refer to the resource model changes matrix, to have the list of all the resource model baroc changed, and add also the heartbeat baroc since it has been changed with this fix pack.

After these steps are completed, rulebase can be loaded and made active.

7) Update the binaries and the resource models on the endpoint.

This can be accomplished in the following way:

A) Automatically, running the command wdmcmddistrib with the option -upgrade. Refer to the User's Guide for more details on the command and how to use it.

B) Manually, performing the following two steps (use this method if you have problems with the endpoints):
B1) Stop the engine, to unlock the binaries and libraries on the endpoint, running the command:
wdmcmd -stop {-p <profile_manager#region> | -e <endpoint>}

B2) Redistribute all profiles that contain updated resource models (this will restart the engine,and update the
resource models on the endpoint, downloading the new binaries using the dependencies mechanism).
Note: If you are using resource models with translated messages, issue the "wdmrm -addcat" command to
add language packs to the message catalogs.

8) Update the IBM Tivoli Monitoring Database

In order to improve RIMHandler and ETLs performance, some RIM database schema changes are required

From the Tivoli environment, move to the $BINDIR/TME/Tmw2k/WarehouseCfg directory and run the
up_itm_db.sh wrapper script.

This will ask you all the information required to connect to the IBM Tivoli Monitoring Database and runs all the required updates to the schema.

NOTE: if you are using DB2, the DB2 environment needs to be defined before exporting the Tivoli environment and running the up_itm_db.sh wrapper script.

9) Promote the ETL processes to "production".

10) If you are using the Web Health Console, you need to replace the ITM_resources.jar in the Web Health Console installation directory (see point 1A of this section). After that you need to restart the Web Server to make the changes effective.

#######################################################################
# Section 7. Known Problems and limitations #
#######################################################################

1) If a wdmcmddistrib -upgrade command is issued towards an endpoint that was using the DMXSpp (or TMW_Spp) resource model as part of a custom profile, the resource model is not updated on the endpoint and a java.lang.NumberFormatException is written to the trace.

This is not an actual error situation because instead of using
custom profiles, you should always distribute these resource
models using the corresponding profiles (SPR_UNIXProfile on UNIX,
and SPR_NtProfile on Windows).
To bypass the specific error situation, add the resource model
manually to the custom profile before issuing the
wdmcmddistrib -upgrade command.

2) When deleting an existing resource model and adding a resource model of the same name (to change the default parameters, thresholds, or some other reason) through wdmrm -add/remove, it is important that ALL Monitoring profile windows from the Desktop GUI are closed.

When adding the resource model to the profile, a copy of the old resource model will be added rather than the updated resource model.

The reason for this behavior is that when a Monitoring profile window is open, all resource Models are loaded into memory.
While the wdmrm -add/remove commands make the necessary changes on the disk, the resource models remain loaded in memory until the Monitoring profile windows are closed.

3) DMXSpp does not support Linux-ppc endpoints. Linux-ppc endpoints are 64-bit and DMXSpp targets 32-bit platforms.

stribution of
profiles will complete successfully.

7) Currently IBM Tivoli Monitoring does not provide the Usage signature to IBM Tivoli License Manager for all
the PACs leveraging IBM Tivoli Monitoring on native (non-Java) Windows engine.

10) If you have IBM Tivoli Monitoring 5.1.2 0059 installed, the libraries for the ILTs are updated but the class files are not.

11) If you have installed Framework 4.1.1 FP04 on Linux platforms, the IBM Tivoli Monitoring 5.1.2 Fix Pack 9 installation could fail. Problem addressed by the Framework APAR IY77095.

12) DMXSpp does not support Solaris Intel endpoints.

alphaWorks Resource Model Builder Debugger for UNIX Overview

What is Resource Model Builder Debugger for UNIX?

Resource Model Builder Debugger for UNIX® allows graphical debugging of the JavaScript^TM decision tree in IBM Tivoli Monitoring (ITM) resource models on Linux® and UNIX. This tool provides full debugging capabilities, such as setting break points and inspecting the value of a variable. It uses the graphical debugger supplied by the Rhino JavaScript interpreter shipped with ITM.

There are two ways to debug resource models:

• debugging graphically through debug_jscript.sh
• running the resource model from the CLI via debug_jscript_cli.sh

How does it work?

ITM Resource Models for UNIX are based on a JavaScript decision tree. ITM is shipped with the Rhino JavaScript engine for running these decision tree scripts. When ITM runs, it uses Rhino to control the execution of each resource model's decision tree.

One component of the Rhino JavaScript engine is a graphical debugger written with Java's Swing. The Resource Model Builder Debugger for UNIX provides a harness for launching a resource model in Rhino's graphical debugger rather than in the normal ITM process. This allows a user to run a single resource model and step through the JavaScript code.

The Resource Model Builder Debugger for UNIX also comes with a tool that can run a resource model from the command line. This tool has been used to run resource models in a single isolated process, which has proven to be one method for discovering memory leaks in a resource model's data provider.

Also see the developerWorks tutorial: Debug IBM Tivoli Monitoring UNIX resource models - Using the Resource Model Builder Debugger for UNIX.

alphaWorks Tivoli Monitoring Resource Model Builder Overview Tivoli Monitoring Resource Model Builder has graduated!

At the end of April 2003, the IBM Tivoli Resource Model Builder was made generally available as a complimentary download at the Tivoli Resource Center's Web site.

IBM Tivoli Monitoring V5.1.1 Implementation Certification Study Guide, SG24-6780-00
Redbook, published 25 May 2005

Fix Pack (5.1.2-ITM-FP04) for IBM Tivoli Monitoring 5.1.2Fix Pack (5.1.2-ITM-FP04) for IBM Tivoli Monitoring 5.1.2

ITM Resource Model Creation: Putting Tivoli Monitoring to work for you

Free tutorial

IBM Tivoli Monitoring (ITM) is a powerful environment that gives you the ability to monitor virtually any type of resource. This tutorial shows you how easily you can build custom monitoring capabilities into ITM using the ITM Resource Model Builder. Resource Models provide a structured environment to provide resource status analysis, notification of significant events, and even automatic corrective measures. ITM Resource Model Builder is an IDE that simplifies the process of creating and debugging Resource Models.

freshmeat.net Project details for Resource Model Builder Debugger

http://www.alphaworks.ibm.com/[..]S_CMP=GR&ca=dgr-lnxd01awrmbdebugger4unix

Procedures

Creating resource models using IBM Tivoli Monitoring Resource Model Builder, Version 1.2.0

To create customized resource models using the IBM Tivoli Monitoring for Messaging and Collaboration: Microsoft Exchange Server CIM classes and a resource model wizard to guide you through the process.

Background information

The resource model wizard guides you through the process of creating resource models using the IBM Tivoli Monitoring for Messaging and Collaboration: Microsoft Exchange Server CIM classes. For more information about creating resource models, refer to the IBM Tivoli Monitoring Resource Model Builder User's Guide.

Required authorization role

None

Before you begin

Before you begin, you must perform the following steps:

1. For Windows NT systems, install and configure Windows Management Instrumentation. For Windows 2000 and Windows XP systems, this step is unnecessary.

   Additional Information: You can download Windows Management Instrumentation from http://msdn.microsoft.com/downloads/.

2. Install IBM Tivoli Monitoring Resource Model Builder.

After you finish

Refer to the IBM Tivoli Monitoring Resource Model Builder documentation for additional information on how to build and deploy your new resource model.

Procedure

1. Open IBM Tivoli Monitoring Resource Model Builder.
2. Click File -> New.
3. Click Basic Resource Model Wizard to launch the wizard and display the scripting language and operating system window.
4. Select one of the following scripting languages:
   • VBA Script Resource Models (Windows only): Limits the operating system type to w32-ix86 (Windows) only.
   • JavaScript Resource Model (all platforms): Enables the resource model to run on all operating systems.
5. If you are creating a JavaScript resource model, select w32-ix86 for the platform.
6. Click Next to open the Datasource Selection Page window.
7. Click CIM/WMI Datasource to open the CIM Data Source Wizard window.
8. Type ROOT\CIMV2 in the Namespace text box.

   Additional Information: ROOT\CIMV2 is the destination that stores the CIM classes.

9. Click the lightning icon to connect to the namespace.

   Additional Information: If you are connected to the namespace, you are not prompted to type your user name and password, if the current ones are valid. If you are prompted with the Logon window, do the following:

   1. Type your user name and password.
   2. Click Logon to connect to the namespace.
10. Install the CIM classes from the CIM Data Source Wizard by following these steps:
    • Click Mof Compiler to display the WMI MOF Compiler Wizard.
    • Select Compile a .MOF file.
    • Click Go.
    • Type the path and file name for your .MOF file in the Path and file name for .MOF file text box.

      Additional Information: Click Browse to search for your MOF files.

    • Click Finish.
    • Repeat step 11 for each .MOF file that you want to install.
    • Click Finish.
11. Select a CIM class.

    Additional Information: The left field displays all available CIM classes for use in your custom resource models. For information about the CIM classes, see Data providers.

12. Click Next to display the Select Properties window.
13. Select one or more CIM class properties to monitor from the Available Properties table.
14. Move the properties to the Selected Properties table by clicking the right arrow icon.
15. Click Next.
16. Follow the Resource Model Wizard instructions to complete your resource model. See IBM Tivoli Monitoring Resource Model Builder documentation for detailed instructions.
17. After the wizard is complete, add the CIM classes as platform-specific dependencies to the resource model by following these steps:
    1. In the IBM Tivoli Monitoring Resource Model Builder window, open the Management view containing the decision tree for your new resource model.
    2. In the decision tree on the left side of the window, click "+" to expand the tree list for the newly created resource model.
    3. Click Dependencies to display the Dependencies Editor page.
    4. Click Add to display the Dependencies window.
    5. Browse to the product installation CD.
    6. Click w32-ix86.
    7. Click OK to add the classes to the Dependencies page

Articles

[09-26-03] IBM Tivoli Monitoring Resource Model Builder

Provides a standard Eclipse interface to a simple step-by-step wizard to build resource models. Your development organization can leverage its core competencies to easily specify Automated Best Practices for monitoring and automatic curing for your IT systems, right out of the box.

IBM Tivoli Monitoring (ITM) is a powerful environment that gives you the ability to monitor virtually any type of resource. This tutorial shows you how easily you can build custom monitoring capabilities into ITM using the ITM Resource Model Builder. Resource Models provide a structured environment to provide resource status analysis, notification of significant events, and even automatic corrective measures. ITM Resource Model Builder is an IDE that simplifies the process of creating and debugging Resource Models.

Red Books

IBM Redbooks IBM Tivoli Monitoring V5.1.1 Implementation Certification Study Guide

This IBM Redbook prepares you with the necessary knowledge to help you complete Certification Test 593: IBM Tivoli Monitoring V5.1.1 Implementation . This test leads to certification for Tivoli Certified Deployment Professional for IBM Tivoli Monitoring.

The scope of the certification tests your ability to demonstrate the following areas of expertise required for IBM Tivoli Monitoring V5.1.1:

• Prerequisite knowledge for IBM Tivoli Monitoring
  
• Planning the implementation
  
• Installation prerequisites
  
• The installation process
  
• Configuration of the IBM Tivoli Monitoring server
  
• Problem determination
  
• General operations
  
• IBM Tivoli Monitoring Workbench
  

You can find the information that you need about these topics all in this IBM Redbook. Plus, you have a chance to test your knowledge using the sample questions at the back of the book.

IBM Redbooks IBM Tivoli Monitoring Version 5.1.1 Creating Resource Models and Providers

This IBM Redbook focuses on using the IBM Tivoli Monitoring Workbench to build resource models (RMs) that use existing ILT providers and custom ILT Java providers. You will learn how to create a custom ILT provider using the supplied Java templates to examine and provide data to ITM for analysis within the resource model that you created through the ITM Workbench. The ITM Workbench is used for developing, debugging, and packaging resource models for IBM Tivoli Monitoring. You will learn how to use the step-by-step wizards provided by the ITM Workbench to create RMs to monitor any number of your IT resources, including operating systems, databases, hardware, and networking resources and applications. In addition, you will learn about the Common Information Model (CIM) used to store metrics and how to collect data stored in a CIM format. Upon completion, you will be able to create, test, and deploy monitoring solutions quickly and efficiently in order to create an autonomic environment.

Tivoli - Support - Information Center - documentation