Caché Upgrade Checklists - InterSystems Documentation

Administrators11.1.7.1 New Parameter ReferenceIf a site controls operation by editing the .cpf, each of these controls must be examined to make sure they are still applicable.Administrators are strongly urged to review the Caché Parameter File Reference book for the current organization, and thevalid parameters and their allowed settings.11.1.7.2 Startup Check for Configuration ChangesCaché configuration information is stored outside of Caché and (by design) can be modified when Caché is not running.Therefore, a special protective option have been added to this version. Rather than protecting the contents of the configurationfile, Caché controls the ability to start the system or modify the configuration of a running system. This protection is enabledby turning Configuration Security on. (Of course, the configuration file can and should be protected outside of Caché bystrictly limiting at the operating system level the ability of users to modify that file.)During startup, if Caché detects that the configuration (.cpf) file has changed since the last time the Caché instance wasstarted, the user running startup will be asked to enter a username and password. This data will be used to verify that theuser is authorized to start Caché with altered configuration parameters. If the user is successfully authenticated, and theuser has %Admin_Manage:Use, Caché will be started with the new configuration parameters.Otherwise, Caché will start with the values of the last known configuration. When this happens, the configuration filesupplied will be copied to cache.cpf_rejected (overwriting any file by that name), and the configuration parameters actuallyused to start Caché will be written to the file specified as the configuration file.11.1.8 Low-level Management InterfacesIn addition to the new Management Portal, system administrators can exercise low-level control over the security of Cachésystems through character-oriented utilities. The available routines are described in The CHUI-Based Management Routines.11.1.9 Web Server ChangesThe evolution of security capability in Caché 5.1 has affected the way hypertext information is served to browsers.11.1.9.1 The Caché Private Web Server is Now ApacheEach installation of Caché 5.1 also installs an instance of Apache as its private web server. Sites may change the configurationto use a different one, but Caché will always install its private server regardless.11.1.9.2 Default Port ChangesBy default, Caché now chooses as the superserver port number the first unused port at or after 1972. Applications whichdepended on the value, 1972, may fail to contact the superserver. In addition, Caché now uses a separate port number forits private web server. The value chosen is the first unused port at or after 8972. Despite both ending in “72”, the two portnumber are not correlated; the superserver port might be 1973 and the web server port number could be 8977.During a custom installation, user may explicitly set both the superserver port and the private WebServer port numbers.11.1.9.3 CSPGateway ChangesCaché version 5.1 has changed the CSPGateway implementation on two of the platforms.Support Removed for OpenVMSThe CSPGateway is no longer supported on OpenVMS. The material referencing it has been removed from the OpenVMSinstallation script and the code is no longer part of the product for OpenVMS.Note:Any existing CSP Gateway files will be removed during a upgrade from a previous version.Caché Upgrade Checklists 229