Global Access Server: Audit Messages
The Axeda and ThingWorx Global Access Servers periodically send status update messages. The GAS audit messages result in updates to the RemoteSession field, but they do not appear in the Audit Subsystem for Axeda GAS v.6.9.2 through 6.9.x or ThingWorx GAS v.7.0.0 and v.7.0.1. The ThingWorx GAS v.7.1.0 supports sending its status updates messages and the eMessagee Connector supports writing these messages to the Audit Subsystem of the ThingWorx Platform. If you require audit messages for GAS, upgrade to ThingWorx GAS v.7.1.0 and to Axeda Compatibility Package (ACP) v.2.2.0.
When you import the Remote Access Extension, the Remote Access Subsystem is created.. When a session is created using an instance of the ThingWorx GAS v.7.1.0, the Remote Access Subsystem generates a ThingWorx audit message. Similarly, when a session is terminated (deleted), this subsystem generates an audit message. These audit messages fall into the RemoteAccess category of audit messages. For information on viewing audit messages, refer to the topic, Searching Audit Data (Queries, Direct Persistence) in the ThingWorx Platform Help Center. For complete details about the Audit Subsystem, refer to the subsection, Audit Subsystem in the ThingWorx Platform 9 help center.
The eMessage Connector processes the following SessionInfoType enumerations and then updates the associated RemoteSession fields:
SessionInfoType Enumeration (type)
SessionInfo Value
Associated Remote Session Fields Updated
DEVICE_IP (9)
agent IP
RemoteSession.agentIP
USER_IP (15)
user IP
RemoteSession.userIP
REMOTE_END (17)
Time that the remote session ended (in milliseconds since 1970)
RemoteSession.endTime
DATA_TRANSFERRED (19)
The number of bytes transferred during the remote session.
Remotesession.bytesTransferred
TERMINATION_CAUSE (23)
The integer that specifies the cause of the session ending. In addition, refer to .
RemoteSession.status, set to TERMINATED.
RemoteSession.terminationCause, set to the cause String mapped to termination cause integer
RemoteSession.lastActivityTime , set to the time that the SessionInfo element is received
When any Remote Session fields need to be updated, the UpdateSession service of the Remote Access Subsystem is called. This service persists any Remote Session fields that have changed. When fields change, the Remote Access Subsystem fires the SessionUpdated event to the Thing associated with the remote session.
* 
The RemoteSession.lastActivityTime property of a Thing is updated with each GAS status update and with status updates from the Remote Access Client (RAC). Any update from either GAS or RAC will result in the Remotesession.lastActivityTime property being updated and the session will not time out. "Inactivity" to the ThingWorx Platform means only that the platform has not received a status update from either RAC or GAS. Inactivity does not mean that there are no bytes being transferred.
Was this helpful?