Integration Server 10.15 | Web Services Developer’s Guide | How Integration Server Determines which Operation to Invoke | Fallback Mechanisms for Determining the Operation | Port Name Is Not Specified
 
Port Name Is Not Specified
If the endpoint URL does not specify a port name (for messages sent over HTTP/S) or the port name is missing from the soapJMS:targetService property (for messages sent via SOAP/JMS), Integration Server attempts to determine the operation by first identifying the SOAP version. Integration Server also obtains the SOAP action value from the SOAP message. Integration Server then looks in the web service descriptor for a binder that uses the specified SOAP version and contains an operation with the specified SOAP action value. Integration Server invokes the IS service that corresponds to this operation.
If Integration Server cannot find an operation with that SOAP action value or there are multiple operations with that SOAP action value, Integration Server compares the fully qualified name of the first element in the SOAP body to the expected first element for an operation. For operations with a Document style, the expected first element is the first part element declared for the operation’s input message in the WSDL document. For operations with an RPC style, the expected first element will have the same name as the operation in the WSDL document. Integration Server then invokes the IS service that corresponds to this operation.
If, after searching for the fully qualified name of the first element in the SOAP body, Integration Server cannot determine which operation to invoke, Integration Server returns a SOAP fault to the web service client.