2.6 Reviewing AppManager Port Usage

AppManager components communicate with each other through default ports. Check for port restrictions specific to your site or firewall protections that might prevent you from using certain ports.

The following table lists the default ports that AppManager uses.

Components Communicating

Ports Used

Protocols

Service/process using port

Connections to QDB:

Task Scheduler service to QDB

1433†

1433 is the default port. You can use any port.

TCP/IP

SQL

Management server to QDB

1433†

1433 is the default port. You can use any port.

ODBC

SQL

Control Center command queue service to QDB

1433†

1433 is the default port. You can use any port.

ODBC

TCP/IP

SQL

Operator Console to QDB

1433†

1433 is the default port. You can use any port.

ODBC

SQL

Connections to CCDB:

Control Center command queue service to CCDB

1433†

1433 is the default port. You can use any port.

TCP/IP

SQL

Control Center console to CCDB

1433†

1433 is the default port. You can use any port.

TCP/IP

SQL

Connections required for deployments:

Deployment Service to Windows agent computers for installation

135, 139‡

If 139 is not available and a firewall is not present, you can use port 445.

TCP/IP

 

Deployment Service to CCDB

Deployment Web Service to CCDB

Proxy Deployment Web Service to CCDB

1433†

1433 is the default port. You can use any port.

TCP/IP

SQL

Deployment Service to Deployment Web Service

80*

HTTP

Background Intelligent Transfer Service (BITS)

Deployment Service running in proxy mode to proxy Deployment Web Service

443*

HTTPS

BITS

Connections between management servers and agents:

Management server to Windows agents

9998

9998 is the default port. You can use any port.

TCP/IP

 

Windows agents to management server

9999

9999 is the default port. You can use any port, but ensure that you also update the port information on the management server. For more information, see the Administrator Guide for AppManager, available on the AppManager Documentation page.

TCP/IP

 

UNIX agents to management server

9001

9001 is the default port. You can use any port, but ensure that you also update the port information on the management server. For more information, see the Administrator Guide for AppManager, available on the AppManager Documentation page.

TCP/IP

 

Connections between UNIX Agent Manager and UNIX agents:

UNIX Agent Manager to UNIX agents

2620

2620 is the default port. You can use any port.

TCP/IP

 

UNIX Agent Manager console to UNIX Agent Manager

2222

2222 is the default port. You can use any port.

TCP/IP

 

Miscellaneous connections

Troubleshooter utility on Operator Console or Control Center console computer to agent

8996*

TCP/IP

 

* Indicates a bidirectional port requirement

† Indicates additional port requirements

If you use a named SQL Server instance, or if you are not using the default SQL Server port (1433), additional port requirements include:

  • The SQL Server browser port, UDP 1434. The SQL Server Browser service helps clients determine the associated SQL Server port to use. Once a client establishes a connection to the SQL Server running on the non-default port, it will not use the SQL Browser again unless the SQL Server port changes.

  • The SQL Server port for the instance that is hosting the QDB and CCDB.

  • If the SQL Server is clustered, include the physical address for each cluster node and the virtual IP address for each repository.

‡ Indicates that you need an additional port range. If you plan to remotely install agents and updates across a firewall, decide how many ports you want to allocate to DCOM processes on the agent computers.