Problem:

Release 4.0:

The creation of apslastdir key works for AS service-pack update.

Application Server installed to a non-default location using the following command line:

setup -s f1Drive:\\FolderName\\NewSetup.ISS For example, setup -s f1C:\\MFAS40\\NewSetup.ISS

The concern is that MF AS setup files will be packaged to a seft-extract file for our customer to download.  They will probably extract it to a network drive for their users to run MF AS silent install (Setup.Bat in our case).  What we will have to ask them to do is to edit Setup.bat to specify where the NewSetup.Iss is located.

Also, when distributing MF AS setup files on a CD with Setup.Bat.  They cannot run Setup.bat directly from the CD, because they have to update Setup.Bat to specify the location of NewSetup.Iss.

Resolution:

Here is what is in the batch file to do the silent install using newsetup.iss file from a different location. Application Server installed to a non-default location using the following command line:

setup -s -f1Drive:\\FolderName\\NewSetup.ISS

For example, setup -s f1C:\\MFAS40\\NewSetup.ISS

Description: must give full path , if setup.iss is in same folder as setup but it will not pick it up , otherwise must give full path ( if keep name as newsetup.iss- must give full path to where it is located)

According to the old Installshield docs, if the setup.iss isn't located in the same directory as setup.exe, then an absolute path must be specified.

So they could rename NewSetup.iss to setup.iss, or continue using a full path...

Three scenarios that will work.

Here is the setup

       Copy App Server setup files for NE 4.0 from the CD to C:\\MFAS40 folder 2.       

       Overlay Setup.INS and Setup.ISS with ones supplied by micro focus.

       Do not rename Setup.ISS  

       Set ASLMNoLicensePrompt=Yes in MicroFocusAppServ40.INI  

       Set szPath=C:\\Program Files\\Micro Focus\\Net Express 4.0\\Application Server

             for [AskDestPath-0] section in Setup.ISS

             Create Setup.Bat install script three different scenario as follows:

Scenario 1 :  if using a different name than setup.iss , Specify NewSetup.ISS with full path

echo off

echo ***** Starting installation *****

setup -s -f1C:\\MFAS40\\NewSetup.ISS

:loop

if not exist "c:\\Program Files\\Micro Focus\\Net Express 4.0\\Application

Server\\DeIsL1.isu" goto loop

aslmpclocate -q

Scenario 2: rename newsetup.iss to setup.iss and in same folder as setup.exe

                   Keep -f1, but omit Setup.ISS

echo off

echo ***** Starting installation *****

setup -s -f1

:loop

if not exist "c:\\Program Files\\Micro Focus\\Net Express 4.0\\Application

Server\\DeIsL1.isu" goto loop

aslmpclocate -q

Scenario 3: rename newsetup.iss to setup.iss and in same folder as setup.exe

                   Omit both -f1 and Setup.ISS

echo off

echo ***** Starting installation *****

setup -s

:loop

if not exist "c:\\Program Files\\Micro Focus\\Net Express 4.0\\Application

Server\\DeIsL1.isu" goto loop

aslmpclocate -q

According to the old Installshield docs, if the setup.iss isn't located

in the same directory as setup.exe, then an absolute path must be

specified.

So they could rename NewSetup.iss to setup.iss, or continue using a full

path...