Security event logging

Security events on a service integration bus are logged as audit or error records in the SystemOut.log file for the bus.

Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.
A security event is the outcome of an attempt by a connecting client application to authenticate to a bus. There are two possible outcomes: authentication success, and authentication failure. Success is logged as an audit record, and failure as an error record. You can control the type and number of audit and error records logged for a bus by configuring a custom property for the bus, in the administrative console. The property is a name-value pair called audit.bus.authentication that can have one of the following three string values:
all
Audit every attempt to authenticate to the bus.
failure
Audit only failure to authenticate to the bus.
none
Do not audit any attempt to authenticate to the bus.
Concept topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 08:46 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=cjr0470_
File name: cjr0470_.html