About Running the Deployment Tester in Batch Mode
The Deployment Tester can be run as a batch client, which enables you to automate the testing process. To regularly check on the health of your system, you can set up your scheduling system to run the batch client daily, weekly, or on any other schedule.
The batch client can be run from any machine where the Deployment Tester batch client is installed. Before running the batch client, be sure to start the Deployment Tester server on the host machine for each component that you want to test.
Syntax for the Batch Deployment Tester Command bclient.sh | bclient.bat
-contract SAS-installation-directory/SASDeploymentTesterClient/2.1/
Contract/SASTestSuite_contract.xml -Vserver=dt-server
-Vdir=contract-file-dir
-VcontractFile=contract-file-name 96 Chapter 7 • Using the Deployment Tester
Syntax Description for the Batch Deployment Tester Command bclient.sh | bclient.bat
specifies the command for starting the batch Deployment Tester. Use -bclient.sh for UNIX or -bclient.bat for Windows.
Requirement: Required -contract
SAS-installation-directory/SASDeploymentTesterClient/2.1/Contract/SASTestSuite_contract.xml specifies the name and location of the launcher contract file,
SASTestSuite_contract.xml. This file calls other test-specific contract files. By default, the SAS Deployment Wizard installs this file in SAS-installation-directory/SASDeploymentTesterClient/2.1/Contract.
In SAS-installation-directory, specify the path where your SAS software is installed on the local machine.
Requirement: Required
Example: -contract C:/Program
Files/SASHome/SASDeploymentTesterClient/2.1/Contract/SASTestSuite_
contract.xml -Vserver=dt-server
specifies the host machine and port for the Deployment Tester server that is to run the test. Use the format host-name:port. The value that you specify depends on which SAS component you are testing. If you are running a test suite for a SAS server, then specify the SAS Deployment Server that is installed on the host machine for the server that you are testing. If you are running a test suite for Remote Services, then specify the SAS Deployment Server on the middle-tier machine where Remote Services is installed. If you are running SAS OQ or SAS IQ, then specify the SAS Deployment Server on the machine that contains the SAS software that you want to test.
If you are running only the SAS OQ or SAS IQ test suite, and if the SAS software that you are testing is on the same machine as the batch client, you can either omit this parameter or specify a value of server-local.
Requirement: This parameter is optional in the following situation: if you are running only the SAS OQ or SAS IQ test suite, and if the SAS software that you are testing is on the same machine as the batch client. In all other situations, the parameter is required.
Tip: The host machine names and ports for each instance of the Deployment Tester server are displayed under Application Management ð Deployment Tester in the Plug-ins tab of SAS Management Console.
Example: -Vserver=server.mycompany.com:10021 -Vdir=contract-file-dir
specifies the directory path for the contract file that is specified in
-Vserver=contract-file-name. The path varies depending on which test suite you are running. To determine the correct path, see “Filenames and Locations for Deployment Tester Test Suite Contracts” on page 98.
Requirement: Required -VcontractFile=contract-file-name
specifies the name of the contract file for the test suite that you want to run. To determine the correct filename, see “Filenames and Locations for Deployment Tester Test Suite Contracts” on page 98.
Using the Deployment Tester Batch Client 97
Requirement: Required -Vuserid=my_userid
specifies a valid user ID to access the component that is being tested.
Requirement: Required for the following test suites: Content Server Tests, OLAP Server Tests, Pooled Workspace Server setinit Test, Remote Services Tests, Stored Process Server Test, and Workspace Server setinit Test.
See: For details about credential requirements, see “Deployment Tester Test Suites and Their Requirements” on page 92.
-Vpassword=my_password
specifies the password associated with the user ID that is specified in -Vuserid=. The password should be encrypted using SAS proprietary 32-bit encryption. To obtain the encrypted password, use PROC PWENCODE. If you do not encrypt the password, it will be transmitted using plain text.
Requirement: Required for the following test suites: Content Server Tests, OLAP Server Tests, Pooled Workspace Server setinit Test, Remote Services Tests, Stored Process Server Test, and Workspace Server setinit Test.
Filenames and Locations for Deployment Tester Test Suite Contracts
The following table provides default directory paths and filenames for the contract files that are used for each Deployment Tester test suite. These values are used in the -Vdir=
and -VcontractFile parameters of the batch command.
Note: The directory paths that are shown here are default locations. The paths in your deployment might be different.
Test Suite Default Directory Path for Contract File for -Vdir=
Contract Filename for 98 Chapter 7 • Using the Deployment Tester
Test Suite Default Directory Path for Contract File for -Vdir=
Contract Filename for -VcontractFile Workspace
Server setinit Test
SAS-configuration-directory/Lev1/SASApp/
WorkspaceServer/dtest/WorkspaceServer
SetinitTest_contract.xml
SAS Deployment Tester Batch Command: UNIX Example
The following is an example of a batch command issued on a UNIX machine to test a SAS OLAP Server that is located on a Windows machine:
cd $SASHOME/SASDeploymentTesterClient/2.1
bin/bclient.sh -contract Contract/SASTestSuite_contract.xml \
"-Vserver=server.sas.com:10021" \
"-Vdir C:\SAS\EBIServer\Lev1\SASApp\OLAPServer\dtest\OLAPServer" \ -VcontractFile=olap_contract.xml
"-Vuserid=domain\user123"
"-Vpassword={sas002}0123456789"
SAS Deployment Tester Batch Command: Windows Example
The following is an example of a batch command issued on a Windows machine to test a SAS OLAP Server that is located on a different Windows machine:
cd C:\Program Files\SASHome\SASDeploymentTesterClient\2.1 bin\bclient.bat -contract Contract\SASTestSuite_contract.xml
"-Vserver=server.sas.com:10021"
"-Vdir=C:\SAS\EBIServer\Lev1\SASApp\OLAPServer\dtest\OLAPServer"
-VcontractFile=olap_contract.xml
"-Vuserid=domain\user123"
"-Vpassword={sas002}0123456789"
Viewing Results of Tests That Are Run from the Deployment Tester Batch Client
If you run tests on a batch basis, you can access the test results by opening the following file:
• On Windows Vista, Windows 7, and Windows Server 2008 systems: C:\Users
\user\AppData\Roaming\SAS\SASDeploymentTesterClient
\2.1\Reports\yyyymmdd\report_test-suite-name\index.html
• On other Windows systems: C:\Documents and Settings\user
\Application Data\SAS\SASDeploymentTesterClient\2.1\Reports
\yyyymmdd\report_test-suite-name\index.html
• On UNIX: user’s-home-directory/.SASAppData/
SASDeploymentTesterClient/2.1/Reports/yyyymmdd/report_test-suite-name/index.html
Using the Deployment Tester Batch Client 99
100 Chapter 7 • Using the Deployment Tester