JMS Configuration

The following table lists the JMS configuration details that can be configured using the wizard.
TIBCO ActiveMatrix SPM Dashboard JMS Configuration Properties
Field Name Property in spmdashboard-config.properties Mandatory Default Value Description
Context Factory rta.client.jms.jndi.contextfactory No com.tibco.tibjms.naming.TibjmsInitialContextFactory JMS JNDI context factory
Provider URL rta.client.jms.jndi.url No tibjmsnaming://localhost:7222 JMS JNDI URI
Username rta.client.connection.username No admin Defines the Username for creating the RTA client session
Password rta.client.connection.password No   Defines the password for creating the RTA client session. This is obfuscated using the obfuscation utility that is shipped with the product.
Test Connection Tests an EMS connection.

(Optional) Select Advanced Options to configure advanced JMS options. Provide the following values and click Next.

Note: If you do not select Advanced Options, the advanced properties take default values. However, if you use Advanced Options, the properties take the last configured values. The spmdashboard-config.properties file has the last configured values.
TIBCO ActiveMatrix SPM Dashboard JMS Configuration Advanced Properties
Field Name Property in spmdashboard-config.properties Mandatory Default Value Description
Queue Connection Factory rta.client.jms.queueconnectionfactory No SPMQueue ConnectionFactory JMS queue connection factory
Inbound Queue rta.client.jms.inbound.queue No spm.inbound.queue The JMS queue on which the client API sends fact messages. It should match the server's rta.jms.inbound.queue property.
Inbound Query Queue rta.client.jms.inbound.query.queue No spm.inbound.query.queue The JMS queue to which the query or other synchronous request/reply-based messages are sent. It should match the server's rta.jms.inbound.query.queue property.
Outbound Queue rta.client.jms.outbound.queue No spm.outbound.queue The JMS queue to receive asynchronous messages like streaming query responses, alerts and server notifications. It should match the server's rta.jms.outbound.queue property.