5495   The unsecured TCP/IP port number on which the Admin Server listens for client requests (if allowed in Cognos Configuration).

5498   The secured TCP/IP port number on which all TM1 components communicate with the Cognos TM1 Admin Server using Transport Layer Security (TLS).

5895     Admin Server to REST API unsecured communication port number (tm1AdminHTTPPortNumber). Specifies the HTTP port number that is used by TM1 Admin Server to communicate with the TM1 REST API for unsecured communication (if allowed). The default value is 5895. This default value cannot be changed using IBM Cognos Configuration. For more information, see “Appendix 1: TM1 Admin Host” in the TM1 REST API documentation.

5898   Admin Server to REST API secured communication port number (tm1AdminHTTPSPortNumber). Specifies the HTTPS port number that is used by TM1 Admin Server to communicate with the TM1 REST API for secured (SSL) communication. The default value is 5898. This value cannot be changed using IBM Cognos Configuration.
For more information, see “Appendix 1: TM1 Admin Host” in the TM1 REST API documentation.

<portNumber> The port on which the TM1 server runs. This parameter is used to distinguish multiple TM1 servers running on the same computer. Valid port values fall between 5000 and 65535. The default value is 12345 (already used by Planning Sample). This parameter is to be set in the Tm1s.cfg server configuration file.

12345  Default portNumber for Planning Sample
12346  Default portNumber for SData
45557  Default portNumber for GO_New_Stores
12347  Default portNumber for PData
5333   Default portNumber for Proven_Techniques
44321  Default portNumber for GO_scorecards
50909  Default portNumber for 24Retail

<HTTPPortNumber> Port number on which the TM1 Server listens for incoming HTTP(S) requests. The IBM Planning Analytics TM1 Server services the REST API using this HTTP(S) channel. The server accepts either standard HTTP or SSL secured HTTPS connections depending on the UseSSL parameter: If UseSSL is set to T, switching the use of SSL on, then the server will accept only HTTPS connections, if UseSSL is set to F then the server will accept unsecured HTTP connections. If HTTPPortNumber is not defined in your tm1s.cfg file, then port number “5001” will be assigned automatically. This parameter is to be set in the Tm1s.cfg server configuration file.
12354  Default HTTPportNumber for Planning Sample
8010   Default HTTPportNumber for SData
5010   Default HTTPportNumber for GO_New_Stores
8011   Default HTTPportNumber for PData
5011   Default HTTPportNumber for Proven_Techniques
44312  Default HTTPportNumber for GO_scorecards
52670  Default HTTPportNumber for 24Retail

<ClientMessagePortNumber>  TM1 Client Message port number. This port number establishes a secondary port for client progress messages to use when a lengthy operation is waiting to be canceled. This parameter is to be set in the Tm1s.cfg server configuration file. The default value is blank. By default, this port number is automatically and dynamically assigned when the TM1 server starts. You do not have to set ClientMessagePortNumber to a specific number unless firewalls or other network issues require the listener port to be a well-known number.
CAUTION: If you choose to set a specific value for the ClientMessagePortNumber parameter, instead of having it dynamically assigned, be sure to assign unique port numbers for all the TM1 server and client message ports you are using. If you have two servers running on the same machine using the same port number, the message activity may cause a system conflict or hang.
17469  Default ClientMessagePortNumber for 24Retail

<LDAPPort>    Port that IBM TM1 Server uses to bind to an LDAP server. It is used if PasswordSource=LDAP in tm1s.cfg. The default LDAPPort is 389 (unsecured). Usually, in production, secured port 636 is used instead (LDAPS).

9510    Default port for both TM1 Application Server (depending on “IBM Cognos TM1” service) and IBM Planning Analytics Spreadsheet Services (the new TM1 Web that depends on “IBM Planning Analytics Spreadsheet Services” service). If both services are still needed on the same machine, then this default port has to be changed for one of them, and TM1 Application Web (pmpsvc) may have to be reconfigured to connect to TM1 Web. Follow this document to achieve this: “How to Configure TM1 Application Web to connect to TM1 Web since 2.0.9.2 ? (IBM Planning Analytics Spreadsheet Services)“

53      Docker daemon port.

80         Planning Analytics Workspace’s PAGatewayHTTPPort (to be defined in /config/paw.ps1). This is an HTTP port that is mapped to the host by pa-gateway. The default value is 80.

443     Planning Analytics Workspace’s PAGatewayHTTPSPort (to be defined in /config/paw.ps1). This is an HTTPS port that is mapped to the host by pa-gateway. The default value is 443.

9012     To use IBM Planning Analytics Administration on Planning Analytics Workspace Local, you install and configure the Planning Analytics Administration agent wherever you install IBM TM1 Server. The default port of the Planning Analytics Administration agent is 9012. This port cannot be easily changed because it is hardcoded in the docker image of the container that is accessing the Administration Agent.

8888     Default admintool port. By default, the Planning Analytics Workspace administration tool is accessible on http://127.0.0.1:8888.
In IBM Planning Analytics Workspace Local version 2.0.44 or later, if port 8888 is not free, you can configure Planning Analytics Workspace Local to access the Planning Analytics Workspace administration tool remotely on Windows Server. For more information, see “Access the Planning Analytics Workspace administration tool remotely on Windows Server“.
If you can’t run a browser on the localhost interface, you can configure Planning Analytics Workspace Local to access the Planning Analytics Workspace administration tool on another IP address. For more information, see “Access the Planning Analytics Workspace administration tool remotely on Linux“