Software Deployment

ORIGINAL: Inabus
Is this is a vendor MSI and do the files sit outside of the MSI, like an admin installation?

P


Having worked on this myself, I think I can answer this on the OP's behalf.

Lotus Notes 8 client ships as a single executable, Notes All Client C19U0EN.exe, for an English installation. When run, this executable unpacks files to a folder (default is a subfolder of %TEMP%). In this subfolder, you will find :

A wrapper SETUP.EXE file.
Several language related INI files (used to localize dialogs for the wrapper setup.exe)
Lotus Notes 8.0.1.msi (the main MSI, approx 3.5MB in size)
Several language transforms (MST's)
Lotus Notes.itw (InstallShield Tuner Wizard file)
Data1.cab (about 235MB in size)
updateSite.zip (this is one of the external files I alluded to earlier - it contains a whole load of java-related .jar files)

Then, during the vendors installation routine, further subfolders are created within the temporary folder, namely

\deploy
\deploy\extras

There are custom actions, written by the vendor, in the MSI which rely on finding updatesite.zip and these subfolders (plus contents) in the source folder.

If one wishes to eliminate the setup wrapper and run just the vendor MSI with a perhaps a language transform and/or response/customisations transform, then, as I see it, the source folder containing the MSI, MST(s) and CAB file must also be prepopulated with the updatesite.zip file and the above subfolders and contents.

Regards,

Spartacus

The Lotus Notes 8 client installer, as shipped by IBM, expects to find certain external files either in the main folder hosting the MSI, or in subfolders of the main folder.

For a typical (UK) English installation,

In the same folder as the MSI :-

[font="courier new"]updateSite.zip

In the \deploy subfolder :-

[font="courier new"]keystore.JCEKS.IBM_J9_VM.install
debug.options
plugin_customization.ini
install.xml
install_en.properties
install.properties

In the \extras subfolder :-

[font="courier new"]presetfeeds.opml

You will need to make the necessary arrangements to have these files and subfolders available at install time.

Unfortunately, I don't have Radia experience, so cannot offer specific advise in that area.

In my own case, the customer this was being packaged for did not allow external source files, so we had to stream all the above external files into the package and then stream them out into the relevent source folders at install-time ... a real chore !

Regards,

Spartacus

Radia..... still trying to tame this beast...

Right now, my solution for some of the quirky directory issues I am getting when publishing is to go to the file objects in system explorer & modify their location to something akin to "&(ZMASTER.ZLIBDRV)&(ZMASTER.ZLIBDIR)DEPLOY" where "&(ZMASTER.ZLIBDRV)&(ZMASTER.ZLIBDIR)" would be the default location that the MSI is copied to if you published your MSI through the Advanced method, though this may also depend on your infrastructure. A safe bet would be to look @ the location variable for your MSI object in system explorer.

Thank you very much for your replies.But I am sorry to say that the package is not installing through Radia even after following both the suggestions provided.So could you please tell us is there any other alternative to install the application.

Are you including the additional files when publishing?
Are you using "longfile name" publishing?
What do the Radia logs say?
Are you machine/user splitting the MSI during publish?
Does the MSI have a transform?

the package is not installing through Radia What happens, then? Nothing? A partial install with a rollback? Any errors? The folks here are good but sadly lacking in clairvoyance :)

Hi,
We tried using the additinal files after suggestion.We use short file names while publishing.The log file does not show much details.We dont split msi while publishing and its machine specific. At the end of the installation say when its 10 sec remaining it throws the error "Could not copy FILE:(2)The system cannot find the file specified. Old path: C:\Documents and settings\default user\install.xml. New path: C:\program Files\IBM\Lotus\notes\framework\RCP\Deploy\Install.xml"
and rolls back.

Try using long file names when publishing, also make sure that the MSI your publishing installs outside of Radia.

Is this is a vendor MSI and do the files sit outside of the MSI, like an admin installation?

P

Hi,
Radia does not support Shortfile names.

Sorry long file names.

Radia version 4 and above certainly DOES support longfile names else there wouldnt be an option that states:

"Use local AIP support for MSI redirector" with an additional option below that which states "Use long filenames"

I know this as I am currently looking at the Radia Publisher on the screen to my right AND use that option for every publish I do on a daily basis :)

P

Not sure if this is relevant, but maybe worth a mention. I don't use RADIA so may not be the same.

On a few occassions, my deployment tool comes up with similar error about unable to copy files. I figured out this was down to the 256 character limit being exceeded. I get round it by copying the files for deployment to the root of the server and repackage\republish onto the deployment server.

Maybe do a search for "~" on the source file to see if any filenames have been shortened.

I ran the tuner to create the transform. However, I wasn't able to use Advanced Publisher using an AIP to publish the Lotus Notes 8.51 application. I got the exact same errors as VinaySalimath. I switched to Basic mode and it installs just fine. One thing that I noticed that when I tried to run msiexec /a <lotus msi> TARGETDIR=<desired directory>, it wouldn't create an AIP. It would only launch the installation of the program.