The Routing Service
All of the action associated with a particular routing rule is encompassed within its routing service. The routing service executes the pre-processing service specified by the rule (if any), invokes the transport service, which delivers the document to a specified destination, and then executes the post-processing service specified by the rule (if any).
The following example shows the contents of a routing service. In this example, the routing service invokes a pre-processing service (TStamp) and then submits the document to the transport service (OutboundProcess).
The Partner Manager automatically generates a routing service when you create a routing rule. You do not build routing services manually, although you can use Designer to edit the services that the Partner Manager builds.
With respect to routing services, keep the following points in mind:
You can use
Designer to view the contents of a routing service.
You can use
Designer to incorporate additional pre- or post-processing steps into the routing service; however, you must insert your changes after the MAP step that appears at the top of the flow. For additional information about adding steps to a routing service, see
Editing a Routing Service.
You must not rename a routing service after you create a routing rule. Doing so will cause the routing rule to fail at run time because the Partner Manager will not be able to locate the service named in the routing rule.
Note:
If the routing rule contains a wildcard character for the Receiver or Message Type, the routing service name will have “WildCard” in the name, instead of “*”.
