Hot fix G77005 addresses the issue(s) in SAS Warranty Analysis 4.31 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/G77.html#G77005
G77005 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as indicated.
G75005 updates SAS Warranty Analysis Client 4.31
G76005 updates SAS Warranty Analysis Mid-Tier 4.31
G74003 updates SAS Warranty Analysis Server 4.31
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, G77005pt.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 G77005pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of G77005pt.zip. The hot fix installation process will extract the contents as needed.
Make backup of following set of jars and then delete any versions of them from
<SASHOME>/SASWarrantyAnalysisMidtier/4.31/Static/plugins/SWA_Eclipse_RCP
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 G77005pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: User’s Guide.
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.
G75005 updates SAS Warranty Analysis Client 4.31
G76005 updates SAS Warranty Analysis Mid-Tier 4.31
G74003 updates SAS Warranty Analysis Server 4.31
G75005 updates SAS Warranty Analysis Client 4.31
Please perform below step on all SAS Warranty Analysis Client machines after installing SWA4.31
client pieces for hotfix.
The installation of the hot fix to the SAS Warranty Analysis Client assumes that
the client is installed in
C:\Program Files\SASHome\If the client is installed in a location other than C:\Program Files\SASHome, the file
<SASHOME>\SASWarrantyAnalysisClient\4.31\configuration\config.inimust be manually modified. All occurrences of the following string
C:/Program Files/SASHome/must be changed the location to where the client is installed. Make sure to use forward slash (/) in the replaced path location. You should verify the folder <SASHOME>\SASVersionedJarRepository exists on your installation.
G76005 updates SAS Warranty Analysis Mid-Tier 4.31
1. Delete
<SASHOME>/SASVersionedJarRepository/eclipse/com.sas.app.launcher.cacheFile
In order for this step to execute correctly, the Metadata Server must be running.
1.1 Invoke the SAS Deployment Manager 9.3
From the SASDeploymentManager directory launch sasdm.sh.
SAS Deployment Manager is installed in the following default location:
<SASHOME>/SASDeploymentManager/9.3
1.2 Select a language in the Choose Language box
1.3 Select Rebuild Web Applications
1.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
1.5 Specify Connection Information, including the sasadm User ID and Password
1.6 Select Warranty Analysis 4.3 as the Web Application to Rebuild
1.7 Verify the information on the Summary screen and select Start
1.8 Select Finish when the deployment is complete
This process will update the SAS Warranty Analysis Mid-Tier 4.31 ear in
<CONFIGDIR>\Lev1\Web\StagingA backup of the original ear file will be placed in the Backup directory.
Step 2: Re-deploy Web Applications
Follow the steps provided for your initial Solution deployment to re-deploy the updated ear to your web application.
G74003 updates SAS Warranty Analysis Server 4.31
From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/smd/analysisoptionattributes_nls.smd
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/smd
From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/swa43_migration.sql
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install
From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/swa42_migration.sql
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install
From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/swa431_hotfix.sas
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install
From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/swa431_migration.sql
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install
From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/util_allocWARRUSER.sas
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/templates
From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_LineOverlay.sas
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/templates
From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/configure/analysisoptions.csv
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/configure
From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/interactionxml/analysisSetup.xml
Merge With: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/interactionxml/analysisSetup.xml
To do a manual merge, open the existing analysissetup.xml and the updated analysissetup.xml in
side-by-side text editor windows. Compare section by section. If the existing analysissetup.xml
has been heavily customized for your installation, the interaction sections in the 2 files may not
correspond well. If that is the case, then add the following 3 interaction sections to the end of
your existing file. If the 2 files do basically match, then when you reach line 328 in the updated file,
the following 3 interaction sections should be inserted into the existing file following the interaction
section just prior that matches. Please contact SAS Technical Support if you have questions about this step.
<Interaction>
<!--
//If Exposure Type = Usage
// Disable Apply Usage Profile and set to Yes
// Disable Calculation Method and set to Adjusted
// Disable Warranty Usage Max Mileage combo box
//End If
-->
<FieldSelected fieldId="AOA163">
<Value label="Usage">USAGE</Value>
</FieldSelected>
<Field fieldId="AOA5" fieldVisibility="DISABLED" requiresValue="true" minSelections="1" maxSelections="1">
<SelectedValue>True</SelectedValue>
</Field>
<Field fieldId="AOA30" fieldVisibility="DISABLED" requiresValue="true" minSelections="1" maxSelections="1">
<SelectedValue>projected</SelectedValue>
</Field>
<Field fieldId="AOA8" fieldVisibility="DISABLED" requiresValue="true" minSelections="1" maxSelections="1">
<SelectedValue>100000-UNLIMITED</SelectedValue>
</Field>
<Field fieldId="AOA134" fieldVisibility="DISABLED" requiresValue="true" minSelections="1" maxSelections="1">
<SelectedValue>frombuild</SelectedValue>
</Field>
</Interaction>
<Interaction>
<!--
//Applicable to Summary Tables
//If Exposure Type = TIS
// Enable Apply Usage Profile and set to Yes
// Enable Calculation Method and set to Adjusted
// Enable Warranty Usage Max Mileage combo box
//End If
-->
<FieldSelected fieldId="AOA163">
<Value label="TIS">TIS</Value>
</FieldSelected>
<Field fieldId="AOA5" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
<SelectedValue>True</SelectedValue>
</Field>
<Field fieldId="AOA30" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
<SelectedValue>projected</SelectedValue>
</Field>
<Field fieldId="AOA8" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
<SelectedValue>36000</SelectedValue>
</Field>
<Field fieldId="AOA134" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
<ResetField keepCurrentValuesIfValid="true"/>
</Field>
</Interaction>
<Interaction>
<!--
//Applicable to Summary Tables
//If Exposure Type = none
// Enable Apply Usage Profile and set to Yes
// Enable Calculation Method and set to Adjusted
// Enable Warranty Usage Max Mileage combo box
//End If
-->
<FieldSelected fieldId="AOA163">
<NoValues/>
</FieldSelected>
<Field fieldId="AOA5" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
<SelectedValue>True</SelectedValue>
</Field>
<Field fieldId="AOA30" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
<SelectedValue>projected</SelectedValue>
</Field>
<Field fieldId="AOA8" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
<SelectedValue>36000</SelectedValue>
</Field>
<Field fieldId="AOA134" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
<ResetField keepCurrentValuesIfValid="true"/>
</Field>
</Interaction>
<CONFIGDIR>/Lev1/SASApp/SASEnvironment/SASWarrantyAnalysis4.3/SASMacro/util_allocWARRUSER.sasand replace this section of code:
%util_assignUserLibname(p_username=&l_personname,
p_libname=WARRUSER, p_subDirPath=filteredData,
p_options=%str(access=readonly));
With this section of code:
/* *****************************************************
* not using this call because it will create the directory if it does not exist;
%util_assignUserLibname(p_username=&l_personname,
p_libname=WARRUSER, p_subDirPath=filteredData,
p_options=%str(access=readonly));
***************************************************** */
%global g_serverPath g_guarc; /* cis: S0796738 */
%local l_dirpath nummems;
%let nummems = 0;
%util_getuserattributes(p_personomrname=&l_personname,
servername_mv=g_servername,
serverpath_mv=g_serverPath
);
%if &g_guarc EQ 0 %then /* user's data directory exists in the PARMSL.USERATTRIBUTES table */
%do;
%let l_dirpath = &g_serverPath.&g_slash.filteredData;
data _null_;
rc = filename("tempdir", "&l_dirpath");
dirid = dopen("tempdir");
if dirid GT 0 then
members = dnum(dirid);
dirid = dclose(dirid);
call symput("nummems",members);
run;
%if &nummems GT 0 %then /* USERFDL physical directory exists and contains data */
libname WARRUSER "&l_dirpath" access=readonly;
%end;
/* -------------------------------------- */
<CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/sasv9_swaconn.cfgto ensure that the USERTL library reference is properly assigned.
<CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/sasv9_swaconn.cfgto ensure that the PARMSL library reference is properly assigned.
"<CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/swa431_hotfix.sas"in your interactive SAS session, and it will update the PARMSL datasets.
This completes the installation of hot fix G77005 on 64-bit Enabled Solaris.