Channel Resource Reference
Channels allow TIBCO BusinessEvents to listen to and send out messages. Channels contain destinations.
You can configure channels of different types, using the appropriate driver. See TIBCO BusinessEvents Architect’s Guide.
To configure an HTTP channel resource, select an HTTP connection resource. No other channel resource fields require configuration.
Field | Global Var? | Description |
---|---|---|
Name | No | (Shown in the Wizard and then in the editor title only.) The name to appear as the label for the resource. Names follow Java variable naming restrictions. Do not use any reserved words. |
Description | No | Short description of the resource. |
Driver | No | Select the driver for the type of channel you are configuring: |
Method of Configuration | No | Properties - Select
Properties to configure this channel resource using properties. The properties configuration is depended on the value of
Driver. If
Driver is:
Resource - Select Resource if you have a shared resource in your project whose properties you want to reuse for this channel. Note: The path to the resource and the resource name cannot contain any of the words listed in TIBCO BusinessEvents Architect’s Guide. |
Resource | No | If you choose Resource as the method of configuration, the Resource field appears. Browse to and select the resource you want to use. For convenience, you can open the selected resource by clicking the underlined label. |
Configuration for TIBCO Rendezvous Channels
Field | Global Var? | Description |
---|---|---|
Service | Yes | The name of the service or port number through which Rendezvous sends messages. In most cases you can leave this field empty, accepting the default value.
For more information about the Rendezvous service parameter, see TIBCO Rendezvous Concepts or TIBCO Rendezvous Administration. Default is 7500 (defined in Global Variables). |
Network | Yes | The network over which Rendezvous sends messages. In most cases you can leave this field empty. For more information about the network parameter, see
TIBCO Rendezvous Administration.
Default is an empty string (defined in Global Variables). |
Daemon | Yes | The location of the Rendezvous daemon, which is usually expressed as a client socket number, for example 6555. In most cases, you can leave this field empty, accepting the default value. For more information about the daemon parameter, see
TIBCO Rendezvous Concepts.
Default is tcp:7500 (defined in Global Variables). |
Configuration for JMS Channels
Field | Global Var? | Description |
---|---|---|
ProviderURL | Yes | The URL at which TIBCO BusinessEvents can contact the Enterprise Message Service server.
Example: tcp://localhost:7222 |
UserName | Yes | A valid user name for the Enterprise Message Service server. |
Password | Yes | The password assigned to the user name specified in UserName, for accessing the Enterprise Message Service server. |
IsTransacted | Yes | Accepts true or false. Specify true if the session has transaction semantics. Specify false if it has non-transaction semantics. For more information about the IsTransacted property, see TIBCO Enterprise Message Service documentation. |
ClientID | Yes | The unique client ID of the connection. |
Configuration for StreamBase Channels
Field | Global Var? | Description |
---|---|---|
StreamBase Server URI | Yes | The URI at which TIBCO BusinessEvents can contact the StreamBase server
Example: sb://localhost:10000/ |
UserName | Yes | A valid user name for the StreamBase server.
Note: This field is required only when the basic authentication is enabled at the StreamBase server. |
Password | Yes | The password assigned to the user name specified in
UserName, for accessing the StreamBase server.
Note: This field is required only when the basic authentication is enabled at the StreamBase server. |
SSL Trust Store File | Yes | Location of the truststore file. |
SSL Trust Store Password | Yes | Password to access the truststore file. |
SSL Key Store File | Yes | Location of the keystore file. |
SSL Key Store Password | Yes | Password to access the keystore file. |
SSL Key Password | Yes | Password to access the key in the keystore file. |
Configuration for ActiveSpaces Channels
Configuration for Kafka Channel
Field | Global Variable? | Description |
---|---|---|
Kafka Broker URLs | Yes | List of URLs (host and port pairs) that are used for establishing the initial connection to the Kafka cluster. The format of the URL is
host1:port1,host:port2,....
For more details refer to the setting bootstrap servers topic in the Kafka Documentation (https://kafka.apache.org/documentation/). |
Security Protocol | Yes | The security protocol is implemented in the Kafka broker. This protocol must match with security protocol configured in the Kafka broker. For more details about how to configure security for Kafka broker, refer to the
Kafka Documentation at
https://kafka.apache.org/documentation/#security. You can select the following security protocol values:
The default value is PLAINTEXT. |
SASL Mechanism | Yes | Type of SASL mechanism is implemented on Kafka broker. This field is active only for SASL_PLAINTEXT and SASL_SSL security protocol. The following SASL mechanisms are supported for the Kafka channel: |
Configure SSL | N/A | Click the
Configure SSL button to open the SSL configuration window and configure SSL details. This button is active only for
SSL and
SASL_SSL security protocol. The following fields are available on the SSL configuration window:
|
Configuration for FTL Channels
Field | Global Var? | Description |
---|---|---|
RealmServer | Yes | The URL at which BusinessEvents can connect to the FTL realm server.
The default value is: http://localhost:8080 |
UserName | Yes | A valid user name for the FTL realm server. |
Password | Yes | The password assigned to the user name specified in UserName, for accessing the FTL realm server. |
Secondary | Yes | The URL of the secondary FTL realm server. |
Configuration for MQTT Channels
Configuration for Kinesis Channels
Field | Global Var? | Description |
---|---|---|
Access Key | No |
Key used in combination with the Secret Key to make programmatic requests to AWS. For example, AKIAIOSFODNN7EXAMPLE The access key is similar to a user name used in a username-password pair. |
Secret Key | No |
Key used in combination with the access key to make programmatic requests to AWS. For example, wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY The access key is similar to the user name used in a user name-password pair. |
Profile Name | No |
You can store frequently used credentials and configuration settings in files. These files are divided into sections that are referenced by name. These sections are called profiles. Enter the profile name that contains the credentials and configuration settings that you want to use. |
Configuration for ActiveSpaces 3.x Channels
Field | Global Var? | Description |
---|---|---|
Realm Server URL | Yes | The URL at which the TIBCO BusinessEvents can connect to the TIBCO FTL realm server.
Default URL: http://localhost:8080 |
Grid Name | Yes | Name of the data grid to which the ActiveSpaces 3.x channel connects |
User Name | Yes | A valid user name for the TIBCO FTL realm server |
Password | Yes | The password assigned to the user name specified in UserName, for accessing the TIBCO FTL realm server |
Secondary | Yes | The URL of the secondary TIBCO FTL realm server. |
Use SSL | No | Check this box if you want to use secure socket layer (SSL) protocol while connecting to the TIBCO FTL realm server. If checked, the Trust Type and Identity fields are activated |
Trust Type | Yes | Specifies whether you want to use a trust file for SSL authentication |
Identity | No | The Identity field is activated if you have selected the Trust File option in the Trust Type dropdown. Browse to select the trust file from your system. |