Siebel Marketing Installation and Administration Guide > Installing and Administering Segmentation and List Generation > Setting Up Marketing Module Parameters in Siebel Analytics >

Administering Configuration Keys for the Marketing Module

Settings for the segmentation and list generation functions of the Analytics Web Server are contained in a configuration file named instanceconfig.xml. The configuration keys in this file control path names for the Marketing File System, logging levels, and other properties. Table 8 shows some of the configuration keys that apply to the Marketing module. For a complete explanation of configuration keys and how to edit the instanceconfig.xml file, see "Making Siebel Analytics Web Configuration Changes" in Oracle Business Intelligence Web Administration Guide.

Table 8. Marketing Parameter Default Settings
Configuration Key
Default Value



Login credential of the Administrative Analytics Server user under which Marketing runs its EXECUTE PHYSICAL queries. These include queries to delete cache result sets, delete saved result sets, delete header saved result sets and insert header result set records.


SADMIN (Encrypted)

Password credential of the Administrative Analytics Server user under which Marketing runs its EXECUTE PHYSICAL queries. The password is encrypted and can be retrieved by posting the following URL as an Administrative Web user:




Maximum number of database cache entries.



Maximum time that a database cache entry can exist before it is expired and removed.



Replaces control characters in the column data with spaces. If this parameter is set to true, control characters in the column data whose ASCII value is less than 32, such as the carriage return and the line feed characters, are replaced by spaces before writing out to any list files.



Enables or disables the hyperlink to the profile dashboard from counts in the Segment Designer and Segment Tree Designer.



Character set encoding of the List Format files generated.



File system path used by Siebel Marketing to store output list files. This path must be accessible to the Analytics Web Server, must have write permissions for the user under which Analytics Web Server is started, and must end with a backslash.

The Marketing transactional application must use the same location as the Marketing File System. In the following situations, Analytics Web Server must have access to the path specified in the MarketingFileSystem parameter:

  • In an environment in which Siebel Server and Analytics Web Server are running on the same platform (homogenous), this path matches the Marketing File System server parameter.
  • In an environment in which Siebel Server and Analytics Web Server are not running on the same platform (heterogeneous), the Siebel File System must be made visible to Analytics Web Server by running a third-party application (such as Samba) where the Siebel File System resides and by exporting this path such as in the following example:

    /export/home/Siebel/filesystem (Analytics Web running on UNIX)



Amount of debugging information saved for each job.



Maximum number of jobs in the job history log. After the maximum is reached, the oldest jobs are expired and removed.



Duration between successive checks on the status of a Marketing job run from the User Interface. The jobs include Segment Counts, Segment Tree Counts, Saved Result Set Creation (in the Segments user interface or the Segment Trees user interface) and Purge and List Format Preview/List Generation. The wait-refresh cycles keep the browser from timing out while waiting for the jobs to complete.



File system path where preview and output list files are written.



Number of default records shown in the List Format Designer when a user selects Generate Preview. This parameter can be overridden by the end users in the Preview user interface by entering a different preview size in the Preview Parameters dialog box.



Controls writing of the Byte Order Mark (BOM) characters at the beginning of list files. Typically applications see BOM characters to identify the encoding of the data.

  • When set to true, BOM characters are inserted at the start of the list file, identifying the character encoding used in the file.
  • When set to false, the BOM characters are not written.
  • If you set the character set encoding to ANSI then no BOM is written.



Applicable only when files are being written out in the Delimited format and when a Text Qualifier is specified.

  • When the default value is true, the column headers are wrapped using the text qualifiers specified in the List Format Options tab.
  • When the default value is false, column headers are not wrapped.
Siebel Marketing Installation and Administration Guide Copyright © 2006, Oracle. All rights reserved.