SUPPORT / SAMPLES & SAS NOTES
 

Support

Installation Note 35787: Validation tools for SAS® 9.2 Business Intelligence installations

DetailsAboutRate It

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:

Foundation Products Validation

SAS Qualification Tools

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.

Business Intelligence (BI) Installation Validation

Using Deployment and Installation Logs

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.

Checking the Status of BI Servers

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:

SAS® Metadata Server
SAS Pooled Workspace Servers
SAS Unpooled Workspace Servers
SAS® Stored Process Server
SAS® OLAP Server
SAS® Content Server
SAS Object Spawner

Documentation about these validation tools are available in the SAS® 9.2 Intelligence Platform: System Administration Guide.

Validating the SAS® 9.2 Servers

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.

SAS Metadata Server
SAS Object Spawner
SAS OLAP Server
SAS Pooled Workspace Server
SAS Stored Process Server
SAS® Workspace Server
SAS DATA Step Batch Server
SAS® Grid Server
SAS® Content Server

Using Scripts to Test Server Status

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:

SAS Metadata Server
SAS Object Spawner
SAS OLAP Server
SAS® Table Server

For information about this topic, see the SAS® 9.2 Intelligence Platform: System Administration Guide.

Using the SAS® Deployment Tester

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:

  1. Open and log on to SAS Management Console.
  2. Expand Application Management.
  3. Click Deployment Tester.
  4. Go to Help and select Help on Deployment Tester.

For information about this topic, see the SAS® 9.2 Intelligence Platform: Installation and Configuration Guide.

Business Intelligence (BI) Migration Validation

Designing a Validation Plan

The information on this "Migration" Web page will help you design a validation plan for your BI migration.

Validating 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:

SAS 9.2 Servers
SAS Deployment Tester
SAS Clients
SAS Enterprise Guide 4.2
SAS Information Map Studio 4.2
SAS Data Integration Studio 4.2
SAS 9.2 Middle Tier and Web Clients
SAS Remote Services
Java Application Server
SAS Stored Process Web Application
SAS Web Report Studio 4.2
SAS Information Delivery Portal 4.2

Metadata Migration Validation

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.

Maintenance Release Validation

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

Electronic Product Registration

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.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemBase SASMicrosoft Windows Server 2003 Datacenter Edition9.2 TS2M0
Microsoft® Windows® for x649.2 TS2M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.2 TS2M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.2 TS2M0
Microsoft® Windows® for 64-Bit Itanium-based Systems9.2 TS2M0
z/OS9.2 TS2M0
Microsoft Windows Server 2003 Enterprise Edition9.2 TS2M0
Microsoft Windows Server 2003 Standard Edition9.2 TS2M0
Microsoft Windows XP Professional9.2 TS2M0
Windows Vista9.2 TS2M0
64-bit Enabled AIX9.2 TS2M0
64-bit Enabled HP-UX9.2 TS2M0
64-bit Enabled Solaris9.2 TS2M0
HP-UX IPF9.2 TS2M0
Linux9.2 TS2M0
Linux for x649.2 TS2M0
OpenVMS on HP Integrity9.2 TS2M0
Solaris for x649.2 TS2M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.