Browse Prior Art Database

Autonomic model for a simple computers's network sanity control Disclosure Number: IPCOM000026708D
Original Publication Date: 2004-Apr-06
Included in the Prior Art Database: 2004-Apr-06
Document File: 7 page(s) / 134K

Publishing Venue



The article describes a possible solution to automate the ITM Fix Packs installation. Not the installation operation per se, but all activities that should be performed by the user after FP had been installed, such: stop/start of all processes running on the TMR Servers/Managed Node, stop/start of the engine running on each endpoint and re-distribution of the resource model.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 47% of the total text.

Page 1 of 7

Autonomic model for a simple computers's network sanity

Disclosed is a description of how all ITM Fix Pack post installation operations may be automated.

The "State of the art" describes the actual status, while "What we can do" describes a porposal of a tool. The "Tool Specifics" give an example on how the tool can be developed.

Achronism Used:

FP: Fix Pack ITM: Ibm Tivoli Monitoring RM: Resource Model

State of the art

    After FP installation customers need to perform lot of operation on the various systems involved:

A. Server Side Operations:

    On all the MNs/Gateways on which the FP has been installed all ITM server side processes should be recycled:
i. tmnt_rm_eng
ii. tmnt_hb_eng
iii. tmnt_datacolector_eng
iv. tmnt_tbsm_eng
v. tmnt_task_eng
vi. tmnt_gw_eng

B. Endpoint Side Operations:

This consists of actually two sub operations:

    Engine Deployment, Resource Model Deployment for the newly shipped resource model
a. Engine Depolyment

    All endpoints that run ITM engine should be stopped and restarted to deploy the new version of the engine on them
b. Resource Model Deployment

    The FP may have fixed problem on resource models. So a new version is provided with installation. The new RM would be upgraded on the TMR server database and all Tmw2kProfile that have loaded it.

    It is needed to distribute those updated profiles to the endpoints that were running them.


Page 2 of 7

What we can do

    A tool can be provided to automate the operations describes in terms of identifying the "Objects" involved and in term of "automate actions" to be performed.

The tool should provide a way for the customer to:
1. have a list of all Managed Nodes (TMR Server included) on which the FP has been installed
2. have a list of endpoint attached to those gateways on which FP has been already installed and that run ITM
3. have a list of all Tmw2kProfile that have been changed with the new version of RM and the endpoint to which re-distribute them
4. perform the necessary actions to complete the installation:
b. stop / start of all ITM server side processes running on the MNs/Gateways:
c. stop / start the ITM engine on all endpoints that run ITM engine to upgrade to the new version
d. distribute all profiles with the new RMs version to the endpoints running them

    "Tivoli Rapid Deployment" already provides a way to deploy Framework and ITM. However, the tool presented here would come into play in an already installed environment and only after installation of fix pack to help a customer to complete the fix pack deployment. The tool is more oriented in offering the customer a way to automate all those actions that are necessary to complete the deployment of an ITM fix pack (or release eventually). At the moment each customer needs to either implement his own automation way to do this or to perform such operations manually.

Tool specifics

The tool can be seen as a two-phases operation:

"Discovery" phase

"Action Planning and Automate Deploy" phase

They will need to be run ea...