Page History
...
The server then checks if SETUP.EXE is in the Application directory. If it isn't then the copy in the LANSA execute directory is transferred to the Client. This is another level of customisation customization available. A developer can put whatever SETUP.EXE file they like in the Application Directory and it will be transferred to the client and executed. For example it could be a self-extracting executable as a way to get other files downloaded to the client.
...
The Application Server can have an Application Directory that does not match the original Application name. The Client needs to install the first MSI specifying the new name as an MSI property. This will set the APPL value to the new one and attach to JIT using the new APPL. The Server will generate a SETUP.BAT that specifies APPL on the MSI command line.
| Info |
|---|
| Modifying the APPL value is not supported when using Feature Set Deployment. |
APPL is a runtime only value that can ONLY be set on the MSI command line. It is only necessary when you have a JIT server. The 1st install of the application needs to set the value too. That is done by supplying the 3 files (SETUP.EXE, SETUP.TXT and the MSI) that the JIT provides to the Client and just getting the Client to run SETUP.EXE rather than the MSI. This is the recommended approach to ensure consistency of APPL value. An alternative is to provide instructions for the Client to run the MSI using msiexec.exe and the property value to pass. Or a batch file can be provided.
...
In summary, the customisation available is:
...
- Create SETUP.TXT yourself and specify the MSI parameters, including all the X_RUN parameters exposed as MSI Properties.
...
- The SETUP.EXE can be replaced and perform whatever install the developer
...
- desires
...
- Use a different Application Name than the one it was built with - for multi-client support at different Package levels. For example, Application built as LANSAInventoryControl could be put in directories Customer1InventoryControl and Customer2InventoryControl. These can then be maintained at different levels even though they are running exactly the same software. They can also be given different Patches too. (This option is not compatible with Feature Set Deployment)
Example setup.txt files
...
- /qb
Displays a progress dialog only for both MSI and MSP installs and no confirmation dialog. Thus the installs happen automatically without any user interaction. MSI installs will use the settings from the previous install.
...
- /l*vx %TEMP%\InstallLog.txt
Diagnostic log file output to user's temporary directory.
...
- /qf
Displays a full user interface which overrides the default Patch behaviour of /passive and also overrides the Silent Install setting inside the MSI/MSP.