Topology Considerations for Siebel Email Response

Processing inbound email messages makes more demands on server resources, particularly CPU usage levels, than processing outbound messages.

Processing of inbound messages associated with a single response group must be handled on a single computer.

If inbound message volume warrants it and if multiple server computers are available to run CommInboundRcvr, CommInboundProcessor, and other components, then consider running CommInboundRcvr and CommInboundProcessor on separate computers (or computers) from other Communications Server components. Topology options for these component are different for real-time and nonreal-time processing. For more information about CommInboundRcvr and CommInboundProcessor, see Siebel Email Administration Guide.

Combining processing of messages for multiple email accounts in a single response group can make processing of inbound messages more efficient. However, if message volume is expected to grow, then limiting the number of email accounts processed by each response group will give you more flexibility to distribute processing across multiple servers, and thereby avoid processing bottlenecks.