Bookshelf v7.8: Configuring SDDC Content Under Microsoft Windows

The Microsoft Windows Siebel Diagnostic Data Collector (SDDC) can be configured to modify or enhance the amount of information collected during a SDDC execution. A Microsoft Windows SDDC configuration file is required by SDDC to modify any configurations to the output. The configuration file is referenced during the SDDC execution. By default, a configuration file is not included with the SDDC utility. It is recommended that you contact Siebel Technical Support before using configuration files. Siebel Technical Support provides configuration files based on the specific information required.

The SDDC configuration file is divided into sections that can be used to configure the type of information and log files collected by the utility. Edit the configuration file with a text editor. See Table 34 for SDDC configuration file parameters.

Table 34. SDDC Configuration File and Parameters
Section	Parameter	Specifies
`[Main]`	`OutputDirectory`	Specifies the directory location for the creation of the SDDC directory and output files.
	`CollectLog`	Specifies whether log files are collected.
	`CollectLogArchive`	Specifies whether log archive files are collected.
	`CollectCrash`	Specifies whether crash files are collected.
	CollectStderrFiles	Specifies whether standard error files are collected.
	`CollectDump`	Specifies whether dump files are collected.
	`CollectAssert`	Specifies whether assert and prefer files are collected.
	`SiebelBinDir`	Specifies the directory location of the SIEBSRVR_ROOT binary folder.
[Registry]	`Key01`	Specifies a registry key for collection.
	`Key02`	Specifies a registry key for collection.
	`Key03`	Specifies a registry key for collection.
[CrashFiles]	`StartDate`	Specifies the start date for a range of crash files to collect.
	`EndDate`	Specifies the end date for a range of crash files to collect.
	`MatchingFiles`	Specifies the crash file extensions to collect. You can specify the collection of Siebel Flight Data Recorder (FDR) files in this section by identifying the extension FDR (for example, `*.fdr`).
`[StderrFiles]`	`StartDate`	Specifies the start date for a range of standard error files to collect.
	`EndDate`	Specifies the end date for a range of standard error files to collect.
	`MatchingFiles`	Specifies the standard error file extensions to collect.
[ProcessDump]	`StartDate`	Specifies the start date for a range of dump files to collect.
	`EndDate`	Specifies the end date for a range of dump files to collect.
	`MatchingFiles`	Specifies the dump file extensions to collect.
[AssertFiles]	`StartDate`	Specifies the start date for a range of assert files to collect.
	`EndDate`	Specifies the end date for a range of assert files to collect.
	`MatchingFiles`	Specifies the assert file extensions to collect.
[LogFiles]	`StartDate`	Specifies the start date for a range of log files to collect.
	`EndDate`	Specifies the end date for a range of log files to collect.
	`MatchingFiles`	Specifies the log file extensions to collect. You can specify the collection of Siebel Application Response Measurement (Siebel ARM) files in this section by identifying the file extension SARM (for example, `*.sarm`).
[LogArchive]	`NumArchives`	Specifies that SDDC collects log archive files from the `NumArchives` directory.
[LogArchive]	`MatchingArchiveDir`	Specifies the archive directories for collection.
[SiebelServer]	LogDir	Specifies the Siebel Server log directory in the case of not being able to connect to the Siebel Gateway Name Server.
[SiebelServer]	LogArchiveDir	Specifies the Siebel Server log archive directory in the case of not being able to connect to the Siebel Gateway Name Server.
[GatewayServer]	LogDir	Specifies the Siebel Gateway Name Server in the case the directory name is different than the default.
[WebServer]	SiebelRoot	Specifies the Siebel Server root directory in the case the directory name is different than the default.

About SDDC Parameter Configuration

The parameters StartDate, EndDate, and MatchingFiles, which appear in several Siebel Diagnostic Data Collector (SDDC) configuration file sections, have common configuration details. See Table 35 for these details.

Table 35. Common Parameter Configuration Details
Common Parameters	Configuration Details
StartDate, EndDate	Set these parameters to specify collection of data between the two dates. If `StartDate` and `EndDate` are set, do not set the parameter `MaxNumFiles`. Configure the dates in the following format: `dd-Month_Acronym-yyyy` where: `dd` = Integer of the date ranging from 01 to 31. `Month_Acronym` = A three-letter month acronym as follows: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec. `yyyy` = Integer of the year. Another valid configuration selection for the `StartDate` and `EndDate` parameters is `NONE`. If `NONE` is entered for `StartDate` and a valid date is entered for `EndDate`, files prior to the end date are collected. If `NONE` is entered for `EndDate` and a valid date is entered for`StartDate`, files from the start date to the current date are collected.
MatchingFiles	Set this parameter to collect multiple file formats using a comma-delimited list. Wildcard characters are also applicable. For example, to collect files containing `siebmtsh` in the filename with the extension `.dmp` and files of the type siebmtshmw5409.dmp, enter: MatchingFiles=siebmtsh*.dmp,siebmtshmw5409.dmp

Example of Microsoft Windows SDDC Configuration File

The following listing is an example of a Microsoft Windows Siebel Diagnostic Data Collector (SDDC) configuration file. See Configuring SDDC Content Under Microsoft Windows for parameter descriptions and configuration details.

Key02 = HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxHashTableSize

Key03 = HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxFreeTcbs

Key04 = HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort