Installation Instructions for Hot Fix J7H010
Linux for x64
Hot fix J7H010 addresses the issue(s) in SAS Studio 3.81 as documented
in the Issue(s) Addressed section of the hot fix download page:
https://tshf.sas.com/techsup/download/hotfix/HF2/J7H.html#J7H010
J7H010 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
J7G010 updates SAS Studio Basic 3.81
J7F010 updates SAS Studio Mid-Tier 3.81
See What is a container hot fix?
in the Hot Fix FAQ for more information about container hot fixes.
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, J7H010pt.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
J7H010pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of J7H010pt.zip. The hot fix installation process will extract the contents
as needed.
IMPORTANT NOTES
-
Files delivered in this hot fix will be backed up during the installation process.
However, it is good general practice to back up your system before applying updates
to software.
-
You must have Administrator Privileges on your CLIENT or SERVER machine.
-
All currently active SAS sessions, daemons, spawners and servers must be terminated
before applying this hot fix.
-
This hot fix should be installed using the same userid who performed the initial
software installation.
-
CONFIGURATION: No automatic configuration scripting is included for this hot fix. If you have previously configured software installed,
the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options.
On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically
selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended
consequences when applying this hot fix.
INSTALLATION
Hot Fix J7H010 must be installed on each machine where the updated components of the product, listed above, are installed.
During the installation process you may see references to all operating systems for which updates
are provided in the hot fix. The installation process will determine the operating system and which
component(s) of SAS Studio 3.81 require updating on the machine. See
SAS Note 44810 for more details.
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 J7H010pt.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.log
for 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 SAS Studio Enterprise (Mid-Tier), this hot fix requires post-installation steps that will update the web
application deployed to your application server. Follow the steps documented in the rebuild_redeploy_webapp doc
to update and deploy the web application.
- Please ensure all users clear cookies and cache from any web browser they are using. In addition, Chrome may need the 'Hosted app data' cleared.
- Update SAS Studio Basic config.properties:
- To determine the location of the config.properties file in your SAS Studio deployment, consult the SAS Studio 3.8 Admin Guide for instructions on editing configuration settings:
https://go.documentation.sas.com/doc/en/webeditorcdc/3.8/webeditorag/n0ke09ir9n1sdfn19f9iwz8j8z60.htm
- Before editing config.properties, create a backup copy.
- Check for the existence of the following properties (default values are shown):
webdms.allowResultsActions=true (3.8 and 3.81 releases)
webdms.showGitSSLCertPath=false (3.81 release only)
webdms.showSSHGitPassword=true (3.8 and 3.81 releases)
webdms.maxLogLinesThreshold=-1 (3.8 and 3.81 releases)
- Add the appropriate entries at the bottom of your config.properties file if they are not already present. Assign the true/false value of each based on the needs of your organization.
- Save and close the config.properties file.
- Restart the SAS Studio services: SASStudioSpawner, SASStudioWebAppServer.
- Sign in to SAS Studio. If you changed the default values, confirm that the application behavior is as expected per documentation.
This completes the installation of hot fix J7H010 on Linux for x64.
Copyright SAS Institute Inc. All Rights Reserved.