Show Menu
TOPICS×

Network configuration

Communication between processes

Certain processes of the application need to communicate with others or to access the LAN and internet. This means that some TCP ports need to be open for these processes.
Use the embedded Apache Tomcat port as a priority (8080 by default) for internal communications between the various application servers of an Adobe Campaign platform.

Delivery server

For the delivery server ( nlserver mta ), the following ports must be open:
Ports Destination Comments
25/tcp (smtp) Anywhere SMTP traffic for e-mail broadcasting.
53/udp (domain) DNS servers DNS queries.
38000/tcp (default port) SMS gateway Used to send SMS traffic to the NetSize SMS router [option].
7777/udp Statistics server Accessing the statistics server.

Inbound mail

For the inbound mail recovery process ( nlserver inMail ), the following ports must be open:
Ports Destination Comments
110/tcp (pop3) Internal mail server POP3 traffic to pick up bounce messages.
25/tcp (smtp) Internal mail server SMTP traffic to send remaining bounce messages that are not automatically processed by the pre-defined rules.

Application server

For the application server ( nlserver web ), the following ports must be open:
Ports Destination Comments
80/tcp (http) 443/tcp (https) Anywhere HTTP or HTTPS traffic (including for the deliverability offer).
When several application servers of an Adobe Campaign platform need to communicate with each other, we recommend using the port of the Apache Tomcat server (by default: 8080) rather than that of the HTTP port of the Web server which redirection module integration was carried out with. This means the port needs to be open between these servers.

SMS delivery status

To track SMS deliveries ( nlserver sms ), the following port must be open:
Ports Destination Comments
38000/tcp (default port) SMS gateway Queries the delivery queue status managed by the NetSize SMS gateway [option].

Rich client

For the Adobe Campaign rich client ( nlclient ), the following ports must be open:
Ports Destination Comments
80/tcp (http)
443/tcp (https)
Application server SOAP traffic (HTTP).

Database access

All components that use the database must be able to connect to it. This is the case for most components, with the exception of the redirection server, which can work alone, and the thin Win32 client, which uses HTTP (or HTTPS) only to communicate with the application server.
The default ports are the following:
Database type Port (default) Destination
Oracle 1521/tcp Database server
PostgreSQL 5432/tcp
Microsoft SQL Server 1433/tcp
DB2 50000/tcp

External access

In addition, certain components must be accessible from the public internet so that e-mail campaigns executed directly from Adobe Campaign can be viewed. This means that some ports need to be open for components.

Redirection server

Listening port Location
80/tcp (http)
443/tcp (https)
Anywhere. Each click on a tracked link generates a HTTP request on the server.

External Web server

This server hosts Web forms, mirror pages, etc. The following ports need to be open:
Listening port Location
80/tcp (http)
443/tcp (https)
Anywhere. Necessary when Web forms are managed directly from the Adobe Campaign platform or when mirror pages are used.

Internal application server (Web)

Listening port Location
80/tcp (http)
443/tcp (https)
All computers executing the thin client or rich client.

Integration with Adobe Experience Manager

Integration between Adobe Campaign and Adobe Experience Manager requires opening several ports if the installation is "on-premise". For more information on configuring this integration, refer to the detailed documentation .
Listening port Description
80 AEM connection to Adobe Campaign
4502
4503
Adobe Campaign connection to AEM's "authoring" and "publishing" instances. The ports to open may be different from the default ports, depending on your AEM configuration.

Bandwidth

Another key parameter of the network configuration to take into account. It is almost always outbound and much in demand during e-mail broadcasts. Here are a few examples of configurations based on our experience:
  • 1 Mb/s for 10,000 emails per hour (average size of 30 Kb)
  • 8 to 10 Mb/s for 100,000 emails per hour (average size of 30 Kb)
If you have constraints in terms of bandwidth, it is possible to schedule campaigns to run during the night when demand is lower.