Hot fix L28001 addresses the issue(s) in SAS Decision Services 6.2 as documented
in the Issue(s) Addressed section of the hot fix download page:
https://tshf.sas.com/techsup/download/hotfix/HF2/L28.html#L28001
L28001 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as indicated.
L25001 updates SAS Decision Services Design Mid-Tier 6.2
L26001 updates SAS Decision Services Engine Server 6.2
L27001 updates SAS Decision Services Logical File Types 6.2
L22001 updates SAS Decision Services Monitor 6.2
L23001 updates SAS Decision Services Plug-ins for SAS Management Console 6.2
L24001 updates SAS Decision Services Server Configuration 6.2
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, L28001pt.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 L28001pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of L28001pt.zip. The hot fix installation process will extract the contents as needed.
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 L28001pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.
The hot fix installation process generates the log file
<!SASHOME>/InstallMisc/InstallLogs/IT_date-and-time-stamp.logfor 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.
For each product installed, click the link to be redirected to post-installation instructions.
L25001 updates SAS Decision Services Design Mid-Tier 6.2
L26001 updates SAS Decision Services Engine Server 6.2
L27001 updates SAS Decision Services Logical File Types 6.2
L22001 updates SAS Decision Services Monitor 6.2
L23001 updates SAS Decision Services Plug-ins for SAS Management Console 6.2
L24001 updates SAS Decision Services Server Configuration 6.2
L25001 updates SAS Decision Services Design Mid-Tier 6.2
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.4
From the SASDeploymentManager directory launch sasdm.sh. The default installation path for the SAS Deployment Manager is
SASHOME/SASDeploymentManager/9.4
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 Decision Services Design 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 Decision Services Design 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.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications, for more details.
L26001 updates SAS Decision Services Engine Server 6.2
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.4
From the SASDeploymentManager directory launch sasdm.sh. The default installation path for the SAS Deployment Manager is
SASHOME/SASDeploymentManager/9.4
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 Decision Services Engine Server 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 Decision Services Engine Server 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.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications, for more details.
L27001 updates SAS Decision Services Logical File Types 6.2
NONE
L22001 updates SAS Decision Services Monitor 6.2
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.4
From the SASDeploymentManager directory launch sasdm.sh. The default installation path for the SAS Deployment Manager is
SASHOME/SASDeploymentManager/9.4
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 Decision Services Monitor 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 Decision Services Design 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.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications, for more details.
L23001 updates SAS Decision Services Plug-ins for SAS Management Console 6.2
NONE
L24001 updates SAS Decision Services Server Configuration 6.2
Note that these instructions provide example filenames and directory names based on a Windows
deployment. If your deployment is to a different operating system please make the appropriate adjustments.
There are seventeen sas files that are included in this Hotfix. They will need to be modified and reloaded to the Federation Server database. Instructions for modifying these sas files are as follows.
tap_logger.sas.orig tap_hash.sas.orig tap_utilities.sas.orig tap_datatype.sas.orig tap_encoder.sas.orig tap_tokenizer.sas.orig tap_datetime.sas.orig tap_array.sas.orig tap_table.sas.orig tap_sqltable.sas.orig tap_sqlstmt_cache.sas.orig tap_gio.sas.orig tap_in_context.sas.orig tap_out_context.sas.orig tap_context.sas.orig loadutilpackages.sas.orig droputilpackages.sas.orig
Ex: proc ds2 nolibs noprompt="@sas.activity.connection.string@"; Becomes: proc ds2 nolibs noprompt="driver=remts;server=<Federation Server hostname>;port=21032;protocol=bridge;uid=fedsrv;pwd=ENTER FEDERATION SERVER ADMIN PASSWORD;conopts=(DSN=BASE_DSN)";
To simplify this step, copy the proc ds2 statement from the .sas files of the same name to the .sas.orig file. Be sure to include the actual Federation Server Admin password in the connection string.
Ex: %include "@sas.util.sas.code@tap_logger.sas"; Becomes: %include "<CONFIGDIR>\Lev1\Applications\SASDecisionServicesServerConfig6.2\SASCode\tap_logger.sas";
The loadutilpackage.sas program will load all the sas files in the <CONFIGDIR>\Lev1\Applications\SASDecisionServicesServerConfig6.2\SASCode directory. Be sure all the files to be loaded contain the Federation Server Admin password.
From SAS Display Manager, execute <CONFIGDIR>\Lev1\Applications\SASDecisionServicesServerConfig6.2\SASCode\loadutilpackages.sas.
This completes the installation of hot fix L28001 on 64-bit Enabled AIX.