|
Siebel Installation Guide for Microsoft Windows: Servers, Mobile Web Clients, Tools > Verifying Your System Using the Environment Verification Tool >
About the EVT Configuration File
EVT uses a configuration file (evt.ini) to determine what checks it needs to perform and for each check what settings it should be checking for. Each Siebel release has a corresponding configuration file specific for that release. This file resides under the bin subdirectory of the SIEBSRVR_ROOT directory. This file consists of two main sections:
- Overridenameserverinfo. These sections are used to provide static information that overrides the Enterprise-level information queried from the Siebel Gateway Name Server attributes. These checks execute only if the
ProcessSection parameter in the check is set to TRUE. All NAMESERVERINFO checks get information from this section if ProcessSection is set to TRUE (default is FALSE) rather than from querying the Gateway Name Server.
- CheckX. These sections contain check definitions for different Checkgroups. Refer to the evt.ini file for a detailed description of parameters used for each check section. A check definition can have the parameters shown in Table 16. Not shown in the table are check-dependent parameters, such as PARAMNAME and PARAMVALUE.
Table 16. EVT Check Definition Format
|
|
CHECKID |
Unique identifier for each check definition. |
CHECKGROUP |
The area of the application environment that is verified by this check. |
CHECKNAME |
Name of the check to run. |
SERVERTYPE |
The server type on which the check can be run—either Siebel Server, Siebel Gateway Name Server, Siebel CORBA Object Manager, Web server with SWSE, or Siebel Database Server. SERVERTYPE can have multiple delimited values separated by commas, for example, SERVERTYPE=DBSERVER,SIEBSRVR,SWSE. |
OSTYPE |
The operating system applicable to this check. OSTYPE can have multiple delimited values separated by commas, for example, OSTYPE=AIX,SOL,W32. For a list of supported operating systems for the current release, review the System Requirements and Supported Platforms on Siebel SupportWeb. |
DEPENDENCY |
This feature is used to implement conditional logic in the .ini file, for example, checking for the right Oracle client version if Oracle is the RDBMS in use. DEPENDENCY can have multiple delimited values separated by commas, for example, DEPENDENCY=Check1,Check231. |
PRIMARY |
Determines whether this check must be printed as part of the output. Checks implemented only to fulfill a dependency are not printed in the output if they prevent the next check from succeeding. |
RESULTMODE |
The value of RESULTMODE specifies how the check will be evaluated. Use one of the following values:
- Evaluate performs a text comparison and returns TRUE if the values are the same (for example, Required Value = YES).
- Inverted is the opposite of Evaluate. If Evaluate returns TRUE, inverted would return FALSE.
- VersionCheck evaluates dotted version strings (for example, the value should be 7.5.3.2 or greater).
- InvertedVersionCheck returns FALSE where VersionCheck would return TRUE.
|
ERRORLEVEL |
This parameter uses two values—WARN and FAIL—to determine whether the failure of a particular check constitutes a critical failure or just a warning. Critical failures are misconfigurations that would result in the failure of Siebel software in one form or another, whereas warnings apply to misconfigurations that may result in reduced performance, but not necessarily a software failure. |
All the parameters in the .ini file should be set to the alias and not the actual value; for example, PARAMNAME=Lang and PARAMVALUE=ENU. You can use # (pound sign) in the evt.ini file to comment out specific lines. You can also add new checks to the .ini file based on your business requirements using the parameters described in Table 16. If you decide to do so, make a copy of the file and make your modifications in the new file, then use the -f option, as described in Table 17, to point EVT to use the new configuration file.
|
