Message Logging
If communications cannot be established with the JADE system, a jadehttp.htm file is output, advising you that the service is down. This file must be in the same directory as the jadehttp library file on the Internet server.
The jadehttp library file reads an initialization file called jadehttp.ini, located in the same directory as the library.
A new log file is always opened after the jadehttp.dll library has been initiated rather than appending to the existing log file. The current date and time is always added to the file name when a new file is created (when the library is initiated or when a log file switch occurs). When a jadehttp.log log file reaches 1M byte, a new log file is created.
For details about the parameters available in the [Jadehttp Logging] section of the jadehttp.ini file that enable you to specify your message logging requirements during Web-enabled applications, see "[
Processing problems in the jadehttp library are logged to the jadehttp.log file, located in the same directory as the library. Failures that occur result from the unavailability of the JADE system.
The IIS server logs all HTML client requests to its own log file. You should enable IIS logging, and set the option to automatically start a new file each day. The jadehttp library file also records routine messages to the log when it is initiated and closed, and when connections to the named pipe or TCP/IP channels are made and broken.
