[Version 5.0.2 and later]Configuring access logging for internal Web server HTTP transport

Why and when to perform this task

To debug potential problems with using the HTTP transport as an internal Web server, you can use the following access logging capabilities.

Steps for this task

  1. Turn access logging on.
    To turn access logging on, add the following Custom Property to the HTTP Transport's configuration settings, and set the value to false:
    
    Property name: AccessLogDisable 
    Values: True/False
    Default: Access log is disabled by default

    When you are ready to turn access logging off, set the value of the AccessLogDisable property back to true.

  2. To specify your own access log file, add the following property to the transport section of the server.xml file:
    
    Property name: AccessLog 
    Value: <filename>
    Default Value: logs/<server instance>/http_access.log
    The default access log file is logs/<server_instance>/http_access.log. Access log entries will have the format:
    <hostname or IP> <user agent> [<local time> -<status code>] <thread id> <http request> <status code> <bytecount>

    Note: If you are going to be using access logging for multiple HTTP transports in a single HTTP server, make sure you specify a unique filename for the access log file associated with each HTTP transport.

  3. Restart the server.

Results

If you have enabled access logging, there will be an access log in the location you specified.

Related tasks
Configuring transports
Configuring error logging for internal Web server HTTP transport



Searchable topic ID:   tcfg_intserver_access
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tcfg_intserver_access.html

Library | Support | Terms of Use | Feedback