Hot fix E6W002 addresses the issue(s) in SAS Portal and Portlets 4.4_M6 as documented
in the Issue(s) Addressed section of the hot fix download page:
https://tshf.sas.com/techsup/download/hotfix/HF2/E6W.html#E6W002
E6W002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
E6V002 updates SAS BI Portlets 4.4_M6
E6U002 updates SAS Information Delivery Portal 4.4_M6
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, E6W002pt.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 E6W002pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of E6W002pt.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 E6W002pt.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.
This hot fix requires post-installation steps that will update the web application deployed to your application server. Follow the steps below to rebuild and redeploy your web application.
NOTE: In order for this step to execute correctly, the Metadata Server must be running.
$ export DISPLAY=<displayname>:0
UNIX:
From the SASDeploymentManager directory execute sasdm.sh.
For example:
$ cd <SASHOME>/SASDeploymentManager/9.4
$ ./sasdm.sh
PC:
From the SASDeploymentManager directory launch sasdm.exe. The default installation path for the SAS Deployment
Manager is C:\Program Files\SAS\SASDeploymentManager\9.4.
A backup of the original war files will be placed in the <CONFIGDIR>/Lev1/Web/Staging/Backup directory.
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".
See SAS 9.4 Intelligence Platform: Middle-Tier Administration Guide for more information.
This completes the installation of hot fix E6W002 on 64-bit Enabled Solaris.
Copyright 2019 SAS Institute Inc. All Rights Reserved.