Campaign | partitions | partition[n] | server

Properties in this category control IBM® Campaign server optimization for each partition.

Campaign|partitions|partition[n]|server|optimization

This property specifies a default value for the maximum amount of system virtual memory to use when running a flowchart. You can increase the value to improve performance or decrease the value to limit the resources used by a single flowchart. The maximum value is 4095 MB. If you enter a larger value, Campaign automatically limits it to 4095 MB.

Set a value equal to (80% x available memory) / (number of expected concurrent flowcharts). For example:

maxVirtualMemory is a global configuration setting. To override the value for a specific flowchart, open the flowchart in Edit mode, select Advanced Settings from the Admin menu

, and change the IBM Campaign Virtual Memory Usage value on the Server Optimization tab.

Campaign|partitions|partition[n]|server|optimization

This property specifies whether IBM® Campaign tries to perform as many operations as possible in the database instead of in the Campaign server.

Setting the value to TRUE can improve flowchart performance. When the value is TRUE, IBM® Campaign avoids pulling the ID lists if possible.

When the value is FALSE, IBM® Campaign maintains lists of IDs in the IBM® Campaign server at all times.

Campaign | partitions | partition[n] | server | optimization

This property specifies the number of operating system threads that are cached by the server process (unica_acsvr) for reuse. By default, the cache is disabled.

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

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

0 (zero), which disables the cache

Campaign|partitions|partition[n]|server|optimization

This property determines the number of bytes allocated for each thread's stack. Do not change this property except under guidance from IBM®. The minimum value is 128 K. The maximum value is 8 MB.

Campaign|partitions|partition[n]|server|optimization

This property defines the list of data sources where persistent Segment temp tables can be created by the Create Seg process. This list is comma-separated. By default, this property is blank.

No default value defined.

Campaign|partitions|partition[n]|server|optimization

To improve performance, set this property to TRUE. When this property is TRUE, strategic segments create Segment temp tables in the data source rather than creating binary files on the IBM® Campaign server. You must specify at least one data source in the Create Segment (CreateSeg) process configuration dialog to hold the temp tables. Also, you must set the AllowTempTables property to TRUE to enable the creation of temporary tables in a data source.

Campaign|partitions|partition[n]|server|optimization

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 that is 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.