All communication between the Agentry Server and the Agentry Client are logged to a log file on the server named messages.log. A transmission from the Agentry Client to the Agentry Server is made up of many individual messages. Each message goes through several states as it is processed by the Agentry Server. A single line is written to the messages.log for each state of each message per user.
The log file is located in the directory where the Agentry Server was installed. If the Server was installed in the default directory, it can be found here for the Agentry Production Server:
C:\Agentry\ServerProd\Logs
/opt/syclo/Agentry-Server/Logs
The messages log is stored in the following location for the Agentry Development Server:
C:\Agentry\ServerDev\Logs
/opt/syclo/Agentry-Server/Logs
| Code | Description |
|---|---|
| 2 | Logout Request - Client logout from Server |
| 3 | Login Request - Client login from Server |
| 7 | Change Password Request - Client attempt to change password |
| 13 | Server error |
| 200 | Object Transaction - Client send of a single transaction to the Server |
| 201 | Object Fetch - Client request for a fetch to be run by the Server and the result objects to be sent to the Client |
| 202 | Client System Info Notice - Client-specific information sent to Server such as Client hardware, OS, screen size, etc. |
| 203 | Object Refresh - Client request for Server to send updated copy of an object |
| 204 | Object Definition Request - Client request for an Agentry object definition |
| 205 | Fetch Definition Request - Client request for an Agentry fetch definition |
| 206 | Transaction Definition Request - Client request for an Agentry transaction definition |
| 207 | Screen Set Definition Request - Client request for an Agentry screen set definition |
| 208 | Action Definition Request - Client request for an Agentry action definition |
| 209 | Rule Definition Request - Client request for an Agentry rule definition |
| 210 | Report Definition Request - Client request for an Agentry report definition |
| 211 | Object Push - Server send of objects and/or messages sent to the Client |
| 212 | Enable Push - Sent by Client to enable push for this user on the Server |
| 213 | Style Definition Request - Client request for an Agentry style definition |
| 622 | Complex Table Request - Client request for all Agentry complex table updates |
| 623 | Data Table Update Request - Client request for all Agentry data table updates. The formatting of <TEXT> following a <p> is not supported. Wrap the <TEXT> that follows in a <p>. |
| State | Name | Description |
|---|---|---|
| O | Outgoing | Message in process of being sent to Client |
| T | Trying | Attempting to connect to Client |
| L | Linked | Successfully connected to Client |
| W | Waiting | Failed attempt to connect to Client, will retry |
| R | Received Response | Client response received by Server |
| S | Sent Response | Server sent information and/or acknowledgement to the Client |
| C | Complete | Message complete |
| X | Cancelled | Message cancelled by Server |
| F | Failed | Message failed, will not retry. The formatting of <TEXT> following a <p> is not supported. Wrap the <TEXT> that follows in a <p>. |
| State | Name | Description |
|---|---|---|
| I | Incoming | Message in process of being received from Client |
| Q | Queued | Message has been decoded, user has been identified, and the message is placed in one of the Server’s work queues |
| S | Sent Response | Server sent information and/or acknowledgement to the Client |
| R | Received Response | Client response received by Server |
| C | Complete | Message complete. The formatting of <TEXT> following a <p> is not supported. Wrap the <TEXT> that follows in a <p>. |