Parameter name

Parameter type

Description

 

 

 

VALUE_DATA_RULES

Operational

If the registry key specified in the KEY parameter and the

 

 

registry value specified in the VALUE parameter both

 

 

exist, then the contents of this parameter are used to

 

 

determine the status of the registry value data check. The

 

 

VALUE_DATA_RULES parameter should contain zero or

 

 

more parameter values that make up the rules. Rules will

 

 

be explained in more detail in a later section.

 

 

 

DEFAULT_RULE

Operational

Used by the collector to determine the status of various

 

 

checks if a specific rule does not apply. No more than one

 

 

parameter value should be provided. If more than one

 

 

parameter value is provided, only the first parameter

 

 

value will be used. The parameter value provided should

 

 

be one of the following: PASS, WARN, or FAIL. If the

 

 

parameter value is set to either WARN or FAIL, then a

 

 

workflow may be used. If the parameter value is set to

 

 

something other than PASS, WARN, or FAIL, errors may

 

 

occur. If no parameter value is provided, this parameter

 

 

defaults to PASS.

 

 

 

KEY_WF

Workflow

Contains the data attached to any workflow that is

 

 

generated by the registry key existence check. Zero or

 

 

more parameter values may be provided.

 

 

 

VALUE_WF

Workflow

Contains the data attached to any workflow that is

 

 

generated by the registry value existence check. Zero or

 

 

more parameter values may be provided.

 

 

 

VALUE_DATA_WF

Workflow

Contains the data attached to any workflow that is

 

 

generated by the registry value data check. Zero or more

 

 

parameter values may be provided.

 

 

 

The way this collector works depends on the data you have provided as parameters.

It first checks for the key existence if one is specified. Then it checks if the value is specified. Finally, if both are found, it verifies the rules specified in VALUE_DATA_RULES. There may be one or more rules specified. The construction of the rules is described below.

Chapter 6. Compliance subsystem implementation

173

Page 191
Image 191
IBM Tivoli and Cisco manual 173