Caché Upgrade Checklists - InterSystems Documentation

Administrators2.1.3.6 License Enforcement TightenedIn this release, the management of licenses, including license limit enforcement, has been improved.Licenses Cannot Be Obtained From The CSP Server ProcessApplications that call $SYSTEM.License.Login() from a CSP server process (serving a CSP page request or a SOAPrequest) will encounter a error and must be changed to use the %CSP.Session login API.DocBook And The Class Browser Now Consume A LicenseIn past versions, /csp/docbook/ and /csp/documatic/ applications did not consume a license when run. Begining with thisrelease, they do.Use Of Management Portal Consumes A LicenseThe System Management Portal application now consumes a license. There is now no difference, from a license use perspective,whether you log in to Caché through a terminal connection and run character-oriented management/operationutilities, or you access this functionality through the browser based Management Portal.Customers who have sites that run with a license key sized to the exact number of users may encounter license limit exceededissues if the Management Portal is used, consumes the last license unit, and another user attempts to log in to Caché.Remote CSP Connections Not Allowed Without A LicenseCaché now enforces the rule that a Caché instance that does not have a valid license key installed will not serve CSPapplications to a remote host. Without a valid license key, CSP applications are now only accessible from a browser on thelocal machine.Task Manager Initiated Processes Consume A License With Web Add-On KeyProcesses started by the task manager will now consume a license as web add-ons.2.1.3.7 Make LoginCookies Authentication Mode Fully IndependentBeginning with this release, for applications which allow both unauthenticated and login-cookie authentication modes, thelogin cookie is now checked before the unauthenticated mode. In prior releases, an application could be logged in asUnknownUser even if a login-cookie was available.2.1.3.8 Increase Frame Stack Size on 64-Bit SystemsThe frame stack size for 64-bit platforms has been increased in this release to account for increased stack usage in recentreleases. It may now be larger than 64KB. (The stack size for 32-bit platforms has already been increased in a previousrelease.) This will prevent errors when programs are migrated forward.This change results in an increase in the memory usage for each partition, depending on the 64-bit platform:• Unicode: 25,032 bytes• 8-bit: 19,817 bytesNote:If your application (or application set) was close to running out of space in previous versions, this additionalconsumption of memory may cause errors. If this happens, the partition size must be increased.2.1.3.9 Changes to %Manager RoleIn this release, the %Manager role now has the %Admin_Journal:USE resource added to it.Caché Upgrade Checklists 9