Installation Instructions for Hot Fix A25003

64-bit Enabled Solaris


Hot fix A25003 addresses the issue(s) in SAS Fair Banking 4.1 on 64-bit Enabled Solaris as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/A25.html#A25003


This hot fix contains updates to the following software components:

SAS Fair Banking Mid-Tier 4.1
SAS Fair Banking Server 4.1

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 software components and release numbers should match the list of software components updated by the individual hot fix installers.


IMPORTANT NOTES

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

  2. You must have Administrator Privileges on your CLIENT or SERVER machine.

  3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

  4. This hot fix should be installed using the same userid who performed the initial software installation.


INSTALLATION


The installer downloaded is A25003s6.bin. Copy A25003s6.bin to each 64-bit Enabled Solaris machine on which SAS Fair Banking 4.1 components are installed.

To install the hot fix, on each machine:

1. Verify that the installation binary has execute permission. If it does not, use the chmod command to make it executable.

$> chmod 755 A25003s6.bin
2. Set your $DISPLAY environment variable
export DISPLAY=<your_node_name>:0
3. Execute A25003s6.bin
<path_to_downloaded_file>/A25003s6.bin
    For example:
./A25003s6.bin

This will initiate the installation wizard, which will guide you through the hot fix installation process. During the installation you will be prompted for the SASHOME location to be updated. You should provide the path to the top level SAS directory where the deploymntreg directory exists.

The installation process will determine which components of SAS Fair Banking 4.1 are installed on the machine, and apply the appropriate updates.

If components of this product are installed on multiple operating systems, you must download the hot fix for the appropriate operating system(s) and follow the installation instructions provided to complete the deployment of this hot fix.


See the Maintenance Installation Tool (MIT) documentation for more details on the installation of hot fixes.


This completes the installation of A25003. Please perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.


POST-INSTALLATION INSTRUCTIONS

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

SAS Fair Banking Mid-Tier 4.1
SAS Fair Banking Server 4.1


SAS Fair Banking Mid-Tier 4.1

This hot fix requires post-installation steps that will update the web application deployed to your application server.


Step 1: Re-build Web Applications

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

1.1 Set the DISPLAY environment variable, for example

$ export DISPLAY=<displayname>:0

1.2 Invoke the SAS Deployment Manager 9.2

From the SASDeploymentManager directory execute config.sh, for example

$ cd <SASHOME>/SASDeploymentManager/9.2
$ ./config.sh

1.3 Select a language in the Choose Language box

1.4 Select Rebuild Web Applications

1.5 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

1.6 Specify Connection Information, including the sasadm User ID and Password

1.7 Select SAS Fair Banking 4.1 as the Web Application to Rebuild

1.8 Verify the information on the Summary screen and select Start

1.9 Select Finish when the deployment is complete


This process will update the SAS Fair Banking ear in <SASCONFIGDIR>Web\Staging. A backup of the original ear file will be placed in the Backup directory.


Step 2: Upgrade customized cds.properties (CDS only)

If you have a customized cds.properties file, add the following line to your cds.properties.

    CDSManagementService.no.access.txt=You will not have access to this record after it is saved based off your group
    permissions. You therefore cannot save this record.
Then replace the same file in sas.solutions.fairbanking.ear in <SASCONFIGDIR>\Web\Staging.


Step 3: Re-deploy Web Applications

3.1 Re-deploy the web applications based on the instructions in SAS Web Application Administration Guide, Chapter 8, for the web application server you are using.


Step 4: Enhance workflow definition (CDS only)
This step can be skipped if A25002 was previously applied

For the problem described in SAS Note 36892 , additional validation is added to make sure that the users are only saving the CDS records which they have the permission to access. This user permission validation test is always executed when the user tries to save a CDS record. However, if this validation needs to be done at the screen level, follow the steps below to enhance the workflows.

4.1 Refer to SAS Fair Banking 4.1 Administrator's Guide, Chapter 2: Workflow Administration to download the current workflow definition files using the “Download the workflow” icon in Actions in the Community Development section of the Administration tab.

4.2 Add the following code to the workflow definition files.

<validation test="IsRecordAccessible()">
<errmsg>
    You will not have access to this record after it is saved based
    off your group permissions. You therefore cannot continue.
</errmsg>
</validation>
    For example, in the sample loans.xml, the section for screen-level validations for GE0010 & GE0015 may look like this:
<!-- Screen-level validations -->
<validation test="not empty(SOURCE_SYSTEM_CD)">
<errmsg>Source system not found for the specified region and application ID.</errmsg>
</validation>
<validation test="IsRecordAccessible()">
<errmsg>
    You will not have access to this record after it is saved based
    off your group permissions. You therefore cannot continue.
</errmsg>
</validation>
4.3 Refer to SAS Fair Banking 4.1 Administrator's Guide, Chapter 2: Workflow Administration to upload the modified workflow definition files.


SAS Fair Banking Server 4.1

HMDA/CRA Install only
This step can be skipped if A25002 was previously applied

1.       Back up the existing Fair Banking solution

2.       Copy <sasroot>\hmdamva\sashelp\*.*  to <rootpath>\global\custom\parameter

3.       Copy <sasroot>\hmdamva\sasmisc\data_model\l_yyyys\* to <rootpath>\global\install\ddl\sas

4.       Copy <sasroot>\hmdamva\sasmisc\data_model\l_ext\* to <rootpath>\global\install\ddl\sas

5.       Copy <sasroot>\hmdamva\sasmisc\setup\* to <rootpath>\global\install\setup

6.       Copy <sasroot>\hmdamva\sasstp\sfb_autoexec_all.sas to  <rootpath>\global\control

7.       Start up Fair Banking SAS environment and run the following codes.

      %inc "&rootpath\global\install\setup\load_job_list.sas"; 

%sfb_rate_job_driver ;

           %inc "&rootpath\global\install\setup\load_columns.sas"; 

              %apply_app_detail_ddl(hmda_or_cra=HMDA);

 

8.       If HMDA data has been loaded before the hotfix is installed, run the following macro for the current submission year. 

              %apply_edits_to_master(hmda_or_cra=HMDA);

           %sfb_reporting_job_driver;

 

9.       Verify the installation.

a.       L_SYS.L_FORMAT_CNTL should have a record with FOR_COLUMN=’FIXED_MORTGAGE_FLG’

b.      L_SYS.L_COUNTY_CODE should not have records with county_desc contains ‘(CA)’.

c.       CNTL.JOB_LIST should have a record with MACRO_CALL=’sfb_rate_job_driver’

d.      L_EXT.EXT_RATE_ARM and L_EXT.EXT_RATE_FIXED should have a lot of records.

e.      CNTL.COLUMNS should have records with NAME in (‘FIXED_MORTGAGE_FLG’ , ‘LOAN_TERM_FIXED_FOR_ARM’ , ‘PRIME_RATE_USED_RT’ ‘PRIME_RATE_USED_DT’)

f.        L_<yyyy>s.APP_HMDA_DETAIL_CURR/ERR/AUDIT tables should have columns FIXED_MORTGAGE_FLG, LOAN_TERM_FIXED_FOR_ARM,  PRIME_RATE_USED_RT, and PRIME_RATE_USED_DT.

g.       Columns FIXED_MORTGAGE_FLG and LOAN_TERM_FIXED_FOR_ARM are added to the current year HMDA correction spreadsheets in <rootpath>\ C:\sas\SFBEntBI\Lev1\Applications\SASFairBanking\4.1\web_imart\error_download\hmda if the spreadsheets exist.

 

Enhance CDS geocoding (CDS only)

The problem described in SAS Note 38307 , requires a customized Dataflux service job that can geocode a street address spanning 2 lines.
Follow the steps below to switch to your customized job.

Copy your customized DataFlux service job to:
<DATAFLUXHOME>/DIS/8.1/svc_job (rename the file to include the .dmc extension).

Modify the following line in   <SASCONFIGDIR>/Lev1/Applications/SASFairBanking/4.1/global/control/sfb_autoexec_all.sas

    call symputx('dfservice','SASFairBanking_AddressVerify_Geocoding');

to replace 'SASFairBanking_AddressVerify_Geocoding’ with your new service job name.

Restart all SAS services.

 

Update the CDS data model

Start up SAS Fair Banking and run the following codes.

proc sql;
alter table cds.cds_record_geo_alloc
add STATEWIDE_ALLOCATION_FLG CHAR(1) label='Statewide allocation flag';
insert into cds.cds_allocation_type values ('MX' 'Multiple assessment area and Statewide' 5);
Restart all SAS services.


This completes the installation of hot fix A25003 on 64-bit Enabled Solaris.