Configure Advanced Routing

You can enable the use of advanced routing to control how tasks are distributed across servers. Advanced routing is recommended for environments with advanced configurations, such as distributed installations or segregated user communities.

To configure advanced routing, text strings called hints are defined in the bibus » dashboard » routingHints property. If you have servers that are optimized for use by different user groups, you can add hints to the group objects to enable routing to specific servers. For example, give the Sales group object a hint of GOSales, and the Finance user group a hint value of Finance.

The bibus » routingTableEntry object contains rules that can be matched with the bibus » routingHintObject. The bibus » routingTableEntry object contains the rule property, which is made up of the hints property of the bibus » routingRuleObject object. Using the example given above, a bibus » routingTableEntry for the Sales group lists SalesServers as the server group to handle a request from that group, and the FinanceServers as the server group to handle requests from the Finance group.

It is possible to assign multiple hints to one object. Hint values identify a set of objects: all objects of the same class with the same hint value. For example, a package could have hints GOSales and PublicPackage. The package is thus a member of two sets: packages with hint equal to GOSales, and packages with hint equal to PublicPackage. If there are several packages with hint PublicPackage, one routing rule could be defined to do specific routing for PublicPackage package requests for the Sales group, another routing rule could route requests for the Finance group, and a third more general rule could be defined to route all other requests for packages with hint publicPackage.

You must have server groups defined to use advanced routing. For information, see Define Server Groups.