Which transports support public smart routing and how can we dedicate engines for inbound and outbound traffic?
Article ID: KB0081677
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | 6.X |
Description
Here are some basic rules related to public smart routing with BusinessConnect:
Issue/Introduction
Rules related to the use of Public Smart Routing with BusinessConnect
Environment
All environments
Resolution
1. You can use Public Smart Routing with the inbound HTTP/S/CA transports, the inbound File Poller, and the inbound SFTP and FTP client transports
2. You cannot use Public Smart Routing with the Gateway Server (GS) FTP and SFTP server plugins
3. You CAN DEDICATE specific engines to handle INBOUND HTTP traffic in a mixed HTTP/GS FTP/GS SFTP server environment. Make sure that the engines in the cluster marked for inbound HTTP request are not in the same cluster as the "No Matching Rules" cluster. The GS FTP Server and GS SFTP Server requests always go to the "No Matching Rules" Cluster.
4. You CANNOT DEDICATE engines for OUTBOUND traffic.
2. You cannot use Public Smart Routing with the Gateway Server (GS) FTP and SFTP server plugins
3. You CAN DEDICATE specific engines to handle INBOUND HTTP traffic in a mixed HTTP/GS FTP/GS SFTP server environment. Make sure that the engines in the cluster marked for inbound HTTP request are not in the same cluster as the "No Matching Rules" cluster. The GS FTP Server and GS SFTP Server requests always go to the "No Matching Rules" Cluster.
4. You CANNOT DEDICATE engines for OUTBOUND traffic.
Feedback
Yes
No
Powered by
