Routing Key using XSLT
If you want to use a custom (non-default) routing key to route a facade request to an appropriate target operation or target operation group, follow these main steps:
To derive a routing key, define a XSLT file with routingKey element tag and upload this XSLT file in the ProcessBody transform field for a facade operation configuration. In such a case, the incoming facade operation request is parsed as per the defined XSLT file and a routing key is returned. After the routing key is populated from the transformation, the Core Engine checks the routing key configuration to determine the target operation or target operation group for a facade operation request. The routing key configuration contains the routing key, the facade operation name, and the target operation name or target operation group name and is configured in the Routing tab of the Config UI. See How to Derive and Configure Routing Key for details.