Introduction

IBM Tivoli Monitoring v6 can hold agent bundles in a depot for remote deployment and remote upgrade procedures. This depot must be maintained via CLI commands. New agent bundles can be imported and old agent bundles can be removed. It is possible to list the content of the depot but the output is often overloaded and cryptic. This java script provides a GUI based tool to maintain the agent depot on the Tivoli Enterprise Management Server. Behind the scene depotmanager uses tacmd command to add/remove bundles.

License

Depotmanager is licensed under GPL3

Requirements

Actual version

1.6.4

JRE

The tool is written in java and requires a Java Runtime Environment 1.5 or higher. Now additional library (nativ or java) are nessesary.

Platform support

Supported on all platforms that can install a JRE 1.5+ Running the tool on a UNIX/Linux system requires a configured and running X-Server.

Environment variables

The Depotmanager

Properties file

A properties file .DepotManager.properties will be created in users HOME directory running the first time. It can be pre-created and the content can be edited.

#DepotManager
#Thu Sep 24 18:51:42 CEST 2009
SOURCE=/mnt/hgfs/ITM622GA/6.2.2.0-TIV-ITM_TMV-Agents
depot=/opt/IBM/ITM/tables/hub_rhel5/depot/PACKAGES

Start

Start the tool by calling the jar file with the java compiler.

java -jar ./Depotmanager.jar

A wrapper script can be used to set the correct JAVA_HOME and CANDLEHOME.

The GUI

Browse for your ITM depot by clicking at 'open folder' or type in the path to the depot. Once the depot is selected you can click at 'Scan depot' to scan the whole depot.

The content is sorted by product code 'PC'. Selecting on content the dependencies will be displayed in several colors.

Import bundles

Click 'Tools' and choose 'Import'. Browse for you image sources where to take bundles from.

Click 'Scan source' to scan the source. You can select now the bundles and platforms you plan to import and press 'Import selected'.

Delete bundles

To remove bundles from your depot select the appropriated product code and press 'Delete selected'. If this bundle has dependencies it will be show coloured.

Search outdated

This options searches for agent bundles with more than one release in the depot. It is useful to remove no longer required versions of a product bundle.

Export bundles

You can extract product bundles to create small image instead of needing the huge ITM Agent source bundle. This option creates a local directory structure of your selected product code.

Logging

For setup logging you have to configure the standard jre logging API. Create a logging.properties file like example below.

handlers= java.util.logging.FileHandler,java.util.logging.ConsoleHandler
.level= INFO

java.util.logging.ConsoleHandler.level = ALL
java.util.logging.ConsoleHandler.formatter = cli.logging.LineFormatter

# Log all to file (max 100kB, 5x rotate-generations)
java.util.logging.FileHandler.level=ALL
java.util.logging.FileHandler.formatter = cli.logging.LineFormatter
java.util.logging.FileHandler.pattern=depotmanager-%g.log
java.util.logging.FileHandler.limit =100000
java.util.logging.FileHandler.count=5
java.util.logging.FileHandler.append=true

To enable this configuration to all user, add the properties file to the depotmanager startup script.

java -Djava.util.logging.config.file=logging.properties -jar ./Depotmanager.jar

To enable this logging configuration only to one user add a logging property to users .Depotmanager.properies in users home directory.

# User depend logging
Logging=C\:\\Lokale Daten\\Thomas.weidlich\\workspace\\DepotManager\\logging.properties

Document Revision History