About Process Engine and JMS Connection Aliases
By default, the Process Engine uses a non-transactional JMS connection alias with the specific name PE_NONTRANSACTIONAL_ALIAS when either of the following conditions is true:
You are running the
Process Engine in a multi-
Integration Server environment (that is, either in a cluster or using distributed models).
OR
You are running a single
Integration Server configuration and running process models generated with receive steps that use the JMS protocol.
Note:
The PE_NONTRANSACTIONAL_ALIAS is created automatically during installation with a default value of DEFAULT_IS_JNDI_PROVIDER. If only a webMethods Broker (deprecated) instance is found on the local server, then DEFAULT_IS_JNDI_PROVIDER is set to point to the webMethods Broker (deprecated) server. If both webMethods Broker (deprecated) and Software AG Universal Messaging are installed, or Universal Messaging only is installed, then DEFAULT_IS_JNDI_PROVIDER is set to point to the Universal Messaging server. If for any reason you create this alias manually, you must reload the WmPRT package after you complete the alias creation.
In the above cases, JMS must be configured on your Integration Server(s) as follows:
In a clustered or distributed
Integration Server environment, the Connection Client ID (JMS)
must be identical for all nodes.
In a non-clustered environment, the Connection Client ID (JMS)
must be different for each node.
A JMS connection alias is required because the Process Engine uses it to broadcast internal events between the Process Engine nodes. When you select the JMS protocol, Process Engine uses the PE_NONTRANSACTIONAL_ALIAS connection alias by default for communication, and generates a destination in the subscription trigger of the generated process. When you publish a message using JMS and the PE_NONTRANSACTIONAL_ALIAS to trigger the process, you must specify this auto-generated destination. For convenience, the pub.prt.jms.send service can be used to simplify sending messages that trigger processes.
In addition to the default connection alias, you can create and specify custom JMS aliases for use with subscription triggers. You must create these connection aliases manually on Integration Server. Custom JMS connection alias names are stored in the process, and custom alias definitions are stored in Integration Server and on webMethods Broker (deprecated).
When you use a custom JMS alias, you can also use a custom destination in the subscription trigger of the generated process. Custom destinations must also be created manually. When you publish a message using JMS and a custom connection alias, you must specify the destination.
When you receive a message using JMS and a custom connection alias, you can specify a destination, or you can use the default destination created by
Designer.
Transition triggers will always use the PE_NONTRANSACTIONAL_ALIAS connection alias.
To learn more about creating JMS connection aliases and working with JMS triggers, see the PDF publication Using webMethods Integration Server to Build a Client for JMS.
Note:
When a JMS-triggered process uses the PE_NONTRANSACTIONAL_ALIAS connection alias, that alias must have the Manage Destinations option shown as Yes in the connection alias Advanced Settings. For more information, see “Setting the Manage Destination Option for a Connection Alias” in the webMethods BPM Process Development Help.