Caché Upgrade Checklists - InterSystems Documentation

Caché 5.1 Upgrade Checklist11.1.1 New License Keys RequiredNote:Caché version 5.1 introduces new capabilities and a new key format. The license servers from prior releases andthe license server for Caché 5.1 do not recognize each others key formats. Existing users MUST obtain newlicenses from InterSystems in order to run Caché version 5.1. Please contact your local sales representative toobtain the new keys corresponding to your existing license or to discuss new licensing options.If a site wishes to run a 5.1 installation on a system where 5.0.x systems will run concurrently, the systems mustobtain the correct license keys from their respective servers. This is done by individually setting the ports to thelicense servers on each system. Caché 5.0.x systems default the license server port to 4001. The license serverport for the version 5.1 system(s) should use a different port number for accessing their license server.Multiple Caché instances that share a key must all be upgraded to 5.1 together.11.1.2 Recompilation After UpgradeAs noted in the Release Notes, and elsewhere in this document, the changes made to Caché for this version are extensiveand pervasive.Important:CAUTION:All user application classes must be recompiled after upgrading to version 5.1. And, all user routines thatcontain embedded SQL statements must also be recompiled as well.Failure to recompile after upgrade may result in unexplained failures during application execution, andpossible data loss.11.1.3 System Management PortalPrior to this version, how Caché was administered depended heavily on the platform where Caché ran. With version 5.1,InterSystems introduces a new administrative interface that is common across all platforms. Caché 5.1 now uses a browserbasedinterface, the System Management Portal, for system management.An advantage of this approach is that (which few exceptions) it is no longer a requirement that any Caché component beinstalled on the system you use to manage an installation. Remote management of systems over the web, subject to accesscontrol established for the site, is now possible and easy. Cross-release compatibility issues are eliminated because boththe data and its formatting information come directly from the system being managed.This new interface subsumes the functions previously distributed among Explorer, SQL Manager, Configuration Manager,and Control Panel functions of the Windows Caché Cube. Because it combines these functions, operators and somedevelopers will also use the portal to accomplish their tasks as well.Important:The version 5.1 management portal cannot be used to manage earlier versions of Caché. The opposite isalso true; the management functions of earlier versions cannot be used to manage Caché configurationsrunning version 5.1.More information on the System Management Portal can be found in the System Administrator documentation.11.1.3.1 Portal and Application Name ConflictsIn Caché 5.1, the instance name chosen at installation time, is used to construct the name of the CSP application that runsthe System Management Portal. For example, assume a Caché system had a CSP application called, “/appserver”. If theinstallation name chosen for this system was “APPSERVER”, the upgrade procedures would construct a CSP applicationto run the System Management Portal called, “/appserver/csp/sys”. After the upgrade this would effectively block accessto the previously available CSP application.226 Caché Upgrade Checklists