AX Server ports
For the Analytics Exchange Service to start successfully on the AX Server server or AX Engine Node, you must ensure that the ports required by the TomEE application server are not being used by other services or applications.
Checking ports in use
From a command prompt, use the NETSTAT command to display in-use ports:
NETSTAT -a
If required ports are being used by another service, you must do one of the following:
- reconfigure the service to use a different port
- temporarily disable the service in Windows Services while you install AX Server
If necessary, you can modify some of the ports used by AX Server after the installation process is complete.
Note
If you are installing AX Server or AX Engine Node for the first time on a server, you should verify that the ports required by the TomEE application server are not in use before you run the installer.
Ports required by the AX Server
AX Server and AX Engine Node are installed with the default port settings used by the Analytics Exchange Service.
| Port | Component | Encryption | Description |
|---|---|---|---|
| 80 | Tomcat Connector HTTP | Non-SSL |
Port used for unencrypted HTTP communication with the server. This is a unidirectional port. It should be opened for outside communication on AX Server and AX Engine Node. |
| 443 | Tomcat Connector HTTPS | SSL |
Port used for encrypted HTTP (HTTPS) communication with the server. This is a bidirectional port. It must be opened on AX Server for communication with AX Client. If you are upgrading an earlier version of AX Server, the default port is 8443. |
| 5432 | PostgreSQL | Supported |
You can specify a different port that is not in use in the AX Server installer. Note If you are configuring a dual-server installation, you must ensure that the PostgreSQL and AX Server and AX Engine Node can communicate on this port. |
| 10000 | AX Connector | TwoFish 128 bit |
If this port is in use, you can specify a different port that is not in use in the AX Server installer. This service is used primarily to access AX Server tables that have been exported to ACL Analytics projects. It must be opened on AX Server for inbound communication. |
| 4201 | AX Engine Node | Non-SSL | Used to connect AX Engine Node to the master AX Server. If the AX Engine Node and AX Server are communicating across a firewall, you must open this port. |
| 1521 | Oracle database | Non-SSL |
Port used for unencrypted Oracle database communication. It must be opened on AX Server and AX Engine Node for communication with the Oracle database. Note Your IT team will stipulate which port is required when Oracle is used as the AX Server database server. The port can be changed after the installation is completed, if necessary. |
| 5432 | Oracle database | SSL |
Port used for encrypted Oracle database communication. It must be opened on AX Server and AX Engine Node for communication with the Oracle database if you are encrypting the connection. Note Your IT team will stipulate which port is required when Oracle is used as the AX Server database server. The port can be changed after the installation is completed, if necessary. |
| 1543 | ACL Connector for Analytics Exchange | SSL |
Port used for establishing an ODBC connection to analytic results. This port is only required if you install the optional ACL Connector for Analytics Exchange service. It must be opened for inbound communication on AX Server. |
Firewall configuration
To connect to AX Server from outside your network firewall, you must allow inbound connections on the following ports:
| Port | Component | Description |
|---|---|---|
|
443 |
Tomcat Connector HTTPS |
Used to enable HTTPS connections to the web server for the AX Web Client and AX Server Configuration web applications, and for secure file transfers to and from AX Server. This port is also required for using aclscript.exe to communicate with ACL GRC modules such as Results or Projects. Note The default value for servers upgraded from versions prior to 5.0.0 is 8443. |
| 10000 | AX Connector | Used to enable access to AX Server tables from client computers through ACL Analytics. |
| 4201 | AX Engine Node | Used to connect AX Engine Node to the master AX Server. If the AX Engine Node and AX Server are communicating across a firewall, you must open this port. |
Each client computer that connects to AX Server must also have the corresponding ports open for outbound communication.
Connecting to ACL GRC
If you intend to transfer data between AX Server and any ACL GRC modules such as Results or Projects, you must allow the following connection:
- Executable aclscript.exe
- Port 443
- Whitelisted domain *.highbond.com