Campaign | partitions | partition[n] | server

Properties in this category control Campaign server optimization for partitions.

The maxVirtualMemory property specifies a default setting for a new Campaign flowchart’s Affinium Virtual Memory Usage property, configurable for each flowchart through the client-side Advanced Settings window. The units are in megabytes.

The useInDbOptimization property specifies whether Campaign tries to perform as many operations as possible in the database instead of in the Campaign server.

If the value is no, Campaign maintains lists of IDs in the Campaign server at all times.

If the value is yes, Campaign avoids pulling the ID lists if possible.

The maxReuseThreads property specifies the number of operating system threads cached by the server process (unica_acsvr) for reuse. By default, the cache is disabled as this property is set to 0.

It is a best practice to use the cache when you want to reduce the overhead of thread allocation, or with operating systems that can exhibit an inability to release threads when asked to do so by an application.

Note that when the maxReuseThreads property is set to a non-zero value, it should be greater than or equal to the value of MaxQueryThreads.

0 (zero), which disables the cache

The threadStackSize determines the number of bytes allocated for each thread's stack. This property should be changed only under guidance from IBM®. The minimum value is 128K. The maximum value is 8MB.

The tempTableDataSourcesForSegments property defines the list of data sources where persistent Segment temp tables should be created by the Create Seg process. This list is comma-separated.

By default, this property is blank.

No default value defined.

When this option is set to TRUE, strategic segments will not create binary files on the Campaign server; instead, strategic segments create Segment temp tables in the data source. When the value is set to TRUE, at least one data source must be specified in the Create Seg process configuration.

The default value (TRUE) forces creation of a parameterized offer attribute view in a Mail List process whose offers are assigned from Optimize. A value of FALSE causes the parameterized offer attribute view to be created only if the Mail List exports at least one parameterized offer attribute.

If this value is set to FALSE, a Mail List process configured to get its input from an Extract process (whose source is an Optimize session) may write NULL values for EffectiveDate and ExpirationDate into the UA_Treatment table, even when the offer includes parameterized Effective and Expiration Dates. In this case, set it back to TRUE.