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. |