POST-INSTALLATION INSTRUCTIONS for hot fix A23003 on 64-bit Enabled Solaris

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