Installation Instructions for Hot Fix C1Y007
64-bit Enabled AIX
Hot fix C1Y007 addresses the issue(s) in SAS Job Monitor 2.2_M1 as documented
in the Issue(s) Addressed section of the hot fix download page:
https://tshf.sas.com/techsup/download/hotfix/HF2/C1Y.html#C1Y007
C1Y007 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
C1X007 updates SAS Job Monitor Administration 2.2_M1
B2C001 updates SAS Job Monitor Data Server Configuration 2.2_M1
H3Z003 updates SAS Job Monitor Mid-Tier Services 2.2_M1
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, C1Y007pt.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
C1Y007pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of C1Y007pt.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 C1Y007 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 Job Monitor 2.2_M1 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 C1Y007pt.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.
This hot fix requires the following post-installation steps:
- Update the 'Is plug-in' value:
From SAS Management Console-> Application Management -> Configuration Manager -> SAS Application Infrastructure->Job Monitor Services,
set the 'Is plug-in?' value to false.
- After hotfix installation has successfully completed you must remove older jar files so only the newest version of each jar file
exists in the following installation locations:
- <SASHome>/SASJobMonitorAdministration/2.2/Static/jars/jobmonitor-hqplugin/lib
- <SASHome>/SASJobMonitorAdministration/2.2/Static/jars/jobmonitor-hqu-plugin/lib
Where <SASHome> is the file location where your SAS Software is installed on a machine.
Note that jar file naming conforms to the following pattern in these directories: <Jar-Name>-<Version-Number>_<Release>.jar
Examine all files with a common <Jar-Name> and only keep the one file with the greatest <Version-Number> value for each
<Jar-Name>.
Using the <Version-Number> is necessary because there are instances when the file creation and modification dates may not differ across jar files.
Note that jar files with a <Release> value of f1jobmt22p or 940m4f will be newer than jars with a <Release> value of m1jobmtr22
or v490m4 because <Release> values with an “f” in the name are delivered via hotfix installation.
When the clean-up process is completed the following should be true:
In <SASHome>/SASJobMonitorAdministration/2.2/Static/jars/jobmonitor-hqplugin/lib there will be one of each of the following <Jar-Name> files:
- jackson
- jobmonitor-api
- jobmonitor-common
- logparser-api
- logparser-dijob
- logparser-dmjob
- sas.svcs.security.authentication.client
- spring-web
In <SASHome>/SASJobMonitorAdministration/2.2/Static/jars/jobmonitor-hqu-plugin/lib there will be one of each of the following <Jar-Name> files:
- commons-math
- jobmonitor-api
- jobmonitor-common
- sas.core
- sas.svc.security.authentication.client
- Remove the 'Job Mntr Hyperic Plugin/SAS Job Monitor Administration' configuration:
- Stop the SAS Environment Manager service as well as all instances of SAS WebAppServer (tcServer)
- Run the SAS Deployment Manager and choose 'Remove Existing Configuration'
- Select only 'Job Mntr Hyperic Plugin/SAS Job Monitor Administration' and continue until you have unconfigured the product.
- Exit the SAS Deployment Manager when completed.
- Remove all remaining files from the following configuration directory locations:
<Config>/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/hqu/jobmonitor/lib
<Config>/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/temp/pdknull/work/lib/jobmonitor
Where <Config> is the file location where you SAS Software configuration exists.
- Remove the following files from the configuration if they exist:
<Config>/Web/SASEnvironmentManager/agent-5.8.0-EE/bundles/agent-5.8.0-EE/pdk/plugins/jobmonitor-plugin.jar
<Config>/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/hq-plugins/ jobmonitor-plugin.jar
Where <Config> is the file location where you SAS Software configuration exists.
- Reconfigure the SAS Job Monitor Administration product
- Run the SAS Deployment Wizard and choose to 'Configure SAS Software'
- Choose the plan you originally installed and when prompted for products to configure, only select 'SAS Job Monitor Administration'
- Complete the configuration and exit the SAS Deployment Wizard.
- Start the SAS Environment Manager services (Server and Agent). (The SDW should have already started the tcServers)
This completes the installation of hot fix C1Y007 on 64-bit Enabled AIX.
Copyright 2020 SAS Institute Inc. All Rights Reserved.