Browse Prior Art Database

Shareable Software Package Management Disclosure Number: IPCOM000128874D
Original Publication Date: 2005-Sep-20
Included in the Prior Art Database: 2005-Sep-20
Document File: 4 page(s) / 83K

Publishing Venue



The purpuse of this disclosure is to provide a mechanism leveraging the ITCM Software Package handling method to face with installation, upgrade and uninstallation of Software Packages containing code for Common Components that have to be shared among several exploiters installed on the same box.

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 52% of the total text.

Page 1 of 4

Shareable Software Package Management


     Componentization in software requires great attention to installation/deployment, upgrade and compatibility issues among components and exploiting products. In particular, if a component has to be shared by different exploiting products, a mechanism must be implemented so to avoid multiple installation of it, which are useless and may even conflict with each other.

     Such a mechanism is, at the present state, defined and implemented by the component installation, with a great amount of overhead due, for example, to discovery of previous installations, parameters management etc. Then, exploiting products must be aware of this mechanism in order to perform their own installation correctly. So, both the component and the product installation are affected by this issue.

     The purpose of this document is to propose a new mechanism that allows using a component, that is installed through IBM Tivoli Configuration Manager "Software Installation Engine" (SIE), without caring about who and how many exploiters are sharing it on the same box.

The proposed mechanism

   This mechanism leverages a new attribute for the software package and some modifications to the current SIE to handle this attribute. By means of this system a component package may be encapsulated in a product package and, at installation/uninstallation time of the latter, the operation performed on the former depends on its presence and state on the target machine. Neither the component nor the product shall worry about the coexistence problem.

     A new software package attribute, which will be referred to as " shareable", is added. Coupled with this, another attribute is added, " share_counter", which will be hidden to the user. The purpose of the first attribute is to declare that the contents of package can be shared by different exploiting products; the second will be internally used by the SIE to maintain a count of the products that are exploiting the shareable package.

     If an exploiting product wanted to use the shared package, instead of using it as is, it should embed it into a new software package created on purpose. Let us call it "exploiting" package. This way, the resulting exploiting package has its own name/version attributes along with the name/version of the embedded shareable package making the exploiting package only being used for a logical registration on the Endpoint catalog, and for managing installation/uninstallation of the shareable package in case of necessity.

     The share_counter attribute will be used to manage installation and uninstallation of different exploiting packages sharing the same shareable


Page 2 of 4

package. See figure below for a pictorial description of relationship between the two packages.

     When the exploiting package gets installed, after the usual checks, the following occurs:

i) If shareable package is not installed, it gets installed and registered in the local SP catalog
ii) Shareable package...