WebSphere brand IBM WebSphere XML Document Management Server, Version 7.0

Audit logging

It is possible to log HTTP and SIP requests from specific users and/or roles. The audit logger will log HTTP PUT, GET, DELETE, POST requests and SIP SUBSCRIBE requests.

About this task
To specify the users/roles to log, change the REPs auditLogByUser and auditLogByRole for the AUID you want to monitor.
  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password. (Omit the password if security is not enabled.)
    3. Click Log in.
  2. Click Resources > Resource Environment > Resource Environment Providers.
  3. Click AUID > Custom Properties.
  4. Click auditLogByUser and change values to desired value.
    Option Description
    auditLogByUser Default is empty. Comma-separated list of users. If specified, then log requests and responses onlyfor these users. Specifying '*' logs all users.
Results
The output is logged in the trace.log for the server of the specified AUID. The trace.log can be found at:
  • was_profile_root/logs/server_name
Note: was_profile_root is the directory for a WebSphere® Application Server Network Deployment profile called profile_name. By default, this directory is:
  • AIX /usr/IBM/WebSphere/AppServer/profiles/profile_name
  • Linux /opt/IBM/WebSphere/AppServer/profiles/profile_name
What to do next
To enable trace, refer to the Trace Logging section of this Information Center. The required audit logging classes are
The audit logging trace levels are:
Fine
Logs the HTTP method, XCAP URI, principal making the request, and the response code going back..
Finer
Logs HTTP headers for both the request and response, along with the elements in Fine tracing.
Finest
Logs the content from the request and content in the returned response, along with the elements in Finer tracing.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.