Siebel Installation Guide for Microsoft Windows > Verifying Your Server Environment >

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 will check 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 on the Siebel Server, or of the SWSE_ROOT directory on the SWSE.

In the evt.ini file, the [CheckX] sections contain check definitions for different check groups. Refer to the evt.ini file for descriptions of parameters used for each check section. A check definition can have the parameters shown in Table 20. Not shown in the table are check-dependent parameters, such as PARAMNAME and PARAMVALUE.

Table 20. EVT Check Definition Format


Unique identifier for each check definition.


The area of the application environment that is verified by this check.


Name of the check to run.


The server type on which the check can be run—either Siebel Server, Siebel Gateway Name Server, Web server with SWSE, or Database Server (RDBMS). For values, see Optional EVT Command Line Flags.

SERVERTYPE can have multiple delimited values separated by commas, for example, SERVERTYPE=DBSERVER,SIEBSRVR,SWSE.


The operating system applicable to this check. OSTYPE can have multiple delimited values separated by commas, for example, OSTYPE=AIX,HPUX,LINUX,SOL,W32.

For a list of supported operating systems for the current release, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.


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.


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.


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.
  • inverted. The opposite of evaluate. Returns FALSE where evaluate would return TRUE.
  • versioncheck. Evaluates version strings, including dotted version strings.
  • invertedversioncheck. The opposite of versioncheck. Returns FALSE where versioncheck would return TRUE.


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.

Parameters in the .ini file must be set to the alias and not to 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 20. If you decide to do so, make a copy of the file and make your modifications in the new file. Then run EVT using the -f option, as described in Optional EVT Command Line Flags, to direct EVT to use the new configuration file.

Siebel Installation Guide for Microsoft Windows Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.