Installation Instructions for Hot Fix B39001

64-bit Enabled HP-UX


Hot fix B39001 addresses the issue(s) in SAS Risk Management for Banking 2.1 on 64-bit Enabled HP-UX as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/B39.html#B39001


This hot fix contains updates to the following software components:

SAS Risk Management for Banking Server 2.1
SAS Risk Management for Banking Mid-Tier 2.1
SAS Asset and Liability Management for Banking Server 2.1
SAS Credit Risk for Banking Server 2.1
SAS Firmwide Risk for Banking Server 2.1
SAS Market Risk for Banking Server 2.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 B39001h6.bin. Copy B39001h6.bin to each 64-bit Enabled HP-UX machine on which SAS Risk Management for Banking 2.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 B39001h6.bin
2. Set your $DISPLAY environment variable
export DISPLAY=<your_node_name>:0
3. Execute B39001h6.bin
<path_to_downloaded_file>/B39001h6.bin
    For example:
./B39001h6.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 Risk Management for Banking 2.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 this hot fix. Post-installation steps must be performed 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 Risk Management for Banking Server 2.1
SAS Risk Management for Banking Mid-Tier 2.1
SAS Asset and Liability Management for Banking Server 2.1
SAS Credit Risk for Banking Server 2.1
SAS Firmwide Risk for Banking Server 2.1
SAS Market Risk for Banking Server 2.1

SAS Risk Management for Banking Server 2.1

NONE

Back to Post-Installation list

SAS Risk Management for Banking Mid-Tier 2.1

Updates to the SAS Risk Management for Banking Mid-Tier 2.1 provided in this hot fix require that Web Applications be rebuilt and redeployed. If this component is installed on 64-bit Enabled HP-UX, follow the steps below to rebuild and redeploy the web application:

Step 1: Re-build Web Application

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

1.1 Invoke the SAS Deployment Manager 9.2

From the SASDeploymentManager directory launch config.sh.
SAS Deployment Manager is installed in the following default location:

<SASHOME>/SASDeploymentManager/9.2

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 SAS Risk Management for Banking 2.1 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 Risk Management for Banking 2.1 ear in <SASCONFIGDIR>/Web/Staging.
A backup of the original ear file will be placed in the directory below:

<SASCONFIGDIR>/Web/Staging/Backup

Step 2: Re-deploy Web Applications

2.1 Re-deploy the web applications based on the instructions for the web application server you are using.

Back to Post-Installation list

SAS Asset and Liability Management for Banking Server 2.1

Updates to the SAS Asset and Liability Management for Banking Server 2.1 require that files delivered in the hot fix be imported via SAS Management Console. Importing the hot fix files will overwrite existing files of the same name that have been previously imported. If customizations have been made to the original adhoc reports that you do not want to lose, you will need to rename the customized version prior importing the updated files.

Follow the steps below to import the updated files:

  1. Log on to SAS Management Console (SMC) as an Administrator. The Administrator role is required to import files via SMC.
  2. Click on the Folders tab.
  3. Navigate to SAS Folders-->System-->Applications-->SAS Risk Management for Banking-->SAS Asset and Liability Management for Banking
  4. Highlight the Live Reports folder, right click, and select Import SAS Package.
  5. Click through the import wizard, pointing to the live_reports.spk file installed into the SASHOME/misc/rmbalmmva/Config/Deployment/Packages location.
    On the same screen, select the "All Objects" radio button. Click Next.
  6. Click Finish.
  7. If the import was successful, the Live Reports folder under the SAS Market Risk for Banking tree in SMC should have an updated date.
Back to Post-Installation list

SAS Credit Risk for Banking Server 2.1

Updates to the SAS Credit Risk for Banking Server 2.1 require that files delivered in the hot fix be imported via SAS Management Console. Importing the hot fix files will overwrite existing files of the same name that have been previously imported. If customizations have been made to the original adhoc reports that you do not want to lose, you will need to rename the customized version prior importing the updated files.

Follow the steps below to import the updated files:

  1. Log on to SAS Management Console (SMC) as an Administrator. The Administrator role is required to import files via SMC.
  2. Click on the Folders tab.
  3. Navigate to SAS Folders-->System-->Applications-->SAS Risk Management for Banking-->SAS Credit Risk for Banking
  4. Highlight the Live Reports folder, right click, and select Import SAS Package.
  5. Click through the import wizard, pointing to the live_reports.spk file installed into the SASHOME/misc/rmbcriskmva/Config/Deployment/Packages location. On the same screen, select the "All Objects" radio button. Click Next.
  6. Click Finish.
  7. If the import was successful, the Live Reports folder under the SAS Market Risk for Banking tree in SMC should have an updated date.
Back to Post-Installation list

SAS Firmwide Risk for Banking Server 2.1

Updates to the SAS Firmwide Risk for Banking Server 2.1 require that files delivered in the hot fix be imported via SAS Management Console. Importing the hot fix files will overwrite existing files of the same name that have been previously imported. If customizations have been made to the original adhoc reports that you do not want to lose, you will need to rename the customized version prior importing the updated files.

Follow the steps below to import the updated files:

  1. Log on to SAS Management Console (SMC) as an Administrator. The Administrator role is required to import files via SMC.
  2. Click on the Folders tab.
  3. Navigate to SAS Folders-->System-->Applications-->SAS Risk Management for Banking-->SAS Firmwide Risk for Banking
  4. Highlight the Live Reports folder, right click, and select Import SAS Package.
  5. Click through the import wizard, pointing to the live_reports.spk file installed into the SASHOME/misc/rmbfirmmva/Config/Deployment/Packages location. On the same screen, select the "All Objects" radio button. Click Next.
  6. Click Finish.
  7. If the import was successful, the Live Reports folder under the SAS Market Risk for Banking tree in SMC should have an updated date.
Back to Post-Installation list

SAS Market Risk for Banking Server 2.1

Updates to the SAS Market Risk for Banking Server 2.1 require that files delivered in the hot fix be imported via SAS Management Console. Importing the hot fix files will overwrite existing files of the same name that have been previously imported. If customizations have been made to the original adhoc reports that you do not want to lose, you will need to rename the customized version prior importing the updated files.

Follow the steps below to import the updated files:

  1. Log on to SAS Management Console (SMC) as an Administrator. The Administrator role is required to import files via SMC.
  2. Click on the Folders tab.
  3. Navigate to SAS Folders-->System-->Applications-->SAS Risk Management for Banking-->SAS Market Risk for Banking
  4. Highlight the Live Reports folder, right click, and select Import SAS Package.
  5. Click through the import wizard, pointing to the live_reports.spk file installed into the SASHOME/misc/rmbmktmva/Config/Deployment/Packages location. On the same screen, select the "All Objects" radio button. Click Next.
  6. Click Finish.
  7. If the import was successful, the Live Reports folder under the SAS Market Risk for Banking tree in SMC should have an updated date.


This completes the deployment of hot fix B39001 on 64-bit Enabled HP-UX.