You can add a binder definition to a service first provider web service descriptor.You can add a binder definition to a service first provider web service descriptor.All existing operations will be duplicated within the new binder.For a web service descriptor that runs in pre-8.2 compatibility mode (Pre-8.2 compatibility mode property is set to true), the new binder must specify the same “use” as the binder that already exists in the provider WSD. For more information about mixed use in binders, see Binders and Mixed Use.For a web service descriptor that does not run in pre-8.2 compatibility mode (Pre-8.2 compatibility mode property is set to false), the new binder must specify the same “style” and “use” as the binder that already exists in the provider WSD. For more information about mixed styles in binders, see Binders and Mixed Style.You can add a binder that specifies the JMS transport only if a valid provider web service endpoint alias exists for the JMS transport. For example, if the only web service endpoint alias that exists for JMS specifies a SOAP-JMS trigger that no longer exists, Integration Server does not consider the endpoint alias to be valid. Consequently, the endpoint alias cannot be assigned to a JMS binder. For more information about creating a web service endpoint alias, see webMethods Integration Server Administrator’s GuideYou can only add a JMS binder to a web service descriptor that does not run in pre-8.2 compatibility mode (Pre-8.2 compatibility mode property is set to false).In a JMS binder for a provider web service descriptor, the property values under JMS Settings and JMS Message Details are set by the web service endpoint alias assigned to the binder. The JMS Settings and JMS Message Details properties are read-only.If the WS-I compliance property is set to True, you can only create binders that comply with the WS-I profile.
on the web service descriptor toolbar or right-click and select Add Binder.In this field... | Specify... | ||
SOAP Version | Whether SOAP messages for this web service should use SOAP 1.1 or SOAP 1.2 message format. | ||
Transport | The transport protocol used to access the web service. Select one of the following: HTTPHTTPSJMS | ||
Use and Style for Operations | The style/use for operations in the provider WSD. Select one of the following: Document - LiteralRPC - LiteralRPC - Encoded | ||
Endpoint | The address at which the web service can be invoked. Do one of the following: To use a provider web service endpoint alias to specify the address, select the Alias option. Then, in the Alias list, select the provider web service endpoint alias.To specify a host and port as the address, select the Host option. Then, in the Host field specify the host name for the Integration Server on which the web service resides. In the Port field, specify an active HTTP or HTTPS listener port defined on the Integration Server specified in the Host field.
| ||
Directive | The SOAP processor used to process the SOAP messages received by the operation in the provider WSD. The Directive list displays all of the SOAP processors registered on the Integration Server. The default processor is ws - Web Services SOAP Processor. |
If you specify HTTP or HTTPS as the transport, but do not specify a host, port, or endpoint alias, 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, web service clients will not execute successfully. For more information see Protocol Mismatch Between Transport
and Primary Port.You can change the default name that Designer assigns to the binder. You can rename the binder by changing the value of the Binder name property or by selecting the new binder, right-clicking it, and selecting Rename.