Network ports

To plan your network topology and firewall rules, you must know which TCP/IP ports are used by the software components.

In general, port numbers are configured in either Library Manager or the Agent registration.xml files. Processes must always be restarted after you make any changes. Always check with the relevant system administrators about which port numbers are being used for external systems such as the project database and license server.

Project database

Several of the components communicate with the project database through JDBC. The port number that is used for this communication depends on the database vendor and configured connection string. Some defaults are listed.
  • IBM® Db2®: 50000
  • Microsoft™ SQL Server: 1433
  • MySQL: 3306
  • Oracle: 1521

HCL OneTest™ API

Outgoing connections are listed.
  • Floating License Server: typically 27000 and 2 more ports. For more information about license keys, see this Technote.
  • Project database
  • Proxy Agent (if you record your own messages)
  • HCL OneTest™ API Agent:

    testing and probes - see HCL OneTest™ API Incoming.

    7824 (by using JDBC stub with an integrated simulation database).

  • HCL Quality Server: 5443 default for HTTPS, 7819 default for HTTP, 7883 default for the Topology Discovery view
  • Messaging transports
  • JDBC database connections
  • Email server for publishing reports
  • Change management systems
  • Source control systems
  • Test management systems, for example IBM® Rational® Quality Manager
Incoming connections are listed.
  • Software AG webMethods recording and stubbing.
    A random port number is used and the HCL OneTest™ API host name is sent for connections coming back. These connections can be overridden in Library Manager with: 
    WMIS Server Port
WMIS Server Bind Address
  • Testing
    By default this port is a random port that is selected at start-up. It might be fixed to a given port (for example, 8989) with the following JVM argument added to Library Manager: 
    -Dgreenhat.http.port=8989
    HCL OneTest™ API passes its host name to the remote system for connections to be made back. It is possible to override this value by setting the following in Library Manager: 
    HTTP Bind Address

    An example is to use the fully qualified host name, or an IP address where your computer has multiple network interfaces.

  • Recording

    Recording Studio incoming messages.

    By default this port is a random port number. It can be changed in Library Manager by setting the value of Recording Port.

  • CICS® Stubs
    A random port number is used and the HCL OneTest™ API host name is sent for connections coming back. These connections can be overridden in Library Manager with: 
    CICS Stub ServerPort
CICS Stub Server Bind Address

HCL OneTest™ API Agent (Virtualization and Performance Tests)

Incoming connections are listed.
  • Command interface: 4476

    Override this port by running with the -p <port> switch.

    For example: Agent -p 4475

  • TestEngine: default random port

    Override this port by editing Agent.config TestEngines section.

    For example: 
    <arg value="-httpPort"/>
<arg value="4477"/>
  • Probe: default random port

    Override this port by running with the -probePort <port> switch.

    For example: 
    Agent -probePort 4478
  • JDBC stubbing (integrated simulation database): 7842

    Override this port by setting IDB Client Port in Library Manager.

  • JMX interface: 8765
    Override this port by configuring Agent.config as shown: 
    <rtcp enabled="true">
<jmxPort value="8787"/>
Outgoing connections are listed.
  • HCL OneTest™ API during testing
  • Project database (Test Engine and Probe processes)
  • HCL Quality Server: 5443 default for HTTPS, 7819 default for HTTP
  • Rational® Quality Manager server: 9443
  • Messaging transports and Probe connections

    There is also internal communication between the Agent and the Test Engine and Probe programs by using random port numbers.

HTTP/TCP Proxy Agent

Incoming connections are listed.
  • HTTP and HTTPS listener: 3128 (Default)

TCP based forwarding rules as configured by user.

Outgoing connections are listed.
  • HCL Quality Server: 5443 default for HTTPS, 7819 default for HTTP
  • HCL OneTest™ API: Recording port
  • HTTP/TCP destinations and forward proxy

JDBC Proxy Agent

This program is a driver that is added to an existing program such as an application server. This program makes these additional connections.

Outgoing connections are listed.
  • HCL Quality Server: 5443 default for HTTPS, 7819 default for HTTP
  • HCL OneTest™ API: Recording port

Java™ Virtualization Agent

This program is a driver that is added to an existing Java™ program to enable the virtualization of Java™ method calls. This program makes these additional connections.

Outgoing connections are listed.
  • HCL Quality Server: 5443 default for HTTPS, 7819 default for HTTP
  • HCL OneTest™ API: Recording port

HCL Quality Server

Incoming connections are listed.
  • General HTTPS requests: 5443 default for HTTPS, 7819 default for HTTP

    User access and Agent communication.

    This port number replaces the previous general HTTP requests on port 7819.

  • Internal Communications Port: 7883

    This port is configured in Installation Manager and used in the Topology Discovery.

  • KariosDB web server stub usage: 7828
Outgoing connections are listed.
  • Project database
  • LDAP authentication server