JIT may not install packages in order expected
|Date:||20 January 2005|
|Abstract:||JIT packages not installed in order expected|
|Submitted By:||LANSA Technical Support|
|Last Review:||December 2010|
When deploying multiple application packages using the Visual LANSA Deployment Tools Just In Time (JIT) deployment model, the JIT package installer will access the packages in alphabetical order (see this tip).
However, in Windows XP SP2 file sorting has changed so embedded numbers are now treated as whole numbers. i.e For packages named PK1, PK10 and PK2, packages will now install in the correct order of PK1, PK2 and PK10 whereas previously the install order would have been PK1, PK10 and PK2.
This issue is discussed in the documentation for V11, under Package Dependencies. It mentions "in some cases, you may deploy your application using more than one package. Naturally, it is important for these packages to be installed in the correct sequence. To ensure this, you would use Package Pre and Co-Requisites."
In cases where the order of package installation is important, each package that is deployed should have a prerequisite of the package before it. The package installer will loop through the packages, installing them in an order which adheres to all prerequisite rules.