Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Wizard and Configuration Tab

The Wizard and Configuration tab have the following fields.

Field | Global Var? | Description
--- | --- | ---
Wizard
File Name | No | 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. Unlike other resource identifiers 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.
Configuration Tab
Description | Yes | Short description of the resource.
User Name | Yes | Username 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.
Password | Yes | Password to use when logging into the JMS server. If the JMS provider does not require access control, this field can be empty.
Auto-Generate Client ID | No | Selecting 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 selected, 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 selected, 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.
Client ID | Yes | 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.
Use SSL | No | 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 | Yes | Specifies whether JNDI should be used to look up the ConnectionFactory object. If this field is not selected, the Provider URL and Use XA Connection Factory fields appear. If this field is selected, JNDI configuration fields appear.
Provider URL | Yes | This field is only available when the Use JNDI for Connection Factory field is not selected. This is the URL to use to connect to the JMS server.
Connection Factory SSL Password | Yes | This field is only available when the Use SSL checkbox is selected, and the User Shared JNDI Configuration checkbox is not selected. 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 | Yes | When this field is selected, the JNDI Configuration field appears. Using this you can choose a JNDI Configuration Reference . When this field is not selected, JNDI configuration fields appear.
JNDI Configuration | No | This field only appears when the Use Shared JNDI Configuration field is selected. This field allows you to choose a JNDI Configuration Reference that specifies the JNDI connection information.
JNDI Context Factory | Yes | This field only appears when the Use Shared JNDI Configuration field is not selected. 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.
JNDI Context URL | Yes | This field only appears when the Use Shared JNDI Configuration field is not selected. 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. See your JNDI provider documentation for the syntax of the URL.
JNDI User Name | Yes | This field only appears when the Use Shared JNDI Configuration field is not selected. Username 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 | Yes | This field only appears when the Use Shared JNDI Configuration field is not selected. 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.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.