Installation Instructions for Hot Fix J56007

Linux for x64

Hot fix J56007 addresses the issue(s) in Forecast Analyst Work Bench 5.1_M1 as documented in the Issue(s) Addressed section of the hot fix download page:

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

J57006  updates  SAS Forecast Analyst Workbench Mid-Tier 5.1_M1
J58005  updates  SAS Forecast Analyst Workbench Server 5.1_M1

See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.

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,, 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 on each machine or save it in a network location that is accessible to all machines.

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


  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.


Hot Fix J56007 must be installed on each machine where the updated components of the product, listed above, are installed. During the installation process you may see references to all operating systems for which updates are provided in the hot fix. The installation process will determine the operating system and which component(s) of Forecast Analyst Work Bench 5.1_M1 require updating on the machine. See SAS Note 44810 for more details.

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, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: User’s Guide.

The hot fix installation process generates the log file

for example, IT_2011-10-31-13.18.21.log. Each attempt to apply a hot fix results in the creation of a new log file giving detailed information regarding the installation process.

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

The content of this hot fix is listed in the hot fix manifest.


Click the link to be redirected to post-installation instructions:

J58005  updates  SAS Forecast Analyst Workbench Server 5.1_M1
J57006  updates  SAS Forecast Analyst Workbench Mid-Tier 5.1_M1
Clearing Cache

J58005  updates  SAS Forecast Analyst Workbench Server 5.1_M1


Note: If you have already installed the hotfix J56004, you would have already performed steps 1 to 2 as part of J56004 installation. You may skip step 1 to 2 below when installing J56007 or higher.

  1. The SAS services must be running while you are executing this macro.
  2. Please ensure that you have executed the one-time DI jobs execution before running the code mentioned below.

    Note: You must execute the macro only once.
For SAS® Forecast Analyst Workbench 5.1 hotfix release, the data administrator must execute the following macro through the Code Editor of SAS Data Integration Studio:
When you execute this macro, the following tasks are performed: J57006  updates  SAS Forecast Analyst Workbench Mid-Tier 5.1_M1

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 Set the DISPLAY environment variable, for example

$ export DISPLAY=<displayname>:0

1.2 Delete the cache file, for example

$ cd <SASHOME>/SASVersionedJarRepository/eclipse
$ rm
1.3Invoke the SAS Deployment Manager 9.3

From the SASDeploymentManager directory execute, for example

$ cd <SASHOME>/SASDeploymentManager/9.3
$ ./

1.4 Select a language in the Choose Language box

1.5 Select Rebuild Web Applications

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

1.7 Specify Connection Information, including the sasadm User ID and Password

1.8 Select Forecast Analyst 5.1 as the Web Application to Rebuild

1.9 Verify the information on the Summary screen and select Start

1.10 Select Finish when the deployment is complete

This process will update the Forecast Analyst Work Bench ear in <CONFIGDIR>/Lev1/Web/Staging and place the updated exploded ear in <CONFIGDIR>/Lev1/Web/Staging/exploded. The Forecast Analyst Work Bench ear includes:

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(R) 9.3 Intelligence Platform: Middle-Tier Administration Guide, Third Edition for more details.

Clearing 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, delete the tmp folder located at


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:

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

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

For Windows platforms, run the following script:

And clear the following directory contents:
C:\Documents and Settings\DefaultUser\Local Settings\ApplicationData\javasharedresources\

Clearing Cache for JBoss instance
Delete the contents under

These folders are created dynamically when we start the Server.

This completes the installation of hot fix J56007 on Linux for x64.