Partner System Networking

Overview

This section describes, in some detail, the network ports and computer-to-computer network interactions involved in various parts of the Partner System. For a quick checklist of the firewall port configurations needed, please read Checklist: Firewall Configuration.

From a system administrator’s perspective, it is critical to know which ports are valid and need to be accessible between machines. Quite often, network security policies dictate that all ports should be blocked unless they are needed. Therefore, you will need to know the ports used by Partner so that you can make appropriate exceptions in firewalls and other security components.

Ports and Protocols Used By Partner

Here is a full list of all ports and protocols used by standard Partner infrastructure and applications. Not all ports are used by any particular application or installation, so consult the remaining sections to see the contexts in which they are used.

These are the TCP ports that the Partner currently utilizes:

Port Name Description Protocol
80 Partner web Partner Web Standard http http/html
443 HTTPS Secure HTTP http/html
3306 Hub MariaDB MariaDB or MySQL RDBMS deployed on a hub install mysql
8000 Staker Job Library Staker job library access via binary Java serialization
8002 Barsoom Job library access via XML exchange http/xml
8004 Yonder Yonder remote filesystem yonder
8005 Hub Web Service Standard SOAP or similar web services on the hub http/xml
8006 MapApp Web Service Standard SOAP or similar web services on the client http/xml
8012 Client MariaDB MariaDB or MySQL RDBMS deployed on a client install mysql
8015 MacLeod Web Service Web Service used for Haversack and other communications http/xml/json

Note that of these, the following are industry standard defaults:

  • HTTP port 80
  • HTTPS port 443
  • MariaDB/MySQL port 3306

Partner Update

Partner Update is responsible for distributing all changes to software, configuration, and maps to all servers and clients in the Partner System.

In a standard installation, HTTP port 80 is used for all computer-to-computer communications.

../_images/NetworkModel-Update.png

Published Map Distribution

Maps are published with the Map Publisher, and then pushed to the Central Hub and the iOS update servers for distribution to the Partner on Java and Partner on iOS clients.

../_images/NetworkModel-Maps.png ../_images/NetworkModel-iOS.png

Field Designer

The Field Designer (also known as the Staker) has the most complex network requirements of any Partner system. It must communicate with its clients in complex ways, and must also communicate with a number of third-party servers.

../_images/NetworkModel-StakingHub.png

Haversack

Haversack is the underlying infrastructure for Partner’s newer field tools, including:

  • Distribution Inspection,
  • Damage Assessment,
  • Right-of-Way, and
  • Mobile Outage.

There are two generations of this infrastructure. The “v4” generation is still in current use with Distribution Inspection, Damage Assessment, and Right-of-Way. The “v5” generation is currently only used for Mobile Outage. The big distinction between these two is that v4 uses a MariaDB database connection for synchronization, while v5 uses an HTTPS web service.

../_images/NetworkModel-Haversackv4.png ../_images/NetworkModel-Haversackv5.png

Table Of Contents

Previous topic

Checklist: Moving a Partner Hub

Next topic

Tuning Parameters

This Page