Chapter 2 Working With Channels and Destinations : Channel Resource Reference

Channel Resource Reference
Channels allow BusinessEvents to listen to and send out messages. Channels contain destinations. After you add a destination to a channel, you can no longer change the driver type.
You can configure channels of three types, using the appropriate driver:
TIBCO Rendezvous channels  connect TIBCO BusinessEvents to TIBCO Rendezvous
JMS channels  connect TIBCO BusinessEvents to TIBCO Enterprise Message Service providers.
Local channels  connect multiple rule sessions at runtime (used in test environments only.
Configuration
The Configuration tab has the following fields.
The name to appear as the label for the resource. Names follow Java variable naming restrictions. Do not use any reserved words. See the section Identifiers (Names) in TIBCO BusinessEvents Language Reference.
Method of Configuration
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 keywords or other reserved words listed in the section Keywords and other Reserved Words in the TIBCO BusinessEvents Language Reference, and they cannot use spaces.
Properties Select Properties to configure this channel resource using properties. See Configuration for TIBCO Rendezvous Channels and Configuration for JMS Channels.
If you choose Resource as the method of configuration, browse to and select the resource you want to use.
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.
The network over which Rendezvous sends messages. In most cases you can leave this field empty, accepting the default value. For more information about the network parameter, see TIBCO Rendezvous Administration.
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.
The URL at which BusinessEvents can contact the Enterprise Message Service server.
Example: tcp://localhost:7222
The password assigned to the username, above, for the purpose of accessing the Enterprise Message Service server.
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.