Installation Instructions for Hot Fix T72010

64-bit Enabled Solaris

Hot fix T72010 addresses the issue(s) in SAS Enterprise Case Management 6.3 as documented in the Issue(s) Addressed section of the hot fix download page:

T72010 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.

T71010  updates  SAS Enterprise Case Management Mid-Tier 6.3
T70002  updates  SAS Enterprise Case Management Server 6.3

See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.

Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The release number information in the Registry report should match the 'member' release number information provided above for the software components installed on each machine in your deployment.

The hot fix downloaded,, includes the updates required for all components listed above on all applicable operating systems. To apply this hot fix on multiple machines, you can either save on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of The hot fix installation process will extract the contents as needed.


  1. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

  2. You must have Administrator Privileges on your CLIENT or SERVER machine.

  3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

  4. This hot fix should be installed using the same userid who performed the initial software installation.

  5. CONFIGURATION: No automatic configuration scripting is included for this hot fix. If you have previously configured software installed, the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options. On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended consequences when applying this hot fix.


Hot Fix T72010 must be installed on each machine where the updated components of the product, listed above, are installed. During the installation process you may see references to all operating systems for which updates are provided in the hot fix. The installation process will determine the operating system and which component(s) of SAS Enterprise Case Management 6.3 require updating on the machine. See SAS Note 44810 for more details.

The hot fix will be applied using the SAS Deployment Manager. By default, the SAS Deployment Manager will search in the <SASHOME>/InstallMisc/HotFixes/New directory for hot fixes to be applied, but will also prompt for a location if you have downloaded hot fixes to a different directory.

After downloading, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.

The hot fix installation process generates the log file

for example, IT_2011-10-31-13.18.21.log. Each attempt to apply a hot fix results in the creation of a new log file giving detailed information regarding the installation process.

Postexec log files are created after the installation is completed and identifies the files that were added, backed up, changed and removed. These log files include the 'member' hot fix id in the name of the file and are also written to the <!SASHOME>/InstallMisc/InstallLogs directory. There is one postexec log for each 'member' hot fix applied (member hot fixes are listed at the top of these instructions).

The content of this hot fix is listed in the hot fix manifest.


Update Solr deployment to add solr.PingRequestHandler

Hot fix T72010 updates the sample solrconfig.xml file found in <SASHome>/SASEnterpriseCaseManagementMidTier/6.3/deploy/sample/Solr/scripts/prepareSolr/EntCaseMgmtCollection/. This solrconfig.xml file is normally copied to the Solr installation via the “Installing Global Search” steps in the ECM Admin Guide (Chapter 4 Post-installation Requirements and Tasks).

If you have already followed the “Installing Global Search” steps, you will need to manually update the solrconfig.xml file in your Solr installation to add the same changes to it that the hot fix made to the sample. If you followed the suggested Solr installation location in the Admin Guide, the directory where you must make changes to the solrconfig.xml file will be:

Windows: \solr-4.7.2\ecm\solr\EntCaseMgmtCollection\conf
Linux: /usr/local/solr-4.7.2/ecm/solr/EntCaseMgmtCollection/conf

Follow the manual steps below:

  1. Update the solrconfig.xml file in your Solr installation. The exact steps you need to follow depend on whether you have made any customizations to solrconfig.xml in your Solr installation.

    1. If you have not made any changes to solrconfig.xml after following the “Installing Global Search” steps:
      Copy the updated solrconfig.xml from the <SASHome>/SASEnterpriseCaseManagementMidTier/6.3/deploy/sample/Solr/scripts/prepareSolr/EntCaseMgmtCollection/ directory to the ecm/solr/EntCaseMgmtCollection/conf directory of the Solr installation.

    2. If you made custom changes to the solrconfig.xml file after following the “Installing Global Search” steps:
      Edit solrconfig.xml in the ecm/solr/EntCaseMgmtCollection/conf directory of the Solr installation to add the solr.PingRequestHandler:
      <!-- ping/healthcheck --> <requestHandler name="/admin/ping" class="solr.PingRequestHandler"> <lst name="invariants"> <str name="q">solrpingquery</str> </lst> <lst name="defaults"> <str name="echoParams">all</str> </lst> <!-- An optional feature of the PingRequestHandler is to configure the handler with a "healthcheckFile" which can be used to enable/disable the PingRequestHandler. relative paths are resolved against the data dir --> <!-- <str name="healthcheckFile">server-enabled.txt</str> --> </requestHandler>

      This can appear anywhere in the file between the <config> and </config> tags, as long as it is not embedded in any other tag or comment. The suggested place to put it is with the other “admin” request handlers. While the exact line numbers in your customized solrconfig.xml may be different from the line numbers below, the following is provided to help you locate the suggested location for the new lines.

      In the original solrconfig.xml file delivered with ECM 6.3, there is a <requestHandler> tag with the name “/admin/” starting at line 942:

      <requestHandler name="/admin/" class="solr.admin.AdminHandlers"/>

      This is followed by several lines of comments, which end at line 964:

      <!-- <requestHandler name="/admin/file" class="solr.admin.ShowFileRequestHandler" > <lst name="invariants"> <str name="hidden">synonyms.txt</str> <str name="hidden">anotherfile.txt</str> </lst> </requestHandler> --> Add the new solr.PingRequestHandler XML stanza (above) after these comment lines, at line 966 in the original file.

  2. Follow the Admin Guide steps to restart Solr.
Update SAS Anti-Money Laundering deployment to enable stateless CAS ticket cache

Follow these steps if you have SAS Anti-Money Laundering:

  1. Locate the web application configuration file in the folder below

  2. Check the file to ensure it contains the change below:

    From: <sas-sso:http> <sas-sso:http-basic pattern="/rest/**"/> </sas-sso:http> To: <sas-sso:http stateless="true"> <!-- enables cas ticket-based authentication --> <sas-sso:intercept-url pattern="/rest/**" access="isAuthenticated()" /> <!-- enables basic-auth --> <sas-sso:http-basic pattern="/rest/**"/> </sas-sso:http>

  3. If the "To" section is present, skip steps 4-6

  4. Make a backup of webapp-config.xml

  5. Edit webapp-config.xml to replace the "From" section above with the "To" section above

  6. Save the change. Note that if the SAS Anti Monday Laundering web application is rebuilt or redeployed in the future, you may need to repeat this step.
Web Application Update

This hot fix requires post-installation steps that will update the web application deployed to your application server. For more information about how to rebuild and redeploy Web Applications, see the SAS® 9.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications on Rebuilding the SAS Web Applications and Redeploying the SAS Web Applications.

  1. Rebuild Web Applications

    NOTE: In order for this step to execute correctly, the Metadata Server must be running.

    Select the appropriate product as the Web Application to Rebuild

  2. Re-start all SAS sessions, daemons, spawners and servers. For more information on the proper order for starting servers, go to SAS® 9.4 Intelligence Platform: System Administration Guide, Fourth Edition and review the section entitled "Starting, Stopping and Checking the Status of Servers".

  3. Redeploy Web Applications
    Redeploy the updated wars to the web application server.

This completes the installation of hot fix T72010 on 64-bit Enabled Solaris.

Copyright 2018 SAS Institute Inc. All Rights Reserved.