Agentry messages.log File

The messages.log file contains log items that are related to client-server messaging. Each message and response sent between SAP Mobile Platform Server and Agentry client is one log item. The information in each item includes the date and time of the message, the Agentry client’s IP address, the type of message or response, and other message information.

The messages log persists until one of the following occurs:

The messages.log file cannot be disabled.

Messages Log Format

The following is an excerpt from a typical messages.log file.
I,  9,  1, 10, 09/12/2013 17:11:18,   ,  0, 70,      , ANGEL: B0A6D984-C97B-4275-B7E4-AEB8FC9D5210
Q,  9,  1, 10, 09/12/2013 17:11:18,   ,  0, 70, user1, ANGEL: B0A6D984-C97B-4275-B7E4-AEB8FC9D5210
A,  9,  1, 10, 09/12/2013 17:11:18,   ,  0, 70, user1, ANGEL: B0A6D984-C97B-4275-B7E4-AEB8FC9D5210
S,  9,  1, 10, 09/12/2013 17:11:22, 22, 23, 70, user1, ANGEL: B0A6D984-C97B-4275-B7E4-AEB8FC9D5210
C,  9,  1, 10, 09/12/2013 17:11:22,   , 23, 70, user1, >unknown<
  • Message State: A single character indicating the state of the message in relation to SAP Mobile Platform Server.
  • Message Code: A numeric value that identifies the type of message. See Message Codes for more information.
  • Subsystem Code: Either 1 or 20. This is a deprecated value that varies only for older SAP products built on Agentry 2.0 code libraries.
  • Message Number: A number assigned by the Agentry client that increments for each message sent.
  • Date and Time: The date and time the message was received by the SAP Mobile Platform Server. This is always the date and time of the SAP Mobile Platform Server host system.
  • Response Code: A numeric code that indicates the response to the message. The message codes “S” and “R” each have a different set of possible response codes. For all other message codes, the response code column is blank.
  • Data Sent/Data Received: A running total of the amount of data sent and received by the SAP Mobile Platform Server per message, with a value in bytes.
  • User ID: ID of the user to which the message belongs. It is normal for the user ID to remain blank for messages with a message state of “I”.
  • Client Location: IP address of the client device. It is normal for the client location to be unknown for messages with a message state of “C”.
Message States—Synchronous Communication
State Name Description
I Incoming Message is being received from the client.
Q Queued Message is decoded, and placed in an SAP Mobile Platform Server work queue; the user is identified.
A Active A previously queued message is being processed by the SAP Mobile Platform Server.
S Sent Response SAP Mobile Platform Server sent information or an acknowledgement to the client.
R Received Response A client response has been received by SAP Mobile Platform Server.
C Complete Message processing is complete.
Push Message States—Asynchronous Communication
State Name Description
O Outgoing Message is being sent to the client.
T Trying SAP Mobile Platform Server is attempting to connect to a client
L Linked SAP Mobile Platform Server has successfully connected to a client.
W Waiting SAP Mobile Platform Server failed in an attempt to connect to a client. It will attempt the connection again.
R Received Response SAP Mobile Platform Server has received a client response.
S Sent Response SAP Mobile Platform Server sent information or an acknowledgement to the client.
C Complete Message processing is complete.
X Cancelled SAP Mobile Platform Server cancelled the message to the client.
F Failed Message failed. SAP Mobile Platform Server will not retry.
Message codes indicate the type of message being processed or sent, and are found in the Message Code column of the messages.log file.
Log Message Codes
Code Description
2 Client logout request
3 Client login request
7 Client user password change request
200 Transaction instance sent to SAP Mobile Platform Server from the client
201 Client has made a fetch processing request
202 Client system information message sent to SAP Mobile Platform Server
203 Client has requested an object be reloaded/refreshed
204 Client has requested the definition of an object
205 Client has requested the definition of a fetch
206 Client has requested the definition of a transaction
207 Client has requested the definition of a screen set
208 Client has requested the definition of an action
209 Client has requested the definition of a rule
210 Client has requested the definition of a report
211 SAP Mobile Platform Server has pushed an object or messages to the client
212 Client has sent an enable push message to SAP Mobile Platform Server for the user
213 Client has requested the definition of a style be sent
622 Client has requested that all complex tables be updated
623 Client has requested that all data tables be updated