Hot fix H33001 addresses the issue(s) in SAS IT Resource Management 3.3 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/H33.html#H33001
H33001 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as indicated.
H29001 updates SAS IT Management Solutions Core Components Data JAR Files 3.3
H32001 updates SAS IT Resource Management Client 3.3
H30001 updates SAS IT Resource Management Data Configuration 3.3
H31001 updates SAS IT Resource Management Data Tier 3.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, H33001pt.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 H33001pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of H33001pt.zip. The hot fix installation process will extract the contents as needed.
The hot fix will be applied using the SAS Deployment Manager (SDM). By default, the SDM 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 H33001pt.zip, follow the instructions provided in the SAS Deployment Wizard/SAS Deployment Manager 9.3: User’s Guide; see the Applying Hot Fixes for Windows and UNIX section in Chapter 5 -- SAS Deployment Manager Tasks to complete the installation of the hot fix.
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.
H29001 updates SAS IT Management Solutions Core Components Data JAR Files 3.3
H32001 updates SAS IT Resource Management Client 3.3
H30001 updates SAS IT Resource Management Data Configuration 3.3
H31001 updates SAS IT Resource Management Data Tier 3.3
H29001 updates SAS IT Management Solutions Core Components Data JAR Files 3.3
NONE
H32001 updates SAS IT Resource Management Client 3.3
NONE
H30001 updates SAS IT Resource Management Data Configuration 3.3
NONE
H31001 updates SAS IT Resource Management Data Tier 3.3
Update SAS IT Resource Management Metadata
In order for this step to execute correctly, the Metadata Server must be running. Please start your Metadata Server now.
You should be logged into the machine hosting your SAS IT Resource Management SAS Application Server using the same userid that
was used for both your original and hot fix installations.
Ensure that an X11 DISPLAY variable has been properly set and exported. Also inspect the level_env.sh script file located
<SAS Configuration Directory>/Levelto confirm whether a JDK_HOME environment variable is being defined. If you do not see a line specifying "JDK_HOME=" then you need to set the JDK_HOME variable from the command line prior to invoking the script specified below. The setting should be to an installed, compatible JDK, and should not include the "/bin" portion of the path.
Change directory to the installation location of the SAS IT Resource Management Data Tier component. This should be
<SASHOME>SASITResourceManagementDataTier/3.3
The script to update the SAS IT Resource Management metadata is named applyHotFix.sh
and it requires two positional
parameters to be passed to it. The first is the password for the SAS administrative user id. The second is the SAS Configuration
Directory path including the Level subdirectory. The syntax for invoking this script is:
applyHotFix.sh <metaPass> <SASConfigDir>
For example,
applyHotFix.sh AdminAdmin1 /install/ITRM33/Lev1
Note: if your configuration directory path contains a space (embedded blank) you must enclose the entire path in double quotes ("path with blanks").
During the execution of this script you should see messages similar to the following output to your shell:
Output from this script is redirected to the log file: itrmhotfix.logand the output from this task will be written to the
Buildfile: /install/SAS/SASITResourceManagementDataTier/3.3/Config/itrmhotfix.xml
applyHotFix.sh has completed.
itrmhotfix.log
file. This log file is located in the same directory
that the script was invoked from.After successful execution the final lines of this log file will be similar to:
BUILD SUCCESSFULNote: If you do not see the
Total time: 45 seconds
BUILD SUCCESSFUL
message you should contact SAS Technical Support.
This completes the installation of hot fix H33001 on 64-bit Enabled HP-UX.