config.script

Software Testing Automation Framework (STAF)的开发代码

all platforms.  This is default mode.
:li.:xph.WINDOWS:exph. - This indicates that windows-based authentication should be used.
This mode is only available on Windows systems.
See :hdref refid=winuser. for more information.
:li.:xph.NONE:exph. - This indicates that usernames will be honored but not authenticated.
In this mode, passwords are ignored and processes are started under the indicated
username.  This mode is only available on Unix systems.
.*:li.PASSWD - This indicates that usernames/passwords will be authenticated using
.*entries stored in the /etc/passwd file.  This mode is only available on Unix systems.
.*:li.SHADOW - This indicates that usernames/passwords will be authenticated using
.*entries stored in the /etc/shadow file.  This mode is only available on Unix
.*systems.
:eul.
:note.Previously, :xph.PASSWD:exph. and :xph.SHADOW:exph. were supported values
for the :xph.PROCESSAUTHMODE:exph. on Unix systems, but support for for these
modes has been removed.
:p.
You may also change this setting dynamically using the PROCESS service's SET command.
:p.:xph.DEFAULTAUTHUSERNAME:exph. specifies the username under which processes
will be started, by default.  Note, this option IS valid even if process
authentication has been disabled.
You may also change this setting dynamically using the PROCESS service's SET command.
:p.:xph.DEFAULTAUTHPASSWORD:exph. specifies the password with which processes
will be authenticated, by default.  Note, this option IS valid even if process
authentication has been disabled.
You may also change this setting dynamically using the PROCESS service's SET command.
:p.:xph.DEFAULTAUTHDISABLEDACTION:exph. specifies what default action should be
taken if the user specifies a username/password on a request to start a process
when process authentication has been disabled.  The following values are
recognized:
:ul compact.
:li.:xph.IGNORE:exph. - This indicates that the username/password should be ignored.  The
request will be processed as if the user had not specified these parameters.
This is the default.
:li.:xph.ERROR:exph. - This indicates that an error should be passed back to the user.
:eul.
You may also change this setting dynamically using the PROCESS service's SET command.
:p.:xph.DEFAULTSHELL:exph. specifies the default shell to use when starting a
process via a separate shell.  The default shell used for Unix systems is /bin/sh.
The default shell used for Windows NT/2000/XP/2003/Vista systems is "cmd.exe /c".
The default shell used for Windows 95/98/ME systems is "command.com /c".
You may also change this setting dynamically using the PROCESS service's SET command.
:p.:xph.DEFAULTNEWCONSOLESHELL:exph. specifies the default shell to use when
starting a process in a new console window (e.g. :xph.NEWCONSOLE:exph.) via a separate shell, overriding
the :xph.DEFAULTSHELL:exph. value if specified.
You may also change this setting dynamically using the PROCESS service's SET command.
:p.:xph.DEFAULTSAMECONSOLESHELL:exph. specifies the default shell to use when
starting a process in the same console as STAFProc (e.g. :xph.SAMECONSOLE:exph.) via a separate shell,
overriding the :xph.DEFAULTSHELL:exph. value if specified.
You may also change this setting dynamically using the PROCESS service's SET command.
:p.
A shell value can contain substitution characters described in the following table.
:table cols='* 4* *' align='c l c'.
:tcap.Substitution Characters for Shells
:thd.
:c.Substitution character
:c.Description
:c.Supported systems
:ethd.
:row.
:c.%c
:c.Substitute the values specified by the :xph.COMMAND:exph. and
:xph.PARMS:exph. options.
:c.Windows and Unix
:row.
:c.%C
:c.Same as %c, except the substituted value will be quoted (with all
nested quotes properly escaped).
:c.Windows and Unix
:row.
:c.%p
:c.Substitute the value specified by the :xph.PASSWORD:exph. option,
or an empty string if no :xph.PASSWORD:exph. is provided.
:c.Windows and Unix
:row.
:c.%P
:c.Same as %p, except the substituted value will be quoted (with all
nested quotes properly escaped).
:c.Windows and Unix
:row.
:c.%t
:c.Substitute the value specified by the :xph.TITLE:exph. option,
or <Unknown> if no :xph.TITLE:exph. is provided.
:c.Windows and Unix
:row.
:c.%T
:c.Same as %t, except the substituted value will be quoted (with all
nested quotes properly escaped).
:c.Windows and Unix
:row.
:c.%u
:c.Substitute the value specified by the :xph.USERNAME:exph. option,
or an empty string if no :xph.USERNAME:exph. is provided.
:c.Windows and Unix
:row.
:c.%U
:c.Same as %u, except the substituted value will be quoted (with all
nested quotes properly escaped).
:c.Windows and Unix
:row.
:c.%w
:c.Substitute the value specified by the :xph.WORKLOAD:exph. option,
or <Unknown> if no :xph.WORKLOAD:exph. is provided.
:c.Windows and Unix
:row.
:c.%W
:c.Same as %w, except the substituted value will be quoted (with all
nested quotes properly escaped).
:c.Windows and Unix
:row.
:c.%x
:c.Substitute the values specified by the :xph.COMMAND:exph. and
:xph.PARMS:exph. options followed by input/output redirection, if
I/O options are specified on the :xph.PROCESS START:exph. request
(e.g. :xph.STDIN, STDOUT:exph.).  When using this option, do not
specify any redirection in the :xph.COMMAND/PARMS:exph. values.
:c.Windows and Unix
:row.
:c.%X
:c.Same as %x, except the substituted value will be quoted (with all
nested quotes properly escaped).
:c.Windows and Unix
:row.
:c.%%
:c.Substitute a %.
:c.Windows and Unix
:etable.

:notel compact.
:li.When specifying a shell value, it must contain one of the following: %c, %C, %x, %X.
:li.The use of %c versus %C, as well as %x versus %X, is highly dependent
on the shell you specify.
If the shell expects the command and parameters to be parsed as a single string,
then use %C or %X.  If the shell expects the command and parameters to be parsed as separate
strings, then use %c or %x.
:li.Specifying 'su - %u -c %C' as the shell when starting a process on a UNIX system
(so that it simulates the environment of the user specified by the :xph.USERNAME:exph. option)
will cause variables specified via an ENV option to not be set for the process.
:enotel.

:h4.Examples
:xmp.
SET CONNECTATTEMPTS 5 CONNECTRETRYDELAY 2000
.*SET MAXFILES 1000
SET MAXQUEUESIZE 1000
SET INITIALTHREADS 10 THREADGROWTHDELTA 3
SET DATADIR /test/stafdata
SET DEFAULTINTERFACE tcp
SET DEFAULTAUTHENTICATOR SampleAuth
SET ENABLEDIAGS
SET RESULTCOMPATIBILITYMODE none
SET DEFAULTSTOPUSING SIGTERM DEFAULTSAMECONSOLE
SET DEFAULTFOCUS minimized
SET PROCESSAUTHMODE windows DEFAULTAUTHUSERNAME testuser DEFAULTAUTHPASSWORD tupass
SET PROCESSAUTHMODE none DEFAULTAUTHUSERNAME guest DEFAULTAUTHDISABLEDACTION error
SET DEFAULTSHELL "C:/cygwin/bin/bash.exe -c %C"
SET DEFAULTSAMECONSOLESHELL "/bin/csh -c %C"
SET DEFAULTNEWCONSOLESHELL "xterm -title %T -e /bin/sh -c %X"
SET DEFAULTSHELL "su - %u -c %C"
:exmp.
.*
.*---------------------------------------------------------------------
.*
:ih1.configuration
:i2.variables
:ih1.variables
:i2.configuration
:h2 id=varcfg.Variables
:h3.Description
:p.You may set STAF variables in the system or shared variable pool at startup by
using the SET VAR configuration statement. SET VAR will set a variable to a certain
value. The variable is created if it does not exist.
:p.Note that you may SET multiple variables with a single request.
:h4.Syntax
:xmp.
SET &lbrk.SYSTEM | SHARED&rbrk. VAR <Name=Value> &lbrk.VAR <Name=Value>&rbrk. ...
:exmp.
:p.:xph.SYSTEM:exph. means the variable is to be set in system variable pool.
This is the default.
:p.:xph.SHARED:exph. means the variable is to be set in shared variable pool.
:p.:xph.VAR:exph. means the variable to be set. Name is the name of the variable
and Value is the value of the variable.
:h4.Examples
:xmp.
SET VAR WebServer=testsrv1.test.austin.ibm.com
SET SHARED VAR "Author1=Jane Tester" VAR "Author2=John Tester"
SET SYSTEM VAR STAF/Service/Log/Directory={STAF/Config/BootDrive}\STAF\Log
:exmp.
.*
.*---------------------------------------------------------------------
.*
:ih1.configuration
:i2.trust
:ih1.trust
:i2.configuration
:h2 id=trustcfg.Trust
:h3.Description
:p.You may grant access to machines or users by using the TRUST configuration
statement.
:p.Trust configuration statements for machines are based on the network
identification of the system.  In particular, different trust levels can be
given to the same system coming in through different networking interfaces.
Both logical and pysical identifiers may be used in trust configuration
statements for machines.
:p.Trust configuration statements for users require that you have
an authenticator registered.
:h4.Syntax
:xmp.
TRUST LEVEL <Level> < DEFAULT | MACHINE <Machine> &lbrk.MACHINE <Machine>&rbrk.... |
                      USER <User> &lbrk.USER <User>&rbrk.... >
:exmp.
:p.:xph.LEVEL:exph. is the level of trust that you wish to grant,
see :hdref refid=trstcon. for a list of trust levels.
:p.:xph.DEFAULT:exph. indicates that you wish to set the default trust level.
This is the trust level that will be used for machines which have no
explicit trust level set.  If no default has been specified in the STAF
Configuration file, the default is set to 3.
:p.:xph.MACHINE:exph. indicates a specific machine for which to set a trust
level.
The format for <Machine> is:
:xmp.
  &lbrk.<Interface>&colon.//&rbrk.<System Identifier>
:exmp.
where:
:ul compact.
:li.:xph.<Interface>:exph. is the name of the network interface.
It is case-insensitive.
If the name of a network interface is not specified, wildcard '*' is
substituted which will match any network interface name.
:li.:xph.<System Identifier>:exph. is a valid network identifier for the network
interface.  It is case-insensitive.
Logical or physical identifiers may be specified for the system
identifier.  Physical identifiers are the lowest-level identifier
available via the specified network interface.  Logical identifiers are more
human readable identifiers tha ultimately map to physical identifiers.
For example, for a TCP/IP interface, the physical identifier for a
machine is the IP address, while the logical identifier for a machine
is the hostname.
:eul.
:p.Note that you can specify match patterns (e.g. wild cards) in the
interface and the system identifier.  These patterns recognize two
special characters, '*' and '?', where '*' matches a string of
characters (including an empty string) and '?' matches any single
character (the empty string does not match).
:p.Note that if you specify the hostname in a trust specification
for a TCP/IP interface, you must specify the long host name
(and/or wildcards).
:p.Note that if you specify a port (e.g. @6500) at the end of the
system identifier, it will be removed.
:p.Requests coming from the local system will now appear as though
they came from an interface named "local" and a system identifier
of "local".  This allows you to specify a trust level for local
requests.  (In STAF V2.x, local requests were automatically granted
a trust level of 5.)
:p.:xph.USER:exph. indicates a user for which to set a trust level.
The format for <User> is:
:xmp.
  &lbrk.<Authenticator>&colon.//&rbrk.<User Identifier>
:exmp.
where:
:ul compact.
:li.<Authenticator> is the name of the authenticator.
It is case-insensitive.  If an authenticator is not specified, the default
authenticator is used.
:li.<User Identifier> is a valid user identifier for the authenticator.
It is case sensitive.
:eul.
:p.Note that you can specify match patterns in the authenticator name
and the user identifier.  These patterns recognize two special characters,
'*' and '?', where '*' matches a string of characters (including an
empty string) and '?' matches any single character (the empty string
does not match).

:h4 id=userTrustMatching.How to determine Effective Trust for a User
:p.If multiple trust specifications would match the same user,
STAF will rank the matching specifications as follows and use the
match with the highest (i.e. lowest numbered) rank:
:ol compact.
:li.Exact match of authenticator and user identifier
:li.Exact match of authenticator, wildcard match of user identifier
:li.Wildcard authenticator match, exact match of user identifier
:li.Wildcard authenticator match, wildcard match of user identifier
:eol.
If multiple trust specifications match within the same rank, the
lowest matching trust level will be used.

:h4 id=machineTrustMatching.How to determine Effective Trust for a Machine

:p.If multiple trust specifications would match the same system,
STAF will rank the matching specifications as follows and use the
match with the highest (i.e. lowest numbered) rank:
:ol compact.
:li.Exact match of interface and physical network identifier
:li.Exact match of interface and logical network identifier
:li.Exact match of interface, wildcard match of physical network identifier
:li.Exact match of interface, wildcard match of logical network identifier
:li.Wildcard interface match, exact match of physical network identifier
:li.Wildcard interface match, exact match of logical network identifier
:li.Wildcard interface match, wildcard match of physical network identifier
:li.Wildcard interface match, wildcard match of logical network identifier
:eol.
If multiple trust specifications match within the same rank, the
lowest matching trust level will be used.

:note.The user authentication overrides the machine authentication.
For example, if the machine trust level is 3 and the authenticated user
has a trust level of 4, then the handle will have a trust level of 4.
If the user has been authenticated, but there are no user authentication
trust matches, the machine trust level is used.  If there is no
machine trust level specified, then the default trust level is used.

:ih1.examples
:i2.trust
:h4.Examples
:xmp.
TRUST DEFAULT LEVEL 3
TRUST LEVEL 5 MACHINE local&colon.//local
TRUST LEVEL 5 MACHINE client1.austin.ibm.com MACHINE client3.raleigh.ibm.com
TRUST LEVEL 5 MACHINE 9.3.224.16
TRUST LEVEL 4 MACHINE tcp&colon.//mysystem.site.com
TRUST LEVEL 0 MACHINE badguy.austin.ibm.com
TRUST LEVEL 3 MACHINE tcp2&colon.//9.3.224.*
TRUST LEVEL 2 MACHINE *.austin.ibm.com
TRUST LEVEL 2 MACHINE tcp*&colon.//*.site.com