Page tree
Skip to end of metadata
Go to start of metadata

The following table lists the default configurations of protocols and ports for different components and services used by various TrueSight Capacity Optimization components.

Default ports and protocols used by TrueSight Capacity Optimization

The following figure shows the default protocols and ports used by TrueSight Capacity Optimization components.


The following table lists the default ports and protocols used by the TrueSight Capacity Optimization components. This table aims to provide you with specific information, and can also help you resolve communication port conflicts and other issues.

TrueSight Capacity Optimization ports and protocols

Type of communication

Default Port

From

To

Protocol

Command line administration

 

22

CLI

TrueSight Capacity Optimization Application Server

SSH

22

CLI

(Remote) ETL Engine Server

SSH

Web access

8000/8443

Browser, remote ETL Engine Server, Integration Studio

TrueSight Capacity Optimization Application Server

HTTP/HTTPS

443/8043

BrowserTrueSight Presentation ServerHTTP/HTTPS

 

 

 

Access to Data Hub Web services

For internal communication to Data Hub: 8280 (Data Hub) and 8380 (Service Container), used by schedulers on Application Server, Local ETL Engine.

ETL Engine Servers

TrueSight Capacity Optimization Application Server
(Data Hub)

HTTP/HTTPS

For external communication to Data Hub following ports are used by Remote ETL Engine:

  • 8000: HTTP
  • 8443: HTTPS

(Remote) ETL Engine Servers

TrueSight Capacity Optimization Application Server
(Data Hub)

HTTP/HTTPS
Internal communication8080 (loopback interface only)TrueSight Capacity Optimization Application Server (Apache HTTPD Web Server)Same server - Web TomcatHTTP
8009 (loopback interface only)TrueSight Capacity Optimization Application Server (Apache HTTPD Web Server)Same server - Web TomcatAJP
8209 (loopback interface only)TrueSight Capacity Optimization Application Server (Apache HTTPD Web Server)Same server - Datahub TomcatAJP
8309 (loopback interface only)TrueSight Capacity Optimization Application Server (Apache HTTPD Web Server)Same server - ServiceContainer TomcatAJP
Shutdown port8005 (loopback interface only)TrueSight Capacity Optimization Application Server (Stop/Restart scripts)Same server - Web TomcatTCP
8205 (loopback interface only)TrueSight Capacity Optimization Application Server (Stop/Restart scripts)Same server - Datahub TomcatTCP
8305 (loopback interface only)TrueSight Capacity Optimization Application Server (Stop/Restart scripts)Same server - ServiceContainer TomcatTCP

DB access from TrueSight Capacity Optimization Application Server

  • 1521 for Oracle (configurable)
  • 5432 for PostgreSQL (configurable)

TrueSight Capacity Optimization Application Server (Gateway Server JSP engine, Data Hub, and scheduler)

Database Server

SQL*Net

DB access from ETL Engine Servers

  • 1521 for Oracle (configurable)
  • 5432 for PostgreSQL (configurable)

ETL Engine servers (scheduler)

Database Server

SQL*Net

Notification email

25 / 465
(configurable)

ETL Engine Server
(Scheduler)

SMTP gateway

SMTP/SSL

TrueSight Capacity Optimization Application Server
(Scheduler)

SMTP

Notification traps

162
(configurable)

ETL Engine Server
(Scheduler)

Trap receiver

SNMP

TrueSight Capacity Optimization Application Server
(Scheduler)

(Optional) User authentication via external LDAP service

389
(configurable)

TrueSight Capacity Optimization Application Server

LDAP service

LDAP/SSL

JDBC

  • 1521 for Oracle (configurable)
  • 5432 for PostgreSQL (configurable)

TrueSight Capacity Optimization Application Server

Database Server

JDBC

Access to data sources

Specific to each connector

(Remote) ETL Engine servers (connectors, Data Accum)

Data source

Specific for each connector

Generic Service Containers

Listen HTTP on TCP 8380

--TCP

 

Ports required for data collection using Proxy Agent in a firewall environment

If you are behind a firewall environment, and proxy data collection is enabled, the following ports need to be configured on your system:

  • Ports 111135139, and 445 from the proxy host to the agentless computer
  • Open RPC ports for DCOM from the proxy host to the agentless computer. You can allow a large range of ports as defined by the OS (range is 1024 - 65536) or you can limit the range by creating specific registry keys, and restarting the agentless computer.

Note

If you make the range of ports too small, you might run out of available ports.

Port requirement summary for Gateway Servers and Agents

Gateway Server for TrueSight Capacity Optimization integrates several components that analyze performance, display detailed graphs, report statistics, predict future performance, and enable capacity planning for your database. Gateway Server supports collecting, analyzing, and modeling business-oriented workloads with system data, and requires several TCP ports to be open in order for the Gateway Server and Perform Agents to communicate.

While there are many components of this product, the focus for purposes of configuring a firewall is the TrueSight Capacity Optimization Gateway ServerPerform Agent, and System Collectors. Some of the associated ports can be changed after the product is installed.

For more information, refer to the following sections:

Default port requirements for Gateway Servers and Agents

The following table summarizes the default port requirements for Gateway Server and Agent. Because these values might have been changed by you installing the software, you should verify that these port values are the ones used by the product.

Port number

Description

10128

The Gateway Server initiates a connection to port 10128 on the Perform Agent system for collection start, query and pull request. Port 10128 is also required for the UDR Collection Manager (UCM). If you are running data collections from the command line, port 10128 must be bidirectional.

10129This is the General Manager Server port. The Gateway Manager component of Application Server uses this port to communicate with the Gateway Server. The Gateway Server VIS parser ETL that runs on the ETL Engine uses this port to locate and transfer VIS files for processing. This port is also used by the GeneralManagerClient command line utility when accessing the Gateway Server.

6768

Perform Agent connects to the Gateway Server port 6768, for status and alert messages. Perform Agent must to be able to initiate a connection to Gateway Server port 6768 for collection status messages. Port 6768 can be used for the UDR Collection Manager (UCM).

6767

Port 6767 is used on the Gateway Server node for the Manager component to communicate with Perform Agent. The Gateway Server node initiates this connection, which is used to start Perform Agent.

30000 or below as necessary

Port 30000 is used for Investigate drill downs. This port is dynamically allocated on the Gateway Server node. The Gateway Server node determines a free port and passes this information along to the remote node. This port is necessary for graphs. On Microsoft Windows Gateway Servers, port 30000 is used for both chart and drill down requests.

This port is used only when Investigate is not configured in the firewall mode.

25

You must set the SMTP server name and SMTP user address in the Control Panel. You only need an SMTP server and address if you want mail.

Configuring Remote ETL Engine (EE)

You can configure Remote EE in one of the following ways:

  • Use the 8000/8443 ports, for both internal communication, and for populating data via the data API. This is the recommended approach. Apache web server acts as a proxy in this case.
  • Use the internal TCP ports 8280 or 8380, for both internal communication, and for populating data via the data API. Though this was the default setup when upgrading from previous TrueSight Capacity Optimization releases to TrueSight Capacity Optimization 10.0, it is recommended that you use the above approach.

Drill down and graph ports

Additional ports are used to activate drill downs within the Gateway Server, for instance, port 30000 is used by the Windows Gateway Server for drill downs and graphs. However, Investigate uses ports differently on UNIX and Microsoft Windows platforms:

  • On UNIX systems: If multiple drill downs or graphs are created, they still use only one port. However, if a port conflict is detected with either of these ports, the next lower port will be checked for availability until an unused port is found.
  • On Windows systems: One port is opened for each graph or drill down (starting at port 30000 for drill downs and graphs) for Investigate drill down requests and Investigate chart requests. The result is that the Windows Gateway Server requires many more ports to be opened through the firewall to support drill downs and graphs. For example, if you have 10 graphs opened, the Windows Gateway Server requires 10 different ports.

Note

If you are using firewall mode, these ports are not used by the remote computers to send data. However, the Gateway Server computer does bind to these ports.

When there is a firewall between the proxy host and the agentless computers, you can encounter issues because WMI uses the Distributed Component Object Model (DCOM) protocol and Remote Procedure Call (RPC) routines, both of which make use of random ports.

2 Comments

  1. Diagram and ports table doesn't show that port 10129 is required from Application Server to Gateway Server in order to start the GeneralManagerServer process.


    "If General Manager UI can't contact with General Manager Server on port 10129 on the remote Gateway Server, it will try to contact Service Daemon on port 10128. If the GeneralManagerServer process was not running the Service Daemon will restart the GeneralManagerServer process on the Gateway Server."


    Otherwise the GeneralManagerServer process must be started by command line:

    nohup $BEST1_HOME/bgs/bin/GeneralManagerServer 10129 &


    Refer to: https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA214000000d44BCAQ&type=Solution 

    1. Hello Peter,

      Thank you for the feedback. We have added this information in the Troubleshooting section for 10.7, 11.0, and 11.3 versions of TSCO. Here's the topic added in 10.7 version:

      The GeneralManagerServer process is not running

      Regards,

      Bipin Inamdar