HTTP Logging

When Jetty servers used in shared resources receive requests, logs are created to capture all attempts to access the servers.

By default, logging is disabled. You can enable HTTP logging from TIBCO Business Studio for BusinessWorks and from a deployed application.

To enable and test logging from TIBCO Business Studio for BusinessWorks in the HTTP Connector Resource shared resource:

  1. In the Advanced tab, select the Enable Access Logs check box.
  2. In the Advanced tab, select Logging Configuration.
  3. Navigate to bw\<Release_Number>\config\design\logback and select logback_leveldebug.xml.
  4. Check the console logs to make sure they display content.

Note: If you use REST service binding to create the HTTP Connector resource at runtime, set the bw.engine.http.jetty.accesslogs.enable system property to true to enable Jetty logs.

To enable and test logging from a deployed application:

  1. Deploy the application on a TEA server.
  2. Enable the debug logging for appnode.
  3. Check the appnode.log file.
  4. Check for log contents similar to the following:

     

    ++++++++++++++++++++

    2017-01-06 16:26:17.609 INFO [bwResourceHTTPConnector.qtp-112]

    com.tibco.bw.http.jetty.accesslogger - [HTTP Connector: mpandav-t450:6565] mpandav-t450

    192.168.56.1 - - [06/Jan/2017:16:26:17 +0530] "GET /?hello HTTP/1.1" 200 41 "-"

    "Jakarta Commons-HttpClient/3.1" - 32 32

    ++++++++++++++++++++

Note: To populate the HTTP logs, enable debug logging for your application.

For more information on enabling HTTP access logging, see "HTTP Connector" in the TIBCO ActiveMatrix BusinessWorks™ Bindings and Palette Reference guide.

Note: The check box, Enable Access Logs, is supported only from ActiveMatrix BusinessWorks™ 6.3.2 version onwards. To enable HTTP access logging for applications created on previous versions of ActiveMatrix BusinessWorks, set the property bw.plugin.http.jetty.accesslogs to true.