INSTALLATION INSTRUCTIONS FOR HOT FIX 45CRSK01 ON WINDOWS


BEFORE DOWNLOADING:

The hot fix 45CRSK01 addresses the issue(s) in 4.5 of SAS Credit Risk Management 
software on Windows 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 45crsk01wn.exe.  

3.  If you are installing the hot fix via a terminal server (i.e. you are using
    Remote Desktop to install the hot fix), the vpd.properties file in your user 
    home directory on that machine must match the one in c:\WINNT or c:\WINDOWS
    (depending on your version of Windows OS). If it doesn't, simply copy 
    c:\winnt\vpd.properties to c:\Document and Settings\<userid>\windows\vpd.properties.
    



INSTALLING THIS HOT FIX:

1.  Technical Support strongly suggests that you back up the files being replaced by this hot fix.  
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 #3 below.

2.  Launch the executable, which will initiate a Java install wizard and will 
guide you through the extraction of the updated components.  


3.  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 Windows 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.


Perform the following steps: 

1. 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>/Lev1/web/webapps
	
NOTE:  <installed_plan_dir> refers to location where the SAS application configurations are 
placed.
	
2. Explode the criskm.war file present in the location <CMHOME> to a temporary folder
   e.g. <CMHOME>/temp.

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

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

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

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

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

8. Copy the war file criskm.war into <CMHOME>  

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

10. Delete all cached files from the web container before deploying hot fix. 
    e.g. For Tomcat webserver, delete the criskm folder from the deployment area in
    i.e. $TOMCAT_HOME/webapps

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