Using network monitoring software, the WebOffice log files can be systematically searched for specific terms in order to detect problematic log messages as quickly as possible and correct the cause.

 

The following steps for setting up log file monitoring refer to the implementation using the software HostMonitor as an example.

 

Use the Add button in the target folder to create a new test case.

 

HostMonitor: Create a new test

 

The Test Log test method is then selected in the target folder.

 

HostMonitor: Choose test method Text log

 

The test parameters change according to this selection. The "File to test field appears, in which the path to the WebOffice log file must be selected:

 

<WebOffice application>\WEB-INF\work\WebOffice.log

 

HostMonitor: Select the file and string to be tested

 

Then select a bad text that defines the string associated with a malfunction.

Possibilities for this are for example:

 

•ERROR

•NullPointerException

•ClassCastException

•StackOverflowError

•IndexOutOfBoundsException

•NoSuchElementException

•ConcurrentModificationException

•UnmarshalException

•IllegalArgumentException

•NOT_IMPLEMENTED

•The Layer IDs of the Service (Warning that layer IDs in a service are not sorted in ascending order)

•etc ...

 

Define Bad record

 

You can then change the test name and the alert method.

 

Define test name and notification method

 

Finished list with several strings to be monitored