Inspecting CGIMessenger.log

Because something may go wrong as you install and deploy your WebObjects applications, the WebObjects Adaptor includes a debugging feature. To trigger the WebObjects Adaptor's debugging mode, follow these instructions.


Using logWebObjects on UNIX systems

Log in as (or su to) root and open a Terminal.app command window.

  1. create an empty /tmp/logWebObjects file
    touch /tmp/logWebObjects
  2. enter
    tail -f /tmp/CGIMessenger.log

This will log any activity of the WebObjects adaptor, and you will be able to trace the WebObjects Adaptor behavior as it tries to connect to the WebObjects application. Do not forget to remove the /tmp/logWebObjects file to stop the logs when you have successfully deployed your WebObjects application.


Using logWebObjects on Windows NT systems

In order to enable debugging you should create the logWebObjects file in the directory specified by the TEMP environment variable.

You can use Notepad to view the resulting CGIMessenger.log file. Keep in mind that the WebObjects Adaptor changes the contents of the CGIMessenger.log file as it responds to each request for a WebObjects application, so you may need to close and reopen the file in order to monitor the WebObjects Adaptor's activity.