Monday, 4 June 2012

Following the script - installing IBM Tivoli Directory Integrator using a response file ( silent installation )

Following on from my previous posts: -

Following the script - installing IBM HTTP Server using a response file ( silent installation )
Following the script - installing and using IBM WebSphere Update Installer using a response file ( silent installation )

here's the next (hopefully) exciting instalment in the series, within which I intend to install all of the IBM Connections and IBM WebSphere Portal solution stack using command line, response files, scripts etc.

So, here we are with IBM Tivoli Directory Integrator (ITDI).

This is a fairly simple process - however, I did cheat initially; I used the GUI to record and create a response file, via the command line: -

$ ./install_tdiv70_linux_x86_64.bin -console -options-record /tmp/installer.properties

(a) Unpack the product ( I'm using the 64-bit version of ITDI to match my installation of Red Hat Enterprise Linux 6.2 )

- See this blog post - IBM Tivoli Directory Integrator - Which Version is Which ? - in order to work which version you have

$ cd /tmp
$ tar xvf /mnt/Products/TDI70/C1IU2ML.tar

(b) Create the response file

$ cd /tmp
$ vi installer.properties

-V TDI_Install_Current="true"
-V TDI_Add_Features="false"
-V TDI_Upgrade_Previous="false"
-V licenseAccepted=true
-P installLocation="/opt/IBM/TDI/V7.0"
-V IS_SELECTED_INSTALLATION_TYPE=custom
-P tdiServerFeature.active=true
-P tdiCEFeature.active=false
-P tdiCEUpdateSiteFeature.active=false
-P tdiJavadocsFeature.active=false
-P tdiExamplesFeature.active=false
-P tdiIEHSFeature.active=false
-P tdiLWIFeature.active=false
-P tdiAMCFeature.active=false
-V TDI_Soldir_UnderHome="false"
-V TDI_Soldir_InstallDir="false"
-V TDI_Soldir_SelectDir="false"
-V TDI_Soldir_Working="true"
-V TDI_Bundled_ISC_Chosen="false"
-V TDI_Custom_ISC_Chosen="false"
-V TDI_No_ISC_Chosen="false"
-V TDI_Migrate_Cloudscape="false"


- There's a couple of things to note here; I'm installing to the default location, I'm performing a custom install, and I am only installing the ITDI server
- Additionally, I'm going to use a working directory, rather than my home or installation directory, for the ITDI solution ( TDISOL )

(c) Perform the installation

$ cd /tmp
$ ./linux_x86_64/install_tdiv70_linux_x86_64.bin -options /tmp/installer.properties -silent

(d) Wait for a few minutes - 2.5 in my case

(e) Check the logs for completion

$ cat /tmp/tdiv70install.log

..
(04-Jun-2012 18:13:35), Install, com.ibm.eec.pit.ismp.product.actions.CreateLinuxShortcutAction, msg1, The Directory entry IBM Tivoli Directory Integrator v7.0 {2} was installed successfully.
(04-Jun-2012 18:13:36), Install, com.ibm.eec.pit.ismp.product.actions.CreateLinuxShortcutAction, msg1, The Application entry Uninstall IBM Tivoli Directory Integrator V7.0 was installed successfully.

...

(f) Validate the installation

$ /opt/IBM/TDI/V7.0/bin/applyUpdates.sh -queryreg

Information from .registry file in: /opt/IBM/TDI/V7.0
Edition: General Purpose
Level: 7.0.0.0
License: None

Fixes Applied
=-=-=-=-=-=-=
None

Components Installed
=-=-=-=-=-=-=-=-=-=
BASE
SERVER
PLUGINS


(g) Prepare for the 7.0.0.5 fix pack - this is the minimum level that IBM Connections 3.0.1 requires/supports

$ cp /mnt/Products/TDI70/7.0.0-TIV-TDI-FP0005.zip /tmp/
$ unzip -j 7.0.0-TIV-TDI-FP0005.zip 7.0.0-TIV-TDI-FP0005/TDI-7.0-FP0005.zip

(h) Replace the installed UpdateInstaller.jar with one shipped in the ZIP file

- I've blogged about this previously

$ mv /opt/IBM/TDI/V7.0/maintenance/UpdateInstaller.jar /opt/IBM/TDI/V7.0/maintenance/UpdateInstaller.jar.ORIGINAL
$ unzip -j 7.0.0-TIV-TDI-FP0005.zip 7.0.0-TIV-TDI-FP0005/UpdateInstaller.jar -d /opt/IBM/TDI/V7.0/maintenance/

Archive:  7.0.0-TIV-TDI-FP0005.zip
  inflating: /opt/IBM/TDI/V7.0/maintenance/UpdateInstaller.jar

- Note that the -d option specifies the target directory and the -j option tells unzip to ignore the path of the file within the ZIP file

(i) Install the fix pack

$ /opt/IBM/TDI/V7.0/bin/applyUpdates.sh -update /tmp/TDI-7.0-FP0005.zip

(j) Wait a while - 2.5 minutes

...
CTGDKO023I Applying fix 'TDI-7.0-FP0005' using backup directory '/opt/IBM/TDI/V7.0/maintenance/BACKUP/TDI-7.0-FP0005'.
CTGDKO027I Updating SERVER.
CTGDKO027I Updating PLUGINS.

...

(k) Check the current installed version

$ /opt/IBM/TDI/V7.0/bin/applyUpdates.sh -queryreg

Information from .registry file in: /opt/IBM/TDI/V7.0
Edition: General Purpose
Level: 7.0.0.5
License: None

Fixes Applied
=-=-=-=-=-=-=
TDI-7.0-FP0005(7.0.0.0)

Components Installed
=-=-=-=-=-=-=-=-=-=
BASE
SERVER
   -TDI-7.0-FP0005
PLUGINS
   -TDI-7.0-FP0005


Sorted.

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...