Hot fix G38012 addresses the issue(s) in SAS Middle Tier 9.3_M1 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/G38.html#G38012
G38012 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as indicated.
G42011 updates SAS Configuration Manager 9.3_M1
G92010 updates SAS Intelligence Platform Object Framework 9.1_M1
G41006 updates SAS Shared Services 9.3_M1
G37012 updates SAS Web Infrastructure Platform 9.3_M1
H83001 updates SAS/SECURE Java Component 9.3_M1
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, G38012pt.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 G38012pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of G38012pt.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 G38012pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: User’s Guide.
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.
For each product installed, click the link to be redirected to post-installation instructions.
G42011 updates SAS Configuration Manager 9.3_M1
G92010 updates SAS Intelligence Platform Object Framework 9.1_M1
G41006 updates SAS Shared Services 9.3_M1
G37012 updates SAS Web Infrastructure Platform 9.3_M1
H83001 updates SAS/SECURE Java Component 9.3_M1
G42011 updates SAS Configuration Manager 9.3_M1
NONE
G92010 updates SAS Intelligence Platform Object Framework 9.1_M1
NONE
G41006 updates SAS Shared Services 9.3_M1
Step 1: Re-build Web Applications
In order for this step to execute correctly, the Metadata Server must be running.
1.1 Set the DISPLAY environment variable, for example
$ export DISPLAY=<displayname>:0
1.2 Invoke the SAS Deployment Manager 9.3
From the SASDeploymentManager directory execute sasdm.sh, for example
$ cd <SASHOME>/SASDeploymentManager/9.3
$ ./sasdm.sh
1.3 Select a language in the Choose Language box
1.4 Select Rebuild Web Applications
1.5 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
1.6 Specify Connection Information, including the sasadm User ID and Password
1.7 Select SAS Web Infrastructure Platform 9.3 as the Web Application to Rebuild
1.8 Verify the information on the Summary screen and select Start
1.9 Select Finish when the deployment is complete
This process will update the SAS Web Infrastructure Platform ears in <CONFIGDIR>/Lev1/Web/Staging and place the updated exploded ears in <CONFIGDIR>/Lev1/Web/Staging/exploded. The SAS Web Infrastructure Platform ears include:
Step 2: Re-deploy Web Applications
2.1 Re-deploy the updated ears listed above to the web application server you are using based on the instructions appropriate for your web application server. See SAS 9.3 Intelligence Platform Middle-Tier Administration Guide, Chapter 7, for more details.
G37012 updates SAS Web Infrastructure Platform 9.3_M1
Step 1: Re-build Web Applications
In order for this step to execute correctly, the Metadata Server must be running.
1.1 Set the DISPLAY environment variable, for example
$ export DISPLAY=<displayname>:0
1.2 Invoke the SAS Deployment Manager 9.3
From the SASDeploymentManager directory execute sasdm.sh, for example
$ cd <SASHOME>/SASDeploymentManager/9.3
$ ./sasdm.sh
1.3 Select a language in the Choose Language box
1.4 Select Rebuild Web Applications
1.5 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
1.6 Specify Connection Information, including the sasadm User ID and Password
1.7 Select SAS Web Infrastructure Platform 9.3 as the Web Application to Rebuild
1.8 Verify the information on the Summary screen and select Start
1.9 Select Finish when the deployment is complete
This process will update the SAS Web Infrastructure Platform ears in <CONFIGDIR>/Lev1/Web/Staging and place the updated exploded ears in <CONFIGDIR>/Lev1/Web/Staging/exploded. The SAS Web Infrastructure Platform ears include:
Step 2: Re-deploy Web Applications
2.1 Re-deploy the updated ears listed above to the web application server you are using based on the instructions appropriate for your web application server. See SAS 9.3 Intelligence Platform Middle-Tier Administration Guide, Chapter 7, for more details.
H83001 updates SAS/SECURE Java Component 9.3_M1
NONE
This completes the installation of hot fix G38012 on Solaris for x64.
Copyright 2015 SAS Institute Inc. All Rights Reserved.