Siebel Application Deployment Manager Guide > Siebel ADM Logging Capabilities and Troubleshooting >

Configuring Siebel ADM Framework Log Files

The Siebel Application Deployment Manager (ADM) logging capabilities can be configured to control the amount of data logged or number of log files retained during an ADM deployment. For more information on configuring ADM logging options, see:

• Configuring ADM Log Files on Siebel Management Server and Siebel Management Agent
• Configuring ADM Log Files on Siebel Servers
• Configuring ADM Server Component Log Files

Configuring ADM Log Files on Siebel Management Server and Siebel Management Agent

This topic describes configuring log files used by ADM on the Siebel Management Server and Siebel Management Agent. For more information on these log files, see About ADM Log Files on Siebel Management Server. The following configurations are available for the log files:

• Log level. The level or amount of information recorded in the log file.
• Log file size. The size of the log file before it is closed.
• Log file cycling. The number of log files saved and recorded in order. Each new log file is appended with a number in sequence. To read the log files in chronological order, open the log file with the highest number. The value for this property indicates the number of log files maintained; that is, if the number of log files saved equals the value set for this property, the oldest log file is deleted when the next log file is created.

NOTE:  The default log level is set to INFO for Siebel Management Server and Management Agent, as well as for ADM server components. Increasing these log levels to FINE slows down the deployment.

To configure the Management Server and Management Agent logging behavior

1. Navigate to the .properties file:
   • On the Siebel Management Server, navigate to the CMSLogging.properties file in the following location: MgmtSrvrInstallDir\config.
   • On the Siebel Management Agent environment, navigate to the AgentLogging.properties file in the following location: MgmtAgentInstallDir\config.
2. To configure the log level, set the com.siebel.adm.mgmtsrvr.deploy.deploymgr.level property in the .properties file to the appropriate level.

   See the following table for the values.

   Log Level	Description
   FINE	Log level providing tracing information, which is useful for debugging.
   INFO	Log level providing informational messages. This setting is the default value.
   WARNING	Log level providing information on potential problems during the deployment. This setting is recommended for normal execution.
   SEVERE	Log level providing information on a serious problem during the deployment.

   An inheritance behavior is based on the log level setting; that is, if you select INFO level, the WARNING and SEVERE level log details are also recorded.

3. To configure the log file cycling, set the java.util.logging.FileHandler.count property in the CMSLogging.properties file to an integer value greater than 0.
4. To configure the log file size, set the java.util.logging.FileHandler.limit property to a value in bytes.

   By default, there is no limit on the log file size.

Configuring ADM Log Files on Siebel Servers

Configuring ADM log files on Siebel Servers requires setting the log levels for Siebel Server event types. For more information on configuring Siebel Server log files, see Siebel System Monitoring and Diagnostics Guide.

Configuring ADM Server Component Log Files

Configuring the ADM server component log files requires setting the log levels for component event types. For more information on configuring Siebel Server component log files, see Siebel System Monitoring and Diagnostics Guide.