![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
•
•
•
• HTTP/S HTTP/S is supported for almost all protocols. Many message packaging and delivery standards such as AS2, S/MIME, and SOAP are also based on HTTP/S and are supported.
• Inbound File Poller This transport is only supported for limited protocols, such as EZComm and EDI.
• FTP Server This transport is protocol specific and does not support inbound document smart routing.
• PartnerExpress This transport is protocol specific and does not support inbound document smart routing.
• TCM Server This transport is protocol specific and does not support inbound document smart routing.
• SSH Server This transport is protocol specific and does not support inbound document smart routing.Figure 18 shows three message queues processed by three clusters that consist of six runtime engines, where three of these engines are simultaneously participating in two clusters.Figure 18 Message Queues and Clusters
• Email size is less than 1MB (Content_Size less than 1.000.0 bytes)
• The sender address is john@acme.com (Sender = john@acme.com)
• Attributes These are objects of a given type that extends the operand implementation by adding a name, default value, and transport property.
• Operators These objects determine the relationship between two (or more) operands.
−
−
• Operands These are objects that are a string, numeric, or Boolean.In this case, Smart Routing will occur when the file size is larger than 1KB and client authentication is not required.
• HTTPS or HTTPS_CA: create a rule for HTTP and use the expression Secure_SSL = true
• FTPS: create a rule for FTP and use the expression Secure_SSL = true
• Any HTTP transport (HTTP/S/CA) and messages which are larger than 2MB: create a rule for the transport HTTP and use the expression
Content_Size greater_than 2,097,152 bytes
• You will assign servers to fault tolerant groups using the procedure described in TIBCO BusinessConnect Interior Server Administration, Enable Service.Figure 19 Server Group AssignmentInbound messages will be delivered to the cluster that is defined by the first matching rule. In the example in Figure 19, there are the following defined rules for the existing clusters:If an inbound message comes in that corresponds to the rules
Sender = "john@acme.com"
and
Content_Size less_than 1000.0 bytes,
the following will happen:
• If the rule Sender = "john@acme.com" comes first and is true, the message will be assigned to the cluster AS1 Email.
• If the rule Content_Size less_than 1000.0 bytes comes first and is true, then the cluster HTTP will be used.Any message may be evaluated as true for more than one rule and, therefore, the first matching rule will decide the group assignment.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |