nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TS 6.5 howto silent install

Frederik

We're planning to upgrade from 5.5 to 6.5, on solaris.

Our question is : how to do non-interactive install. We were thinking to use the response file approach (where all the questions are answered in a text file, and we run the installer as thus : ./install.sh -i console < responsefile. We did that for 5.5, but We haven't tried it yet on 6.5, but now I found a thread saying that doesn't work. (I started new thread, cause I think that thread is on the wrong board, + is very old)

http://devnet.interwoven.com/forums/cgi-bin/showflat.pl?Cat=&Board=NEWSGROUPS_GENERAL&Number=72264&page=0

In short : can you do a non-interactive install on TS 6.5 and sp2?

with response file, or how does the -f <properties-file> work ??

Thanks !!
Frederik

Find more posts tagged with

Comments

skip11

Hi,

I wrote that post that you provide in this thread. The post actually has nothing to go with using supported response file with
the installer in console mode. It has to do with creating a Solaris pkg, and using the installer with a custom response file.
I aussumed that the ksh script which kicks off the install sequence switches the input to the install from stdin in ksh
to some sort of input to the java (ZeroG Install anywhere) process.That would explain why the install sequence correclty
received input until a certain point. I could never get it to work, and eventually completely redesinged the install procedure
for 6.x teamsite via Solaris pkg.

regards,

R.Barger
Credit Suisse Group
Zurich, Switzerland

Frederik

Hi skip,

thanks for the update.
I think though that I might not be fully understanding what you call a "supported response file" and a "custom response file".

We had indeed in mind to homebrew a text file, that contains one answer per line, and then start the installer with : ./install.sh -i console < response

I guess that's what you call a "custom response file", and that is how we installed 5.5. I believe you found this to not work in TS 6.x

What do you mean with "supported response file". I can not find any info about that or the "-f install.properties" feature of install.sh, here or in support KB.

However, I did discover a bunch of files ending on *install.properties in the iwhome/../iwinstall/log folder, and so now I'm _guessing_ that they may be used for the "-f <file>" feature, to replay the same (type of) install. Anyone can confirm ?

Thanks for your input !
Frederik.

skip11

Hi,

install.properties is what I mean by supported response file - it contains the values used to do the install the
last time it was run, if I'm not mistaken. It can be modified and used for other installs with the -f option to
console mode.

regards,

R.Barger
Credit Suisse Group
Zurich, Switzerland

dazzlad

Hi,

I am interested on getting a working silent install from a clean Solaris system up to TeamSite 6.5 SP2.

I saw that you can pass the install.sh a install.properties file, but this doesn't seem to be created when I perform a manual install.

Is this documented anywhere?

Thanks.

Darren.

skip11

Hi,

I wish I could help you. I have done an extensive search of the support site and
I can no longer find ANY reference to this. A search there does not even find install.sh,
even though it is in the product documentation. I'll have to chime in with others who say the
search facility on the support site is terrible. I sniffed around and acutally found the file
in question. It is located in the directory above IWHOME called iwinstall. under iwinstall
there is a log directoy; there you can find the file. mine looks like this:

TeamSite120411162004install.properties
#Global Properties File
#Tue Nov 16 12:04:19 MET 2004
PCN=0
tomcatport=9080
IW_HOME_4DISPLAY=/cs/iw
LOGLOCATION=/var/log/iw
INSTALLER_UI=CONSOLE
http=81
licensekey=<sorry, can't have that>
ms3=/msutil.jar
ms2=/msbase.jar
IW_TSHOME=/cs/iw/iw-home
ms1=/mssqlserver.jar
RMI_PORT=1099
SAM=0
proxyport=1080
IW_DEBUG=false
IW_LOG=/cs/iw/iwinstall/log/092811162004install_log.log
IW_PRODUCT_DIR=/cs/iw/iw-home
IW_JNDI_PORT=3035
IW_OPENJMS_PORT=3030
IW_HOME=/cs/iw
wsport=9082
APA=0
IW_MODULES=/cs/iw/iwinstall/modules
STORELOCATION=/cs/iw/data
IW_PRODUCT_DIR_4DISPLAY=/cs/iw/iw-home
IW_PRODUCT_NAME=TeamSite
IW_GPF=/tmp/install.dir.1678/MyWorkingSpot/install.properties
vaemail=systemmanagement.cms-internet@credit-suisse.com
IW_PRODUCTS=/cs/iw/iwinstall/products
IW_DATABASE_TYPE=default
date=NoLimits
db2=/db2jcc.jar
portnum=3035
IW_UPGRADE=false
https=443
IWINSTALL=/cs/iw/iwinstall
MOUNTLOCATION=/iwmnt

This file does not contain ALL the input to the install, but I supose one could add the missing
parameters. It can be renamed to anything, and used with the -f option to console mode install.
By the way, this log dirrectoy also contains the install properties for other products like search and
CSF.

regards,

R.Barger
Credit Suisse Group
Zurich, Switzerland

dazzlad

Excellent.

I see a similar file for the CSSDK install in that folder too.

Nothing for Opendeploy though.

Even though this is a start I guess you still have to page through 10 pages of terms and conditions manually when kicking off the TS installer.
I will post back here if I get the chance to investigate this server.

I guess you also need a solution for installing TeamSite customisations if you want to distribute an entire application.

Thanks for the info!

Darren.

Frederik

Hi again,

thanks to Ralph (skip) again for the input.

In the mean time, I have been "re-engineering" the silent install functionality, based on the logic hidden in install.sh, trial and error, and the install log error messages. Thanks to IWOV for not documenting this feature! :-(

After a normal console install (for any Teamsite component or patch), you should check the folder
`iwgethome`/../iwinstall/log

it should contain a log file and an install.properties file. The files are pre-fixed by name of the product (but only if install succeeded - and not for patches, it seems and timestamp ( HHMMmmddyyyy ).

e.g. for my Teamsite SP2 install, I found :
note : my `iwgethome` : /extra/app/gwts/iw-home. Make appropriate changes for yours

[g60921@sdas0003]:/extra/app/gwts/iwinstall/log$ cat TS650SP2113712142005install.properties
#Global Properties File
#Wed Dec 14 11:37:52 MET 2005
IW_PRODUCT_CUR_VERSION=6.5.0.0.41240
IW_LOG=/extra/app/gwts/iwinstall/log/105712142005install_log.log
IW_HOME_4DISPLAY=/extra/app/gwts
INSTALLER_UI=CONSOLE
IW_PRODUCT_DIR=/extra/app/gwts/iw-home
IW_PRODUCT_NAME=TS650SP2
IW_PRODUCT_DIR_4DISPLAY=/extra/app/gwts/iw-home
IW_DRIVER_INSTALLER_TEMP_DIR=/tmp/install.dir.7299
IW_DEBUG=false
IW_MODULES=/extra/app/gwts/iwinstall/modules
IW_GPF=/tmp/install.dir.7299/MyWorkingSpot/install.properties
IW_HOME=/extra/app/gwts
IW_MODULE_HOME=/extra/app/gwts/iwinstall/modules/cssoapsrvr/SP2.5.0.2
IWINSTALL=/extra/app/gwts/iwinstall
IW_PRODUCTS=/extra/app/gwts/iwinstall/products
IW_UPGRADE=true

Now, copy this file to the folder where you have install.sh, and change some values to turn this into a suitable file for silent install:
IW_LOG=/extra/app/gwts/iwinstall/log/dummy.log
INSTALLER_UI=SILENT
IW_GPF=/tmp/temp.install.properties

Note:

IW_LOG file will be appended to if existing, and will soon after starting install be renamed to "{date:HHMMmmddyyyy}install_log.log". Later on it will be renamed to "TS650SP2{date:HHMMmmddyyyy}install_log.log" on successful ending.
IW_GPF must point to an EXISTING file, and will be overwritten. This file will contain an "actualised" version of the properties (with corrected log file and temp dir references)
IW_DRIVER_INSTALLER_TEMP_DIR will be ignored. Another temp dir will be created.

Then, you can use this file, in a silent install. You MUST run install from within the same directory, and must refer to properties file by absolute path. You MUST NOT use the "-i console".

touch /tmp/temp.install.properties # create a blank file
./install.sh -f absolute-path-to-properties-file

example : ./install.sh -f /tmp/installpack_unzipped/TeamSiteSP/install.properties

You will get some info on the stdout, but no questions. Check the logfile in the folder iwinstall/log. As described above, this logfile will change names a few times during the install.

Similar stuff has worked for me also on the Search and SearchSP2 installer, and TS Patch 62533.

As Ralph said, the properties file reflects the choices made during the first, console install. Any questions that were not asked then (e.g. subchoices to a major choice), may be missing from the properties file, and thus it may be difficult to set up a different install by only changing the properties file. (because you may not know the codes for missing properties).

greets,
Fred

-- hope I didn't mess up to much ;-)
-- IWOV : I'll take a Creative Vision:M as compensation for doing your documentation job.

EDIT : fixed some missing text because I had put it between < and >

Edited by Frederik on 12/16/05 08:37 AM (server time).

dazzlad

Frederik, this is great work.

I wish there was some kind of unofficial documentation project so everyone could make use of this!

Thanks.

Darren.

Frederik

In reply to:

Similar stuff has worked for me also on the Search and SearchSP2 installer, and TS Patch 62533.

We're now finding out that this silent install approach, that worked nicely for the 6.5 Search, and 6.5 SP2, etc, DOES NOT SEEM TO WORK for the base TS 6.5 installation, even though we've used all the same tricks.

I also noticed that the TS 6.0 install manuals describe the SILENT install mode in good detail, but then that section was removed in the 6.1 and 6.5 manuals. Anyone know why? Were there problems with this in 6.0 already?

All help appreciated !
--Fred