Channels and Destinations : Channel Resource Reference

Channel Resource Reference
Channels allow BusinessEvents to listen to and send out messages. Channels contain destinations.
You can configure channels of different types, using the appropriate driver. See Overview of Channels and Destinations.
Wizard and Configuration Section
The Wizard and the Configuration section have the following fields.
(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. See Identifiers (Names).
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 words listed in Keywords and Other Reserved Words.
Properties  Select Properties to configure this channel resource using properties. See:
If you choose Resource as the method of configuration, the Resource field appears. 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. 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.
Default is tcp:7500 (defined in Global Variables).
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.
TOMCAT  is a J2EE servlet container. Use TOMCAT if you need to host servlets.
BUILT-IN  is a good choice if the need is to send and receive many small requests.