IBM Installation Manager

From DigitalOps.Org Wiki

Jump to: navigation, search

Contents

Introduction

The IBM Installation Manager (IM) is an application that lets you manage installs and updates of IBM tools on a host.

Users

Install Prerequisites

In order to install the IBM Installation Manager you must:

  • Have administrator rights on the destination machine
  • Have approx. 150Mb of spare disk space (this is for IM alone - additional packages will have their own space requirements)

Installation

To install IBM Installation Manager just run the the platform specific installer as a local administrator on the machine you want to install to. Disk space and other requirements are verified during the install process.

Uninstalling

To uninstall just run one of the following:

  • Windows C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\uninstall\uninstall.exe
  • Linux /var/ibm/InstallationManager/uninstall/uninstall

INFOINFO: These commands just uninstall IM itself, you should use IM to uninstall any individual packages before you run these.

Administrators

Updates to the Package Repository

Administrators use the IBM Packaging Utility to add packages to a repository which is accessible via a file share (NFS or SMB) or HTTP.

Install Configurations

I've found these options are useful to ensure a consistent user experience, they do the following:

  • Ensure this install of IM is persistent 
temporary='false'
  • Set the repository list to point at your local repository 
<server>
<repository location='http://localrepositoryhost:port/IBMIMRepo'/>
</server>
  • Unselect the "Search service repositories during install and updates" tick box. This prevents IM from looking on the internet for updates, within an organisation you want to control when these updates are rolled out. 
<preference name='offering.service.repositories.areUsed' value='false' />
  • Don't allow the user to change the value of this field in future 
<preference name='offering.service.repositories.areUsed_EDITABLE' value='false' />
  • Set the application defaults and other install options when installing packages, in this example, ClearCase: 
<data key='user.CC_RegSvrHostName,com.ibm.rational.xxx' value='ccregsrv.domain.com'/>
<data key='user.CC_...

These go in install.xml. Here is a typical Windows example which installs IM along with ClearCase and ClearQuest preconfigured with site specific options (... many left out for clarity): 

<?xml version="1.0" encoding="UTF-8"?>
<agent-input acceptLicense='true' rebootLater='true' clean='true' temporary='false'>
<server>
<repository location='http://localrepositoryhost:port/IBMIMRepo'/>
</server>
<profile installLocation='C:\Program Files\IBM\RationalSDLC' id='IBM Rational SDLC'>
<data key='eclipseLocation' value='C:\Program Files\IBM\RationalSDLC'/>
<data key='user.Team_Conv_InstallDirectory' value='C:/Program Files/IBM/RationalSDLC'/>
<data key='cic.selector.nl' value='en'/>
...
</profile>
<install modify='false'>
<offering features='agent_core,agent_jre' id='com.ibm.cic.agent' version='1.3.1000.20090618_1714'/>
<offering profile='IBM Rational SDLC' version='7.1.0.00-7-1-D081110'
features='com.ibm.rational.clearcase.top,com.ibm.rational.clearcase.mvfs,com.ibm.rational.clearcase.local.views.vobs'
id='com.ibm.rational.clearcase.nt_i386'/>
<offering profile='IBM Rational SDLC' version='7.1.0.00-7-1-D081110'
features='com.ibm.rational.clearquest.core,com.ibm.rational.clearquest.CQEC' id='com.ibm.rational.clearquest.nt_i386'/>
</install>
<preference name='offering.service.repositories.areUsed' value='false' />
<preference name='offering.service.repositories.areUsed_EDITABLE' value='false' /> 
<preference value='C:\Program Files\IBM\IMShared' name='com.ibm.cic.common.core.preferences.eclipseCache'/>
<preference value='30' name='com.ibm.cic.common.core.preferences.connectTimeout'/>
<preference value='30' name='com.ibm.cic.common.core.preferences.readTimeout'/>
<preference value='0' name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount'/>
<preference value='false' name='offering.service.repositories.areUsed'/>
<preference value='false' name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode'/>
<preference value='false' name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication'/>
<preference value='true' name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts'/>
<preference value='false' name='PassportAdvantageIsEnabled'/>
<preference value='false' name='com.ibm.cic.common.core.preferences.searchForUpdates'/>
</agent-input>

Admin only packages

Some tools are used only by an Admin, for example, the Package Utility (PU), IBM Rational License Server, test fixes etc. I install these into an Admin Repo which is not for use by the general population but can be added to IM (on an Administrator's machine) as follows:

  • Open File -> Preferences
  • Add Repository...
  • Set Repo as, for example, \\localrepositoryhost\IBMIMAdminRepo
  • Ok

The suggested procedure is that packages are installed here first and then moved (copy + delete with PU) to the "production" repository when they are released for general use. Both the Admin and Public repository should be owned by a single user and read-only to everyone else.

References

Retrieved from "http://www.digitalops.org/wiki/index.php/IBM_Installation_Manager"