Installation Instructions for Hot Fix B86001
64-bit Enabled AIX
Hot fix B86001 addresses the issue(s) in SAS Web Analytics 5.3_M3 on 64-bit Enabled AIX as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/B86.html#B86001
IMPORTANT NOTES
-
You must have SAS Web Analytics 5.3_M3 installed on your system before applying this hot fix.
Refer to SN-35968 for instructions on how to determine which product releases you have installed.
-
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.
-
You must have Administrator Privileges on your CLIENT or SERVER machine.
-
All currently active SAS sessions, daemons, spawners and servers must be terminated
before applying this hot fix.
- This hot fix should be installed using the same userid who performed the initial
software installation.
PRE-INSTALLATION INSTRUCTIONS
Before beginning, note that the following actions will fix a number of issues, but they
will also undo any customizations that administrators have made to the existing ETL
processes and reporting mechanisms. Specifically, all customizations to the ETL's aggregate
jobs will be undone. The stored processes which feed the WRS reports have also changed.
To ensure that changes are not lost, users are advised to make note of all changes to be
retained, because they will have to be reinstituted manually. Read the instructions
carefully before beginning.
Prior to installing the hotfix
- Back up all physical data and metadata.
- Copy or move any customized reports, information maps and stored processes under
/Products/SAS Web Analytics to another folder.
- Shut down all sas sessions and services.
- Unschedule any flows.
- Download hot fix B86001 for your operating system and save it to your
local hard drive.
INSTALLATION
Follow these steps to install the hot fix.
1. The installer downloaded is B86001r6.bin. Verify that the installation binary
has execute permission. If it does not, use the chmod command to make
it executable.
$> chmod 755 B86001r6.bin
2. Set your $DISPLAY environment variable
export DISPLAY=<your_node_name>:0
3. Execute B86001r6.bin
<path_to_downloaded_file>/B86001r6.bin
For example:
./B86001r6.bin
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 Installation Tool
(MIT) documentation for more details on the installation of hot fixes.
The content of this hot fix is listed in the hot fix manifest.
POST-INSTALLATION INSTRUCTIONS
Step 1: Restart servers
Start all the SAS servers that were stopped in the Pre-Installation Instructions, including
Connect, Object Spawner, Metadata server, Application Server, OLAP Server, Table Server, etc.
Step 2:Update daily total metadata and template_jobs files
- Update daily total metadata
- Open SAS Management console
- Navigate to \Products\SAS Web Analytics\Data Sources\Report Data;
left click on the folder
- Right click on it and select Import SAS Package
- Browse for the file; the package file is named f2wa53_weba_map_daily_total.spk
and will exist in
- Windows - !SASROOT\weba\sasmisc\config\Deployment\Packages
- Unix - !SASROOT/misc/weba/config/Deployment/Packages
- Check the Include Access Controls box
- Select Next three times
- Select the target application server that corresponds to the default SASApp
and click Next (Default: SASApp)
- Repeat the process for the WORK library (Default: Work Library)
- Repeat the process for RPT_DAILY_TOTAL (Keep the default)
- Repeat the process for STP_WEBA_DAILY_TOTAL (Keep the default)
- Select Next and then Finish
- Replace the template_jobs_win.subprop file with the template_job_win.subprop file
- The files are located in
- Windows - !SASROOT\weba\sasmisc\config\Deployment\Packages
- Unix - !SASROOT/misc/weba/config/Deployment/Packages
- Rename template_jobs_win.subprop to template_jobs_win.subprop.old
- Open the template_jobs_win.subprop file and locate the following lines
[Connections: Application Server]
ApplicationServer[1].SourceName=SASApp
ApplicationServer[1].TargetName=SASApp
- Open the template_jobs_win.subprop.orig file and locate the following lines
[Connections: Application Server]
ApplicationServer[1].SourceName=SASApp
ApplicationServer[1].TargetName=@oma.appserver.servercontext.name@
- Replace @oma.appserver.servercontext.name@ with the value of the
ApplicationServer[1].TargetName in the template_jobs_win.subprop.old file
- Save the edited template_jobs_win.subprop.orig
as template_jobs_win.subprop
Step 3:Update existing web mart metadata
Manual Instructions:
- Open DI Studio
- For regenerate the metadata for each web mart
- Open SAS Management Console
- Go to System/Applications/SAS Web Analytics/Web Analytics 5.3.3/Sites
- Delete the folder for each web mart that is going to be regenerated
- Open DI Studio
- Go to \SharedData\WebAnalytics or the folder where the web mart
job folders reside and either rename or delete each web mart folder
- If one or more jobs have been customized
- Rename the folder
- Rename the Library object under the EvntSrc, WaAnly,
WaCnfg, WaMart, WaSrc and WaWork
- If none of the job have been customization delete the folder
- Open Products -> SAS Web Analytics -> Sample Jobs -> Site Initialization
- Open the properties of the Weba_Site_Initialization Transformation
- Select Options Tab
- Enter the old Webmart name
- Enter in metadata user id and password
- Enter in the root directory where the web mart subdirectories reside
- For Data mart table type, choose SAS or Oracle depending on which mart is
being converted via the hot fix
- Select Yes for Recreate Only the Metadata
- Follow regular instructions for the other fields
- Run
Using the utility program:
A utility program, weba_f2wa53_hotfix_prep.sas, for updating an existing web mart’s
metadata is part of the hot fix and is located in the following directory:
- Windows: !SASROOT\weba\sasmisc
- Unix: !SASROOT/misc/weba
weba_f2wa53_hotfix_prep.sas does the following:
- Re-initializes a web mart’s metadata after either completely deleting the existing metadata
or renaming the existing libraries and the folder containing the jobs
- Determines if any of the following aggregates need to be regenerated:
- aggr_ref_term* - if session_total values are missing the aggregate will
need to be regenerated
- aggr_hourly_status* - if daily_sessions values are missing the aggregate
will need to be regenerated
- aggr_daily_total* - if daily_sessions values are missing the aggregate
will need to be regenerated
- aggr_platform - if page_sum values are missing the aggregate will need to be regenerated
- Renames any aggregates that need regeneration by replacing the AGGR prefix with
the ARCH prefix
Instructions for using the weba_f2wa53_hotfix_prep.sas utility are contained within
the header information of the program. If the utility program runs successfully the metadata will
be updated and a list of additional aggregate jobs will be listed in the log if additional aggregates
need to be regenerated.
To run the weba_f2wa53_hotfix_prep.sas utility program, either open an interactive
SAS session or use a batch SAS session that has access to Web Analytics macros.
Step 4: Regenerate aggregates
- Preparing individual web marts for running ETL
- Go to folder that contains the web mart jobs folders, for example,
/Shared Data/Web Analytics/my mart
- Go to the 5.3.3 Jobs/ETL Jobs folder and update jobs with appropriate customizations
- Hotfix change - weba_1900_agg_page_status has been redesigned to create 5 sets of
aggregates instead of one; any customizations will need to be made to all 5 aggregates
- Customize jobs - use the jobs within the old ETL job folder to customize the new jobs
- Export the job code from DI Studio
- Schedule the weba_1900_agg_page_status job for each mart that has been updated;
see DI Studio help on scheduling a job
- Schedule any other updated job if necessary
- Aggregates regeneration
The following jobs must be run to generate aggregates prior to running the first ETL:
- weba_1900_agg_page_status
- see the weba_f2wa53_hotfix_prep.log to determine if one or more of the
following aggregate jobs will need to be run
- WEBA_1800_AGGR_HOURLY_STATUS
- WEBA_1500_AGGR_REF_TERM
- WEBA_2000_AGGR_PLATFORM
- WEBA_2050_AGGR_HOURLY_STATISTICS
Manual Instructions:
Follow the instructions in the SAS Web Analytics Administration Guide, pp. 162 - 170, for
regenerating the aggregates within DI Studio.
Using the utility program:
A utility program, weba_regen_aggregates.sas, for updating an existing web mart’s
metadata is part of the hotfix and is located in the following directory:
- Windows - !SASROOT\weba\sasmisc
- Unix - !SASROOT/misc/weba
Instructions for using the weba_regen_aggregates.sas utility are contained within
the header information of the program. All aggregate jobs must be deployed from SAS Data Integration
Studio into the directory specified within weba_regen_aggregates.sas prior to running the program.
To run the weba_regen_aggregates.sas utility program, either open an interactive SAS
session or use a batch SAS session that has access to Web Analytics macros.
Step 5: Restart the ETL
- The following steps should be completed prior to restarting the ETL:
- a web mart’s metadata should have been updated
- ETL jobs updated with any customizations
- aggregates regenerated
- weba_1900_agg_page_status job deployed to the directory where the ETL jobs for the
web mart are stored
- Once all the steps are completed ETL’s can be scheduled.
This completes the installation of hot fix B86001 on 64-bit Enabled AIX.