Adding an HTTP Channel and Destination
In this task you configure an HTTP channel with one destination. The AllOps destination listens for messages that come from HTTP forms embedded in the project’s readme.html file.
Example projects use the HTTP channel because it does not require use of any external software. If you have TIBCO ActiveMatrix BusinessWorks, TIBCO Enterprise Message Service, TIBCO Rendezvous, or other source for messages you can experiment with adding different types of channels.
Learning Points
- What are channels and destinations?
- Messages enter and leave the system through channels. You create destinations within a channel to define the message sources and sinks. Typically,
events are created using data in incoming messages; outgoing messages are created using data from events. Later in the tutorial, you will set up the relationship between these destinations and the event types that they listen to by default.
Note that in this tutorial outbound messages are simply sent to the console, so there are no outbound destinations.
- How are channels and destinations created?
- You create channels and destinations at design-time, as explained below. When you are planning TIBCO BusinessEvents projects, you would consider the incoming and outgoing messages for your project, and then define the channels, destinations, and the corresponding event types — outbound events are transformed into appropriate messages, and inbound messages are transformed into events of a specified type.
- Why Use Shared Resources?
- Shared resources are generally used in channels to configure communication with some external system such as a database server or JMS server. You can configure the connection once and use it in multiple places. If some configuration has to be changed, you just have to change it in one place.
Copyright © Cloud Software Group, Inc. All rights reserved.