The Tivoli ISM Library
IBM Tivoli is developing a number of pre-packaged ICCT bundles for IBM products and are making them available via the ISM library:
ht
tps://www-304.ibm.com/software/brandcatalog/ismlibrary/search#query=icct:icct
I have listed the product install bundles available at the time of writing at the bottom of this blog entry, and more are being released all the time.
Bundle structure and pre-requisites
The majority of the bundles in the ISM library perform 3 functions:
1) mount software binaries
The software binaries themselves are not supplied with the bundle and need to be provided by the builder of the virtual appliance. In addition the binaries are not packaged in the bundle itself as this would create a package too large for the ICCT tool to manipulate. instead each product install package also includes the mountSoftwareBinaries bundle. This bundle creates an nfs mount to a location on an nfs server that contains the install binaries. For the mountSoftwareBinaries package to work on a linux OS the nfs-utils package must be installed.
2) Install the IBM Installation Manager
Many of the product installation bundles will first install the IBM Installation Manager. The Installation Manager is then used to process the supplied product response file to install the product. The Installation Manager requires the following libraries to be installed on Linux: gtk2.i686, libXtst.686, glibc, glibc.i686, libgcc.i686
3) Install the Product
The product is typically installed using the Installation Manager via a supplied response file. The response file can be edited to change installation options. Alternatively you can use the Installation Manager to perform a manual installation using the -skipinstall parameter to generate a new response file (this is also a useful approach if you are installing a different version of the product).
Red Hat Example Kickstart
In order for the mountSoftwareBinaries and Installation Manager to work successfully the following entries are required to be added to the bottom of the default ICCT kick start file between the %packages and %end lines.
@base
@network-tools
nfs-utils
libgcc
glibc
glibc.i686
libgcc.i686
gtk2.i686
libXtst.i686
N.B . when editing a kickstart file for ICCT you must download the default kickstart file and append to it. If you use a non ICCT kickstart file your virtual appliance will not boot.
Bundles Available on ISM at the time of writing
IBM DB2 Server 9.7
IBM WASND8.0 with HTTP Server 8.0 on single VM [1.0]
Tivoli Access Manager for e-business 6.1.1.3 - RHEL
Tivoli Access Manager for e-business 6.1.1.3 - SLES
IBM Tivoli Storage Manager agent V 6.3
IBM WebSphere MQ 7.0.1 Server
IBM WebSphere MQ 7.0.1.4 Server
IBM License Metric Tool Agent for System X platform
IBM WebSphere MessageBroker 8.0.0.0 Server
Oracle 11G R2 in SLES11 OS
IBM Tivoli Monitoring Agent for MQ
IBM HTTP Server 7.0
Apache Web Server 2.4.1
IBM Tivoli Directory Server v6.3
IBM Tivoli Monitoring Agent for Linux OS v6.X
IBM WAS Update Installer v70021
IBM Tivoli Monitoring Agent for WAS
IBM WebSphere Application Server Network Deployment 8.0
IBM WebSphere Application Server Community Edition 3.0
IBM Tivoli Monitoring Agent for DB2
IBM Tivoli Endpoint Manager Agent
IBM License Metric Tool Agent for System X platform
Tags: 
bundle
icct
websphere
glib
nfs-utils
db2
icon
installationmanager
mountsoftwarebinaries