|Bookshelf Home | Contents | Index | PDF|
To prevent problems with campaign loading, make sure that the Analytics Web Server service and Siebel Server service are running on an admin account that has read and write access to the directories used by the Marketing File System. In Windows, these services default to running under the localsystem account, which can not access the Marketing File System because it is not a recognized user across the network.
For segmentation and list generation, access to the Marketing File System is shared between the Siebel Server and the Analytics Web Server. If the Siebel Server and Analytics Web Server are installed on a combination of UNIX and MS Windows operating systems (heterogeneous environment), the Marketing File System must be configured for sharing across environments.
Siebel Marketing can be installed and operated in environments that use a combination of UNIX and Windows operating systems, but with some restrictions. The server components that use the Marketing File System need to be on the same operating system, otherwise the difference in path name syntax prevents them from finding files. Analytics Web Server must have visibility and write permissions to the Marketing File System. In a mixed (heterogeneous) environment, you may have to run a third-party application such as Samba to access the Marketing File System across different platforms.
Analytics Web Server uses the MarketingFileSystem parameter to identify the location to which it writes out generated list files. This parameter on the Analytics Web Server points to the same path as the Marketing File System parameter on the Marketing Component Group. However, the path syntax should correspond to the platform on which the Analytics Web Server is running.
You could export this file system path to be visible on MS Windows by running a third-party application such as Samba on the UNIX machine. In this example, the parameters would be set as shown in the following list:
If the Communications server component and the Workflow server component are not on the same operating system, you need to change the Marketing File System for Communications Outbound Manager server parameter. This enables the workflow process manager component to use the path syntax that corresponds to the operating system on which the Communication Outbound Manger is running.
|Siebel Marketing Installation and Administration Guide||Copyright © 2006, Oracle. All rights reserved.|