Hot fix F01002 addresses the issue(s) in SAS Profitability Management 2.2 on Windows as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/F01.html#F01002
F01002 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.
E98002 for SAS Profitability Management Client 2.2
E97002 for SAS Profitability Management Mid-Tier 2.2
E99002 for SAS Profitability Management Utility 2.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.
The installer downloaded is F01002wn.exe.
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.
Note: If your Windows operating system is Windows Vista, Windows 7 or Windows Server 2008, it may be necessary to "right-click" F01002wn.exe and select "Run as administrator".
See the Maintenance Install Tool (MIT) Usage Guide for more details on the installation of hot fixes.
This completes the installation of F01002. You must perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.
For each product installed, click the link to be redirected to post-installation instructions.
E98002 for SAS Profitability Management Client 2.2
E97002 for SAS Profitability Management Mid-Tier 2.2
E99002 for SAS Profitability Management Utility 2.2
E98002 for SAS Profitability Management Client 2.2
The installation of the hot fix to the SAS Profitability Management Client assumes that
the client is installed in
C:\Program Files\SAS\If the client is installed in a location other than C:\Program Files\SAS, the file
<SASHOME>\SASProfitabilityManagementClient\2.2\configuration\config.inimust be manually modified. All occurences of
C:\Program Files\SAS\must be changed to reflect the location to where the client is installed. It is recommended that you back up the config.ini before manually editing the file. You should confirm that the SASVersionedJarRepository paths are correct for your installation.
E97002 for SAS Profitability Management Mid-Tier 2.2
This hot fix requires post-installation steps that will update the web application deployed to your application server.
Step 1: Re-build Web Applications
In order for this step to execute correctly, the Metadata Server must be running.
1.1 Invoke the SAS Deployment Manager 9.2
From the SASDeploymentManager directory launch config.exe. The default installation path for the SAS Deployment Manager is
C:\Program Files\SAS\SASDeploymentManager\9.2
1.2 Select a language in the Choose Language box
1.3 Select Rebuild Web Applications
1.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
1.5 Specify Connection Information, including the sasadm User ID and Password
1.6 Select Profitability Mgmt 2.2 as the Web Application to Rebuild
1.7 Verify the information on the Summary screen and select Start
1.8 Select Finish when the deployment is complete
This process will update the Profitability Management ear, sas.profitabilitymanagement2.2.ear,
in <CONFIGDIR>\Lev1\Web\Staging and place the updated exploded ear in
<CONFIGDIR>\Lev1\Web\Staging\exploded.
A backup of the original ear file will be placed in the Backup directory.
Step 2: Re-deploy Web Applications
2.1 Re-deploy the updated sas.profitabilitymanagement2.2.ear to the web application server you are using based on the instructions appropriate for your web application server.
E99002 for SAS Profitability Management Utility 2.2
NONE
This completes the installation of hot fix F01002 on Windows.