pub.trigger:enableJMSTriggers

WmPublic. Enables one or more JMS triggers.

Input Parameters

triggerNameList

String List Specifies the JMS triggers that you want to enable.

applyChangeAcross Cluster

String Optional. Flag indicating whether the specified JMS triggers should be enabled across all the servers in the cluster. Set to:

true to enable the specified JMS triggers on all the nodes in the cluster.

Note:
To make the state change on all the servers in a cluster, the Integration Server must be configured to synchronize trigger changes across the cluster. For more information about configuring an Integration Server to synchronize trigger management changes across a cluster, see webMethods Integration Server Administrator’s Guide.

false to enable the JMS triggers on the local Integration Server only. This is the default.

Output Parameters

None.

Usage Notes

When a JMS trigger is enabled, the JMS trigger is running and connected to the JMS provider. Integration Server retrieves and processes messages for the JMS trigger.

You can also use the Settings > Messaging > JMS Trigger Management pages in Integration Server Administrator to disable, enable, and suspend JMS triggers. For more information, see webMethods Integration Server Administrator’s Guide.

You can use the pub.trigger:disableJMSTriggers service to disable one or more JMS triggers.

Use the pub.trigger:suspendJMSTriggers service to suspend one or more JMS triggers.

If you set applyChangeAcrossCluster to true and the synchronization is not successful, the following occurs:

If Integration Server does not update all the Integration Servers in the cluster successfully, the Integration Server writes the following server log entry for each server that could not be updated:

[ISS.0098.0107E] Error occurred during cluster invoke:
Alias = remoteAliasName; Service = serviceName; = exceptionName

The Integration Server Administrator also displays the following message:

[ISS.0085.9203] Errors occurred while updating remote aliases
(x of y updates failed). See server logs for more details.

If Integration Server cannot update the Integration Servers in the cluster because the change could not be made locally, the Integration Server Administrator displays the following message:

[ISS.0085.9204] Local update failed: Exception providing reason for failure.
(Note: The cluster synchronization will not run until all local errors
are resolved.)

If the Integration Server cannot update the Integration Servers in the cluster because cluster synchronization is not configured, the Integration Server writes the following server log entry:

[ISS.0033.0156W] Cluster invoke did not complete successfully.
Cluster Synchronization feature is not configured.

You can use the Integration Server Administrator to view and change cluster synchronization status for triggers. For more information, see webMethods Integration Server Administrator’s Guide.