Friday, 6 August 2010

Installing Tivoli Directory Integrator 6.1.1 Fixpacks ...

This is purely an aide memoire, to save me having to look it up each time; in order to install a fix pack onto TDI 6.1.1 using the GUI, run the following command ( as root ): -


I've never been too sure why I see the exception: -

Error in copying /tmp/ismp001/8229657/data/a7390f9ecf6457bf3713f951c90b1bdb/  there may not be enough space on device

and: - File does not exist: /usr/ibm/common/acsi/jre/lib/ext/svcdump.jar
        at com.installshield.boot.streamhandler.ISMPFileURLStreamHandler.openConnection(Unknown Source)
        at sun.misc.URLClassPath$JarLoader.getJarFile(
        at sun.misc.URLClassPath$JarLoader.<init>(
        at sun.misc.URLClassPath$
        at Method)
        at sun.misc.URLClassPath.getLoader( Compiled Code))
        at sun.misc.URLClassPath.getLoader( Code))
        at sun.misc.URLClassPath.getResource( Code))
        at$ Code))
        at Method)
        at Code))
        at Code))
        at java.lang.ClassLoader.loadClass( Code))
        at java.lang.ClassLoader.loadClass(
        at java.util.ResourceBundle.loadBundle(
        at java.util.ResourceBundle.findBundle(
        at java.util.ResourceBundle.getBundleImpl(
        at java.util.ResourceBundle.getBundle(
        at com.installshield.util.LocalizedStringResolver.resolve(Unknown Source)
        at com.installshield.util.LocalizedStringResolver.resolve(Unknown Source)
        at com.installshield.wizard.Wizard.executeStartupBeans(Unknown Source)
        at com.installshield.wizard.Wizard.startup(Unknown Source)
        at com.installshield.boot.BootMain.bootstart(Unknown Source)
        at com.installshield.boot.BootMain.executeBoot(Unknown Source)
        at Source)

but it appears to work.

It's also worth noting that I see a "Sign On to the Server" dialogue box three times; this is spookily reminiscent of the dialogue boxes that I used to see when installing WebSphere Application Server on OS/400 back in the day but .... clicking 'Cancel' gets rid of the box, and TDI seems none the worse.

Final point, running: -

/usr/ibm/common/ci/gmi/bin/gmi -help

returns: -

Update Installer Command Line Options:

Displays a list of available command line options.

Displays the Update Installer version.

Runs Update Installer in console mode.  This option suppresses the graphical user

-record <response-file>
Creates a response file containing options for running Update Installer in silent mode.

-silent -options <response-file>
Runs Update Installer in silent mode.  A response file, previously created with the
-record option, can be used to specify the actions to be performed by Update Installer.

Runs Update Installer in uninstall mode.  Maintenance is removed by Update Installer.

-uuid <uuid>
Identifies the 32-character UUID of the offering that will be updated by Update Installer.
If more than one instance of the offering is installed, the -discriminant
option is required.

-discriminant <discriminant>
Identifies the discriminant that uniquely identifies an installed instance
of the offering to Solution Install.

-mdvFile <mdv-file-list>
Identifies one or more maintenance package, separated by
spaces, to be installed or uninstalled by Update Installer.
This option may only be used with the -silent option.

-fixName <IU-name-list>
Identifies one or more IU fix names, separated by spaces, to be uninstalled.
This option may only be used with the -silent option.

-updateVersion <update-version>
Identifies the version of an update to be uninstalled.
This option may only be used with the -silent option.

For more information, see the Update Installer User's Guide.

which is rather handy.

No comments:

Grokking grep

A colleague was tinkering with grep  and, thanks to him, I discovered a bit more about the trusty little utility. I had not really explored ...