Routing Filters Index

Explains how to configure routing filters in a policy depending on, firstly, whether the client is using the Enterprise Gateway as a proxy or an endpoint, and secondly, whether service virtualization is required.

Use the Routing Wizard to auto-generate the filters required to route messages directly to a specified destination or using an HTTP proxy.

The Connection filter is responsible for sending messages to the target Web Service, potentially over a mutually authenticated channel.

This is the simplest filter to use to send a request to a target Web Service.

In cases where the Enterprise Gateway is deployed as a proxy, the URL received in the request line of the HTTP request can be used to route messages to the ultimate destination.

Force the Enterprise Gateway to return specific HTTP status codes in responses sent to clients.

Use this filter to send the request to a different path than was originally requested by the client.

Configure details of the machine hosting the target Web Service.

This filter is used to pass control up to a Servlet Application or Static Content Provider.

Download messages from a file transfer server.

Upload messages to a file transfer server for archive purposes.

Insert WS-Addressing information into a SOAP message.

Send a message to a messaging system using synchronous or asynchronous transfer modes.

Use WS-Addressing information contained in a SOAP message to route the message to its intended destination.

Write the current message contents to a file.

Send messages to an email recipient using an SMTP server.

Place messages on a TIBCO Enterprise Messaging Service queue or topic.

Place messages on a TIBCO Rendezvous queue or topic.

Passively listen on a network interface for response messages sent back to a client so that they can be logged.