Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Deployment Configuration : Step 3: Configuring Smart Routing

Step 3: Configuring Smart Routing
Public smart routing is used to better distribute the workloads and alleviate the likelihood of bottlenecks while receiving inbound documents. Multiple clusters can be introduced to handle a variety of workloads separately. A rule-based routing mechanism based on a combination of configurable conditions and predefined set of criteria is used to make decisions so that it can dispatch the workloads to the best fitting cluster for processing.
In order to configure public transports and use public smart routing, you need to configure clusters of machines based on the transport type, define conditions (rules) for these clusters, and then map the clusters into groups. For more information about rule based routing, see TIBCO BusinessConnect Concepts, Public Smart Routing.
Configuring Smart Routing Rules
To enable or disable an inbound transport for the installation, do the following:
1.
Expand Application Management > BusinessConnect > Configuration.
2.
Click the BusinessConnect link in the Configuration Builder panel.
3.
Select the Public Process Configuration tab.
 
4.
Click Add.
5.
6.
Click OK.
The dialog New Rule with the selected transport type appears:
7.
The value is not case sensitive
8.
The defined rules will be displayed in the field Rule Expression.
Rule Options for the HTTP/S, HTTPCA, and AS2_HTTP/S Transports
Defining Rules Using Regular Expressions
The supplied examples refer to TIBCO BusinessConnect™ Services Plug-in (EZComm).
Request_URI matches "/EZComm": using the HTTP rule type, create a rule for the Request_URI attribute, use the "matches" operator, specify "/EZComm" for the value.
Query_String matches ".*fromTp=Partner.*": using the HTTP rule type, create a rule for the Query_String attribute, use the "matches" operator, specify ".*fromTp=Partner.*" for the value
Query_String matches ".*operationID=BC%2F1\.0%2FNotify.*": using the HTTP rule type, create a rule for the Query_String attribute, use the "matches" operator, specify ".*operationID=BC%2F1\.0%2FNotify.*" for the value
Rule Options for the FTP/S and SSHFTP Transports
Defining Rules Using Regular Expressions
The supplied example refer to TIBCO BusinessConnect Services Plug-in (EZComm).
(Protocol matches "EZComm") and (From_Partner matches "MyPartner"): using the SSHFTP rule type, create a rule for the Protocol attribute, use the "matches" operator, specify "/EZComm" for the value, add a new condition for the From_Partner attribute, use the "matches" operator, specify "MyPartner" for the value
Rule Options for the File Transport
 
Rule Options for the Email and AS1_Email Transports
9.
Figure 2 Listed Clusters
The numbers in front of the rules represent their precedence. Once the rules are added and the routing conditions defined, you can group (map) them into fault tolerant groups using the selected criteria.
Map Clusters
Clusters are mapped using the configured rules into fault tolerance groups. The Map Clusters window allows you to list the configured clusters by:
Cluster maps can be edited as follows:
1.
Click Map Clusters.
You will notice that, in addition to all the clusters you have defined, there is one additional cluster called NO MATCHING RULES. By default, all service instances are added to this cluster and later can be assigned to another cluster.
Figure 3 Map Clusters Dialog
To read more about this cluster, see TIBCO BusinessConnect Concepts, NO MATCHING RULES.
2.
From the Group by list, select the criteria by which you want to group the server clusters:
Load Balanced Cluster Name (Rule Id)   Clusters are grouped by the cluster name defined for load balancing
Assigned Fault Tolerant Group   Clusters are grouped in the previously assigned fault tolerant groups
Service Instance   Clusters are grouped by the existing service instances
None   If selected, all load balanced clusters, fault tolerant groups, and service instances are listed without grouping.
Regardless of the grouping on the screen, you will be able to add the previously assigned fault tolerant groups of servers to any of the clusters.
Assigning a Fault Tolerance Group to a Cluster
After you import a .csx file that contains the configured public Smart Routing rules, the clusters are still not mapped to any of the fault tolerant groups. You must add again the fault tolerant group to the cluster.
To assign a fault tolerant group to a cluster (define rules for this group):
1.
The Edit Cluster Map dialog appears.
2.
3.
Click Add to Cluster Map.
The fault tolerant groups to which you assigned the specified cluster map are now listed under Assigned Fault Tolerant Groups.
You can remove any group(s) that you want by checking their check boxes and clicking Remove From Cluster Map.
4.
Click Save.
This will list the fault tolerant groups you have assigned under the appropriate cluster.
Clusters have been mapped to two fault tolerant groups (domain.BCFTGROUP.A and domain.BCFTGROUP.B), and also to two different service instances (machine1 - Interior Server and machine2 - Interior Server).
5.
View the assigned clusters by the assigned fault tolerant groups (Figure 4), by the load balanced cluster name (Figure 5), or by service instance
Figure 4 Assigned Fault Tolerant Groups
Figure 5 Load Balanced Cluster Name
Figure 6 Service Instance
Notice that the cluster NO MATCHING RULES appears in both fault tolerant groups and on both service instances. Notice also the cluster HTTP appears in two fault tolerant groups and on two service instances. This means that ClusterFTPS, AS1Email, and File will be processed only by one of the fault tolerant groups and on one of the instances, while the cluster HTTP will be processed on both the group A and B and on both instances of the Interior Server.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved