Logging of user interface calls

Application (EJB) calls to BeanConnect are logged at separate loggers (BeanConnect.ui and its child loggers). This output can assist users in diagnosing problems in their applications.

Output to the logger BeanConnect.ui may use the levels INFO, DEBUG or TRACE. For a summary, see the following table:

List of the BeanConnect.ui loggers, their levels and meaning

Logger	Level	Meaning
BeanConnect.ui.out	INFO	Logging of outbound interface calls without data
BeanConnect.ui.oltpmsg	INFO	Logging of OLTP message interface calls without data
BeanConnect.ui.data.api	DEBUG	Logging of all data transferred at the user interface
BeanConnect.ui.data.net	TRACE	Logging of all data transferred at the user interface in the form in which it is transferred in the network, i.e. possibly recoded.
BeanConnect.ui.in	INFO	Logging of the OLTP message objects transferred to and from the message endpoint application

Example 26 Control of logging output

• Logger BeanConnect.ui set to level INFO:

  All the user interface calls are logged without data.

• Logger BeanConnect.ui set to level DEBUG:

  All the user interface calls are logged together with the data transferred on these calls.

• Logger BeanConnect.ui set to level TRACE:

  All the user interface calls are logged together with the data transferred on these calls and any encoded data.

• Logger BeanConnect.ui.out set to level INFO and BeanConnect.ui.data.net set to level TRACE:

  All the outbound interface calls are logged together with the encoded data. Calls at the OLTP message interface and data transferred at the outbound interface are not logged.