12 1 Major differences in Package 13 JIT Upgrade

LANSA Deployment Tool

12.1 Major differences in Package 13 JIT Upgrade

  • It's the same as it was in essence, though it is now just the one file to deploy, not a set of directories and files.
  • Now that LANSA produces MSI and MSP files they can be deployed using Microsoft SCCM – System Centre Configuration Manager. LANSA JIT Upgrade is not required.
  • SCCM is a far more capable deployment engine than LANSA JIT Upgrade, though SCCM can be more complex to set up in the first place. Thus LANSA JIT Upgrade will be kept as simple as possible leaving the SCCM functionality for more complex deployment scenarios.
  • V12 Application Server can be upgraded independently to V13
  • V13 Application Server will deliver V12 packages the same as the V12 Application Server.
  • The MSI delivered is the latest one in the x_apps folder.
  • The MSP delivered is the next one that has not been installed and matches the language of the installed MSI.
  • The install may be customized by adding an optional SETUP.TXT file with parameters to add to the msiexec command line. That is, any of the properties that the MSI and/or Windows Installer exposes.
  • An MSI is an independent install and an MSP is intended to be a cumulative install, so the prerequisite functionality has been removed.
  • The authorized users have been removed.
  • Only a single application is installed. The multiple applications options have been removed.
  • JIT DLL Upgrade is no longer supported.
  • Multiple languages are supported for each install
  • Multilingual Text Variables are now used for all text values which appear in the MSI UI, in order to support multiple languages.