Campaigns Failing Due To FileSystem MisMatch In OBI And Marketing Environments (Doc ID 2086587.1)

Last updated on AUGUST 16, 2016

Applies to:

Siebel Marketing Server - Version 15.1 [IP2015] and later
Information in this document applies to any platform.

Symptoms

Environment:
-------------------
Product Type: Siebel Marketing Server
Version: 15.1 [IP2015]
OS platform: Microsoft Windows x64 (64-bit)
DB: Oracle Database - Enterprise Edition
Env type: Production

Statement of Issue:
-----------------------------
A user has a requirement to manually generate list files in OBI.

The OS user under which OBI is running doesn’t have write access to the Siebel filesystem directory (\\xxx\E122_ODEV-SiebelFS). Therefore, if FileSystem is set to the Siebel filesystem in instanceconfig.xml, the user expectedly gets an error when manually generating list files in OBI.

To avoid this error, FileSystem has been changed to a directory that OBI can write to (\\xxx\E122_ODEV-SiebelFS\Marketing).

However, as a result, campaign loads from Siebel are failing. Marketing File System is set to \\xxx\E122_ODEV-SiebelFS for the Workflow Process Manager. OBI writes the list file to FileSystem + Marketing\EAI and Siebel looks for the file in Marketing File System + Marketing\EAI (\\xxx\E122_ODEV-SiebelFS\Marketing\EAI). The file isn’t located here and the load fails.

Expected Behavior:
---------------------------
A user can manually generate list files in OBI and campaign loads from Siebel complete correctly.

Actual Behavior:
-----------------------
A user can manually generate list files in OBI, but campaign loads from Siebel don’t complete correctly.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms