Protocol Mismatch Between Transport and Primary Port
A protocol mismatch between the transport for a binder in a provide web service descriptor and the primary port can occur in the following situations:
When creating a service first web service descriptor, you specify a transport, but do not specify a host, port, or endpoint alias and there is not a default provider endpoint alias for the transport protocol,
Integration Server uses the primary port as the port in the endpoint URL.
When creating a WSDL first provider web service descriptor and default provider endpoint alias is not specified for the protocol used by the binding in the WSDL document.
Integration Server uses the primary port as the port in the endpoint URL.
If the selected transport and the protocol of the primary port do not match, Designer displays the following warning when you save the provider web service descriptor:
Selected transport protocol does not match that of the primary port
on Integration Server.
For example, suppose that you specify a transport of HTTPS when creating the provider web service descriptor, but do not specify a host, port, or endpoint alias. Additionally, Integration Server does not identify a default web service provider endpoint alias for HTTPS. Furthermore, the primary port is an HTTP port. In this situation, Designer displays the above message.
You must resolve this mismatch before making a WSDL document for this provider web service descriptor available to web service consumers. Otherwise, the web service clients will not execute successfully.