Configure database load utility

Optimize uses the same configuration settings as Campaign for implementing a database load utility. If you have configured Campaign to work with a database load utility, you have configured Optimize to use the same commands. Similarly, if you configure Optimize to work with a database load utility, you are configuring Campaign to work with a database load utility. Each assumes a different root directory, /Campaign for Campaign or /Optimize for Optimize, so you can specify different commands in the loader command and template files.

A large component of an optimization session is reading data from the PCT and writing data to the OCT. Configuring a database load utility improves the performance of your optimization sessions and is considered a best practice. A database load utility also improves performance when populating PCT tables with an Campaign flowchart.

When you configure a database load utility to work with Optimize, it behaves as described for the following Optimize tables:

*
PCT table - If the number of unique customers is greater than or equal to the MinReqForLoaderCommand or MinReqForLoaderCommandForAppend, Optimize uses the database load utility.
*
POA table - Optimize uses the database load utility irrespective of the values for MinReqForLoaderCommand or MinReqForLoaderCommandForAppend.
*
OCT table - Optimize uses the database load utility irrespective of the values for MinReqForLoaderCommand or MinReqForLoaderCommandForAppend.
*
RC table - Optimize uses the database load utility irrespective of the values for MinReqForLoaderCommand or MinReqForLoaderCommandForAppend.

To configure a database load utility for Optimize complete the following steps.

*
Complete the database load utility configuration in the Campaign partitions as described in the Campaign documentation.
*
Confirm that the Optimize installation has the database load utility command in the same location as Campaign.
You must create the same relative folder structure on both machines because Campaign and Optimize both reference the Campaign > Partitions > PartitionN > DataSources > DataSourceName > LoaderCommand property.
For example, if LoaderCommand is /app/Unica/Campaign/partitions/partition1/scripts/load.sh, you must copy load.sh to /app/Unica/Optimize/partitions/partition1/scripts on your Optimize machine, creating the directories if necessary.
*
Confirm that the Optimize installation has the control file template for the database load utility in the same location as Campaign.
The file defined by Campaign > Partitions > PartitionN > DataSources > DataSourceName > LoaderControlFileTemplate must exist on both the Campaign and Optimize machines. The control file template should be located in the same relative directory. On the Campaign machine, the file should be relative to /Campaign, for example, /Campaign/partitions/partition1/scripts. On the Optimize machine, the files should be relative to /Optimize for example /Optimize/partitions/partition1/scripts.
On UNIX systems, use softlinks to create the control file templates in the Optimize directories. For example, from the /Optimize/partitions/partition1/scripts directory, run the following command:
ln –s /Campaign/partitions/partition1/scripts/load.ctr load.ctr
Copyright IBM Corporation 2012. All Rights Reserved.