Installation Instructions for Hot Fix J3H002

Solaris for x64

Hot fix J3H002 addresses the issue(s) in SAS Portal and Portlets 4.4_M7 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/J3H.html#J3H002

J3H002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.

J3G002  updates  SAS BI Portlets 4.4_M7
J3F002  updates  SAS Information Delivery Portal 4.4_M7

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, J3H002pt.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 J3H002pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of J3H002pt.zip. The hot fix installation process will extract the contents as needed.

IMPORTANT NOTES

1. 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.

2. You must have Administrator Privileges on your CLIENT or SERVER machine.

3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

4. This hot fix should be installed using the same userid who performed the initial software installation.

5. 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

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 J3H002pt.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

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.

POST-INSTALLATION INSTRUCTIONS

This hot fix requires post-installation steps. Follow the steps below to complete the installation of all updates.

1. Rebuild Web Applications

   NOTE: In order for this step to execute correctly, the Metadata Server must be running.

   1. If you are installing this hot fix on a UNIX system, set the DISPLAY environment variable.
      For example:

      $ export DISPLAY=<displayname>:0

   2. Invoke the SAS Deployment Manager 9.4

      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.

   3. Select a language in the Choose Language box

   4. Select Rebuild Web Applications

   5. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

   6. Specify Connection Information, including the sasadm User ID and Password

   7. Select the appropriate product as the Web Application to Rebuild

   8. Verify the information on the Summary screen and select Start

   9. Select Finish when the deployment is complete

   
   This process will update the appropriate wars in <CONFIGDIR>/Lev1/Web/Staging.
   

   A backup of the original war files will be placed in the <CONFIGDIR>/Lev1/Web/Staging/Backup directory.

2. Rebuild portlet archive file
   1. Modify <CONFIGDIR>/Lev1/Web/Utilities/runTargetScript_RebuildSASPARs.sh or run TargetScript_RebuildSASPARs.bat

   2. Supply the password for sasadm@saspw

   3. In the line containing <CONFIGDIR>/Lev1/Web/Utilities/launchconfigtarget.bat/sh, add the following argument prior to "%TARGET%" at the end

      -Dwizard.type="sdw"

   4. Save and run the script.

   Please see SAS Note 66864 for more detailed usage of URLDisplayPortlet.UrlRestrictions property.
   

3. Redeploy Web Applications

   Redeploy the updated wars to the web application server. See SAS 9.4 Intelligence Platform: Middle-Tier Administration Guide for more details.

   
   

This completes the installation of hot fix J3H002 on Solaris for x64.


Copyright 2021 SAS Institute Inc. All Rights Reserved.