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
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, T72010pt.zip, 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 T72010pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of T72010pt.zip. The hot fix installation process will extract the contents as needed.
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 T72010pt.zip, 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
<!SASHOME>/InstallMisc/InstallLogs/IT_date-and-time-stamp.logfor 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:
Follow the manual steps below:
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:
This is followed by several lines of comments, which end at line 964:
Follow these steps if you have SAS Anti-Money Laundering:
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.
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
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.