Campaign | partitions | partition[n] | server

Note: This category is not related to HCL Contact Optimization.

maxVirtualMemory

Configuration category

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

Description

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:

If available virtual memory on server = 32 GB
Number of concurrent flowcharts = 10
Set virtual Memory = ( 80 % x 32 ) / 10 = approximately 2.5 GB / flowchart

Default value

128 (MB)

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 Tiny person, pencil, and circle, with menu arrow icon , and change the HCL Campaign Virtual Memory Usage value on the Server Optimization tab.

Screen capture of Server Optimization tab

useInDbOptimization

Configuration category

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

Description

This property specifies whether HCL 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, HCL Campaign avoids pulling the ID lists if possible.

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

Default value

FALSE

Valid Values

TRUE | FALSE

maxReuseThreads

Configuration category

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

Description

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.

Default value

0 (zero), which disables the cache

threadStackSize

Configuration category: Campaign|partitions|partition[n]|server|optimization
Description: 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.
Default value: 1048576

tempTableDataSourcesForSegments

Configuration category: Campaign|partitions|partition[n]|server|optimization
Description: 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.
Default value: No default value defined.

doNotCreateServerBinFile

Configuration category: Campaign|partitions|partition[n]|server|optimization
Description: 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 HCL 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.
Default value: FALSE
Valid Values: TRUE | FALSE

forceViewForPreOptDates

Configuration category

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

Description

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.

Default value

TRUE

Valid Values

TRUE | FALSE

httpCompressionForResponseLength

Configuration category

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

Description

This property enables and configures compression for HTTP responses from the HCL Campaign web application to the client browser for flowchart-specific messages. The Campaign web application reads this property only once for each partition. If you modify this property, you must restart the web application for the change to take effect.

Compression can improve page load and interaction times by reducing the amount of data that is sent over HTTP.

All responses that have a data length greater than or equal to the httpCompressionForResponseLength value (in KB) are candidates for compression. Any other responses are not compressed.

Compression reduces network transfer, but it requires resources on the server side. Therefore, compression makes sense only for large amounts of data, when sufficient server-side resources are available. If you typically have network delays that can slow large data transfers, you can analyze how much time it takes to load a given amount of data. For example, suppose that some of your HTTP requests are <100 KB in size, but most are 300 to 500 KB. In this case, you would increase the value of this property to 500 KB so that only responses >= 500 KB in size are compressed.

To disable compression, set the value to 0.

Default value

100 (KB)

Valid Values

0 (disables compression) or higher