Purpose
The purpose of this document is to provide detailed explanation on the Agentry Message Log and how it can be interpreted during analysis.
Overview
Explanation on how the Agentry Messages Log can be interpreted and analysed.
Introduction
· All communication between the Agentry Server and the Agentry Clients is 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 and 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 stage of each message per user.
· Each message has Message Code, Subsystem Code, and a Response Code. The Message Code is a numeric value which identifies the type of each Agentry message. The Subsystem Code is a numeric value that is 1 or 20 for Agentry messages, however other Syclo products may use different values.
· The Message Number is assigned by the client and is incremented for each message sent.
· The Response Code is a numeric value that indicates the response to the message. Each Message Code has a different set of possible Response Codes. Note that only the “S” and “R” message States have a Response Code, otherwise it is blank.
· Data Sent and Data Received is a running total of the bytes sent and received by the server per message.
· It is normal for the User ID to be blank for “I” messages and the Client Location to be >unknown< for “C” messages
Message States
Client to Server | ||
State | Name | Description |
I | Incoming
| message in the 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
|
A
| Accepted | server work queue has accepted the message and processing has begun |
S
| Sent Response
| server sent information and/or acknowledgment to the client
|
R
| Received Response
| client response received by server
|
C
| Complete
| message complete
|
Server to Client | ||
State | Name | Description |
O
| Outgoing
| message in the 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 acknowledgment to the client
|
C
| Complete
| message complete
|
X
| Canceled
| message canceled by server
|
F
| Failed
| message failed, will not retry
|
Message Codes
| Msg. Code | Resp Code | Name | Description |
| 8 | Public Key Request | Client request for servers public key | |
| 9 | Login Request | Client login to server | |
| 18 | Login Failure Response | ||
| 19 | Password Expired Response | ||
| 20 | Password Expired Warning Response | ||
| 21 | Password Warning No Change Response | ||
| 22 | Login Failure Account Blocked Response | ||
| 202 | Client System Info Notice | Client specific information sent to server such as client hardware, OS, screen size, etc. | |
| 21 | Incompatible Versions Response | ||
| 7 | Change Password Request | Client attempt to change password | |
| 18 | Change Password Account Blocked Response | ||
| 212 | Enable Push | Sent by client to enable push for this user on the server | |
| 2 | Logout Request | Client logout from server | |
| 623 | Data Table Update Request | Client request for all Agentry Data Table updates | |
| 67 | Data Table Update Response | ||
| 74 | Data Table Data Updated Response | ||
| 622 | Complex Table Update Request | Client request for all Agentry Complex Table updates | |
| 67 | Complex Table Update Response | ||
| 68 | Complex Table Definition Change Response | ||
| 70 | Complex Table Delete Records Response | ||
| 71 | Complex Table Transmit Index Response | ||
| 72 | Complex Table Index Update Response | ||
| 73 | Complex Table Reload State Response | ||
| 74 | Complex Table Data Updated Response | ||
| 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 | |
| 203 | Object Refresh | Client request for server to send an updated copy of an object | |
| 211 | Object Push | Server send of objects and/or messages sent to the client | |
| 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 | |
| 213 | Style Definition Request | Client request for an Agentry Style definition | |
| 214 | Image Definition Request | Client request for an Agentry Image definition | |
| 218 | Keep Alive Message | Message send either to or by the server when the client stays connected via push or background sending | |
| 215 | Client to client Connection | ||
| 216 | Client to client Data Transfer | ||
| 217 | Client to client Disconnect |
Response Codes
| Resp Code | Name |
| 0 | Acknowledgment |
| 1 | Unknown User |
| 2 | Could Not Decode |
| 3 | Exception Thrown |
| 16 | Success |
| 17 | Failure |
| 21 | Delete Business Object |
| 22 | Delete Business Object |
| 23 | Replace Business Object |
| 24 | Business Object Partial Update |
| 25 | Client App Version Info |
| 26 | App Update Info |
| 27 | System Time Info |
| 28 | Notify User |
| 29 | Cannot Accept |
| 30 | Get External Data |
| 31 | Get External Data Chunk |
| 32 | External Data Chunk |
| 33 | Transaction Failure |
Cluster Message and Response Codes
| Msg Code | Resp Code | Name |
| 200 | Cluster Join Request | |
| 201 | Cluster Join Accepted Response | |
| 202 | Cluster Join Rejected Response | |
| 203 | Cluster Join Ignored Response | |
| 210 | Cluster License Sync | |
| 211 | Cluster License Sync Response | |
| 220 | Cluster User Data Sync | |
| 221 | Cluster User Data Sync Response | |
| 230 | Cluster User Login Notice | |
| 240 | Cluster Data Update | |
| 250 | Cluster Key Value Update | |
| 260 | Cluster Leave Request |
Related Content
Related Documents
Syclo Resource Center Article ID: KB10538
Related SAP Notes/KBAs