Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Private Process Configuration : JMS Transport

JMS Transport
To learn more about the JMS transport, see TIBCO Enterprise Message Service User’s Guide, Using the SSL Protocol.
When JMS is selected, TIBCO BusinessConnect will assume that the runtime communication with the private process will take place over a secured or unsecured JMS connection. JMS can only be selected (and saved successfully) if the specified connection factory uses the TIBCO Enterprise Message Service factory string: com.tibco.tibjms.naming.TibjmsInitialContextFactory. Otherwise, the transport can only be saved if this button is not selected.
Configuring JMS Transport
To configure JMS settings, do the following:
1.
The initial context factory class for accessing JNDI. (javax.naming.Context.INITIAL_CONTEXT_FACTORY).
Note: TIBCO BusinessConnect 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.
User name to use when logging into the JNDI server (javax.naming.Context.SECURITY_PRINCIPAL).
Password to use when logging into the JNDI server (javax.naming.Context.SECURITY_CREDENTIALS).
Note: The unlimited strength JCE jurisdiction policy files are pre-installed on the TIBCO Java Runtime Environment (JRE).
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.
installation_prefix.installation_name.INITIATOR.REQUEST
installation_prefix and installation_name are configured under
BusinessConnect > System Settings > General tab.
installation_prefix.installation_name.INITIATOR.RESPONSE
Note: If a user configures the private process to receive an INITIATOR.RESPONSE message from the TIBCO BusinessConnect server synchronously over the JMS transport, this activity will be successfully completed as soon as the expected response is received. If the TIBCO BusinessConnect server 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.
installation_prefix.installation_name.RESPONDER.REQUEST
installation_prefix.installation_name.RESPONDER.RESPONSE
Example: installation_prefix.installation_name.RESPONDER.ACK
2.
Once you have entered all required data in the section JMS Settings, click Test Connection to verify that the connection works.
3.
JMS Auto Reconnect for the TIBCO BusinessConnect Server
If the JMS server is down or the network connection is down when TIBCO BusinessConnect 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 TIBCO BusinessConnect engine and the JMS server is terminated during runtime, the engine will try to establish connection. During this time, messages from private process to TIBCO BusinessConnect 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.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved