When you enable a database load utility, instead of holding all contact and response history in memory before writing to the staging tables, runtime writes the data to a staging file. You define the location of the directory containing the staging files with the externalLoaderStagingDirectory property. This directory contains several subdirectories. The first subdirectory is the runtime instance directory, which contains the contactHist and respHist directories. The contactHist and respHist directories contain uniquely named subdirectories in the format of audienceLevelName. uniqueID. currentState, which contain the staging files.
Contents of directory ready to be written to the database. You should rename a directory from ATTN or ERROR to RERUN after you have corrected the problem.You can define the runtime instance directory by defining the interact.runtime.instance.name JVM property in the application server startup script. For example, you could add -Dinteract.runtime.instance.name=instance2 to your web application server startup script. If not set, the default name is DefaultInteractRuntimeInstance.
The samples directory contains sample files to assist you with writing your own database load utility control files.
IBM Unica Interact
8.5.0
|
Copyright IBM Corporation 2011. All Rights Reserved.
|
For more information, see our support and community site: Customer Central
|
|