Thursday, 13 September 2012

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

This follows on from my previous post: -


which covered the silent ( response file ) installation of IBM Tivoli Directory Integrator V7.0 ( as included with IBM Connections 3.0 ).

This new post is focused upon IBM Tivoli Directory Integrator V7.1, which is now the pre-requsite for IBM Connections 4.0 ( see the IC4 System Requirements for further information ).

It's much the same, but TDI V7.1 has a different format to it's response file.

So I started by unpacking the TDI product: -

$ cd /tmp
tar xvf /mnt/hgfs/Software/TDI71/CZ9MNML.tar

and then recorded a new response file: -

./linux_x86_64/install_tdiv71_linux_x86_64.bin -r /tmp/tdi71_responsefile

This is a good way of validating the differences between the old response file: -

-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"

and the new response file: -

# Thu Sep 13 13:44:57 BST 2012
# Replay feature output
# ---------------------
# This file was built by the Replay feature of InstallAnywhere.
# It contains variables that were set by Panels, Consoles or Custom Code.

#Has the license been accepted
#-----------------------------
LICENSE_ACCEPTED=TRUE

#Choose Install Folder
#---------------------
USER_INSTALL_DIR=/opt/IBM/TDI/V7.1

#Choose Install Set
#------------------
CHOSEN_FEATURE_LIST=Server,CE
CHOSEN_INSTALL_FEATURE_LIST=Server,CE
CHOSEN_INSTALL_SET=Custom

#Solutions Directory
#-------------------
TDI_SOLDIR_HOME=0
TDI_SOLDIR_INSTALL=0
TDI_SOLDIR_SELECT=0
TDI_SOLDIR_CWD=1

#Server Port Values
#------------------
TDI_SERVER_PORT=1099
TDI_SYSTEM_STORE_PORT=1527
TDI_REST_API_PORT=1098
TDI_MQE_SYSTEMQ_PORT=41001

#Register Server as Service
#--------------------------
TDI_REGISTER_SERVER=0


If nothing else, the new response file is way shorter, especially if I take out the comments: -

LICENSE_ACCEPTED=TRUE
USER_INSTALL_DIR=/opt/IBM/TDI/V7.1
CHOSEN_FEATURE_LIST=Server,CE
CHOSEN_INSTALL_FEATURE_LIST=Server,CE
CHOSEN_INSTALL_SET=Custom
TDI_SOLDIR_HOME=0
TDI_SOLDIR_INSTALL=0
TDI_SOLDIR_SELECT=0
TDI_SOLDIR_CWD=1
TDI_SERVER_PORT=1099
TDI_SYSTEM_STORE_PORT=1527
TDI_REST_API_PORT=1098
TDI_MQE_SYSTEMQ_PORT=41001
TDI_REGISTER_SERVER=0


:-)

Now, for me, my work here is done, as I've installed TDI 7.1 as well as generating the response file :-)

However, next time around, I'll need to actually install the product using the response file.

This is how I'll do it: -

install_tdiv71_win_x86.exe -i silent -f /tmp/tdi71_responsefile

#LifeIsGood

Thanks to the TDI documentation here for some useful information on the silent installation process.

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="{...