Difference between revisions of "Server Ports"

From PresenceWiki
Jump to: navigation, search
(Database Server)
Line 78: Line 78:
Main Database Socket Port: 9092
Main Database Socket Port: 9092
Log Action Request Port: 4444
Log Action Request Port: 4444
Log Message Receipt: 4445
Log Message Receipt: 4445

Revision as of 11:04, 4 January 2010

Fixed Server Ports

The Presence Server process (presenceserver.exe) runs a number of TCP/IP socket services for internal communication. The services, and the ports that they listen on, are listed below.

Please note that MOST of the ports used by Presence are configurable by editing the presenceconfig.xml document.

Encryption Server

Default Port: 8217

This is used when Presence servers must negotiate an encryption key in order to store private data (such as Filter comparison data).

Administration Client Listener

Default Port: 8215

This is a generic port reserved for communications between the Administration Client and the Presence Server.

On Demand Server

Default Port: 8222

This service listens for On Demand Task requests (via On Demand Clients) and processes them. Note that prior to Presence 3.3, all On Demand requests were routed via the Primary Presence Server on port 8221, then passed to an appropriate slave server on port 8222. Since the new architecture no longer makes use of a dedicated primary server, requests are now sent directly to the appropriate work server.

Web Service Server

Default Port: 8241

The Web Service Server listens for remote Web Service Requests - Tasks which are deployed as a Web Service.

Heartbeat Status Reporting Service

Default Port: 8230

This service is responsible for reporting the status of the Presence Server to the Heartbeat Server.

Channel Subscription Service

Default Port: 8081

This is a built-in Web Application that allows users to subscribe and unsubscribe from Message Channels.

Dynamically Allocated Ports

The following TCP/IP ports are initially assigned dynamically, which means that they will use any available free port. When a port is assigned, it is written to the presenceconfig.xml file for re-use on future start-ups. This allows the Presence administrator to specify the port numbers if required.

Entries in presenceconfig.xml are listed in the following form:

<socket key="XXXX" port="XXXX" />

Where "key" represents the class name of the Presence object that creates the port. This is identified in the items below:

Debug Engine

Key: com.internationalpresence.server.debug.DebugEngine

The Debug Engine handles communications between the Presence Server and the Administration Client when the Client is running a Task in Debug Mode.

Remote Call Task Listener

Key: com.internationalpresence.server.remotecall.RemoteTaskCallListener$DelegatedListener

Queued Process Change listener

Key: com.internationalpresence.v33.server.queue.QueuedProcessChangeListener

Task Invalidator

Key: com.internationalpresence.admin.TaskInvalidator

Task Completion Listener

Key: com.internationalpresence.v33.server.queue.QueuedProcessTaskCompletionListener

Database Server

Presence uses Pointbase (TM) database for internal data storage. This runs as part of a separate process (dbserv.exe), which is also responsible for collating log messages from clients and servers, and utilizes the following TCP/IP ports:

Main Database Socket Port: 9092

Log Action Request Port: 4444

Log Message Receipt: 4445

The first port (9092) is not configurable. The Log Action Request Port and Log Message Receipt Port can be configured by edited presenceconfig.xml (under they "syslogging" XML element).


The following table is a summary of default port numbers used by Presence processes.

Process Name Socket Description Default Port Configurable?
presenceserver.exe Encryption Server 8217 Y
Admin Client Listener 8215 Y
On Demand Server 8222 Y
Web Service Server 8241 Y