Caché Upgrade Checklists - InterSystems Documentation

Caché 2010.2 Upgrade Checklist2. If the file is not of a character type, the charset will always be set to “ ” for binary files.3. If ^%SYS(“CSP”, “DefaultFileCharset”) is defined, then this is the charset to use when serving files.4. If this is a Unicode installation, Caché will use the default file character translate table.5. On 8–bit installations, Caché will use the system default charset.4.2.7.2 CGI Variable SERVER_NAMEThe CGI environment variable SERVER_NAME is now in the set of fields that are placed at the beginning of the first requestdata block dispatched to Caché. This is to enable the CSP server in Caché to identify the application early in the requestprocessing cycle. The order of the first three fields in the data block is now as follows:1. Session ID (CSPCHD)2. CGI environment variable, SERVER_NAME3. Request path/file (CSPLIB)4.2.7.3 Properly Handle Session Id Between Secure And Non-Secure PagesIf a page loaded via an http link itself has a link to an https page, Caché will now not include the CSPCHD SessionId. Thisis true even if token-based session management is in effect, or if this is the initial page of a session and autodetection logicis active.Note:This may be overridden with the CSPSHARE=1 parameter to regain the previous behavior, but is not recommended.Applications should not be sharing a session between secure and insecure pages as this could be a security riskleaking information from the secure pages to the non-secure ones.4.2.8 XML Changes4.2.8.1 Use Caché InitialExpression To Represent XML Schema Fixed AttributesCaché now represents the fixed attribute for elements and attributes in an XML schema using the InitialExpression keywordin Caché classes created by the XML schema wizard. If an application is depending on being able to determine if a fixedelement or attribute has been specified, it will no longer be able to do this.Note:The ability to determine whether an attribute has been specified violates the spirit and letter of the rules for attributeusage in XML. Also, this is not a complete implementation of fixed attributes since the value may later be changed.4.2.8.2 XMLImport Efficiency ChangesXMLImport has been changed to process child elements more efficiently rather than the previous method of recursivelyprocessing subtrees. Users who have applications that override XMLImport may be required to redesign some of theirapplication processing.4.2.9 Web Services Changes4.2.9.1 Correct Handling Of MIME PartsThis version corrects an error in the handling of messages with MIME parts present in prior versions. If the WSDL specifiesdocument/literal and MakeMessageStyle=1 (message format which allows multiple parts), Caché now creates the partswhich correspond to MIME content if they are called for by the soap:body element of the . Priorversions incorrectly ignored all MIME parts, even if they were in the parts list or defaulted to the parts list.88 Caché Upgrade Checklists