Installation Instructions for Hot Fix D73031

64-bit Enabled Solaris

Hot fix D73031 addresses the issue(s) in SAS Financial Management 5.2_M1 on 64-bit Enabled Solaris as documented in Problem Notes

46689 Error indicating a user is not authorized to work with forms
46690 Unable to see more than one form in the SASŪ Financial Management Form Manager
46686 SASŪ Financial Management Java API does not update target members in a form set
47779 SASŪ Financial Management e-mail reminders are sent after a form set is locked

You MUST apply D73027 before applying this hot fix.

D73031 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as indicated. See the Container Hot Fixes section in the Maintenance Install Tool (MIT) Usage Guide for more information about container hot fixes.

E32012 for SAS Financial Management Mid-Tier 5.2_M1
E33012 for SAS Financial Management Web Data Entry 5.2_M1
E36008 for SAS Financial Management 5.2_M1

INSTALLATION

Important Notes

1. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

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

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

4. This hot fix should be installed using the same userid who performed the initial software installation.

Downloading the hot fix

1. This hot fix must be installed on each machine where the updated components of the product, listed above, are installed. The installation process will determine which components of SAS Financial Management 5.2_M1 are installed on each machine, and apply the appropriate updates.

2. If the updated components of this product are installed on multiple operating systems, you must download the hot fix for the appropriate operating system(s) and follow the installation instructions provided to complete the deployment of this hot fix.

3. When downloading SAS 9.2 hot fix packages, you must choose to Save the hot fix to disk, then execute the install from the saved location. Attempting to install a hot fix directly from the download page results in the error documented in SAS Note 37104.

4. The installer downloaded is D73031s6.exe.

Prior to executing the hot fix shut down the SAS servers

1. Log on to the WebLogic Server Administration Console at
   http://midtierservername:7501/console

2. On the left side of the screen under Domain Structure, select Environment > Servers

3. Select the Control tab

4. Select SAS Servers 3, 4 and 5 and click Shutdown > Force Shutdown Now > Yes

5. Exit out of the SAS Information Delivery Portal.

Installing the hot fix

1. Verify that the installation binary has execute permission. If it does not, use the chmod command to make it executable.

   $> chmod 755 D73031s6.bin

2. Set your $DISPLAY environment variable

   export DISPLAY=<your_node_name>:0

3. Execute D73031s6.bin with the -alwaysoverwrite option

   <path_to_downloaded_file>/D73031s6.bin -alwaysoverwrite

       For example:

   ./D73031s6.bin -alwaysoverwrite

   
   This will initiate the installation wizard, which will guide you through the hot fix installation process. During the installation you will be prompted for the SASHOME location to be updated. You should provide the path to the top level SAS directory where the deploymntreg directory exists.

See the Maintenance Install Tool (MIT) Usage Guide for more details on the installation of hot fixes.

This completes the installation of D73031. You must perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.

POST-INSTALLATION INSTRUCTIONS

Updates provided in this hot fix require that the following Web Applications be rebuilt and redeployed.

Server 3: SAS Financial Management Mid-Tier
Server 3: SAS Solutions Services Mid-Tier
Server 4: SAS OLAP Data and Compute Server Mid-Tier for Solutions
Server 5: SAS Financial Management Web Data Entry

Re-build Web Application

In order for this step to execute correctly, the Metadata Server must be running.

1. Set the DISPLAY environment variable, for example

   $ export DISPLAY=<displayname>:0

2. Invoke the SAS Deployment Manager 9.2

   From the SASDeploymentManager directory execute config.sh, for example

   $ cd <SASHOME>/SASDeploymentManager/9.2
   $ ./config.sh

3. Select a language in the Choose Language box

4. Select Rebuild Web Applications

5. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

6. Specify Connection Information, including the sasadm User ID and Password

7. Select the mid-tier applications listed above as the Web Applications to Rebuild

8. Verify the information on the Summary screen and select Start

9. Select Finish when the deployment is complete

<SASCONFIGDIR>/Web/Staging

<SASCONFIGDIR>/Web/Staging/Backup

Re-deploy Web Application

1. Remove the cache for the updated ear files under

   <drive>:/SAS/Config/Lev1/Web/SASDomain/servers/SASServer4/tmp/_WL_user

   (delete entire folder for each ear file)

2. Re-deploy the web application using WebLogic Admin console.

   To deploy this application it is important to deploy from <SASCONFIGDIR>/Web/Staging.

   Verify that in the settings overview tab for the Financial Management Mid-Tier and Financial Management Web Data Entry ear files to be re-deployed that the deployment order is set to 110.

   Verify that in the settings overview tab for the Solutions Services Mid-Tier and OLAP Data and Compute Server Mid-Tier for Solutions ear files to be re-deployed that the deployment order is set to 100.

3. Re-deploy WebSphere Application.

   Re-deploy the web application using WebSphere Admin console by using the Update function.

   To deploy this application it is important to deploy from /Web/Staging.

   Verify that the Deploy WebServices checkbox is selected

Re-start the Web Application Servers

1. Re-start SAS Remote Services (which will likely require that you also re-start SASServer1 and SASServer2).

2. Re-start SASServer3 and SASServer4 (you will likely also need to re-start SAS Server5 since the other application servers were stopped).

3. From Weblogic Admin Console, select SASServer 3, 4, and 5 > Start > Yes

This completes the deployment of hot fix D73031 on 64-bit Enabled Solaris.