User guide

Sender event logging on Windows 158
New in RGS 5.1.5 is reporting of the IP address and port number of the Local Computer whenever the Local
Computer either establishes a connection to the Sender or disconnects from the Sender. In Figure 9-3, a
connection has been established to the Sender from a Local Computer with IP address 15.2.76.60 and port
number 3279.
Figure 9-3 Reporting of the Local Computer IP address when a connection is made to the Sender
9-2 Usages of the HPRemote log
The HPRemote log has several important usages:
• Troubleshooting—The HPRemote log can be used to aid troubleshooting of connection issues between the
RGS Sender and Receiver. If you’re unable to view the HPRemote log because of RGS connection difficulties,
Microsoft Remote Desktop can be used to connect to the Remote Computer to view the HPRemote log.
• Automatic Remote Application Termination—Network outages or loss of connectivity between a Remote and
Local Computer can leave a remote desktop session running without supervision. To prevent applications
from running unattended, a customer-designed agent can use the HPRemote log to monitor the status of
connections to determine if application termination is required. If so, the agent would be designed to take
the appropriate action to terminate the application.
Chapter 10, “Remote Application Termination
,” describes how to create an agent that uses the HPRemote
log to automatically monitor the connection between the Remote and Local Computers—and then take
whatever action you require. Sample code is provided to facilitate creation of the agent.
• Other automated actions—The basic principle behind using the HPRemote log to perform automatic Remote
Application Termination can be used to create an agent to automatically monitor and process any of the
events logged by the RGS Sender. Chapter 10 lists the events logged by the RGS Sender, and describes
their format. Using the sample code provided, you can create an agent to automatically monitor and process
any Sender events.