Property | Description | |
Enabled | Specifies whether the webMethods Messaging Trigger is enabled or disabled. | |
Select... | To... | |
True | Enable the webMethods Messaging Trigger. An enabled webMethods Messaging Trigger contains one or more valid conditions. | |
False | Disable the webMethods Messaging Trigger. A disabled webMethods Messaging Trigger can contain valid or invalid conditions. A disabled webMethods Messaging Trigger does not have any subscriptions registered on the Integration Server or the messaging provider. | |
Join expires | Indicates whether the join expires after the time period specified in Expire after. | |
Select... | To... | |
True | Indicate Integration Server should stop waiting for the remaining documents in a join condition after the time specified in Expire after elapses. | |
False | Indicate that the join should not expire. That is, Integration Server should wait indefinitely for the remaining documents in a join condition. | |
Note:webMethods Messaging Triggers that receive documents from Universal Messaging do not use joins. Designer ignores the value of the Join expires property if the trigger subscribes to publishable document types that can be published to Universal Messaging. | ||
Expire after | Specifies how long Integration Server waits for the remaining documents in the join condition. The default join time-out period is 1 day. Note:webMethods Messaging Triggers that receive documents from Universal Messaging do not use joins. Designer ignores the value of the Expire after property if the trigger subscribes to publishable document types that can be published to Universal Messaging. | |
Priority enabled | Specifies whether priority messaging is enabled or disabled for the webMethods Messaging Trigger. This property applies to webMethods Messaging Triggers that receive documents from Broker only. webMethods Messaging Triggers that receive documents from Universal Messaging always receive higher priority documents in an expedited fashion. Additionally, priority messaging does not apply to locally published documents received by the webMethods Messaging Trigger. At run time, Integration Server ignores the value of the Priority enabled property if the trigger receives a locally published document. | |
Select... | To... | |
True | Enable priority messaging for the webMethods Messaging Trigger. Note: If priority messaging is enabled on an existing trigger, the Broker connection is dropped and the client is deleted. The client gets recreated when the Broker connection is re-established. This may result in loss of documents for that trigger. | |
False | Disable priority messaging for the trigger. | |
Execution user | Specifies the name of the user account whose credentials Integration Server uses to execute a service associated with the webMethods Messaging Trigger. You can specify a locally defined user account or a user account defined in a central or external directory. Note: The Execution user property only applies to webMethods Messaging Triggers that receive documents from Universal Messaging. The publishable document type to which a trigger subscribes determine the messaging provider from which the trigger receives messages. At run time, Integration Server ignores the value of the Execution user property if a webMethods Messaging Trigger receives locally published documents or documents from Broker | |
Permissions | Click  to assign or view ACL permissions to a webMethods Messaging Trigger. | |
Reuse | Specifies whether this element can be dragged from the CentraSite Registry Explorer view to a BPM process or CAF project. When this property is set to public, you can drag the asset to a BPM process or CAF project. When this property is set to private (the default), you cannot drag the asset to a BPM process or CAF project. All published assets are available for Impact Analysis, whether they are public or private. Although changing the public/private status will immediately change whether or not you can drag an element to a BPM process or CAF project, the element's status in CentraSite will not change until the next publication of assets to CentraSite. | |