13.07.2015 Views

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Administrators2.1.3.15 Changes In The Treatment Of The USER Database On <strong>Upgrade</strong> And InstallInstallation processing will no longer modify the USER database and namespace settings on upgrade, nor will it recreateUSER database and namespace definitions if they are not present. A new install will create the USER database andnamespace by default on all platforms.The feature “server_user” is no longer visible in custom installs on Windows, but it is possible to disable the USER databaseinstallation in new install Windows by disabling the installation of feature “server_user” using command line, creating atransform, or modifying MSI package.2.1.3.16 Changes To CSP Gateway Installation For Apache On UNIX®UNIX® installation scripts will no longer update the external web server configuration if it was already configured for CSPGateway. If the web server was not previously configured for CSP Gateway, the new configuration will use the sharedmodules mechanism rather than the CGI-based mechanism used by default in previous versions. This change affects theregular UNIX® installer, the CSPInstall standalone CSP Gateway installation script, and RPM and DMG installations.The CSP Gateway installation process will not change a web server configuration when it detects that the web server wasalready configured for CSP Gateway. The current detection mechanism consists of parsing the Apache configuration filefor the string “/csp” in any line not started with a comment character(#). If the installer detects that the web server waspreviously configured for CSP Gateway, it produces a message stating that any required re-configuration should be donemanually. Nonetheless, it still upgrades CSP Gateway binary files as needed.2.1.3.17 Configuration File ChangesSTU Parameter RemovedThe STU=1 parameter in the CPF file has been removed. To start the system for maintenance, use the Emergency Startupoption.Emergency Startup has been enhanced so:• Neither TASKMGR, Shadowing, Mirroring, nor (if applicable) Ensemble productions are started.• ZSTU,%ZSTART,%ZSTOP,ZSHUTDOW are not run when the system starts or stops.• User processes which log in using the emergency id do not run %ZSTART or %ZSTOP.2KB Buffer Allocation ReassignedIn the [config], section, if space is allocated for 2KB buffers in the globals= declaration, an amount of memory equalto the same number of 8KB buffers will be added to that allocated for 8KB buffer, and the 2KB allocation will be ignored.In the [Startup] sections, if the DBSizesAllowed parameter had an entry for 2KB buffers, this will be removed.MirrorSet Options ExpandedIn the [MirrorSetMembers] section, the new parameters ConnectTo and MemberType have been added. Each parameterallows for the following values: AgentAddress, AgentPort, ConnectsTo, ECPAddress, GUID,InstanceDirectory, MemberType, MirrorAddress, MirrorSSPort, Reserved.Method For Retrieving / Storing Mirror Client Name For SSL Authentication ChangedThe handling of SSL identification fields in mirroring has been revised. Commas no longer need to be converted to slashes,and fields no longer need to be re-ordered for comparison. This change can affect applications trying to use a certificatewhere the Subject field contains slashes (/) in the data. The DN fields are now base64 encoded when stored in the .cpf fileto avoid issues of commas in the data within a comma delimited field.<strong>Caché</strong> <strong>Upgrade</strong> <strong>Checklists</strong> 11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!