For this example project, you will add an HTTP channel and destination.
Procedure
-
Right-click the
Channels folder and select
.
You will see the New Channel Wizard.
-
Add information to the following fields:
-
In the Channel Name field, type
HTTP.
Note: This value is case sensitive. Ensure that you use all capital letters.
-
In the Description field, type
An HTTP channel.
-
In the Driver Type field, select
HTTP.
-
Click
Finish.
You will see the Channel editor.
Note: You cannot change the resource name in the editor after you click Finish in the new resource wizard. (You can change the description, however.) You can later rename the resource using a shortcut menu refactoring option.
-
In the Resource field, browse to and select the HTTP connection resource you created.
Only valid shared resources for the current resource display.
-
In the Destinations section, click
Add and name the destination
AllOps. Leave all other fields set to their default values.
Note: Provided Examples Requirements:
- HTTP and
AllOps are required names for examples. The readme.html uses the
AllOps destination in its embedded forms.
- The HTTP connection port must match the readme port .
-
Save and close the resource.
Tip:
- Default Events
- All messages arriving at a destination are transformed to the destination’s default event, unless the message specifies a different event. Adding a default event is not necessary for example projects, because the
readme.html, which starts an HTTP channel, specifies the event to use.
Adding a default event, however, does stop a warning sign from appearing! — this warning draws your attention to the fact that a destination does not have a default event, but does not indicate an error.
Default events and destinations are explained in the next step.
Result
Now you have built a channel and a destination within that channel to listen for messages. The next step is to create some events.
Copyright © TIBCO Software Inc. All Rights Reserved.