Connection Filters Index

This tutorial explains how to configure routing filters within a policy depending on, first of all, whether the client is using the Enterprise Gateway as a proxy or an endpoint, and secondly, whether service virtualization is required or not.

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

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

Configure details of the machine hosting the 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.

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

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

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

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

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

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

Insert WS-Addressing information into a SOAP message.

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

Send messages to an email recipient via an SMTP server.

Upload messages to an FTP server for archival purposes.

Place messages on a TIBCO Rendezvous queue or topic.

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

Write the current message contents to a file.