If any of the default ports that the SOA web services use are already in use, the following information explains how to troubleshoot and correct the conflicts. The way to find and correct port conflicts is different depending on whether your system has only an SOA Gateway or both an SOA Gateway and a Secure SOA Server.
The default port numbers for the services are shown in the following table.
Service |
HttpPort |
NetTcpPort |
|---|---|---|
Monitor |
NA(1) |
49301 |
Campaign Manager |
49202 |
49203 |
Recipe Exchange |
49200 |
49201 |
Mynah Integration |
NA(1) |
49205 |
The following table summarizes the locations where you should verify the service's port numbers. The port number for each service must be the same on each computer (and firewall, if installed) where the port is active. If you need to change a port (for example, if another application is already using one of the default ports) select an unused port in the range 49152 to 49999.
Web Service |
Verify Port Numbers on... |
|||
|---|---|---|---|---|
ProfessionalPLUS |
SOA Gateway |
Secure SOA Server |
Firewall |
|
Monitor |
Yes(1) |
Yes |
Yes |
Yes |
Campaign Manager |
No |
Yes |
Yes |
Yes |
Recipe Exchange |
No |
Yes |
Yes |
Yes |
Mynah Integration |
Yes(1) |
No |
No |
No |
If any of the default ports that the SOA web services use are already in use, the following information explains how to troubleshoot and correct the conflicts. The way to find and correct port conflicts is different depending on whether your system has only an SOA Gateway or both an SOA Gateway and a Secure SOA Server. If a service does not activate, check the Windows Event Viewer for the reason.
The following sections are generalized instructions for verifying and adjusting the port number for the web services. The examples in the instructions use NetTcpPort numbers. If you are using HttpPort binding, adjust the port numbers in the instructions as required.