IBM Support

Ports needed for Web Services with App Connect Enterprise or IBM Integration Bus

Troubleshooting


Problem

You are using App Connect Enterprise (ACE) or IBM Integration Bus (IIB) and need to plan for HTTP and HTTPS traffic supporting either standard HTTP calls or SOAP HTTP messaging. You need to know how many ports will be used and how to configure which ports are in use.

Resolving The Problem

App Connect Enterprise components use several ports for different HTTP based functions.
By default, ACE components use these ports, if the corresponding function is enabled.

All of these port numbers are configurable.

Port# Usage
4414 This port will be used by the Integration Node web admin listener
7080 This port will be used by the biphttplistener process for plain HTTP traffic to all ExecutionGroups
7083 This port will be used by the biphttplistener for encrypted HTTP (HTTPS) traffic to all ExecutionGroups
7600 This port will be used by the REST Admin listener for an independent Integration Server
7800-7842 This range of ports will be assigned incrementally for plain HTTP traffic to each EG that has a SOAPInput node, in the order that each EG starts up
7843-7885 This range of ports will be assigned correspondingly to the plain HTTP traffic port for HTTPS traffic to each EG that has a SOAPInput node, in the order that each EG starts up

For example, suppose you have a single Integration Node with two Integration Servers, each with an HTTPInput node and a SOAPInput node. If both the HTTPListener and the SOAP HTTPConnector are configured to allow both plain and encrypted HTTP (http and https), then these ports will be used:

4414 - all traffic to the Integration Node
7080 - all unencrypted traffic to all HTTPInput nodes in both Integration Servers
7083 - all encrypted traffic to all HTTPInput nodes in both Integration Servers
7800 - all unencrypted traffic for SOAPInput nodes deployed to the first Integration Server that starts up
7801 - all unencrypted traffic for SOAPInput nodes deployed to the second Integration Server that starts up
7843 - all encrypted traffic for SOAPInput nodes deployed to the first Integration Server that starts up
7844 - all encrypted traffic for SOAPInput nodes deployed to the second Integration Server that starts up

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"ARM Category":[{"code":"a8m0z0000008ZykAAE","label":"ACE-\u003EConnectivity"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"ARM Category":[{"code":"a8m50000000CiCEAA0","label":"IIB-\u003EConnectivity"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
24 May 2022

UID

swg21420032