| Panel |
|---|
On This Page: |
Finding the failure point
ServiceOptimizer log files may be cyclic. The size of the log file is determined by a database parameter. Once this size is reached, then the logging will start overwriting from near the top of the file (just under the initialization information). Therefore to find the latest logging may not be as simple as looking at the bottom of the file. Instead you will need to search for the timestamp that the log file was last written to. In this case you may see something like:
...
The following sections describe each of the commonly used interfaces and the details that are seen in the log file for each connection to the interface. At the correct level of tracing each interface will display the information that is passed through to SERVICEOptimizer and the response that SERVICEOptimizer gives back. In all cases it is important to get as much information as possible from the user about what action they were trying to perform, what time the problem occurred and what data they were sending (eg postcode/zipcode of job, job reference, engineer details, date).
Identifying the entry
Each API call can be identified in the APIAgent log file by a key word. This keyword can then be used in a search for all occurrences of that interface call. Because of the volumes of each call that can occur in a day it may be worth redirecting the search results to a file for further diagnosis. The following is the list of key words for the main interfaces
...
If you want to know the results of the API call then you will need to look in the API Agent log file at the lines following and you should be able to see +<Number>/n - the number will match the ServicePower API return code as described in Return Codes.
Database Issues
Find the last entry in the log file and search up for the following:
...