INSTALLATION INSTRUCTIONS FOR HOT FIX 31WEBOLAPVR16 ON WINDOWS BEFORE DOWNLOADING: The hot fix 31webolapvr16 addresses the issue(s) in Release 3.1 of SAS Web Olap Viewer for Java software on Windows as documented in the "Issue(s) Addressed" section of the hot fix download page: http://ftp.sas.com/techsup/download/hotfix/webolapvr31.html#31webolapvr16 IMPORTANT NOTE(S): 1. You must have SAS Web Olap Viewer for Java Release 3.1 installed on your system before applying this hot fix. 2. You must have SAS 9.1.3, Service Pack 4 installed on your machine before applying this hot fix. 3. The SAS metadata foundation repository must contain a BI root folder with the name 'BIP Tree'. This is the default BI root folder name used in SAS 9.1.3 installs. If this root folder does not exist, it can be created using the SAS Management Console Business Reports Manager 4. If you have both SAS Web OLAP Viewer for Java 3.1 and SAS Information Delivery Portal then you must download hot fix 31webolapvr16 and 913WEBINFRAKIT16 respectively for this hot fix to be fully functional. 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 . 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: \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\scripts\sas_comboBoxView.js Date: 11/30/07 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\scripts\sas_ExceptionHighlightingSelector.js Date: 11/30/07 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\scripts\sas_treeview.js Date: 05/03/06 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\styles\sasComponentsTheme.css Date: 10/05/07 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\templates\ExceptionHighlightingChartSelectorPanel.html Date: 11/30/07 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\templates\ExceptionHighlightingSelectorPanel.html Date: 11/30/07 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\web.xmlhost.orig Date: 08/20/07 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\web.xmltrusted.orig Date: 08/20/07 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\dl.util.concurrent.jar Date: 03/18/03 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.ads.iqueryutil.jar Date: 07/07/09 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.common.framework.jar Date: 05/06/08 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.dataexplorer.jar Date: 09/25/09 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.iquery.dataservices.jar Date: 07/15/09 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.iquery.metadata.jar Date: 07/07/09 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.oma.joma.jar Date: 06/04/08 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.oma.joma.rmt.jar Date: 06/04/08 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.rpf.jar Date: 02/15/08 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.servlet.jar Date: 12/11/08 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.storage.jar Date: 12/11/08 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.svc.core.jar Date: 05/06/08 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.swing.jar Date: 02/15/08 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.swing.remote.jar Date: 07/07/09 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.web.framework.jar Date: 02/23/09 (EST) \SASWebOlapViewerforJava\3.1\SASWebOLAPViewer\WEB-INF\lib\sas.webolapviewer.jar Date: 04/28/08 (EST) MANUAL POST-INSTALLATION STEPS: After the hot fix, 31webolapvr16 , finishes execution, you should rebuild and redeploy the associated .war file by following the steps below: 1. Run the "configure.bat" file in "/3.1" to create a new war file for deployment. 2. If you are running any of the following solutions in your environment SAS Financial Management SAS Strategic Performance Management SAS Human Capital Management SAS Campaign Web Studio you must implement the steps documented in SN-020856 before proceeding with the next step in these instructions (redeploying the war file). See http://support.sas.com/techsup/unotes/SN/020/020856.html for the detailed instructions. 3. Follow the steps in the "/3.1/config.pdf" file for redeploying the war file. This completes the installation of hotfix 31webolapvr16 on Windows.