JMS connector account parameters

JMS connector account parameters define the connection details required to link the platform with a JMS-compliant messaging provider. These parameters typically include the provider URL, connection factory, security credentials, and JNDI settings, enabling secure and reliable communication for sending and receiving messages through queues or topics.

Name: Name of the account for identification.
Description: Short description about the account.
Messaging provider template: Messaging Provider that webMethods Integration must connect with to send or receive messages.
Provider URL: Primary URL of the initial context for sessions with the JNDI provider. The URL specifies the JNDI directory in which the JNDI provider stores JMS-administered objects.
Clustered UM: Option to specify whether the realm specified in the Provider URL is part of a cluster. Server clustering refers to a group of servers that work together as one system to provide users with higher availability. These clusters are used to reduce downtime and outages by allowing another server to take over in the event of an outage. This option is applicable only if the provider is Universal Messaging and is clustered.
Follow the Master: Whether connections that are created from this account must always connect to the master realm server in the cluster. This setting affects producer and consumer connections that are created by using this account. If selected, webMethods Integration always connects to the master realm server in a Universal Messaging cluster to send or receive messages. Otherwise, webMethods Integration connects to one of the servers that are listed by following the order that is specified in Connection retry mode. This option is applicable only if the provider is Universal Messaging and is clustered.
Clustered Realm URLs: Remaining URLs of the cluster. This option is applicable only if the provider is Universal Messaging and is clustered. This option is applicable only if the provider is Universal Messaging is clustered and the Follow the Master option is disabled.
Connection retry mode: The method by which webMethods Integration must attempt to connect to one of the servers in the cluster when the existing connection is lost. In sequential mode, webMethods Integration retries to establish connections with the servers in the order specified in the list. In random mode, webMethods Integration retries to establish a connection at random to any of the servers specified in the list.
Provider URL Failover List: JNDI URLs that webMethods Integration must connect to if the existing connection is lost. This option is applicable only if the provider is not a clustered Universal Messaging setup. Failover support enables recovery from failures that occur during processing, making your applications more robust. For example, by having more than one messaging servers, you protect your application from failure in case one of the servers becomes unavailable. If the webMethods Integration connection with the server fails, webMethods Integration automatically reconnects to another server provided in the list.
Connection ClientID: JMS client identifier that is associated with the connections that are established by this account.
JMS connection factory lookup name: Lookup the name for the connection factory that you want to use to establish a connection with the Messaging provider specified in this JMS Connector Account.
Security principal: Username that webMethods Integration provides to the JNDI provider for accessing the JNDI directory.
Security credentials: Password that webMethods Integration provides to the JNDI provider for accessing the JNDI directory.
Use SSL: Option to establish a secure communication between webMethods Integration and the JNDI provider.
Truststore Alias: Alias for the truststore that contains the certificates of the certificate authority (CA) for the JNDI provider.
Keystore alias: Alias for the keystore that contains the client certificates for webMethods Integration to use when connecting to the JNDI provider by using two-way SSL.
Key alias: Alias to the key that contains the private key for connecting to the JNDI provider by using two-way SSL.
Max retry attempts: Option to specify whether the webMethods Integration must retry to connect to the Messaging Provider when a transient error occurs, such as connectivity loss with Messaging Provider.
Retry interval: Duration (in seconds) that the publisher waits before retrying the publish action again. When you configure the Max retry attempts and Retry interval options, the publisher flow service or workflow does not end the publish action immediately when a transient error occurs. webMethods Integration retires to publish the message for the configured number of times based on the specified Retry interval . webMethods Integration throws an exception if the error persists even after retrying.
Cache JMS Sessions: Whether JMS sessions and related session objects that are created by the producer must be cached between publishing calls. When sending a message, webMethods Integration creates and closes a new JMS session for each message. When a cached session pool is defined for a JMS account, webMethods Integration draws from a pool of OpenJMS sessions for sending a message instead of opening and closing a session for each JMS message. You can specify the minimum and maximum sizes for the session pools as well as the idle time after which an idle session object can be removed from the pool.
Create new connection per subscriber: Whether to create a new connection for each subscriber to receive messages in parallel using this account. Otherwise, all subscribers use the same connection. The number of connections a subscriber can make can be set in the Connection Count property under Message Processing in Subscriber settings.