JMS Connection resource describes a JMS connection. This section provides a reference to the fields. For procedures see Adding a Shared Resource.
Global Var? 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 Identifiers (Names).Unlike other resource identifiers, however, shared resource identifiers can have spaces in the name.This field appears on the New JMS Connection Wizard. The name then appears in the title of the resource. 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. Auto-Generate Client ID Checking this field specifies you wish to automatically generate the client ID if no client ID is specified or if the specified ID is already in use. When this field is checked, if a value is specified in the Client ID field, an attempt is made to use the specified value. However, if the specified value is already in use, a new client ID is generated.If this field is not checked, then the value specified in the Client ID field is used. If no value is specified in the Client ID field, then no client ID is set. If the value specified in the Client ID field is already in use, an exception is thrown. Client ID for the connection. Typically JMS providers have a provider-specific format for client IDs. See your JMS provider’s documentation for more information about client IDs. Each connection must use a unique Client ID.You cannot use the same JMS Connection resource for accessing both topics and queues. You should create separate JMS Connection resources if you wish to access both topic and queue destinations. Specifies whether you wish to use SSL for the connection to the JMS server. SSL is used when the Use SSL checkbox is checked. Click the Configure SSL button to configure the SSL connection parameters.Note: SSL is supported only when using TIBCO Enterprise Message Service.See Configure SSL for more information. Use JNDI for Connection Factory Specifies whether JNDI should be used to look up the ConnectionFactory object. If this field is unchecked, the Provider URL and Use XA Connection Factory fields appear. If this field is checked, JNDI configuration fields appear. This field is only available when the Use JNDI for Connection Factory field is unchecked. Use XA Connection Factory This field is only available when the Use JNDI for Connection Factory field is unchecked. Connection Factory SSL Password This field is only available when the Use SSL checkbox is checked, and the User Shared JNDI Configuration checkbox is unchecked.The SSL configuration is specified in the ConnectionFactory object, except for the client SSL password.You can specify your client SSL password in this field, or you can leave this field empty. If your password is not specified, the private key password is used. Use Shared JNDI Configuration When this field is checked, the JNDI Configuration field appears. It allows you to choose a JNDI Configuration. JNDI Configuration This field only appears when the Use Shared JNDI Configuration field is checked.This field allows you to choose a JNDI Configuration that specifies the JNDI connection information. See JNDI Configuration for more information. JNDI Context Factory 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: 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. JNDI Context URL 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 To Add a Shared Resource for a step you must take to enable the connection to work.Note that this button is only enabled if JNDI is not used (that is, the Use JNDI for Connection Factory field is unchecked) or if the required JNDI fields on the Configuration and Advanced tab are supplied when JNDI is used.
Global Var? Topic Connection Factory This field is only available when the Use JNDI for Connection Factory field on the Configuration tab is checked.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 This field is only available when the Use JNDI for Connection Factory field on the Configuration tab is checked.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. Optional JNDI Properties Any additional properties to supply for the connection. You specify a name, datatype, and value for each property.These properties are typically vendor-specific. See your JNDI provider documentation for more information about the available properties.
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.
Trusted Certificates Folder Location of the trusted certificates on this machine. The trusted certificates are a collection of certificates from servers to whom you will establish connections. If the server you wish to establish a connection presents a certificate that does not match one of your trusted certificates, the connection is refused.Trusted certificates must be imported into a folder, and then you can select the folder in this field. The location of the client certificate. This is a resource contained in the General palette.You only need to specify the client certificate when the JMS server requires client authentication.See Identity Resource for more information. Specifies whether SSL tracing should be enabled during the connection. If checked, the SSL connection messages are logged and sent to the console. Specifies whether SSL debug tracing should be enabled during the connection. Debug tracing provides more detailed messages than standard tracing. Specifies whether you wish to verify that the host you are connecting to is the expected host. The host name in the host’s digital certificate is compared against the value you supply in the Expected Host Name field. If the host name does not match the expected host name, the connection is refused.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: Specifies the name of the host you are expecting to connect to. This field is only relevant if the Verify Host Name field is also checked.If the name of the host in the host’s digital certificate does not match the value specified in this field, the connection is refused.This prevents hosts from attempting to impersonate the host you are expecting to connect to. 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.When this field is unchecked, only cipher suites with an effective key length of up to 128 bits can be used.
Copyright © TIBCO Software Inc. All Rights Reserved.