Configuring JMS Settings

  1. On System Settings tile > General, click Internal Messaging (JMS).
  2. To configure Private Process JMS
    1. Click Private Process JMS and enter the information specified in below table and click Save.
  3. To configure Intercomponent JMS,
    1. Click Intercomponent JMS and enter the information specified in below table and click Save.
      JMS Settings
      Field Enter
      JMS Settings
      Protocol Prefix jms://
      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.

      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 any TIBCO 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, Adding LDAP/JMS/Email Server Certificates.

      The credential is stored in the BusinessConnect Container Edition keystore and is expected to be configured on the TIBCO Enterprise Message Service server according to the corresponding guidelines.

      Expected JMS Server Host Name The value of the common name component of the TIBCO Enterprise Message Service server's leaf certificate. This is usually the hostname of the resource, 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 checked.
      Strong Ciphers Only If the box is checked, 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 TIBCO Java Runtime Environment (JRE).
      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.
      Queues/Topics (Settings in this section are not configurable)
      Initiator Request Queue

      installation_prefix.installation_name.INITIATOR.REQUEST

      This is the queue on which BusinessConnect Container Edition listens for requests from the Private Process to initiate requests to its partners.

      installation_prefix and installation_name are configured under

      System Settings > General > Installation Properties.

      Initiator Response Queue installation_prefix.installation_name.INITIATOR.RESPONSE

      This is the destination (queue) on which the Private Process listens for a response from the Initiator’s BusinessConnect Container Edition server.

      Note: If a user configures the private process to receive an INITIATOR.RESPONSE message from the BusinessConnect Container Edition server synchronously over the JMS transport, this activity will be successfully completed as soon as the expected response is received. If the BusinessConnect Container Edition sever then resends the same INITIATOR.RESPONSE message for any reason, such as when the user triggers the resend, such message will no longer be requested by the private process and may need to be manually removed. Leaving these messages in the queue won’t cause any problems unless such retries occur in large numbers: if they do, the user should consider manual maintenance of the JMS queue for the INITIATOR.RESPONSE messages.
      Responder Request Queue installation_prefix.installation_name.RESPONDER.REQUEST

      This is the destination (queue) on which the Responder BusinessConnect Container Edition server sends requests to the Private Process.

      Responder Response Queue installation_prefix.installation_name.RESPONDER.RESPONSE

      This is the destination (queue) on which the Responder BusinessConnect Container Edition server listens to responses from the Private Process.

      Responder Acknowledgement Confirm Queue This is the queue on which Responder BusinessConnect Container Edition sends acknowledgement messages to private processes.

      Example: installation_prefix.installation_name.RESPONDER.ACK

Intercomponent DMZ-JMS (Optional)

You can optionally configure an EMS server in the DMZ, which is dedicated for the communication between the Gateway and Interior servers.

The component settings for Intercomponent DMZ-JMS settings are exactly 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 BusinessConnect Container Edition engine starts up, the engine will try to reconnect to the JMS server for a specified period of time (as set in the field Reconnect Max Duration). If the connection could not be established within this time, the engine will stop.

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

If the connection between the BusinessConnect Container Edition and the JMS server is terminated during runtime, the engine will try to establish connection. During this time, messages from private process to BusinessConnect Container Edition will not be received. If the protocols are trying to send 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 if the connection is established. If the connection is established then the message is sent to private process. If the connection is not established with this period of time the engine will throw an appropriate error message.