Port conflicts on the SOA Gateway only

This is a DeltaV workgroup that contains an SOA Gateway. It may or may not have a firewall protecting the SOA Gateway. 

Each web service attempts to activate on its default port, but if that port is already in use, the service activates on the first available port number between 49152 and 49999.

To troubleshoot and correct port conflicts:

  1. If the default port of any of the services is already in use the service does not start and you must set a new port for the service in the SOA Gateway Administration application. Use the Windows netstat command to find a port between 49152 and 49999 that is not being used.
  2. If a firewall is in place to protect the SOA Gateway, you must configure the firewall to allow communications on the ports that Recipe Exchange and Campaign Manager use.