class="sapTxtSml" style="font-weight: normal;"> After couple of days of fiddling around, API browsing and reading documentation I was able to understand how the log-configuration.xml file enabled developers to specify various logging parameters at design time and how log configurator enabled at run time to manage log levels. This web log is an attempt to answer some of the questions from the WebDynpro forum and also an easy pickup point to enable logging within WebDynpro applications. This web log is not tutorial a on how the logging apis work but a description of the available tools and services with in the Web AS that allows for easy management of the logging framework. Different logging requirements for an application As far I see it the stakeholders for logged data from an application would be a 1) developer 2) System Administrator and 3) Application support personnel. The log data in question here is typically from a business application in production. What differentiates these people is the kind of the data that each of them would want to view and the different conditions under which they would want to view it. Some of the possible scenarios are. - Resource usage such as memory or connection management details at peak loads by System administrator
- Application tracing (methods called, events fired, exceptions raised) to debug an error condition experienced by an end user by a Developer
- Application support personnel in tandem with the Developer to answer why a functional aspect of the application differs in behaviour under certain contexts.
Applying the above requirements to an application: Say the primary class that is connected to database connection management is com.sdn.trial.wd.dbpool.ConnectionHandlerCust and the core class that is involved in a business process is com.sdn.trial.wd.orders.PurchaseOrderProcess
The requirement is to log runtime connection pooling details into a separate file sdnconnectionusg.trc and source purchase order creation details into the general application log used by the system sdnapplications.log. |