The Is Page Flow parameter of the destination identifies the approach followed by destination for processing HTTP requests. If the
Is Page Flow parameter is set to true the HTTP request is processed using the Action Rule Function based approach otherwise Event based approach is used. This section explains the two different approaches for working with HTTP requests, and how to add an HTTP channel and destination.
RESTMessageSerializer, which is set while configuring the channel, maps HTTP requests to TIBCO BusinessEvents. HTTP headers and HTTP parameters in the GET method are mapped to similarly named event properties. When both parameters and headers are specified, parameters take precedence.
The transfer encoding (charset) in the
Content-Type header indicates what type of transformation is applied to the POST data (message body) to safely transfer content between sender and recipient. If the
Content-Type header is missing, UTF-8 is used as the default transfer encoding.
When you want the REST serializer to deserialize a GET request into an event with a payload, include the _payload_ request parameter. The string value of the
_payload_ parameter will always be used as payload in the event.
To send non-ASCII event properties in GET methods, use HTTP parameters. HTTP parameters are passed as the QueryString of the request URI, that is, the part of the URI that contains data to be passed to web applications.
To decode the QueryString, use either the URI Encoding or the body encoding. The body encoding is specified in the
contentType HTTP header. Select either the URI Encoding or Use Body Encoding for URI setting in the HTTP channel Advanced tab.
For example, the requestURI for the request
https://localhost:7000/Transport/Channel/StudentDestination is
/Transport/Channel/StudentDestination. TIBCO BusinessEvents engine maps the request with a destination having URI
/Transport/Channel/StudentDestination if it exists.
For example, the requestURI for the request
https://localhost:7000/Transport/Channel/StudentDestination is
/Transport/Channel/StudentDestination. TIBCO BusinessEvents engine maps the request with a destination having context path
/Transport/Channel/StudentDestination if it exists.
To configure an HTTPS (Secure) Connection Check the
SSL checkbox, click the
Configure SSL button, and complete the pop-up dialog settings. The server must authenticate to the client. In the Identity field, provide the location of the Server Identity File. (See
Task B).
To follow the action rule function based approach Check the Is Page Flow checkbox and specify the appropriate
Context Path and
Action Rule function for the destination. Specify the context path in the same format as the server would receive the
requestURI in the HTTP request.
To follow the event based approach In the
Serializer field select the appropriate serializer:
In the event based approach For receiving HTTP requests and sending responses, configure events in the usual way, and select an HTTP-based destination as the default destination.
In the action rule function based approach For example, in response to a POST request you might do the following:
In the event based approach For example, in response to a POST request you might do the following:
As another example, in response to a GET request you might do the following: