Caché Upgrade Checklists - InterSystems Documentation

Caché 5.1 Upgrade ChecklistService NameMinimalNormalLockedDown%Service_DDPNoNoNo%Service_ECPNoNoNo%Service_LATNoNoNo%Service_MSMActivateNoNoNo%Service_MonitorNoNoNo%Service_ShadowNoNoNo%Service_TelnetNoNoNo%Service_WeblinkNoNoNo11.1.6 Emergency AccessAs a contingency, Caché provides a special emergency access mode that can be used under certain dire circumstances, suchas severe damage to security configuration information or “unavailability” of any users with the %Admin_Manage:U or%Admin_Security:U privileges. (Although Caché attempts to prevent this situation by ensuring that there is always atleast one user with the %All role, that user may not be available or may have forgotten his or her password.)When Caché is running in emergency access mode, only a single user (the “emergency user”) is permitted. Caché is startedin emergency access mode through a command-line switch, which passes a user name and password for the emergencyuser. This user name does not have to be previously defined within Caché. (In fact, even if the user name is defined inCaché, the emergency user is conceptually a different user.) The emergency user name and password are only valid for asingle invocation of emergency mode.The user starting Caché in emergency access mode must have operating-system level system management privileges. (OnWindows systems, the user must be a member of the Administrators group. On UNIX® systems, the user must be root. OnOpenVMS systems, the user must have a system UIC.) Caché authenticates this user by checking his or her operating systemlevel characteristics. When Caché is started in emergency access mode:• The emergency user is the only permitted user. Any attempt by another user to log in will fail.• The emergency user automatically has the %All role.• The Console and CSP services are enabled. All other services are disabled. This does not affect the enabled or disabledstatus of services in the configuration; only the current “in memory” information about services is affected.• Caché password authentication is used and unauthenticated access is forbidden for all services.• If possible, auditing is enabled for all events. Caché startup proceeds even if this is not possible.11.1.7 Configuration File ChangesOne consequence of the new capabilities added in version 5.1 is that major differences have been made to the form andcontent of the configuration file that provides many of the initialization values when Caché starts up. This section does notdetail every change in the configuration file, only the more apparent ones.Note:As of this version, the parameter file MUST be named cache.cpf.228 Caché Upgrade Checklists