How to upgrade a deployed application (including VLF) to a V11 runtime environment
|Date:||2 November 2005|
|Product/Release:||Visual LANSA V11|
|Abstract:||How to upgrade your existing (deployed) applications from V10 a V11 runtime environment. Includes steps for upgrading VLF applications|
|Submitted By:||LANSA Technical Support|
When a new version of LANSA is released, it is recommended that you upgrade your development environment to take advantage of new features and fixes. Upgrading the development environment is simple and well documented. However when it comes to your existing deployed LANSA applications, you cannot just insert the LANSA Upgrade CD to upgrade them to the latest version.
There are 2 methods that can be used to upgrade deployed applications. Both of these methods assume that the development/deployment PC has already been upgraded to V11 with the latest EPCs. This allows the deployment tool to create packages that include the latest runtime environment.
Note: This tip is specifically for upgrading a runtime environment from V10 to V11 with EPC751 (CU1). If you are attempting to upgrade from V11GA to 11 CU1 then please contact support as there are known issues with that upgrade.
One thing to keep in mind is that application updates should always be kept separate from Runtime/EPC updates. This is stipulated in our documentation and there are various reasons for this
Visual LANSA Applications (Components, Functions and Processes):
The simplest method, is to apply V11 and the latest EPCs to the deployment PC and then rebuild the original installation package, ensuring that you select "Deploy with EPCs" in the Package Settings.
If Method 1 is not possible or feasible (perhaps due to the fact that the package no longer exists, or if the package size would be too big), you can upgrade the runtime objects on their own.
Prior to creating the runtime upgrade package, you must apply EPC751 and the latest EPCs to the deployment PC.
To create a runtime only package:
Note that these settings are a suggestion only, and may not match what your application requires. You should think carefully about which settings to select when creating this runtime upgrade package. If in doubt, please send an email to support and list all the relevant details.
The upgrade package should be created as a new package in the same application that your original application was built in. Once you have created the package, go to the Package Settings, be sure to select at least the following settings, as well as any other specific settings that your application uses (I.e. Web Environment Support etc)
The rest of the package should be built with settings that are relevant for your application. Note that in the following example, Install Boot Directory, as well as most of the Desktop settings and Setup Options are set to NO
Once you have created this package, you will be able to just run the setup on the target PC (be sure to install to the same directory as the deployed application).
Visual LANSA Framework Applications:
Upgrading a VLF application is similar to upgrading a normal VL application with some small additional steps. Prior to deploying the runtime upgrade you should also upgrade the VLF to the latest version as well.
You may note that after upgrading the VLF on the deployment PC, the framework will be reset to the standard version. This is governed by the files VF_SY001_System.XML and VF_SY001_Tables.XML which get renamed to VF_SY001_Upgrade_Saved_nnn.XML and VF_SY001_Tables_Upgrade_Saved_n.XML respectively when you upgrade the VLF. You may need to rename them back before rebuilding your package.
The easiest method for upgrading VLF is to rebuild the initial installation package, or create a copy of the initial installation package. This is the same as upgrading a regular Visual LANSA application
The second method is to create a runtime upgrade package. This is exactly the same as for regular Visual LANSA Applications (see above), with an optional (but recommended) second step to upgrade the VLF . The steps are:
- Create the runtime-only upgrade package.
- For VLF applications, you should also include the upgraded VLF runtime objects in either in the package created above or in a new package.
Upgrading the VLF is not compulsory, however we strongly advise that this is done (the VLF was updated in EPC738). The instructions below are the same as what you would follow any time you want to upgrade the VLF environment on a deployed PC. This should only be used as a supplement to the information that is already in the documentation.
If you are creating another deployment package for the VLF upgrade, you should use the same package settings that were used in the initial deployment of your application.
For a list of Objects to be deployed with the application, please refer to the Framework Repository Objects table which can be found in the Visual LANSA Framework documentation (under Appendix, 'Whats included in the Framework?').
For Windows deployments you should be concentrating on the column titled "Deploy to Execution Repositories (Windows)".
You may note that after upgrading the VLF on the deployment PC, the framework will be reset to the standard version. This is governed by the files VF_SY001_System.XML and VF_SY001_Tables.XML which get renamed to VF_SY001_Upgrade_Saved_nnn.XML and VF_SY001_Tables_Upgrade_Saved_n.XML respectively when you upgrade the VLF. This does NOT affect the deployed application as you are not deploying these files.
Once you have included all of the required objects, you can build the package and apply it to the client PC. The custom application DLLs and files do NOT need to be redeployed, as both LANSA and the VLF support backwards compatibility.