Hot fix M2K014 addresses the issue(s) in SAS Middle Tier 9.4_M8 as documented
in the Issue(s) Addressed section of the hot fix download page:
https://tshf.sas.com/techsup/download/hotfix/HF2/M2K.html#M2K014
M2K014 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
M2I014 updates SAS Configuration Manager 9.4_M8
M2H014 updates SAS Foundation Services 9.4_M8
M2G014 updates SAS Intelligence Platform Object Framework 9.4_M8
M2F014 updates SAS Web Infrastructure Platform 9.4_M8
Before applying this hot fix, follow the instructions in SAS KB0036131 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, M2K014pt.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 M2K014pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of M2K014pt.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 M2K014pt.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.
Hot Fix Post Installation steps to Rebuild and Redeploy Web Applications
This hot fix requires post-installation steps that will update the web application deployed to your application server, and move updated files so delivered fixes are surfaced.
Rebuild and Redeploy Web Applications
NOTE: In order for this step to execute correctly, the Metadata Server must be running.
- Rebuild Web Applications
Select the appropriate product as the Web Application to Rebuild; it is recommended that you rebuild and redeploy all of the web applications after applying this hot fix.
- 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".
- Redeploy Web Applications-- Redeploy the updated wars to the web 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.
This completes the installation of hot fix M2K014 on 64-bit Enabled Solaris.
Copyright SAS Institute Inc. All Rights Reserved.