INSTALLATION INSTRUCTIONS FOR HOT FIX 45CRSK01 ON AIX 64BIT


BEFORE DOWNLOADING:

The hot fix 45CRSK01 addresses the issue(s) in 4.5 of SAS Credit Risk Management
software on AIX 64bit as documented in the "Issue(s) Addressed" section of
the hot fix download page:

   http://ftp.sas.com/techsup/download/hotfix/crsk.html#45crsk01

IMPORTANT NOTE(S):

1.  You must have SAS Credit Risk Management 4.5 installed on your 
    system before applying this hot fix.

2.  Manual steps are necessary to complete the hot fix installation after the 
    automated process completes. Therefore, it is important that you read the 
    this file before launching 45crsk01r6.exe.  



INSTALLING THIS HOT FIX:

1. Technical Support strongly suggests that you back up the files being replaced by this
hotfix.  You should always try to include the current date in the name of the backup file
created to distinguish between versions of backup files.  By doing this you will maintain
a history of the file, which will be helpful when multiple iterations of a hot fix have
been applied to the same file.  

For example,

    cp  sas.foo.jar  sas.foo.jar.07012006

where 07012006 is the date when the hot fix is applied.

The .<date> extension MUST be appended AFTER the .jar extension as it appears above 
to avoid unexpected results due to jar mismatching.

The files that should be backed up for this hot fix are listed in Step #5 below.


2. Extract the contents of 45crsk01r6.tar into a temporary directory, for 
example $HOME/tmp/45crsk01.

         $> cd $HOME
         $> mkdir tmp
	 $> cd tmp
         $> mkdir 45crsk01
         $> cd 45crsk01
         $> tar -xf $HOME/45crsk01r6.tar

    where $HOME is the location to where the tar file was downloaded.


The tar command will extract the following files to the temporary directory:

	    r64/Setup_AIX_Power
	    r64/media.inf 
	    r64/setup.jar


3.  Verify that Setup_AIX_Power has execute permission.  If it does not, use
the 'chmod' command to make it executable:


         $> cd /tmp/45crsk01/r64
         $> chmod 755 Setup_AIX_Power


4.  Initiate the installation wizard


         $>  export DISPLAY=<nodename>:0           <==== set your display

         $>  cd /tmp/45crsk01/r64 

         $>  ./Setup_AIX_Power 


This will initiate the Java install wizard.  Follow the prompts to complete the
installation.  



5.  To verify the installation of the hot fix confirm that the file(s) in the location(s)
below have been updated to the level indicated by the date provided:

     <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk/httpfilters/SecurityFilter.class 
                  Date: 03/05/09  (EST)

     <CMHOME>/webapps/criskm//WEB-INF/classes/com/sas/ets/creditrisk/ResourceKeysCreditrisk.class
                  Date: 03/05/09 (EST)

     <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk/ApplicationResources.properties 
                  Date: 02/26/09 (EST)

     <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk/ApplicationResources_en.properties 
                  Date: 02/26/09 (EST)
                  
Note : <CMHOME> refers to the SAS Credit Risk Installation location. Typically in AIX it is !SASHOME/SASCreditRiskManagement/4.5.   
                  


MANUAL POST-INSTALLATION STEPS:
                   
After the hot fix, 45crsk01, finishes execution, you should update the Web application by 
redeploying the .war file associated with the changes above.

The updated files delivered to the system must be updated in the .war file which was 
originally created in the initial webserver start.


NOTE: For Tomcat webserver, the Credit Risk webapp is deployed as war file, which is exploded
and $TOMCAT_HOME/webapps/criskm directory is created at webserver start.
The new .war file deployment will replace the existing contents of the criskm folder at 
$TOMCAT_HOME/webapps/criskm when the webserver re-starts. Please make a copy of the current 
.war file at this location as a backup.  Once the new file is created and running properly 
the backup may be deleted.


Perform the following steps: 

1) Stop any web service related to SAS Credit Risk Management which could be consuming the
   .war file at location $TOMCAT_HOME/webapps/criskm.

2) Take a backup of the following files and folders -
	a. criskm.war file present in the location <CMHOME>
	b. criskm.war file present in the location <installed_plan_dir>/web/webapps
	
NOTE:  <installed_plan_dir> refers to location where the SAS application configurations 
       are placed.

3) Explode the criskm.war file present in the location <CMHOME> to a temporary folder
   e.g. <CMHOME>/temp.

         $> cd <CMHOME>
         $> mkdir temp
         $> cp criskm.war ./temp
         $> cd temp
         $> unzip criskm.war

   After exploding the criskm.war file, remove it from the temp folder:
         $> rm criskm.war

4) Copy the SecurityFilter.class file from 
   <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk/httpfilters 
   folder to the temporary exploded folder 
   e.g. <CMHOME>/temp/WEB-INF/classes/com/sas/ets/creditrisk/httpfilters

         $> cd <CMHOME>/temp/WEB-INF/classes/com/sas/ets/creditrisk/httpfilters
         $> cp <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk/httpfilters/SecurityFilter.class .


5) Copy the ResourceKeysCreditrisk.class file from 
   <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk 
   folder to the temporary exploded folder 
   e.g. <CMHOME>/temp/WEB-INF/classes/com/sas/ets/creditrisk

         $> cd <CMHOME>/temp/WEB-INF/classes/com/sas/ets/creditrisk
         $> cp <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk/ResourceKeysCreditrisk.class .


6) Copy the ApplicationResources.properties file from 
   <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk
   folder to the temporary exploded folder 
   e.g. <CMHOME>/temp/WEB-INF/classes/com/sas/ets/creditrisk

         $> cd <CMHOME>/temp/WEB-INF/classes/com/sas/ets/creditrisk
         $> cp <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk/ApplicationResources.properties .

7) Copy the ApplicationResources_en.properties file from 
   <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk
   folder to the temporary exploded folder
   e.g. <CMHOME>/temp/WEB-INF/classes/com/sas/ets/creditrisk

         $> cd <CMHOME>/temp/WEB-INF/classes/com/sas/ets/creditrisk
         $> cp <CMHOME>/webapps/criskm/WEB-INF/classes/com/sas/ets/creditrisk/ApplicationResources_en.properties .


8) Package the exploded files in temporary folder (e.g. <CMHOME>/temp) into 
   criskm.war using a zip utility like jar.

         $> cd <CMHOME>/temp
         $> <JAVA_HOME>/jar cvf criskm.war *


9) Copy the war file criskm.war into the <CMHOME>/temp

         $> cd <CMHOME>/temp
         $> cp <CMHOME>/temp/criskm.war .

10) Copy the war file criskm.war into the deployment area in the Application Server 
    e.g. $TOMCAT_HOME/webapps

         $> cd $TOMCAT_HOME/webapps
         $> cp <CMHOME>/temp/criskm.war .


11) Delete all cached files from the web container before deploying hot fix. 
    $TOMCAT_HOME/webapps

         $> cd $TOMCAT_HOME/webapps
         $> rm -r criskm

12) Redeploy the criskm.war files Web application's Web server machine. You should redeploy
    these web applications using the tools provided by the container.

    For example, in WebLogic you should use the WebLogic management console to undeploy and 
    redeploy each web application.


NOTE:  You must restart the web application (re-deploy) before the changes will surface.
    

This completes the installation of hot fix 45crsk01.