Port conflicts on the SOA Gateway and Secure SOA Server

This is a DeltaV domain that contains an SOA Gateway connected to another domain that contains a Secure SOA Server. There may or may not be 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:

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 in the SOA Gateway Administration application. Use the Windows netstat command to find a port between 49152 and 49999 that is not being used.
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, Campaign Manager, and the Monitor Host web service use.
Set up the Secure SOA Server making sure the Monitor service activates.
If your system has a firewall protecting the SOA Gateway, make sure the port you use for the Monitor service is open on the firewall.
Once the Monitor service is running on both the SOA Gateway and Secure SOA Server, check the Campaign Manager and Recipe Exchange web services. Each service should be using the same port on the SOA Gateway and the Secure SOA Server. If they are different, use the Windows netstat command to find a common available port between 49152 and 49999 for each service.
If a firewall is in place to protect the SOA Gateway, verify that the firewall allows communications on the ports that Recipe Exchange, Campaign Manager, and Monitor Host web services use.