Installation instructions for hot fix J2L021 on 64-bit Enabled Solaris

Installation Instructions for Hot Fix J2L021

64-bit Enabled Solaris

Hot fix J2L021 addresses the issue(s) in SAS Middle Tier 9.4_M7 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/J2L.html#J2L021

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

J2K020 updates SAS Foundation Services 9.4_M7
J2I020 updates SAS Configuration Manager 9.4_M7
J2J020 updates SAS Intelligence Platform Object Framework 9.4_M7
I9F021 updates SAS Web Infrastructure Platform 9.4_M7

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

Do NOT extract the contents of J2L021pt.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.

PRE-INSTALLATION

This hot fix is one of four hot fixes that MUST be applied in order to fully implement High Availability with SAS Job Flow Scheduler on Linux for x64; see SAS Note 67800 The High Availability feature is added to SAS® Job Flow Scheduler for more information.
The required hot fixes include
J9K003 or later for SAS Workload Orchestrator 9.4_M7 available on
https://tshf.sas.com/techsup/download/hotfix/HF2/J9K.html#J9K003
J2L004 or later for for SAS Middle Tier 9.4_M7 available on
https://tshf.sas.com/techsup/download/hotfix/HF2/J2L.html#J2L004
K1J001 or later for SAS Job Flow 9.4_M7 available on
https://tshf.sas.com/techsup/download/hotfix/HF2/K1J.html#K1J001
I9E004 or later for SAS Management Console 9.4_M7 available on
https://tshf.sas.com/techsup/download/hotfix/HF2/I9E.html#I9E004
In order to use High Availability with SAS Job Flow Scheduler, you must apply all four of these hot fixes. If you apply any of the hot fixes but do not apply all four, SAS Job Flow Scheduler does not work, even with High Availability disabled.
This hot fix requires scripting to automatically reconfigure SAS Workload Orchestrator 9.4_M7 after the hot fix has been applied. The Apply Hot Fix and Configure SAS Hot Fix steps in the SAS Deployment Manager must be run in separate steps when applying the hot fix. You must first apply the hot fix without selecting the Configure SAS Hot Fix option. After the hot fix has been successfully applied, you need to start all the SAS servers. After the services have started, run the SAS Deployment Manager again and select "Configure SAS Hot Fix" only.

INSTALLATION

Hot Fix J2L021 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 Middle Tier 9.4_M7 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 J2L021pt.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.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.

POST-INSTALLATION INSTRUCTIONS

SAS Security Updates

SAS Security Updates are applied during the initial installation of your software. In order to maintain the latest level of security offered by SAS, security updates should be applied and/or re-applied after any changes to your software, including installation of hot fixes. The current SAS Security Updates for all releases of SAS are available at https://tshf.sas.com/techsup/download/hotfix/HF2/SAS_Security_Updates.html. Please re-apply security updates in accordance with the SAS Security Updates and Hot Fixes document available on the SAS Security Updates web page.

NOTE: If you install this hot fix, you must also install hotfix I9U002 to surface the fix documented in SAS Note 69524

Hot Fix Post Installation steps to Rebuild and Redeploy Web Applications

This hot fix requires post-installation steps that will update the web application deployed to your application server, and move updated files so delivered fixes are surfaced.

Rebuild and Redeploy Web Applications

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

- Rebuild Web Applications

Select the appropriate product as the Web Application to Rebuild; it is recommended that you rebuild and redeploy all of the web applications after applying this hot fix.

- Re-start all SAS sessions, daemons, spawners and servers.

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

- Redeploy Web Applications-- Redeploy the updated wars to the web application server.

For more information about how to rebuild and redeploy Web Applications, see the SAS® 9.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications.