Installation instructions for hot fix G77007 on 64-bit Enabled AIX

Installation Instructions for Hot Fix G77007

64-bit Enabled AIX

Hot fix G77007 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#G77007

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

G75007 updates SAS Warranty Analysis Client 4.31
G76007 updates SAS Warranty Analysis Mid-Tier 4.31
G74003 updates SAS Warranty Analysis Server 4.31

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

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

SAS Warranty Analysis Mid-Tier 4.31

Make backup of following set of jars and then delete any versions of them from

<SASHOME>/SASWarrantyAnalysisMidtier/4.31/Static/plugins/SWA_Eclipse_RCP

sas.analytics.mfg.queue.client
sas.analytics.mfg.warranty.app
sas.analytics.mfg.warranty.core.client
sas.graph.silk
sas.graph.statgraph.nls
sas.graph.statgraph
sas.swing

INSTALLATION

Hot Fix G77007 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 Warranty Analysis 4.31 require updating on the machine. See SAS Note 44810 for more details.

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

For each product installed, click the link to be redirected to post-installation instructions.

G75007 updates SAS Warranty Analysis Client 4.31
G76007 updates SAS Warranty Analysis Mid-Tier 4.31
G74003 updates SAS Warranty Analysis Server 4.31

G75007 updates SAS Warranty Analysis Client 4.31

Configuration
Once the hotfix is installed at customer site, following is the way export to spreadsheet will behave:

If user exports any file, SWA client creates directory called 'Warranty' in logged in (OS) user's home folder, if does not exist already. All exported files are stored in this folder.
If administrator wants to configure different directory name he needs to add property 'swa.io.tmpdirname' and assign desired value.
Example:
For CD client: to change the directory name to 'SWADownloadArea' add entry '-Dswa.io.tmpdirname=SWADownloadArea' in wrtyanl.ini file
For JWS client: < property name="swa.io.tmpdirname" value="SWADownloadArea" > < /property > in SWA_Eclipse_RCP.jnlp file
If user wants to just save the file without launching it. He needs to create file 'DO_NOT_EXPORT.txt' in the above directory. In addition, with this setting, the exported file would get saved with naming convention (< AnalysisName_AnalysisType_UniqueNumber >.CSV.)
For example:
-for Details analysis having name 'DetailsTable1' the file name could be 'DetailsTable1_DETAIL_2013_06_11_05_49_23.CSV'.
-for Pareto name having name 'Pareto1' could be 'Pareto1_PARETO_2013_06_11_05_42_27.CSV'.
While downloading file from server, client downloads it in chunks. Default chunk size is 5 MB(Mega bytes). This can be altered by changing the value of property 'swa.io.chunksize'.
Example:
For CD client: to change the chunk size to '50 MB' add entry '-Dswa.io.chunksize=50' in wrtyanl.ini file
For JWS client: < property name="swa.io.chunksize" value="50" > < /property > in SWA_Eclipse_RCP.jnlp file.

Known Issue:
When this fix is applied Windows XP users will not get message due to user home directory for Windows XP contains spaces(c:\Document And Settings\UserName\). Rest of the functionality works fine. The file is downloaded in the ‘Warranty’ (or any other directory configured in step#2).

G76007 updates SAS Warranty Analysis Mid-Tier 4.31

Web application Update

Updates to the SAS Warranty Analysis Mid-Tier 4.31 provided in this hot fix require that Web Applications be rebuilt and redeployed. If this component is installed on Unix, follow the steps below to rebuild and redeploy the web application:

Remove com.sas.app.launcher.cacheFile

1. Delete

<SASHOME>/SASVersionedJarRepository/eclipse/com.sas.app.launcher.cacheFile

Step 1: Re-build Web Applications

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\Staging

A 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

The following set of instructions are only applicable if G77005 has not been applied. There are no updates for the Server Tier being delivered in this Hotfix.

The following files are delivered to the SAS install area. Take a backup of below files from configuration directory and then copy files locations mentioned below:

     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

The following file is also delivered to the SAS install area. In case given line of code does not exists in the file, this file should be manually merged with the existing file in the Config area. Otherwise ignore this step:

     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>

In case given line of code does not exists in the file, make a backup of following file and then manually edit this file. Otherwise ignore this step:

<CONFIGDIR>/Lev1/SASApp/SASEnvironment/SASWarrantyAnalysis4.3/SASMacro/util_allocWARRUSER.sas

and 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;
	/* -------------------------------------- */

Update the Graphics Templates Catalog

Make a backup of existing Graphics Template Catalog which is located in USERTL library before running below mentioned code.

Start an interactive SAS session using the configuration file
<CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/sasv9_swaconn.cfg
to ensure that the USERTL library reference is properly assigned.
Modify the path in the following code to point to your configuration directory, and modify the g_slash to run in your environment:

Options validvarname=v7;
%let g_swaConfigRoot = <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install;
%let g_slash = /;

%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTagsets_GTL.sas";
%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_BarChart.sas";
%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_BarChart_MVA.sas";
%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_BarChartOverlay.sas";
%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_ControlChart.sas";
%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_Dummy.sas";

%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_LineOverlay.sas";
%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_ProbPlot.sas";
%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_SDChart.sas";
%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_SolidDashLines.sas";
%include "&g_swaConfigRoot.&g_slash.templates&g_slash.styleTemplate_SWAStyle.sas";
%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_OverlayTrend.sas";

Note: this code was excerpted from <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/runinstall.sas.
Run this code in your interactive SAS session, and it will update the contents of your Graphics Template Catalog.

Update the PARMSL datasets

Make a backup of existing PARMSL library before running below script to update the datasets.

Start an interactive SAS session using the configuration file
<CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/sasv9_swaconn.cfg
to ensure that the PARMSL library reference is properly assigned.
Run
"<CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/swa431_hotfix.sas"
in your interactive SAS session, and it will update the PARMSL datasets.

Update the ‘init.sas’ file

Take a backup of existing ‘init.sas’ file which is located at "<CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install path. Configure the ‘g_dpi’ global variable setting in init.sas file.

Edit the init.sas file in a text editor and declare the g_dpi global variable.
Go to ‘%global’ statement and add g_dpi variable at the end of line but before the semi-colon.
Initialize the g_dpi variable.
Add the following line after the below the %global statement after semi-colon.
%let g_dpi=300;

This completes the installation of hot fix G77007 on 64-bit Enabled AIX.