Copyright © TIBCO Software Inc. All Rights Reserved |
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 Overview of Channels and Destinations.
Local channels are in memory; information in a local channel could be lost if the TIBCO BusinessEvents engine fails.
Global Var? (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). Select the driver for the type of channel you are configuring: 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. As a convenience, you can open the selected resource by clicking the underlined label. 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.Default is an empty string (defined in Global Variables). 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 TIBCO BusinessEvents can contact the Enterprise Message Service server.Example: tcp://localhost:7222 A valid username for the Enterprise Message Service server. 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. HTTP Server Type
• 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.
Copyright © TIBCO Software Inc. All Rights Reserved |