With the connections defined we can start to create the filtered connection, which will look like:

It is worth noting that the integration is two-way; this is because we want to show a return value that clearly represents an outcome: having succeeded or failing to pass through the filter. But additionally, ICS will not allow one-way integrations to have a filter. You can verify this by creating a version of our source connection with a modified WSDL where, wsdl:message name="FlightInfoUpdateResponseMsg" and <wsdl:output> elements are removed, and then trying to construct the integration we are about to describe; you will then see that the option to incorporate a filter is not available.

This constraint is based on the possibility that, when filters are used for routes, one endpoint may return a result and the other does not, in which case what do you do? Enforcing a return solves the problem in terms of consistency, even if you then define the return...