INSTALLATION INSTRUCTIONS FOR HOT FIX 31WEBRPTVR20 ON WINDOWS


BEFORE DOWNLOADING:

The hot fix package downloaded is a self extracting executable named 31webrptvr20wn.exe.



IMPORTANT NOTE(S):

1.  You must have SAS Web Report Viewer Release 3.1 installed on your 
    system before applying this hot fix.

2.  The hotfix must be installed using the same userid who performed the 
    initial SAS Web Report Viewer Release 3.1 installation.

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

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

5.  If you have made changes directly to the deployed 

         SASWebReportViewer\WEB-INF\WebReportViewerProperties.xml 

    that are not duplicated in 

         <!SASHOME>\SASWebReportViewer\3.1\config\WebReportViewerProperties.xml.orig

    back up the deployed SASWebReportViewer\WEB-INF\WebReportViewerProperties.xml.

6.  If you are running any of the following solutions with  SAS Web Report Viewer:

        SAS Financial Management 
        SAS Strategic Performance Management 
        SAS Human Capital Management  

    back up the following locations.  If the solutions listed were installed with the default 
    configuration settings, the locations should appear as:

        <config-dir>\sas\SASSolutionsConfig\Lev1\web\webapps\exploded
        <config-dir>\sas\SASSolutionsConfig\Lev1\web\Deployments

    If the solutions were installed with non-default configuration settings, the locations
    to back up should be similar to:

        <config-dir>\Lev1 



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.

As an alternative to creating backups of the individual files, you may use an archive utility
like tar for Unix or WinZip for Windows to back up the entire directory

    <!SASHOME>\SASWebReportViewer\3.1


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:

      <!SASHOME>\SASWebReportViewer\3.1\SAS_Service_Level.properties
      Date: 08/30/10 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\code\errorPage.jsp
      Date: 04/03/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\userManagement.jsp
      Date: 04/03/07 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\code\cdd_templates\ExceptionHighlightingChartSelectorPanel.html
      Date: 11/30/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\cdd_templates\ExceptionHighlightingSelectorPanel.html
      Date: 11/30/07 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\code\scripts\citation_createNewFilter.js
      Date: 11/11/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\scripts\citation_filterRankCrosstab.js
      Date: 08/20/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\scripts\citation_logon.js
      Date: 01/25/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\scripts\citation_popup.js
      Date: 12/21/06 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\scripts\citation_reportControl.js
      Date: 08/02/06 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\scripts\sas_comboBoxView.js
      Date: 09/17/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\scripts\sas_ExceptionHighlightingSelector.js
      Date: 11/30/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\scripts\sas_exportSelector.js
      Date: 11/20/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\scripts\sas_treeview.js
      Date: 08/20/08 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\code\styles\citation.css
      Date: 08/20/08 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-components\builderSelectDataDialogTabContent.jsp
      Date: 08/04/06 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-components\editReportImageDialogContent.jsp
      Date: 12/12/06 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-components\invokingApplicationReturn.jsp
      Date: 05/04/06 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-components\linkPromptsSharedDialogContent.jsp
      Date: 06/06/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-components\reportWizardStep1Content.jsp
      Date: 08/04/06 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-components\saveOptionsDialogContent.jsp
      Date: 03/12/09 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-components\viewReportDataPane.jsp
      Date: 08/04/06 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-components\viewReportHowDoIMenu.jsp
      Date: 06/15/07 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-components\filterViewElement\filterRankCrosstabDialogTabContent.jsp
      Date: 08/20/08 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-layouts\dialogLayout.jsp
      Date: 04/03/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\tiles-layouts\mainPageLayout.jsp
      Date: 04/03/07 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\web.xml
      Date: 03/29/10 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\jobflow.jar
      Date: 03/12/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\jobflowui.jar
      Date: 02/19/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\lsfsecurity.jar
      Date: 02/07/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.ads.iqueryutil.jar
      Date: 07/07/09 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.core.jar
      Date: 11/09/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.core.net.jar
      Date: 11/09/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.expr.visuals.jar
      Date: 08/28/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.graph.bip.jar
      Date: 12/04/09 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.graph.core.jar
      Date: 11/09/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.graph.esrimap.jar
      Date: 11/09/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.graph.gtk.jar
      Date: 11/09/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.graph.report.jar
      Date: 08/07/06 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.iquery.dataservices.jar
      Date: 05/14/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.iquery.metadata.jar
      Date: 07/07/09 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.report.jar
      Date: 02/15/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.report.output.management.jar
      Date: 05/14/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.report.renderer.core.jar
      Date: 12/10/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.report.renderer.html.jar
      Date: 09/01/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.report.renderer.pdf.jar
      Date: 05/14/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.report.repository.jar
      Date: 11/09/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.report.services.jar
      Date: 08/28/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.reportviewer.web.jar
      Date: 09/01/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.rpf.jar
      Date: 02/15/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.schedule.model.jar
      Date: 11/09/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.servlet.jar
      Date: 09/01/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.smc.schedule.remote.jar
      Date: 03/13/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.storage.jar
      Date: 12/11/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.svc.connection.jar
      Date: 05/07/09 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.svc.storedprocess.jar
      Date: 11/12/07 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.swing.jar
      Date: 08/28/08 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.swing.remote.jar
      Date: 05/14/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\sas.web.framework.jar
      Date: 02/23/09 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\code\WEB-INF\lib\saslogin.jar
      Date: 02/07/08 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\config\WebReportViewerProperties.xml.orig
      Date: 02/13/08 (EST)


      <!SASHOME>\SASWebReportViewer\3.1\config\Source\Java\resources\web.xml.host.tomcat
      Date: 03/29/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\config\Source\Java\resources\web.xml.host.weblogic
      Date: 03/29/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\config\Source\Java\resources\web.xml.host.websphere
      Date: 03/29/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\config\Source\Java\resources\web.xml.trusted.tomcat
      Date: 03/29/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\config\Source\Java\resources\web.xml.trusted.weblogic
      Date: 03/29/10 (EST)

      <!SASHOME>\SASWebReportViewer\3.1\config\Source\Java\resources\web.xml.trusted.websphere
      Date: 03/29/10 (EST)


4.  Un-deploy, Configure and Deploy SAS Web Report Viewer

***  If you are running any of the following solutions with  SAS Web Report Viewer 
     skip this step and proceed with step #5.

        SAS Financial Management 
        SAS Strategic Performance Management 
        SAS Human Capital Management 

Configure and deploy SAS Web Report Viewer by following the instructions for your 
operating system and web application server in the file 

      <!SASHOME>\SASWebReportViewer\3.1\deployment.html.
  

  
Note:  If SAS Web Report Viewer was originally installed using the SAS Configuration
Wizard, there is a copy of the .war file in the <configuration-dir>\Lev1\web\webapps folder.
Also, if the application is configured for deployment in WebLogic, an additional
directory containing an exploded copy of the SASWebReportViewer.war exists in the
<configuration-dir>\Lev1\web\webapps\exploded folder. To maintain the same version of the
.war file in all locations, it is recommended that you replace these files when
reconfiguring this application.


5.  Un-deploy,  Configure and Deploy SAS Web Report Viewer to Solution environments

***  You must implement the steps documented in SN-020856 before configuring and 
     deploying this hot fix.  See

        http://support.sas.com/techsup/unotes/SN/020/020856.html

     for  the detailed instructions.  

***  Step #5 is necessary for SAS Financial Management and SAS Strategic Performance Management 
     only if SAS Web Report Viewer are used.

***  Step #5 is required for SAS Human Capital Management.


        a.  Stop all Managed Servers.

        b.  Re-create the SASWebReportViewer.war in the installation folder.  

            The script that should be executed is

	<!SASHOME>\SASWebReportViewer\3.1\sas.wrv.config.bat

        c.  Deploy SAS Web Report Viewer to Foundation.

            The script that should be executed is

	For Weblogic:
	<config_dir>\Lev1\Utilities\SASSolutionsServices\Deployment\bin\FoundationWebReportViewer.bat

	For Websphere:
	<config_dir>\Lev1\Utilities\SASSolutionsServices\Deployment\bin\FoundationWebReportViewerWS.bat

        d.  Deploy SAS Web Report Viewer to Solutions.

            The script that should be executed is

	For Weblogic:
	<config_dir>\Lev1\Utilities\SASSolutionsServices\Deployment\bin\SolutionsWebReportViewer.bat

	For Websphere:
	<config_dir>\Lev1\Utilities\SASSolutionsServices\Deployment\bin\SolutionsWebReportViewerWS.bat

        e.  Deploy SAS Web Report Viewer to HR.
                        *** This step applies only if  SAS Human Capital Management is installed.

            The script that should be executed is

	For Weblogic:
	<config_dir>\Lev1\Utilities\SASSolutionsServices\Deployment\bin\HRWebReportViewer.bat

	For Websphere:
	<config_dir>\Lev1\Utilities\SASSolutionsServices\Deployment\bin\HRWebReportViewerWS.bat

        f.  Deploy SAS Web Report Viewer to Finance.
                        *** This step applies only if  SAS Financial Management is installed.
            
            The script that should be executed is

	For Weblogic:
	<config_dir>\Lev1\Utilities\SASSolutionsServices\Deployment\bin\FinanceWebReportViewer.bat

	For Websphere:
	<config_dir>\Lev1\Utilities\SASSolutionsServices\Deployment\bin\FinanceWebReportViewerWS.bat


6.  Update login.config file  

*** This step is required only if you have a SAS Financial Management, SAS Performance 
*** Management or SAS Human Capital Management installed.  If you do not have one of 
*** these products installed, this step can be skipped.  

        a.  Open login.config file in your WRS installation folder, for example

           on Windows:  <!SASHOME>\SASWebReportStudio\3.1\live\login.config
           on Unix:     <!SASHOME>/SASWebReportStudio/3.1/live/login.config

        b.  Change the following line and save the file.

           from: 
       	      com.sas.services.security.login.OMILoginModule optional "debug"="false"

           to (if Weblogic): 
       	      com.sas.services.security.login.weblogic.WLOMILoginModuleImpl optional "debug"="false"

           to (if WebSphere): 
       	      com.sas.solutions.security.jaas.WSOMILoginModule optional "debug"="false"

        c.  Open login.config file in your Portal configuration folder, for example

            on Windows:  <Config-Dir>\Lev1\web\Deployments\Portal\login.config

        d.  Change the following line and save the file.

            from: 
       	      com.sas.services.security.login.OMILoginModule

            to (if not already set to the following): 
       	      com.sas.services.security.login.weblogic.WLOMILoginModuleImpl

        e.  In order to fully implement the fix for 

              SN-018045 - 'Could not get the row level security for Type="PhysicalTable"' error 
              when scheduling a report in SAS Web Report Studio 

              http://support.sas.com/techsup/unotes/SN/018/018045.html

           you must add the trusted user information (trusteduser and trustedpw) to the file 

              ConfigDir\Lev1\web\Deployments\SASSolutionsServices\login.config file 

           for the remote services deployment.  For example the existing login.config may 
           look similar to this

     /** Login Configuration for SAS Enterprise Solutions **/

     PFS {
        com.sas.services.security.login.weblogic.WLOMILoginModuleImpl  required      
             "host"="hostname.na.sas.com"
             "port"="8561"
             "repository"="Foundation"
             "domain"="DefaultAuth"
             "debug"="false";
     };


After editing, it should contain trusteduser and trustedpw information and look similar 
to this:

/** Login Configuration for SAS Enterprise Solutions **/

     PFS {
        com.sas.services.security.login.weblogic.WLOMILoginModuleImpl  required      
             "host"="hostname.na.sas.com"
             "port"="8561"
             "repository"="Foundation"
             "domain"="DefaultAuth"
             "trusteduser"="mytrusteduserid"
             "trustedpw"="mytrustedpw"
             "debug"="false";
     };


        d.  Restart all the services.



This completes the installation of hotfix 31WEBRPTVR20.