Determining the Operation for a SOAP/JMS Request

Integration Server 10.15 | Web Services Developer’s Guide | How Integration Server Determines which Operation to Invoke | Determining the Operation for a SOAP/JMS Request

When Integration Server receives a web service request sent over SOAP/JMS, Integration Server uses the following process to identify the SOAP action and determine which operation (IS service) to invoke:

1. Integration Server retrieves the following JMS message properties from the JMS message:

This JMS Message property...	Indicates...
soapJMS:targetService	The fully qualified name of the provider web service descriptor that contains the operation and the name of the port in the WSDL document that contains the operation. In a WSDL document generated by Integration Server, each port name corresponds to a binder in the web service descriptor.
soapJMS:soapAction	The SOAP action value.

2. Integration Server determines which operation is associated with the SOAP action value contained in soapJMS:soapAction.

If the SOAP action value is unique within the selected binder, Integration Server invokes the service that corresponds to the operation with the assigned SOAP action value.

If the SOAP action value is not unique (more than one operation in a binder share the same SOAP action value), Integration Server cannot use the SOAP action to determine the operation to invoke. Instead, Integration Server determines the operation to invoke by examining the fully qualified name (namespace name and local name) of the first element in the SOAP body. For more information about how Integration Server resolves duplicate SOAP action values, see Duplicate SOAP Action.