LiveCycle® Data Services Developer's Guide

Administering Data Services Applications > Logging > Server-side service logging

Server-side service logging

You can perform server-side logging for LiveCycle Data Services requests and responses. You configure server-side logging in the logging section of the Flex services configuration file. By default, output is sent to System.out. For information about client-side logging, see Building and Deploying Flex 2 Applications.

You set the logging level to one of the following available levels:

• all
• debug
• info
• warn
• error
• none

In the filter pattern elements, you can specify the categories of information to log. In the class attribute of the target element, you can specify flex.messaging.log.ConsoleTarget to log messages to the standard output or the flex.messaging.log.ServletLogTarget to log messages to use your application server's default logging mechanism for servlets.

The following example shows a logging configuration that uses the Debug logging level:

<logging>

<!-- You may also use flex.messaging.log.ServletLogTarget. -->
    <target class="flex.messaging.log.ConsoleTarget" level="Debug">
        <properties>
            <prefix>[Flex]</prefix>
            <includeDate>false</includeDate>
            <includeTime>false</includeTime>
            <includeLevel>false</includeLevel>
            <includeCategory>false</includeCategory>
        </properties>
        <filters>
            <pattern>Endpoint</pattern>
            <!--<pattern>Service.*</pattern>-->
            <!--<pattern>Message.*</pattern>-->
        </filters>
    </target>
</logging>

In a production environment, Adobe recommends that you set the logging level to warn so that both warnings and errors are displayed. If there are warnings that occur frequently that you prefer to ignore, change the level to error so that only errors are displayed.

The following table describes the logging levels:

You can use the following matching patterns as the values of pattern elements:

• Client.*
• Client.FlexClient
• Client.MessageClient
• Configuration
• Endpoint.*
• Endpoint.General
• Endpoint.AMF
• Endpoint.FlexSession
• Endpoint.HTTP
• Endpoint.RTMP
• Endpoint.Type
• Message.*
• Message.General
• Message.Command.*
• Message.Command.operation-name

  where operation-name is one of the following: subscribe, unsubscribe, poll, poll_interval, client_sync, server_ping, client_ping, cluster_request, login, logout

• Message.coldfusion
• Message.Data.*
• Message.Data.operation-name

  where operation-name is one of the following: create, fill, get, update, delete, batched, multi_batch, transacted, page, count, get_or_create, create_and_sequence, get_sequence_id, association_add, association_remove, fillids, refresh_fill, update_collection

• Message.Remoting
• Message.RPC
• Message.Selector
• Message.Timing
• Resource
• Protocol.*
• Protocol.RTMP
• Protocol.RTMPT
• Service.*
• Service.Cluster
• Service.Data.*
• Service.Data.General
• Service.Data.Hibernate
• Service.Data.SQL
• Service.Data.Transaction
• Service.HTTP
• Service.Message
• Service.Message.*
• Service.Message.JMS (logs a warning if a durable JMS subscriber can't be unsubscribed successfully)
• Service.Remoting
• Security
• Startup.*
• Startup.MessageBroker
• Startup.Service
• Startup.Destination
• DataService.General (deprecated, use Service.Data.General)
• DataService.coldfusion
• DataService.Hibernate (deprecated, use Service.Data.Hibernate)
• DataService.Transaction (deprecated, use Service.Data.Transaction)

LiveCycle Data Services ES 2.5

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/lcds/logging_9.html

Add Comment