Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Managing JMS Triggers | About WS Endpoint Triggers
 
About WS Endpoint Triggers
 
Editing WS Endpoint Triggers
A WS (Web Service) endpoint trigger is a SOAP-JMS trigger with limited configuration options. A WS endpoint trigger is associated with a provider web service endpoint alias and acts as a listener for any provider web service descriptors to which the alias is assigned. Typically, WS endpoint triggers are used with virtual services deployed to webMethods API Gateway.
Keep the following points in mind when working with WS endpoint triggers:
*Integration Server uses the following naming convention when creating a WS endpoint trigger: WS Endpoint Trigger: aliasName where aliasName is the provider web service endpoint alias name.
*Integration Server saves WS endpoint triggers to the following configuration file: Integration Server_directory /instances/instance_name/config/endpoints/providerJMS.cnf.
*The existence of the WS endpoint trigger is tied to the provider web service endpoint alias. If you select WS Endpoint Trigger as the JMS trigger to use with a provider web service endpoint alias, Integration Server creates the WS endpoint trigger a part of creating the alias. If you delete the alias, Integration Server deletes the WS endpoint trigger as well.
*At the time it creates the WS endpoint trigger, Integration Server sets some default properties, such as serial processing and the JMS connection alias. You can use Integration Server Administrator to change the default values.
Note:
While WS endpoint triggers are SOAP-JMS triggers, WS endpoint triggers have a subset of the properties and features of a SOAP-JMS trigger. For example, exactly-once processing, fatal error handling, and transient error handling are available for SOAP-JMS triggers only.
*When Integration Server creates a WS endpoint trigger, Integration Server assigns a placeholder destination. The destination name uses the format: wseQueue_aliasName where aliasName is the provider web service endpoint alias name. Unless a queue with this name exists, you must specify the actual destination to which the WS endpoint trigger subscribes.
*When Integration Server creates a WS endpoint trigger, Integration Server leaves the WS endpoint trigger in a disabled state. You must enable the trigger for it to receive messages from the JMS provider. For more information about enabling JMS triggers, see About JMS Trigger Status and State.
*You can only edit the WS endpoint trigger using Integration Server Administrator. You cannot use Designer to edit a WS endpoint trigger.
*Integration Server sets the execution user to Administrator for all WS endpoint triggers.