Configuring Connections to the Marketing Content Server

Oracle Marketing Segmentation handles segmentation, which involves dividing a target audience into different segments given different criteria based on the subject areas.

When a segment is ready, users create lists of the contacts and accounts that satisfy the criteria for the segment. Users then specify whether to store the generated lists on the file system, in a database, or on a specified Content Server.

For users to store the lists on a Content Server, you as the administrator must configure the connection to the Content Server by specifying the appropriate URL and other values in the instanceconfig.xml file.

Use various elements in the instanceconfig.xml file to configure settings for the connection to the Marketing Content Server.

  1. Open the instanceconfig.xml file for editing, at:

    BI_DOMAIN/config/fmwconfig/biconfig/OBIPS

  2. Locate the section in which you must add the elements that are described in the following list:
    • URL: Specifies the address of the content server machine.

    • SocketTimeoutSec: Specifies the number of seconds that the socket waits for the Content Server to respond while transferring records. The default value is 60. There is no minimum or maximum value.

    • FileSizeMB: Specifies the size in megabytes of files that are generated during ListGeneration and inserted into the Content Server. The default is 10. The minimum size is 1MB and the maximum size is 50MB.

  3. Include the elements and their ancestor elements as appropriate, as shown in the following example:
    <ServerInstance>
     <Marketing>
      <ContentServer>
        <URL>myhost.com:6666/st1b2rep/idcplg</URL>
        <SocketTimeoutSec>120</SocketTimeoutSec>
        <FileSizeMB>5</FileSizeMB>
      </ContentServer>
     </Marketing>
    </ServerInstance>
    

    You cannot specify values for user name and password in the instanceconfig.xml file. Instead you specify values stored securely within the central credentials wallet, along with all other user names and passwords.

  4. Save your changes and close the file.
  5. Restart Oracle Business Intelligence.