JMS
The JMS panel contains the following fields.
| Field | Module Property? | Description |
|---|---|---|
| Installation Name | Yes | The name of the TIBCO BusinessConnect installation. |
| Installation Prefix | Yes | Prefix that defines an installation. |
| JMS User Name | Yes | 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 | Yes | 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 | Yes | The initial context factory class for accessing JNDI.
See TIBCO BusinessConnect Trading Partner Administration Guide for details. |
| JNDI Context URL | Yes | This is the URL to the JNDI service provider.
See TIBCO BusinessConnect Trading Partner Administration Guide for details. |
| JNDI User Name | Yes | If the deployed JMS/JNDI provider(s) requires no authentication with the client, the JMS User Name/JNDI User Name fields might be left blank. |
| JNDI Password | Yes | If the deployed JMS/JNDI provider(s) requires no authentication with the client, the JMS Password/JEDI Password fields might be left blank. |
| Topic Connection Factory | Yes | The TopicConnectionFactory object stored in JNDI.
See TIBCO BusinessConnect Trading Partner Administration Guide for details. |
| Queue Connection Factory | Yes | The QueueConnectionFactory object stored in JNDI.
See TIBCO BusinessConnect Trading Partner Administration Guide for details. |
| Auto Confirm | Yes | Specifies whether inbound JMS messages are confirmed to the provider automatically (after successfully dispatching them to at least one of the subscribing event sources), or the process definition needs to explicitly take care of that by placing a Confirm activity in the process definition and confirming the corresponding event.
Once this check box is selected, inbound messages are automatically confirmed, which means that inbound JMS messages dispatched to BusinessWorks are acknowledged so that the JMS provider can remove them accordingly. Otherwise, messages might be left in the JMS provider's persistent store. TIBCO BusinessConnect business protocols might specify JMS topic transports and expect non-durable receivers on some miscellaneous messages (specified by the AE schemas of these messages) that can be lost without causing problems. This can help to reduce the load on JMS providers. Regarding message types that are set on topics and do not need confirmation, consult the corresponding business protocol’s User’s Guide. |
| Auto Create Destinations | Yes | Managing administered objects, such as JMS topics and queues on the preferred JMS provider, is generally the responsibility of the JMS provider’s administrator.
If privileges allow it, the palette can create the required queues and topics automatically and dynamically. If selected, the starting JMS transport attempt to create the needed destinations (queues and/or topics) in the specified transport modes. If unsuccessful, an exception is raised and either the privileges need to be adjusted or the administered objects need to be created manually. Regarding the requirements of the destinations, the user's guides of the specific protocols can provide more guidance. |
| Reconnect Duration (>= mins) | Yes | Timeout configuration property in minutes both for the TIBCO BusinessConnect server and the TIBCO BusinessConnect palette . |
| Secured | Yes | If the
Secured check box is selected, the secure JMS transport is used.
Secure JMS can only be selected if the TIBCO Enterprise Message Service specific JNDI Context Factory has been specified. If the JNDI Context Factory field is empty or it specifies a different provider's factory, a dialog appears when selecting the box and gives an error. When the dialog is accepted, the Secured check box moves back to the unselected state and the secure JMS transport remains (or becomes) disabled. |
| Test JMS Connection | Click
Test JMS Connection to test whether a proper connection is established.
Upon successful connection, a dialog reports the status and the name/version of the provider with whom the connection has been established. If the connection is unsuccessful, cause is indicated if available. |
Secure JMS Transport
When you click the Import Selected Business Protocol button in the Configuration tab and the plug-in imports the configuration from the TIBCO BusinessConnect configuration store, the credentials for the JMS server and client identity are fetched and stored in the BC Connection shared resource .
The retrieved configuration properties can always be overridden in the plug-in level using new values. That includes turning on or off the secure transport, as well as reconfiguring or changing the credentials that are configured for the TIBCO BusinessConnect server transport.
If the TIBCO Enterprise Message Service server requires a secure transport, then disabling this transport, although possible in the plug-in, results in a connection failure when the project is building up the JMS transport at runtime.
The secure JMS transport includes the following fields.
| Field | Module Property? | Description |
|---|---|---|
| Verify JMS Server | Yes | If selected, the JMS server's identity (its X509 certificate as well as the specified value in the
Expected JMS Server Host Name field) is verified against the data received during the SSL handshake. If either the trusted CA certificates or the expected host name do not match, the transport creation fails.
If this verification is not required, TIBCO BusinessConnect can establish a JMS connection with any TIBCO Enterprise Message Service server whose credentials are different from the configured properties. |
| Trusted JMS Server Certificates | No | If the credentials are supposed to be identical on both the TIBCO BusinessConnect server and the TIBCO BusinessConnect palette-based private process, no changes in the configuration are needed after the import of the configuration on the palette. |
| Expected JMS Server Host name | Yes | This is the value of the common name component of the TIBCO Enterprise Message Service server's leaf certificate. It is usually the hostname of the resource that is running the TIBCO 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 | Yes | See the corresponding field in TIBCO BusinessConnect Trading Partner Administration Guide for details. |
| Use Trace | Yes | See comments in TIBCO ActiveMatrix BusinessWorks Palette Reference, "JMS Palette" for details. |