Technical Limitations Using External HTTP Load Balancer with the Marketing Server on OBIEE 10g
(Doc ID 949781.1)
Last updated on APRIL 14, 2020
Applies to:Siebel Marketing - Version 8.0  to 8.1.1  [Release V8]
Information in this document applies to any platform.
This document discusses the technical limitations to running Marketing jobs in a load balanced OBIEE environment, where multiple BI Presentation Servers are front-ended by an external HTTP load balancer. This document will also describe how to setup the integration to OBIEE from the CRM in order to bypass the load balancer and point directly to one BI Presentation Server for all marketing jobs.
It is currently within the future product roadmap to address the technical limitations and provide full support for a clustered and load-balanced Marketing Server.
The information discussed in this article affects users of Siebel Marketing Server (the segmentation engine) running on Oracle Business Intelligence Enterprise Edition 10g in clustered configurations where multiple BI Presentation Servers (BIPS) are used in conjunction with an external HTTP load-balancer and the Siebel Marketing application is configured to point to the load-balancer for Marketing jobs executed during a campaign load/launch operation. Examples of Marketing jobs would be PrepareCache, WriteListFiles, and UpdateCounts.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document