Use this page to view the journal, a file that records some of the Web browser client and program client activity occurring on the Directory Server.
Shows the total number of journal entries generated since this journal file was started. This could be the same or more than the value in Entries held, depending on whether the oldest entries have been overwritten by more recent ones.
Shows the total number of journal entries currently stored in the journal file. The maximum value is determined by the configured maximum journal file size; once it is reached, new journal entries overwrite the oldest journal entries.
Shows the current size of the journal file in bytes.
Shows the entry number of the journal record. When the journal file is restarted or deleted, the entry number is reset back to 1, and is sequentially incremented for each following journal entry.
Shows the local date and time that the journal record was written to the journal file.
Shows the unique identifier string associated with a particular session. For a Web browser session logged onto the user interface, this is the same identifier as appears in the top right-hand corner of the Web page. For a program client session, the source network address for the request is also shown.
If no requester identifier is shown, the journal event was generated by an internal action or there was no information available about the requester.
Shows the text of the journal event, up to 128 characters.
Green text indicates that the journal event has been generated by program client requests.
Red text indicates that the journal event has been generated by Web browser requests.
Black text indicates that the journal event has been generated by the Directory Server itself.
Click this to delete this journal and start a new one. You might want to do this if you are debugging a problem with a service and you want a well-defined journal starting-point.
Click this to export the journal entries to a text file. The text file will be called journal.txt and will be saved to /var/mfcobol/logs . You might do this to load the journal file in a text editor to search for events involving specific objects or to annotate entries.
If journal.txt already exists, it will be overwritten.