Platform Deployment Guide › Technical Information › Allocating UDP and TCP Ports › Example Communication Sequence

Example Communication Sequence

As an example, consider the sequence of communications when replicating captured data from a gateway or client to a CMS.

Note: Replication of policy data from a CMS to a gateway or client uses a symmetric method.

1. Gateway notifies CMS that data is available

   The gateway sends the CMS a CA DataMinder machine identification service UDP packet containing the number of items to replicate and other replication details. The relevant startup.properties setting on both the gateway and the CMS is default.pingports.

2. CMS prepares to pull data up from gateway

   The CMS opens a TCP socket to the gateway and sends and receives packets requesting replication service information from the RMI registry. The relevant startup.properties setting on the gateway is default.rmiports.

   Note: This socket can stay open for up to 15 seconds after the data transfer completes before closing, to save re-negotiating the connection if it is required within that time.

3. CMS pulls data from gateway

   The CMS opens a TCP socket to the gateway and reads captured data from the gateway. The relevant startup.properties setting on the gateway is default.serverports.

   Note: This socket can stay open for up to 15 seconds after the data transfer completes before closing to save re-negotiating the connection if it is required within that time.