Network ports

The following table lists the connection protocols and default ports that BMC Helix Data Manager components use to communicate with each other and the external databases and file systems to which they connect. All port numbers are configurable.

Component	Protocol	Port	Direction	Purpose
Workbench	HTTPS	8444	Inbound	Client browser access to the Workbench
Workbench	TCP/IP	5432	Outbound	Workbench connectivity to the Repository
Repository	TCP/IP	5432	Inbound	Incoming connections to the Repository
Engine	TCP/IP	5432	Outbound	Engine connectivity to the Repository
	TCP/IP	1433	Outbound	Engine connectivity to a MS SQL database (dependent on deployment)
	TCP/IP	1521	Outbound	Engine connectivity to an Oracle database (dependent on deployment)
	TCP/IP	5432	Outbound	Engine connectivity to a PostgreSQL database (dependent on deployment)
	TCP/IP	ARS port	Outbound	Engine connectivity to an AR System server via the BMC Helix ITSM API on the port defined for the AR System server (optional)

To deploy the Workbench using HTTPS, you must provide a certificate.

Tip

You can connect only one BMC Helix Data Manager Workbench to a single BMC Helix Data Manager Repository. But you can connect more than one BMC Helix Data Manager runtime instance to a single BMC Helix Data Manager Repository. This configuration allows a high degree of flexibility in the installation and configuration of BMC Helix Data Manager. For example, you might want to install the BMC Helix Data Manager Runtime with a local deployment for more than one MS SQL database server. For more information, see Deployment-scenarios.

The BMC Helix Data Manager Runtime must be configured with a connection to the BMC Helix Data Manager Repository prior to startup. After the initial connection, the BMC Helix Data Manager Runtime automatically registers itself and is available to run tasks.

Network ports

On this page