Installation Instructions for Hot Fix F73002

64-bit Enabled Solaris

Hot fix F73002 addresses the issue(s) in Profitability Management 2.21 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/F73.html#F73002

F73002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as indicated.

F70002  updates  SAS Profitability Management Client 2.21
F71002  updates  SAS Profitability Management Mid-Tier 2.21
F72002  updates  SAS Profitability Management Utility 2.21

Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The release number information in the Registry report should match the 'member' release number information provided above for the software components installed on each machine in your deployment.

The hot fix downloaded, F73002pt.zip, includes the updates required for all components listed above on all applicable operating systems. To apply this hot fix on multiple machines, you can either save F73002pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of F73002pt.zip. The hot fix installation process will extract the contents as needed.

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.

INSTALLATION

The hot fix will be applied using the SAS Deployment Manager (SDM). By default, the SDM will search in the <SASHOME>/InstallMisc/HotFixes/New directory for hot fixes to be applied, but will also prompt for a location if you have downloaded hot fixes to a different directory.

After downloading F73002pt.zip, follow the instructions provided in the SAS Deployment Wizard/SAS Deployment Manager 9.3: User's Guide; see the Apply Hot Fixes section in Chapter 5 -- SAS Deployment Manager Tasks to complete the installation of the hot fix.

The hot fix installation process generates the log file

<!SASHOME>/InstallMisc/InstallLogs/IT_date-and-time-stamp.log

Postexec log files are created after the installation is completed and identifies the files that were added, backed up, changed and removed. These log files include the 'member' hot fix id in the name of the file and are also written to the <!SASHOME>/InstallMisc/InstallLogs directory. There is one postexec log for each 'member' hot fix applied (member hot fixes are listed at the top of these instructions).

POST-INSTALLATION INSTRUCTIONS

For each product installed, click the link to be redirected to post-installation instructions.

F70002  updates  SAS Profitability Management Client 2.21
F71002  updates  SAS Profitability Management Mid-Tier 2.21
F72002  updates  SAS Profitability Management Utility 2.21

F70002  updates  SAS Profitability Management Client 2.21

Updates to your Profitability Management client machines are also required. Since the clients can only be installed on Windows or Windows for x64, you must download F73002 for Windows to your client machines and apply the hot fix per the installation instructions provided.

F71002  updates  SAS Profitability Management Mid-Tier 2.21

Web application Update

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.3

From the SASDeploymentManager directory launch sasdm.sh. The default installation path for the SAS Deployment Manager is

SASHOME/SASDeploymentManager/9.3

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 SAS Profitability Management Mid-Tier 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 SAS Profitability Management Mid-Tier ear in <CONFIGDIR>/Lev1/Web/Staging. 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 ear listed above to the web application server you are using based on the instructions appropriate for your web application server. See SAS 9.3 Intelligence Platform, Middle-Tier Administration Guide, Chapter 7, Administering SAS Web Applications, for more details.

Step 3: Clear the Web Application Server Cache

• What is Cache?
  Basically, all the web-tier related files (.jsp .class, JSPCompiled files etc.,) get stored in the <app_your_application> directory. This is treated as cache whenever there is a restart of a Web Application Server instance. When this happens, the WebApp server will look for the last serviced object status stored in the cache for service for any pending requests.

• Why do we need to remove Cache?
  Whenever your application is accessed for the first time for a fresh deployment of a new version, WebApp server does a lookup in this directory to see if any older objects persist that will be a conflict with new code objects. This is where the need for removal of cache arises.

• Clearing Cache for Web Logic instance
  For WebLogic 9.x onwards, removal of cache means deleting each server instance's tmp folder that contains cache and stage folders. You can simply remove tmp folder provided there are no configuration changes to the server.

  For Web-Logic, if SAS Profitability Management is deployed to SASServer2, delete the tmp folder located at

  SASConfig\Lev1\Web\SASDomain\servers\SASServer2\tmp

• Clearing Cache for Web Sphere instance
  Clear WebSphere cache every time you rebuild and redeploy the ear files.

  From the file structure, delete the following folders/files:

  ibm\websphere\appserver\profiles\<app server profile>\temp\<node>\<app server> folder
  ibm\websphere\appserver\profiles\<app server profile>\wstemp, delete files in this folder

  IBM Support may ask you to clear the class cache. There are several reasons for this. After an upgrade, it is possible that the class caches are still holding onto previous versions of classes. It is also possible that the caches became corrupted.

  Please remember there are two caches that will need to be cleared, the JVM's cache and the OSGi cache. The server has to be stopped before clearing the cache.

• To clear the OSGi class cache
  For UNIX platforms, run the following script in each profile:

  /profiles/profile_name/bin/osgiCfgInit.sh

  For Windows platforms, run the following script in each profile:

  \profiles\profile_name\bin\osgiCfgInit.bat

• To clear the JVM's class cache (Windows, Linux and AIX only)
  For UNIX platforms, run the following script:

  <WebSphere_HOME>/bin/clearClassCache.sh

  For Windows platforms, run the following script:

  <WebSphere_HOME>\bin\clearClassCache.bat

  And clear the following directory contents:

  C:\Documents and Settings\DefaultUser\Local Settings\ApplicationData\javasharedresources\

• Clearing Cache for JBoss instance
  Delete the contents under

  <JBossHome>/server/SASServer2/tmp

  and

  <JBossHome>/server/SASServer2/work

  These folders are created dynamically when the Server is started.

F72002  updates  SAS Profitability Management Utility 2.21

NONE

This completes the installation of hot fix F73002 on 64-bit Enabled Solaris.