Specifications

Level One: Protege GX Installer Study Guide | August 2013 189
Stopping the Event Service
The Event Service can be stopped without adversely affecting the system. Stopping this service will prevent the
server from receiving all messages from controllers.
If your site has operators actively monitoring the system, then they should be advised prior to stopping the
service, as they will not receive any events, alarms or status updates while the service is offline.
Stopping the Event Service has no impact on the monitoring station reporting services already running on the
controller, such as Contact ID or ArmorIP. These will continue to report offsite as long as their phone line or
network connection remains intact.
While the Event Service is offline, controllers will store events locally. When the service comes back online, the
events are transmitted along with the time they actually occurred (field time). As GX Controllers can store a
minimum of 2000 events onboard, the Event Service can be offline for a reasonably long time before any events
are lost.
The Event Service uses a default incoming port of 22000.
Protege GX Client Communication
The GX Client communicates with the Data Service using the Windows Communication Foundation (WCF)
default TCP port of 808 or HTTP port of 8000.
This can be set at the time of installation, but should only be changed if there is another program already
installed on the Server which is also utilizing WCF communications on the default port.
Data
Service
GX Client(s)
TCP 808
HTTP 8000