Creating single virtual domain for Siebel and OBIEE

If Siebel CRM and Oracle BI EE are running on two different Servers (which should be the case for most implementations), then the embedded Oracle BI screens may not function properly for all actions such as, opening the properties for List Formats, requiring a second click for editing within the formula editor of the segment designer due some issues with cross-site scripting. This behavior is also documented within the following SR: avoid UI navigation issues associated to Siebel Marketing – OpenUI integrated to OBI (2008422.1) and within the Official documentation of the Installation guide:

Since these various issue are caused by some cross-site scripting, the workaround is to pretend to the client that Siebel and Oracle BI are running on the same host, hence creating a single virtual domain for Siebel and OBIEE.

This can be achieved by configuring a proxy reverse setting on the HTTP Web Server where Siebel web extensions are running. This proxy reverse configuration will exchange the hostname of OBIEE e.g. with the hostname of the Siebel host e.g.

Within the support note of the SR (2008422.1) OHS is used for this proxy reverse configuration. The following diagram shows the updated request flow for the single virtual domain:

A short step-by-step guide for the Workaround using OHS can be found here.


Instantiation of Export List for Siebel Campaigns

Once a direct mail Campaign is launched/executed in Siebel, a Export List is instantiated based on the Export List format (defined in OBIEE and typically containing the Campaign Members), writing the file to the shared marketing file system for distributing to external Agencies.

This progress and completion of the process between OBIEE writing the file and Siebel loading the file via the Integration Object to the Campaign Member Table S_CAMP_CON can also be check from the Task Log Applet of the Campaign :


While the Oracle BI system will check the current campaign Members (at point of launching the Campaign) and associate the data according to the export list format definition, not all scenarios might return data. E.g. a Export list may join the Campaign Members with a Asset, but in case of a small Campaign maybe none of the selected Members might own a Asset resulting in zero Records. In this no(zero) records is the correct result of the Export List. This is also displayed as a Warning in the Task Log Applet:


However, a Bug exists (3-12931858661 : List Export formats in Marketing Segmentation behave differently when there is no data) in the current release of Oracle BI (OBIEE) for this process, as a file containing zero Records is not written as a file (no file created) leading to a Error in Siebel instead:


Since the Issue is with Oracle BI this can also be re-produced within the Oracle BI instance. When clicking the Generate Preview button a error Message is displayed in the List Format designer, informing that no file has been created:


Which is also logged in the Administration of Marketing Jobs view:

The Workaround

To enforce the generation of Export files, even in case of zero records the XML definition of the Export List needs to be changed by adding a header / footer XML tag.

When creating a new Export list the XML definition does not contain a header / footer XML Tag when clicking the “Get XML” Button:

To add a header / footer Tag to the XML definition of the Export list, one needs to just click on the Header and Footer Tab and then click the “Set XML” Button resulting in a header / footer Tag in the XML definition:

This header/ footer Tag will ensure that a Export file is always written to the shared Marketing file system. The preview looks then like the following: