Tuesday, 28 July 2015

IBM InfoSphere Master Data Management Silent Installation

In a silent installation, the IBM Installation Manager is invoked passing in a file (called the response file) containing parameter values required for installing Master Data Management.  This includes the Install Location, the location at which the MDM installable is available, the location at which the Shared resources can be stored, the features to be installed and configuration parameter value for each feature.

Sample response files for installing MDM are available in the MDM Startup Toolkit.  The Installation Manager can also be of help in creating a response file.  The record option can be used and a file name can be specified.  The Installation Manager operations will be recorded and the parameter values provided during installatin will be stored in the response file.  This file can be used as is, or with required modifications.

Recording from Installation Manager to create response file for Silent Install
C:\Program Files (x86)\IBM\Installation Manager\eclipse>IBMIM.exe -dataLocation D:/InstanceLogs/MDMLogs -record MDMInput.res

Silent install using a response file
C:\Program Files (x86)\IBM\Installation Manager\eclipse>IBMIM.exe -dataLocation D:/InstanceLogs/MDMLogs -silent -input MDMInput.res -acceptLicense -nosplash

The Silent installation process is quicker, although the validations provided by the Installation Manager GUI are not available with it.  Silent installation response files can be generated and used when installation has to be performed multiple times. 

The most important advantage of Silent install is that it allows the user to provide customized values for certain inputs, which is not possible with the Installation Manager GUI.  For example, when a custom WebSphere Application Server profile trust file is created, the path of this file and the password for this file cannot be provided when Installation Manager GUI is used.  However, these values can be modified and specified when Silent installation is used, using the below parameters.

<data key='user.L2.was.node.client.trust.file.url,com.ibm.mdm.advanced' value='etc/DummyClientTrustFile.jks'/>
<data key='user.L2.was.truststore.pwd,com.ibm.mdm.advanced' value='WebAS'/>

Key parts of the response file
    <variable name='sharedLocation' value='D:/Instances/Shared'/>

Declares the Shared Location used by the Installation Manager

    <repository location='D:\Installables\MDM\Cuba\MDM\disk1'/>

Holds the details of the MDM repository

  <profile id='InfoSphere MDM Standard Edition or Advanced Edition' installLocation='D:\Instances\MDM114'>
    <data key='eclipseLocation' value='D:/Instances/MDM114'/>

Holds the profile id, the install location and the entire set for parameters for configuring the instance

  <install modify='false'>
    <!-- InfoSphere MDM Standard Edition or Advanced Edition -->
    <offering profile='InfoSphere MDM Standard Edition or Advanced Edition' id='com.ibm.mdm.advanced' version='11.4.0.FP00IF000_20140924-0832' features='com.ibm.im.mdm.db.feature,com.ibm.im.mdm.app.feature,com.ibm.mdm.ba.webapp.feature,com.ibm.mdm.ev.webapp.feature' installFixes='none'/>

Holds the details of the offering, the id, the version and the features to be installed.  It also indicates whether the installation is a new one, or it is a modification of an existing instance, using the flag modify.

Indicates that the instance has to be uninstalled.

A set of preferences are mentioned.

Silent installations using response files
Installation Manager command line arguments