INSTALLATION INSTRUCTIONS FOR HOT FIX 913WEBINFRAKIT16 ON HPUX FOR ITANIUM BEFORE DOWNLOADING: The hot fix 913webinfrakit16 addresses the issue(s) in 9.1.3 SP4 of webinfrakit software on HPUX for Itanium as documented in the "Issue(s) Addressed" section of the hot fix download page: http://ftp.sas.com/techsup/download/hotfix/idp913.html#913webinfrakit16 IMPORTANT NOTE(S): 1. You must have SAS Information Delivery Portal 9.1.3 SP4 installed on your system before applying this hot fix. 2. It is recommended that the hot fix be installed using the same userid who performed the SAS 9.1.3 installation. 3. You must have Administrator Privileges on your CLIENT or SERVER machine and all currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix. 4. If you have both SAS Information Delivery Portal and SAS Web OLAP Viewer for Java 3.1 installed then you must also download and install hot fix 31WEBOLAPVR14 for this hot fix to be fully functional. 5. 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 913webinfrakit16hx.exe. INSTALLING THIS HOT FIX: 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 #4 below. 1. Extract the contents of 913webinfrakit16hx.tar into a temporary directory, for example /tmp/913webinfrakit16. $> mkdir /tmp/913webinfrakit16 $> cd /tmp/913webinfrakit16 $> tar -xf $HOME/913webinfrakit16hx.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: h6i/Setup_HPUX_IA64 h6i/media.inf h6i/setup.jar 2. Verify that Setup_HPUX_IA64 has execute permission. If it does not, use the 'chmod' command to make it executable: $> cd /tmp/913webinfrakit16/h6i $> chmod 755 Setup_HPUX_IA64 3. Initiate the installation wizard $> export DISPLAY=:0 <==== set your display $> cd /tmp/913webinfrakit16/h6i $> ./Setup_HPUX_IA64 This will initiate the Java install wizard. Follow the prompts to complete the installation. 4. 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: /Web/Portal2.0.1/DeployedPortlets/DAVContent.par Date: 06/01/07 (EST) /Web/Portal2.0.1/OMR/LoadPackageOrderPreference.sas.orig Date: 07/10/06 (EST) /Web/Portal2.0.1/Portal/jsp/html/portal/task/RemovePage.jsp Date: 05/31/07 (EST) /Web/Portal2.0.1/Portal/jsp/html/portal/viewer/ViewerPost.jsp Date: 06/28/07 (EST) /Web/Portal2.0.1/Portal/scripts/sas_comboBoxView.js Date: 11/30/07 (EST) /Web/Portal2.0.1/Portal/scripts/sas_ExceptionHighlightingSelector.js Date: 11/30/07 (EST) /Web/Portal2.0.1/Portal/scripts/sas_treeview.js Date: 05/03/06 (EST) /Web/Portal2.0.1/Portal/styles/sasComponentsTheme.css Date: 10/05/07 (EST) /Web/Portal2.0.1/Portal/templates/ExceptionHighlightingChartSelectorPanel.html Date: 11/30/07 (EST) /Web/Portal2.0.1/Portal/templates/ExceptionHighlightingSelectorPanel.html Date: 11/30/07 (EST) /Web/Portal2.0.1/Portal/WEB-INF/struts-config.xml Date: 05/11/09 (EST) /Web/Portal2.0.1/Portal/WEB-INF/web.xml.orig Date: 08/20/07 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.iquery.dataservices.jar Date: 07/15/09 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.rpf.jar Date: 02/15/08 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.swing.remote.jar Date: 07/07/09 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.common.framework.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.iquery.metadata.jar Date: 07/07/09 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.oma.joma.jar Date: 06/04/08 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.oma.joma.rmt.jar Date: 06/04/08 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.svc.core.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.servlet.jar Date: 12/11/08 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.dataexplorer.jar Date: 03/27/09 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.portal.jar Date: 05/11/09 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.common.framework.ext.jar Date: 07/06/06 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.portal.metadata.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.web.framework.jar Date: 02/23/09 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.ads.iqueryutil.jar Date: 07/07/09 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.storage.jar Date: 12/11/08 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.svc.storedprocess.webapp.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.swing.jar Date: 02/15/08 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.svc.connection.jar Date: 05/07/09 (EST) /Web/Portal2.0.1/Portal/WEB-INF/lib/sas.preferences.webapp.jar Date: 07/16/07 (EST) /Web/Portal2.0.1/PortalConfigure/WIKConf.xml Date: 07/06/06 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/web.xml.orig Date: 08/20/07 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.common.framework.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.iquery.metadata.jar Date: 07/07/09 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.oma.joma.jar Date: 06/04/08 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.oma.joma.rmt.jar Date: 06/04/08 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.svc.core.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.servlet.jar Date: 12/11/08 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.common.framework.ext.jar Date: 07/06/06 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.portal.metadata.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.web.framework.jar Date: 02/23/09 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.svc.connection.jar Date: 05/07/09 (EST) /Web/Portal2.0.1/SASPreferences/WEB-INF/lib/sas.preferences.webapp.jar Date: 07/16/07 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.common.framework.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.iquery.metadata.jar Date: 07/07/09 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.oma.joma.jar Date: 06/04/08 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.oma.joma.rmt.jar Date: 06/04/08 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.svc.core.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.dataexplorer.jar Date: 03/27/09 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.portal.jar Date: 05/11/09 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.common.framework.ext.jar Date: 07/06/06 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.portal.metadata.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.web.framework.jar Date: 02/23/09 (EST) /Web/Portal2.0.1/SASServices/WEB-INF/lib/sas.svc.connection.jar Date: 05/07/09 (EST) /Web/Portal2.0.1/SASStoredProcess/scripts/sas_treeview.js Date: 05/03/06 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/web.xml.orig Date: 08/20/07 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.common.framework.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.iquery.metadata.jar Date: 07/07/09 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.oma.joma.jar Date: 06/04/08 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.oma.joma.rmt.jar Date: 06/04/08 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.svc.core.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.servlet.jar Date: 12/11/08 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.common.framework.ext.jar Date: 07/06/06 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.portal.metadata.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.web.framework.jar Date: 02/23/09 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.ads.iqueryutil.jar Date: 07/07/09 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.storage.jar Date: 12/11/08 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.svc.storedprocess.webapp.jar Date: 05/06/08 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.swing.jar Date: 02/15/08 (EST) /Web/Portal2.0.1/SASStoredProcess/WEB-INF/lib/sas.svc.connection.jar Date: 05/07/09 (EST) /Web/Portal2.0.1/themes/SASTheme_default/themes/default/styles/sasComponentsTheme.css Date: 10/05/07 (EST) /Web/Portal2.0.1/themes/SASTheme_default/themes/default/templates/ExceptionHighlightingChartSelectorPanel.html Date: 11/30/07 (EST) /Web/Portal2.0.1/themes/SASTheme_default/themes/default/templates/ExceptionHighlightingSelectorPanel.html Date: 11/30/07 (EST) /Web/Portal2.0.1/themes/SASTheme_winter/themes/winter/styles/sasComponentsTheme.css Date: 10/12/07 (EST) /Web/Portal2.0.1/themes/SASTheme_winter/themes/winter/templates/ExceptionHighlightingChartSelectorPanel.html Date: 11/30/07 (EST) /Web/Portal2.0.1/themes/SASTheme_winter/themes/winter/templates/ExceptionHighlightingSelectorPanel.html Date: 11/30/07 (EST) /Web/Portal2.0.1/Tools/lib/sas.svc.connection.jar Date: 05/07/09 (EST) MANUAL POST-INSTALLATION STEPS: After the hot fix, 913webinfrakit16, finishes execution, you should update the SAS Services application and rebuild/redeploy the Portal.war, SASStoredProcess.war and SASPreferences.war files. Perform the following steps: 1) Stop the servlet container and the SAS Services application. 2) Run the configure_wik utility to update the SAS Services application and create a new Portal.war, SASStoredProcess.war, and SASPreferences.war files. You may find the configure_wik utility in a location such as C:\Program Files\SAS\Web\Portal2.0.1. 3) Start the SAS Services application. 4) Un-deploy and Redeploy the Portal.war, SASStoredProcess.war and SASPreferences.war files to the servlet container on your portal Web application's Web server machine. You should redeploy these web applications using the tools provided by the servlet container. For example, in WebLogic you should use the WebLogic management console to undeploy and redeploy each web application. 5) Start the servlet container. 6) Copy the new sas.svc.connection.jar file to the custom\lib directory. In most cases Xythos is installed in $SASHOME, therefore this location would be: $SASHOME\xythos\2.2\custom\lib for 9.1.3 The current release of the SAS Information Delivery Portal displays packages published to a channel in ascending sort order (oldest is displayed at the top and newest at the bottom). This hotfix provides a mechanism to allow the sort order to be controlled by a SAS preference, thus allowing a site-wide default to be set and individuals to override that default. A new SAS program, LoadPackageOrderPreference.sas, is available in the OMR subdirectory of the setup directory. When run, this program will change the package sort order to descending (newest is displayed at the top and oldest at the bottom). The following steps only need to be performed if you wish to change package sort order. On Windows systems, follow these steps: 1) Go to the OMR subdirectory of the setup directory. 2) Right-click on LoadPackageOrderPreference.sas or LoadPackageOrderPreference_utf8.sas, and select Batch Submit with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation. 3) You must restart the servlet container after submitting the LoadPackageOrderPreference.sas for the functionality to surface. On Unix systems, follow these steps: 1) Go to the OMR subdirectory of the setup directory. 2) Submit LoadPackageOrderPreference.sas or LoadPackageOrderPreference_utf8.sas with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation. 3) You must restart the servlet container after submitting the LoadPackageOrderPreference.sas for the functionality to surface. This completes the installation of hot fix 913webinfrakit16.