![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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.
Table 10 JMS (Sheet 1 of 4) 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). To create this certificate, follow the steps described in TIBCO BusinessConnect Trading Partner Administration, Adding LDAP/JMS/Email Server Certificates 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 and installation_name are configured under
BusinessConnect > System Settings > General tab. 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.
2. Once you have entered all required data in the section JMS Settings, click Test Connection to verify that the connection works.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |