Validation of a correct deployment is an important topic for IT organizations. Organizations need to be able to validate correctness following an initial deployment. SAS provides tools to help validate that SAS software has been correctly deployed. However, how you use these tools is dependant on your specific deployment.
With SAS 9.2, several new validation tools are available and many existing tools are enhanced. This document briefly discusses these validation tools relative to the following topics, and provides context for how these tools might be used:
The SAS Installation Qualification Tool (SASIQ) does a checksum test against Foundation SAS files. This tool verifies the validity of the installed files. This tool is especially useful if it is run after applying a hot fix to validate that hot-fix files were installed correctly.
The SAS Operational Qualification Tool (SASOQ) invokes the operational tests. It runs the tests and validates the output from the test.
For more information about the SAS Qualification tools, see the SAS® 9.2 Qualification Tools User’s Guide.
Logs are created during the deployment process, and are created in each SASHOME directory. Deployment logs are always created and contain detailed information that might require knowledge of internal systems to interpret. The level of detail captured is pre-set by SAS, and is not affected by administrative log-level settings. Deployment logs are separate from configuration logs and from runtime logs.
SAS Note 35426. "Logs that can be used to troubleshoot the SAS®® 9.2 (TS2M0) installations" provides additional information about the SAS deployment logs.
Many SAS servers that are defined in metadata and displayed via SAS® Management Console can be validated. You can do this immediately after installation and configuration or during troubleshooting. SAS provides a number of validation tools that you can use to determine the status of your SAS BI server components:
Documentation about these validation tools are available in the SAS® 9.2 Intelligence Platform: System Administration Guide.
There are processes that enable you to confirm that the various SAS servers you have deployed are running properly. Validation processes for the following tools are explained in the SAS® 9.2 Intelligence Platform: System Administration Guide.
To display the status of a server or spawner from a command line, you can use the -status option of the script for that server or spawner:
For information about this topic, see the SAS® 9.2 Intelligence Platform: System Administration Guide.
The SAS Deployment Tester is a tool that is designed to be used by consultants and system administrators. In a SAS Intelligence Platform deployment, SAS Deployment Tester is delivered as a plug-in for SAS Management Console. The specific tests that SAS Deployment Tester runs are delivered as part of the software that is being tested.
Primary documentation on this tool is available via the online help system. Follow these steps to access the SAS Deployment Tester online help:
For information about this topic, see the SAS® 9.2 Intelligence Platform: Installation and Configuration Guide.
The information on this "Migration" Web page will help you design a validation plan for your BI migration.
To validate your BI migration, follow the step-by-step instructions in Chapter 6, "Validating Your SAS Migrated Deployment" in the SAS® Intelligence Platform: 9.1.3 to 9.2 Migration Guide.This chapter covers the following topics:
With SAS 9.2, you have the option to put the metadata server into quiesce mode, which means that access is suspended. By suspending user access to the system, the administrative mode provides a consistent environment during the validation process. Further information about this topic is available in the SAS® 9.2 Intelligence Platform: System Administration Guide.
During maintenance release installation a Deployment Summary is generated with a list of the products that were installed and upgraded. Audit files for the maintenance release identify all of the changes that occurred during an installation of a maintenance release.
For information about the maintenance release Deployment Summary and audit files, see the "About the Installation Files" section on page 19 of "Maintenance Planning for SAS® 9.2".
Although not specifically a validation process, the installation builds a file that describes the configuration of the system and enables the installer to optionally send the file to SAS at the end of each run of the SAS® Deployment Wizard. Regardles of whether the file is sent to SAS, it is created and kept on the system as SDW_sysinfo_yyyymmdd_order- number.dat.
For information about this topic, see the Electronic Product Registration Web page.
|Product Family||Product||System||SAS Release|
|SAS System||Base SAS||Microsoft Windows Server 2003 Datacenter Edition||9.2 TS2M0|
|Microsoft® Windows® for x64||9.2 TS2M0|
|Microsoft Windows Server 2003 Enterprise 64-bit Edition||9.2 TS2M0|
|Microsoft Windows Server 2003 Datacenter 64-bit Edition||9.2 TS2M0|
|Microsoft® Windows® for 64-Bit Itanium-based Systems||9.2 TS2M0|
|Microsoft Windows Server 2003 Enterprise Edition||9.2 TS2M0|
|Microsoft Windows Server 2003 Standard Edition||9.2 TS2M0|
|Microsoft Windows XP Professional||9.2 TS2M0|
|Windows Vista||9.2 TS2M0|
|64-bit Enabled AIX||9.2 TS2M0|
|64-bit Enabled HP-UX||9.2 TS2M0|
|64-bit Enabled Solaris||9.2 TS2M0|
|HP-UX IPF||9.2 TS2M0|
|Linux for x64||9.2 TS2M0|
|OpenVMS on HP Integrity||9.2 TS2M0|
|Solaris for x64||9.2 TS2M0|
|Date Modified:||2009-07-24 14:03:31|
|Date Created:||2009-05-04 13:10:19|