13.07.2015 Views

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Caché</strong> 5.1 <strong>Upgrade</strong> Checklist11.1.22 Recommendations<strong>InterSystems</strong> has several recommendations to administrators setting up a <strong>Caché</strong> 5.1 system.11.1.22.1 Enterprise Cache Protocol (ECP)<strong>InterSystems</strong> strongly recommends the use of ECP for distrubuted systems. ECP represents a significant advance overpredecessor networking approaches such as DCP. Customers currently using DCP will see improvements in performance,reliability, availability, and error recovery by converting to ECP.11.1.22.2 Change Default Password SettingWhen installing <strong>Caché</strong> with a security setting of “Minimal”, the default passwords of all users created are set to “SYS”.<strong>InterSystems</strong> suggests strongly that the password of these users be set to a different value as soon as possible so that, eventhough the security level of the system is low, control over access is established from the start of operation.11.1.22.3 CACHELIB as Read-Only DatabaseIn <strong>Caché</strong> version 5.1, for security reasons <strong>InterSystems</strong> has made CACHELIB a read-only database. This is a change fromthe previous practice. <strong>InterSystems</strong> strongly recommends that sites maintain CACHELIB as a read-only database. Thosesite- and application-defined globals, classes, tables and so on which might previously have been placed in CACHELIBshould be moved elsewhere.11.1.23 LimitationsThe following limitations apply to <strong>Caché</strong> 5.1 or specific operating systems running <strong>Caché</strong>:11.1.23.1 Maintaining Information Coherence Across SystemsOn clustered <strong>Caché</strong> systems, it is highly desirable to maintain the same list of users, roles, applications, and so on acrossall the systems of the cluster. The initial release of <strong>Caché</strong> version 5.1 does not provide facilities for propagating changesin one system to others. This must be addressed by assuring that administrators manually make the same changes on eachsystem.11.1.23.2 Maintaining Coherence with KerberosSites using Kerberos as the authentication mechanism must manually propagate changes to the list of valid users held byKerberos to <strong>Caché</strong>. Future versions of <strong>Caché</strong> may provide mechanisms for doing this automatically but the initial releasedoes not.11.1.23.3 Consolidating Audit LogsIf a site wishes to run audit reports, or other analyses of their devising, on the audit data from several systems (for example,all the systems of a cluster), the individual audit logs must be consolidated manually.11.1.23.4 Write Image Journal FilesThe format of the WIJ (write-image journal) file has changed for <strong>Caché</strong> 5.1 to improve recovery in clustered systems. Thishas two consequences:1. If an unresolved failure remains on any system to be upgraded, be sure to restart <strong>Caché</strong> and do a recovery before youupgrade to the new version.240 <strong>Caché</strong> <strong>Upgrade</strong> <strong>Checklists</strong>

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

Saved successfully!

Ooh no, something went wrong!