Use this transport to route messages to another service that executes on the local machine or on a remote Integration Server. The entire pipeline is submitted to the specified routing notification service. If you connect to a remote Integration Server, you should edit the assigned service of this routing notification and add a MAP step before the invoke step pub.remote:invoke, where you drop all unnecessary parameters from the pipeline so that the amount of data sent over the network is as small as possible. The IS Transport supports the Forward Confirm event feature. In case of $action set to 4 (Confirm event), the assigned service is called a second time. You can add pre- and post-processing steps to the pipeline if you wrap the service you want invoke and assign the wrapper service to the routing notification.