![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
JMS Connection resource describes a JMS connection. This section provides a reference to the fields. For procedures see Adding a Shared Resource.
The name to appear as the label for the resource. Names follow Java variable naming restrictions. Do not use any reserved words. Names must be unique within a folder. See Identifier Naming Requirements. Note: SSL is supported only when using TIBCO Enterprise Message Service.See Configure SSL for more information. This field allows you to choose a JNDI Configuration that specifies the JNDI connection information. See JNDI Configuration for more information. This field only appears when the Use Shared JNDI Configuration field is unchecked. Required. The initial context factory class for accessing JNDI. (javax.naming.Context.INITIAL_CONTEXT_
FACTORY). You can choose from the drop down list of supported classes or you can type in a different InitialContextFactory class name.Note: TIBCO BusinessEvents 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. This field only appears when the Use Shared JNDI Configuration field is unchecked. Required. This is the URL to the JNDI service provider (javax.naming.Context.PROVIDER_URL). An example URL is provided when one of the supported JNDI context factory classes is selected. This field only appears when the Use Shared JNDI Configuration field is unchecked. 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. This field only appears when the Use Shared JNDI Configuration field is unchecked. 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.The Test Connection button allows you to test the connection specified in the configuration of this resource. See Enabling the Test Connection Feature for a step you must take to enable the connection to work.
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. 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.
When using JNDI to lookup the JMS Connection factory, the parameters ssl_identity and ssl_verify_host must be specified in the factories.conf file of the Enterprise Message Service server.
See Identity Resource for more information. Note: The default context factories for TIBCO Enterprise Message Service automatically determine if host name verification is necessary. If you are using a custom implementation of the context factories, your custom implementation must explicitly set the verify host property to the correct value. For example: When checked, this field specifies that the minimum strength of the cipher suites used can be specified with the bw.plugin.security.strongcipher.minstrength custom engine property. See TIBCO ActiveMatrix BusinessWorks Administration for more information about this property. The default value of the property disables cipher suites with an effective key length below 128 bits.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |