Global Access Server: Audit Messages
The Global Access Server periodically sends status update messages. The GAS audit messages result in updates to the RemoteSession field, but they do not appear in the Audit Subsystem.
The RemoteAccess Subsystem is generic and used for all Remote Access Providers. When a session is created using one of the providers, the Remote Access Subsystem generates a ThingWorx audit message. Similarly, when a session is terminated (deleted), the RemoteAccess Subsystem generates an audit message. These audit messages fall into the RemoteAccess category of audit messages. For more information on viewing audit messages, refer to the topic, Searching Audit Data (Queries, Direct Persistence) in the ThingWorx Platform Help Center.
The eMessage Connector processes the following enumerations and then updates the associated RemoteSession fields:
SessionInfoType Enumeration (type)
SessionInfo Value
Associated RemoteSession 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 Why is a Remote Session Terminated?.
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 RemoteSession fields need to be updated, the UpdateSession service of the RemoteAccess Subsystem is called. This service persists any RemoteSession fields that have changed. If any fields changed, the Remote Access Subsystem fires the SessionUpdated event to the Thing associated with the remote session.
Was this helpful?