Hot fix T54012 addresses the issue(s) in SAS Visual Scenario Designer 6.3 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/T54.html#T54012
T54012 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
T36012 updates SAS Visual Scenario Designer 6.3
T53002 updates SAS Visual Scenario Designer 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, T54012pt.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 T54012pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of T54012pt.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 T54012pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: 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.
T36012 updates SAS Visual Scenario Designer 6.3
T53002 updates SAS Visual Scenario Designer Server 6.3
T36012 updates SAS Visual Scenario Designer 6.3
Note that these instructions provide example filenames and directory names based on a Unix deployment; if your deployment is
to a different host OS please make the appropriate adjustments.
Copy scdmid_default.properties
Step 1: Backup the scdmid_default.properties under the SASHome and SASDepot locations.
<SASHome>/SASDeploymentManager/9.4/product_data/scdmid__94120__prt__xx__sp0__1/configure <SASDepot>/product_data/scdmid__94120__prt__xx__sp0__1/configure
Web application Update
This hot fix requires steps that will update the web application deployed to your application server.
Step 1: Stop SAS Services
For information about stopping and restarting the server, depending on your operating system, see Chapter 6 “Operating Your Servers”
in
SAS 9.4 Intelligence Platform: System Administration Guide.
Step 2: Re-build Web Applications
This process will update the SAS Visual Scenario Designer war in
<CONFIGDIR>/Lev1/Web/Staging.
and a backup of the original war file will be placed in the
<CONFIGDIR>/Lev1/Web/Staging/Backup directory.In order for this step to execute correctly, the Metadata Server must be running.
2.1 Invoke the SAS Deployment Manager 9.4
From the SASDeploymentManager directory launch sasdm.sh. The default installation path for the SAS Deployment Manager is
<SASHOME>/SASDeploymentManager/9.42.2 Select a language in the Choose Language box
2.3 Select Rebuild Web Applications
2.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
2.5 Specify Connection Information, including the sasadm User ID and Password
2.6 Select Visual Scenario Designer 6.3 as the Web Application to Rebuild
2.7 Verify the information on the Summary screen and select Start
2.8 Select Finish when the deployment is complete
Step 3: Unzip the new war file from the staging location to the SAS Visual Scenario Designer deployment area.
3.1 Locate the war file for SAS Visual Scenario Designer in the staging directory:
<CONFIGDIR>/Lev1/Web/Staging/sas.visualscenariodesigner.war3.2 Unzip the war file created to the SAS Visual Scenario Designer deployment within SASServer7.
For example, mv the old war up one directory
mv <CONFIGDIR>/Lev1/Web/WebAppServer/SASServer7_1/sas_webapps/sas.visualscenariodesigner.war ~/Then upzip the new war file to the SASServer7_1 deployment directory.
unzip <CONFIGDIR>/Lev1/Web/Staging/sas.visualscenariodesigner.war -d <CONFIGDIR>/Lev1/Web/WebAppServer/SASServer7_1/sas_webapps/sas.visualscenariodesigner.warStep 4: Delete the work directory in SASServer7
rm -rf <CONFIGDIR>/Lev1/Web/WebAppServer/SASServer7_1/workStep 5: Delete the contents of the temp directory in SASServer7
rm -rf <CONFIGDIR>/Lev1/Web/WebAppServer/SASServer7_1/temp/*Step 6: Clear your browser cache
http://java.com/en/download/help/webcache.xml
Step 8: Restart SAS Services
For information about stopping and restarting the server, depending on your operating system, see Chapter 6 “Operating Your Servers”
in
SAS 9.4 Intelligence Platform: System Administration Guide.
T53002 updates SAS Visual Scenario Designer Server 6.3
NONE
This completes the installation of hot fix T54012 on Linux for x64.
Copyright 2017 SAS Institute Inc. All Rights Reserved.