Example Message Log Configuration and Output

7-6 Oracle WebLogic Server SIP Container Developer’s Guide Example 7–5 shows a sample message-debug configuration using log rotation. Example 7–5 Sample Log Rotation Configuration ?xml version=1.0 encoding=UTF-8? sip-server xmlns=http:www.bea.comnswlcpwlss300 xmlns:sec=http:www.bea.comnsweblogic90security xmlns:xsi=http:www.w3.org2001XMLSchema-instance xmlns:wls=http:www.bea.comnsweblogic90securitywls message-debug logging-enabledtruelogging-enabled file-min-size500file-min-size log-filenamesip-messages.loglog-filename rotation-typebyTimerotation-type number-of-files-limitedtruenumber-of-files-limited file-count5file-count rotate-log-on-startupfalserotate-log-on-startup log-file-rotation-dirold_logslog-file-rotation-dir rotation-time00:00rotation-time file-time-span20file-time-span date-format-patternMMM d, yyyy h:mm a zdate-format-pattern message-debug sip-server rotation-type Configures the criterion for moving older log messages to a different file. This element may have one of the following values: ■ bySize—This default setting rotates log messages based on the specified file-min-size. ■ byTime—This setting rotates log messages based on the specified rotation-time. ■ none—Disables log rotation. number-of-files-limited Specifies whether or not the server places a limit on the total number of log files stored after a log rotation. By default, this element is set to false. file-count Configures the maximum number of log files to keep when number-of-files-limited is set to true. rotate-log-on-startup Determines whether the server must rotate the log file at server startup time. log-file-rotation-dir Configures a directory in which to store rotated log files. By default, rotated log files are stored in the same directory as the active log file. rotation-time Configures a start time for log rotation when using the byTime log rotation criterion. file-time-span Specifies the interval, in hours, after which the log file is rotated. This value is used when the rotation-type element is set to byTime. date-format-pattern Specifies the pattern to use for rending dates in log file entries. The value of this element must conform to the java.text.SimpleDateFormat class. Table 7–3 Cont. XML Elements for Configuring Log Rotation Element Description Part III Part III Using Diameter This part describes developing applications using Diameter. Diameter is a peer-to-peer protocol that involves delivering attribute-value pairs AVPs. A Diameter message includes a header and one or more AVPs. The collection of AVPs in each message is determined by the type of Diameter application; the Diameter protocol also allows for extension by adding new commands and AVPs. Diameter enables multiple peers to negotiate their capabilities with one another, and defines rules for session handling and accounting functions. WebLogic Server includes an implementation of the base Diameter protocol that supports the core functionality and accounting features described in RFC 3588 http:www.ietf.orgrfcrfc3588.txt . WebLogic Server uses the base Diameter functionality to implement multiple Diameter applications, including the Sh, Rf, and Ro applications described later in this document. You can also use the base Diameter protocol to implement additional client and server-side Diameter applications. The base Diameter API provides a simple, Servlet-like programming model that enables you to combine Diameter functionality with SIP or HTTP functionality in a converged application. Part VI contains the following chapters: ■ Chapter 8, Using the Diameter Base Protocol API ■ Chapter 9, Using the Profile Service API ■ Chapter 10, Developing Custom Profile Service Providers ■ Chapter 11, Using the Diameter Rf Interface API for Offline Charging ■ Chapter 12, Using the Diameter Ro Interface API for Online Charging