Deployment Tool Package naming convention and Package Dependencies
|Date:||15 December 2004|
|Abstract:||Deployment Tool Package naming convention and Package Dependencies|
|Submitted By:||LANSA Technical Support|
|Last Review:||November 2010|
When creating application upgrade packages in the Visual LANSA Deployment Tool, the use of Pre-requisite and Co-requisite packages should be used to ensure that packages are installed in the correct order, if package dependencies exist.
If you do not set up Pre-requisite and Co-requisite package entries, then essentially you are saying that the order doesn't matter ie. each package is distinct and can be installed at anytime irrespective of whether other packages have been installed or not. If the package installation order does matter, then you should use the Pre-requisite and Co-requisite package setting.
The use of Pre-requisite and Co-requisite packages is explained in detail in section 4.8 Package Dependencies in the LANSA Application Deployment Tool guide.
The use of Pre-requisite and Co-requisite packages is particularly relevant if you use a JIT deployment model as the package installation process is automated and the use of this facility will ensure seamless automatic updates.
There is an extra consideration if your package naming convention is of the form UPDATE1, UPDATE2, UPDATE3 ... UPDATE10, UPDATE11, UPDATE12, UPDATE13, etc.
In this case the JIT package installer will access the packages in alphabetical order. Which means that package UPDATE11 will be installed before package UPDATE2, which may not necessarily be what you want.
This can be avoided by:
- using a naming convention of the form UPDATE001, UPDATE002 etc.
- using the Pre-requisite and Co-requisite entries