Configure a custom TCP port

AVEVA Historian uses default TCP port 32565 for communication.

• The "receiving" Historian (for example, the Historian server for data collection or the tier-2 server for replication) needs to allow inbound connections on the configured port.

• No inbound connections need to be allowed into the "sending" application for this communications channel, but it may be needed by other components (for example, if the "sending" node is also receiving SuiteLink data, SuiteLink requires port 5413 to be opened).

• These requirements apply to the Windows Firewall and any hardware firewall sitting between the systems.

You can configure a custom port for data historization from AVEVA Application Server and for replication.

WARNING! If the Historian is running and receiving data, clients using the port, such as AppEngines or replication, will be disconnected and go into store-and-forward mode. Make sure all clients have store-and-forward configured or data loss will occur.

To configure a custom port for Application Server:

1. Change the ReplicationTcpPort system parameter on the Historian. Do the following:

   1. Start the Operations Control Management Console (OCMC).

   2. Make sure that the Historian is not shut down and disabled. If it is, right-click Management Console, point to All Tasks, and then click Enable (allow to run) Historian.

   3. Change the ReplicationTcpPort system parameter default value to the custom port number. For more information on editing system parameters, see Edit system parameters.

      A message appears stating that you must manually update the firewall settings.

   4. Commit the configuration change. For more information on committing changes, see Commit configuration changes.

      The configuration service detects the change and restarts the Historian Client Access Point (HCAP) to allow it to use the custom port.

   5. To confirm the change, open the ArchestrA Logger to see a message from aahClientAccessPoint such as "Client access point (Opening Historian listening port nnnnnn)…" where nnnnnn is the custom port number you just configured.

2. Update the firewall settings on the Historian computer and update router/switch settings to allow communication through the custom port.

3. Change the TCP port on the Application Server. Do the following:

   1. Undeploy the Galaxy.

   2. Open the object editor for either the WinPlatform or the AppEngine.

   3. In the History area of the configuration options, expand Advanced settings and change the TCP port option value to the custom port number.

   4. Save the configuration.

   5. Repeat steps b through d for all AppEngines.

   6. Redeploy the Galaxy.

   Application Server now sends data to the Historian through the custom port.

To configure a custom port for replication:

4. Change the ReplicationTcpPort system parameter to the custom port value on the tier-2 Historian.

5. Update the firewall settings on the tier-2 Historian computer and update router/switch settings to allow communication through the custom port.

6. Change the replication server TCP port setting to the custom port value on the tier-1 Historian. For more information on editing replication server properties, see Edit replication server properties.

7. Commit the configuration change. For more information on committing changes, see Commit configuration changes.

The tier-1 Historian now replicates data to the tier-2 Historian through the custom port.