Changing the Binder Transport
You can change the specified transport of a binder in a service first provider web service descriptor by changing the value of the binder Transport property. Keep the following points in mind when changing the binder transport:
A binder can specify the JMS transport only if the web service descriptor does not run in compatibility mode (the
Pre-8.2 compatibility mode property is set to false).
You can change the transport to JMS only if a provider web service endpoint alias that specifies the JMS transport exists already.
If you change the transport from HTTP or HTTPS to JMS,
Designer automatically assigns the first valid provider web service endpoint alias that specifies the JMS transport to the
Port alias property of the binder. If there is not valid endpoint alias for JMS, the binder transport cannot be changed. 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.
Additionally, Designer updates the Port address property to display the initial part of the JMS URI, specifically “jms”:<lookup var>:<dest>?targetService.
If you change the transport from JMS to HTTP or HTTPS,
Designer deletes the values of the
Port alias property and the
Port address property. If the
Integration Server identifies a default provider endpoint alias for the protocol used by the binder,
Designer sets
Port alias property to DEFAULT(
aliasName). If you want to use a specific web service endpoint alias to specify the hostname and port for the provider web service endpoint URL, make sure to specify that alias in the
Port alias property.
When you change the transport,
Designer updates the
Binding type and
SOAP binding transport properties to match the selected transport.