Preferred Routing

TIBCO API Exchange Gateway supports routing of the client request based on preferred routing key. To use preferred routing, specify a preferred routing key for a partner operation as a facade access.

TIBCO API Exchange Gateway processes a facade operation request from the partner for preferred routing, as follows:

• If the Preferred Routing Key is not blank, preferred routing is enabled and the Core Engine uses this value as the routing key. Make sure to configure a routing key which matches the preferred routing key.
• If the Preferred Routing Key is blank, the Core Engine does not enable preferred routing.
• To select the target operation for the facade operation request, configure the preferred routing key on the Routing tab of the Config UI.
  • If the preferred routing key is not configured on the Routing tab, the default routing key is used.
  • If the default routing key is not configured, an error such as Route not found for transaction ID transaction_ID is returned.

• Use Case for Preferred Routing
  Using plan type for preferred routing.
• Overriding Preferred Routing Key using XSLT
  To change the value of the preferred routing key using the XSLT file, follow these steps:

Copyright © Cloud Software Group, Inc. All rights reserved.