When considering upgrades of GuardIEn and/or CA Gen to a new release, a common misconception is that the upgrade has to be implemented all at once with the upgrade of the CSE and GuardIEn software, regeneration of code and deployment of new versions of workstation software all happening as part of the upgrade and development frozen until complete.
For example, you might currently be using CA Gen 8.5 (or earlier) for the encyclopaedia and generated code and wish to upgrade to 8.6. However not all of the applications are able to regenerate and retest their code as part of the upgrade process at present and hence the choice is either to postpone the upgrade or install a new encyclopaedia server and database and selectively transfer projects across to the new encyclopaedia.
This can be further complicated when you wish to use one release of CA Gen (e.g. 8.6) for developing a new release of the application and also maintain the production code using an earlier release (e.g. 8.5). If you implement a new encyclopaedia for the new release, migrating changes between models becomes much more difficult when they are in separate encyclopaedias.
There is an alternative...
The flexibility offered by GuardIEn to generate and install the application code it is sometimes overlooked when considering options for upgrades, especially for upgrading the application code.
