New additional TCP port for AEB Engines operated on-premise

After you install the November 2020 service pack (official release planned for November 19, 2020), all AEB Engines will use a new additional TCP port.

This TCP port is used within a multi-node system for communication between the individual engine nodes, thereby improving operation. 

Do you operate an AEB Engine in a multi-node system in your own data center? Then action is required.

Before you install the November 2020 SP, please make sure that communication between the servers of the individual AEB Engine nodes is allowed via the new TCP port. If the connection between the individual engine nodes of a multi-node system is blocked, e.g. by a firewall, enable the new TCP port (e.g. by using a firewall exception).

Please note, without enabling the port the Windows service of the engine will be starting, but the engine will not work.   

• The new TCP port is calculated from the base port of the AEB Engine + 701. For example, if the base port of the AEB Engine is set to 8000, the new TCP port is 8701.
• You can find the base port of your engine under Administration > System > Settings > "Base address" in the "Ports" section (admin rights required).

You can determine whether you are using a multi-node system as follows:
If more than one instance is stored in the application under Administration > System > System information > Folder: Server instances, you have a multi-node system and must take action.

If you are not using a multi-node system, you do not need to take any action.