ActiveMatrix BPM: JMS Configuration

Field/Button Description
Use Admin EMS Configuration Whether to use the internal EMS server to handle inbound JMS requests. If this option is:
  • selected, the remaining fields show the internal EMS server details. You cannot edit these values.
  • cleared, the remaining fields are enabled, allowing you to enter the details of an external JMS server to use instead.

Default: Selected

Server Type The JMS server type.

Default: TIBCO EMS

JMS Url The URL of the JMS server to be used by this BPM system to handle JMS messages.

Default: tibjmsnaming://localhost:7222

build.properties entry: bpm.userapp.jndi.jms.url

Initial Context The initial context factory to use for the JNDI lookup of the JMS server. TIBCO recommend that you do not change the default value.

Default: com.tibco.tibjms.naming.TibjmsInitialContextfactory

build.properties entry: bpm.userapp.jms.initial.context

Connection Factory The name of the connection factory used to create the connection to the JMS server. TIBCO recommend that you do not change the default value.

Default: GenericConnectionFactory

build.properties entry: bpm.jms.connection.factory

Inbound Request Queue The name of the JMS server queue that this BPM system uses to receive messages. TIBCO recommend that you do not change the default value.

Default: queue.sample

build.properties entry: bpm.userapp.jms.request

Username The user account to be used to connect to the JMS server.

Default: admin

build.properties entry: bpm.userapp.jms.username

Password The password for the user account to be used to connect to the JMS server.

build.properties entry: bpm.userapp.jms.password

JMS Connection is SSL Enabled Whether the external JMS server is enabled for SSL. When selected, the SSL Trust Store Configuration fields are enabled. (This option is not available if the internal EMS server is being used.)
Note: If this BPM system is distributed across different machines (to provide high availability and/or scalability), the Trust Store Location must be SHARED_DIR\keystores - see Shared File System.

Default: Cleared

build.properties entry: bpm.userapp.jms.enablessl

Test Connection Verifies that TIBCO Configuration Tool can connect to the JMS server using the information supplied on this page.
SSL Trust Store Configuration:
Create a Trust Store Obtains certificates from the specified JMS server and creates a new trust store, which will be used to establish the trust relationship with the JMS server:
  1. Click Create a Trust Store.
  2. Specify a password to protect the keystore and click Next. The SSL setup wizard displays the certificates imported from the JMS server.
  3. In the Trust Selected Certifications area, select the certificates to trust and click Finish. The wizard fills in the Keystore Location, Keystore Type, and Keystore Password fields.

    If you do not click Create a Trust Store, you must specify the details of an existing trust store that can be used to establish the trust relationship with the JMS server.

Trust Store Location Either:
  • the location in which the created trust store will be stored, or
  • the location of the trust store to be uploaded to ActiveMatrix Administrator. (You can either type this directly or use the Browse button to find it.)

build.properties entry: bpm.userapp.jms.ssl.keystorelocation

Trust Keystore Type The type of the created or uploaded trust store: JKS or JCEKS.

Default: JKS

build.properties entry: bpm.userapp.jms.ssl.keystoretype

Trust Store Password Either:
  • the password specified in the Create a Trust Store wizard, or
  • the password required to access the trust store that is to be uploaded.

build.properties entry: bpm.userapp.jms.ssl.keystorepassword

This information is used to create the following BPM runtime resource templates/instances, which this BPM system uses to communicate with the JMS server.

Type Name Description
JNDI Connection Configuration amx.bpm.userapp.jndiConnConf Provides a JNDI connection to look up the JMS server.
JMS Connection Factory Configuration amx.bpm.userapp.jmsConnFactoryConf These two are used (with the JNDI Connection Configuration) to establish inbound communication with the JMS server.
JMS Destination Configuration amx.bpm.userapp.jms.request.conf
JMS Connection Factory amx.bpm.userapp.jmsConnFactory Used (with the JNDI Connection Configuration) to establish outbound communication with the JMS server.
Note: The following table shows how certain ActiveMatrix BPM: JMS Configuration fields are mapped to the specified resource templates, via BPM application substituion variables (SVars).
Value of the ActiveMatrix BPM: JMS Configuration field ... ... is written to the BPM application SVar... ... which is used in Resource Template(s) ... ... to populate the field ...
JMS Url userappProviderUrl amx.bpm.userapp.jndiConnConf Provider URL
Initial Context userappInitialContextFactory amx.bpm.userapp.jndiConnConf Initial Context Factory
Connection Factory userappConnectionFactory amx.bpm.userapp.jmsConnFactoryConf Connection Factory JNDI Name
amx.bpm.userapp.jmsConnFactory Connection Factory JNDI Name
Inbound Request Queue userappJmsRequest amx.bpm.userapp.jms.request.conf Destination JNDI Name

See "Resource Templates > Shared Resource Templates" in TIBCO ActiveMatrix BPM - SOA Administration for more information about these shared resources.