Configuring JMS Settings

To learn more about the JMS transport, see "Using the SSL Protocol" topic in the TIBCO Enterprise Message Service™ User’s Guide.

Select the JMS option to enable the runtime communication with the private process over a secured or unsecured JMS connection. JMS can only be selected (and saved successfully) if the specified connection factory uses the Enterprise Message Service factory string: com.tibco.tibjms.naming.TibjmsInitialContextFactory. Otherwise, the transport can only be saved if this option is not selected.

When selecting a server name under Internal Messaging (JMS), the Details pane and the Credentials pane appears.

Note: BusinessConnect Container Edition sends some messages on JMS Topics, such as ERROR advisories. You can configure JMS Durable topics to avoid message loss.

You can use JMS option to configure JMS and Intercomponent JMS.

Procedure

On the Admin UI, go to System Settings > General, click Internal Messaging (JMS).
To configure Private Process JMS, click Private Process JMS. To configure Intercomponent JMS, click Intercomponent JMS.

Enter the information specified in the following table and click Save.

JMS Settings
Field	Enter
JMS Settings Details
JMS User Name	User name to use when logging into the JMS server. If the JMS provider does not require access control, this field can be empty. Not all JMS servers require user names and passwords. Refer to your JMS provider documentation and consult your system administrator to determine if your JMS server requires a user name and password.
JMS Password	Password to use when logging into the JMS server. If the JMS provider does not require access control, this field can be empty.
JNDI Context Factory	The initial context factory class for accessing JNDI (javax.naming.Context.INITIAL_CONTEXT_FACTORY). Note: BusinessConnect Container Edition attempts to find the class. However, you may need to add the Java file supplied by your JNDI service provider to the `CLASSPATH` environment variable to use JNDI.
JNDI Context URL	This is the URL to the JNDI service provider (javax.naming.Context.PROVIDER_URL). See your JNDI provider documentation for the syntax of the URL. The following is a sample EMS `URL: tibjmsnaming://<EMS_URL>:7222`
JNDI User Name	User name to use when logging into the JNDI server (javax.naming.Context.SECURITY_PRINCIPAL). If the JNDI provider does not require access control, this field can be empty.
JNDI Password	Password to use when logging into the JNDI server (javax.naming.Context.SECURITY_CREDENTIALS). If the JNDI provider does not require access control, this field can be empty.
Topic Connection Factory	The TopicConnectionFactory object stored in JNDI. This object is used to create a topic connection with a JMS application. See your JNDI provider documentation for more information about creating and storing TopicConnectionFactory objects.
Queue Connection Factory	The QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with a JMS application. See your JNDI provider documentation for more information about creating and storing QueueConnectionFactory objects.
Reconnect Max. Duration (mins)	This is the time during which the BusinessConnect Container Edition server will try to reconnect. After this time, there will be no attempt to reconnect. This duration time does not represent the reconnection frequency. Default is `10` minutes.
Secured	If selected, the transaction will be secured.
Verify JMS Server	If selected, the JMS server's identity (that is, its X509 certificate as well as the specified value in the “Expected JMS Server Host Name” field) will be verified against the data received during the SSL handshake. If either the trusted CA certificates or the expected hostname doesn't match, the transport creation fails. If this verification is not required, BusinessConnect Container Edition can establish a JMS connection with an Enterprise Message Service, whose credentials are different from the configured properties.
JMS Server Certificate	The certificate credential of the JMS server. To create this certificate, follow the steps described in TIBCO BusinessConnect™ Container Edition Trading Partner Administration guide, Adding LDAP/JMS/Email Server Certificates. The credential is stored in the BusinessConnect Container Edition keystore and is expected to be configured on an Enterprise Message Service server according to the corresponding guidelines.
Expected JMS Server Host Name	The value of the common name component of an Enterprise Message Service server's leaf certificate. This is usually the hostname of the resource, running an Enterprise Message Service server. If it is a test system, the common name (CN) value may be any arbitrary string, which must match the value of this field if the Verify JMS Server check box is selected.
Strong Ciphers Only	If the box is selected, only strong encryption algorithms will be used between the server (or the palette) and the JMS provider. The below cipher suites are offered by the connecting client (either BusinessConnect Container Edition or the palette) in this mode: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA SSL_RSA_WITH_RC4_128_SHA SSL_RSA_WITH_3DES_EDE_CBC_SHA SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA Note: The unlimited strength JCE jurisdiction policy files are pre-installed on the JRE bundled with TIBCO products.
Use Trace	See comments in TIBCO ActiveMatrix BusinessWorks Palette Reference, JMS Palette section Advanced. When this option is used, the SSL-specific debug tracing for the secure JMS transport will be sent to the engine standard output only.
JMS Credentials
New Certificate	The EMS Route certificate needs to be uploaded for authentication here when the SSL JMS server is being used and when the user selects Verify JMS server option. The EMS Route certificate is found in the EMS folder.

Tip: Intercomponent DMZ-JSM (Optional): You can optionally configure an EMS server in the DMZ for the communication between the Gateway and Interior servers. The component settings for Intercomponent DMZ-JMS settings are exactly the same as that of Intercomponent JMS Settings.

JMS Auto Reconnect for the BusinessConnect Container Edition Server

If the JMS server is down or the network connection is down when the BusinessConnect Container Edition engine starts, the engine tries to reconnect to the JMS server for a specified period of time (as set in the field Reconnect Max Duration). If the connection is not established within this time, the engine stops.

However, if the connection between the engine and the JMS server is established within the specified period (as set in the field Reconnect Max Duration), the engine will continue to run.

If the connection between BusinessConnect Container Edition and the JMS server is terminated during runtime, the engine will try to establish connection. During this time, messages from the private process to BusinessConnect Container Edition are not received.
If the protocols are trying to send a message to private process, the engine will hold the message for a specified period of time (as set in the field Reconnect Max Duration), configured in the JMS transport, to check whether the connection is established.
If the connection is established, then the message is sent to private process.
If the connection is not established within this period of time, an error occurs.

Did you find this helpful?

Yes No