Professional Documents
Culture Documents
Unica Campaign 850 Administrators Guide
Unica Campaign 850 Administrators Guide
Administrator's Guide
Copyright
Copyright IBM 2011 IBM Corporation Reservoir Place North 170 Tracer Lane Waltham, MA 02451-1379 All software and related documentation is subject to restrictions on use and disclosure as set forth in the IBM International Program License Agreement, with restricted rights for U.S. government users and applicable export regulations. Companies, names, and data used in examples herein are fictitious unless otherwise noted. IBM, the IBM logo, Unica and the Unica logo, NetInsight, Affinium and MarketingCentral are trademarks or registered trademarks of the IBM Corporation in the United States, other countries or both. Other product and service names might be trademarks of IBM or other companies. Copyright IBM Corporation 2011. All rights reserved.
Table of Contents
Preface Contacting IBM Unica technical support ...................................................................................21 1 Administration in IBM Unica Campaign..................................................................23
About administration in Campaign ..................................................................................................... 23 Campaign-related administrative tasks in IBM Unica Marketing ........................................................23
System Tables ............................................................................................................................ 39 User Tables................................................................................................................................. 39 User Variables............................................................................................................................. 39 Windows impersonation administration .............................................................................................. 40 What is Windows impersonation?................................................................................................... 40 Why use Windows impersonation?................................................................................................. 40 What is the relationship between Campaign users and Windows users?......................................40 The Windows impersonation group ................................................................................................ 41 Windows impersonation and logging into IBM Unica Marketing.....................................................41 Working with Windows impersonation ............................................................................................41 Set the Windows impersonation property ...................................................................................41 Create Campaign users .............................................................................................................. 41 Create the Windows impersonation group..................................................................................42 Assign the Windows impersonation group to policies.................................................................42 Assign rights to the Windows impersonation group....................................................................42 About support of Proxy Server Authentication ...................................................................................43 To set authentication credentials for a virtual data source named proxy .......................................43
Working with system tables ................................................................................................................ 52 To map or re-map a system table................................................................................................... 52 To unmap a system table ............................................................................................................... 53 To unmap the segment membership table ................................................................................53 To view system table contents........................................................................................................ 54 Working with user tables..................................................................................................................... 54 About working with user tables ....................................................................................................... 55 Guidelines for mapping user tables ................................................................................................ 55 To access data sources from within a flowchart.............................................................................55 Working with user tables while editing a flowchart .........................................................................56 Working with user tables by using the Admin menu...................................................................56 Working with user tables from the Select process......................................................................56 Working with user tables from exported data .............................................................................56 Working with user tables from exported data .............................................................................57 Working with user tables from the Campaign Settings page..........................................................57 To map a base record table to an existing database table.........................................................57 Mapping a base record table to an existing file ..........................................................................59 To map a base record table to a file ........................................................................................... 59 To map a base record table to an existing fixed-width flat file....................................................60 To map a base record table to an existing delimited file ............................................................60 To map a dimension table........................................................................................................... 62 To map a general table to a database table ...............................................................................63 To map a general table to a file .................................................................................................. 64 Re-mapping user tables .............................................................................................................. 65 To re-map a user table................................................................................................................ 66 Profiling values and counts ......................................................................................................... 66 To configure profiling ................................................................................................................. 67 To unmap a user table ................................................................................................................ 67 To create a new user table through an output process ..............................................................68 Working with data dictionaries ............................................................................................................ 69 To open a data dictionary ............................................................................................................... 70 To apply changes to a data dictionary ............................................................................................70 When to use a data dictionary ........................................................................................................ 70 Data dictionary syntax..................................................................................................................... 70
Version 8.5.0
To manually create a new data dictionary ......................................................................................71 Working with table catalogs ................................................................................................................ 71 To access table catalogs ................................................................................................................ 71 To open a table catalog .................................................................................................................. 72 To create a table catalog ................................................................................................................ 72 To load a stored table catalog ........................................................................................................ 73 Deleting table catalogs.................................................................................................................... 74 To update pre-computed profiles for tables in a table catalog .......................................................74 To define a data folder for a table catalog ......................................................................................75
To modify a custom attribute .......................................................................................................... 88 Standard offer attributes ................................................................................................................. 90 Working with offer templates .............................................................................................................. 90 To create an offer template............................................................................................................. 91 To modify an offer template ............................................................................................................ 92 To reorder offer templates .............................................................................................................. 93 To retire an offer template .............................................................................................................. 94 Using offer custom attributes in offer templates .............................................................................94 Adding list values to the Channel attribute .....................................................................................94 Offer template references ................................................................................................................... 95 Template icons................................................................................................................................ 95 Default offer attributes..................................................................................................................... 96
Version 8.5.0
Task 3: Map the Unica system tables to the database tables ..................................................107 Task 4: Map the user tables containing relevant data to the appropriate audience level(s) ....108 Task 5: Save the mapped tables in a table catalog..................................................................108 Removing an audience level......................................................................................................... 109 To remove an audience level.................................................................................................... 109 About global suppressions and global suppression segments.........................................................109 Switching audiences with global suppressions.............................................................................110 About creating global suppression segments ...............................................................................110 To create the global suppression segment in a flowchart ........................................................110 To specify the segment as a global suppression segment .......................................................111 Updating global suppression segments ........................................................................................ 111 Deleting global suppression segments .........................................................................................112 Logging for global suppressions ................................................................................................... 112
Response history concepts............................................................................................................... 121 What is response history?............................................................................................................. 122 What is the response type? .......................................................................................................... 122 How does response history relate to audience levels? ................................................................122 How does response history relate to database tables?................................................................122 Foreign key constraints in response history tables.......................................................................123 What is an action table? ............................................................................................................... 123 What does an action table contain?.............................................................................................. 123 Why use an action table? ............................................................................................................. 123 Working with response history.......................................................................................................... 124 Creating response history tables for new audience levels ...........................................................124 Mapping response history tables to Unica system tables.............................................................124 To set the number of days after an offer expires to record responses.........................................124 To add a response type ................................................................................................................ 125 Logging response history.............................................................................................................. 125 Response history references ............................................................................................................ 125 Default response types ................................................................................................................. 126 Sample UA_ActionCustomer Table .............................................................................................. 126
Dimension hierarchy concepts.......................................................................................................... 135 What is a dimension hierarchy?........................................................................................................ 135 Why use dimension hierarchies?...................................................................................................... 136 About dimension hierarchies and cubes........................................................................................... 136 About dimension hierarchies and database tables ...........................................................................136 Working with dimension hierarchies ................................................................................................. 138 About working with dimension hierarchies....................................................................................138 Designing dimension hierarchies .................................................................................................. 138 Accessing dimension hierarchies in Campaign ............................................................................138 To create a dimension hierarchy .................................................................................................. 139 To load a stored dimension hierarchy...........................................................................................140 To edit a dimension hierarchy ...................................................................................................... 140 To update a dimension hierarchy ................................................................................................. 141 To remove a dimension hierarchy ................................................................................................ 141
11 Trigger Administration..........................................................................................143
About triggers in IBM Unica Campaign ............................................................................................ 143 What is an inbound trigger?.............................................................................................................. 143 Why use an inbound trigger?........................................................................................................ 143 Inbound triggers and the Schedule process .................................................................................144 What is broadcasting? .................................................................................................................. 144 What is an outbound trigger?............................................................................................................ 144 Synchronous outbound triggers .................................................................................................... 145 Asynchronous outbound triggers .................................................................................................. 145 Why use an outbound trigger?...................................................................................................... 145 Return values for outbound triggers .............................................................................................146 How are triggers defined?................................................................................................................. 146 Working with trigger folders and triggers ..........................................................................................146 To create folders to organize triggers ...........................................................................................146 To move a trigger folder................................................................................................................ 147 To edit a trigger folder................................................................................................................... 147 To delete a trigger folder............................................................................................................... 148 To create a trigger......................................................................................................................... 148 To edit or move a trigger............................................................................................................... 149 To delete a trigger......................................................................................................................... 150
10
Setting up outbound triggers............................................................................................................. 151 Setting up a process to execute an outbound trigger ...................................................................151 To set up a flowchart to execute an outbound trigger on success ...............................................151 To set up a flowchart to execute an outbound trigger on failure ..................................................152 Setting up inbound triggers............................................................................................................... 152 To set up inbound triggers ............................................................................................................ 152 Configuring the Schedule process to run with an inbound trigger ................................................153 To broadcast a trigger to all flowcharts of a campaign.................................................................153 To broadcast a trigger to a flowchart ............................................................................................ 153 To broadcast a trigger to all campaigns........................................................................................ 154 Setting up the trigger utility on a remote Windows machine ............................................................154 unica_actrg utility: required files.................................................................................................... 155 Reference information for trigger administration...............................................................................155 Tokens supported by triggers ....................................................................................................... 155 Unica trigger utility syntax ............................................................................................................. 157 Unica trigger utility options............................................................................................................ 157
12 Logging Administration........................................................................................158
About logging .................................................................................................................................... 158 The Campaign Listener log............................................................................................................... 158 The Campaign web application log................................................................................................... 159 Flowchart logs................................................................................................................................... 159 The sessions log............................................................................................................................... 160 The web connections log .................................................................................................................. 160 Windows event logs .......................................................................................................................... 160 The log4j log file................................................................................................................................ 160 Working with logs.............................................................................................................................. 160 Campaign Listener logging tasks.................................................................................................. 161 To configure Campaign Listener logging ..................................................................................161 To view the Campaign Listener log file.....................................................................................161 Campaign web application logging tasks......................................................................................161 To configure Campaign web application logging ......................................................................161 To change the file name and location of the Campaign web application log ...........................162 Flowchart logging tasks ................................................................................................................ 162 To configure flowchart logging .................................................................................................. 162
Version 8.5.0
11
To enable or disable flowchart logging .....................................................................................163 To modify flowchart logging levels ............................................................................................163 To view flowchart log files ......................................................................................................... 163 To clear a flowchart log file ....................................................................................................... 163 Windows event logging tasks........................................................................................................ 164 To configure Windows event logging for the Campaign listener ..............................................164 To configure Windows event logging for flowcharts .................................................................164 log4j logging tasks ........................................................................................................................ 164 To configure logging in log4j ..................................................................................................... 164 To change the location of the campaign_log4j.properties file...................................................165
12
About outputting unique codes ..................................................................................................... 175 About outputting errors ................................................................................................................. 175 About placing the custom code generators ..................................................................................176 To specify the location of the custom offer code generator..........................................................176 Code generation references ............................................................................................................. 176 Properties related to code generation...........................................................................................177 Parameters for the default campaign and cell code generators ...................................................178 Parameters for the default offer code generator...........................................................................178
Version 8.5.0
13
To start the listener on UNIX systems ......................................................................................187 To stop the listener on UNIX systems ......................................................................................187 Campaign listener log ................................................................................................................... 187 Campaign Listener Shutdown utility (svrstop) ..................................................................................188 Campaign srvstop utility reference................................................................................................ 188 To use the svrstop utility to shut down the Campaign listener .....................................................189 To use the svrstop utility to shut down the Optimize listener .......................................................190 Campaign Server Manager (unica_svradm).....................................................................................190 To run the Campaign Server Manager .........................................................................................191 Campaign Server Manager commands ........................................................................................ 191 Cap (Distributed Marketing) ...................................................................................................... 191 Changeowner............................................................................................................................ 192 Connect..................................................................................................................................... 192 Disconnect ................................................................................................................................ 192 Exit ............................................................................................................................................ 192 Help........................................................................................................................................... 192 Kill ............................................................................................................................................ 192 Loglevel..................................................................................................................................... 193 Quit............................................................................................................................................ 193 Resume .................................................................................................................................... 193 Run ........................................................................................................................................... 193 Save ......................................................................................................................................... 195 Set ............................................................................................................................................. 195 Shutdown .................................................................................................................................. 195 Status ........................................................................................................................................ 195 Stop........................................................................................................................................... 196 Suspend .................................................................................................................................... 197 Uncap (Distributed Marketing) .................................................................................................. 197 Version ...................................................................................................................................... 197 To kill a running flowchart ............................................................................................................ 198 Campaign session utility (unica_acsesutil) ....................................................................................... 198 Environment variables required for unica_acsesutil .....................................................................198 Campaign session utility use cases.............................................................................................. 199 Exporting and importing objects between servers ....................................................................199
14
About the exporting and importing process ..............................................................................199 About conflicts with existing data when importing ....................................................................200 To export a campaign, session, or flowchart ............................................................................200 To import a campaign, session, or flowchart ............................................................................201 Backing up sessions ................................................................................................................. 201 Updating record counts and lists of distinct values...................................................................201 Manipulating table catalogs....................................................................................................... 202 Documenting catalog contents.................................................................................................. 203 Campaign session utility return values ........................................................................................ 203 Campaign session utility syntax.................................................................................................... 204 Campaign session utility options ................................................................................................. 204 Campaign cleanup utility (unica_acclean) ........................................................................................207 Environment variables required for unica_acclean .......................................................................207 Campaign cleanup utility use cases .............................................................................................207 Generating a list of orphaned files and tables ..........................................................................208 To output a list of orphaned files and tables.............................................................................208 Deleting the files and tables listed in a file................................................................................208 To delete the files and tables listed in a file..............................................................................208 Deleting all orphaned temp files and tables..............................................................................209 To delete all orphaned temp files and tables from your system ...............................................209 About orphaned files and tables ............................................................................................... 209 Generating a list of files and tables selectively by object type and criteria...............................209 To generate a list of files and tables selectively by object type and criteria .............................210 Deleting files and tables selectively by object type and criteria................................................210 To delete files and tables selectively by object type and criteria ..............................................210 Campaign cleanup utility syntax ................................................................................................... 211 Campaign cleanup utility options .................................................................................................. 211 Campaign report generation utility (unica_acgenrpt)........................................................................213 Use case: capture cell counts from flowchart runs .......................................................................214 IBM Unica Campaign report generation utility syntax...................................................................214 IBM Unica Campaign report generation utility options..................................................................214 Parameters used with the unica_acgenrpt -p option ................................................................215 ActiveX cleanup utility (uacflchk) ...................................................................................................... 217 ActiveX cleanup utility prerequisites .............................................................................................217
Version 8.5.0
15
ActiveX cleanup utility syntax........................................................................................................ 217 Running the ActiveX cleanup utility in check mode (no options)..................................................218 ActiveX cleanup utility check mode messages .........................................................................218 ActiveX cleanup utility options ...................................................................................................... 219 Database testing utilities ................................................................................................................... 219 cxntest utility ................................................................................................................................. 219 To use the cxntest utility ........................................................................................................... 219 odbctest utility ............................................................................................................................... 220 To use the odbctest utility ......................................................................................................... 220 db2test utility ................................................................................................................................. 222 To use the db2test utility ........................................................................................................... 222 oratest utility.................................................................................................................................. 223 To use the oratest utility............................................................................................................ 223 Database load utilities....................................................................................................................... 223 Fast loader repeated tokens ......................................................................................................... 224
16
Test that your attribute table is correctly configured .................................................................234 Test campaigns and flowcharts that have ASCII and non-ASCII characters ...........................235 Test flowchart input and output that contains ASCII and non-ASCII characters ......................235 Test that the correct language directory is used.......................................................................236 Test the date formats in calendar reports .................................................................................237 Test that the currency symbol displays correctly for your locale ..............................................237 Configuring Campaign for multiple locales ....................................................................................... 237 Before you begin: Campaign must be installed ............................................................................238 Configuring for multiple locales on SQL .......................................................................................238 Configuring for multiple locales on Oracle ....................................................................................238 Configure encoding properties (Oracle) ....................................................................................238 Configure date/time settings (Oracle) ....................................................................................... 239 Configure environment variables (Oracle) ................................................................................239 Configure the cmpServer.bat file (Oracle) ................................................................................240 Configuring for multiple locales on DB2........................................................................................240 Configure encoding properties (DB2) .......................................................................................240 Configure date/time settings (DB2)........................................................................................... 241 Configure environment variables (DB2).................................................................................... 241 Configure application server startup scripts (DB2) ...................................................................241
Version 8.5.0
17
Web access control category........................................................................................................ 260 LDAP synchronization category.................................................................................................... 261 LDAP references for Unica user creation category ......................................................................269 LDAP reference to Unica group map category .............................................................................270 Reporting configuration properties.................................................................................................... 270 Cognos 8 category........................................................................................................................ 271 SQL Configuration category.......................................................................................................... 274 Campaign category....................................................................................................................... 275 Offer Performance category.......................................................................................................... 276 [Contact Metric] category .............................................................................................................. 277 [Response Metric] category .......................................................................................................... 278 Performance category................................................................................................................... 279 Offer Response Breakout category............................................................................................... 280 [Response Type] category ............................................................................................................ 281 Campaign Offer Contact Status Breakout category......................................................................282 [Contact Status Code] category .................................................................................................... 283 [Campaign Custom Column] category ..........................................................................................284 [Offer Custom Column] category .................................................................................................. 284 [Cell Custom Column] category .................................................................................................... 285 Interact category ........................................................................................................................... 286 Interact Performance category...................................................................................................... 287 eMessage category....................................................................................................................... 288 Campaign configuration properties ................................................................................................... 288 Campaign category....................................................................................................................... 288 Collaborate category..................................................................................................................... 290 navigation category....................................................................................................................... 290 caching category........................................................................................................................... 292 Campaign > partitions ................................................................................................................... 294 eMessage category....................................................................................................................... 294 reports category ............................................................................................................................ 296 validation category ........................................................................................................................ 298 audienceLevel category ................................................................................................................ 299 field[n] category............................................................................................................................. 300 dataSources category ................................................................................................................... 301
18
Campaign > partitions > partition[n] > systemTableMapping ......................................................360 systemCodes category ................................................................................................................. 360 encoding category......................................................................................................................... 363 timeout category ........................................................................................................................... 364 collaborate category...................................................................................................................... 365 permissions category .................................................................................................................... 365 flowchartConfig category .............................................................................................................. 367 flowchartSave category................................................................................................................. 369 dataProcessing category .............................................................................................................. 370 optimization category .................................................................................................................... 374 logging category............................................................................................................................ 376 flowchartRun category .................................................................................................................. 381 profile category ............................................................................................................................. 382 internal category ........................................................................................................................... 382 fileDialog category ........................................................................................................................ 384 offerCodeGenerator category ....................................................................................................... 384 monitoring category ...................................................................................................................... 386 ProductReindex category.............................................................................................................. 388 category ........................................................................................................................................ 388 server category ............................................................................................................................. 392 logging category............................................................................................................................ 393
Armenian....................................................................................................................................... 402 Baltic Rim...................................................................................................................................... 402 Celtic ............................................................................................................................................. 402 Central Europe.............................................................................................................................. 402 Chinese (both Simplified and Traditional) .....................................................................................402 Chinese (Simplified) ...................................................................................................................... 403 Chinese (Traditional)..................................................................................................................... 403 Cyrillic............................................................................................................................................ 403 English .......................................................................................................................................... 403 Georgian ....................................................................................................................................... 404 Greek ............................................................................................................................................ 404 Hebrew.......................................................................................................................................... 404 Icelandic ........................................................................................................................................ 404 Japanese....................................................................................................................................... 404 Korean........................................................................................................................................... 405 Lao ................................................................................................................................................ 405 Northern Europe ........................................................................................................................... 405 Romanian...................................................................................................................................... 405 Southern Europe ........................................................................................................................... 405 Thai ............................................................................................................................................... 406 Turkish .......................................................................................................................................... 406 Vietnamese ................................................................................................................................... 406 Miscellaneous ............................................................................................................................... 406 Date and time formats ...................................................................................................................... 406 Formats for DateFormat and DateTimeFormat ............................................................................407 Formats for DateOutputFormatString and DateTimeOutputFormatString ....................................410
20
N10013
Preface
N40001
System information
When you call IBM Unica technical support, you might be asked to provide information about your environment. If your problem does not prevent you from logging in, much of this information is available on the About page, which provides information about your installed IBM Unica applications. You can access the About page by selecting Help > About. If the About page is not accessible, you can obtain the version number of any IBM Unica application by viewing the version.txt file located under each applications installation directory.
Version 8.5.0
21
Preface
22
N1001A
Data source operations. Provides access to pages for performing the following tasks: Table mappings manage user and system table mappings Datasource access manage and view details of your data sources Dimension hierarchies create and manage dimension hierarchies required in your business operation Audience levels create and manage audience levels required in your business operation System log view the Listener (aclsnr) log for the current session
N60001
Version 8.5.0
Administering Windows impersonation Configuring proxy server authentication Managing configuration properties Configuring reporting Scheduling flowcharts with the IBM Unica Scheduler
For information on performing these tasks, see the Marketing Platform Administrator's Guide.
24
N10027
About security in IBM Unica Campaign About security policies Security scenarios Implementing security policies About administrative permissions in Campaign Windows impersonation administration About support of Proxy Server Authentication
Version 8.5.0
25
Applying security policies to objects or folders allows you to separate the objects in Campaign for use by different groups of users. For example, you could configure your security policies so that users belonging to one policy cannot access or even view objects that are associated with other policies. You can create your own security policies or use the default global security policy included with Campaign.
NE0001
The global security policy applies to all users through the Owner and Folder Owner roles, including users who have not been assigned to any other specific role in the global policy. Because the global policy always applies, it can be used, for example, to globally deny permissions to a role.
NF0001
26
1. Identifies all groups and roles to which this user belongs within the global security policy. A user can belong to one, many, or no roles. A user belongs to the Owner role if they own an object; they belong to the Folder Owner role if they own the folder in which an object resides. A user belongs to other roles only if they have been specifically assigned to that role (either directly or because they belong in a group assigned to that role). 2. Identifies whether the object being accessed has been assigned to a customdefined policy, if any exist. If so, the system then identifies all groups and roles to which the user belongs within this custom policy. 3. Aggregates the permissions for all roles to which the user belongs, based on results from steps 1 and 2. Using this composite role, the system evaluates the permissions for the action as follows: a. If any roles have Denied permission for this action, then the user is not allowed to perform it. b. If no roles have Denied permission for this action, then it checks to determine whether any roles have Granted permission for this action. If so, the user is allowed to perform the action. c. If neither a nor b is true, the user is denied the permission.
N100001
Version 8.5.0
27
Keep the design simple. Campaign allows you to create multiple security policies and roles, but you should keep the security design as simple as possible, and use as few policies and roles as possible to achieve your security needs. At the most minimal level, for example, you can use the default global security policy as is, without creating new roles or policies. Avoid potential conflicts among security policies. If your organization implements more than one security policy, keep potential conflicts in mind when designing the policies. For example, users with Move and Copy permissions in more than one security policy are able to move or copy objects and folders to locations across the policies in which they have these permissions. In doing so, because the moved objects or folders take on the security policy of their destination (if under another folder), they might cause situations where the rightful users in one division are no longer able to access the moved objects because they have no roles in the destination security policy, or where users with roles in the destination security policy who were not intended to access the objects, find that they now can. Assign view permissions to allow users to modify objects. To modify many of the objects in Campaign, users must be granted both view and modify permissions for the object. This requirement applies to the following objects: campaigns flowcharts offers offer lists offer templates sessions strategic segments
N90001
Security scenarios
This section provides security model examples and explains how they are implemented in Campaign using security policies.
N120001
Scenario 1: Company with a single division Scenario 2: Company with multiple separate divisions Scenario 3: Restricted access within a division
Security scenarios
Solution Only a single security policy is required, as objects do not have to be separated by group or division. In the existing global security policy, define roles corresponding to the employee jobs, and for each role, define the appropriate permissions for each object or function. The table below displays a sample subset of object permissions for three roles: Manager, Designer, and Reviewer. For example, a Manager has full access and editing ability for campaigns and offers; a Reviewer can access campaigns and offers, but cannot add, edit, delete, or run them. Optionally, you can also create user groups in IBM Unica Marketing that match these roles, and then assign user permissions simply by adding users to these groups. The following table shows a sample subset of the object permissions for this scenario.
Functions/Role Campaigns Add Campaigns Edit Campaigns Delete Campaigns Run Campaigns View Campaign Summary Manager Designer Reviewer
Offers
N130001
Add Offers Edit Offers Delete Offers Retire Offers View Offer Summary
Version 8.5.0
29
Campaigns Add Campaigns Edit Campaigns Delete Campaigns View Campaign Summary
30
Security scenarios
Functions/Role
Folder Owner
Object Owner
Manager
Designer
Reviewer
Campaigns Add Campaigns Edit Campaigns Delete Campaigns View Campaign Summary
Offers
N140001
Version 8.5.0
31
Define a Read-Only role that grants only read permissions on objects. Assign all users within the division to this role. Keep the default permissions as defined for the Owner and Folder Owner roles. If your company requires only a single security policy, you can use the global policy and assign all users to the Review role. Each user will be allowed to edit or delete their own objects (under the Owner role) and objects in their own folders (under the Folder Owner role), but only view objects and folders owned by others (under the Read-Only role). The following table shows a sample subset of the object permissions for this scenario.
Functions/Role Campaigns Add Campaigns Edit Campaigns Delete Campaigns View Campaign Summary Folder Owner Object Owner Reviewer
Offers
NA0001
Keep in mind the following rules when associating a folder or object with a security policy: You cannot assign a security policy to objects within folders. Objects automatically inherit the security policy of the folder in which they reside. The top-level folder determines the security policy. Objects within a folder, including subfolders, inherit the security policy of the parent folder. In other words, the security policy of the top-level folder determines the security policy of objects and subfolders within it. Therefore, you cannot manually assign a security policy to objects within folders. To change the security policy of an object, you must move the object into a folder with the desired security policy or into the top-level root folder. Security policy changes when objects are moved or copied. Objects and folders can be moved or copied across security policies, but the user performing the move or copy must have permissions to do so, in both the source and destination policies. After an object or folder is moved or copied to a folder or location belonging to a different security policy than its source, the security policy of the lower-level objects or subfolders is automatically changed to the new folders or locations security policy.
NB0001
You can add other administrative roles for each partition as needed. The procedures for managing administrative roles and permissions in Campaign is the same as the procedures for managing roles and permissions in Marketing Platform.
N180002
34
Administration
Permission Access Monitoring Area Perform Monitoring Tasks Description Allows access to the Campaign Monitoring area. Allows performing of monitoring tasks in the Campaign Monitoring area. Allows access to reports in the Campaign Analytics area. If Optimize is installed, allows access to that application. Allows performing of administrative functions using the Campaign Server Manager (unica_svradm). Allows running of the Campaign report generation utility (unica_acgenrpt). Allows taking over control of flowcharts in Edit or Run mode from other users. Taking over control of a "locked" flowchart locks out the other user and all changes in the flowchart since the last save are lost. Connect to Running Flowcharts Allows attaching to running flowcharts through Campaign Server Manager (unica_svradm) or the Campaign user interface. Allows terminating the Campaign Server (unica_acsvr) using the Campaign Server Manager (unica_svradm). Allows terminating the Campaign Listener (unica_aclsnr) using the Campaign Server Manager (unica_svradm) or using the svrstop utility. Allows running of the Campaign session utility (unica_acsesutil). Allows overriding the Virtual Memory setting in flowchart Advanced Settings. Allows access to and managing of custom attribute definitions from the Campaign Settings page. Allows access to cell reports from the Reports icon on a flowchart Edit page. Excludes access to the Cell Content Report unless this is also explicitly granted.
Access Analysis Area Access Optimizations Link Run svradm Command Line Tool
36
About administrative permissions in Campaign Permission Cell Report Export Description If cell report access is granted, allows printing and exporting of cell reports. Allows access to the Cell Content report from the Reports icon on a flowchart Edit page. If Cell Content Report Export is granted, allows printing and exporting of the Cell Content report. Allows performing cleanup operations using the unica_acclean or a custom tool. Allows changing ownership of an object or folder.
Audience levels
Permission Add Audience Levels Description Allows creation of new audience levels under Manage Audience Levels on the Campaign Settings page. Allows deleting of existing audience levels under Manage Audience Levels on the Campaign Settings page. Allows creation and configuration of global suppression segments in Campaign. Allows clearing or selecting the Disable Global Suppressions for This Flowchart checkbox on the flowchart Advanced Settings dialog.
N1C0001
Data sources
Permission Manage Datasource Access Description Allows managing data source logins from the Administration area and within flowcharts. Allow enabling the Save with Database Authentication Information flag in table catalogs and flowchart templates.
N1D0001
Version 8.5.0
37
Dimension Hierarchies
Permission Add Dimension Hierarchies Edit Dimension Hierarchies Delete Dimension Hierarchies Refresh Dimension Hierarchies
N1E0001
Description Allows creation of new dimension hierarchies. Allows editing of existing dimension hierarchies. Allows deletion of existing dimension hierarchies. Allows refresh of existing dimension hierarchies.
History
Permission Log to Contact History Tables Description Allows enabling or disabling logging to contact history tables when configuring contact processes. Allows clearing entries from the contact history tables. Allows enabling or disabling logging to response history tables when configuring the Response process. Allows clearing entries from the response history tables.
Logging
Permission View System and Flowchart Logs Clear Flowchart Logs Override Flowchart Log Options
N200001
Description Allows viewing of flowchart logs and the system log Allows clearing of flowchart logs. Allows override of default flowchart logging options.
38
System Tables
Permission Map System Tables Remap System Tables Unmap System Tables Delete System Table Records
N220001
Description Allows mapping system tables. Allows remapping system tables. Allows unmapping system tables. Allows deletion of records from system tables.
User Tables
Permission Map Base Tables Map Dimension Tables Map General Tables Map Delimited Files Map Fixed-Width Flat Files Map Database Tables Remap User Tables Unmap User Tables Recompute Counts and Values Description Allows mapping base tables. Allows mapping dimension tables. Allows mapping general tables. Allows mapping user tables to delimited files. Allows mapping user tables to fixed-width flat files. Allows mapping user tables to database tables. Allows remapping of user tables. Allows unmapping of user tables. Allows using Compute button in table mapping to recompute table counts and values. Allows the use of raw SQL in Select process queries, custom macros, and dimension hierarchies.
N230001
User Variables
Permission Manage User Variables Description Allows creating, deleting and setting default values for user variables in flowcharts. Allows use of user variables in output files or tables.
Version 8.5.0
39
What is Windows impersonation? Why use Windows impersonation? How do Campaign users and Windows users relate? How do Windows impersonation users relate to a group? Windows impersonation and logging into Campaign
40
Version 8.5.0
41
Create external users by configuring Active Directory users and group synchronization. Each user you create must have the same login name as the users Windows user name.
N2C0001
For more information about assigning groups to policies, see your Microsoft Windows documentation.
N2E0001
42
Version 8.5.0
43
1. On the Settings > Users page, add a data source named proxy for each Campaign user. 2. Set the user name and password for the proxy data source to the proxy servers user name and password. The data is automatically encrypted when stored in the Marketing Platform; however, the data is only encoded (not encrypted) when passed from the Web server to the Active-X implementation. If additional security is required for this communication, you must configure Campaign to use SSL. If the user name or password for the proxy server change, the user must update these authentication values to match by editing the values for the "proxy" data source for each user.
44
N10146
About table administration Table administration concepts Initial table administration tasks Working with system tables Working with user tables Working with data dictionaries Working with table catalogs
Data dictionaries, which define the structure of user tables based on fixed-width flat files Table catalogs, which enable the efficient management of mapped user tables
What are system tables? What are user tables? About mapping tables What is a data dictionary? What is a table catalog?
Version 8.5.0
45
Related Topics
Working with user tables
N3D0001
Version 8.5.0
47
A data dictionary is required to interpret the structure and format of a fixed-width ASCII text file. It defines the field names, their order, their data type (string or numeric) and the byte positions they occupy in the file. Data dictionaries are automatically created for fixed-width flat files created by Campaign and these typically do not need to be manually created or edited. You use data dictionaries in output processes such as Snapshot, Mail List, and Call List to ensure that the flat file tables you create adhere to a specific structure. A data dictionary defines the table fields, data types, and sizes. You can develop data dictionaries for vendor or channel-specific output and re-use them to create output of a pre-determined format. If you are using a fixed-width flat file created by a non-Unica third-party application, you may need to manually or programmatically create an associated data dictionary. Or you may want to copy an existing data dictionary and edit it to create a new file. You also can edit a data dictionary to change field names. You must be sure that you are not corrupting data if you choose to edit any of the other fields in the data dictionary.
Related Topics
Working with data dictionaries
N3B0001
You can save mapped user tables to a table catalog, then use the same table catalog in other flowcharts. This means you can: Make changes to the table catalog in one flowchart, then propagate these changes to other flowcharts by importing the updated table catalog into each flowchart. Retain the internal catalog you first loaded for that flowchart, although you copy it to other flowcharts and make changes there.
48
Make different changes to the internal catalogs of a number of different flowcharts, starting from one template table catalog.
You should delete table catalogs only using the Campaign interface. If you remove tables or otherwise change table catalogs directly in the file system, Campaign cannot guarantee data integrity in your system.
Related Topics
Working with table catalogs Deleting table catalogs
N320001
Prerequisites: expected state following installation Testing system table access Testing user table access Mapping Customer audience level system tables
For more information about these tasks, see the installation documentation. In addition, you should define necessary audience levels before beginning to work with user tables, as you need to specify audience levels related to your base tables. For instructions on confirming that the Campaign system is ready for you to begin the table administration tasks, see:
N420001
To test system table access Testing user table access Mapping Customer audience level system tables
Version 8.5.0
49
You can now map the user data into Campaign, as described in Working with user tables. You can also view the customer databases that Campaign is set up to access when editing a flowchart. Click the Admin icon and select Database Sources. The Database Sources window opens, listing the system table database, and all configured customer databases. From this window, you can log into and log out of customer databases.
Related Topics
To access data sources from within a flowchart
N440002
Version 8.5.0
51
Running the Create Seg process populates a database table if you have mapped it to a segment membership system table. If you run the Create Seg process when the database table is not mapped to the segment membership system table, you must rerun the Create Seg process to populate the table if you map it later. Otherwise, Optimize sessions in Optimize that use strategic segments may provide inaccurate results. If you are not using strategic segments in flowcharts or Optimize sessions Using strategic segments in Campaign flowcharts and Optimize sessions is optional. If you are not using strategic segments, the best practice is that you do not map the segment membership table. Mapping an audience's segment membership system table causes Campaign or Optimize to refresh the table each time you run the flowchart or Optimize session that includes the audience. This is unnecessary processing overhead if you are not using strategic segments.
N330001
To map or re-map a system table To unmap a system table To view system table contents
52
5. If the table is not automatically selected in the Source Table drop-down list, select it (entries are alphabetically listed by owner.table names). Source table fields in the Campaign database are automatically mapped to required fields. For system tables, you do not need to add or remove any field mappings; all field entries should be matched automatically. When mapping a system table, do not select a different table from the Source Table list; you will not be able to complete the mapping. If you do this accidentally, click Cancel and select a the correct table in the Table Mappings window. 6. Click Finish.
N480001
By default, this file is located at Optimize\partitions\<partition[n]>\conf. 4. Restart the Campaign listener (unica_aclsnr). 5. Restart the Optimize listener (unica_aolsnr).
N490001
About working with user tables To access data sources from within a flowchart Working with user tables while editing a flowchart Working with user tables from the Campaign Settings page To map a base record table to an existing database table Mapping a base record table to an existing file To map a dimension table To map a general table to a database table To map a general table to a file
IBM Unica Campaign - Administrator's Guide
Re-mapping user tables Profiling values and counts To unmap a user table To create a new user table through an output process You should define necessary audience levels before beginning to work with user tables, as you need to specify audience levels related to your base tables.
N4B0001
N450001
Version 8.5.0
55
The Database Sources window opens. The database containing system tables is listed, as well as all databases for which Campaign is configured to access. 2. To log into a database, select it and click Login. 3. Click Close. You now have access to tables in that database. To query a table in that database, you must map that table, as described in the next section.
N4C0001
Using the Admin menu Mapping a new user table through the Select process Exporting data to a base or general table through Snapshot, Call List, and Mail List processes
Mapping a base record table to an existing database table Mapping a base record table to an existing file Mapping a dimension table Mapping a general table to a database table Mapping a general table to a file Re-mapping a user table Unmapping a user table
Mapping a base record table to an existing database table Mapping a base record table to an existing file
Related Topics
To create a new user table through an output process
N5B0001
You map a new base record table to make data accessible to processes in flowcharts. 1. Begin from the New Table Definition - Select the table type window.
Version 8.5.0
57
The Dimension Table and General Table options are not be listed when you access the table mapping wizard from a Select process. 2. If necessary, select Base Record Table, then click Next. 3. Select Map to Existing Table in Selected Database, select the data source name, then click Next. 4. Select the table you want to map from the Source Table list. The tables are listed in alphabetical order by < owner >.< table_name >. If you do not see a table you expect, check whether the data source is configured to filter specific table entries. The source fields in the table you select are mapped automatically to new table fields in the base record table you are creating. To change the automatic mappings, select fields from the Source Table Fields list or the New Table Fields List, and use the Add, Remove, Up 1, an Down 1 buttons, until the table is mapped as required. You can click on the Field Name column in the New Table Fields section to automatically sort column names alphabetically in ascending (or descending) order. 5. Click Next. 6. Optionally, you can change the name which Campaign will use for the base record table and its fields to a more user-friendly value. a. To change the table name, edit the name in the Unica Table Name field. b. To change a field name, select the field name in the New Table Fields list, and edit the text in the Unica Field Name field. 7. Click Next. 8. Select an Audience Level from the drop-down list. The Audience Fields list is automatically populated with the fields required to define the selected audience level. You must match one or more fields in the new base table that correspond to each required key. 9. If the selected audience level is normalized (that is, each unique audience ID appears at most once in the current base table), check This audience level is normalized in this table. Setting this option correctly is important for correct configuration of options in an Audience process. If you don't know the correct setting, leave this option unchecked. 10. Click Next. 11. Optionally, in the Specify Additional audience levels screen, you can specify one or more additional audience levels contained in the base record table. Adding additional audience levels allows users to use this table as a switching table to translate from one audience level to another using the Audience process in a flowchart. a. Click Add. The Audience Level and ID Fields window opens.
58 IBM Unica Campaign - Administrator's Guide
b. Select an Audience Level Name. c. For each Audience Field, match appropriate field(s) from the base table to the corresponding key(s) in the audience level. d. If the selected audience level is normalized (that is, each unique audience ID appears at most once in the current base table), check This audience level is normalized in this table. e. Click OK. f. Repeat steps a through f for each audience level you want to add for the base table, then click Next.
12. If dimension tables exist in the current table catalog, the Specify Relationship to Dimension Tables window opens: a. Check the box to the left of any dimension table that is related to the base record table you are creating. b. For each related dimension table, in the New Tables Key Fields(s) To Use list, select a field from the base table to match each listed key in the Dimension Table's Key Field(s) list, then click Next. 13. You can choose to pre-compute the distinct values and frequency counts for specific fields, or allow users to perform real-time profiling of data in the base record table. 14. Click Finish. You have created the base record table based on an existing database table. The new base table is part of the current table catalog, which you can managed through the table manager.
Related Topics
Profiling values and counts Working with table catalogs
N4F0001
You map a new base record table to make data accessible to processes in flowcharts.
N5C0001
3. Select Map to Existing File, then click Next. 4. Specify the type of file and mapping settings.
N5D0001
You map a new base record table to make data accessible to processes in flowcharts. 1. Begin from the New Table Definition - Select the table type window. 2. If necessary, select Base Record Table, then click Next. 3. Select Map to Existing File, then click Next. 4. Keep the default File Type selection of Fixed-Width Flat File. The Settings section of the window appears. 5. In the Settings section of the window, click Browse to select the Source File from within your campaign partition root directory. Campaign automatically populates the Dictionary File field with the same path and file name, except with the .dct extension. You can override this entry if necessary.
N5E0002
60
This is important if you have a space-delimited file with spaces as part of a field entry. In this case, the field must be enclosed in quotation marks so the embedded spaces are not interpreted as field delimiters. For example, if you had a row of data such as: John Smith 100 Main St., with the delimiter as SPACE and Qualifier set to NONE, Campaign would parse this as five different fields (John as the value of the first field, Smith as the second, 100 as the third, and so forth). If the qualifier is set to Double Quote, then this record is correctly parsed as two fields (name and street address). Campaign does not support the use of the double quote character (") in field entries of delimited files. If any of your field entries contain double quotes, change them to another character before mapping a table to the file. 8. Click Browse to select the Source File from within your partition directory. 9. Specify the fields to use in the new table. By default, all fields in the file are listed. If you are mapping a delimited file, you can override the field type that is automatically detected by Campaign (Numeric or Text) or the width, which samples the first 100 lines of the file. If you set the field width to a value that is too small, data will be truncated. You use the Add, Remove, Up 1 and Down 1 buttons to specify the Source Table Fields that are included in the new table and their order. Click on the Field Name column in the New Table Fields section to automatically sort column names alphabetically in ascending (or descending) order. 10. When finished, click Next. The Specify table name and field information screen opens. 11. Accept the defaults, or edit the Unica Table Name field to change the name of the table as it will appear in Campaign. You can also change the Unica Field Name mapped to each source field name by selecting the field name and editing the text in the Unica Field Name text box in the Edit Selected Field Information section. 12. When your changes are complete, click Next. The Specify the selected table's audience level and assign ID field(s) to it screen opens. 13. Select an Audience Level from the drop-down list. The Audience Fields list is automatically populated. You must select a field in the new base table that is the corresponding key for each listed entry. 14. Click Next. The Specify Additional Audience Levels screen opens. 15. Optionally, in the Specify Additional audience levels screen, you can specify one or more additional audience levels contained in the base record table. Adding additional audience levels allows users to use this table as a switching table to translate from one audience level to another using the Audience process in a flowchart. a. Click Add. The Audience Level and ID Fields window opens. b. Select an Audience Level Name.
Version 8.5.0
61
c. For each Audience Field, match appropriate field(s) from the base table to the corresponding key(s) in the audience level. d. If the selected audience level is normalized (that is, each unique audience ID appears at most once in the current base table), check This audience level is normalized in this table. e. Click OK. f. Repeat steps a through f for each audience level you want to add for the base table, then click Next.
16. You can choose to pre-compute the distinct values and frequency counts for specific fields, or allow users to perform real-time profiling of data in the base record table. 17. Click Finish. You have created the base record table based on an existing file. The new base table is part of the current table catalog, which you can managed through the table manager.
Related Topics
Profiling values and counts Working with table catalogs
N500001
You map a new dimension table to make data that augments data in a base table, such as demographics based on postal codes, accessible to processes in flowcharts. Dimension tables must be mapped to a database table and must be related to one or more base tables that are mapped to tables in the same IBM Unica data source (that is, the same database). In defining the dimension table, you can specify the specific join conditions between the base and dimension tables. 1. Begin from the New Table Definition - Select the table type window. You cannot map a dimension table from a Select process. 2. Select Dimension Table, then click Next. 3. Select the table you want to map from the Source Table list. The source fields in the table you select are mapped automatically to new table fields in the base dimension table you are creating. To change the default selections, select fields from the Source Table Fields list or the New Table Fields List, and use the Add, Remove, Up 1, and Down 1 buttons, until the table is mapped as required, then click Next.
62 IBM Unica Campaign - Administrator's Guide
You can click on the Field Name column in the New Table Fields section to automatically sort column names alphabetically in ascending (or descending) order. 4. (Optional) Change the name Campaign will use for the dimension table and its fields. a. To change the table name, edit the name in the IBM Unica Table Name field. b. To change a field name, select the mapping in the New Table Fields list, and edit the text in the IBM Unica Field Name field, then click Next. 5. Specify the dimension tables key(s), and how the table will be joined to base record tables. 6. Select one or more keys in the Key Field(s) list. 7. Check Key Field(s) are Normalized in This Table, if this is the case. 8. Select the Table Join Method, then click Next. The option Always use inner join will always use an inner join between the base table and this dimension table, returning only audience IDs from the base table that appear in the dimension table. The Always use outer join option will always perform an outer join between the base table and this dimension table (which provides the best results if the dimension table is known not to contain at least one row for every audience ID in the base table). The default setting of auto uses an inner join in the Select and Segment processes and an outer join in output processes (Snapshot, Mail List, and Call List). This typically provides the desired behavior where values in the dimension table are required for selection criteria, but NULLs should be output for missing audience IDs for any dimension table fields that are output. 9. If base record tables exist, the Specify Relationship to Base Tables screen opens. Check the box to the left of any base record table that is related to the dimension table you are creating Specify the join fields, then click Next. 10. You can choose to pre-compute the distinct values and frequency counts for specific fields, or allow users to perform real-time profiling of data in the base record table. 11. Click Finish. You have created the dimension table.
Related Topics
Profiling values and counts
N510001
Version 8.5.0
Through the Campaign Settings page, as described in Working with user tables from the Campaign Settings page.
You map a new general table to export Campaign data for use by other applications. 1. Begin from the New Table Definition - Select the table type window. 2. Select General Table, then click Next. 3. Select Map to Existing Table in Selected Database, select the customer database name, then click Next. 4. Select the table you want to map from the Source Table list. The source fields in the table you select are mapped automatically to new table fields in the general table you are creating. To change the automatic mappings, select fields from the Source Table Fields list or the New Table Fields List, and use the Add, Remove, Up 1, an Down 1 buttons, until the table is mapped as required, then click Next. 5. (Optional) Change the name which Campaign will use for the general table and its fields. To change the table name, edit the name in the Unica Table Name field. To change a field name, select the mapping in the New Table Fields list, and edit the text in the Unica Field Name field. 6. Click Finish You have created the general table based on a database table.
N520001
You map a new general table to export Campaign data for use by other applications. 1. Begin from the New Table Definition - Select the table type window. 2. Select General Table, then click Next. 3. Select Map to Existing File, then click Next. 4. To map a base record table to a fixed-width flat file: a. Keep the default File Type selection. b. Click Browse to select the Source File. Campaign will automatically populate the Dictionary File field with the same path and file name, except with the .dct extension. You can override this entry if necessary. 5. To map a base record table to a delimited file:
64 IBM Unica Campaign - Administrator's Guide
a. Select Delimited File for the File Type. b. Check First Row of Data Contains Field Names if this is the case. c. Select the Field Delimiter used: TAB, COMMA, or SPACE. d. Select the Qualifier used to indicate how strings are delimited in the file: None, Single Quote, or Double Quote. e. Click Browse to select the Source File, then click Next. The Specify the New Tables Fields window opens. 6. Specify the fields to use in the new table. By default, all fields in the file are listed. If you are mapping a delimited file, you can override the field type that is automatically detected by Campaign, which samples the first 100 lines of the file. When you export data to a fixed-width flat file on disk, you can override the preset field lengths by editing the data dictionary for that file. You use the Add, Remove, Up 1 and Down 1 buttons to specify the Source Table Fields that are included in the new table and their order. 7. When finished, click Next. The Specify table name and field information window opens. 8. Accept the defaults, or edit the Unica Table Name field to change the name of the table as it will appear in Campaign; and change the Unica field names that are mapped to the source field names. 9. Click Finish. You have created the general table based on a file.
Related Topics
To manually create a new data dictionary
N530001
If you remove a field that has been referenced in a flowchart or change the name of the table or referenced fields, you will cause the flowchart to become unconfigured. You must then manually edit each process box where the table is used to correct references.
Version 8.5.0
65
Remember that remapping a user table changes only the local table mapping for the current flowchart. To save the updated table mapping to the table catalog, you must save the table catalog. Once saved into the table catalog, any flowchart subsequently using (or importing that table catalog) will see the changes. You can re-map a user table: When editing a flowchart, through the Admin menu, as described in Working with user tables while editing a flowchart. Through the Campaign Settings page, as described in Working with user tables from the Campaign Settings page.
Related Topics
To update pre-computed profiles for tables in a table catalog
N610001
Mapping a base record table to an existing database table Mapping a base record table to an existing file Mapping a dimension table Mapping a general table to a database table Mapping a general table to a file
66
You can choose to both pre-compute profiles and allow users to dynamically profile in real-time, or you can choose to disable real-time profiling and force users to always use the pre-computed profiles. Enabling or disabling the Allow real-time profiling option applies to all table fields, not just the checked ones. If you disable real-time profiling and do not specify an alternate means for pre-generated profiles, users will not be able to view any values or counts for any fields in this table. If you disable real-time profiling and provide pre-computed profiles for one or more fields, users will be able to access the pre-computed profiles, which is for the entire table. Users will not be able to profile only the values for the input cell of a process. To provide the greatest flexibility, you should allow real-time profiling.
Related Topics
To update pre-computed profiles for tables in a table catalog
N620001
To configure profiling
1. Check the fields for which you want Campaign to pre-compute distinct values and frequency counts. By default, Campaign stores the pre-computed profiles in the Campaign > partitions > partition[n] > profile category as data source_table name_field name. 2. If you have distinct values and counts stored in a separate database table that Campaign should use, click Configure Data Sources. Select Data pre-defined in a table, select the table name, the field containing the values, and the field containing the counts. Then click OK. 3. Check Allow real-time profiling to have Campaign update its records of values for the selected fields in real-time. This option allows users editing a flowchart to see the current values for these fields. However, it also requires a database query each time a user clicks Profile, which can potentially degrade performance.
N550001
1. Begin from the New Table Definition - Select the table type window. 2. Select the table to unmap.
Version 8.5.0 67
3. Click Unmap Table. You are prompted to confirm. 4. Click OK to unmap the table. You cannot reverse this process. To restore an unmapped table, you must map it as if for the first time, or import a stored table catalog that contains the mapped table definition. If you are uncertain about permanently unmapping a table, you can always save your current table mappings into a table catalog for later restoration if needed.
Related Topics
Working with table catalogs
N560001
68
h. Select the Audience Level for the new table and specify the audience level field in the new table. i. j. Click Next >. Optionally, select additional audience levels for the new table by clicking Add.
k. Click Next >. l. Define profiling for the new table. For more information, see Profiling values and counts.
m. Click Finish. 7. If you select to create a new file: a. Click Next >. b. Select Fixed-Width Flat File or Delimited File, then specify the Settings fields appropriately. c. Click Next >. d. Select the Source Table Fields to export to the new table or file. You can select from Campaign Generated Fields, the audience-level identifier, and fields from the input cell. Use the Add, Remove, Up, and Down buttons to define fields in the New Table Fields list. e. Click Next >. f. Select the Audience Level for the new table and specify the audience level field in the new table.
g. Click Next >. h. Optionally, select additional audience levels for the new table by clicking Add. i. j. Click Next >. Define profiling for the new table. For more information, see Profiling values and counts.
k. Click Finish.
Related Topics
To map a general table to a database table Profiling values and counts
N350001
Version 8.5.0
69
You can change information as needed in the file, making sure that the data that will be stored in the associated table can use the parameters you are setting.
N640001
70
The format and comment fields are not used by Campaign. Therefore, for the best results, use Unknown for the format value and to leave the Comment field blank.
N5F0001
To access table catalogs To open a table catalog To create a table catalog To load a stored table catalog Deleting table catalogs To update pre-computed profiles for tables in a table catalog To define a data folder for a table catalog
2. Click Manage Table Mappings. The Table Mappings window appears. 3. In the Table Mappings window, select Show User Tables. You can also access table catalogs from the Options menu while editing a flowchart.
N680001
72
If you leave Save with Database Authentication Information unchecked, anyone using this table catalog will need to provide a database login and password for any data sources referenced in the table catalog. These passwords may be already stored in their ASM user profile. If they do not already have a stored valid login and password, the user is prompted to provide them. This setting is the best practice for security purposes. If you check Save with Database Authentication Information, the current authentication information (the login[s] and password[s] you are currently using to access these data source[s]) are saved with the table catalog and anyone with access permissions to this table catalog will automatically be connected to the data sources using the authentication stored in the table catalog. This means that users of this table catalog will not need to provide a login or password to access these data sources and will have all the privileges of the stored login for reading and writing to the data source. You may want to avoid this setting for security reasons.
8. Select a folder in which to save the table catalog using the Save Under drop-down list. You can organize table catalogs in folders. Select an existing folder from the Items List, or click the New Folder button to create a new folder. If you do not select a specific folder, or choose None in the Save Under drop-down list, the current table catalog will be saved at the top level. The selected folder appears after the Save Under field. 9. Click Save. The table catalog is saved as a .cat file if no extension was provided with the name and in the location you have selected. If you specified a file name with a .xml extension, the table catalog is saved in XML format.
Related Topics
Working with user tables
N6A0001
2. Click Load. The Load Tables window opens. 3. Choose the appropriate option to select whether, when the tables are loaded, you want to clear or to overwrite the existing mappings. By default, the option to clear existing mappings is selected. 4. Click OK. The Stored Table Catalogs window opens. 5. Select the name of the table catalog that you want to load. When you click on the name of a table catalog, its information appears in the Info box and the Load Catalog button is enabled. 6. Click Load Catalog. The selected catalog is loaded. You see the details of the table(s) in the new catalog displayed in the Table Mappings window.
N400001
If you have selected a subset of tables, the Recompute Record Counts and List of Distinct Values for Selected Tables option is selected. The option to compute All Tables is available. If you have not selected any tables for computing and want to enable the option to compute values for selected tables, click Cancel on the Recompute window. The window closes and you are returned to the Table Mappings window, where you can select the tables for which you want the record counts and values to be computed. 4. When you are satisfied with your selection, click OK. When the computations are complete, you return to the Table Mappings window.
Related Topics
Profiling values and counts
N6B0001
Version 8.5.0
75
N102ED
4 Customizing Campaigns
N6C0001
About campaign customization Custom campaign attributes Custom cell attributes Custom offer attributes Working with custom attributes Custom initiatives Custom products
76
Related Topics
Standard offer attributes
N750001
Version 8.5.0
77
4 - Customizing Campaigns
When you create an offer template, you supply values for all static attributes. When a user creates an offer based on that template, the values you entered are used by default; the user can override these default values as needed. However, users cannot override values for static attributes when using the offer in a flowchart process. There are static attributes that are automatically included in all offer templates.
Related Topics
Default offer attributes
N770001
78
To add a custom attribute To modify a custom attribute Using offer custom attributes in offer templates Adding list values to the Channel attribute
Version 8.5.0
79
4 - Customizing Campaigns
e. From the Form Element Type list, select the type of data to be stored in the attribute field for offers or cells. After you add the custom attribute, you cannot change its data type. f. Depending on your selection, you may need to enter one of the following: Maximum String Length, if you selected Select Box - String or Text Field - String. This specifies the maximum number of characters that will be stored for any value of this custom attribute. Decimal Places, if you selected Text Field - Numeric or Text Field Currency. This specifies the number of decimal places to the right of the decimal point that are displayed.
If you select Text Field - Currency, be aware that the currency value reflects the number of decimal places customarily used in the local currency. Therefore, if you specify a number of decimal places less than the number commonly used, the currency value will be truncated. g. If you selected Select Box - String as the Form Element Type: Optionally check Allow addition of list items from within edit forms to enable any user to add new unique values to the attribute drop-down list when creating offers using the template containing the attribute. If any user adds a new value to the custom attribute, the value is subsequently displayed for all users. Enter possible selections for the field by entering values in the New or Selected Item field and clicking Accept . Values are presented to users in the order entered. You can delete values from the list by selecting one or more in the Source list of available values and clicking Remove.
5. When you have entered all the data for the custom attribute, click Save Changes.
N7B0002
80
3. Click the name of the custom attribute you want to modify. The Attributes Details window opens. 4. Modify data for the custom attribute as follows: a. If you are modifying a custom attribute that you created, you can edit the Attribute Display Name. If you are modifying one of the standard custom attributes, you cannot edit this field. b. If you are modifying a custom attribute that you created, you can edit the Internal Name. However, be aware that any uses of the internal name by existing flowcharts will cause an error, and you will receive a warning when you save the attribute. If you are modifying one of the default custom attributes, you cannot edit this field. Custom attribute internal names must be globally unique and are caseinsensitive. They have specific character restrictions and must start with an alphabetic character. For details, see About special characters. c. Optionally, modify the Description. d. If the attribute is a Select Box - String or Text Field - String field, you can modify the Maximum String Length. This specifies the maximum number of characters that will be stored for any value of this custom attribute. If you decrease the Maximum String Length of a String field when modifying an attribute, you receive a warning that existing data may be truncated. Decreasing the length of an existing custom attribute will truncate any data values longer than the new length, which can adversely affect response tracking if the field is used for matching purposes. e. If the attribute is a Text Field - Numeric or Text Field - Currency, you can modify the Decimal Places. This specifies the number of decimal places to the right of the decimal point that are displayed. For example, for currency, you may want to specify a decimal place value of two to show cents. If you decrease the Decimal Places number when modifying an attribute, if the attribute is used by offers or cells, the value for the attribute for those offers or cells as displayed through the web-based GUI is truncated to the new number of decimal places allowed. However, the value with the original number of decimal places is retained in the database. f. If the attribute is a Select Box - String, you can: Change the setting for Allow addition of list items from within edit forms. Modify list items.
You can only add or remove list items if the attribute was originally created with the Allow addition of list items from within edit forms option selected.
Version 8.5.0
Add list items by entering values in the New or Selected Item field and clicking Accept.
81
4 - Customizing Campaigns
Remove list items by selecting one or more items in the Source list of available values and clicking Remove. Edit an existing list item by selecting it in the Source list of available values. The item displays in the New or Selected Item field, where you can edit it and then click Accept.
5. When you have finished making your modifications, click Save Changes.
N710001
Custom initiatives
Campaign is delivered with a built-in attribute called Initiative. The Initiative attribute is a drop-down list on the campaign Summary tab. Initially, there are no values in the drop-down list; as an administrator, you define the initiatives to select from.
N7E0001
To add an initiative
You can add initiatives that users can select from the Initiative drop-down list in the campaign Summary tab. You add initiatives directly in the database table UA_Initiatives. 1. Access the Campaign system table database using your database management system. 2. In the database table UA_Initiatives, add values in the InitiativeName column. Each value can be a maximum of 255 characters. 3. Save the changes to the UA_Initiatives table.
N720001
Custom products
Users can associate an offer with one or more products. Product IDs are stored in the UA_Product table in the Campaign system table database. Initially, there are no records in this table. As an administrator, you can populate this table.
Related Topics
To add a product
N7F0001
To add a product
You can add products that users can associate with offers. You add products directly in the database table UA_Products. 1. Access the Campaign system table database using your database management system. 2. Locate the UA_Product table. The table is delivered with two columns:
82 IBM Unica Campaign - Administrator's Guide
Custom products
3. Optionally, modify the table to include additional columns. You may also delete the UserDefinedFields column. 4. Populate the table as necessary to include products that can be associated with offers. 5. Save the changes to the UA_Product table.
Version 8.5.0
83
N10357
Offer template concepts What is an offer? What is an offer template? Offer templates and security Why use offer templates? Planning offer templates and offers Working with offer attributes Working with offer templates Offer template references
What is an offer? What is an offer template? Offer templates and security Why use offer templates? What are offer custom attributes?
What is an offer?
An offer is the specific marketing communication that you send to particular groups of people, using one or more channels. An offer can be simple or complex, and typically contains a creative piece, a cost, a channel, and an expiration date. For example, a simple offer from an online retailer could consist of free shipping on all online purchases made in the month of April. A more complex offer could consist of a credit card from a financial institution, with a personalized combination of artwork, introductory rate, and expiration date that varied based on the recipients credit rating and region.
84 IBM Unica Campaign - Administrator's Guide
In Campaign, offers are: Based on an offer templates that you administer. Used in campaigns, where they are associated with target cells.
Associated offers are then delivered to customers identified in these target cells. You can also group offers into lists, and assign offer lists to target cells. Offer names and offer list names have specific character restrictions. For details, see About special characters.
N820001
Version 8.5.0
85
N850001
As a best practice, Unica recommends keeping parameterized values in offers to a minimum. Most offer attributes should not be parameterized. You should create parameters only for those attributes that will not change the essence of an offer, such as effective and expiration dates. You should carefully consider the design of your offers and offer templates, as this can have a significant effect on how you can analyze and report on your campaign details. For information on working with offers, see the Campaign Users Guide.
N860001
86
Version 8.5.0
87
Decimal Places, if you selected Text Field - Numeric or Text Field Currency. This specifies the number of decimal places to the right of the decimal point that are displayed.
If you select Text Field - Currency, be aware that the currency value reflects the number of decimal places customarily used in the local currency. Therefore, if you specify a number of decimal places less than the number commonly used, the currency value will be truncated. g. If you selected Select Box - String as the Form Element Type: Optionally check Allow addition of list items from within edit forms to enable any user to add new unique values to the attribute drop-down list when creating offers using the template containing the attribute. If any user adds a new value to the custom attribute, the value is subsequently displayed for all users. Enter possible selections for the field by entering values in the New or Selected Item field and clicking Accept . Values are presented to users in the order entered. You can delete values from the list by selecting one or more in the Source list of available values and clicking Remove.
5. When you have entered all the data for the custom attribute, click Save Changes.
N7B0002
88
b. If you are modifying a custom attribute that you created, you can edit the Internal Name. However, be aware that any uses of the internal name by existing flowcharts will cause an error, and you will receive a warning when you save the attribute. If you are modifying one of the default custom attributes, you cannot edit this field. Custom attribute internal names must be globally unique and are caseinsensitive. They have specific character restrictions and must start with an alphabetic character. For details, see About special characters. c. Optionally, modify the Description. d. If the attribute is a Select Box - String or Text Field - String field, you can modify the Maximum String Length. This specifies the maximum number of characters that will be stored for any value of this custom attribute. If you decrease the Maximum String Length of a String field when modifying an attribute, you receive a warning that existing data may be truncated. Decreasing the length of an existing custom attribute will truncate any data values longer than the new length, which can adversely affect response tracking if the field is used for matching purposes. e. If the attribute is a Text Field - Numeric or Text Field - Currency, you can modify the Decimal Places. This specifies the number of decimal places to the right of the decimal point that are displayed. For example, for currency, you may want to specify a decimal place value of two to show cents. If you decrease the Decimal Places number when modifying an attribute, if the attribute is used by offers or cells, the value for the attribute for those offers or cells as displayed through the web-based GUI is truncated to the new number of decimal places allowed. However, the value with the original number of decimal places is retained in the database. f. If the attribute is a Select Box - String, you can: Change the setting for Allow addition of list items from within edit forms. Modify list items.
You can only add or remove list items if the attribute was originally created with the Allow addition of list items from within edit forms option selected. Add list items by entering values in the New or Selected Item field and clicking Accept. Remove list items by selecting one or more items in the Source list of available values and clicking Remove. Edit an existing list item by selecting it in the Source list of available values. The item displays in the New or Selected Item field, where you can edit it and then click Accept.
5. When you have finished making your modifications, click Save Changes.
Version 8.5.0 89
Attribute Internal Name AverageResponseRevenue ChannelType Channel CostPerOffer ExpirationDuration EffectiveDate ExpirationDate FulfillmentCost
Form Element Type Text Field - Numeric Select Box - String Select Box - String Text Field - String Text Field - Numeric Text Field - Date Text Field - Date Text Field - Currency
Before beginning to work with offer templates, you should create the custom attributes you anticipate needing. Working with offer templates requires the appropriate permissions, including permission to view offer templates. For example, to add offer templates, you must be granted both the Add Offer Templates and View Offer Templates permissions. For information on setting permissions, see Managing Security in Campaign.
Related Topics
About campaign customization
N890001
90
If you have added the Offer Valid/Expiration Dates attribute to the template as a parameterized attribute, on this screen you are presented with a Flowchart run date option. If you select this option instead of entering a default Offer Valid date, Campaign uses the date on which the process using offer runs, not the run date of the entire flowchart. 10. If you selected Allow offers created from this template to be used in real-time interactions, enter an Interaction Point ID and an Interaction Point Name. You can enter any integer for the Interaction Point ID default value, and any string for Interaction Point Name. The values are automatically populated with the correct data by the runtime environment, however, the design environment requires a default value. 11. Click Finish. You have created the offer template. It can now be used for creating offers.
Related Topics
Offer templates and security Template icons
N8A0001
92
If the offer template is currently used by an offer, you cannot change settings for offer attributes. If the template is not being used, you can modify the attributes in the offer template as needed. Use the arrow buttons (<< and >>) to move attributes into and out of the attribute list for the offer template, and to change the order and type (static, hidden, or parameterized) of included attributes. 6. Click Next >>. The New Offer Template Step 3 of 3: Default Valueswindow opens. 7. For attributes in the offer template, supply a default value. When creating offers, users can change the default value of static and parameterized attributes. However, users cannot change the value you enter for hidden static attributes. If you have added the Offer Valid/Expiration Dates attribute to the template as a parameterized attribute, on this screen you are presented with a radio box Flowchart run date. If you select this option instead of entering a default default Offer Valid date, Campaign uses the date the process that uses the offer runs, not the entire flowchart. 8. Click Finish. You have modified the offer template.
Related Topics
Offer templates and security Template icons About campaign customization
N8B0001
4. To change the order of offer templates, select one template at a time and click the up or down icons to move that templates location in the list. 5. When the offer templates are in the desired order, click Save Changes.
N8C0001
94
Template icons
You select a template icon as part of the basic options when you create or modify an offer template. The template icon serves as a visual clue about the offer template when users create new offers. The following table lists and shows the available template icons:
Icon Name offertemplate_default.gif Icon
offertemplate_manychans.gif
offertemplate_manydates.gif
offertemplate_manyresp.gif
offertemplate_manysegs.gif
offertemplate_repeatingtabl.gif
offertemplate_simpleemail.gif
Version 8.5.0
95
offertemplate_simplephone.gif
offertemplate_versions.gif
N760001
96
N103E6
About audience level administration About audience levels Why different audience levels are needed in Campaign The default Customer audience level Creating additional audience levels About audience levels and system tables About audience levels and user tables Working with audience levels About global suppressions and global suppression segments
Create the audience levels needed for your companys campaigns. Create database tables in the Campaign system database to support the new audience levels. Map system tables to the supporting database tables for the new audience levels in the Campaign system database. Specify audience levels and associated database fields when mapping user tables. Create global suppression segments for one or more audience levels.
Version 8.5.0
Customer is next in the hierarchy, and each customer can have multiple accounts. Account is at the bottom of the hierarchy.
Other, more complex examples of audience hierarchies exist in business-to-business environments, where audience levels may need to exist for businesses, companies, divisions, groups, individuals, accounts, and so on. These audience levels may have different relationships with each other, for example one-to-one, many-to-one, or many-to-many. By defining audience levels, you allow these concepts to be represented within Campaign so that users can manage the relationships among these different audiences for targeting purposes. For example, although there might be multiple prospects per household, you might want to limit mailings to one prospect per household. An audience level is composed of a fixed number of keys or database table fields, which together uniquely identify a member of that audience level. For example, the audience level Customer might be identified by a single IndivID field or by a combination of a HouseholdID field and a MemberNum field. For more details about audience levels, see the section on the Audience process in the Campaign Users Guide.
N910001
For more details about audience levels, see the section on the Audience process in the Campaign Users Guide.
N920001
98
Related Topics
Default Customer audience level system tables Mapping Customer audience level system tables
N930001
These system table entries are automatically created when you create the audience level. You must then: Create the physical database tables in the Campaign system table database. Map these system tables to the database tables. IBM recommends that you map the segment membership table only if you are using strategic segments with Campaign flowcharts or Optimize sessions in Optimize.
Related Topics
Required fields in audience-level-specific tables Task 3: Map the Unica system tables to the database tables
N980002
Version 8.5.0
99
If these tables are mapped as listed above, then the sample reports provided with Campaign will work with a minimum number of changes. The SQL statements used to create these tables and their related indices can be used as templates to create tables for other audience levels.
Related Topics
Creating additional audience levels
N9C0002
100
The field names (and in particular any unique identifier field names) in the new audience level must exactly match the field name(s) in the database table for mapping. This allows Campaign to automatically match the database fields to the appropriate system table fields when you create the audience level. Audience level field names have specific character restrictions. For details, see About special characters
Related Topics
Workflow for setting up a new audience level
N9A0001
Required fields in the contact history table Required fields in the detailed contact history table Required fields in the response history table Required fields in the segment membership table
Version 8.5.0
101
Key No No No No No
Length 8 8 8 8 8
Campaign is shipped with additional fields (ValueBefore and UsageBefore) in the UA_ContactHistory table for the Customer audience level to support the example reports. You can define your own additionally tracked fields for contact history and customize reports as needed.
Related Topics
Audience level unique identifiers
N9F0001
Key Yes No No No No No No
Column Name Identifier for audience level TreatmentInstID ContactStatusID ContactDateTime UpdateDateTime DateID TimeID
Data Type numeric or text bigint bigint datetime datetime bigint bigint
Length
Allow Nulls No
8 8 8 8 8 8
Related Topics
Audience level unique identifiers
102
Each response history table you create for a new audience level should have a foreign key constraint on the UA_Treatment table's TreatmentInstID field.
Related Topics
Audience level unique identifiers
NA10002
Version 8.5.0
103
Length 8
Allow Nulls No No
Related Topics
Audience level unique identifiers
N950001
User tables with a single audience level User tables with multiple audience levels
In this table, the Acct_ID might be unique for each record. Because an individual could have multiple accounts, and a household could contain multiple individuals, multiple records could have the same values for the Indiv_ID and HHold_ID fields. Assuming you have three audience levels, Account, Customer, and Household, when you map this user table, you could specify all three of these audience levels and associate them with the corresponding fields listed above in the user table. This enables flowchart designers to switch target audiences, or scope one audience level by another (for example, accounts per customer, customers per household, or accounts per household) when using this table.
Related Topics
Working with user tables
N960001
Task 1: Create the required database tables for each new audience level Task 2: Create the new audience levels in Campaign Task 3: Map the Unica system tables to the database tables Task 4: Map the user tables containing relevant data to the appropriate audience level(s) Task 5: Save the mapped tables in a table catalog
Task 1: Create the required database tables for each new audience level
You must create physical database tables in the Campaign system database to support each new audience level(s) you create. The required tables for each audience level are: A contact history table A detailed contact history table
105
Version 8.5.0
Each required table has a set of required fields. You can create additional custom fields in your audience tables. You should create indices on the tables you create. For example, if you create the INDIV_ContactHistory table for a new Individual audience level, you could create an index as follows: CREATE INDEX XIE1INDIV_ContactHistory ON INDIV_ContactHistory ( IndivID ).
106
Audience level field names have specific character restrictions. You must specify exactly the same names as the field names in the database tables for this audience level. Fields can only be mapped in Task 3: Map the Unica system tables to the database tables, if Campaign finds an exact match for the field names. For example, if you are creating the new audience level Household and you specify one field for unique audience level identifier called HouseholdID, you must make sure the ID field in your audience level-specific database tables matches this exactly; in other words, that it is also named HouseholdID. 6. Click OK. In the Audience Levels window, when you select the new audience level, you see the required tables listed as Not Mapped. You perform the mapping in Task 3: Map the Unica system tables to the database tables.
Related Topics
About special characters
N9B0002
Version 8.5.0
107
5. On the table mapping window, select the database table corresponding to the Unica system table for that audience level. The Source Table Fields list is populated with the fields from the database table you selected. The Required Fields list is populated with Selected Fields (from your source database table) and the corresponding Required Fields (from the Unica system table). Fields can only be mapped if Campaign finds an exact match for the field names. 6. Click Next to specify mapping for any custom fields in your database tables. 7. Click Next to specify display names for custom fields. This option is not available for all tables. 8. Click Finish to complete the mapping. Repeat this procedure for each required Unica system table for the audience level. You can also perform this task from the Manage Table Mappings link on the Campaign Settings page.
Related Topics
To map or re-map a system table
NA70001
Task 4: Map the user tables containing relevant data to the appropriate audience level(s)
When you map a user table, you must specify one primary audience level. You can also specify one or more alternate audience levels. For each audience level, map to the user table containing the identifier for the entity at that audience level.
Related Topics
Working with user tables About audience levels and user tables
NA80001
108
Version 8.5.0
109
You do this by creating this list of unique IDs as a strategic segment, then by specifying that segment as a global suppression segment for a particular audience level. Only one global suppression segment can be configured for each audience level. If a global suppression segment has been configured for an audience level, all top-level Select, Extract, or Audience processes associated with that audience level automatically exclude the IDs in the global suppression segment from their output results, unless the global suppression is explicitly disabled for a specific flowchart. By default, flowcharts have global suppression enabled so that no action needs to be taken for any configured global suppression to be applied. For details about disabling global suppressions, see the Campaign Users Guide. An exception to the default of global suppression being enabled is the flowchart containing the CreateSeg process that created the global strategic segment itself. In this case, the global suppression is always disabled (only for the audience level for which the global suppression segment is created).
NAA0001
Creating the global suppression segment in a flowchart Specifying the segment as a global suppression segment
110
You should specify all data sources where the global strategjc segment is commonly used. If the strategic segment is not persisted in a data source, then the suppression is done on the Campaign server using the binary file. If the CreateSeg process is unable to create the strategic segment or write the segment to any of the specified data sources, it will be unconfigured or fail when run. Changes to the temp table data sources are made at the time you save the process configuration, not when the flowchart is saved or run. 4. Click OK. On the Define Segments tab, you see that the data source you selected is displayed in the Temp Table DS column for the current segment.
NAD0002
Version 8.5.0
111
The best practice for creating or updating global suppression segments is to do this when no flowcharts at the same audience level are running (and thus potentially using the segment(s)). The consistency of suppression lists cannot be guaranteed if global suppression segments are created or updated while flowcharts are using them.
NAF0001
112
N104DB
Before you begin working with contact history Contact history concepts Working with contact history Default contact status codes
What is contact history? What is detailed contact history? What is contact status? About updating contact status How does contact history relate to audience levels? How does contact history relate to database and system tables? What is offer history? What is treatment history?
Version 8.5.0
113
Related Topics
What is treatment history?
NB70001
Version 8.5.0
115
Related Topics
About audience level administration
NBA0001
For example, a typical flowchart results in a list of targeted customers, output through a Call List or Mail List process. A record of the offer(s) made in that flowchart are written to the UA_OfferHistory table offer history. If users turn off contact history logging in the Call List or Mail List process, offer history made in that process is not written to the database. Offer history is written to the database for production runs only, not test runs. Offer history is not stored in separate tables by audience level; all offer history is stored across the same set of system tables.
NBC0001
116
Creating contact history tables for new audience levels Mapping contact history tables to Unica system tables To add a contact status code Logging history Updating contact history Clearing contact history
Version 8.5.0
117
When you create these tables, you must create indexes on them. For example, if you create the INDIV_ContactHistory table for a new Individual audience level, you could create an index as follows: CREATE INDEX XIE1INDIV_ContactHistory ON INDIV_ContactHistory ( IndivID )
Related Topics
Required fields in the contact history table Required fields in the detailed contact history table
NBF0001
e. In the CountsAsContact column, enter 1 if the status represents a successful contact, or 0 if it does not. This column is used by Optimize for managing contact fatigue. It also may be useful for queries against the contact history table to suppress individuals who have received a specific number of contacts within some time period. f. In the Defaults column, enter 0 if that status is not to be the default, or 1 if it is. Enter 2 for the default status for control cells. Ensure that only one row was the value 1 and one row has the value of 2 in this column.
4. Save the table changes. If necessary, see the documentation for your database management system for detailed instructions on modifying data in tables.
Related Topics
Default contact status codes
NC00001
Logging history
To log contact history, users configure one or more contact processes (Call List or Mail List). Then, when the flowchart is run (in production, not test mode), contact history is written to the table(s) related to the audience-level(s) used in the flowchart. When logging to contact history is enabled, offer and treatment history are written as well. If the process is configured to log contact history, but runs on a cell with no selected targets, no records history records are written. Users can optionally choose to not have contact history logged by the Call List or Mail List process. For more information, see the Campaign Users Guide.
NC10001
Version 8.5.0
119
0 1 0 2
120
N1055B
Before you begin working with response history Response history concepts Working with response history Response history references
What is response history? What is the response type? How does response history relate to audience levels? How does response history relate to database tables? Foreign key constraints in response history tables What is an action table? What does an action table contain? Why use an action table?
121
Version 8.5.0
122
Related Topics
About audience levels and system tables
NCB0001
Version 8.5.0
123
Creating response history tables for new audience levels Mapping response history tables to Unica system tables To set the number of days after an offer expires to record responses To add a response type Logging response history
124
Version 8.5.0
ResponseTypeID 1 2 3 4 5 6 7
ND10001
Name
Description
Counts- AsResponse 0 0 1 0 0 0 1
IsDefault
0 0 0 0 0 0 1
Length 8 8
Allow Nulls No No
126
Column Name ResponseChannel CampaignCode OfferCode CellCode TreatmentCode ProductID ResponseTypeCode Related Topics
What is an action table?
Length 16 32 64 64 64 8 64
Version 8.5.0
127
N105E3
9 Operational Monitoring
ND60001
About operational monitoring To configure operational monitoring To access the All Monitored Runs page Viewing the All Monitored Runs page To sort the list of flowcharts on the All Monitored Runs page Working with flowcharts through the All Monitored Runs page Operational monitoring references
128
To reverse the sorting order, click the column name again. If you leave the All Monitored Runs page and return to it, the flowcharts are listed in the default sort order (ascending by campaign name).
NDE0001
Version 8.5.0
129
9 - Operational Monitoring
The flowchart stops. Its status on the All Monitored Runs page changes to Stopped and the status indicator color changes to red.
NE10001
130
The suspend process starts. The flowcharts status on the All Monitored Runs page changes to Suspending and the color of the status indicator changes to yellow. In Suspending status, you cannot perform any actions on a flowchart. It may take a while to successfully suspend a running flowchart, because it must wait until running process boxes reach a state where they can be safely saved and resumed. When the suspend process completes, the flowcharts status changes to Suspended; the color of the status indicator remains yellow.
NE20001
The flowchart resumes running. Its status on the All Monitored Runs page changes to Running and the color of the status indicator changes to green.
NDC0001
Version 8.5.0
131
9 - Operational Monitoring
Description
Valid Actions
Suspend Stop
The flowchart was paused during running from the flowchart Run menu. (You cannot pause a flowchart from the Monitoring page.) When a flowchart is paused, the process remains intact but stops processing, guaranteeing that no work is lost when the flowchart run is continued. Note that with the Pause action, system resources are not released (CPU utilization stops, but memory is not freed). You can continue running a paused flowchart from the flowchart Run menu. For details about pausing and continuing a flowchart run, see the Campaign Users Guide.
Suspending (Yellow)
The flowchart Suspend action has been initiated from the Monitoring page and the flowchart is transitioning to this status.
None
132
Description
Valid Actions
The flowchart Suspend action has completed and the flowchart is in a suspended state. The process is shut down and system resources have been released; a placeholder remains to enable restarting the flowchart run at the point at which it was suspended. You can resume running a suspended flowchart using the Resume button on the Monitoring page. Running process boxes that can be rerun from the beginning, resulting in the same net behavior, are immediately stopped when the Suspend command is issued, and any partially completed work is lost. These process boxes will be re-run when the flowchart run is resumed.
Resume
None
The flowchart run was stopped either by a user None from the flowchart Run menu or due to an error (that is, one or more process boxes in the flowchart encountered an error). For details about stopping a flowchart from the flowchart Run menu, see the Campaign Users Guide. The run failed due an unhandled error or a server error (that is., the flowchart server process exited unexpectedly). None
Failed (Red)
NE40001
Version 8.5.0
133
9 - Operational Monitoring Icon Name Print this Item Description Select one or more monitored runs by clicking the checkbox next to each item, then click this icon to print the selected item(s). Click this icon to refresh the list of monitored runs on the page.
Refresh
134
N10647
Dimension hierarchy concepts What is a dimension hierarchy? Why use dimension hierarchies? About dimension hierarchies and cubes About dimension hierarchies and database tables Working with dimension hierarchies
What is a dimension hierarchy? Why use dimension hierarchies? About dimension hierarchies and cubes About dimension hierarchies and database tables
Version 8.5.0
135
You cannot split a lower level bin (for example, bin 26-30 above) and divide individuals aged 26-27 into young and 28-30 into middle, when rolling up to a higher level. Any single bin in a lower level must fall completely within a higher level bin. If you wanted to actually define young as those aged 21-27, you would need to create separate bins (for example, 26-27 and 28-30) in the lower level so they could roll up into young and middle, respectively. Other commonly specified dimension hierarchies are time, geography, product, department, and distribution channel. However, you can create any kind of dimension hierarchy that relates to your business or campaign.
NE70001
Dimensions that are comprised of an unlimited number of levels and elements Data points built as input to customer analytic reporting and visual selection Rollups into unlimited number of categories to support drill-down capability
Each level in the dimension hierarchy The raw SQL or Unica expression that defines the audience entities in the bin The data source
For example, the Age dimension hierarchy has three levels. The first level is All ages; below this are the two levels shown in the two levels of the following list: Under 30 Under 20 20 to 25 26 to 30
30 to 50 30 to 40 41 to 50
Over 50 51 to 60 Over 60
Under 30 Under 30
< 20 Years Old 20 - 25 Years Old 26 - 30 Years Old 30 - 40 Years Old 41 - 50 Years Old 51 - 60 Years Old Over 60
age < 20
Your datamart
age between 20 Your datamart and 25 age between 26 Your datamart and 30 age between 31 Your datamart and 40 age between 41 Your datamart and 50 age between 51 Your datamart and 60 age > 60 Your datamart
MemberAge
All Ages
Under 30
MemberAge
All Ages
30 - 50 Years
MemberAge
All Ages
30 - 50 Years
MemberAge
All Ages
Over 50
MemberAge
NEA0001
All Ages
Over 50
Version 8.5.0
137
About working with dimension hierarchies Designing dimension hierarchies Accessing dimension hierarchies in Campaign To create a dimension hierarchy To load a stored dimension hierarchy To edit a dimension hierarchy To update a dimension hierarchy To remove a dimension hierarchy
When this dimension hierarchy is mapped into Campaign, the dimension hierarchy is available in a Cube process for building dynamic data cubes on strategic segments. You or a Unica consulting team must create the dimension hierarchy definition in the data mart or flat file. This is an operation external to Campaign. Also, the lowest level of the dimension hierarchy must use either raw SQL or a pure Unica expression (no custom macros, user variables, or derived fields) to define the individual audience ID membership for each bin.
NEC0001
How dimensions relate to each other (for example, Age/Geography/ Timespan). Level of detail for each dimension and cube. Dimensions are not limited to a single cube; they can be used in many cubes. Dimensions must roll up cleanly across boundaries, so elements must be mutually exclusive and not overlap.
When editing a flowchart, by clicking the Admin icon and selecting Dimension Hierarchies. Through the Campaign Settings page, by clicking Manage Dimension Hierarchies. When dimension hierarchies are used to create cubes, we recommend that you use the Cube process to create dynamic data cubes from a flowchart in the Sessions area of the application.
NEE0001
4. Click Map Table. The Edit Table Definition window opens. 5. To map your dimension hierarchy table to either a table in the database or a flat file containing the dimension hierarchy definition, follow the instructions in To map a base record table to an existing database table. After you finish mapping your dimension hierarchy, you return to the Edit Dimension window, which now includes details for the new dimension hierarchy. 6. Click OK. You return to the Dimensions window.
Version 8.5.0
139
7. (Optional but recommended) You can store a dimension hierarchy for future use in a table catalog by clicking Save. If you store a dimension hierarchy you can retrieve it later for another use or share it with other users rather than recreating it.
Related Topics
Accessing dimension hierarchies in Campaign Working with table catalogs
NEF0001
6. To modify the table mapping, click Map Table. The Edit Table Definition window opens.
140
7. Follow the instructions in To map a base record table to an existing database table. 8. After you finish mapping your dimension, you return to the Edit Dimension window, which now includes details for the new dimension hierarchy. 9. Click OK. You return to the Dimensions window. 10. (Optional but recommended) You can store your changes to any dimension hierarchies for future use in a table catalog by clicking Save.
Related Topics
Accessing dimension hierarchies in Campaign To load a stored dimension hierarchy
NF10001
Version 8.5.0
141
142
N106AA
11 TriggerAdministration
NF30001
About triggers in IBM Unica Campaign What is an inbound trigger? What is an outbound trigger? How are triggers defined? Working with trigger folders and triggers Setting up outbound triggers Setting up inbound triggers Setting up the trigger utility on a remote Windows machine Reference information for trigger administration
Version 8.5.0
143
11 - Trigger Administration
NFD0001
A predictive model updating its scores in the database triggers an acquisition campaign, which is waiting for the latest scores, to run. A third-party scheduling tool is used to schedule and trigger the execution of flowcharts. The run completion of Optimization session triggers the execution of the participating campaigns to retrieve and process their optimized results.
What is broadcasting?
Broadcasting is the process of notifying all flowcharts in Campaign, specific campaigns, or specific flowcharts that an inbound trigger has executed. Schedule processes configured to listen for that inbound trigger then execute. To send an inbound trigger to a campaign or flowchart, you must broadcast the triggers to Campaign using the trigger utility, CAMPAIGN_HOME /bin/unica_actrg.exe.
Related Topics
Setting up inbound triggers
NF50001
144
Related Topics
Setting up outbound triggers
N1000001
Version 8.5.0
11 - Trigger Administration
N1030001
To create folders to organize triggers To move a trigger folder To edit a trigger folder To delete a trigger folder To create a trigger To edit or move a trigger To delete a trigger
146
5. In the Create Under drop-down list, select the folder in which to create the new folder, or select None to create a top-level folder. 6. If you are creating a top-level folder, select a security policy. A sub-folder automatically inherits its security policy from its parent folder. 7. Click Save.
Related Topics
About security in IBM Unica Campaign
N1050001
Version 8.5.0
147
11 - Trigger Administration
6. In the Create Under drop-down list, select the folder under which you want to move the selected folder, or select None to make the folder a top-level folder. 7. If you are editing a top-level folder, select a security policy. A sub-folder automatically inherits its security policy from its parent folder. 8. Click Save.
Related Topics
About security in IBM Unica Campaign
N1070001
To create a trigger
You must have permissions to create triggers. 1. When editing a flowchart, select Tools > Stored Triggers. The Stored Trigger Definitions window opens. 2. Click New Item. The data fields for the new trigger appear on the right of the window. 3. Optionally, select a folder to save the trigger to in the Save Under drop-down list. The folder location you select governs which users can access the trigger, based on the folders security policy. 4. Enter a name for the trigger in the Name field.
148
You cannot use spaces in the string, but you can use underscores (_). This name must be unique within the folder where you save it.
IBM Unica Campaign - Administrator's Guide
5. If you are creating a trigger in the top-level folder, select a security policy, or keep the default. 6. Optionally, enter a description of the trigger in the Note field. You can provide a free-form text description of the trigger for documentation purposes. You also may want to keep a modification history of who modified the trigger, when, and what changes were made. 7. In the Command field, enter the path relative to the current partition root and filename of the executable file on the Campaign server. You can click Browse to visually select the executable file from within the current partition. If you are creating an outbound trigger, to make it synchronous, terminate the command with a question mark (?). To make the trigger asynchronous, do not terminate the command with a special character, or use an ampersand (&). 8. Click Save to save the trigger. 9. Click Close to exit the Stored Trigger Definitions window.
Related Topics
About security in IBM Unica Campaign
N1090001
Version 8.5.0
149
11 - Trigger Administration
If you change the trigger name, any processes referring to that trigger will become unconfigured and will be unable to run. You will need to edit each process to refer to the new trigger name. 6. If you are modifying a trigger in the top-level folder, or moving a trigger to the toplevel folder, select a security policy, or keep the default. 7. Optionally, modify the description of the trigger in the Note field. 8. Optionally, in the Command field, modify the path relative to the current partition root and file-name of the executable file on the Campaign server. You can click Browse to visually select the executable file from within the current partition. If you are creating an outbound trigger, to make it synchronous, terminate the command with a question mark (?). To make the trigger asynchronous, do not terminate the command with a special character, or use an ampersand (&). 9. Click Save to save the trigger. 10. Click Close to exit the Stored Trigger Definitions window.
Related Topics
About security in IBM Unica Campaign
N10A0001
To delete a trigger
You must have permissions to delete triggers. If you delete a trigger, any processes referring to that trigger will become unconfigured and will be unable to run. You must edit each process to remove the reference to the deleted trigger. 1. When editing a flowchart, select Tools > Stored Triggers. The Stored Trigger Definitions window opens, displaying all triggers defined within the current Campaign partition. 2. Locate and select the trigger to delete in the Items List. 3. Click Remove. You are prompted to confirm the deletion. 4. Click OK to delete the trigger. 5. Click Close to exit the Stored Trigger Definitions window.
Related Topics
About security in IBM Unica Campaign
NF80001
150
Related Topics
About security in IBM Unica Campaign
N10B0001
In the Schedule tab, you specify the trigger(s) to execute Schedule tab. In the Call List and Mail List processes, you specify the trigger(s) to execute in the Fulfillment tab. For information on configuring these processes, see the Campaign Users Guide.
N10C0001
Version 8.5.0
151
11 - Trigger Administration
To broadcast a trigger to all flowcharts of a campaign To broadcast a trigger to a flowchart To broadcast a trigger to all campaigns
152
The Schedule process may also be configured to execute based on other conditions. Configuring the trigger condition will additionally execute the subsequent processes when the specified triggers are received. For a flowchart to run upon receipt of an inbound trigger, it must have a Schedule process configured as described above, and it must be running. Running the flowchart puts the flowchart into a waiting, or listening, state so that the flowchart is ready to execute when the trigger is received. A flowchart that is not running when the trigger is broadcast will not execute. For more information about configuring the Schedule process, see the Campaign Users Guide.
N10F0001
Version 8.5.0
153
11 - Trigger Administration
The trigger is broadcast only to all running flowcharts with the specified name. If the flowchart of the specified name starts with a Schedule process configured to run when receiving a broadcast based on the web_hit inbound trigger, that flowchart runs when the broadcast trigger is received.
N1110001
154
config.xml
Tokens supported by triggers Syntax for the Unica Trigger Utility Order of parameters for the Unica Trigger Utility
<CAMPCODE>
Version 8.5.0
11 - Trigger Administration Token <CONTACTLIST> Description Contact list specified in a contact process. If the Contact List is written to a file, the appropriate full path name and file name replace the trigger token. If the Contact List is written to a database table, the token is simply removed. <CONTACTLOG> The log of the particular contact process. When the Log is written to a file, the appropriate full path name and file name replace the trigger token. <FLOWCHARTFILENAME Full path name of a flowchart's .ses file Processes that support outbound > triggers. <IXUSER> The user name of the Distributed Marketing user. Processes that support triggers, trigger on failure, trigger on success. Select process Call List and Mail List processes. Where Used Call List and Mail List processes.
<OUTPUTTEMPTABLE>
A token for use in raw SQL in pre- and post-processing under the Advanced window to create a temp table. For example:Create <OUTPUTTEMPTABLE> as SELECT CustIDs from CustomerTable WHERE ... The Marketing Platform security user name of the user who created the flowchart. The name of the current process box. The ID of the current process box. The ID of the current flowchart.
<OWNER>
Processes that support triggers, trigger on failure, trigger on success. Processes that support triggers. Processes that support triggers. Processes that support triggers, trigger on failure, trigger on success. Processes that support triggers, trigger on failure, trigger on success.
<SESSIONNAME>
156
Reference information for trigger administration Token <UserVar. UserVarName > Description Any user variable value. The user variable must be defined in current flowchart. Where Used Processes that support triggers, trigger on failure, trigger on success.
N1150001
Version 8.5.0
157
N107A3
12 Logging Administration
N1160001
About logging The Campaign Listener log The Campaign web application log Flowchart logs The sessions log The web connections log Windows event logs The log4j log file Working with logs
About logging
Campaign can provide you with four different types of logs:
N1170001
The Campaign Listener log The Campaign web application log Flowchart logs The sessions log The web connections log Windows event logs (when the Campaign server is installed on Windows) The log4j log file
158
The number of logs retained and the maximum size of each log depend on the value of the Applications>Campaign>unicaACListener>logMaxBackupIndex and the Applications>Campaign>unicaACListener>logMaxFileSize properties, respectively.
Related Topics
Campaign Listener logging tasks
N1180001
Flowchart logs
Each campaign flowchart generates flowchart-specific logging information when it is run. The log is in a file called campaign_name__campaign_code__flowchart_name.log. By default, this log file is located in the Campaign_home /partitions/ partition_name /logs directory. However, when you are editing a flowchart you can customize the log location by clicking the Options menu and selecting Change Log Path. Note that you cannot select Change Log Path unless AllowCustomLogPath is enabled in the Campaign properties.
Related Topics
Flowchart logging tasks
N11A0001
Version 8.5.0
159
12 - Logging Administration
Applications > Campaign > unicaACListenter > enableWindowsEventLogging, for the Campaign listener. Applications > Campaign > partitions > partition_name > server > logging > enableWindowsEventLogging, for flowcharts in that partition.
Campaign Listener logging tasks Campaign web application logging tasks Flowchart logging tasks Windows event logging tasks
160
Configuring Campaign Listener logging Viewing the Campaign Listener log file
Configuring Campaign web application logging Changing the filename and location of the Campaign web application log
12 - Logging Administration
N1260001
To change the file name and location of the Campaign web application log
To complete this task, you must have appropriate permissions to use Marketing Platform. For information, see the Marketing Platform Administrator's Guide. On the Configuration page, modify the value of the log4jConfig property in the Campaign > logging category to specify location and name for the file used to define the properties of the Campaign web application log.
N1210002
Configuring flowchart logging Enabling or disabling flowchart logging Modifying flowchart logging levels Customizing the flowchart log file location Viewing flowchart log files Clearing a flowchart log file
allowCustomLogPath enableLogging enableWindowsEventLogging keepFlowchartLogOpen logFileBufferSize loggingCategories loggingLevels logMaxBackupIndex logMaxFileSize logProcessId
IBM Unica Campaign - Administrator's Guide
N1280001
windowsEventLoggingCategories windowsEventLoggingLevels
Because log files can grow quickly when informational or debugging messages are logged, it is recommended that you clear these options unless debugging. 3. Check the message categories to log. 4. Check Include the Process ID in Log Entries to have the process ID included for each entry. 5. Click OK to save the settings.
N12B0001
Version 8.5.0
163
12 - Logging Administration
Configuring Windows event logging for the Campaign listener Configuring Windows event logging for flowcharts
For information on the properties, see the context help or the Marketing Platform Administrator's Guide.
N1300001
For information about changing log4j property settings, see the following sources: The comments in the campaign_log4j.properties file. The log4j documentation on the Apache web site: http://logging.apache.org/log4j/1.2/manual.html After you change values in the campaign_log4j.properties file, you must restart the IBM Unica Campaign web application.
N1320001
Version 8.5.0
165
N10862
About codes in Campaign About campaign codes About offer codes About cell codes About treatment codes Code formats About code configuration properties About code generators About custom code generators About creating custom code generators Code generation references
Set configuration parameters to control how each type of code is generated, and valid formats for codes. Create and set up a custom code generator if the default generators do not meet your needs.
166
When users create a campaign, the Campaign Code field is automatically populated with a unique value from the code generator. Users can click Regenerate code to have the code generator supply a new identifier, or they can enter a code manually. If users manually enter a code, it must be unique and in the specified format.
Related Topics
Code formats Default code formats To change the campaign code format
N1350001
Whether cell codes must be unique within a flowchart depends on the setting of the AllowDuplicateCellCodes configuration parameter (described in Code generation references). If the value of AllowDuplicateCellCodes is No, cell codes must be unique within a flowchart; the same cell code can still exist in different flowcharts and campaigns. If the value of AllowDuplicateCellCodes is Yes, cell codes within a single flowchart do not have to be unique. If duplicate cell codes are not allowed and a user enters a cell code that is already used elsewhere in the same flowchart, no error is immediately generated. However, users can validate flowcharts and detect duplicate cell codes using the flowchart validation tool if duplicate cell codes are not allowed. For information on flowchart validation, see the section on Validating Flowcharts in the Campaign Users Guide. Automatically generated cell codes are guaranteed to be unique only if no user ever overrides any cell code. For more information about working with cells, see the Campaign Users Guide.
Related Topics
Code generation references Code formats Default code formats To change the cell code format
N1370001
168
Code formats
Code formats
The default and valid format for each type of generated code uses a series of characters to represent the character types. The following table lists the characters you can use to control code formats.
Any uppercase letter A-Z Any uppercase letter A-Z, or any number, 0-9 Any uppercase letter A-Z, any number 0-9. However, users can replace the generated character with any ASCII character. To specify variable length codes, the code format must end with one or more " x" characters, and the allowVariableLengthCodes property must be set to " yes".
Example
Format definition CAMP_aaannn Example of generated code CAMP_DWP839 (CAMP_, followed by three randomly generated capital letters, then three randomly generated numeric digits) Related Topics
Properties related to code generation
N13E0001
Version 8.5.0
169
Where Defined campCodeFormat parameter on the Marketing Platform Configuration page cellCodeFormat parameter on the Marketing Platform Configuration page In each offer template defined in Campaign In each offer template defined in Campaign
Cell
Annnnnnnnn
Offer
nnnnnnnnn
Treatment
nnnnnnnnn
N1430001
Version 8.5.0
171
Offer code formats are defined in offer templates rather than configured using parameters.
Related Topics
Properties related to code generation About offer codes To change the offer or treatment code format in an existing offer template
N13A0001
Replace <install_dir> with the actual directory in which <Campaign/> is installed. If the code generators built-in to Campaign do not meet your companys needs, you can develop and use custom code generators.
Related Topics
Default code formats
N13B0001
172
Related Topics
About custom code generators About creating custom code generators
N1470001
Version 8.5.0
173
To complete this task, you must have the appropriate permissions in IBM Unica Marketing. For information, see the Marketing Platform Administrators Guide. You specify the offer and treatment code generators for each offer template you create. Each offer created based on a template then uses the program(s) you specify to generate unique offer and treatment codes.
Related Topics
Offer template concepts
N1490001
174
3. Click the link for the offer template whose offer code generator you want to specify. 4. On the Step 1 offer template definition page, enter the executable name of the custom treatment code generator as the value of the Treatment Code Generator field. If you leave this field empty, the default treatment code generator is used. 5. Click Finish.
N13C0001
Example
The following example shows the correct code output format: 1 "unique_code"
Related Topics
Requirements for custom code generators
N14F0001
Version 8.5.0
Example
The following example shows the correct code output format: 0 "error_message" The error message generated by the custom code generator is displayed to the user and written to the log.
N1500001
Properties related to code generation Parameters for the default campaign and cell code generators Parameters for the default offer code generator Parameters for custom code generators
176
campCodeFormat
campCodeGenProgFile
cellCodeFormat
cellCodeGenProgFile
displayOfferCodes
offerCodeDelimiter
allowDuplicateCell codes
defaultGenerator
offerCodeGenerator Class
offerCodeGenerator Classpath
offerCodeGenerator ConfigString
N1510001
Version 8.5.0
177
-f -i -m -n -o -s -u -v -y
N1520001
178
Parameter -f -i -m -n -s -u -v -y
Use Passes in the code format, used to override the default format. Passes in an additional integer to be used to generate a unique code. Passes in the month. Can accept one or two integers, from 1 - 12. Passes in the campaign name. Passes in an additional string to be used to generate a unique code. Passes in the campaign ID, to use instead of the system generated ID. Prints the first argument to the standard out stream (STOUT). Passes in the year. Accepts four integers.
Example
uacoffercodegen -f nnnnnnnnn nnnnnnnnn nnnnnnnnn nnnnnnnnn nnnnnnnnn -a 5 -u 3 -y 2008 -m 1 -d 14
Version 8.5.0
179
N10942
About advanced settings To access Advanced settings About the General settings About the Server Optimization settings About the Test Run Settings
Whether results from runs of this flowchart are saved; Whether flowchart processing is done in database or on the Campaign server; Whether global suppression is disabled for this flowchart; The Y2K (Year 2000) threshold;
IBM Unica Campaign - Administrator's Guide
N1580001
Whether Campaign automatically saves this flowchart; Whether Campaign uses checkpoints during runs of this flowchart; The maximum number of data errors Campaign allows; The triggers to send if a run of this flowchart results in an error; The triggers to send if a run of this flowchart completes successfully.
Y2K threshold
The Y2K Threshold value determines how Campaign interprets years that are represented with only two digits. We highly recommend that you store dates in the database with 4-digit years to prevent confusion.
Version 8.5.0
181
Valid values are 0 to 100; any values higher than 100 are set to 100. The default setting for Y2K Threshold is 20. Campaign uses the Threshold value to calculate a range of years whose lower limit is the threshold value + 1900 and whose higher limit is 99 years above that. For example, if you set the Y2K Threshold to 50, the range of years is from 1900+50 = 1950, to 99 years above that, that is, 2049. So, if you enter a two-digit year greater than or equal to your threshold (in this case, 50), the date is interpreted to be in the 1900s. If you enter a two-digit year less than your threshold, it is interpreted to be in the 2000s. If you sent the Y2K Threshold to the maximum value of 100, the range of years will be 1900+100 = 2000, to 2099. In this case, all two-digit years are interpreted to be in the 2000s. You can change this threshold as needed.
N15C0001
Auto-save
You can set the auto-save feature to automatically save your work periodically (for example, every 5 minutes) for recovery purposes. If the Campaign server terminates while you are editing a flowchart, if you had Auto-Save enabled, when you re-open the flowchart, you will see the last auto-saved version. You must have previously saved the current flowchart (provided a file name) for this feature to work. Campaign stores auto-save files in a temporary directory so that the original flowchart files are not changed. Therefore, in non-recovery situations (for example, if you manually exit flowchart Edit mode without saving your flowchart) auto-saved versions are not retrieved. In this situation, when you re-open a flowchart that you manually left without saving, you will see the last manually saved version. Auto-save never saves flowcharts that are in a paused state, even if Auto-save occurs while a selected process is running. The default setting for Auto-Save is Never.
N15D0001
Checkpoint
The Checkpoint feature provides the ability to capture a snapshot of a running flowchart for recovery purposes. A checkpoint save has the same effect as if you selected File > Save, and allows you to recover a flowchart in the state of the most recent checkpoint save, in the event the server stops or goes down. When you set a frequency interval for checkpoint, it controls a timer on the server for a running flowchart. Checkpoint saves are made at the specified intervals.
182
Checkpoint is active during a flowchart run and when you run a branch in the Flowchart. When the running flowchart saves, Campaign saves it in Paused mode. When you open the flowchart, you must either stop or resume the flowchart. When you resume, the currently executing processes run again from the beginning. The default setting for Checkpoint is Never.
N15E0001
Version 8.5.0
183
184
N109B6
IBM Unica Campaign utilities Campaign Listener (unica_aclsnr) Campaign Listener Shutdown utility (svrstop) Campaign Server Manager (unica_svradm) Campaign session utility (unica_acsesutil) Campaign cleanup utility (unica_acclean) Campaign report generation utility (unica_acgenrpt) ActiveX cleanup utility (uacflchk) Database testing utilities Database load utilities
Version 8.5.0
185
Related Topics
Starting and stopping the listener
N1700001
-r (the default) This option starts a recovery run by forcing the listener to find and register any running flowcharts. Use this parameter if for some reason the listener goes down and you have flowcharts (that is, acsvr processes) still running. The listener stores flowchart information in a text file ( unica_acslnr.udb). When you use the -r option, the listener checks the file for running flowcharts and re-establishes the connections. Even if the running flowchart processes (flowchart and branch production runs only) went down with the listener, the listener reloads those flowcharts and resumes running them from the last saved checkpoints. -u -v 186 This option uninstalls the listener utility as a service (Windows only). This option displays the current version of the listener. IBM Unica Campaign - Administrator's Guide
Version 8.5.0
187
Related Topics
About logging
N1660001
-S
188
Campaign Listener Shutdown utility (svrstop) Argument -s <serverName> Description The host name of the server on which the listener is running, such as optimizeServer or campaignServer.example.com. If you omit this argument, the utility attempts to shut down the specified listener on your local server. The IBM Unica Marketing user with Campaign administrator privileges to shut down the specified listener. If you omit this value, you will be prompted for a user when you run the utility. The password for the IBM Unica Marketing user you specified with the -y argument. If you omit this value, you will be prompted for a password when you run the utility. Reports the version information for the svrstop utility and exits without further actions. The product whose listener you want to shut down. Set this to "Optimize" to shut down the Optimize listener. Any other value for this argument, or omitting this argument, shuts down the Campaign listener.
-y <user>
-z <password>
-v
-P <product>
Version 8.5.0
189
Optionally, you could include -y <username> and -z <password> as arguments with the svrstop> command to prevent the user name and password prompts from appearing. When you enter the required information, the Campaign listener is shut down.
N17A0002
190
When you start the unica_svradm utility, it checks whether the listener is running. If the listener is running, the connection automatically establishes and the names of the server and the port number are displayed.
N17B0001
1. At a command prompt, enter: unica_svradm -s listener_server -y Unica_Marketing_username -z Unica_Marketing_password 2. At the following prompt: unica_svradm[server:port]> issue the commands described in Unica Campaign Server Manager commands.
Related Topics
Campaign Listener (unica_aclsnr)
N17C0001
Version 8.5.0
191
Changeowner
Changeowner -o <olduserid> -n <newuserid> -p <policyid> The Changeowner command allows you to change the owner of a user's campaigns. You might use this command, for example, if you are deleting or disabling a user and want to re-assign ownership of that user's campaigns to a new user.
Option -o <olduserid> -n <newuserid> -p <policyid>
N17F0001
Description User ID of the current owner of the campaign. User ID of the new owner you want to assign to the campaign. Policy ID of the security policy to apply to the campaign.
Connect
Connect [-f] [-s server ] [-p port ] The Connect command connects to the listener running on the server at port number. You can be connected to only one server at a time. To connect to another server, use f (forced) connection.
N1800001
Disconnect
Disconnect The Disconnect command disconnects from the server. This command is available only if you are connected to a server. To connect to another server, you can use the -f parameter, or disconnect first, and then connect to the new server.
N1810001
Exit
Exit The Exit command logs you out of the Campaign Server Manager.
N1820001
Help
Help The Help command displays the available commands.
N1830001
Kill
Kill -p pid
192
The Kill command issues a "kill -p" to the pid specified (the Windows NT equivalent is issued on Windows NT). This is intended for run-away processes.
Related Topics
To kill a running flowchart
N1850002
Loglevel
Loglevel [high | low | medium | all] The Loglevel command sets the listener logging level for Campaign or, if you enter the command without any arguments, displays the current logging level. If you modify the logging level, the change takes effect immediately, so there is no need to restart the listener after entering this command.
N1860001
Quit
Quit The Quit command logs you out of the Campaign Server Manager.
N1870001
Resume
Resume {-s flowchart_name |-p pid |-a} The Resume command resumes the running of one or more flowcharts.
N1880002
Use -s to resume a single, specific flowchart by name Use -p to resume the specified process ID Use -a to resume all suspended flowcharts
Run
Run -p relative-path-from-partition-root -u Unica_Marketing_Platform_user_name [-h partition] [-c catalogFile] [-s] [-m] The Run command opens and runs a specific single flowchart file, where relative flowchart path and file name, partition, catalog file and user name are given. You can use the following syntax: [-S dataSource -U db_User -P db_Password]* On Unix platforms, flowcharts will be executed by the Unix account specified as the usernames alternate login. On Windows NT, the flowchart is run as the administrators user login.
Version 8.5.0
193
Specifies that you are running multiple flowcharts. This option is not supported for batch flowcharts. Specifies the relative path from the partition root Specifies the data source password Specifies a synchronous run Specifies the data source Specifies the IBM Unica Marketing user name Specifies the data source user name Specifies the user variable values for a flowchart directly in the command, using this syntax: [-v "varname=[']value[']"]*
-p -P
-s -S -u -U -v
-x
Specifies the user variable values for a flowchart in an XML file, using this syntax: [-x xml-filename]
194
Campaign Server Manager (unica_svradm) <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <UserVariables> <UserVar Name="UVAcctType"> <Values> <Option>Gold<Option> </Values> </UserVar> </UserVariables>
N1890001
Save
Save {-s flowchart_name|-p pid|-a} The Save command saves the current state of an active flowchart.
Option -s -p -a
N18A0001
Description Saves a single, specific flowchart by name defined by the flowchart-name. Saves a flowchart defined by the pid. Saves all running flowcharts.
Set
Set [variable[=value]] The Set command displays and sets environment variables. Omit the value to view the current value and provide it to set the specified variable.
N18B0001
Shutdown
Shutdown [-f] The Shutdown command shuts down the listener. The system checks for any running flowchart. If running flowcharts are found, a warning message displays, asking for confirmation of shutdown. To override and force shutdown, use -f .
N18C0002
Status
Status [-d |-i] [-u] [-v | -c]] The Status command displays information both about running and suspended flowcharts (with flowchart name, owner, and file location).
Version 8.5.0
195
15 - IBM Unica Campaign Utilities Option d i u v Description Adds Server ID, Campaign Code, and Campaign ID to the displayed output. Displays the process ID (PID) only Use this option when the displayed data contains non-ASCII characters. Verifies the existence of the unica_acsvr processes before displaying output, which prevents crashed processes from being displayed in the Status list. Verifies the existence of the unica_acsvr processes before displaying output, which prevents crashed processes from being displayed in the Status list. Option c also instructs the listener to clean up any temporary files in the partition temp directory that are associated with crashed server processes.
The Status command identifies the processes as follows: c - connected (client is connected to the listener process -- may be running, may not) d - disconnected (client is closed but the flowchart is running in the background) o - orphaned (client is not connected to the flowchart and it is not running in the background -- this is a lost process that cannot be reconnected to the listener and should be killed so people can log into it) A value of <no writer> in the WRITER column refers to a server process that does not have a client in edit mode, which may happen when no client is connected, and for login sessions.
N18D0001
Stop
Stop [-f] {-s flowchart_name |-p pid | -a} The Stop command checks for active clients, warns if any are present (this can be overridden with the -f force option), and stops the Unica server processes.
Option -s -p -a Description Stops a single, specific flowchart by name defined by the flowchart_name Stops flowcharts by pid. Stops all running flowcharts.
196
Suspend
Suspend [-f] {-s flowchart_name | -p pid |-a} The Suspend command allows you to quiesce a running campaign and save the state for later restart with the matching command, Resume. All flowcharts currently running an output process complete data export activities and the flowchart is then saved as a paused flowchart. This causes the least amount of work to be lost and preserves data integrity of output files. If flowcharts must be stopped immediately, issue a Save command followed by Stop.
Option -s Description Suspends a single, specific flowchart by name defined by the <flowchart_name> Suspends flowcharts specified by pid Suspends all running flowcharts
-p -a
The system finishes running any currently running processes, and does not allow any subsequent processes to start. The flowchart is saved and written to the list of suspended flowcharts. The -f parameter allows you to force a suspend. Once suspended, the flowchart is written to the listener as a suspended flowchart. If the flowchart is not running at the time of Suspend, it is saved, but not written to the listener and cannot be started with Resume.
N18F0001
Version
Version The Version command displays the version of unica_svradm and the version of the listener process to which you are connected. You can use this command to help troubleshoot a version mismatch error.
N1840001
Version 8.5.0
197
On UNIX only, the database-specific library path appropriate to your UNIX platform:
198
N1910001
Exporting and importing objects between servers Backing up sessions Updating record counts and lists of distinct values Manipulating table catalogs Documenting catalog contents
N1980001
2. You manually move (copy) the output file to the target server. Before you can import a flowchart to a target system, its flowchart (.ses) file, as well as its associated campaign or session, must already exist on the target system. Therefore you should export and import all campaigns and sessions before exporting and importing their associated flowcharts, and you must manually copy the flowchart (.ses) files to the target server. 3. On the target server, you import the unica_acsesutil output file using the -i option .
N1990001
This example generates an output file named campaign.exp for exporting the campaign associated with Flowchart1, based on the campaigns/Campaign C000001_C000001.ses file located on partition1.
200
This example generates an output file named flowchart.exp for exporting flowchart C000001_Flowchart1, based on the campaigns/Campaign C000001_C000001_ Flowchart1.ses file located on partition1.
N19B0001
This example uses the previously generated campaign.exp file and imports Campaign C000001 data to the system tables on the target system, as well as to the campaigns/Campaign C000001_C000001.ses file located on partition1.
This example uses the previously generated flowchart.exp file and imports the data associated with Campaign C000001_Flowchart1 to the system tables on the target system, as well as to the campaigns/Campaign C000001_C000001_Flowchart 1.ses file located on partition1.
N1940001
Backing up sessions
Use the Campaign session utility to back up sessions. You can write a script to export every file in the session directory and import them to a backup system.
N1950001
-n -- recompute record counts only -l -- recompute list of distinct values only -a -- recompute record counts and list of distinct values for all tables
Use these options to recompute all record counts and/or list of values for a session (-s) or for a catalog (-t). You can combine these options with other options such as import (i).
You must specify the parameters that define the database connection (-S, -U, -P) if the connection information is not stored in the flowchart.
N1960001
202
Keeping catalogs in XML format risks exposing data access passwords. If you maintain catalogs in XML format, you should ensure that the file(s) are protected at the operating system level.
Version 8.5.0
203
-b
-c
-c <outputFileName>
Generates a table catalog in outputFileName in .cat format (Campaign internal format). This option is ignored with the -s option. Exports the object type specified by the -f option to a file named exportFileName. If the -f option is not used, by default a flowchart is set for export.
-e
-e <exportFileName>
204
Option -f
Description Specifies the type of object to export. If this option is omitted, by default a flowchart is set for export. If -f is used, requires one of the following arguments: flowchart campaign session
-h
-h <partitionName>
Specifies the name of the partition in which the flowchart file (specified with -s) is located. This parameter is required.
-i
-i <importFileName>
Specifies the name of the file being imported. This should be a file that was exported using the -e option in a previous export operation. Specifies the owner of the file being imported or exported. Specifies the security policy of the file being imported. Recompute only the list of distinct values. Recompute only record counts. Specify the catalog with the name outputFileName. If unspecified, the default is catFileName.xml or catFileName .cat, depending on whether you use the -x or -c option. The output file name should specify a destination directory when using wild cards. Specifies the password for the database user account. Used in conjunction with the -U and -S options. Print table mappings to the console. Generate a flowchart XML report in outputFileName. This parameter is ignored when you use the -t option (using a table catalog as input).
-j
-j <owner>
-k
-k <policy>
-l -n -o
-l -n -o <outputFileName>
-P
-P <DBPassword>
-p -r
-p -r <outputFileName>
Version 8.5.0
205
Option -S
Syntax -S <dataSource>
Description Specifies the name of the data source for the object being operated on. Use in conjunction with the -U <database_user> and -P <database_password> options.
-s
-s <sesFileName>
Specifies a Campaign flowchart (.ses) file on which to operate. Specifying an .ses file is always required for exporting and importing, regardless of the object type (campaign, session, or flowchart). When exporting or importing a campaign or session with multiple associated flowcharts, any of the associated .ses files can be used. The file name should include the path below the partition in which this flowchart file is located (defined using the -h option). For example, a valid value for -s is: campaign/Campaign C00001_C00001_Flowchart 1.ses The <sesFileName> can contain wildcard characters to operate on multiple matching flowcharts.
-t
-t <catFileName>
Read a table catalog named < catFileName > as the input. The <catFileName> can contain wildcard characters.
-U
-U <DBUserName>
Specifies the user login for the data source specified by the -S option. Use in conjunction with the -P option, which specifies the database password for this database user.
-u
-u
Uses existing database authentication information when saving table catalogs. Displays the version number and exits. Generates a table catalog file in an alternate XML format in outputFileName. If the input table catalog is a .cat file, it generates a corresponding .xml file, and vice versa.
-v -x
-v -x <outputFileName>
206
Option -y -z
Description Specifies the IBM Unica Marketing user name. Specifies the password for the IBM Unica Marketing user specified by the -y option.
N1690001
temporary files and tables associated with a specified object or object type, based on given criteria. orphaned temporary files and tables -- temporary files and tables that have been left behind after their associated object was deleted.
Version 8.5.0
207
N1A10001
Generating a list of files and tables selectively by object type and criteria Deleting files and tables selectively by object type and criteria
Example
unica_acclean -o OrphanList.txt -w orphan This example generates a list of orphaned files and tables and writes it to the file OrphanList.txt.
N1A20001
208
To delete all orphaned temp files and tables from your system
unica_acclean -d -w orphan
N1A90001
Tables
The utility scans databases in the current partition to obtain the list of temporary tables. Tables are identified as temporary based on the TempTablePrefix or ExtractTablePrefix properties specified for each data source on the Marketing Platform Configuration page. Once the list of temporary tables is compiled, all flowchart files in the system are scanned to see if any of these temporary tables are used by a flowchart. Any temporary table not referenced by a flowchart is considered orphaned. The cleanup utility scans only those data sources defined in the Marketing Platform User Administration module for the user running the utility. Therefore, users running the cleanup utility should always make sure that they have authentication rights to the global or appropriate set of data sources for scanning.
Files
The utility scans two locations to identify temporary files: the partitions temp directory (<partition home>/<partition>/tmp) to obtain the list of files identified as temporary files based on the .t~# extension. the <partition home>/<partition>/[campaigns | sessions] directory for files having a known Campaign temp file extension.
Once the list of temporary files is compiled, all flowchart files in the system are scanned to see if any of these temporary files are not used by any flowchart. Any temporary file not referenced by a flowchart is considered orphaned.
N1A40001
Generating a list of files and tables selectively by object type and criteria
You can use the cleanup utility to generate a list of files and tables by object type and criteria.
N1AA0001
Version 8.5.0
209
To generate a list of files and tables selectively by object type and criteria
unica_acclean -o <list file name> -w {flowchart | campaign | session | sessionfolder | campaignfolder} -s criteria [-r]
210
Make sure that any date criteria are specified in the correct date format for your database.
N1AC0001
The cleanup utility is non-interactive unless user name or password are not specified. If user name is not specified, the tool prompts for user name and password. If password is not specified, the tool prompts for password.
N1AD0001
-f
-h
-h
-i
-l
-l {low | medium | high | all}][-f Specifies logging level and the log file name. If no level is specified, medium is used by default. <logFileName>] -n < partition name > Use this option to supply the name of the partition. If the partition name is not specified, the default of partition 1 is used.
-n
Version 8.5.0
211
15 - IBM Unica Campaign Utilities Option -o Syntax -o <listfilename> Description Outputs the list of tables and files to the specified file, but does not delete them. Must be used when the -u option is used. The -u and -p options must be used together. Use this option to supply the password for the user specified with the -u option. -r -r This option can be used only with the -w option for either campaignfolder or sessionfolder objects. When a folder is specified for cleanup and the -r option is added, the unica_acclean tool performs the operation for all subdirectories of the specified folder. If only the -w option is used with a folder, unica_acclean performs the operation only on the top level folder. -s -s <criteria> Used with the -w option, defines criteria for cleanup, specified as a SQL query. The SQL LIKE operator can be used to do a search based on wild cards. Any data table column for the specified object can be used as a criterion: When specifying a campaign folder or session folder as the object, criteria are based on columns in the UA_Folder table. When specifying a campaign as the object, criteria are based on columns in the UA_Campaign table. When specifying a flowchart as the object, criteria are based on columns in the UA_Flowchart table. When specifying a session as the object, criteria are based on columns in the UA_Session table.
-p
-u
Must be used when the -p option is used. The -u and -p options must be used together. Use this option to supply the IBM Unica Marketing user name of the user running the utility.
-v
-v
212
Campaign report generation utility (unica_acgenrpt) Option -w Syntax -w {flowchart | campaign | session | sessionfolder | campaignfolder | orphan} -s <criteria> [-r] Description Searches for temp files and tables associated with the specified object type, based on the specified criteria, except when used with the orphan option. Only when used with orphan, searches for orphaned temp files and tables across the entire system. Requires -s <criteria> for all options except orphan. For details, see -s. Optionally use the -r option to recursively search subfolders within folders. For details, see -r.
N16A0002
For more information about these reports, see the IBM Unica Campaign User's Guide. The default file name of the exported file is unique and based on the flowchart name. It is saved in the directory you specify. If the file already exists, it is overwritten. The default file format is tab-delimited. The exported file contains the current data from the flowchart's .ses file. If a flowchart is writing to the .ses file when the unica_acgenrpt utility is run, the resulting report file could contain data from the previous run of the flowchart. If you are invoking the unica_acgenrpt utility using an on-success trigger, your script should contain an appropriate delay before executing unica_acgenrpt to account for the length of time that your flowcharts will need to finish writing to the .ses file. The amount of time required to save the .ses file varies greatly depending upon the size and complexity of the flowchart. Use of the unica_acgenrpt utility requires the Run genrpt Command Line Tool permission in the Administrative Roles security policy. For more information on security policies and permissions, see Managing Security in Campaign .
N1AE0002
Version 8.5.0
213
214
Option -r
Syntax -r <reportType>
Description Specifies the type of report to be generated. Valid values include the following: CellList (Cell List report) Profile (Cell Variable Profile report) XTab (Cell Variable Crosstab report) CellContent (Cell Content report)
-p
-p <name>=<value>
Specifies report parameters using name=value pairs. The -p option can appear multiple times, and must appear after the -r option. For a list of valid name=value pairs supported by the -p option, see Parameters used with the unica_acgenrpt -p option.
-d
-d <delimiter>
Used to separate columns in the output file. The default is TAB. Includes column names before the report data in the output file. Appends a unique text identifier to the end of the output file. Specifies the output file name. The default is <sesFileName> with .ses replaced by .csv; specifies a destination directory when using wildcards. Specifies a login user name for Campaign. Specifies the password for the user login. Displays the version number of the utility and exits.
-n
-n
-i
-i
-o
-o <outputFileName>
-y -z -v
-y <user> -z <password> -v
N1B10002
Version 8.5.0
215
cell2 bins
Optional Optional
meta
Optional
field2
Required
cell2 bins
Optional Optional
meta
Optional
216
ActiveX cleanup utility (uacflchk) Parameter name field Usage Optional Description Name of a field you want to include in the report. Repeat multiple times to specify additional fields. If no field is specified, the report displays values for the audience field(s). Number of records you want to include in the report. The default is 100. Specifies whether you want to skip records with duplicate ID values. Enabling this option is useful if you are using non-normalized tables. Valid values are TRUE and FALSE. The default is FALSE.
records
Optional
skipdups
Optional
N16B0001
N1B30001
218
N16C0001
cxntest utility
The cxntest utility allows you to test connections to a target database and, once connected, to issue a variety of commands.
N1BB0001
The utility does not prompt for confirmation of your selections. 3. If the connection is successful, you can enter the following commands at the prompt: bprint[ pattern ] Performs an array fetch on a list of tables, 500 at a time. Can optionally specify a search pattern. describe table Describes the specified table. Returns each column name and its corresponding data type, storage length, precision, and scale. exit Terminates the database connection and exits. help Displays a list of supported commands. print [pattern] Returns a list of tables. Can optionally specify a search pattern. quit Terminates the database connection and exits. SQL_command Executes any valid SQL command or series of SQL commands.
N1B80001
odbctest utility
The odbctest utility allows you to test Open DataBase Connectivity (ODBC) connections to a target database and, once connected, to issue a variety of commands. It is supported on AIX, Solaris, Windows and HP-UX systems (32-bit only). For Oracle and DB2 databases, use their native utilities.
Related Topics
oratest utility db2test utility
N1BC0002
Database testing utilities dBASE Files (Microsoft dBase Driver (*.dbf)) Excel Files (Microsoft Excel Driver (*.xls))
2. The odbctest utility is prompt-driven. You must enter the following information exactly at the prompts: a. The name of the database you want to connect to (taken from the list of Registered Data Sources) b. A database user ID c. The password associated with the database user ID The utility does not prompt for confirmation of your selections. 3. When you have successfully connected to the database, the odbctest utility prints out messages like the following and presents you with a command prompt:
Server ImpactDemo conforms to LEVEL 1. Server's cursor commit behavior: CLOSE Transactions supported: ALL Maximum number of concurrent statements: 0 For a list of tables, use PRINT.
4. You can enter the following commands at the prompt: bulk [number_of_records] Sets the number of records to return, as specified by number_of_records. The default is 1. descres SQL_command Describes the columns returned by the SQL command specified by SQL_command. describe pattern Describes the table or tables specified by pattern. Returns the corresponding type, data type, storage length, precision, and scale. exit Terminates the database connection and exits. help Displays a list of supported commands. print [pattern] Returns a list of tables. Can optionally specify a search pattern. quit Terminates the database connection and exits. SQL_command Executes any valid SQL command or series of SQL commands.
Version 8.5.0 221
N1B90001
db2test utility
The db2test utility allows you to test connections to a DB2 database and, once connected, to issue a variety of commands.
N1BD0001
The utility does not prompt for confirmation of your selections. 3. When you have successfully connected to the database, the db2test utility prints out messages like the following and presents you with a command prompt:
Server ImpactDemo conforms to LEVEL 1. Server's cursor commit behavior: CLOSE Transactions supported: ALL Maximum number of concurrent statements: 0 For a list of tables, use PRINT.
4. You can enter the following commands at the prompt: describe pattern Describes the table or tables specified by pattern. Returns the corresponding type, data type, storage length, precision, and scale. exit Terminates the database connection and exits. help Displays a list of supported commands. print [pattern] Returns a list of tables. Can optionally specify a search pattern.
222
N1BA0001
oratest utility
The oratest utility allows you to test connections to an Oracle server.
N1BE0001
1. Creates a temporary data file as fixed width or delimited text. If specified by the LoaderControlFileTemplate property, a temporary control file is dynamically created based on the template file and the list of fields that need to be sent to the database. 2. Issues the command specified by the LoaderCommand property. This can be either a direct call to the database load utility executable or a call to a script that launches the database load utility. 3. Cleans up the temporary data file and control file. This functionality allows you to load data into a new or empty database table and append data to an existing database table. Campaign does not support using load utilities to update records in an existing database table.
N1BF0001
Token <CONTROLFILE>
Description This token is replaced with the full path and file name to the temporary control file that Campaign generates according to the template that is specified in the LoaderControlFileTemplate parameter. This token is replaced with the value of the DSN property. If the DSN property is not set, the <DSN> token is replaced by the data source name used in the category name for this data source (the same value used to replace the <DATABASE> token). This token is replaced with the name of the data source that Campaign is loading data into. This is the same data source name used in the category name for this data source. This token is replaced with the full path and file name to the temporary data file created by Campaign during the loading process. This file is in the Campaign Temp directory, UNICA_ACTMPDIR. This token is replaced with the number of fields in the table.
<DSN>
<DATABASE>
<DATAFILE>
<NUMFIELDS>
224
Token <PASSWORD>
Description This token is replaced with the database password from the current flowchart connection to the data source. This token is obsolete, but is supported for backward compatibility. See <TABLENAME>, which replaced <TABLE> as of version 4.6.3. This token is replaced with the database table name that Campaign is loading data into. This is the target table from your Snapshot process or the name of the Temp Table being created by Campaign. This token is replaced with the database user from the current flowchart connection to the data source.
<TABLE>
<TABLENAME>
<USER>
In addition to these special tokens, every line includes other characters. To include a single character on every line except the last line, the character can be enclosed within angle brackets. You can enclose only a single character between the angle bracket (< >) characters for this functionality. This is commonly used to separate the list of fields with a comma. For example, the following syntax generates a comma-separated list of field names: <FIELDNAME><,> The angle bracket (< >) characters around the comma indicate that the comma should be present on every line, after every inserted field name, except the last. If any sequence of characters does not fit this requirement, it is repeated every time, including the last. So for example, to generate a parenthesized, comma-separated list of field names in which each field name is preceded by a colon, you can use the following syntax:
( :<FIELDNAME><,> )
Because the colon is not enclosed within angle bracket (< >) characters, it repeats for every line; however, the comma appears on every line except the last. It might produce output as follows:
( :FirstName, :LastName, :Address, :City, :State, :ZIP )
Version 8.5.0
225
Note that the comma does not appear after the last field name (ZIP), yet the colon appears before every field name.
226
N10C3B
Introduction About using non-ASCII data or non-US locales Configuring Campaign for a non-ASCII language or a non-US locale Configuring Campaign for multiple locales
Introduction
Campaign and PredictiveInsight support the use of localized data and non-United States locales, including multiple user-preferred locales within the same installation of the Unica application. To ensure that your application is set up to work correctly with nonASCII data, non-United States locales, or user-specified locales, you must perform some specific configuration tasks. Unica strongly recommends that you avoid using your Unica applicaton before you have completely configured your system and tested it for your data and locale. It is recommended that you perform these configuration steps on a new installation of the application.
N1C10001
"About character encodings". "About interaction with non-ASCII databases". "About the multi-locale feature".
Version 8.5.0
227
Campaign and PredictiveInsight communicate directly with the database client and the client communicates with the database. Each database varies in how it handles language-sensitive data. You must understand the encoding and date format that your database server and client use, and ensure that you configure your Unica application correctly for these settings.
N1C90001
The format of a time field can have various characteristics, including: The hour format (for example, 12-hour or 24-hour format) The representation of minutes and seconds The locale-specific indicator for AM/PM
228
If you use the multi-locale feature, you should not use date formats containing 3letter months (MMM), %b (abbreviated month name), or %B (full month name). Instead, you should use a delimited or fixed format with a numeric value for the month. For more details about date formats, see . For more details about the multilocale feature, see . Date and time formats can appear in SQL statements as well as in the data returned by the database (called a resultset). Some database clients support or require different formats between SQL statements (output) and resultsets (input). The Configuration page for Campaign includes a parameter (DateFormat, DateOutputFormatString, DateTimeFormat, and DateTimeOutputFormatString) for each of the different formats.
N1C70001
Version 8.5.0
229
If you use the multi-locale feature, you should not use date formats containing 3letter months (MMM), %b (abbreviated month name), or %B (full month name). Instead, use a delimited or fixed format with a numeric value for the month.
N1CC0001
In Windows, the language and regional settings must match. Regional settings affect all non-Unicode programs in Windows, and must be explicitly set.
N1CD0001
230
In multi-locale installations of Campaign, when file names are in mixed languages, or when the command shell language (encoding) does not match the file name encoding, file names might appear garbled in command-line displays. Multi-locale installations of Campaign on Windows platforms is supported only on NTFS drives, as FAT32 does not support Unicode character sets. Cell Profile Reports are not localized and remain in English regardless of locale.
N1C20001
Version 8.5.0
231
If the language you need is not yet installed, use the information from the following sources to configure supported UNIX variants to work with a given language: Solaris 9 International Language Environments Guide (http://docs.sun.com/app/docs/doc/806-6642) AIX 5.3 National Language Support Guide and Reference (http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.js p? topic=/com.ibm.aix.nls/doc/nlsgdrf/nlsgdrf.htm) HP-UX 11 Internationalization Features White Paper (http://docs.hp.com/en/5991-1194/index.html)
N1D40001
Set encoding parameters for the web application server (WebSphere only)
For WebSphere only, if you are using Campaign with a non-ASCII encoding, you must set -Dclient.encoding.override=UTF-8 as a JVM argument to ensure that the application server uses UCS Transformation Format for encoding. For detailed instructions on doing this, see the IBM WebSphere documentation.
N1D00002
The configuration of the Campaign web application determines the language and locale used both for translated Campaign messages (for example, text in the Campaign user interface) as well as the format of dates, numbers, and currency symbols on the applications web pages. It is also vital for allowing flowcharts to display non-ASCII text, because the display language is used to initialize the flowchart editor.
232
Campaign supports non-ASCII column names, table names, and database names; however, it supports NCHAR, NVARCHAR, etc. columns on SQL Server databases only. On DB2, NCHAR and NVARCHAR format columns are treated as if they were regular text fields; on Oracle, they are treated as numeric fields. Log in to Marketing Platform and configure the following properties. Record these values for future reference. For information about these properties, see the Campaign Installation Guide.
N1D10001
Campaign > currencyLocale Campaign > supportedLocales Campaign > defaultLocale Campaign > partitions > partition[n] > dataSources > [data_source_name]> DateFormat Campaign > partitions > partition[n] > dataSources > [data_source_name]>DateOutputFormatString Campaign > partitions > partition[n] > dataSources > [data_source_name]>DateTimeFormat Campaign > partitions > partition[n] > dataSources > [data_source_name]> DateTimeOutputFormatString Campaign > partitions > partition[n] > dataSources > [data_source_name]>EnableSelectOrderBy Campaign > partitions > partition[n] > dataSources > [data_source_name] > ODBCunicode Campaign > partitions > partition[n] > dataSources > [data_source_name]> StringEncoding Campaign > partitions > partition[n] > dataSources > [data_source_name]> SuffixOnCreateDateField Campaign > partitions > partition[n] > server > encoding > stringEncoding Campaign > partitions > partition[n] > server > encoding > forceDCTOneBytePerChar Campaign > unicaACListener > logStringEncoding Campaign > unicaACListener >systemStringEncoding
Test that your database is correctly configured Test that your attribute table is correctly configured Test campaigns and flowcharts with ASCII and non-ASCII characters Test flowchart input and output with ASCII and non-ASCII characters Test that the correct language directory is used Test that the date formats in calendar reports are correct Test that the currency symbol displays correctly for your locale
234
Test campaigns and flowcharts that have ASCII and non-ASCII characters
1. In Campaign, create a campaign using the following guidelines: Use only ASCII characters for the names, but use non-ASCII characters in other fields, such as the Description and Objective fields. The default dates displayed in the Effective/Expiration Dates fields should appear in your locales date format. Select new dates for each of the Effective/Expiration Dates fields using the Calendar Tool, making sure that you select a day greater than 12 so that it will be obvious if the day is incorrectly represented as the month. Verify that the dates you selected using the Calendar Tool are displayed correctly in the fields. If there are custom campaign attributes existing, the field labels for these should appear in your database encoding, regardless of your default locale or user locale.
2. When you are finished with the basic campaign fields, click Save and Add a Flowchart. 3. Accept the default flowchart name, but use non-ASCII characters in the Flowchart Description field. 4. Click Save and Edit Flowchart. 5. Verify that the campaign and flowchart are saved successfully and any campaign and flowchart labels with non-ASCII characters display correctly. 6. On the campaigns Summary tab, click Edit and modify the campaign name to use non-ASCII characters. 7. Click Save Changes and verify that the non-ASCII characters display correctly. 8. Select the flowchart you just created, click Edit and rename the flowchart using nonASCII characters. 9. Click Save Changes and verify that the non-ASCII characters display correctly.
N1D80001
Test flowchart input and output that contains ASCII and nonASCII characters
1. Still in the test flowchart you created in "Test campaigns and flowcharts with ASCII and non-ASCII characters", click Edit. 2. Add a Select process to the flowchart and configure it using the following guidelines: In the Input field, select a mapped user table. The available fields from the selected table are displayed in the Available Fields area. Select a field that you know contains non-ASCII characters, and click Profile. Verify that the non-ASCII characters display correctly.
Version 8.5.0
235
3. In the same Select process configuration, do another test, this time using a flat file with non-ASCII characters as the input: In the Input field, select a select a flat file that uses non-ASCII characters. The available fields from the selected file are displayed in the Available Fields area. Verify that the non-ASCII characters display correctly.
4. On the General tab of the Select Process Configuration window, replace the default name in the Process Name field with a name containing non-ASCII characters, then click OK. 5. Verify that the non-ASCII process name displays correctly on the process. 6. Add a Snapshot process to the flowchart and connect it so that it takes input from the existing Select process. 7. Configure the Snapshot process to Export to file. 8. Run the Select > Snapshot flowchart and locate the specified output file. 9. Verify that the output looks correct. 10. Add a Schedule process to the flowchart and configure a custom run: In the Process Configuration window, select Custom Run from the Schedule to Run field. Use the Calendar to specify a date and time. For the date, choose a day greater than 12 so that it will be obvious if the day is incorrectly represented as the month. Remember to click Apply, then click OK to save the date and time before closing the Calendar Tool.
11. Verify that the date and time are displayed correctly in the Run On Time field. 12. Close the Process Configuration window and click Save and Exit. 13. Select Settings > Campaign Settings. The Campaign Settings page appears. 14. Select Manage Table Mappings. 15. In the Table Mappings window, in the list of Unica system tables, select the UA_Campaign table and click Browse. 16. In the Campaign Table window, verify that non-ASCII characters display correctly. 17. In the Table Mapping window, select the UA_Flowchart table and verify that nonASCII characters display correctly. 18. When you successfully complete this test, delete the test campaigns and their flowcharts, and any files that you used for testing.
N1D90001
The Calendar of Campaigns appears. Notice that the time delineation selector that appears vertically to the right of the report (day/week/2 week/month) is an image 2. Right-click the image and select Properties. 3. In the Properties window for the image, examine the Address (URL) for the image. For example, the Address might be: http://localhost:7001/Campaign/de/images/calendar_nav7.gif indicating that the language and locale setting is German (de). 4. Verify that the language and locale setting matches either your default application setting or your user locale preference (if any).
N1DA0001
Test that the currency symbol displays correctly for your locale
1. Select Settings > Campaign Settings. The Campaign Settings window appears. 2. Select Offer Template Definitions. 3. Create a new and on the New Offer Template (Step 2 of 3) page, select Cost Per Offer from the Available Standard and Custom Attributes list, and move it to the Selected Attributes list. 4. Click Next and on the New Offer Template (Step 3 of 3) page, examine the Cost Per Offer attribute field under Parameterized Attributes. Verify that the currency symbol appearing in parentheses is correct for your locale. 5. When you complete this test successfully, click Cancel because you don't need to create the offer template.
N1C30001
Version 8.5.0
237
UTF-8
UTF-8
Campaign > unicaACListener >systemStringEncoding UTF-8. If necessary, you can set more than one encoding, separated by commas, but keep UTF-8 first in the series. For example: for example, UTF-8,ISO-8859-1,CP950. Campaign > partitions > partition[n] > dataSources > [data_source_name] > ODBCunicode UCS-2
For the configuration properties that specify date and time formats, accept the default values.
N1DE0001
238
Property Campaign > partitions > partition[n] > dataSources > [data_source_name] > StringEncoding Campaign > partitions > partition[n] > server > encoding > stringEncoding Campaign > unicaACListener > logStringEncoding
Value UTF-8
UTF-8
UTF-8
%Y-%m-%d
DT_DELIM_Y_M_D
%Y-%m-%d %H:%M:%S For Japanese databases, the delimiter for the time portion must be a period (.) So, for Japanese databases set the value to: %Y/%m/%d %H.%M.%S
N1E10001
UTF-8
UTF-8
240
DT_DELIM_Y_M_D
%Y-%m-%d %H:%M:%S For Japanese databases, the delimiter for the time portion must be a period (.) So, for Japanese databases set the value to: %Y/%m/%d %H.%M.%S
N1E60001
Version 8.5.0
241
242
N10D47
IBM Unica Marketing configuration properties Marketing Platform configuration properties Reporting configuration properties Campaign configuration properties
Unica URL
Specifies the URL used for the IBM Unica Marketing. This is set at installation time and normally should not be changed. Note that the URL contains the domain name, as shown in the following example. protocol://machine_name_or_IP_address.domain_name:port_number/con text-root The machine name should not be localhost. Default Value Not defined Example In an environment configured for SSL, the URL might look like this: https://machineName.companyDomain.com:8080/customer/unica
N1ED0001
244
Version 8.5.0
245
If you change this value after users and passwords have been created, the new expiration date takes effect for existing users the next time they change their password. Valid Values Any integer Default Value 30
246
TokenLifetime
Specifies the length of time, in seconds, that a token generated by the Marketing Platform is valid. It is part of the suite sign-on implementation, and you should not change this value. Valid Values Any positive integer Default Value 15
Default region
Specifies the default locale for the Marketing Platform. If you plan to install Campaign, you should set this value to match the locale set for Campaign in Campaigns defaultLocale property. Valid Values Supported locales Default Value en_US
Version 8.5.0
247
Platform
Region setting
Specifies the locale preference for IBM Unica Marketing users. When you set this property on the Configuration page, the setting you apply is the default setting throughout IBM Unica Marketing for all users, except those whose locale preference is set individually through the Marketing Platform's User page. When you set this property for an individual user, the setting you apply for that user overrides the default setting. This preference setting affects display of the language, time, numbers, and dates in IBM Unica Marketing applications. Availability of locales may vary depending on the IBM Unica Marketing application, and not all IBM Unica applications support this locale setting in the Marketing Platform. See specific product documentation to determine availability and support for the Region setting property. Default Value English (United States)
Help server
The URL of the server on which IBM Unica hosted online help is installed. If IBM Unica Marketing users have internet access, you should not change the default value, which points to the online help server maintained and updated by IBM Unica . Valid Values Any server on which IBM Unica hosted help is installed. Default Value The URL of the IBM Unica hosted help server.
248
JMS server
The IBM Unica Scheduler uses JMS, which by default is enabled in the Marketing Platform. There is no requirement to install or configure JMS. However, for enhanced reliability, you may want to run JMS on a different machine from the one where you install the Marketing Platform and IBM Unica Marketing applications. If you do so, you must set this property and JMS port to point to the server on which you installed Active MQ. Valid Values The machine name or IP address and domain of any server on which Active MQ is installed. Include the domain name. For example: myMachine.myDomain.com Default Value localhost
JMS port
The IBM Unica Scheduler uses JMS, which by default is enabled in the Marketing Platform. There is no requirement to install or configure JMS. However, for enhanced reliability, you may want to run JMS on a different machine from the one where you install the Marketing Platform and IBM Unica Marketing applications. If you do so, you must set this property and JMS server to point to the server on which you installed Active MQ.
Version 8.5.0 249
Valid Values The port on which Active MQ is installed. Include the domain name. The default port is 61616. Default Value 61616
Start page
The URL of the page that appears when users log in to IBM Unica Marketing. The default is the default dashboard. Valid Values Any IBM Unica Marketing URL except form submissions pages, edit pages, and search result pages. Default Value The default dashboard.
Domain name
The name of the domain where IBM Unica Marketing is installed. The value is set during installation. You should not change this unless the domain name changes. Default Value Not defined
Every hour
The job is triggered every hour. Default Value 0 0 0/1 * * ?
Every day
The job is triggered every 24 hours. Default Value 000**?
Version 8.5.0
Every January - 0 0 0 1 ? JAN * Every February - 0 0 0 1 ? FEB * Every March - 0 0 0 1 ? MAR * Every April - 0 0 0 1 ? APR * Every May - 0 0 0 1 ? MAY * Every June - 0 0 0 1 ? JUN * Every July - 0 0 0 1 ? JUL * Every August - 0 0 0 1 ? AUG * Every September - 0 0 0 1 ? SEP * Every October - 0 0 0 1 ? OCT * Every November - 0 0 0 1 ? NOV * Every December - 0 0 0 1 ? DEC *
252
Platform > Scheduler > Schedule registrations > Campaign > [Object type]
A different category exists for each of the two object types that can be scheduled with the IBM scheduler: flowchart and mailing. Properties in these categories should not normally be changed.
Platform > Scheduler > Schedule registrations > Campaign > [Object type] > [Throttling group]
Default throttling groups exist for each of the two object types that can be scheduled with the scheduler flowchart and mailing. You can use the Throttling group template to create additional groups.
Throttling threshold
The greatest number of schedules associated with this group that can run concurrently. The configured scheduler groups appear in the Scheduler Group drop-down list in the Scheduler user interface for creating and editing schedules. The default throttling group is set to 999, which is effectively no limit. Because all schedules must belong to a throttling group, you should leave this value unchanged so that schedules that you do not want to throttle can be assigned to this group. Valid Values Any positive integer.
Version 8.5.0 253
Default Value
N1F50001
Default throttling group - 999 Group created from a template - Not defined
Valid Values Windows integrated login | Unica Marketing Platform | LDAP | Web access control Default Value Unica Marketing Platform
N1F60001
Platform > Security > Login method details > Windows integrated login
Domain
Sets the value of JCIFS SMB client library property jcifs.smb.client.Domain. Specifies the domain that is used if no domain is specified in an SMB URL. Set this value to the Windows domain name. For most environments, set either this property or the Domain Controller property. Default Value Undefined. Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory server and Windows integrated login is enabled.
254 IBM Unica Campaign - Administrator's Guide
Client Timeout
Sets the value of JCIFS SMB client library property jcifs.smb.client.soTimeout. Specifies the amount of time, in milliseconds, before sockets are closed if there is no activity between the client and server. This number should be as small as possible but long enough to allow the protocol handshaking to complete, which depends on network characteristics. Default Value 1000 Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory server and Windows integrated login is enabled.
Cache Policy
Sets the value of JCIFS SMB client library property jcifs.netbios.cachePolicy. Specifies the amount of time, in seconds, that the NetBIOS name is cached to reduce redundant name queries. If the value is set to 0 is no caching takes place. If the value is set to -1 the cache is never cleared. This property is used when SMB signing is enabled and required in a Windows 2003 domain. Default Value 0 Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory server and Windows integrated login is enabled.
Domain Controller
Sets the value of JCIFS SMB client library property jcifs.http.domainController. Specifies the IP address of a server that should be used to authenticate HTTP clients (used by NtlmHttpFilter and NetworkExplorer). You may use the IP address of a workstation in the domain specified in the Domain property. For most environments, set either this property or the Domain property. Default Value Undefined. Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory server and Windows integrated login is enabled.
Version 8.5.0
255
Strip Domain
Specifies whether the Marketing Platform removes a domain from users' login names when they access the IBM Unica Marketing. If your Windows configuration requires a domain to be included with users' login names when they log in, set this value to False. Valid Values True | False Default Value True Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory server and Windows integrated login is enabled.
256
Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory server and Windows integrated login is enabled.
N1F70001
Default Value (&(|(objectClass=user)(objectClass=person))(uid=%s)) Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
258
Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Base DN
Specifies the base distinguishing name (DN) pointing to the root of the LDAP directory structure. Valid Values Any valid DN (see RFC 1779, RFC 2253) Default Value [CHANGE ME] Availability This property is used only when the Marketing Platformis configured to integrate with a Windows Active Directory or other LDAP server.
Version 8.5.0
259
Platform > Security > Login method details > Web access control
Username pattern
Java regular expression used to extract the user login from the HTTP header variable in web access control software. Note that you must XML-escape any XML characters in the regular expression. The recommended value for SiteMinder and Tivoli Access Manager is \w* Valid Values Any Java regular expression. Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with web access control software.
260
Platform > Security > Login method details > LDAP synchronization
LDAP sync enabled
Set to true to enable LDAP or Active Directory synchronization. Valid Values true | false Default Value false Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Version 8.5.0
261
Default Value SUBTREE Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
ldap://IP_address:port_number ldap://machineName.domain.com:port_number
IBM Unica Campaign - Administrator's Guide
On LDAP servers, the port number is typically 389 (636 if SSL is used). If IBM Unica Marketing is integrated with an Active Directory server, and your Active Directory implementation uses serverless bind, set the value of this property to the URL for your Active Directory server, using the following form: ldap:///dc=example,dc=com Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Version 8.5.0
263
264
Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Version 8.5.0
265
User login
Maps the IBM Unica Marketing user's login to the equivalent user attribute in your LDAP or Active Directory server. User login is the only required mapping. Typically, the value for this attribute is uid for LDAP servers and sAMAccountName for Windows Active Directory servers. You should verify this on your LDAP or Active Directory server. Default Value uid Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
First name
Maps the First Name user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value givenName Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Last name
Maps the Last Name user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value sn Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
User title
Maps the Title user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value title
266
Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Department
Maps the Department user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Company
Maps the Company user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Country
Maps the Country user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
User email
Maps the Email Address attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value mail
Version 8.5.0
267
Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Address 1
Maps the Address user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Work phone
Maps the Work Phone user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value telephoneNumber Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Mobile phone
Maps the Mobile Phone user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Home phone
Maps the Home Phone user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value Undefined
268 IBM Unica Campaign - Administrator's Guide
Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Alternate login
Maps the Alternate Login user attribute in the Marketing Platform to the equivalent user attribute in your LDAP or Active Directory server. Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
N1FA0001
Platform > Security > Login method details > LDAP synchronization > LDAP references for Unica user creation
LDAP reference
The syntax for the LDAP reference value is: SEARCHBASE DELIMITER FILTER where: SEARCHBASE is the Distinguished Name (DN) of the object. For information on how to obtain the value for SEARCHBASE, see the Marketing Platform administrator's documentation. DELIMITER is the value of LDAP config Unica group delimiter FILTER is the LDAP or Active Directory attribute filter. FILTER is optional: if omitted, the Marketing Platform server dynamically creates the filter based on the value of LDAP user reference attribute name.
Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
N1FB0001
Version 8.5.0
269
Platform > Security > Login method details > LDAP synchronization > LDAP reference to Unica group map
LDAP reference map
Users who are members of the LDAP or Active Directory group specified here are imported to the Marketing Platform group specified in the Unica group property. Set the value of this property using the following syntax: SEARCHBASE DELIMITER FILTER where: SEARCHBASE is the Distinguished Name (DN) of the object. DELIMITER is the value of the LDAP config AM group delimiter property. FILTER is the LDAP or Active Directory attribute filter. FILTER is optional: if omitted, the Marketing Platform server dynamically creates the filter based on the value of the LDAP user reference attribute name property. Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
Unica group
Users who are members of the LDAP or Active Directory group specified in the LDAP reference group property are imported to the Marketing Platform group specified here. Default Value Undefined Availability This property is used only when the Marketing Platform is configured to integrate with a Windows Active Directory or other LDAP server.
N1EA0001
270
Integration Name
Read-only. Specifies that IBM Cognos 8 BI is the third-party reporting or analytical tool used by the IBM Unica Marketing to display the reports. Default Value Cognos 8
Vendor
Read-only. Specifies that IBM Cognos is the name of the company that provides the application specified by the Integration Name property. Default Value Cognos
Version
Read-only. Specifies the product version of the application specified by the Integration Name property. Default Value 8.4
Enabled
Specifies whether IBM Cognos 8 BI is enabled for the suite. Valid Values True | False Default Value False
Version 8.5.0
271
Domain
Specifies the fully-qualified company domain name in which your Cognos server is running. For example, myCompanyDomain.com. If your company uses subdomains, the value in this field must include the appropriate subdomain as well. Valid Values A string no longer than 1024 characters. Default Value [CHANGE ME]
Portal URL
Specifies the URL of the IBM Cognos Connection portal. Use a fully qualified host name, including the domain name (and subdomain, if appropriate) that is specified in the Domain property. For example: http://MyReportServer.MyCompanyDomain.com/cognos8/cgibin/cognos.cgi You can find the URL in IBM Cognos Configuration at: Local Configuration > Environment . Valid Values A well-formed URL. Default Value http://[CHANGE ME]/cognos8/cgi-bin/cognos.cgi
Dispatch URL
Specifies the URL of the IBM Cognos Content Manager. Use a fully qualified host name, including the domain name (and subdomain, if appropriate) specified in the Domain property. For example: http://MyReportServer.MyCompanyDomain.com:9300/p2pd/servlet/dispa tch You can find the URL in Cognos Configuration at: Local Configuration > Environment . Valid Values A well-formed URL. Default Value http://[CHANGE ME]:9300/p2pd/servlet/dispatch Note that 9300 is the default port number for the Cognos Content Manager. Be sure that the port number specified matches that used in the Cognos installation.
272 IBM Unica Campaign - Administrator's Guide
Authentication mode
Specifies whether the IBM Cognos application is using the IBM Unica Authentication Provider, which means it relies on the Marketing Platform for authentication. Valid Values anonymous: means authentication is disabled. authenticated: means that the communications between the IBM Unica system and the IBM Cognos system are secured at the machine level. You configure a single system user and configure it with the appropriate access rights. By convention, this user is named "cognos_admin." authenticatedPerUser: means that the system evaluates individual user credentials.
Authentication namespace
Read only. The namespace of the IBM Unica Authentication Provider. Default Value Unica
Version 8.5.0
273
Reports > Schemas > [product] > [schema name] > SQL Configuration
Table/View Name
Specifies the name of the view or table that the SQL script you generate for this reporting schema will create. As a best practice, you should not change the name for any of the standard or default Table/View names. If you do, you must also change the name of the view in the Cognos model in IBM Cognos Framework Manager. When you create a new reporting schema for a new audience level, you must specify the names of all the new reporting tables/views. Valid Values A string with the following restrictions. It can be no longer than 18 characters It must use all UPPER-CASE letters
Following is the naming convention you should use: Start the name with the letter "UAR" Add a one-letter code to represent the IBM Unica application. See the list of codes, below. Add an underscore character Add the table name, including a one or two letter code to indicate the audience level Finish with an underscore character.
274
The SQL generator appends a time dimension code, if appropriate. See the list of codes, below. For example: UARC_COPERF_DY is the name of the reporting view or table for Campaign Offer Performance by Day. Following is the list of IBM Unica application codes. Campaign: C eMessage: E Interact: I Distributed Marketing: X Marketing Operations: P Leads: L
Following is the list of the Time Dimension Codes added by the generator. Hour: HR Day: DY Week: WK Month: MO Quarter: QU Year: YR
Version 8.5.0
275
Audience Key
Specifies the name of the column that is the Audience Key for the audience level supported by this reporting schema. Valid Values A string value no longer than 255 characters If the key includes more than one column, use commas between the column names. For example, ColumnX,ColumnY. Default Value CustomerID
Valid Values Day, Week, Month, Quarter, Year Default Value Day, Month
N2000001
Reports > Schemas > Campaign > [schema name] > Columns > [Contact Metric]
Use this form to add contact metrics to the Campaign Performance or Offer Performance reporting schemas.
Column Name
Specifies the name to use in the reporting view or table for the column specified in the Input Column Name field. Valid Values The name can be no longer than 18 characters, it must be in all UPPER-CASE letters, and it cannot have spaces. Default Value [CHANGE ME]
Function
Specifies how the contact metric is determined or calculated. Valid Values count, count distinct, sum, min, max, average Default Value count
Version 8.5.0
277
Default Value 0
N2010001
Reports > Schemas > Campaign > [schema name] > Columns > [Response Metric]
Use this form to add the response metrics you want to include in your reports to the Campaign Performance or Offer Performance reporting schemas.
Column Name
Specifies the name to use in the reporting view or table for the column specified in the Input Column Name field. Valid Values The name can be no longer than 18 characters, it must be in all UPPER-CASE letters, and it cannot have spaces. Default Value [CHANGE ME]
Function
Specifies how the response metric is determined or calculated. Valid Values count, count distinct, sum, min, max, average Default Value count
278
Default Value 0
N2020001
Audience Key
Specifies the name of the column that is the Audience Key for the audience level supported by this reporting schema. Valid Values A string value no longer than 255 characters If the key includes more than one column, use commas between the column names. For example, ColumnX,ColumnY. Default Value CustomerID
Version 8.5.0 279
280
Reports > Schemas > Campaign > Offer Response Breakout > [Response Type]
Use this form to add to the reporting schema any custom response types you want to include in your reports.
Column Name
Specifies the name to use in the reporting view or table for the column specified in the Response Type Code field. Valid Values The name can be no longer than 18 characters, it must be in all UPPER-CASE letters, and it cannot have spaces. Default Value [CHANGE ME]
Your Campaign installation may have additional custom response type codes. Default Value [CHANGE ME]
Version 8.5.0
281
Default Value 0
N2050001
Reports > Schemas > Campaign > Campaign Offer Contact Status Breakout
This schema supports reporting on campaign-detailed contacts, broken out by contact status type and by offer data. This schema template gives different contact counts for each custom Contact Status Type for campaigns and offers grouped by campaign. By default, none of the example Campaign reports use this schema.
Audience Key
Specifies the name of the column that is the Audience Key for the audience level supported by this reporting schema. Valid Values A string value no longer than 255 characters If the key includes more than one column, use commas between the column names. For example, ColumnX,ColumnY. Default Value CustomerID
282
Reports > Schemas > Campaign > Campaign Offer Contact Status Breakout > [Contact Status Code]
Column Name
Specifies the name to use in the reporting view or table for the column specified in the Contact Status field. Valid Values The name can be no longer than 18 characters, it must be in all UPPER-CASE letters, and it cannot have spaces. Default Value [CHANGE ME]
Contact Status
The name of the contact status code. This is the value held in the ContactStatusCode column in the UA_ContactStatus table. Valid Values The example contact status types are as follows. CSD (campaign send) DLV (delivered) UNDLV (undelivered) CTR (control)
Your Campaign installation may have additional custom contact status types. Default Value [CHANGE ME]
N2070001
Version 8.5.0
283
Reports > Schemas > Campaign > Custom Attributes > Columns > [Campaign Custom Column]
Use this form to add to the reporting schema any custom campaign attributes that you want to include in your reports.
Column Name
Specifies the name to use in the reporting view or table for the attribute identified in the Attribute ID field. Valid Values The name can be no longer than 18 characters, it must be in all UPPER-CASE letters, and it cannot have spaces. Default Value [CHANGE ME]
Attribute ID
The value from the attribute's AttributeID column in the UA_CampAttribute table. Default Value 0
Value Type
The data type of the campaign attribute. Valid Values StringValue, NumberValue, DatetimeValue If this campaign attribute holds a currency value, select NumberValue. If this campaign attribute's Form Element Type was set to Select Box - String in Campaign, select StringValue. Default Value StringValue
N2080001
Reports > Schemas > Campaign > Custom Attributes > Columns > [Offer Custom Column]
Use this form to add to the reporting schema any custom offer attributes that you want to include in your reports.
284
Column Name
Specifies the name to use in the reporting view or table for the attribute identified in the Attribute ID field. Valid Values The name can be no longer than 18 characters, it must be in all UPPER-CASE letters, and it cannot have spaces. Default Value [CHANGE ME]
Attribute ID
The value from the attribute's AttributeID column in the UA_OfferAttribute table. Default Value 0
Value Type
The data type of the offer attribute. Valid Values StringValue, NumberValue, DatetimeValue If this offer attribute holds a currency value, select NumberValue. If this offer attribute's Form Element Type was set to Select Box - String in Campaign, select StringValue. Default Value StringValue
N2090001
Reports > Schemas > Campaign > Custom Attributes > Columns > [Cell Custom Column]
Use this form to add to the reporting schema any custom cell attributes that you want to include in your reports.
Column Name
Specifies the name to use in the reporting view or table for the attribute identified in the Attribute ID field. Valid Values The name can be no longer than 18 characters, it must be in all UPPER-CASE letters, and it cannot have spaces.
Version 8.5.0 285
Attribute ID
The value from the attribute's AttributeID column in the UA_CellAttribute table. Default Value 0
Value Type
The data type of the cell attribute. Valid Values StringValue, NumberValue, DatetimeValue Default Value StringValue
N20A0001
286
Audience Key
Specifies the name of the column that is the Audience Key for the audience level supported by this reporting schema. Valid Values A string value no longer than 255 characters. If the key includes more than one column, use commas between the column names. For example, ColumnX,ColumnY. Default Value CustomerID
Version 8.5.0
287
Campaign
These configuration properties specify the component applications and locales that your installation of Campaign supports.
currencyLocale
The currencyLocale property is a global setting that controls how currency is displayed in the Campaign web application, regardless of the display locale.
288
No currency conversion is performed by Campaign when the display locale changes (for example, if the multi-locale feature is implemented and the display locale changes based on user-specific locales). You must be aware that when a locale is switched, for example, from English US, in which a currency amount is, for example, US$10.00, to a French locale, the currency amount is unchanged (10,00) even if the currency symbol changes with the locale. Default Value en_US
supportedLocales
The supportedLocales property specifies the locales or languagelocale pairs that Campaign supports. The value of this property is set by the installer when you install Campaign. Default Value All languages/locales into which Campaign has been localized.
defaultLocale
The defaultLocale property specifies which of the locales specified in the supportedLocales property is considered the default display locale for Campaign. The value of this property is set by the installer when you install Campaign. Default Value en
acoInstalled
The acoInstalled property specifies whether Optimize is installed. When Optimize is installed and configured, set the value to yes, which causes the Optimize process to be displayed in flowcharts. If the value is true and Optimize is not installed or configured, the process is displayed but disabled (grayed out). path Affinium/Campaign/acoInstalled Valid Values false and true Default Value false
Version 8.5.0
289
collaborateInstalled
The collaborateInstalled property specifies whether Distributed Marketing is installed. When Distributed Marketing is installed and configured, set the value to true, which causes the Distributed Marketing features to be available in the Campaign user interface. Valid Values true | false Default Value false
N20E0001
CollaborateIntegrationServicesURL
The CollaborateIntegrationServicesURL property specifies the server and port number of Distributed Marketing. This URL is used by Campaign when a user publishes a flowchart to Distributed Marketing. Default Value http://localhost:7001/collaborate/services/CollaborateIntegration Services/1.0
N20F0001
welcomePageURI
The welcomePageURI property is used internally by IBM applications. It specifies the Uniform Resource Identifier of the Campaign index page. You should not change this value. Default Value No default value defined.
seedName
The seedName property is used internally by IBM applications. You should not change this value. Default Value No default value defined.
290 IBM Unica Campaign - Administrator's Guide
type
The Campaign > navigation > type property is used internally by IBM applications. You should not change this value. Default Value No default value defined.
httpPort
This property specifies the port used by the Campaign web application server. If your installation of Campaign uses a port that is different from the default, you must edit the value of this property. Default Value 7001
httpsPort
If SSL is configured, this property specifies the port used by the Campaign web application server for secure connections. If your installation of Campaign uses a secure port that is different from the default, you must edit the value of this property. Default Value 7001
serverURL
The Campaign > navigation > serverURL property specifies the URL used by Campaign. If your installation of Campaign has a URL that is different from the default, you should edit the value as follows:
http://machine_name_or_IP_address:port_number/context-root
serverURLInternal
The serverURLInternal property specifies the URL for the Campaign web application when SiteMinder is used. If the property is empty, the value in the serverURL property is used. If you use SiteMinder, you must set this value to the URL for the Campaign web application server, formatted as follows:
http://machine_name_or_IP_address:port_number/context-root
path Affinium/Campaign/navigation/serverURLInternal
Version 8.5.0 291
campaignDetailPageURI
The campaignDetailPageURI property is used internally by IBM applications. It specifies the Uniform Resource Identifier of the Campaign detail page. You should not change this value. Default Value campaignDetails.do?id=
flowchartDetailPageURI
The flowchartDetailPageURI property is used to construct a URL to navigate to the details of a flowchart in a specific campaign. You should not change this value. Default Value flowchartDetails.do?campaignID=&id=
offerDetailPageURI
The offerDetailPageURI property is used to construct a URL to navigate to the details of a specific offer. You should not change this value. Default Value offerDetails.do?id=
offerlistDetailPageURI
The offerlistDetailPageURI property is used to construct a URL to navigate to the details of a specific offer list. You should not change this value. Default Value displayOfferList.do?offerListId=
displayName
The displayName property specifies the link text used for the Campaign link in the drop-down menu that exists in the GUI of each IBM product. Default Value Campaign
N2100001
offerTemplateDataTTLSeconds
The offerTemplateDataTTLSeconds property specifies the length of time, in seconds, that the system retains the Offer Template cache data (Time to Live). An empty value means the cache data is never purged. Default Value 600 (10 minutes)
campaignDataTTLSeconds
The campaignDataTTLSeconds property specifies the length of time, in seconds, that the system retains the Campaign cache data (Time to Live). An empty value means the cache data is never purged. Default Value 600 (10 minutes)
sessionDataTTLSeconds
The sessionDataTTLSeconds property specifies the length of time, in seconds, that the system retains the Session cache data (Time to Live). An empty value means the cache data is never purged. Default Value 600 (10 minutes)
folderTreeDataTTLSeconds
The folderTreeDataTTLSeconds property specifies the length of time, in seconds, that the system retains the Folder Tree cache data (Time to Live). An empty value means the cache data is never purged. Default Value 600 (10 minutes)
attributeDataTTLSeconds
The attributeDataTTLSeconds property specifies the length of time, in seconds, that the system retains the Offer Attribute cache data (Time to Live). An empty value means the cache data is never purged. Default Value 600 (10 minutes)
Version 8.5.0
293
initiativeDataTTLSeconds
The initiativeDataTTLSeconds property specifies the length of time, in seconds, that the system retains the Initiative cache data (Time to Live). An empty value means the cache data is never purged. Default Value 600 (10 minutes)
offerDataTTLSeconds
The offerDataTTLSeconds property specifies the length of time, in seconds, that the system retains the Offer cache data (Time to Live). An empty value means the cache data is never purged. Default Value 600 (10 minutes)
segmentDataTTLSeconds
The segmentDataTTLSeconds property specifies the length of time, in seconds, that the system retains the Segment cache data (Time to Live). An empty value means the cache data is never purged. Default Value 600 (10 minutes)
N2110001
eMessagePluginJarFile
Complete path to the location of the plugin file that operates as the Recipient List Uploader (RLU). This plugin to Campaign uploads OLT data and associated metadata to the remote services hosted by IBM. The location you specify must be the full local directory path in the file system for the machine that hosts the Campaign web application server.
294
The IBM installer populates this setting automatically for the default partition when you run the installer. For additional partitions, you must configure this property manually. Because there is only one RLU for each eMessage installation, all partitions must specify the same location for the RLU. Do not change this setting unless IBM instructs you to do so. Valid Values Full local directory path to the machine where you installed the Campaign web server. Default Value No default value defined.
defaultSeedInterval
The number of messages between seed messages if defaultSeedType is Distribute list. Default Value 1000
defaultSeedType
The default method that eMessage uses to insert seed addresses into a recipient list. Valid Values Distribute IDS - Distribute IDs evenly, based on the size of the recipient list and the number of seed addresses available, inserts seed addresses at equal intervals throughout the entire recipient list. Distribute list - Insert seed address for every defaultSeedInterval IDs in main list. Inserts the entire list of available seed addresses at specified intervals throughout the recipient list. You must specify the interval between insertion points.
oltTableNamePrefix
Used in the generated schema for the output list table. You must define this parameter. Valid Values The prefix can contain no more than 8 alphanumeric or underscore characters, and must start with a letter. Default Value OLT
Version 8.5.0
295
oltDimTableSupport
This configuration parameter controls the ability to add dimension tables to output list tables (OLT) created in the eMessage schema. Dimension tables are required to use advanced scripting for email to create data tables in email messages. The default setting is False. You must set this property to True enable marketers to create dimension tables when they use the eMessage process to define a recipient list. For more information about creating data tables and using advanced scripts for email, see the eMessage User's Guide. Valid Values True | False Default Value False
N2130001
offerAnalysisTabCachedFolder
The offerAnalysisTabCachedFolder property specifies the location of the folder that contains the specification for bursted offer reports listed on the Analysis tab when you reach it by clicking the Analysis link on the navigation pane. The path is specified using XPath notation. Default Value /content/folder[@name='Affinium Campaign - Object Specific Reports']/folder[@name='offer']/folder[@name='cached']
segmentAnalysisTabOnDemandFolder
The segmentAnalysisTabOnDemandFolder property specifies the location of the folder that contains the segment reports listed on the Analysis tab of a segment. The path is specified using XPath notation. Default Value /content/folder[@name='Affinium Campaign - Object Specific Reports']/folder[@name='segment']/folder[@name='cached']
offerAnalysisTabOnDemandFolder
The offerAnalysisTabOnDemandFolder property specifies the location of the folder that contains the offer reports listed on the Analysis tab of an offer. The path is specified using XPath notation.
296
segmentAnalysisTabCachedFolder
The segmentAnalysisTabCachedFolder property specifies the location of the folder that contains the specification for bursted segment reports listed on the Analysis tab when you reach it by clicking the Analysis link on the navigation pane. The path is specified using XPath notation. Default Value /content/folder[@name='Affinium Campaign - Object Specific Reports']/folder[@name='segment']
analysisSectionFolder
The analysisSectionFolder property specifies the location of the root folder where report specifications are stored. The path is specified using XPath notation. Default Value /content/folder[@name='Affinium Campaign']
campaignAnalysisTabOnDemandFolder
The campaignAnalysisTabOnDemandFolder property specifies the location of the folder that contains the campaign reports listed on the Analysis tab of a campaign. The path is specified using XPath notation. Default Value /content/folder[@name='Affinium Campaign - Object Specific Reports']/folder[@name='campaign']
campaignAnalysisTabCachedFolder
The campaignAnalysisTabCachedFolder property specifies the location of the folder that contains the specification for bursted campaign reports listed on the Analysis tab when you reach it by clicking the Analysis link on the navigation pane. The path is specified using XPath notation. Default Value /content/folder[@name='Affinium Campaign - Object Specific Reports']/folder[@name='campaign']/folder[@name='cached']
campaignAnalysisTabEmessageOnDemandFolder
The campaignAnalysisTabEmessageOnDemandFolder property specifies the location of the folder that contains the eMessage reports listed on the Analysis tab of a campaign. The path is specified using XPath notation.
Version 8.5.0 297
campaignAnalysisTabInteractOnDemandFolder
Report server folder string for Interact reports. Default Value /content/folder[@name='Affinium Campaign']/folder[@name='Interact Reports'] Availability This property is applicable only if you have installed Interact.
interactiveChannelAnalysisTabOnDemandFolder
Report server folder string for Interactive Channel analysis tab reports Default Value /content/folder[@name='Affinium Campaign - Object Specific Reports']/folder[@name='interactive channel'] Availability This property is applicable only if you have installed Interact.
N2140001
validationClass
The validationClass property specifies the name of the class used for validation in Campaign. The path to the class is specified in the validationClasspath property. The class must be fully qualified with its package name. For example: com.unica.campaign.core.validation.samples.SimpleCampaignValidato r indicates the SimpleCampaignValidator class from the sample code. This property is undefined by default, which causes Campaign to perform no custom validation.
298
validationConfigString
The validationConfigString property specifies a configuration string that is passed into the validation plugin when Campaign loads it. The use of the configuration string may vary, depending on the plugin used. This property is undefined by default. Default Value No default value defined.
validationClasspath
The validationClasspath property specifies the path to the class used for custom validation in Campaign. You may specify the path as follows: The value may be either full path or a relative path. If the path is not an absolute path, the behavior depends on the application server that is running Campaign. WebLogic uses the path to the domain work directory which by default is
c:\bea\user_projects\domains\mydomain.
If the path ends in a slash (forward slash / for UNIX or backslash \ for Windows), then Campaign assumes the path is to a directory that contains the Java plug-in class that should be used. If the path does not end in a slash, then Campaign assumes that it is the name of a jar file that contains the java class. For example: The value /opt/affinium/campaign/pdk/lib/validation.jar is the path on a UNIX platform that would point to the jar file that comes out of the box with the plug-in developer kit. This property is undefined by default, which causes the property to be ignored.
Version 8.5.0
299
Properties in the partition[n] > audienceLevels > audienceLevel category specify the number of fields in the audience level and the name of an audience level. These properties are populated when a user creates audience levels udience levels in Campaign. You should not edit properties in this category.
numFields
This property is populated when a user creates audience levels on the Administration page in Campaign. You should not edit this property. Default Value No default value defined.
audienceName
This property is populated when a user creates audience levels on the Administration page in Campaign. You should not edit this property. Default Value No default value defined.
N2160002
Campaign > partitions > partition[n] > audienceLevels > audienceLevel > field[n]
Properties in the this category define an audience level field. These properties are populated when a user creates audience levels on the Administration page in Campaign You should not edit properties in this category.
type
The partition[n] > audienceLevels > audienceLevel > field[n] > type property is populated when a user creates audience levels on the Administration page in Campaign. You should not edit this property. Default Value No default value defined.
name
The partition[n] > audienceLevels > audienceLevel > field[n] > name property is populated when a user creates audience levels on the Administration page in Campaign. You should not edit this property. Default Value No default value defined.
N2170003
300
AccessLibrary
Campaign chooses its data source access library according to the data source type. For example, libora4d.so is used for Oracle connectivity, while libdb24d.so is used for DB2 connectivity. In most cases, the default selections are appropriate. However, the AccessLibrary property can be changed if the default value proves to be incorrect in your Campaign environment. For example, 64-bit Campaign provides two ODBC access libraries: one appropriate for ODBC data sources compatible with the unixODBC implementation (libodb4d.so used by Campaign to access, for example, Informix), and the other compatible with the DataDirect implementation (libodb4dDD.so used by Campaign to access, for example, Teradata).
If you determine that the default access library should be overridden (for example, if you purchase a DataDirect driver manager and driver for Informix), set this parameter as required (in the example, to libodb4dDD.so, overriding the default selection of libodb4d.so). This property is empty by default. Default Value No default value defined.
Version 8.5.0
301
ASMSaveDBAuthentication
The ASMSaveDBAuthentication property specifies whether, when you log in to Campaign and map a table in a data source you have not previously logged in to, Campaign saves your user name and password in IBM Unica Marketing. If you set this property to TRUE, Campaign does not prompt you for a user name and password when you subsequently log in to the data source. If you set this property to FALSE, Campaign prompts you for a user name and password each time you log in to the data source. Valid Values TRUE | FALSE Default Value TRUE
ASMUserForDBCredentials
The ASMUserForDBCredentials property specifies the IBM Unica Marketing user name assigned to the Campaign system user (required for accessing the Campaign system tables). This property is undefined by default. Default Value No default value defined.
AllowBaseJoinsInSelect
Determines whether Campaign attempts to perform a SQL join of base tables (from the same data source) used in a Select process; otherwise, the equivalent join is performed on the Campaign server. Valid Values TRUE | FALSE Default Value TRUE
AliasPrefix
The AliasPrefix property specifies the way Campaign forms the alias name that Campaign creates automatically when using a dimension table and writing to a new table. Note that each database has a maximum identifier length; check the documentation for the database you are using to be sure that the value you set does not exceed the maximum identifier length for your database.
302
Default Value A
AllowSegmentUsingSQLCase
The AllowSegmentUsingSQLCase property specifies whether the Campaign Segment process consolidates multiple SQL statements into a single SQL statement, when specific configuration conditions are met. Setting this property to TRUE results in significant performance improvements when all of the following conditions are met: Segments are mutually exclusive. All segments come from a single table. Criteria for each segment are based on the IBM macro language.
In this case, Campaign generates a single SQL CASE statement to perform segmentation, followed by segment-by-field processing on the Campaign application server. Valid Values TRUE | FALSE Default Value TRUE
AllowTempTables
The AllowTempTables property specifies whether Campaign creates temporary tables in the database. Creating temporary tables can significantly improve the performance of campaigns. When the value is TRUE, temporary tables are enabled. When temporary tables are enabled, each time a query is issued against the database (for example, by the Segment process), the resulting IDs are written in a temporary table in the database. When an additional query is issued, Campaign may use that temporary table to retrieve rows from the database. If temporary tables are not enabled, Campaign retains the selected IDs in the server memory. The additional query retrieves IDs from the database and matches them to the IDs in server memory. For more information on controlling temporary table joins, see MaxTempTableJoinPctSelectAll and MaxTempTableJoinPctWithCondition. You must have appropriate privileges to write in the database to use temporary tables. This is determined by the database login you provide when you connect to the database. Default Value TRUE
Version 8.5.0
303
UseTempTablePool
This property is supported only for Teradata data sources. For all other supported databases, this option should be set to FALSE. When the UseTempTablePool property is set to TRUE, temp tables will not be dropped from the database. Temp tables will be truncated and reused from the pool of tables maintained by Campaign. When set to FALSE, temp tables are dropped and re-created every time a flowchart is run. Valid Values TRUE | FALSE Default Value FALSE
TempTablePreTruncateRunScript
This property is supported only for Teradata data sources. For all other supported databases, this property should not be set. Use the TempTablePreTruncateRunScript property to specify a script or executable that will be run before a temp table is truncated. The script that you specify can be used to negate the effect of a SQL statement specified in the PostTempTableCreateRunScript property. For example, with the PostTempTableCreateRunScript property, you could specify a script that includes the following SQL statement to create an index: CREATE INDEX <TABLENAME>Idx_1 (<KEYCOLUMNS>) ON <TABLENAME> Then, specify another script with the following statement in the TempTablePreTruncateRunScript property to drop the index: DROP INDEX <TABLENAME>Idx_1 ON <TABLENAME> Valid Values File name of a shell script or executable Default Value Not defined
TempTablePreTruncateExecutionSQL
This property is supported only for Teradata data sources. For all other supported databases, this property should not be set.
304
Use the TempTablePreTruncateExecutionSQL property to specify a SQL query that will be run before a temp table is truncated. The query that you specify can be used to negate the effect of a SQL statement specified in the TempTablePostExecutionSQL property. For example, with the TempTablePostExecutionSQL property, you could specify the following SQL statement to create an index: CREATE INDEX <TABLENAME>Idx_1 (<KEYCOLUMNS>) ON <TABLENAME> Then, specify the following query in the TempTablePreTruncateExecutionSQL property to drop the index: DROP INDEX <TABLENAME>Idx_1 ON <TABLENAME> Valid Values A valid SQL query Default Value Not defined
BulkInsertBlockSize
The BulkInsertBlockSize property defines the maximum size of a data block, in number of records, that Campaign passes to the database at a time. Default Value 100
BulkInsertRequiresColumnType
The BulkInsertRequiresColumnType property is required to support Data Direct ODBC data sources only. Set this property to TRUE for Data Direct ODBC data sources when using bulk (array) inserts. Set the property to FALSE to be compatible with most other ODBC drivers. Default Value FALSE
BulkReaderBlockSize
The BulkReaderBlockSize property defines the size of a data block, in number of records, that Campaign reads from the database at a time. Default Value 2500
Version 8.5.0
305
ConditionalSQLCloseBracket
The ConditionalSQLCloseBracket property specifies the type of bracket used to indicate the end of a conditional segment in raw SQL custom macros. Conditionalized segments enclosed within the brackets specified by the ConditionalSQLOpenBracket and ConditionalSQLCloseBracket properties are used only if temp tables exist, and are ignored if there are no temp tables. Default Value } (closing curly brace)
ConditionalSQLOpenBracket
The ConditionalSQLOpenBracket property specifies the type of bracket used to indicate the start of a conditional segment in raw SQL custom macros. Conditionalized segments enclosed within the brackets specified by the ConditionalSQLOpenBracket and ConditionalSQLCloseBracket properties are used only if temp tables exist, and are ignored if there are no temp tables. Default Value { (opening curly brace)
ConnectionCacheSize
The ConnectionCacheSize property specifies the number of connections that Campaign maintains in a cache for each data source. By default (N=0), Campaign establishes a new connection to a data source for each operation; if Campaign maintains a cache of connections and a connection is available for reuse, Campaign uses the cached connection rather than establishing a new connection. If the setting is not 0, once a process is done with a connection, Campaign keeps up to the specified number of connections open for an amount of time specified by the InactiveConnectionTimeout property. After this time expires, the connections are removed from the cache and closed. Default Value 0 (zero)
DSN
Use the DSN property to identify the physical data source for the Campaign data source you are defining. This value is undefined by default. You can specify multiple logical data sources that refer to the same physical data source. For example, you can create two Campaign data sources, one with AllowTempTables = TRUE and the other with AllowTempTables = FALSE. Each of these data sources would have a different data source name in Campaign, but if they refer to the same physical data source they will have the same DSN value.
306
DSNUsingOSAuthentication
The DSNUsingOSAuthentication property applies only when an Campaign data source is SQL Server. Set the the value to TRUE when the DSN is configured to use Windows Authentication mode. Valid Values TRUE | FALSE Default Value FALSE
DateFormat
Campaign uses the value of the DateFormat property to determine how to parse data in date formats when using the Campaign macro language or when interpreting data from date columns. Set the value of the DateFormat property to the format in which Campaign expects to receive dates from this data source. The value must match the format your database uses to display dates on select. For most databases, this setting is the same as the setting for the DateOutputFormatString property. If you use the multi-locale feature, you should not use date formats containing 3letter months (MMM), %b (abbreviated month name), or %B (full month name). Instead, you should use a delimited or fixed format with a numeric value for the month. To determine the date format your database uses, select a date from the database as described in the following table. Selecting a date by database
Database DB2 To determine the correct setting ... Connect to the database from a machine running the Campaign server. Use db2test, located in the Campaign\bin directory, to connect and issue the following command: values current date
Version 8.5.0
307
Database Informix
To determine the correct setting ... Informix has different formats for writing and selecting from the database. Connect to the database from a machine running the Campaign server. Use odbctest, located in the Campaign\bin directory, to connect and issue the following command: select today from informix.systables where tabid=1;
Netezza
Connect to the database from a machine running the Campaign server. Use odbctest, located in the Campaign\bin directory, to connect and issue the following command: CREATE TABLE date_test (f1 DATE); INSERT INTO date_test values (current_date); SELECT f1 FROM date_test; Another way to select date format is to run following command: SELECT current_date FROM ANY_TABLE limit 1; where ANY_TABLE is the name of any existing table
Oracle
Log into the database from the machine running the Campaign server. Use SQL *Plus to connect and issue the following command: SELECT sysdate FROM dual The current date is returned in NLS_DATE_FORMAT for that client.
SQL Server
Connect to the database from a machine running the Campaign listener. Use odbctest, located in the Campaign\bin directory, to connect and issue the following command: SELECT getdate()
Sybase
Connect to the database from a machine running the Campaign server. Use odbctest, located in the Campaign\bin directory, to connect and issue the following command: select today(*) from sys.dummy;
Additional considerations
Note the following database-specific instructions.
308
Teradata Teradata allows you to define the date format on a per-column basis. In addition to dateFormat and dateOutputFormatString, you need to set SuffixOnCreateDateField. To be consistent with our system table settings, use: SuffixOnCreateDateField = FORMAT 'YYYY-MM-DD' DateFormat = DELIM_Y_M_D DateOutputFormatString = %Y-%m-%d
SQL Server If the Use regional settings when outputting currency, numbers, dates, and times option is not checked in the ODBC data source configuration, then you cannot reset the date format. In general, it is easier to leave this setting unchecked so that the date format configuration does not change for each language. Valid Values Any of the formats specified in the DATE macro Default Value DELIM_Y_M_D
DateOutputFormatString
The DateOutputFormatString property specifies the format of the date datatype to be used when Campaign writes any date, such as a campaign start or end date, to a database. Set the value of the DateOutputFormatString property to the format that the data source expects for columns of the type date. For most databases, this setting is the same as the setting for the [data_source_name] > DateFormat property. The DateOutputFormatString property can be set to any of the formats specified for format_strin the DATE_FORMAT macro. Note that the DATE_FORMAT macro accepts two different kinds of formats. One is an identifier (for example, DELIM_M_D_Y, DDMMMYYYY, the same as accepted by the DATE macro), while the other is a format string. The value of the DateOutputFormatString property must be a format string it must not be one of the DATE macro identifiers. Typically, use one of the delimited formats. You can verify whether you have selected the correct format by creating a table and inserting a date in the format you selected, as described in the following procedure.
To verify DateOutputFormatString
1. Connect to the database using the appropriate tool, as described in the table for "Selecting a date by database". Do not use the query tools that come with the database (such as SQL Servers Query Analyzer) to verify that dates are being sent to the database correctly. These query tools might convert the date format to something other than what Campaign actually sent to the database.
Version 8.5.0
309
2. Create a table and insert a date in the format you selected. For example, if you selected %m/%d/%Y:
CREATE TABLE date_test (F1 DATE) INSERT INTO date_test VALUES ('03/31/2004')
If the database allows the INSERT command to complete successfully, then you have selected the correct format. Default Value %Y/%m/%d
DateTimeFormat
The value of the [data_source_name] > DateTimeFormat property specifies the format in which Campaign expects to receive datetime/timestamp data from a database. It must match the format your database uses to display datetime/timestamp data on select. For most databases, this setting is the same as the setting for DateTimeOutputFormatString. Typically, you should set the DateTimeFormat by prepending your DateFormat value with DT_ after determining the DateFormat value as described in the table for " Selecting a date by database". If you use the multi-locale feature, you should not use date formats containing 3letter months (MMM), %b (abbreviated month name), or %B (full month name). Instead, you should use a delimited or fixed format with a numeric value for the month. Valid Values Only delimited formats are supported, as follows: DT_DELIM_M_D DT_DELIM_M_D_Y DT_DELIM_Y_M DT_DELIM_Y_M_D DT_DELIM_M_Y DT_DELIM_D_M DT_DELIM_D_M_Y
310
DateTimeOutputFormatString
The DateTimeOutputFormatString property specifies the format of the datetime datatype to be used when Campaign writes any datetime, such as a campaign start or end date and time, to a database.Set the value of the DateTimeOutputFormatString property to the format that the data source expects for columns of the type datetime. For most databases, this setting is the same as the setting for the [data_source_name] > DateTimeFormat property. See DateOutputFormatString for a method for verifying that the format you select is correct. Default Value %Y/%m/%d %H:%M:%S
DB2NotLoggedInitially
The DB2NotLoggedInitially property determines whether Campaign uses the not logged initially SQL syntax when populating temporary tables in DB2. When set to TRUE, this property disables logging for inserts into temp tables, which improves performance and decreases database resource consumption. If your version of DB2 does not support the not logged initially syntax, set this property to FALSE. Valid Values TRUE | FALSE Default Value TRUE
DB2NotLoggedInitiallyUserTables
The DB2NotLoggedInitiallyUserTables property determines whether Campaign uses the not logged initially SQL syntax for inserts into DB2 user tables. When set to TRUE, this property disables logging for inserts into the user tables, which improves performance and decreases database resource consumption. When set to TRUE, if a user table transaction fails for any reason, the table will become corrupted and must be dropped. All data previously contained in the table will be lost. The DB2NotLoggedInitiallyUserTables property is not used for the Campaign system tables. Valid Values TRUE | FALSE
Version 8.5.0
311
DefaultScale
The DefaultScale property determines floating point precision when a Campaign Snapshot process exports numeric fields to a table. When the value is 0 (zero) Campaign preserves the floating point precision in the field being exported. You can limit the floating point precision by changing this property. For example, if you set the value at 3, floating point precision would be three places (0.NNN). Default Value 0 (zero)
DeleteAsRecreate
The DeleteAsRecreate property specifies whether, when an output process is configured to REPLACE TABLE and if TRUNCATE is not supported, Campaign drops and recreates the table or only deletes from the table. When the value is TRUE, Campaign drops the table and recreates it. When the value is FALSE, Campaign executes a DELETE FROM from the table. Valid Values TRUE | FALSE Default Value FALSE
DeleteAsTruncate
The DeleteAsTruncate property specifies whether, when an output process is configured to REPLACE TABLE, Campaign uses TRUNCATE TABLE or deletes from the table. When the value is TRUE, Campaign executes a TRUNCATE TABLE from the table. When the value is FALSE, Campaign executes a DELETE FROM from the table. The default value depends on the database type. Valid Values TRUE | FALSE Default Value TRUE for Netezza, Oracle, Sybase and SQLServer. FALSE for other database types.
312
DisallowTempTableDirectCreate
The DisallowTempTableDirectCreate property specifies the way Campaign adds data to a temp table. When set to FALSE, Campaign performs direct create-and-populate SQL syntax using one command; for example, CREATE TABLE <table_name> AS ... (for Oracle and Netezza) and SELECT <field_names> INTO <table_name> ... (for SQL Server). When set to TRUE, Campaign creates the temp table and then populates it directly from table to table using separate commands. Valid Values TRUE | FALSE Default Value FALSE
EnableBaseDimSelfJoin
The EnableBaseDimSelfJoin property specifies whether the Campaign database behavior will perform self-joins when the Base and Dimension tables are mapped to the same physical table and the Dimension is not related to the Base table on the Base table's ID field(s). By default, this property is set to FALSE, and when the Base and Dimension tables are the same database table and the relationship fields are the same (for example, AcctID to AcctID), Campaign assumes you do not want to perform a join. Default Value FALSE
EnableSelectDistinct
The EnableSelectDistinct property specifies whether the internal lists of IDs for Campaign are de-duplicated by the Campaign server or by the database. When the value is TRUE, the database performs de-duplication, and SQL queries generated against the database then have the form (when appropriate):
SELECT DISTINCT key FROM table
When the value is FALSE, the Campaign server performs de-duplication, and SQL queries generated against the database have the form:
SELECT key FROM table
Version 8.5.0
313
Your database is constructed so that unique identifiers (primary keys of base tables) are already guaranteed to be de-duped. You want the Campaign application server to perform de-duplication to reduce resource consumption/burden on the database.
Regardless of what value you specify for this property, Campaign automatically ensures that keys are de-duplicated as required. This property merely controls where the deduplication effort occurs (on the database or on the Campaign server). Valid Values TRUE | FALSE Default Value TRUE
EnableSelectOrderBy
The EnableSelectOrderBy property specifies whether the internal lists of IDs for Campaignare sorted by the Campaign server or by the database. When the value is TRUE, the database performs the sorting, and SQL queries generated against the database have the form:
SELECT <key> FROM <table> ORDER BY <key>
When the value is FALSE, the Campaign server performs the sorting, and SQL queries generated against the database have the form:
SELECT <key>FROM <table>
Only set this property to FALSE if the audience levels used are text strings on a nonEnglish database. All other scenarios can use the default of TRUE. Valid Values True | False Default Value TRUE
ExcludeFromTableDisplay
The ExcludeFromTableDisplay parameter allows you to limit the database tables that are displayed during table mapping in Campaign. It does not reduce the number of table names retrieved from the database. Table names matching the specified patterns are not displayed.
314
For example, if you set the value of this parameter to sys.*, tables with names that begin with sys. are not displayed. Note that the values for this parameter are casesensitive. Default Value UAC_*, which excludes temp tables and Extract tables, when the ExtractTablePrefix propertys value is the default value
ExtractTablePrefix
The ExtractTablePrefix property specifies a string that is automatically prepended to all Extract table names in Campaign. Default Value UAC_EX
ForceNumeric
The ForceNumeric property specifies whether Campaign retrieves numeric values as the data type double. When the value is set to TRUE, Campaign retrieves all numeric values as the data type double. Valid Values TRUE | FALSE Default Value FALSE
InactiveConnectionTimeout
The InactiveConnectionTimeout property specifies the number of seconds an inactive Campaign database connection is left open before it is closed. Setting the value to 0 disables the timeout, leaving the connection open. Default Value 120
InsertLogSize
The InsertLogSize property specifies when a new entry is entered in the log file while the Campaign Snapshot process is running. Every time the number of records written by the Snapshot process reaches a multiple of the number specified in the InsertLogSize property, a log entry is written. The log entries can help you determine how far a running Snapshot process has progressed. Note that setting this value too low may create large log files. Valid Values Postitive integers
Version 8.5.0 315
JndiName
The JndiName property is used only when configuring the Campaign system tables (not for other data sources, such as customer tables). Set its value to the Java Naming and Directory Interface (JNDI) data source that is defined in the application server (Websphere or WebLogic). Default Value campaignPartition1DS
LoaderCommand
The LoaderCommand property specifies the command issued to invoke your database load utility in Campaign. If you set this parameter, Campaign enters the database loader utility mode for all output files from the Snapshot process that are used with the replace all records settings. This parameter also invokes the database loader utility mode when Campaign uploads ID lists into temp tables. The valid value for this property is any full path name either to the database load utility executable or to a script that launches the database load utility. Using a script allows you to perform additional setup before invoking the load utility (for example, moving files to a database server first or invoking ISQL to use the load command in Sybase IQ). Most database load utilities require several arguments to be launched successfully. These arguments can include specifying the data file and control file to load from and the database and table to load into. Campaign supports the following tokens, which are replaced by the specified elements when the command is run. Consult your database load utility documentation for the correct syntax to use when invoking your database load utility. This parameter is undefined by default. Tokens available to LoaderCommand are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart being run. This token is replaced with the code for the campaign associated with the flowchart. This token is replaced with the name of the campaign associated with the flowchart being run.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
316
Token <CONTROLFILE>
Description This token is replaced with the full path and file name to the temporary control file that Campaign generates according to the template that is specified in the LoaderControlFileTemplate parameter. This token is replaced with the name of the data source that Campaign is loading data into. This is the same data source name used in the category name for this data source. This token is replaced with the full path and file name to the temporary data file created by Campaign during the loading process. This file is in the Campaign Temp directory, UNICA_ACTMPDIR. This token is replaced with the database user name for the database. This token is replaced with the value of the DSN property. If the DSN property is not set, the <DSN> token is replaced by the data source name used in the category name for this data source (the same value used to replace the <DATABASE> token). This token is replaced with the name of the flowchart being run. This token is replaced with the number of fields in the table. This token is replaced with the database password from the current flowchart connection to the data source. This token is obsolete, but is supported for backward compatibility. See <TABLENAME>, which replaced <TABLE> as of version 4.6.3. This token is replaced with the database table name that Campaign is loading data into. This is the target table from your Snapshot process or the name of the Temp Table being created by Campaign. This token is replaced with the database user from the current flowchart connection to the data source.
<DATABASE>
<DATAFILE>
<DBUSER>
<DSN>
<FLOWCHARTNAME>
<NUMFIELDS> <PASSWORD>
<TABLE>
<TABLENAME>
<USER>
Version 8.5.0
317
Valid Values Any full path name either to the database load utility executable or to a script that launches the database load utility Default Value No default value defined.
LoaderCommandForAppend
The LoaderCommandForAppend parameter specifies the command issued to invoke your database load utility for appending records to a database table in Campaign. If you set this parameter, Campaign enters database loader utility mode for all output files from the Snapshot process that are used with the append records settings. This parameter is specified as a full path name either to the database load utility executable or to a script that launches the database load utility. Using a script allows you to perform additional setup before invoking the load utility (for example, moving files to a database server first or invoking ISQL to use the load command in Sybase IQ). Most database load utilities require several arguments to be successfully launched. These can include specifying the data file and control file to load from and the database and table to load into. The tokens are replaced by the specified elements when the command is run. Consult your database load utility documentation for the correct syntax to use when invoking your database load utility. This parameter is undefined by default. Tokens available to LoaderCommandForAppend are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart being run. This token is replaced with the code for the campaign associated with the flowchart being run. This token is replaced with the name of the campaign associated with the flowchart being run. This token is replaced with the full path and file name to the temporary control file that Campaign generates according to the template that is specified in the LoaderControlFileTemplate parameter. This token is replaced with the name of the data source that Campaign is loading data into. This is the same data source name used in the category name for this data source. IBM Unica Campaign - Administrator's Guide
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<CONTROLFILE>
<DATABASE>
318
Token <DATAFILE>
Description This token is replaced with the full path and file name to the temporary data file created by Campaign during the loading process. This file is in the Campaign Temp directory, UNICA_ACTMPDIR. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the value of the DSN property. If the DSN property is not set, the <DSN> token is replaced by the data source name used in the category name for this data source (the same value used to replace the <DATABASE> token). This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the number of fields in the table. This token is replaced with the database password from the current flowchart connection to the data source. This token is obsolete, but is supported for backward compatibility. See <TABLENAME>, which replaced <TABLE> as of version 4.6.3. This token is replaced with the database table name that Campaign is loading data into. This is the target table from your Snapshot process or the name of the Temp Table being created by Campaign. This token is replaced with the database user from the current flowchart connection to the data source.
<DBUSER>
<DSN>
<FLOWCHARTNAME>
<NUMFIELDS> <PASSWORD>
<TABLE>
<TABLENAME>
<USER>
LoaderControlFileTemplate
The LoaderControlFileTemplate property specifies the full path and file name to the control file template that has been previously configured in Campaign. When this parameter is set, Campaign dynamically builds a temporary control file based on the template that you specify here. The path and name of this temporary control file is available to the <CONTROLFILE> token that is available to the LoaderCommand parameter.
Version 8.5.0 319
Before you use Campaign in the database loader utility mode, you must configure the control file template that is specified by this parameter. The control file template supports the following tokens, which are dynamically replaced when the temporary control file is created by Campaign. For the correct syntax required for your control file, please see your database loader utility documentation. This parameter is undefined by default. Tokens available to LoaderControlFileTemplate are the same as those described for the LoaderCommand property, plus the following special tokens, which are repeated once for each field in the outbound table.
Description This token is replaced with the column ordinal in the database. This token is replaced with the length of the field being loaded into the database. This token is replaced with the name of the field being loaded into the database. This token is replaced with the number of the field being loaded into the database. This token is replaced with the literal "CHAR( )". The length of this field is specified between the (). If your database happens to not understand the field type, CHAR, you can manually specify the appropriate text for the field type and use the <FIELDLENGTH> token. For example, for SQLSVR and SQL2000 you would use "SQLCHAR(<FIELDLENGTH>)" This token is replaced with the actual database type that this field is loaded into. This token places the specified character(s) on all fields being loaded into the database, except the last. A typical use is <,> which repeats a comma all fields except the last. This token places the specified characters only on the last repeated line. This token places the specified character(s), including the angle brackets < >, on all lines.
<FIELDNAME>
<FIELDNUMBER>
<FIELDTYPE>
<NATIVETYPE>
<xyz>
<~xyz>
<!xyz>
320
LoaderControlFileTemplateForAppend
The LoaderControlFileTemplateForAppend property specifies the full path and file name to the control file template that has been previously configured in Campaign. When this parameter is set, Campaign dynamically builds a temporary control file based on the template that is specified here. The path and name of this temporary control file is available to the <CONTROLFILE> token that is available to the LoaderCommandForAppend property. Before you use Campaign in the database loader utility mode, you must configure the control file template that is specified by this parameter. The control file template supports the following tokens, which are dynamically replaced when the temporary control file is created by Campaign. See your database loader utility documentation for the correct syntax required for your control file. Tokens available to your control file template are the same as those for the LoaderControlFileTemplate property. This parameter is undefined by default. Default Value No default value defined.
LoaderDelimiter
The LoaderDelimiter property specifies whether the temporary data file is a fixedwidth or delimited flat file, and, if it is delimited, the characters Campaign uses as delimiters. If the value is undefined, Campaign creates the temporary data file as a fixed width flat file. If you specify a value, it is used when the loader is invoked to populate a table that is known to be empty. Campaign creates the temporary data file as a delimited flat file, using the value of this property as the delimiter. This property is undefined by default. Valid Values Characters, which can be enclosed in double quotes, if desired. Default Value No default value defined.
Version 8.5.0
321
LoaderDelimiterAtEnd
Some external load utilities require that the data file be delimited and that each line end with the delimiter (for example, Informix's dbaccess using External Tables). To accommodate this requirement, set the LoaderDelimiterAtEnd value to TRUE, so that when the loader is invoked to populate a table that is known to be empty, Campaign uses delimiters at the end of each line. FALSE Valid Values TRUE | FALSE Default Value FALSE
LoaderDelimiterAtEndForAppend
Some external load utilities require that the data file be delimited and that each line end with the delimiter (for example, Informix's dbaccess using External Tables). To accommodate this requirement, set the LoaderDelimiterAtEndForAppend value to TRUE, so that when the loader is invoked to populate a table that is not known to be empty, Campaign uses delimiters at the end of each line. Valid Values TRUE | FALSE Default Value FALSE
LoaderDelimiterForAppend
The LoaderDelimiterForAppend property specifies whether the temporary Campaign data file is a fixed-width or delimited flat file, and, if it is delimited, the character or set of characters used as delimiters. If the value is undefined, Campaign creates the temporary data file as a fixed width flat file. If you specify a value, it is used when the loader is invoked to populate a table that is not known to be empty. Campaign creates the temporary data file as a delimited flat file, using the value of this property as the delimiter. This property is undefined by default. Valid Values Characters, which you may enclose in double quotes, if desired. Default Value No default value defined.
322 IBM Unica Campaign - Administrator's Guide
LoaderUseLocaleDP
The LoaderUseLocaleDP property specifies, when Campaign writes numeric values to files to be loaded by a database load utility, whether the locale-specific symbol is used for the decimal point. Set this value to FALSE to specify that the period (.) is used as the decimal point. Set this value to TRUE to specify that the decimal point symbol appropriate to the locale is used. Valid Values TRUE | FALSE Default Value FALSE
MaxItemsInList
Allows you to specify the maximum number of items that Campaign is allowed to include in a single list in SQL (for example, the list of values following an IN operator in a WHERE clause). Valid Values integers Default Value 1000 (Oracle only), 0 (unlimited) for all other databases
MaxQueryThreads
The MaxQueryThreads property specifies the upper limit on the number of simultaneous queries allowed to run against each database source from a single Campaign flowchart. Campaign executes database queries using independent threads. Because Campaign processes run in parallel, it is common to have multiple queries executing simultaneously against a single data source. If the number of queries to be run in parallel exceeds the value specified by this property, the Campaign server automatically limits the number of simultaneous queries to this value. The maximum value is unlimited. Note that when the maxReuseThreads property is set to a non-zero value, it should be greater than or equal to the value ofMaxQueryThreads. Default Value Varies depending on the database
Version 8.5.0
323
MaxRowFetchRecords
When the selected number of IDs is less than the value specified by the MaxRowFetchRecords property, Campaign passes the IDs to the database, one at a time in a separate SQL query. This process may be very time-consuming. If the number of selected IDs is greater than the value specified by this parameter, Campaign uses temporary tables (if allowed against the database source), or it pulls down all the values from the table, not including any unnecessary values. For performance reasons, it is recommended to keep this number low. Default Value 100
MaxTempTableJoinPctSelectAll
When a query is issued, Campaign creates a temporary table on the database containing the exact list of IDs, as a result of the query. When an additional query that selects all records is issued against the database, the MaxTempTableJoinPctSelectAll property specifies whether a join is performed with the temporary table. If the relative size of the temporary table (specified as a percentage) is greater than the value of the MaxTempTableJoinPctWithCondition property, no join is performed. All records are selected first, then unwanted records are discarded. If the relative size of the temporary table (specified as a percentage) is less then or equal to the value of MaxTempTableJoinPctWithCondition property, the join is performed with the temporary table first, and then the resulting IDs are retrieved to the server. This property is applicable only if the value of the AllowTempTables property is set to TRUE. This property is ignored if the useInDbOptimization property is set to YES. Valid Values Integers between 0-100. A value of 0 means that temporary table joins are never used; a value of 100 means that table joins are always used, regardless of the size of the temporary table. Default Value 90 Example Assume that MaxTempTableJoinPctSelectAll is set to 90. First, you might want to select customers (CustID) with account balances (Accnt_balance) greater than $1,000 from the database table (Customer). The corresponding SQL expression generated by the Select process may look like this:
SELECT CustID FROM Customer WHERE Accnt_balance > 1000
324
The Select process may retrieve 100,000 IDs from the total table size of 1,000,000, which is 10%. If temporary tables are allowed, Campaign writes the selected IDs (TempID) into a temporary table (Temp_table) in the database. Then, you might want to snapshot the selected IDs (CustID) together with the actual balance (Accnt_balance). Since the relative size of the temporary table (Temp_table) is less than 90 percent (MaxTempTableJoinPctSelectAll), the join is done with the temporary table first. The SQL expression generated by the Snapshot process may look like this:
SELECT CustID, Accnt_balance FROM Customer, Temp_table WHERE CustID = TempID
If the Select process retrieves more than 90 percent the subsequent Snapshot process retrieves all the records, and matches them with the first set of IDs, discarding the unnecessary ones. The SQL expression generated by the Snapshot process may look like this:
SELECT CustID, Accnt_balance FROM Customer
MaxTempTableJoinPctWithCondition
When a query is issued, Campaign creates a temporary table on the database containing the exact list of IDs, as a result of the query. When an additional query, selecting records with limitation conditions is issued against the database, the MaxTempTableJoinPctWithCondition property specifies whether a join should be performed with the temporary table. If the relative size of the temporary table (specified as a percentage) is greater than the value of MaxTempTableJoinPctWithCondition, no join is performed. This avoids the overhead in the database where it may not be needed. In this case, the query is issued against the database, the resulting list of IDs retrieved, and then unwanted records are discarded as they are matched to the list in server memory. If the relative size of the temporary table (in percentage) is less than or equal to the value of MaxTempTableJoinPctWithCondition, the join is done with the temporary table first, and then the resulting IDs are retrieved to the server. This property is applicable only if the value of the AllowTempTables property is set to TRUE. Valid Values Integers between 0-100. A value of 0 means temporary table joins are never used; a value of 100 means that table joins are always used, regardless of the size of the temporary table. Default Value 20
Version 8.5.0
325
MinReqForLoaderCommand
Use this property to set the threshold for using the bulk loader. Campaign invokes the script assigned to the LoaderCommand parameter when the number of unique IDs in the input cell exceeds the value defined here. The value of this property does not represent the number of records that will be written. If this property is not configured, Campaign assumes the value is the default value (zero). If this property is configured but a negative value or non-integer value is set as the value, Campaign assumes the value is zero. Valid Values Integers Default Value 0 (zero)
MinReqForLoaderCommandForAppend
Use this property to set the threshold for using the bulk loader. Campaign invokes the script assigned to the LoaderCommandForAppend parameter when the number of unique IDs in the input cell exceeds the value defined here. The value of this property does not represent the number of records that will be written. If this property is not configured, Campaign assumes the value is the default value (zero). If this property is configured but a negative value or non-integer value is set as the value, Campaign assumes the value is zero. Valid Values Positive integers Default Value 0 (zero)
NumberOfRetries
The NumberOfRetries property specifies the number of times Campaign automatically retries a database operation on failure. Campaign automatically resubmits queries to the database this number of times before reporting a database error or failure. Default Value 0 (zero)
ODBCTableTypes
The ODBCTableTypes property is required to support Sybase IQ/ASE data sources only. Campaign requires this property to be set in order to display the list of tables in the table mapping window. Add the following values to this property to enable mapping for Sybase IQ/ASE data sources:
326 IBM Unica Campaign - Administrator's Guide
'TABLE','VIEW','SYNONYM','ALIAS' This property is empty by default, which is appropriate for data sources other than Sybase IQ/ASE. Valid Values 'TABLE','VIEW','SYNONYM','ALIAS' Default Value Not defined
ODBCUnicode
The ODBCUnicode property specifies the type of encoding used in Campaign ODBC calls. It is used only with ODBC data sources and is ignored when used with Oracle or DB2 native connectivity. If this property is set to UTF-8 or UCS-2, the data sources StringEncoding value must be set to either UTF-8 or WIDEUTF-8, otherwise the ODBCUnicode propertys setting is ignored. Valid Values Possible values for this property are: Disabled - Campaign uses ANSI ODBC calls. UTF-8 - Campaign uses Unicode ODBC calls and assumes a SQLWCHAR is a single byte. This is compatible with DataDirect ODBC drivers. UCS-2 - Campaign uses Unicode ODBC calls and assumes a SQLWCHAR is 2 bytes. This is compatible with Windows and unixODBC ODBC drivers.
ODBCv2
Use the ODBCv2 property to specify which ODBC API specification Campaign should use for the data source. The default value of FALSE allows Campaign to use the v3 API specification, while a setting of TRUE causes Campaign to use the v2 API specification. Set the ODBCv2 property to TRUE for data sources that do not support the ODBC v3 API specification. When the ODBCv2 property is set to TRUE, Campaign does not support the ODBC Unicode API, and values other than disabled for the ODBCUnicode property are not recognized. Valid Values TRUE | FALSE
Version 8.5.0
327
OwnerForTableDisplay
The OwnerForTableDisplay property allows you to limit the table mapping display in Campaign to tables owned by a specified user, or to one or more sets of tables owned by the specified user(s). To display only those tables owned by one or more users, specify the database user IDs using a comma-separated list. For example:
<property name="OwnerForTableDisplay">user1,user2,user3</property>
To specify a table name pattern in addition to the user name, append the pattern to the user ID. For example, the following setting limits the table display to tables beginning with ABC for user1 and XYZ for user2:
OwnerForTableDisplay=user1.ABC%,user2.XYZ%
PostSegmentTableCreateRunScript
Specifies a script or executable that Campaign runs after a Segment temp table has been created and populated. Tokens available to PostSegmentTableCreateRunScript are described in the following table:
Token <DBUSER>
Description This token is replaced with the database user name for the database where the Segment temp table was created. This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the Segment temp table was created. This token is replaced with the name of the campaign associated with the flowchart for which the Segment temp table was created. This token is replaced with the code for the campaign associated with the flowchart for which the Segment temp table was created.
<AMUSER>
<CAMPAIGNNAME>
<CAMPAIGNCODE>
328
Token <FLOWCHARTNAME>
Description This token is replaced with the name of the flowchart associated with the Segment temp table creation. This token is replaced with the database password from the current flowchart connection to the data source. This token is replaced with the Segment temp table column name(s).
<PASSWORD>
<KEYCOLUMNS>
Valid Values File name of a script or executable Default Value Not defined
PostSnapshotTableCreateRunScript
Use the PostSnapshotTableCreateRunScript property to specify a script or executable that Campaign runs after a Snapshot table has been created and populated. Tokens available to PostSnapshotTableCreateRunScript are described in the following table:
Token <DBUSER>
Description This token is replaced with the database user name for the database where the Snapshot table was created. This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the Snapshot table was created. This token is replaced with the name of the campaign associated with the flowchart for which the Snapshot table was created. This token is replaced with the code for the campaign associated with the flowchart for which the Snapshot table was created. This token is replaced with the name of the flowchart associated with the Snapshot table creation.
<AMUSER>
<CAMPAIGNNAME>
<CAMPAIGNCODE>
<FLOWCHARTNAME>
Version 8.5.0
329
Token <PASSWORD>
Description This token is replaced with the database password from the current flowchart connection to the data source. This token is replaced with the Snapshot table column name(s).
<KEYCOLUMNS>
Valid Values File name of a shell script or executable Default Value Not defined
PostExtractTableCreateRunScript
Use the PostExtractTableCreateRunScript property to specify a script or executable for Campaign to run after an Extract table has been created and populated. Tokens available to PostExtractTableCreateRunScript are described in the following table:
Token <DBUSER>
Description This token is replaced with the database user name for the database where the Extract table was created. This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the Extract table was created. This token is replaced with the name of the campaign associated with the flowchart for which the Extract table was created. This token is replaced with the code for the campaign associated with the flowchart for which the Extract table was created. This token is replaced with the name of the flowchart associated with the Extract table creation. This token is replaced with the database password from the current flowchart connection to the data source. This token is replaced with the Extract table column name(s). IBM Unica Campaign - Administrator's Guide
<AMUSER>
<CAMPAIGNNAME>
<CAMPAIGNCODE>
<FLOWCHARTNAME>
<PASSWORD>
<KEYCOLUMNS> 330
Valid Values File name of a shell script or executable Default Value Not defined
PadTextWithSpaces
When set to TRUE, the PadTextWithSpaces property causes Campaign to pad text values with spaces until the string is the same width as the database field. Valid Values TRUE | FALSE Default Value FALSE
PostTempTableCreateRunScript
Use the PostTempTableCreateRunScript property to specify a script or executable for Campaign to run after a temp table has been created and populated in a user data source or in the system tables database. Tokens available to PostTempTableCreateRunScript are described in the following table:
Token <DBUSER>
Description This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation.
<AMUSER>
<CAMPAIGNNAME>
<CAMPAIGNCODE>
<FLOWCHARTNAME>
Version 8.5.0
331
Token <PASSWORD>
Description This token is replaced with the database password from the current flowchart connection to the data source. This token is replaced with the temp table column name(s).
<KEYCOLUMNS>
PostUserTableCreateRunScript
Specifies a script or executable that Campaign runs after a User table has been created and populated. Tokens available to PostUserTableCreateRunScript are described in the following table:
Token <DBUSER>
Description This token is replaced with the database user name for the database where the User table was created. This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the User table was created. This token is replaced with the name of the campaign associated with the flowchart for which the User table was created. This token is replaced with the code for the campaign associated with the flowchart for which the User table was created. This token is replaced with the name of the flowchart associated with the User table creation. This token is replaced with the database password from the current flowchart connection to the data source. This token is replaced with the User table column name(s).
<AMUSER>
<CAMPAIGNNAME>
<CAMPAIGNCODE>
<FLOWCHARTNAME>
<PASSWORD>
<KEYCOLUMNS>
PrefixOnSelectSQL
Use the PrefixOnSelectSQL property to specify a string that is automatically prepended to all SELECT SQL expressions generated by Campaign. This property applies only to SQL generated by Campaign, and does not apply to SQL in raw SQL expressions used in the Select process. This property is automatically added to the SELECT SQL expression without checking its syntax. If you use this property, make sure it is a legal expression. This property is undefined by default. Tokens available to PrefixOnSelectSQL are described in the following table:
Token <AMUSER> Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<USER>
QueryThreadSleep
The QueryThreadSleep property affects the CPU utilization of the Campaign server process (UNICA_ACSVR). When the value is TRUE, the thread that the Campaign server process uses to check for query completion sleeps between checks. When the value is FALSE, the Campaign server process checks continuously for query completion.
Version 8.5.0 333
ReaderLogSize
The ReaderLogSize parameter defines when Campaign makes a new entry in the log file when reading data from the database. Every time the number of records read from the database reaches a multiple of the number defined by this parameter, a log entry is written in the log file. This parameter can help you determine how far a process has progressed in its run. Setting this value too low may create large log files. Valid Values Integers Default Value 1000000 (one million records)
SegmentTempTablePrefix
Sets the prefix for Segment tables created by the CreateSeg process in this data source. Default Value UACS
SQLOnConnect
The SQLOnConnect property defines a complete SQL statement that Campaign executes immediately after each database connection. The SQL statement generated by this property is automatically passed to your database without checking its syntax. If you use this property, make sure it is a legal expression. The string may be enclosed in quotes, but this is not required. This property is undefined by default. Tokens available to SQLOnConnect are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created.
<CAMPAIGNCODE>
334
Token <CAMPAIGNNAME>
Description This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the Campaign user name of the user running the flowchart.
<DBUSER>
<FLOWCHARTNAME>
<USER>
UOSQLOnConnect
The SQLOnConnect property defines a complete SQL statement that Campaign executes immediately after each database connection. The UOSQLOnConnect property is similar to this, but specifically applicable to Optimize. The SQL statement generated by this property is automatically passed to your database without checking its syntax. If you use this property, make sure it is a legal expression. The string may be enclosed in quotes, but this is not required. This property is undefined by default. Tokens available to UOSQLOnConnect are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
Version 8.5.0
335
Token <DBUSER>
Description This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the Campaign user name of the user running the flowchart.
<FLOWCHARTNAME>
<USER>
ShareConnection
The ShareConnection property controls the number of connections Campaign uses for database operations. When the value is FALSE each database operation is performed on a new connection. When the value is TRUE a single connection is used to execute all database operations. Valid Values TRUE | FALSE Default Value FALSE
StringEncoding
The StringEncoding property specifies the character encoding of the database. When Campaign retrieves data from the database, the data is transcoded from the encoding specified to the internal encoding of Campaign (UTF-8). Likewise, when Campaign sends a query to the database, character data is transcoded from the internal encoding of Campaign to the encoding specified in the StringEncoding property. The value of this property must match the encoding used on the database client. You should not leave this value blank although it is undefined by default. If you use ASCII data, set this value to UTF-8. If your database clients encoding is set for UTF-8, the recommended setting for this value is WIDEUTF-8. The WIDE-UTF-8 setting only works if your database client is set to UTF-8. If you use the partitions > partition[n] > dataSources > [data_source_name] > ODBCUnicode property, this property is set to either UTF-8 or WIDEUTF-8, otherwise the ODBCUnicode propertys setting is ignored.
336
See Appendix C, Internationalization and Encodings for a list of supported encodings. See the following sections for important exceptions and additional considerations. Default Value No default value defined. Example
Database-specific considerations
For DB2, or SQL Server, you should use a code page rather than an iconv encoding. For Teradata, you should override some default behavior. This section describes set the correct value for the StringEncoding property with these databases. DB2 To determine the correct value for the StringEncoding property with a DB2 database, look up the code page that corresponds to the regional settings of the Campaign servers operating system. To set the value of the StringEncoding property for a DB2 database, add this command to the Campaign server startup script:
db2set DB2CODEPAGE=CPIBM_code_page
This affects all DB2 data sources and may affect other running programs. SQL Server To determine the correct the value for the StringEncoding property with a SQL Server database, look up the code page that corresponds to the regional settings of the server's operating system. For example, to use Code Page 932 (Japanese Shift-JIS):
StringEncoding=CP932
Teradata Note that Teradata supports per-column character encoding, while Campaign supports only per-data source encoding. UTF-8 cannot be used with Campaign due to a bug in the Teradata ODBC driver. Teradata sets a default character encoding for each login. You can override this using a parameter in the ODBC data source configuration on Windows or in the odbc.ini on UNIX platforms as follows:
CharacterSet=UTF8
Version 8.5.0
337
The default encoding for a Teradata table is LATIN. Teradata has very few built-in encodings, but it supports user-defined encodings. The default value of the StringEncoding property is ASCII. For many situations involving a UTF-8 database, we recommend that you use WIDEUTF-8 pseudo-encoding, described in the WIDEUTF-8 section.
WIDEUTF-8
Campaign is normally responsible for transcoding between its internal encoding, UTF-8, and the encoding of the database. When the database is encoded in UTF-8, the value UTF-8 can be specified for StringEncoding (except for SQLServer), and no transcoding will be needed. Traditionally, these have been the only viable models for Campaign to access non-English data within a database. In the 7.0 version of Campaign, a new database encoding called WIDEUTF-8 was introduced as a valid value for the StringEncoding property. By using this encoding, Campaign still uses UTF-8 to communicate with the database client, but allows the client to perform the task of transcoding between UTF-8 and the encoding of the actual database. This enhanced version of UTF-8 is needed to alter the widths of table column mappings so that they will be wide enough for transcoded text. The WIDEUTF-8 pseudo-encoding may be used only in the database configuration. It should not be used for any other purpose. Oracle does not support transcoding through the client.
SuffixOnAllOtherSQL
The SuffixOnAllOtherSQL property specifies a string that is automatically appended to every SQL expression, generated by Campaign, which are not covered by the SuffixOnInsertSQL, SuffixOnSelectSQL, SuffixOnTempTableCreation, SuffixOnUserTableCreation, or SuffixOnUserBaseTableCreation properties. This property applies only to SQL generated by Campaign, and does not apply to SQL in raw SQL expressions used in the Select process. SuffixOnAllOtherSQL is used for the following expression types, when generated by Campaign:
TRUNCATE TABLE table DROP TABLE table DELETE FROM table [WHERE ...] UPDATE table SET ...
This property is automatically added to the SQL expression without checking its syntax. If you use this parameter, make sure it is a legal expression. The string may be enclosed in quotes, but this is not required. This property is undefined by default.
338 IBM Unica Campaign - Administrator's Guide
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<USER>
SuffixOnCreateDateField
The SuffixOnCreateDateField property specifies a string that Campaign automatically appends to any DATE fields in the CREATE TABLE SQL statement. For example, you might set this property as follows:
SuffixOnCreateDateField = FORMAT 'YYYY-MM-DD
If this property is undefined (the default), the CREATE TABLE command is unchanged. See the table in the description of the DateFormat property. Default Value No default value defined.
Version 8.5.0
339
SuffixOnInsertSQL
The SuffixOnInsertSQL property specifies a string that is automatically appended to all INSERT SQL expressions generated by Campaign. This property applies only to SQL generated by Campaign, and does not apply to SQL in raw SQL expressions used in the Select process. SuffixOnInsertSQL is used for the following expression type, when generated by Campaign:
INSERT INTO table ...
This property is automatically added to the SQL expression without checking its syntax. If you use this property , make sure it is a legal expression. The string may be enclosed in quotes, but this is not required. This property is undefined by default. Tokens available to SuffixOnInsertSQL are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<USER>
340
SuffixOnSelectSQL
The SuffixOnSelectSQL property specifies a string that is automatically appended to all SELECT SQL expressions generated by Campaign. This property applies only to SQL generated by Campaign, and is does not apply to SQL in raw SQL expressions used in the Select process. This property is automatically added to the SQL expression without checking its syntax. If you use this property, make sure it is a legal expression. The string may be enclosed in quotes, but this is not required. This property is undefined by default. Tokens available to SuffixOnSelectSQL are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<USER>
SuffixOnTempTableCreation
Use the SuffixOnTempTableCreation property to specify a string that is automatically appended to the SQL expression generated by Campaign when a temp table is created. This property applies only to SQL generated by Campaign, and does not apply to SQL in raw SQL expressions used in the Select process. To use this property, the AllowTempTables property must be set to TRUE.
Version 8.5.0
341
You may want to use tokens to substitute the table name and the column name(s) (<TABLENAME> and <KEYCOLUMNS>) in this SQL statement, since these are generated dynamically during the execution of the campaign. This property is automatically added to the SQL expression without checking its syntax. If you use this property, make sure it is a legal expression. The string may be enclosed in quotes, but this is not required. This property is undefined by default. For Oracle databases, the configuration parameter is appended to the temp table creation SQL expression after the table name. Tokens available to SuffixOnTempTableCreation are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the temp table column name(s). This token is replaced with the temp table name. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
342
SuffixOnSegmentTableCreation
Specifies a string that is automatically appended to the SQL expression generated by Campaign when a Segment temp table is created. Tokens available to SuffixOnSegmentTableCreation are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the Segment temp table was created. This token is replaced with the code for the campaign associated with the flowchart for which the Segment temp table was created. This token is replaced with the name of the campaign associated with the flowchart for which the Segment temp table was created. This token is replaced with the database user name for the database where the Segment temp table was created. This token is replaced with the name of the flowchart associated with the Segment temp table creation. This token is replaced with the Segment temp table column name(s). This token is replaced with the Segment temp table name. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<KEYCOLUMNS>
<TABLENAME> <USER>
SuffixOnSnapshotTableCreation
Use the SuffixOnSnapshotTableCreation property to specify a string that is automatically appended to the SQL expression generated by Campaign when a Snapshot table is created.
Version 8.5.0 343
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the Snapshot table was created. This token is replaced with the code for the campaign associated with the flowchart for which the Snapshot table was created. This token is replaced with the name of the campaign associated with the flowchart for which the Snapshot table was created. This token is replaced with the database user name for the database where the Snapshot table was created. This token is replaced with the name of the flowchart associated with the Snapshot table creation. This token is replaced with the Snapshot table column name(s). This token is replaced with the Snapshot table name. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<KEYCOLUMNS>
<TABLENAME> <USER>
SuffixOnExtractTableCreation
Use the SuffixOnExtractTableCreation property to specify a string that is automatically appended to the SQL expression generated by Campaign when an Extract table is created. Tokens available to SuffixOnExtractTableCreation are described in the following table:
344
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the Extract table was created. This token is replaced with the code for the campaign associated with the flowchart for which the Extract table was created. This token is replaced with the name of the campaign associated with the flowchart for which the Extract table was created. This token is replaced with the database user name for the database where the Extract table was created. This token is replaced with the name of the flowchart associated with the Extract table creation. This token is replaced with the Extract table column name(s). This token is replaced with the Extract table name. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
SuffixOnUserBaseTableCreation
Use the SuffixOnUserBaseTableCreation property to specify a string that is automatically appended to the SQL expression that Campaign generates when a user creates a Base table (for example, in an Extract process). This property applies only to SQL generated by Campaign, and does not apply to SQL in raw SQL expressions used in the Select process. You may want to use tokens to substitute the table name and the column name(s) (<TABLENAME> and <KEYCOLUMNS>) in this SQL statement, since these are generated dynamically during the execution of the campaign. This property is automatically added to the SQL expression without checking its syntax. If you use this property, make sure it is a legal expression. The string may be enclosed in quotes, but this is not required.
Version 8.5.0 345
This property is undefined by default. Tokens available to SuffixOnUserBaseTableCreation are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the temp table column name(s). This token is replaced with the temp table name. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
SuffixOnUserTableCreation
Use the SuffixOnUserTableCreation property to specify a string that is automatically appended to the SQL expression that Campaign generates when a user creates a General table (for example, in a Snapshot process). This property applies only to SQL generated by Campaign, and does not apply to SQL in raw SQL expressions used in the Select process. This property is automatically added to the SQL expression without checking its syntax. If you use this property, make sure it is a legal expression. The string may be enclosed in quotes, but this is not required. This property is undefined by default.
346 IBM Unica Campaign - Administrator's Guide
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the temp table name.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<TABLENAME>
SystemTableSchema
Specifies the schema used for Campaign system tables. The default value is blank. This parameter is only relevant for the UA_SYSTEM_TABLES data source. Leave this value blank unless the UA_SYSTEM_TABLES data source contains multiple schemas (for example, an Oracle database used by multiple groups). (In this context, schema indicates the initial portion of a qualified table name of the form X.Y (for example, dbo.UA_Folder). In this form, X is the schema and Y is the unqualified table name. This terminology for this syntax differs among the different database systems supported by Campaign.) If multiple schemas exist in the system tables database, then set this value to the name of the schema in which the Campaign system tables were created. Default Value No default value defined.
Version 8.5.0
347
TempTablePostExecutionSQL
Use the TempTablePostExecutionSQL property to specify a complete SQL statement that Campaign executes immediately after the creation of a temporary table in a user data source or in the system tables database. The AllowTempTables property must be set to TRUE to enable the creation of temp tables in a data source. You may want to use tokens to substitute the table name and the column name(s) (<TABLENAME> and <KEYCOLUMNS>) in this SQL statement, since these are generated dynamically during the execution of the campaign. This property is automatically added to the SQL expression without checking its syntax. If you use this property, make sure it is a legal expression. The string may be enclosed in quotes, but this is not required. The TempTablePostExecutionSQL property treats semicolons as delimiters to execute multiple SQL statements. If your SQL statement contains semicolons and you want it to execute as one statement, use a backslash as an escape character before the semicolons. If you are using stored procedures with the TempTablePostExecutionSQL property, be sure that you use the correct syntax for your database. The following example for Oracle calls a stored procedure and uses backslashes to escape the semicolon: begin dbms_stats.collect_table_stats()\; end\; Tokens available to TempTablePostExecutionSQL are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the temp table column name(s).
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<KEYCOLUMNS>
348
Description This token is replaced with the temp table name. This token is replaced with the Campaign user name of the user running the flowchart.
TableListSQL
Use the TableListSQL property to specify the SQL query to use to include synonyms in the list of tables available to map. The default value is blank. This property is required if your data source is SQL Server and you want to be able to map synonyms in the returned table schema. This property is optional if you want to use a specific SQL query with other data sources in place of, or in addition to, the table schema information retrieved using the standard methods (such as an ODBC call or native connection). To ensure that Campaign works with SQL Server synonyms, you must set the UseSQLToRetrieveSchema property to TRUE in addition to setting this property as described here. If you set this property with a valid SQL query, Campaign issues the SQL query to retrieve the list of tables for mapping. If the query returns one column, it's treated as a column of names; if the query returns two columns, the first column is assumed to be a column of owner names, and the second column is considered to be a column of table names. If the SQL query does not begin with an asterisk (*), Campaign merges this list with the list of tables that are normally retrieved (such as through ODBC calls or native connections). If the SQL query begins with an asterisk (*), the list returned by the SQL replaces the normal list, rather than being merged with it. Valid Values A valid SQL query Default Value None Example If the data source is SQL Server, under normal circumstances the ODBC API call that Campaign uses returns a list of tables and views, but no synonyms. To include the list of synonyms as well, set TableListSQL similar to the following:
Version 8.5.0 349
A - Configuration Properties on the Configuration Page select B.name AS oName, A.name AS tName from sys.synonyms A LEFT OUTER JOIN sys.schemas B on A.schema_id = B.schema_id ORDER BY 1, 2
To retrieve the list of tables, views, and synonyms, avoiding the ODBC API completely, set TableListSQL similar to the following:
*select B.name AS oName, A.name AS tName from (select name, schema_id from sys.synonyms UNION select name, schema_id from sys.tables UNION select name, schema_id from sys.views) A LEFT OUTER JOIN sys.schemas B on A.schema_id = B.schema_id ORDER BY 1, 2
If the data source is Oracle, you can use a query similar to the following to retrieve the list of tables, views, and synonyms in place of the data retrieved using the native connection method that looks at the ALL_OBJECTS view:
*select OWNER, TABLE_NAME from (select OWNER, TABLE_NAME from ALL_TABLES UNION select OWNER, SYNONYM_NAME AS TABLE_NAME FROM ALL_SYNONYMS UNION select OWNER, VIEW_NAME AS TABLE_NAME from ALL_VIEWS) A ORDER BY 1, 2
UseSQLToRetrieveSchema
Uses a SQL query, rather than an ODBC or native API call, to retrieve the schema to use as the table's schema for this data source. The default value for this property is FALSE, indicating that Campaign should use its standard method (ODBC or native connection, for example) to retrieve the schema. Setting this property to TRUE causes Campaign to prepare a SQL query similar to select * from <table> to retrieve the table's schema. This can provide advantages that are specific to each data source. For example, some data sources (Netezza, SQL Server) do not properly report SQL synonyms (alternative names for database objects, defined using the create synonym syntax) through the default ODBC or native connections. By setting this property to TRUE, SQL synonyms are retrieved for data mapping within Campaign. The following list describes the behavior of this setting for a number of data sources: For Netezza, you must set this property to TRUE to allow support for synonyms. Setting this property to TRUE tells Campaign to prepare a SQL query to retrieve the table's schema. No other settings or values are needed to support synonyms in Netezza data sources. For SQL Server, to allow support for synonyms you must set this property to TRUE and enter valid SQL in the TableListSQL property for this data source. See the description for the TableListSQL property for more details. For Oracle data sources, setting this property to TRUE tells Campaign to prepare the SQL query to retrieve the table's schema. The result set identifies NUMBER fields (no precision/scale specified, which may cause issues in Campaign) as NUMBER(38), which avoids those possible issues.
350
For other data sources, you can optionally set this property to TRUE to use the default SQL select query described above, or to specify valid SQL in the TableListSQL property to use instead of, or in addition to, the ODBC API or native connection that is used by default. See the description for the TableListSQL property for more details.
Valid Values TRUE | FALSE Default Value FALSE Example To allow Campaign to work with Netezza or SQL Server synonyms:
UseSQLToRetrieveSchema=TRUE
UserTablePostExecutionSQL
Use the UserTablePostExecutionSQL property to specify a complete SQL statement that Campaign executes immediately after the creation of a user table in a user data source or in the system tables database. You may want to use tokens to substitute the table name and the column name(s) (<TABLENAME> and <KEYCOLUMNS>) in this SQL statement, since these are generated dynamically during the execution of the campaign. This property is automatically added to the SQL expression without checking its syntax. If you use this property, make sure it is a legal expression. The string may be enclosed in quotes, but this is not required. The UserTablePostExecutionSQL property treats semicolons as delimiters to execute multiple SQL statements. If your SQL statement contains semicolons and you want it to execute as one statement, use a backslash as an escape character before the semicolons. If you are using stored procedures with the UserTablePostExecutionSQL property, be sure that you use the correct syntax for your database. The following example for Oracle calls a stored procedure and uses backslashes to escape the semicolon: begin dbms_stats.collect_table_stats()\; end\; Tokens available to UserTablePostExecutionSQL are described in the following table:
Version 8.5.0
351
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the user tables were created. This token is replaced with the code for the campaign associated with the flowchart for which the user tables were created. This token is replaced with the name of the campaign associated with the flowchart for which the user tables were created. This token is replaced with the database user name for the database where the user tables were created. This token is replaced with the name of the flowchart associated with the user table creation. This token is replaced with the user table column name(s). This token is replaced with the user table name. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
SegmentTablePostExecutionSQL
Use the SegmentTablePostExecutionSQL property to specify a complete SQL statement that Campaign runs after a Segment temp table has been created and populated. Tokens available to SegmentTablePostExecutionSQL are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the Segment temp table was created.
352
Token <CAMPAIGNCODE>
Description This token is replaced with the code for the campaign associated with the flowchart for which the Segment temp table was created. This token is replaced with the name of the campaign associated with the flowchart for which the Segment temp table was created. This token is replaced with the database user name for the database where the Segment temp table was created. This token is replaced with the name of the flowchart associated with the Segment temp table creation. This token is replaced with the Segment temp table column name(s). This token is replaced with the Segment temp table name. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<KEYCOLUMNS>
<TABLENAME> <USER>
SnapshotTablePostExecutionSQL
Use the SnapshotTablePostExecutionSQL property to specify one or more complete SQL statements that are executed immediately after a Snapshot table has been created and populated. Tokens available to SnapshotTablePostExecutionSQL are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the Snapshot table was created.
Version 8.5.0
353
Token <CAMPAIGNCODE>
Description This token is replaced with the code for the campaign associated with the flowchart for which the Snapshot table was created. This token is replaced with the name of the campaign associated with the flowchart for which the Snapshot table was created. This token is replaced with the database user name for the database where the Snapshot table was created. This token is replaced with the name of the flowchart associated with the Snapshot table creation. This token is replaced with the Snapshot table column name(s). This token is replaced with the Snapshot table name. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<KEYCOLUMNS>
<TABLENAME> <USER>
ExtractTablePostExecutionSQL
Use the ExtractTablePostExecutionSQL property to specify one or more complete SQL statements that are executed immediately after the creation and population of an Extract table. Tokens available to ExtractTablePostExecutionSQL are described in the following table:
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which the Extract table was created.
354
Token <CAMPAIGNCODE>
Description This token is replaced with the code for the campaign associated with the flowchart for which the Extract table was created. This token is replaced with the name of the campaign associated with the flowchart for which the Extract table was created. This token is replaced with the database user name for the database where the Extract table was created. This token is replaced with the name of the flowchart associated with the Extract table creation. This token is replaced with the Extract table column name(s). This token is replaced with the Extract table name. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
TempTablePrefix
The TempTablePrefix parameter specifies a string that is automatically prepended to the names of all temporary tables created by Campaign. You should use this parameter to help you identify and manage your temp tables. You also can use this property to cause temp tables to be created in a particular location. For example, if the user token corresponds to a schema, you can set
TempTablePrefix="<USER>"
and all temp tables will be created in the schema of whatever user is connected to the data source. Tokens available to TempTablePrefix are described in the following table:
Version 8.5.0
355
Token <AMUSER>
Description This token is replaced with the IBM Unica Marketing user name associated with the flowchart for which temp tables were created. This token is replaced with the code for the campaign associated with the flowchart for which temp tables were created. This token is replaced with the name of the campaign associated with the flowchart for which temp tables were created. This token is replaced with the database user name for the database where the temp tables were created. This token is replaced with the name of the flowchart associated with the temp table creation. This token is replaced with the Campaign user name of the user running the flowchart.
<CAMPAIGNCODE>
<CAMPAIGNNAME>
<DBUSER>
<FLOWCHARTNAME>
<USER>
You must make sure the final temp table name after resolving tokens does not exceed any database-specific name length restrictions. In tokens used for TempTablePrefix, any characters that are not valid for database table names will be stripped. After tokens are resolved, the resulting temp table prefixes must start with an alphabetic character, and must contain only alphanumeric characters or underscore characters. Illegal characters will be removed silently. If any resulting temp table prefix does not begin with an alphabetic character, Campaign prepends the letter U to the prefix. Default Value UAC
TeradataDeleteBeforeDrop
The TeradataDeleteBeforeDrop parameter applies only to Teradata data sources. It specifies whether records are deleted prior to a table being dropped. Set this value to TRUE to delete all records from a table prior to dropping the table. If Campaign is unable to delete the records for any reason, it will not drop the table. Set this value to FALSE to drop a table without first deleting all records.
356
TruncateSQL
The TruncateSQL property is available for use with DB2 data sources, and allows you to specify alternate SQL for table truncation. This property applies only when DeleteAsTruncate is set to TRUE. When DeleteAsTruncate is set to TRUE, any custom SQL in this property is used to truncate a table. When this property is not set, Campaign uses the TRUNCATE TABLE <TABLENAME> syntax. This parameter is undefined by default. Tokens available to TruncateSQL are described in the following table:
Token <TABLENAME>
Description This token is replaced with the database table name that Campaign is truncating.
Type
The partitions > partition[n] > dataSources > [data_source_name] > type property specifies the database type of this data source. Valid Values Valid values for system tables are: SQLServer DB2 DB2ODBC ORACLE ORACLE8 ORACLE9
Valid values for customer tables also include: SYBASE INFORMIX7 INFORMIX8 INFORMIX9 TERADATA
357
Version 8.5.0
Default Value The default value depends on the database template used to create the data source configuration.
UseExceptForMerge
When Campaign performs exclusions in the Merge process or in the Segment process, by default it uses "NOT EXISTS" syntax, as:
SELECT IncludeTable.ID FROM IncludeTable WHERE NOT EXISTS (SELECT * FROM ExcludeTable WHERE IncludeTable.ID = ExcludeTable.ID)
If UseExceptForMerge is enabled (value set to YES) and we cannot use "NOT IN" (because UseNotInForMerge is disabled, or because the audience level is comprised of multiple fields and the data source is not Oracle), then the syntax will be altered as: Oracle
Others
UseMergeForTrack
Implements SQL MERGE syntax to improve the performance of the Track process. The UseMergeForTrack property can be set to TRUE for DB2, Oracle, SQL Server 2008, and Teradata 12. It can also be used with other databases that support the SQL MERGE statement. Valid Values TRUE | FALSE
358 IBM Unica Campaign - Administrator's Guide
UseNonANSIJoin
The UseNonANSIJoin property specifies whether this data source uses non-ANSI join syntax (for example, for Oracle versions earlier than 8, and Informix8). If the data source type is set to Informix8, the value of UseNonANSIJoin is ignored, and non-ANSI join syntax appropriate for Informix8 is always used. If the data source type is set to Oracle7 or Oracle8, and the value of UseNonANSIJoin is set to TRUE, the data source uses non-ANSI join syntax appropriate for Oracle. If the data source type is set to Sybase, and the value of UseNonANSIJoin is set to TRUE, the data source uses non-ANSI join syntax appropriate for Sybase.
UseNotInForMerge
When Campaign performs exclusions in the Merge process or in the Segment process, by default it uses "NOT EXISTS" syntax, as:
SELECT IncludeTable.ID FROM IncludeTable WHERE NOT EXISTS (SELECT * FROM ExcludeTable WHERE IncludeTable.ID = ExcludeTable.ID)
If UseNotInForMerge is enabled (value set to YES), and either (1) the audience level is comprised of a single ID field, or (2) the data source is Oracle, then the syntax will be altered as:
SELECT IncludeTable.ID FROM IncludeTable WHERE IncludeTable.ID NOT IN (SELECT ExcludeTable.ID FROM ExcludeTable)
Version 8.5.0
359
UseSQLToProfile
The UseSQLToProfile property allows you to configure Campaign to submit the SQL query GROUP BY to the database to compute profiles (using SELECT field, count(*) FROM table GROUP BY field ), rather than fetching records. A value of FALSE (the default) causes Campaign to profile a field by retrieving the field's value for all records in the table and to track the count of each distinct value. A value of TRUE causes Campaign to profile a field by issuing a query similar to the following:
which pushes the burden to the database. Valid Values TRUE | FALSE Default Value FALSE
N2180001
offerCodeDelimiter
The offerCodeDelimiter property is used internally to concatenate multiple code parts (for example, to output the OfferCode field in Campaign Generated Fields) and for incoming offer codes in the Campaign Response process, to split the offer code into multiple parts. The value must be only a single character. Note that in this version of Campaign, the NumberOfOfferCodesToUse parameter no longer exists. This value now comes from the offer template (every offer template can have a different number of offer codes).
360
Default Value -
allowVariableLengthCodes
The allowVariableLengthCodes property specifies whether variable length codes are allowed in Campaign. If the value is yes, and if the trailing part of the code format is x, the length of the code can vary. For example, if the code format is nnnnxxxx, then the code can be from 4 to 8 characters long. This applies to campaign, offer, version, tracking, and cell codes. If the value is no, variable length codes are not allowed. Valid Values yes | no Default Value no
displayOfferCodes
The displayOfferCodes property specifies whether to show offer codes beside their names in the Campaign GUI. If the value is yes, offer codes are displayed. If the value is no, offer codes are not displayed. Valid Values yes | no Default Value no
cellCodeFormat
The cellCodeFormat property is used by the campaign code generator to define the format of the cell code that is automatically created by the default cell code generator. For a list of valid values, see campCodeFormat. Default Value Annnnnnnnn
campCodeFormat
The campCodeFormat property is used by the campaign code generator to define the format of the campaign code that is automatically generated by the default campaign code generator when you create a campaign.
Version 8.5.0 361
Valid Values The possible values are as follows: A-Z or any symbol - treated as a constant a - random letters A-Z (upper case only) c - random letters A-Z or numbers 0-9 n - random digit 0-9 x - any single ASCII character from 0-9 or A-Z. You can edit the generated campaign code and replace the ASCII character that Campaign substituted for the x with any ASCII character, and Campaign will use that character instead.
cellCodeGenProgFile
The cellCodeGenProgFile property specifies specifies the name of the cell code generator, and if the generator is the default one supplied by Campaign, any supported options. Note that the properties that control the format of the code generated are set in the cellCodeFormat property. See campCodeGenProgFile for a list of supported options. If you write your own cell code generator, replace the default value with the absolute path of your custom program, including the file name and extension, and using forward slashes (/) for UNIX and backslashes (\) for Windows. Default Value uaccampcodegen (the code generator supplied by Campaign)
campCodeGenProgFile
The campCodeGenProgFile property specifies the name of the campaign code generator, and if the generator is the default one supplied by Campaign, any supported options. Note that the properties that control the format of the code generated are set in the campCodeFormat property. If you write your own campaign code generator, replace the default value with the absolute path of your custom program, including the file name and extension, and using forward slashes (/) for UNIX and backslashes (\) for Windows. The default campaign code generator can be called with the following options:
362
-y Year (four integers) -m Month (one or two integers, cannot exceed value of twelve) -d Day (one or two integers, cannot exceed value of 31) -n Campaign name (any string, cannot exceed 64 characters)
IBM Unica Campaign - Administrator's Guide
-o Campaign owner (any string, cannot exceed 64 characters) -u Campaign code (any integer). Allows you to specify the exact campaign ID rather than having the application generate one for you. -f Code format if overriding the default. Takes the values specified in campCodeFormat. -i Other integer. -s Other string.
stringEncoding
The partition[n] > server> encoding > stringEncoding property how Campaign reads in and writes out flat files. It should match the encoding used for all flat files. If not configured elsewhere, this is the default setting for flat file encoding. WIDEUTF-8 is not supported for this setting. By default, no value is specified, and outgoing text files are encoded as UTF-8, which is the default encoding for Campaign. It is a best practice to explicitly set this value to an encoding appropriate for your system, even if the value is UTF-8, the same as the implicit default. If you do not set the value of the StringEncoding property for data sources in the dataSources category, the value of this stringEncoding property is used as the default value. This can cause unnecessary confusion -- you should always explicitly set the StringEncoding property in the dataSources category. See the Campaign Administrator's Guide for a list of supported encodings. Default Value No default value defined.
forceDCTOneBytePerChar
The forceDCTOneBytePerChar property specifies whether Campaign should use the original field width for output files, rather than the potentially expanded width reserved to allow sufficient space for transcoding into UTF-8.
Version 8.5.0
363
A text value may have different lengths, depending on the encoding used to represent it. When the text value comes from a data source whose stringEncoding property is neither ASCII nor UTF-8, Campaign reserves three times the field width in order to ensure sufficient space for transcoding into UTF-8. For example, if the stringEncoding property is set to LATIN1, and the field in the database is defined as VARCHAR(25), Campaign will reserve 75 bytes to hold the transcoded UTF-8 value. Set the forceDCTOneBytePerChar property to TRUE if you want to use the original field width. Valid Values TRUE | FALSE Default Value FALSE
N21B0001
waitForGracefulDisconnect
The waitForGracefulDisconnect property specifies whether the Campaign server process continues to run until the user gracefully disconnects, or exits regardless of whether the user intended to disconnect. If the value is yes, the default, the server process continues to run until it can determine that the user wants it to exit. This option prevents changes from being lost, but can result in server processes accumulating. If the value is no, the server process shuts down and server processes are prevented from accumulating, but users can lose work if a network interruption occurs or if they do not follow the recommended sequence of actions to exit gracefully. Valid Values yes | no Default Value yes
urlRequestTimeout
The urlRequestTimeout property specifies the number of seconds the Campaign server process waits for a response from external servers. Currently, this applies to requests to IBM Unica Marketing servers and eMessage components that operate with Campaign.
364 IBM Unica Campaign - Administrator's Guide
If the Campaign server process does not receive a response within this period, a communication timeout error is reported. Default Value 60
delayExitTimeout
The delayExitTimeout property specifies the number of seconds an Campaign flowchart waits, after the user has disconnected and all runs have completed, before exiting. Setting this property to a non-0 value enables subsequent Campaign flowcharts to make use of existing instances rather than starting a new instance. Default Value 10
N21C0001
catalogFolderPermissions
The catalogFolderPermissions property specifies the permissions of directories created by Campaign through the Stored Table Catalogs > Create Folder window. Default Value 755 (owner has read/write/execute access, group and world have execute/read access)
templateFolderPermissions
The templateFolderPermissions property specifies the permissions of template directories created by Campaign through the Stored Templates > Create Folder window. Default Value 755 (owner has read/write/execute access, group and world have read/execute access)
366
allowDuplicateCellcodes
The allowDuplicateCellcodes property specifies whether the cell codes in the Campaign Snapshot process can have duplicate values. If the value is no, the Campaign server enforces unique cell codes. If the value is yes, the Campaign server does not enforce unique cell codes. Default Value yes
allowResponseNDaysAfterExpiration
The allowResponseNDaysAfterExpiration property specifies the maximum number of days after all offer's expiration dates that responses can tracked. These late responses can be included in performance reports. Default Value 90
agfProcessnameOutput
The agfProcessnameOutput property specifies the output behavior of the Campaign Generated Field (UCGF) in the List, Optimize, Response, and Snapshot processes. If the value is PREVIOUS, the USGF contains the process name associated with the incoming cell. If the value is CURRENT, the UCGF holds the process name of the process in which it is used. Valid Values PREVIOUS | CURRENT Default Value PREVIOUS
logToHistoryDefault
The logToHistoryDefault property specifies whether the Log to Contact History and Tracking Tables option in the Log tab of the Campaign contact processes defaults to enabled.
Version 8.5.0 367
If the value is yes, the option is enabled. If the value is no, the option is disabled in any newly created contact processes. Valid Values yes | no Default Value yes
defaultBehaviorWhenOutputToFile
Specifies the behavior for contact processes in Campaign when outputting to a file. This property applies only within the current partition. This default behavior (if set) is only applied for processes when they are newly added to flowcharts; once a process is added to a flowchart, the output behavior can be changed in the process configuration. Valid Values Append to Existing Data Create New File Replace All Records
defaultBehaviorWhenOutputToDB
Specifies the behavior for contact processes in Campaign when outputting to a database table. This property applies only within the current partition. This default behavior (if set) is only applied for processes when they are newly added to flowcharts; once a process is added to a flowchart, the output behavior can be changed in the process configuration. Valid Values Append to Existing Data Replace All Records
368
replaceEmbeddedNames
When the replaceEmbeddedNames property is set to TRUE, Campaign replaces user variable and UCGF names embedded in query text with actual values, although these names must be separated by a non-alphanumeric character, such as an underscore (for example, ABCUserVar.v1 will not be substituted, while ABC_UserVar.v1 will be substituted). Set this property to TRUE for backwards compatibility with Campaign 7.2 and earlier. When set to FALSE, Campaign replaces only distinct user variable and UCGF names with actual values (in both Unica and raw SQL expressions). Set this property to FALSE for backwards compatibility with Campaign 7.3 and higher. Valid Values TRUE | FALSE Default Value FALSE
N21F0001
checkpointFrequency
The checkpointFrequency property specifies (in minutes) the default setting for a new Campaign flowcharts checkpoint property, configurable for each flowchart through the client-side Advanced Settings window. The checkpoint feature provides the ability to capture a snapshot of a running flowchart for recovery purposes. Valid Values Any integer Default Value 0 (zero)
autosaveFrequency
The autosaveFrequency property specifies (in minutes) the default setting for a new Campaign flowcharts auto-save property, configurable for each flowchart through the client-side Advanced Settings window. The auto-save function performs a forced save of flowcharts during editing and configuration. Valid Values Any integer
Version 8.5.0
369
longNumericIdsAsText
The longNumericIdsAsText property specifies whether the Campaign macro language will treat numeric IDs longer than 15 digits as text. Set the value to yes to specify that numeric IDs longer than 15 digits will be treated as text. Set the value to no to specify that numeric IDs longer than 15 digits are treated as numeric values (and thus might lose precision or uniqueness if truncated or rounded). This setting is ignored if the partitions > partition[n] > dataSources > [data_source_name] > ForceNumeric property is set to TRUE for fields coming from this data source. Valid Values yes | no Default Value no
stringConcatWithNullIsNull
The stringConcatWithNullIsNull property controls the behavior of the Campaign macro STRING_CONCAT. When the value is yes, STRING_CONCAT returns NULL if any of its inputs is NULL. When the value is no, STRING_CONCAT returns the concatenation of all of its non-NULL properties; in this case, STRING_CONCAT returns NULL only if all of its inputs are NULL. Valid Values yes | no Default Value yes
370
performCaseInsensitiveComparisonAs
The performCaseInsensitiveComparisonAs property specifies how Campaign compares data values when the compareCaseSensitive property is set to no (that is, during case-insensitive comparisons). This property is ignored if the value of compareCaseSensitive is yes. When the value is UPPER, Campaign converts all data to upper case before comparing. When the value is LOWER, Campaign converts all data to lower case before comparing. Valid Values UPPER | LOWER Default Value LOWER
upperAllowsDate
The upperAllowsDate property specifies whether the UPPER database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server. Set the value to yes if the database is SQL Server or Oracle. The UPPER function in these databases allows a DATE/DATETIME parameter. Set the value to no if the database is DB2, Teradata, Sybase, or Informix. The UPPER function in these databases does not allow a DATE/DATETIME parameter. Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes. Valid Values yes | no Default Value yes
compareCaseSensitive
The compareCaseSensitive property specifies whether the Campaign data comparisons are sensitive to alphabetic case (UPPER vs. lower). When the value is no, Campaign ignores case differences when comparing data values and sorts textual data in a binary, case-insensitive manner. This setting is strongly recommended when English data is used. When the value is yes, Campaign distinguishes data values based on case differences, performing a true binary-value comparison of each character. This setting is strongly recommended when non-English data is used.
Version 8.5.0
371
lowerAllowsDate
The lowerAllowsDate property specifies whether the LOWER database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server. Set the value to yes if the database is SQL Server or Oracle. The LOWER function in these databases allows a DATE/DATETIME parameter. Set the value to no if the database is DB2, Teradata, Sybase, or Informix. The LOWER function in these databases does not allow a DATE/DATETIME parameter. Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes. Typically, only one database type is in use at a customer site, but there are some installations in which multiple database types are in use. Valid Values yes | no Default Value yes
substrAllowsDate
The substrAllowsDate property specifies whether the SUBSTR/SUBSTRING database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server. Set the value to yes if the database is Oracle or Teradata. The SUBSTR/SUBSTRING function in these databases allows a DATE/DATETIME parameter. Set the value to no if the database is SQL Server, DB2, Sybase, or Informix. The SUBSTR/SUBSTRING function in SQL Server, DB2, and Sybase does not allow a DATE/DATETIME parameter. Informix SUBSTR does accept a DATE parameter, but the DATE is first converted to text, and the conversion changes the format. So SUBSTR would return different results in the database compared with the Campaign server, so the best practice is to set substrAllowsDate to no when the database is Informix. Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes.
372
ltrimAllowsDate
The ltrimAllowsDate property specifies whether the LTRIM database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server. Set the value to yes if the database is SQL Server, Oracle, or Teradata. The LTRIM function in these databases allows a DATE/DATETIME parameter. Set the value to no if the database is DB2, Sybase, or Informix. The LTRIM function in these databases does not allow a DATE/DATETIME parameter. Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes. Typically, only one database type is in use at a customer site, but there are some installations in which multiple database types are in use. Valid Values yes | no Default Value yes
rtrimAllowsDate
The rtrimAllowsDate property specifies whether the RTRIM database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server. Set the value to yes if the database is SQL Server, Oracle, or Teradata. The RTRIM function in these databases allows a DATE/DATETIME parameter. Set the value to no if the database is DB2, Sybase, or Informix. The RTRIM function in these databases does not allow a DATE/DATETIME parameter. Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes. Valid Values yes | no Default Value yes
Version 8.5.0 373
likeAllowsDate
The likeAllowsDate property specifies whether the LIKE database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server. Set the value to yes if the database is SQL Server or Oracle. The LIKE function in these databases allows a DATE/DATETIME parameter. Set the value to no if the database is DB2, Teradata, Sybase, or Informix. The LIKE function in these databases does not allow a DATE/DATETIME parameter. This setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes. Valid Values yes | no Default Value yes
fileAllSpacesIsNull
The fileAllSpacesIsNull property controls how Campaign interprets an empty field in a mapped flat file by specifying whether an all-spaces value in a flat file should be considered to be a NULL value. When the value is yes, an all-spaces value is considered to be a NULL value. Campaign matches queries such as <field> is null, but fails queries such as <field> = "". When the value is no, an all-spaces value is treated as a non-NULL empty string. Campaign matches queries such as <field> = "", but fails <field> is null. Valid Values yes | no Default Value yes
N2210001
maxVirtualMemory
The maxVirtualMemory property specifies a default setting for a new Campaign flowcharts Affinium Virtual Memory Usage property, configurable for each flowchart through the client-side Advanced Settings window. The units are in megabytes. Default Value 128
useInDbOptimization
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. Valid Values yes | no Default Value no
maxReuseThreads
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. Default Value 0 (zero), which disables the cache
tempTableDataSourcesForSegments
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. Default Value No default value defined.
Version 8.5.0
375
doNotCreateServerBinFile
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. Valid Values TRUE | FALSE Default Value FALSE
N2220001
enableWindowsEventLogging
The enableWindowsEventLogging property enables or disables Campaign server logging to the Windows event log. If the value is yes, logging to the Windows event log is enabled. If the value is no, logging to the Windows event log is disabled. If disabled, the windowsEventLoggingLevel and windowsEventLoggingCategory settings are ignored. Valid Values yes | no Default Value no
logFileBufferSize
The logFileBufferSize property is used when the value of the keepFlowchartLogOpen property is yes. It sets an upper bound on the number of log messages after which the messages will be written to file. If the value is 1, every log message is written immediately to file, effectively disabling buffering but causing somewhat worse performance. This property is ignored if the value of keepFlowchartLogOpen is set to no.
376
Default Value 5
keepFlowchartLogOpen
The keepFlowchartLogOpen property specifies whether Campaign opens and closes the flowchart log file each time a line is written to the log file. If the value is no, Campaign opens and closes the flowchart log file. If the value is yes, Campaign opens the flowchart log file only once, and closes the flowchart log file only when the flowchart's server process exits. A value of yes may improve performance of real-time flowcharts. A side effect of using the yes setting is that recently-logged messages may not be immediately visible in the log file, as Campaign flushes the log messages to file only when its internal buffer becomes full or when the number of logged messages equals the value of the logFileBufferSize property. Valid Values yes | no Default Value no
logProcessId
The logProcessId property controls whether the process ID (pid) of the Campaign Server process is logged in the log file. If the value is yes, the process ID is logged. If the value is no, the process ID is not logged. Valid Values yes | no Default Value yes
logMaxBackupIndex
The logMaxBackupIndex property specifies the number of backup Campaign server log files that are kept before the oldest is erased. If the value is 0 (zero), no backup files are created, and the log file is truncated when it reaches the size specified by the logFileMaxSize property. For a value of n, where n is greater than zero, the files {File.1, ..., File.n-1} are renamed to {File.2, ..., File.n}. Also, File is renamed File.1 and closed. A new File is created to receive further log output.
Version 8.5.0
377
loggingCategories
The loggingCategories property specifies the category of messages written to the Campaign server log file. This works in conjunction with loggingLevels, which determines which messages are logged based on severity (for all selected categories). You can specify multiple categories in a comma-separated list. The special category all provides a shorthand for specifying all logging categories. Valid Values Supported categories are: ALL BAD_ORDER CELL_ACCESS CONFIG DATA_ERRORS DBLOAD FILE_ACCESS GENERAL COMMANDS MEMORY PROCRUN QUERY SORT SYSQUERY TABLE_ACCESS TABLE_MAPPING TABLE_IO WEBPROC
loggingLevels
The loggingLevels property controls the amount of detail written to the Campaign server log file, based on severity.
378 IBM Unica Campaign - Administrator's Guide
LOW represents the least detail (the most severe errors only), and ALL includes trace messages and is intended primarily for diagnostic purposes. You can adjust these settings from within a flowchart through the Tools >Logging Options menu. You may want to set the loggingLevels property to ALL during configuration and testing, to maximize the logging output from Campaign for diagnostic purposes. This setting generates a large amount of data and therefore may not be advisable for production operation. Default Value MEDIUM
windowsEventLoggingCategories
The windowsEventLoggingCategories property specifies the category of messages written to the Campaign server windows event log. This works in conjunction with windowsEventLoggingLevels, which determines which messages are logged based on severity (for all selected categories). You can specify multiple categories in a comma-separated list. The special category all provides a shorthand for specifying all logging categories. Valid Values ALL BAD_ORDER CELL_ACCESS CONFIG DATA_ERRORS DBLOAD FILE_ACCESS GENERAL COMMANDS MEMORY PROCRUN QUERY
Version 8.5.0
379
logFileMaxSize
The logFileMaxSize property specifies the maximum size, in bytes, that the Campaign server log file is allowed to reach before being rolled over to backup files. Default Value 10485760 (10 MB)
windowsEventLoggingLevels
The windowsEventLoggingLevels property controls the amount of detail written to the Campaign server windows event log based on severity. Valid Values LOW MEDIUM HIGH ALL
LOW represents the least detail (the most severe errors only), and ALL includes trace messages and is intended primarily for diagnostic purposes. Default Value MEDIUM
enableLogging
The enableLogging property specifies whether Campaign server logging is turned on at session startup. If the value is yes, logging is turned on. If the value is no, logging is turned off. Valid Values yes | no
380 IBM Unica Campaign - Administrator's Guide
maxDataErrorsAllowed
The maxDataErrorsAllowed property specifies the maximum number of data conversion errors allowed in an Campaign Snapshot export. Default Value 0 (zero), which allows no errors
saveRunResults
The saveRunResults property specifies what files are saved when you save an Campaign flowchart. If the value is yes, the underscore files are saved and, if the value of useInDbOptimization is yes, database temp tables persist. If the value is no, only the .ses file is saved and you cannot view intermediate results if you reload the flowchart. Valid Values yes | no Default Value yes
testRunDefaultSize
The testRunDefaultSize property specifies the default maximum number of IDs for each top-level process in an Campaign test run. A value of 0 (zero) removes the limitation on the number of IDs. Default Value 0 (zero)
N2240001
Version 8.5.0
381
profileMaxTextCategories
The profileMaxTextCategories and profileMaxNumberCategories properties specify the maximum number of categories created in Campaign during profiling for text and numeric values, respectively. These values are different from the setting for the number of bins displayed to the user, which can be modified through the user interface. Default Value 1048576
profileMaxNumberCategories
The profileMaxNumberCategories and profileMaxTextCategories properties specify the maximum number of categories created in Campaign during profiling for numeric and text values, respectively. These values are different from the setting for the number of bins displayed to the user, which can be modified through the user interface. Default Value 1024
N2250002
internalIdLowerLimit
The internalIdUpperLimit and internalIdLowerLimit properties constrain the Campaign internal IDs to be within the specified range. Note that the values are inclusive: that is, Campaign may use both the lower and upper limit. Default Value 0 (zero)
internalIdUpperLimit
The internalIdUpperLimit and internalIdLowerLimit properties constrain the Campaign internal IDs to be within the specified range. Note that the values are inclusive: that is, Campaign may use both the lower and upper limit.
382 IBM Unica Campaign - Administrator's Guide
eMessageInstalled
Indicates that eMessage is installed. When you select yes, eMessage features are available in the Campaign interface. The IBM installer sets this property to yes for the default partition in your eMessage installation. For additional partitions where you have installed eMessage, you must configure this property manually. Valid Values yes | no Default Value no
interactInstalled
After installing the Interact design environment, this configuration property should be set to yes to enable the Interact design environment in Campaign. If you do not have Interact installed, set to no. Setting this property to no does not remove Interact menus and options from the user interface. To remove menus and options, you must manually unregister Interact using the configTool utility. Valid Values yes | no Default Value no Availability This property is applicable only if you have installed Interact.
MO_UC_integration
Enables integration with Marketing Operations. Valid Values yes | no Default Value no
Version 8.5.0
383
Legacy_campaigns
When the MO_UC_integration property is set to Yes, the Legacy_campaigns property enables access to campaigns created before enabling integration, including campaigns created in Campaign 7.x and linked to Plan 7.x projects. Valid Values yes | no Default Value no
N2260001
defaultOutputDirectory
The defaultOutputDirectory property specifies the path used to initialize the Campaign File Selection dialog. The defaultOutputDirectory property is used when an output data file is mapped into Campaign. If no value is specified, the path is read from the environment variable UNICA_ACDFDIR. Default Value No default value defined.
defaultInputDirectory
The defaultInputDirectory property specifies the path used to initialize the Campaign File Selection dialog. The defaultInputDirectory property is used when an input data file is mapped into Campaign. If no value is specified, the path is read from the environment variable UNICA_ACDFDIR. Default Value No default value defined.
N2270001
384
offerCodeGeneratorClass
The offerCodeGeneratorClass property specifies the name of the class Campaign uses as its offer code generator. The class must be fully qualified with its package name. Default Value com.unica.campaign.core.codegenerator.samples.ExecutableCodeGener ator
offerCodeGeneratorConfigString
The offerCodeGeneratorConfigString property specifies a string that is passed into the offer code generator plug-in when it is loaded by Campaign. By default, the ExecutableCodeGenerator (shipped with Campaign) uses this property to indicate the path (relative to Campaign application home directory) to the executable to run. Default Value ./bin
defaultGenerator
The defaultGenerator property specifies the generator for the cell codes that appear in contact-style process boxes and are used to assign cells to Target Control Spreadsheet cells. The Target Control Spreadsheet manages cell and offer mappings for campaigns and flowcharts. Default Value uacoffercodegen.exe
offerCodeGeneratorClasspath
The offerCodeGeneratorClasspath property specifies the path to the class Campaign uses as its offer code generator. It can be either a full path or a relative path. If the path ends in a slash (forward slash / for UNIX or backslash \ for Windows), Campaign assumes it to be a path to a directory that contains the Java plug-in class that should be used. If the path does not end in a slash, Campaign assumes it is the name of a jar file that contains the Java class. If the path is relative, Campaign assumes it is relative to the Campaign application home directory. Default Value codeGenerator.jar(packaged in the Campaign.war file)
N2280001
Version 8.5.0
385
cacheCleanupInterval
The cacheCleanupInterval property specifies the interval, in seconds, between automatic cleanups of the flowchart status cache. This property is not available in versions of Campaign earlier than 7.0. Default Value 600 (10 minutes)
cacheRunCompleteTime
The cacheRunCompleteTime property specifies the amount of time, in minutes, that completed runs are cached and display on the Monitoring page. This property is not available in versions of Campaign earlier than 7.0. Default Value 4320
monitorEnabled
The monitorEnabled property specifies whether the monitor is turned on. This property is not available in versions of Campaign earlier than 7.0. Default Value yes
serverURL
The Campaign > monitoring > serverURL property specifies the URL of the Operational Monitoring server. This is a mandatory setting; modify the value if the Operational Monitoring server URL is not the default. If Campaign is configured to use Secure Sockets Layer (SSL) communications, the Operational Monitoring URL must begin with https, and the port must be set to 443. For example: https://localhost:443/Campaign/OperationMonitor Default Value http://localhost:7001/Campaign/OperationMonitor
386
monitorEnabledForInteract
If set to yes, enables Campaign JMX connector server for Interact. Campaign has no JMX security. If set to no, you cannot connect to the Campaign JMX connector server. This JMX monitoring is for the Interact contact and response history module only. Valid Values True | False Default Value False Availability This property is applicable only if you have installed Interact.
protocol
Listening protocol for the Campaign JMX connector server, if monitorEnabledForInteract is set to yes. This JMX monitoring is for the Interact contact and response history module only. Valid Values JMXMP | RMI Default Value JMXMP Availability This property is applicable only if you have installed Interact.
port
Listening port for the Campaign JMX connector server, if monitorEnabledForInteract is set to yes. This JMX monitoring is for the Interact contact and response history module only. Valid Values An integer between 1025 and 65535. Default Value 2004 Availability This property is applicable only if you have installed Interact.
Version 8.5.0 387
startTime
The startTime property specifies the time of day when offer/product associations are updated for the first time. The first update occurs on the day after the Campaign server is started, and subsequent updates occur at intervals specified in the interval parameter. The format is HH:mm:ss, using a 24-hour clock. Note that when Campaign first starts up, the startTimeproperty is used according to the following rules: If the time of day specified by startTime is in the future, the first offer/product associations update will occur at startTime of the current day. If startTime is in the past for the current day, the first update will occur at startTime tomorrow, or at interval minutes from the current time, whichever is earlier.
interval
The interval property specifies the time, in minutes, between updates of offer/product associations. The update occurs for the first time at the time specified in the startTime parameter, on the day after the Campaign server is started. Default Value 3600 (60 hours)
N22A0001
Campaign >unicaACListener
Properties in this category specify logging levels, certain access privileges, language encodings, number of operating system threads, and the protocol, host, and port of the Campaign listener. These properties need to be set only once per instance of Campaign; they do not need to be set for every partition.
enableWindowsImpersonation
The enableWindowsImpersonation property specifies whether Windows Impersonation is enabled in Campaign Windows. For more details about Windows Impersonation in Campaign, see the Campaign Administrators Guide. Set the value to TRUE to use Windows Impersonation.
388 IBM Unica Campaign - Administrator's Guide
Set the value to FALSE if Windows Impersonation is not used. Valid Values TRUE | FALSE Default Value FALSE
enableWindowsEventLogging
The Campaign > unicaACListener > enableWindowsEventLogging property controls logging to the Windows event log. Set this property to TRUE to log to the Windows event log. Valid Values TRUE | FALSE Default Value FALSE
serverHost
The serverHost property specifies the name or IP address of the machine where the Campaign listener is installed. If the Campaign listener is not installed on the same machine where IBM Unica Marketing is installed, change the value to the machine name or IP address of the machine where the Campaign listener is installed. Default Value localhost
logMaxBackupIndex
The logMaxBackupIndex property specifies how many backup files can exist before the oldest one is deleted. If you set this property to 0 (zero), Campaign does not create any backup files and the log file stops logging when it reaches the size you specified in the logMaxFileSize property. If you specify a number (N) for this property, when the log file (File) reaches the size you specified in the logMaxFileSize property, Campaign renames the existing backup files (File.1 ... File.N-1) to File.2 ... File.N , renames the current log file File.1, closes it, and and starts a new log file named File. Default Value 1 (creates one backup file)
Version 8.5.0
389
logStringEncoding
The logStringEncoding property controls the encoding used for all log files. This value should match the encoding used on the operating system. For multi-locale environments, UTF-8 is the preferred setting. If you change this value, you should empty or remove all affected log files to prevent writing multiple encodings into a single file. WIDEUTF-8 is not supported for this setting. Valid Values See the Campaign Administrator's Guide for a list of supported encodings. Default Value native
systemStringEncoding
The systemStringEncoding property specifies the encoding(s) used to interpret values coming into Campaign from the operating system (file system paths and filenames, for example), as well as the encoding in which Campaign presents values back to the operating system. This value should be generally be set to native. For multi-locale environments, UTF-8 is the preferred setting. The value can include more than one encoding, separated by commas: for example, UTF-8,ISO-8859,CP950 WIDEUTF-8 is not supported for this setting. Valid Values See the Campaign Administrator's Guide for a list of supported encodings. Default Value native
loggingLevels
The Campaign > unicaACListener > loggingLevels property controls the amount of detail written to the log file. Valid Values LOW MEDIUM HIGH
390
maxReuseThreads
The Campaign > unicaACListener > maxReuseThreads property sets the number of operating system threads cached by the Campaign listener process (unica_aclsnr) for reuse. 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. Default Value 0 (zero), which disables the cache
logMaxFileSize
The logMaxFileSize property specifies the maximum size, in bytes, that the log file can reach before rolling into the backup file. Default Value 10485760 (10 MB)
windowsEventLoggingLevels
The windowsEventLoggingLevels property controls the amount of detail written to the Windows event log file based on severity. Valid Values LOW MEDIUM HIGH ALL
The ALL level includes trace messages intended for diagnostic purposes. Default Value MEDIUM
serverPort
The serverPort property specifies the port where the Campaign listener is installed. Default Value 4664
Version 8.5.0
391
useSSL
The useSSL property specifies whether to use Secure Sockets Layer for communications between the Campaign listener and the Campaign web application. Valid Values yes | no Default Value no
keepalive
Use the keepalive property to specify, in seconds, the frequency with which the Campaign web application server sends keep alive messages on otherwise-inactive socket connections to the Campaign listener. Using the keepalive configuration parameter enables socket connections to remain open through extended periods of application inactivity in environments configured to close inactive connections between the web application and the listener (for example, a firewall). When there is activity on a socket, the keep alive period is automatically reset. At the DEBUG logging level in the web application server, the campaignweb.log will show evidence of the keep alive messages as they are sent to the listener. Valid Values positive integers Default Value 0, which disables the keepalive feature
N22B0001
fullContextPath
The fullContextPath property is used internally, and specifying a value is optional. It specifies the URL that the ActiveX control uses to communicate to the application server Listener proxy. This property is undefined by default, which causes the system to determine the URL dynamically. Default Value No default value defined.
N22C0001
392
log4jConfig
The log4jConfig property specifies the location of the Campaign log properties file, campaign_log4j.properties. Specify the path relative to the Campaignhome directory, including the file name. Use forward slashes (/) for UNIX and backslashes (\) for Windows. Default Value ./conf/campaign_log4j.properties
Version 8.5.0
393
N10F2D
About special characters Special characters not supported Objects with no naming restrictions Objects with specific naming restrictions
394
Description Percent Asterisk Question mark Pipe (vertical bar) Colon Comma Less than symbol Greater than symbol Ampersand Backward slash Forward slash Double quotation mark
audience levels (audience level field names have naming restrictions) custom attribute display names (custom attribute internal names have naming restrictions) offer templates
Version 8.5.0
For these objects, names must: contain only alphabetic or numeric characters, or the underscore (_) character start with an alphabetic character Derived field names have additional restrictions. For details, see Naming restrictions for derived fields.
396
N10F49
N3C0002
DB2
bigint char date decimal double float int numeric real smallint timestamp varchar
Netezza
bigint byteint char(n) [1] date
Version 8.5.0 397
float(p) int nchar(n) [2] numeric(p, s) nvarchar(n) [2] smallint timestamp varchar(n) [1] 1. Not supported when used in the same table with nchar or nvarchar. 2. Not supported when used in the same table with char or varchar.
Oracle
DATE FLOAT (p) NUMBER [ (p , s) ] [1] TIMESTAMP VARCHAR2(size BYTE) 1. Precision is required when using NUMBER unless you have set the data source property Campaign > partitions > partitionN > dataSources > [dataSourceName] > UseSQLToRetrieveSchema to TRUE. If you do not specify a precision and do not set that data source property, Campaign assumes it can store the values in a data type that preserves 15 digits of precision. This can be problematic because, if the field holds values whose precision exceeds 15 digits, precision will be lost when the value is brought into Campaign.
SQL Server
bigint bit char(n) [1] datetime decimal float int nchar [2] numeric nvarchar [2]
398 IBM Unica Campaign - Administrator's Guide
real smallint text tinyint varchar(n) [1] 1. Not supported when used in the same table with nchar or nvarchar. 2. Not supported when used in the same table with char or varchar.
Teradata
bigint byteint char date decimal float int numeric smallint timestamp varchar
Version 8.5.0
399
N10F4F
Introduction
This section provides information on character encodings and language-sensitive database considerations, and lists the encodings supported by Campaign and PredictiveInsight.
N1C80001
This section lists the encodings that are supported by Campaign. The values in these lists are valid values for setting the Campaign internationalization parameters listed in . Note the following: Each bullet within an encoding group is a space-separated list of different names for the same encoding. Each name in a bullet with multiple names is an alias for the other encodings in the group. You can set the Campaign configuration parameters to any of the values in a group, depending on how your system uses the encodings. When setting values for the Campaign StringEncoding configuration parameters, the pseudo-encoding WIDEUTF-8 is the recommended value in most cases. However, you can use one of the encodings included in the following lists. Additionally, if the database is DB2 or SQL Server, you should use a code page rather than one of the encodings in this list. For details, see the context help or the Marketing Platform Administrator's Guide.
IBM Unica Campaign - Administrator's Guide
400
Campaign uses two character encodings that are treated slightly differently than other encodings: ASCII and UTF-8. Both are case-sensitive. These encodings are accepted on all platforms including AIX. They have slightly different behaviors in Campaign for column widths during table mapping, and for transcoding operations.
N2320001
Western Europe
N2330001
CP819 IBM819 ISO-8859-1 ISO-IR-100 ISO8859-1 ISO_8859-1 ISO_88591:1987 L1 LATIN1 CSISOLATIN1 CP1252 MS-ANSI WINDOWS-1252 850 CP850 IBM850 CSPC850MULTILINGUAL MAC MACINTOSH MACROMAN CSMACINTOSH NEXTSTEP HP-ROMAN8 R8 ROMAN8 CSHPROMAN8
Unicode encodings
ISO-10646-UCS-2 UCS-2 CSUNICODE UCS-2BE UNICODE-1-1 UNICODEBIG CSUNICODE11 UCS-2LE UNICODELITTLE ISO-10646-UCS-4 UCS-4 CSUCS4 UTF-8 UCS-4BE UCS-4LE UTF-16 UTF-16BE UTF-16LE UTF-32 UTF-32BE UTF-32LE UNICODE-1-1-UTF-7 UTF-7 CSUNICODE11UTF7 UCS-2-INTERNAL UCS-2-SWAPPED UCS-4-INTERNAL UCS-4-SWAPPED JAVA
401
Version 8.5.0
N2340001
C99
Arabic
N2350001
ARABIC ASMO-708 ECMA-114 ISO-8859-6 ISO-IR-127 ISO8859-6 ISO_8859-6 ISO_8859-6:1987 CSISOLATINARABIC CP1256 MS-ARAB WINDOWS-1256 MACARABIC CP864 IBM864 CSIBM864
Armenian
N2360001
ARMSCII-8
Baltic Rim
N2370001
CP1257 WINBALTRIM WINDOWS-1257 CP775 IBM775 CSPC775BALTIC ISO-8859-13 ISO-IR-179 ISO8859-13 ISO_8859-13 L7 LATIN7
Celtic
N2380001
Central Europe
N2390001
ISO-8859-2 ISO-IR-101 ISO8859-2 ISO_8859-2 ISO_8859-2:1987 L2 LATIN2 CSISOLATIN2CP1250 MS-EE WINDOWS-1250 MACCENTRALEUROPE 852 CP852 IBM852 CSPCP852 MACCROATIAN
402
Chinese (Simplified)
N23B0001
CN GB_1988-80 ISO-IR-57 ISO646-CN CSISO57GB1988 CHINESE GB_2312-80 ISO-IR-58 CSISO58GB231280 CN-GB-ISOIR165 ISO-IR-165 CN-GB EUC-CN EUCCN GB2312 CSGB2312 CP936 GBK GB18030 HZ HZ-GB-2312
Chinese (Traditional)
N23C0001
EUC-TW EUCTW CSEUCTWB IG-5 BIG-FIVE BIG5 BIGFIVE CN-BIG5 CSBIG5 CP950 BIG5-HKSCS BIG5HKSCS
Cyrillic
N23D0001
CYRILLIC ISO-8859-5 ISO-IR-144 ISO8859-5 ISO_8859-5 ISO_88595:1988 CSISOLATINCYRILLIC CP1251 MS-CYRL WINDOWS-1251 MACCYRILLIC KOI8-R CSKOI8R KOI8-U KOI8-RU KOI8-T 866 CP866 IBM866 CSIBM866 855 CP855 IBM855 CSIBM855 CP1125 ("PC, Cyrillic, Ukrainian") MACUKRAINE
English
ANSI_X3.4-1968 ANSI_X3.4-1986 ASCII CP367 IBM367 ISO-IR-6 ISO646US ISO_646.IRV:1991 US US-ASCII CSASCII 437 CP437 IBM437 CSPC8CODEPAGE437
403
Version 8.5.0
Georgian
N23F0001
GEORGIAN-ACADEMY GEORGIAN-PS
Greek
N2400001
CP1253 MS-GREEK WINDOWS-1253 ECMA-118 ELOT_928 GREEK GREEK8 ISO-8859-7 ISO-IR-126 ISO8859-7 ISO_8859-7 ISO_8859-7:1987 CSISOLATINGREEK MACGREEK CP737869 CP-GR CP 869 IBM869 CSIBM869
Hebrew
N2410001
HEBREW ISO-8859-8 ISO-IR-138 ISO8859-8 ISO_8859-8 ISO_8859-8:1988 CSISOLATINHEBREW CP1255 MS-HEBR WINDOWS-1255 862 CP862 IBM862 CSPC862LATINHEBREW MACHEBREW
Icelandic
N2420001
Japanese
404
JISX0201-1976 JIS_X0201 X0201 CSHALFWIDTHKATAKANA ISO-IR-87 JIS0208 JIS_C6226-1983 JIS_X0208 JIS_X0208-1983 JIS_X0208-1990 X0208 CSISO87JISX0208 ISO-IR-159 JIS_X0212 JIS_X0212-1990 JIS_X0212.1990-0 X0212 CSISO159JISX02121990 EUC-JP EUCJP EXTENDED_UNIX_CODE_PACKED_FORMAT_FOR_JAPANESE CSEUCPKDFMTJAPANESE MS_KANJI SHIFT-JIS SHIFT_JIS SJIS CSSHIFTJI ISO-IR-14 ISO646-JP JIS_C6220-1969-RO JP CSISO14JISC6220RO
IBM Unica Campaign - Administrator's Guide
N2430001
Korean
N2440001
EUC-KR EUCKR CSEUCKR CP949 UHC ISO-IR-149 KOREAN KSC_5601 KS_C_5601-1987 KS_C_5601-1989 CSKSC56011987 CP1361 JOHAB ISO-2022-KR CSISO2022KR
Lao
Note that Lao uses the same alphabet as Thai.
N2450001
Northern Europe
N2460001
ISO-8859-4 ISO-IR-110 ISO8859-4 ISO_8859-4 ISO_8859-4:1988 L4 LATIN4 CSISOLATIN4 ISO-8859-10 ISO-IR-157 ISO8859-10 ISO_8859-10 ISO_8859-10:1992 L6 LATIN6 CSISOLATIN6
Romanian
N2470001
MACROMANIA
Southern Europe
N2480001
Version 8.5.0
405
Thai
N2490001
MACTHAI ISO-IR-166 TIS-620 TIS620 TIS620-0 TIS620.2529-1 TIS620.2533-0 TIS620.2533-1 CP874 WINDOWS-874
Turkish
N24A0001
CP1254 MS-TURK WINDOWS-1254 MACTURKISH 857 CP857 IBM857 CSIBM857 ISO-8859-9 ISO-IR-148 ISO8859-9 ISO_8859-9 ISO_8859-9:1989 L5 LATIN5 CSISOLATIN5
Vietnamese
N24B0001
Miscellaneous
N1CA0001
ISO-8859-15 ISO-IR-203 ISO8859-15 ISO_8859-15 ISO_8859-15:1998 ISO-8859-16 ISO-IR-226 ISO8859-16 ISO_8859-16 ISO_8859-16:2000 CP858 (IBM: " Multilingual with euro " ) 860 (IBM: " Portugal - Personal Computer " ) CP860 IBM860 CSIBM860 863 (IBM: " Canadian French - Personal Computer " ) CP863 IBM863 CSIBM863 865 (IBM: " Nordic - Personal Computer " )CP865 IBM865 CSIBM865
406
MMDDYYYY
DELIM_M_D For DateTimeFormat, use DT_DELIM_M_D DELIM_M_D_Y For DateTimeFormat, use DT_DELIM_M_D_Y DELIM_Y_M For DateTimeFormat, use DT_DELIM_Y_M DELIM_Y_M_D For DateTimeFormat, use DT_DELIM_Y_M_D YYMMM
70MAR
Version 8.5.0
407
Format YYMMMDD
Description 2-digit year, 3-letter month, and 2-digit day 2-digit year 2-digit year and 2-digit month
Example(s) 70MAR31
YY YYMM YYMMDD
70 7003
2-digit year, 2-digit month, and 2- 700331 digit day 4-digit year and 3-letter month 4-digit year, 3-letter month, and 2-digit day 4-digit year 4-digit year and 2-digit month 1970MAR 1970MAR31
YYYYMMM YYYYMMMDD
1970 197003
4-digit year, 2-digit month, and 2- 19700331 digit day Any delimited month followed by year 3-70, 3/70, Mar 70, March 1970
DELIM_M_Y For DateTimeFormat, use DT_DELIM_M_Y DELIM_D_M For DateTimeFormat, use DT_DELIM_D_M DELIM_D_M_Y For DateTimeFormat, use DT_DELIM_D_M_Y DD DDMMM DDMMMYY
31-MAR-70, 31/3/1970, 31 03 70
31 31MAR
408
Format DDMMMYYYY
Description
Example(s)
2-digit day, 3-letter month, and 4- 31MAR1970 digit year 2-digit day and 2-digit month 2-digit day, 2-digit month, and 2digit year 2-digit day, 2-digit month, and 4digit year 2-digit month and 2-digit year 2-digit month and 4-digit year 3-letter month 3-letter month and 2-digit day 3103 310370
DDMM DDMMYY
DDMMYYYY
31031970
3-letter month, 2-digit day, and 2- MAR3170 digit year 3-letter month, 2-digit day, and 4- MAR311970 digit year 3-letter month and 2-digit year 3-letter month and 4-digit year Month of the year MAR70 MAR1970 January, February, March, and so on or Jan, Feb, Mar, and so on Sunday, Monday, Tuesday, and so on (Sunday = 0) Sun, Mon, Tues, and so on (Sun = 0)
MMMDDYYYY
WEEKDAY
WKD
N24D0001
Version 8.5.0
409
410
Characters that are part of the format and are not preceded by a percent sign (%) are copied unchanged to the output string. The formatted string must fit in 16 bytes or less.Use the # character to eliminate any leading 0. For example, %d produces 2digit numbers in the range (01 - 31), while %#d produces 1- or 2-digit numbers as appropriate (1 - 31). Similarly, %m gives (01 - 12) while %#m gives (1 - 12).
Version 8.5.0
411
N1102A
E ErrorCodes
N24E0001
412
Code 309 310 311 312 314 315 316 317 318 319 320 321 322 323 324 325 328 329 330 331 332 Version 8.5.0
Error Description Error loading saved expression from file (unknown function). Error loading saved expression from file (rand obj). Error loading saved object from file (invalid ID). Error loading saved expression from file (stack). Error saving object to file (invalid ID). Error saving expression to file (large mem). Consecutive operators in expression. Operator syntax error. Parenthesis missing. Parentheses mismatched. Unknown expression. No name given. No expression following an equal sign. Ambiguous field name. Can't sort more than 2^16 points. Error accessing virtual memory (stat=0). Matrix multiply dimension mismatch. Matrix multiply dimension too big. Singular matrix error. Invalid number of arguments. Argument(s) must be scalar number(s). 413
E - Error Codes
Code 333 334 335 336 338 339 341 342 343 345 346 348 349 350 353 354 356 357 358 359 360 414
Error Description Argument must be greater than 0. Values of argument(s) are invalid. Values of argument(s) must be between -1 and 1. Dimensionality of argument(s) is invalid for the function. Length of arguments must be equal. Dimensionality of arguments must be equal. Standard deviation or other statistical calculation is invalid. Only vector is allowed for the 1st argument. Supplied argument must be integer. Expression is mathematically undefined. Unable to get training pattern. Supplied keyword is not appropriate for this function. Floating pointer value overflow error. Trying to take square root of negative number. Function's total returned string size is too large. String type not allowed in one or more arguments. Row/column index is not valid. Mixing numbers and text columns not allowed. String quote mismatch. Expression is too complex. String length too long. IBM Unica Campaign - Administrator's Guide
Code 361 362 363 364 365 367 368 369 370 371 372 373 377 381 382 383 384 393 394 395 396 Version 8.5.0
Error Description Number parsing code not valid. This function cannot process numbers. String quote mismatched or missing. This function generates too much data. Too many outputs from this function. Multiple-column outputs not allowed in recursive expressions. Recursive function trying to access future values (not causal). Inputs from the first row contains error. Output column(s) too long. Input/Output dimension of algorithm is corrupted. Recursive variable invalid Internal Only: Null ParseTree! Unknown value in substitution Error encountered interpreting variable type: 'Money' Error encountered interpreting Variable Type: 'Telephone' Error encountered interpreting Variable Type: 'Date' Error encountered interpreting Variable Type: 'Time' Boolean expression may be compared only to 1 or 0 Values out of range for one or more arguments. A numeric column must be specified with any keyword other than CountOf. BETWEEN syntax is: <val> BETWEEN <val1> AND <val2> 415
E - Error Codes
Error Description SUBSTR[ING] syntax is: SUBSTR[ING](<string><offset><size>) Option [OutputValue] is only allowed for MinOf, MaxOf, and MedianOf keywords. Null value found. Unable to change file permissions (chmod). Unable to retrieve file attributes (stat). Unable to remove file. Unable to create memory object; check log file for memory or file errors. Unable to lock memory object page; check log file for memory or file errors. Unable to load memory object; check log file for memory or file errors. Unable to create I/O object; check log file for memory or file errors. Unable to create I/O object; check log file for memory errors. Invalid supporting file extension; this may indicate a corrupted file. Invalid UTF-8 character encountered. Unable to convert from wide character to native encoding. Unable to convert from native encoding to wide character. Unable to create directory. Unable to remove directory. Internal parse tree construction error. Internal error: Configuration root not specified.. Configuration server URL is not specified.
399 450 451 452 453 454 455 456 457 458 459 460 461 462 463 500 600 601
416
Error Description Specified configuration category not found. Specified configuration property must have absolute file path. Invalid response from configuration server. INTERNAL ERROR: Requested configuration path is different from current root. Configuration categories and properties cannot have empty name. Configuration category name cannot contain forward slash. Specified configuration property must have relative file path. INTERNAL ERROR: Partition name not specified. Cannot determine default partition. No partition with the given name. No partitions defined at all. Invaild parameters specified in config.xml. INTERNAL ERROR: Security manager is already initialized. INTERNAL ERROR: Invalid result set name specified. User is not mapped to any partition. User is mapped to multiple partitions. User is not mapped to the specified partition. User is not authorized to access the application. Out of memory.
606 607 608 609 610 611 612 614 620 621 622 623 625 626 700
Version 8.5.0
417
E - Error Codes
Code 701
Error Description Cannot open file. Possible causes: [Campaign could not transcode a non-ASCII file name.] [Campaign could not locate the specified file.] [Campaign cannot open the file properly.] [Campaign could not transcode a non_ASCII file name.] [A file could not be copied because it could not be opened.] Suggested solutions: [Verify the file exists in the expected location.] [Examine the log file for the name of the file causing the error.] [Ask your system administrator for assistance.]
702 703 704 710 711 723 761 768 773 774 778 779 780
File seek error. File read error. File write error. Flowchart file data corrupted. File create error. Error in one or more input variables to this function. Out of disk space. Error saving file. Access denied. INTERNAL HMEM ERROR: cannot flush memory when swapping is disabled. Numerical error: Unknown floating point error. Numerical error: Explicit generation. Numerical error: Invalid number.
418
Code 781 782 783 784 785 786 787 788 789 790 967 997 998 999 1400 1500 1501 1550 1649 1650 1709 Version 8.5.0
Error Description Numerical error: Denormal. Numerical error: Division by zero. Numerical error: Floating point overflow. Numerical error: Floating point underflow. Numerical error: Floating point round-off. Numerical error: Floating point unemulated. Numerical error: Square root of negative number. Numerical error: Stack overflow. Numerical error: Stack underflow. Internal Error. Data dictionary contains an invalid definition. Internal error: GIO stack overflow. Error loading object: size check failed. Extended Error Row offset not found for given row Insufficient memory for this operation. Maximum histogram range exceeded Internal Error 1550: Vector is not allowed for any argument.. First parameter cannot be vector if COL keyword is used. Client/Server version mismatch. 419
E - Error Codes
Error Description Unable to initialize sockets. Unable to create a socket. Unable to connect to the specified server. Possible causes: [Your browser cannot connect to the Campaign server.] [Your browser cannot find the host name.] Suggested solutions: [Ask your network administrator to check that the server and client machines can 'ping' each other.] [Ask your Campaign administrator to check that the Campaign server machine does not use the port assigned to the Campaign listener process for another application.] [Try the steps that caused the error again. If the error occurs again, reboot your client machine, and ask your system administrator to reboot the Campaign server machine.]
1713 1714
Unable to send socket data. Unable to receive socket data. Possible causes: [The number of bytes received from socket does not match the expected number.] [Campaign timed out waiting for data from the socket.] [There was a socket error when sending messages.] Suggested solutions: [Ask your network administrator to check that the server and client machines can 'ping' each other.] [Ask your Campaign administrator to check that the Campaign server machine does not use the port assigned to the Campaign listener process for another application. [Try the steps that caused the error again. If the error occurs again, reboot your client machine, and ask your system administrator to reboot the Campaign server machine.]
1715 1716
420
Code 1717 1719 1729 1731 1733 1734 1735 1736 1737 1738 1739 1741 1742 1743
Error Description Communication request has timed out. INTERNAL ERROR: Communication request has timed out. Client/Server library: Error retrieving drive information. INTERNAL ERROR: Invalid argument index specified. Listener unable to create semaphore. Listener: invalid File Block server port. Listener unable to invoke specified command. Listener: invalid UDME server port. Listener: invalid Shannon server port. Listener: unable to communicate with server process. Listener: internal data integrity error. Unable to create thread. Unable to wait for thread. Client/Server library: Invalid process.Possible causes: A process, such as trigger, bulk loader, or the UDISvr, no longer exists.Suggested solutions: Examine the log file to determine if one of these processes ended abnormally. Ask your Campaign administrator to restart the process that ended abnormally. If the error occurs again, ask your system administrator for assistance. Client/Server library: Invalid semaphore. Client/Server library: Invalid mutex. Client/Server library: Insufficient memory. INTERNAL ERROR: Client/Server library: Timeout elapsed object not signaled. Client/Server library: Wait for object failed.
Version 8.5.0
421
E - Error Codes
Error Description Client/Server library: Invalid directory specified. INTERNAL ERROR: Requested server function unsupported. Server shutting down; request refused. UDMEsvr: flowchart requested for deletion is in use. Someone else is already in EDIT or RUN mode. Edit before run is completed is not allowed Requested flowchart is active for another user. Server process has exited. Possible causes:The Campaign listener cannot start the Campaign server process. Suggested solutions: Ask your system administrator for assistance.
Maximum number of flowchart instances is already in use. Requested flowchart is active for Distributed Marketing. Requested flowchart is in use by an Campaign user. Unable to authenticate user. Possible causes: [The password you provided does not match the password stored in the Marketing Platform.] [The user name or password field for accessing the database or other object is empty in the Marketing Platform] [The user name or password field for accessing the database or other object is empty in the Marketing Platform.] Suggested solutions: [Check that the user name and password you provided are correct.] [Ask your Campaign administrator to check that your user names and passwords stored in the Marketing Platform are complete and correct.]
1791
422
Code 1792 1793 1794 1795 1796 1797 1823 1824 1825 1830 1831 1832 2000 2001 2002 2003 2004 2005 2006 2007 2008 Version 8.5.0
Error Description Invalid file mode specified. INTERNAL ERROR: Exit status requested for active process. Evaluation period has expired. Invalid License Code. Flowchart name has been changed by the writer Flowchart name has been changed by the writer INTERNAL ERROR: Mismatch in request parmeter count. INTERNAL ERROR: Mismatch in request parameter type. INTERNAL ERROR: Mismatch in request scalar or vector count. Unsupported protocol type encountered. Invalid API. No server process found for specified run. Run may be completed already. HTTP session object is invalid. HTTP connection object is invalid. HTTP request object is invalid. Error adding HTTP request headers. Error setting HTTP proxy credentials. Error setting HTTP server credentials. Error sending HTTP request. Error receiving HTTP response. Error querying HTTP response headers. 423
E - Error Codes
Error Description Error reading HTTP response data. Error status returned in HTTP response. Error querying HTTP authentication schemes. No matching HTTP authentication schemes. Proxy server authentication failure. You must provide a valid proxy server username and password in a data source named proxy in the Marketing Platform before re-attempting to log into Campaign. Web server authentication failure.You must provide a valid web server username and password in a data source named "webserver\" in the Marketing Platform before re-attempting to log into Campaign. HTTP request error after PAC file authentication failure. HTTP request error after PAC file scheme failure. Internal Error. Internal Error: Cannot find Process. Internal Error: Cannot find Connection. Internal Error: Cannot find Process. Internal Error: Cannot find Connection. Internal Error: Unknown function tag. Flowchart contains cycles. Internal Error: Cannot get memory buffer from GIO. flowchart is running. Internal Error: Unknown copy state. Error modifying system table.
2014
2015 2016 10001 10022 10023 10024 10025 10026 10027 10030 10031 10032 10033
424
Error Description One or more Processes are not configured. Process has multiple Schedule inputs. Internal Error: Cannot find Process. One or more pasted Processes have derived fields defined. They may need to be redefined. Branch has one or more input processes outside of the branch. flowchart DOM creation error. flowchart DOM parse error. Flowchart is recovered from auto-save file. The Flowchart that creates the Global Suppression Segment needed by this run is currently executing. The Global Suppression Segment is missing. The Global Suppression Segment is at the wrong audience level. Only one process box of this type is allowed. Only one branch is allowed. Flowchart must begin with an Interaction process box. Unable to find treatment in the Treatment Cache. Internal Error: Process not registered. Internal Error: Unknown function tag. Process is running. Process run results will be lost. Internal Error. Process is not configured. 425
10043 10044 10046 10047 10048 10049 10116 10119 10120 10121 10122 10125 Version 8.5.0
E - Error Codes
Code 10126 10127 10128 10129 10130 10131 10132 10133 10134 10136 10137 10138 10139 10140
Error Description Process input is not ready. Process name not unique. Internal Error: Invalid Process index. Internal Error: Invalid Report ID. Internal Error: Invalid Table ID. Internal Error: Invalid Field index. Internal Error: Invalid Cell ID. Internal Error: Invalid Field index. Internal Error: Invalid Process for registration. Process run stopped by user. Changes are not allowed while the Process is queued. Changes are not allowed while the Process is running. Changes are not allowed while a subsequent Process is running or queued. The source of the Process has been changed. Derived fields and subsequent Processes may need to be reconfigured. One or more selected Tables don't exist. Changes are not allowed while the flowchart is running. Process DOM creation error. Process DOM parse error. Unknown Process Parameter. Process name contains invalid character.
426
Error Description Output Cell Name is empty. Accumulate ID's option must be turned off for schedule process to run on queue. Command not allowed in Reader mode. Cannot open Segment data file. Segment data file error: Invalid header. Internal Error: Invalid Segment (Data file name is blank). Undefined user variable referenced in path. Critical error encountered. A preceding process has not been run in production mode. Cell name conflict detected in flowchart. Cell code conflict detected in flowchart. Topdown target cell is linked more than once. Linked topdown cell missing or already linked to another Invalid field name. Target cell is not yet approved to run in production. In order to run in production, all input cells for this process must be linked to cells in the TCS. This process cannot handle topdown cells that are control cells or have control cells. Cannot open Segment TempTable. Internal Error: Invalid Segment (Segment TempTable DB is blank). Internal Error: Invalid Segment (Segment TempTable name is blank).
10149 10150 10151 10152 10153 10154 10155 10156 10157 10158 10159 10161 10162 10163
10164
Version 8.5.0
427
E - Error Codes
Code 11167 11168 11169 10200 10201 10206 10207 10208 10209 10210 10211 10300 10301 10302 10303 10304
Error Description Inputs have different audience levels. Specified flowchart template not found in the system. Interact base table mapping not found. Internal Error: Invalid 'From' Process Internal Error: Invalid 'To' Process Internal Error: Invalid 'From' Process Internal Error: Invalid 'To' Process Internal Error: Invalid connection index. Internal Error: DOM creation error. Internal Error: DOM parse error. Conflicting cell code ignored. ServerComm out of memory. INTERNAL ERROR: No function registered for class. INTERNAL ERROR: Requested function not supported. Another flowchart connection has been established; reconnect not allowed. All communication ports in the range specified in UNICA_ACSVR.CFG are in use. Requested flowchart is already in use. Command not allowed in reader mode Flowchart is in use. Not enough privileges to takeover. INTERNAL ERROR: flowchart not running.
428
Error Description INTERNAL ERROR: Client connected to flowchart. Unrecognized command. Invalid syntax. INTERNAL ERROR: SUSPEND RUN in progress. No sessions were affected. The operation cannot be performed at this time. Please review the flowchart log for the probable cause and try again later. New connections have been disabled. An administrator must use unica_svradm's UNCAP command to re-enable. flowchart run completed with errors. Cached data not found Flowcharts need to be specified with relative, not absolute, pathnames to the partitionHome property defined in the central configuration repository provided by IBM Unica Marketing. INTERNAL ERROR: Client already connected. Client is not connected to a server. Connection to server has been lost. Retry?
10356
Version 8.5.0
429
E - Error Codes
Code 10404
Error Description Unable to communicate with server process; it may have exited. Possible causes [The Campaign server process:] [cannot start when you log in, or when you create or open a flowchart.] [no longer exists when you re-connect to the server.] [terminated abnormally.]
Suggested solutions [Ask your Campaign administrator to check that the:] [Campaign listener process is running.] [same version of the Campaign web application, listener, and server are running on your system.] port number is properly configured in the central configuration repository provided by Marketing Platform.]
Ask your system administrator to examine the system log for additional information related to this error. 10405 10406 10407 10408 10409 10410 10411 Server process is unresponsive; RETRY to wait or CANCEL to disconnect. INTERNAL ERROR: Communication with server already in progress. You have been disconnected; an administrator has suspended this flowchart. You have been disconnected; an administrator has killed this flowchart. You have been disconnected; an administrator has stopped this flowchart. You have been disconnected; an administrator has removed this flowchart. You have been disconnected; an administrator has taken control of this flowchart. HTTP SessionID is invalid, or HTTP Session has timed out. Windows impersonation failure Continue sending windows authentication messages Stop sending windows authentication messages Failed to generate TYPE-1 message
430
Error Description Failed to generate TYPE-2 message Failed to generate TYPE-3 message Server process is unresponsive; unable to connect at this time. Server process is unresponsive; unable to send trigger to all specified flowcharts at this time. Server process is unresponsive; unable to reconnect at this time. Server process is unresponsive; unable to complete requested action at this time. Possible causes The Campaign server is busy processing another request. Suggested solutions Ask your system administrator to check that Campaign server machine has enough CPU or memory resource.
10452 10453
10454
Server process is updating flowchart data; unable to complete requested action at this time INTERNAL ERROR: SRunMgr RunProcess thread already running. Process's run was cancelled by Run Manager destruction. Invalid Campaign Code format. Invalid Offer Code format. Failed to generate Campaign Code. Failed to generate Offer Code. Invalid Treatment Code format. Failed to generate Treatment Code. Invalid Cell Code format.
Version 8.5.0
431
E - Error Codes
Code 10537 10538 10539 10540 10541 10542 10550 10551 10552 10553 10554 10555 10556 10557 10558 10559 10560 10561 10562 10563 10564 432
Error Description Failed to generate Cell Code. Invalid Version Code format. Failed to generate Version Code. Campaign code format contains invalid characters. Cell code format contains invalid characters. Treatment code format contains invalid characters. HTTP communication error. Invalid response from ASM Server. ASM Server: unknown error. ASM Server: Login is invalid. ASM Server: Error while inserting into db. ASM Server: Error while trying to map ASM objects. ASM Server: Error because object already exists. ASM Server: Password Expired. ASM Server: Password is too short. ASM Server: Password not properly formed. Internal Error: parsing data returned from ASM Server. ASM Server: Valid login required. ASM Server: Group name required. ASM Server: Action not supported. ASM Server: Exceeded maximum allowable pw attempts. IBM Unica Campaign - Administrator's Guide
Code 10565 10566 10567 10568 10569 10570 10571 10572 10573 10576 10577 10578 10580 10581 10582 10583 10584 10585 10586 10590 10591 Version 8.5.0
Error Description ASM Server: Password does not contain minimum number of numerics. ASM Server: Password cannot be same as login. ASM Server: Password cannot be reused from before. ASM Server: User logon is disabled. ASM Server: Password does not contain minimum number of letters. ASM Server: Password cannot be blank. ASM Server: Password is incorrect. This action requires proper privileges. ASM Server: Internal System Error. Internal Error: ASM client module is not initialized. Login required to query for db credentials. Security data integrity error. HTTP communication error Invalid response from eMessage Server eMessage Server: unknown error eMessage Server: Internal System Error eMessage server url is not set. Internal Error: parsing data returned from eMessage Server Error returned from eMessage Server. setuid failed. setgid failed 433
E - Error Codes
Code 10600 10601 10603 10604 10605 10606 10607 10608 10612 10613
Error Description Internal Error: Cell already initialized Internal Error: Source Cell not initialized Internal Error: Invalid cell ID. Internal Error: Invalid field index. Audience ID field not defined. Internal Error: Cannot find table manager. Invalid Table ID. Operation not allowed while cell is being accessed. Internal Error: Derived Field not found. Field not found. Possible causes: [The field no longer exists because of table mapping change.] [The audience level changed.] [The field was deleted.] Suggested solutions: Re-configure the process box to reference a different field.
Internal Error: Derived variable not initialized. Internal Error: Expression returns multiple columns. Internal Error: Invalid row index. Ambiguous field name. Internal Error: selected fields not yet computed. Internal Error: Access object became invalid. Internal Error: No Data Source selected for Raw SQL Query.
434
Error Description Error writing temporary file on Campaign server. Operations not allowed on different audience levels. Reference to stored query not found. Internal Error: Derived variable should not contain data. Incompatible sort order detected. Set \enable_select_order_by=FALSE\ in dbconfig.lis. Cannot resolve reference to stored query: Stored Query table not yet mapped. User Variable not defined. Cell results are missing; preceding processes must be rerun. Invalid value in 'counts' field. Internal Error: Bad STCell _Select State. Derived variable name conflicts with an existing Persistent Derived Field. Temp table not available for <TempTable> token. Temp table has too many rows Temp table does not have enough rows <OutputTempTable> token used, but data source configuration does not allow temp tables. Cannot create temp table on system database. Check datasource configuration to make sure temp tables are allowed and bulk insert or database loader is enabled. HTTP communication error with Instance Manager Incompatible field type or width. Duplicate parameter name for Custom Macro.
10635 10636 10637 10638 10639 10641 10642 10643 10644 10645
10646
Version 8.5.0
435
E - Error Codes
Code 10801 10802 10803 10804 10805 10806 10807 10808 10809
Error Description Missing parameter name for Custom Macro. Incorrect number of parameters for Custom Macro. Illegal parameter name for Custom Macro. Name conflicts with an existing Custom Macro. Missing parameter for Custom Macro. Parameter name is a reserved word. Illegal Custom Macro name. Name conflicts with an existing IBM Macro. Parameter used within Custom Macro expression is not part of Macro definition. Audience level is not defined in selected ACO session. Proposed contact table is not defined in selected ACO session. Proposed offer attribute table is not defined in selected ACO session. Optimized contact table is not defined in selected ACO session. INTERNAL DYNAMIC CAST ERROR Invalid configuration for ODS Campaign. Internal Error: SendMessage error. Internal Error. Internal Error: Unknown report type. The flowchart is being accessed by another user. Memory allocation error.
10810 10811 10812 10813 10820 10821 11001 11004 11005 11006 11100
436
Code 11101 11102 11104 11105 11107 11108 11109 11110 11111 11112 11113 11114 11115 11116 11117 11119 11120 11121 11122 11128 11131 Version 8.5.0
Error Description Internal Error: Unknown function tag. Internal Error: Unknown class name in IDtoPtr. Internal Error: Bad magic number in SCampaignContextConfig. File name not specified. Server campaign context internal error. Internal Error: Cannot lock report. Table is not defined. Environment variables not set. Internal Error: Error getting field info. Invalid Password. Flowchart name not unique or empty. Campaign code not unique. Active flowchart can not be deleted. The specified file is not a Campaign flowchart file. Deletion of an old flowchart file is not supported. Please delete it manually. Unable to write unica_tbmgr.tmp file in tmp directory. Unable to rename unica_tbmgr.bin in conf directory. Unable to copy unica_tbmgr.tmp to unica_tbmgr.bin file. Unable to read unica_tbmgr.bin file in conf directory. Operation disallowed in configuration. Invalid template file format. 437
E - Error Codes
Code 11132 11133 11134 11135 11136 11137 11138 11139 11140 11141 11142 11143 11144 11145 11146 11147 11148 11150 11151 11152
Error Description XML initialization error. DOM creation error. DOM parse error. Internal Error: Unknown user variable Server campaign context cell locking error. Server campaign context file open error. The named user exists already. No user list table is mapped to the admin. session. User not found. Wrong password. File read error. Empty user variable. Flowchart name and Campaign code not unique. authentication_server_url missing in unica_acsvr.cfg file. Invalid user variable. User Variable not found. Changes to the virtual memory setting are not allowed. Unable to create folder file. Please check your OS privilege. Unable to delete folder file. Please check your OS privilege. Unable to rename folder/campaign/session file. Please check your operating system privilege.
438
Code 11153 11154 11155 11156 11157 11158 11159 11160 11161 11162
Error Description Unable to create campaign/session file. Please check your OS privilege. Unable to delete campaign/session file. Please check your OS privilege. Unable to move folder/campaign/session file. Please check your OS privilege. Failed to authenticate datasource. Effective date is later than expiration date Unable to open campaign/session file. Please check your OS privilege. Unable to read Log file. Please check your OS privilege. Cannot display log. Log file name not specified Operation is not allowed while the flowchart is running. Log file does not exist. Change logging levels if you would like to see more logging information. Campaign/session file does not exist in the file system. Server Stored List Internal Error. Stored List unknown function tag. Invalid security policy. Container internal error (1). Container internal error (2). Container data loading error. Unable to create transcoders between specified encoding and UTF-8. Unable to transcode text value. Cannot determine name of local host.
11163 11164 11165 11166 11201 11202 11203 11230 11231 11232
Version 8.5.0
439
E - Error Codes
Code 11251 11253 11254 11255 11256 11257 11258 11259 11260 11261 11262 11263 11264 11265 11266 11267 11268 11269 11270 11271 11272 440
Error Description New passwords mismatched. Please re-type. Stack overflow during sort operation. Too many arguments passed to command-line parser. Unbalanced quotes in command or config-file parameter. Unable to open flowchart LOG file for append. Unable to write to flowchart LOG file. Unable to rename flowchart LOG file. Invalid Multibyte or Unicode character encountered. Illegal or duplicate campaign code. Invalid old password New read/write passwords mismatched. New read-only passwords mismatched. Invalid read/write password. Invalid read-only password. Password must contain at least 6 characters. Report registered. Report name missing. New passwords mismatched. Cannot create temporary file on client computer. Error reading temporary file on client computer. Error writing temporary file on client computer. IBM Unica Campaign - Administrator's Guide
Code 11273 11274 11275 11276 11280 11281 11282 11283 11284 11285 11286 11287 11288 11289 11290 11300
Error Description Set new configuration as default? Unmap the selected table(s)? No fields selected. No flowchart name. Execution Checkpoints will not be performed. Server version is newer than client version. Upgrade client installation? Server version is older than client version. Downgrade client installation? Installation executable retrieved but unable to execute. About to clear flowchart log. Are you sure? Help topic not found. Error parsing help topics file. flowchart is recovered from auto-save file. Error loading bitmap. Settings changed. Save catalog now? Flowchart is already open. Disconnect current user and connect? Flowchart must be saved before this operation can proceed. Invalid field name. Look at the end of message for invalid field name. Possible causes: [The field no longer exists bacause of table mapping change.] [The audience level changed.] [The field was deleted.] Suggested solutions: Re-configure the process box to reference a different field. Invalid Field Name=
Version 8.5.0
441
E - Error Codes
Code 11301 11302 11303 11304 11305 11306 11307 11308 11309 11310 11311 11312 11313 11314 11315 11316 11317 11318 11319
Error Description Invalid field index. No more records. Operation not allowed while table is being accessed. Locked tables cannot be removed. Invalid table ID. ParseTree context in use. Random access of basetable by parsetree not allowed. Invalid table index. Invalid key index. Index key not initialized. Entry not found in dimension table. ID field not specified. Invalid Table access. Data already imported. Internal error: VFSYSTEM missing Input files not yet specified. No data. Modification not yet started. Entry into index field is not unique.
442
Code 11320
Error Description Unable to create lock file in conf directory. Possible causes: The Campaign server cannot lock the dummy_lock.dat file Suggested solutions: Ask your system administrator to check that the file is not locked by another process. If another process is not locking the file, ask the Campaign administrator to reboot the Campaign server to remove the lock.
11321 11322 11323 11324 11325 11326 11327 11328 11329 11330 11331 11332 11333 11334 11335 11336 11337 11338 Version 8.5.0
Internal table error Unknown function tag Data Dictionary file name not specified. Function or Operation not supported. 'dbconfig.lis' file not found. Dimension table does not have a key field. ID of new version conflicts with existing versions. Cannot open table catalog file. Too many duplicate ID's to perform table join. Unable to delete template file Unable to delete catalog file. Error parsing Data Dictionary file: invalid format. Error converting text data to numeric. Field width too small to hold converted numeric value. Field width too small to hold source text data. Accessed table not mapped. Duplicate ID encountered in normalized table. Internal error: Invalid temp table. 443
E - Error Codes
Code 11339 11340 11341 11342 11343 11344 11345 11346 11347 11348 11349 11350 11351 11352 11353 11354 11355 11356 11357 11358 11359 444
Error Description Audience definition not compatible: wrong number of fields. Audience definition not compatible: type mismatch. Name of new version conflicts with existing versions. Field not found. Data dictionary has changed. XML table catalog file is invalid. Loader command exited with an error status. Table schema has changed; please remap the table. No results for queue table. Internal error, wrong return format. Internal error loading catalog. No catalog loaded. Internal error connecting to table. Not connected to a table. Invalid keyword in dbconfig.lis file. Invalid UDI connection. Internal Error: base table not set. Invalid table name. DOM creation error. DOM parse error. Unable to import duplicate system table entry. Unable to lock system table. IBM Unica Campaign - Administrator's Guide
Code 11360 11361 11362 11363 11364 11365 11366 11367 11368 11369 11370 11371 11372 11373 11374 11375 11376 11377 11378 11379 11380 Version 8.5.0
Error Description PACKED DECIMAL field type is supported for export only. This operation is not supported. Too many fields returned by SQL expression. Data field returned by SQL expression does not agree with user specification. Unknown database specification in raw SQL Custom Macro. Raw SQL Custom Macro returning only ID list is not allowed in this context. Segment not found. Temp table not available for <TempTable> token. Contact History Table is not yet defined for this audience level. Response History Table is not yet defined for this audience level. Dimension Element expression is missing. Ambiguous bin definition. Custom Macro returned wrong number of fields. Custom Macro result fields are not compatible with the current audience level. Dimension Element name is not unique across all levels. Unknown Dimension Name. Unknown Dimension Element. Missing database specification for raw SQL Custom Macro. Campaign code not unique. Root dimension element missing in XML file. Error converting date from one format to another. 445
E - Error Codes
Code 11381 11382 11383 11384 11385 11386 11387 11388 11389 11390 11391 11392 11393 11394 11395 11396 11397
Error Description Not enough privileges to use RAW SQL in Dimensions. Syntax error: Missing AND/OR operator. Syntax error: Extra AND/OR operator at end of selection criteria. Field not compatible: Numeric field expected. Field not compatible: Date field expected. Error returned from UDI server. Internal ID would exceed limit. Cannot open Segment data file. Segment data file error: Invalid header. Internal Error: Invalid Segment (Data file name is blank Error accessing segment data. Cannot perform table join unless tables are on the same database. Unable to add entry to non-persistent queue Audience level is reserved, cannot add. Audience level is reserved, cannot remove. Internal Error: Invalid optimized contact table name. Field data exceeded the table mapping width for this field. Remap the table and manually increase the field width before running the flowchart. Post temp table create run script completed with error(s). Cannot allocate an ID for a new object because the allocator is busy. Temp table not available for <OutputTempTable> token.
446
Code 11401 11402 11403 11404 11405 11408 11409 11410 11411 11412 11413 11414 11415 11416 11417 11418 11419 11420 11500 11501 11502 Version 8.5.0
Error Description Invalid audience level definition. Missing audience field definition. Invalid or missing audience field name. Duplicate audience field name. Invalid or missing audience field type. INTERNAL ERROR: Invalid ID. INTERNAL ERROR: Wrong DAO type. DAO INTERNAL ERROR. INTERNAL ERROR: System DAO factory is not initialized yet. INTERNAL ERROR: Unknown DAO implementation requested. INTERNAL ERROR: Invalid type detected in DAO transfer. Insert operation only supported on single table. Update operation only supported on single table. Delete operation only supported on single table. SQL query returned multiple records when unique record is expected. Default contact status not found in ContactStatus table. Contact History table must be mapped before Detailed Contact History table. Offer not found in the system. Internal Error: Not a valid table in the database. Internal Error: No table has been selected. Selected table has no field entries. 447
E - Error Codes
Code 11503 11504 11505 11506 11507 11508 11509 11510 11511 11512 11513 11514 11515 11516 11517 11518 11519 11520 11521 11522 11523 448
Error Description Invalid column index. Invalid column name. Invalid data source. Selected table is invalid or corrupted. Insufficient memory. Database row deletion error. Error in processing SQL query. No data returned - check query. No matching row was found in the query result. No more rows in the database. Error inserting row into database table. Bad database ID column. Error updating database table. Error creating new database table. Number of columns not correct for this type of query. Database connection error. Error in getting results from database. Unknown database type for dataSources. Internal Error: Incorrect state for query results. Invalid database connection (user is not logged in to DB). First unique ID not set. IBM Unica Campaign - Administrator's Guide
Code 11524 11525 11526 11527 11528 11529 11530 11531 12000 12001 12002 12003 12004 12005 12006
Error Description Invalid data type for this column. Query has no FROM clause. Query uses alias. Internal Error: Error in database temporary table. Database Error. INTERNAL ERROR: No threads available to run query. Invalid property for dataSources Catalog/Template contains different DB login(s). Contact History Table not specified. Customer ID not specified. Offer ID not specified. Channel field not specified. Date field not not specified. No proposed contacts table templates. No tables available for template. Template tables must be mapped at Customer level and must contain the required Offer, Channel, and Date fields. No tables available for opt-in/opt-out tables. Opt-in/opt-out tables must be mapped at Customer level. Opt-in/Opt-out tables not specified. \"Customer In...\" rules will not be available. Offer Table not specified. Offer Name field not specified. Offer ID will be used for display. Channel Table not specified.
12007
Version 8.5.0
449
E - Error Codes
Error Description Channel Name field not specified. Channel ID will be used for display. Field name(s) of Offer audience level in template table does not agree with Contact History Table. Field name(s) of Offer audience level in offer table does not agree with Contact History Table. No tables available for offer table. Offer table must be mapped at Offer level. No tables available for channel table. Channel table must be mapped at the Channel level. Killing the server process will lose all work since the last save. Are you sure? Window creation failed. Remove the following tables associated with this audience level? Remove the selected dimension hierarchies? Flowchart is in use. Do you still want to continue? If you click Yes, changes made by other user will be lost.
12016
12017 12018
Remove the selected audience level? Audience name already exists. This flowchart has been modified or removed by another user. You will be switched to Summary tab now. All changes after the last save will be discarded. This flowchart needs to be updated. Click OK to update now. You will need to redo the last action after update is completed. Object is either initializing or has failed to initialize. You may try this operation again. Remove the selected items? You have chosen to cancel connection to Campaign system tables.You will be switched to Summary tab now.
12027
12028
12029 12030
450
Error Description Cannot proceed without connection to Campaign system tables. This table is only supported when Interact is installed. Failed to load flowchart. Retry? HTTP Session has timed out. Click OK to log back in. Flowchart control is not compatible. Browsers need to close to download the lower version. Please close all other browsers manually and click OK to close this browser.On browser restart, the control will get downloaded automatically. There are still other browsers running. Please close them before clicking OK. Field name contains illegal character. Audience level name not specified. Audience field(s) not specified. No errors detected in flowchart configuration. This running flowchart has been paused by another user. Cannot navigate up a directory: already at root. Cannot create directory; check log file for detailed error information. Merge process internal error. Merge process connecting from process error. Merge process cell locking error. Merge process stopped by user. Merge process cell operation error. Merge process getting source cell error. Merge process not configured.
12036 12037 12038 12039 12040 12041 12206 12207 12301 12303 12304 12305 12306 12307 12308
Version 8.5.0
451
E - Error Codes
Code 12309 12310 12311 12312 12401 12600 12601 12602 12603 12604 12605 12606 12607 12608 12609 12610 12611 12612 12613 12614 12615 452
Error Description No input cell is chosen. No input cell is used. Selected input cells have different audience levels. Missing source cell(s). Input connection may be invalid. Execute Internal Error (1) INTERNAL ERROR: SReport Report in use; unable to delete. INTERNAL ERROR: Invalid report ID. INTERNAL ERROR: Invalid report type saved. INTERNAL ERROR: Invalid report cell ID. INTERNAL ERROR: Report not initialized before run. INTERNAL ERROR: Missing value. INTERNAL ERROR: Unable to lock report. INTERNAL ERROR: Invalid field specified. Report cannot be created without any cells. INTERNAL ERROR: No more cell records available. Report name conflicts with another registered report. Cannot open HTML file for write. Field type does not match internal setting. Table may need to be remapped. Report name is empty. Command not allowed in Reader mode IBM Unica Campaign - Administrator's Guide
Code 13000 13001 13002 13003 13004 13005 13006 13101 13104 13110 13111 13113 13114 13115 13116 13117 13118 13119 13120 13121 13122 Version 8.5.0
Error Description An error occured while parsing the response from the webapp. The client id is missing in the response from the webapp. The resolution id is missing in the response from the webapp. The is complete flag in the response from the webapp, has a bad value An uknown error code has been returned from the webapp. HTTP communication error The response required an iscomplete flag, but it was missing. Internal error. Cell locking error. Process not configured. Unknown function tag. Report locking error. Profile report generation error. Table locking error. No input cell. No input selected. Missing selection criteria. No data source is selected. Selected tables have different audience levels. Audience level not specified. DOM creation error. 453
E - Error Codes
Code 13123 13124 13125 13131 13132 13133 13134 13135 13136 13137 13138
Error Description DOM parse error. Unknown parameter. Invalid parameter value. Database authentication required. String conversion error. No fields are selected for extract. Duplicate output name in fields to extract. No skip duplicate field selected. Command not allowed in Reader mode No source table selected. Error selecting based on dimension hierarchy: No tables mapped at selected Segment's audience level. Missing table mapping for selected optimize session. Missing CustomerInsight Selection. Selected CustomerInsight Selection is not valid. Missing NetInsight Selection. Selected NetInsight Selection is not valid. Contact process memory allocation error. Contact process internal error. Contact process connecting from process error. Contact process locking cell error.
454
Code 13205 13206 13207 13208 13209 13210 13211 13212 13213 13214 13215 13216 13217 13218 13219 13220 13221 13223 13224 13225 13226 Version 8.5.0
Error Description Contact process stopped by user. Contact process locking contact table error. Contact process locking version table error. Contact process getting cell information error. Contact process getting table information error. Contact process locking table error. Contact process unknown function tag error. Contact process GIO open error. Contact process locking report error. More information is needed for a creative piece. Exactly one variable cost item should be chosen. Conflict variable cost items. More information is needed for a version. At least one creative piece have to be chosen. At least one response channel have to be chosen. One contact channel has to be chosen. The chosen ID is not unique. Contact ID is not unique. Treatment page: No source cell. Treatment page: Contact ID is not selected. Treatment page: No version is selected. 455
E - Error Codes
Code 13227 13228 13229 13230 13231 13232 13233 13234 13235 13236 13237 13238 13239 13240 13241 13242 13244 13246 13248 13249 13250 456
Error Description Contact list page: No export table is selected. Contact list page: No summary file is chosen. Contact list page: No export fields are chosen. Tracking page: Frequency of update is not chosen. Tracking page: Monitor period can not be zero. Responders page: No responder table is chosen. Unreachable page: No unreachable table is chosen. Log page: No table is chosen to log contacts. Log page: No fields are chosen to log contacts. Log page: No table is chosen to log responders. Log page: No fields are chosen to log responders. Log page: No table is chosen to log unreachable. Log page: No fields are chosen to log unreachable. Contact process getting cell field infomation error. Contact list page: No trigger is specified. Contact list page: no sort field is chosen. Invalid field. Double to string conversion error. Contact list page: No export file is chosen. Contact list page: No delimiter is specified. Selected tables have different audience levels. IBM Unica Campaign - Administrator's Guide
Code 13251 13252 13253 13254 13255 13256 13257 13258 13259 13260 13261 13262
Error Description Contact list page: No export dictionary file is chosen. Log page: No file is chosen to log contacts. Log page: No delimiter is specified for contacts. Log page: No dictionary file is specified for contacts. Log page: No file is chosen to log responders. Log page: No delimiter is specified for responders. Log page: No dictionary file is specified for responders. Log page: No file is chosen to log unreachable. Log page: No delimiter is specified for unreachable. Log page: No dictionary file is specified for unreachable. Contact List Page: Selected Data Export Filename contains Invalid Path Contact List Page: Selected Data Dictionary for Export File contains an Invalid Path. Contact List Page: No skip duplicate field is chosen. Contact List Page: Update Records require a base table with audience same as input. Log Page Contact: Update Records require a base table with audience same as input. Log Page Responders: Update Records require a base table with audience same as input. Log Page Unreachable: Update Records require a base table with audience same as input. Tracking page: No trigger is specified. Responders page: No responder query is specified. 457
13263 13264
13265
13266
13267
E - Error Codes
Code 13270 13271 13272 13273 13274 13275 13276 13277 13278 13279 13280 13281 13282 13283 13284 13285 13286 13301 13304 13310 13311 458
Error Description Responders page: No data source is selected. Unreachable page: No unreachable query is specified. Unreachable page: No data source is selected. Selected source cells have different audience levels. Unknown parameter for Contact Process. Invalid parameter value for Contact Process. Version Name is not unique. Empty or Duplicate Cell Codes. About to modify a version used by another flowchart. Log Page Contact: No skip duplicate field is chosen. Log Page Responders: No skip duplicate field is chosen. Log Page Unreachable: No skip duplicate field is chosen. Contact process DOM creation error. No data source is selected. Contact List Page: Selected Data Dictionary File does not exist. Log page: No fields are chosen to log contacts. Command not allowed in Reader mode Internal error. Cell locking error. Profile report generation error. Unknown function tag. IBM Unica Campaign - Administrator's Guide
Code 13312 13313 13314 13315 13316 13317 13318 13320 13321 13322 13323 13324 13400 13401 13403 13404 13405 13408 13409 13410 13411 Version 8.5.0
Error Description Report locking error. No input is selected. No field is selected. No query is specified. No data source is specified. Name not unique. No table is selected. Unknown parameter. Invalid parameter value. Name not specified. Invalid name. Command not allowed in Reader mode Schedule process memory allocation error. Schedule process internal error. Connecting from process error. Cell locking error. Process stopped by user. Date format error. Time format error. Total schedule period is zero. No schedule to run is chosen. 459
E - Error Codes
Code 13412 13413 13414 13415 13416 13417 13418 13419 13420 13421 13422 13423 13424 13501 13503 13504 13505 13506 13507 13508 13510 460
Error Description Run on time needs times. Run on triggers needs triggers. Need output triggers. Elapsed time is zero. Additional wait must work with one of the first three run options. Schedule run time(s) outside the schedule period. Invalid time format. At least one of the custom run options has to be selected. Delay exceeds the total schedule period. Invalid time. Start time has expired. Input queue table not selected. Selected queue table is invalid. Cannot use 'Run Selected Process' on this process Sample process internal error. Sample process connecting from process error. Sample process cell locking error. Sample process stopped by user. Sample process locking sample table error. Sample process locking version table error. Sample process getting source cell error. Sample process unknown function tag. IBM Unica Campaign - Administrator's Guide
Code 13511 13512 13513 13514 13515 13516 13517 13518 13519 13520 13521 13601 13602 13603 13604 13605 13701 13703 13704 13705 13706 Version 8.5.0
Error Description Sample process not configured. Sample process output cell size exceeding input cell size. No source cell is chosen. No ordering field is chosen. Name not unique. Unknown parameter for Sample Process. Invalid parameter value for Sample Process. Sample name not specified. Invalid sample name. Command not allowed in Reader mode Sample size not specified. Internal error. GIO open error. The named trigger doesn't exist. Trigger name not specified Trigger completed with error(s). Score process internal error. Score process connecting from process error. Score process cell locking error. Score process stopped by user. Score process cell operation error. 461
E - Error Codes
Code 13707 13708 13709 13716 13717 13718 13719 13720 13721 13723 13724 13725 13726 13727 13728 13729 13730 13801 13803 13804 13805 462
Error Description Number of models can't be zero. Score process GIO open error. Environment variables not set. Score field prefix is missing. An internal model is not selected. An external model is not chosen. Model variables are not completely matched. No input is selected. The number of models is zero. Score field prefix not unique. The external model (rtm) file is incompatible with current SCORE configuration. Invalid field. dbscore process completed with error(s). Unknown parameter for Score Process. Cannot find external model file. Cannot get model information. Model file may be invalid. Command not allowed in Reader mode SelectOpt process internal error. SelectOpt process connecting from process error. SelectOpt process cell locking error. SelectOpt process stopped by user. IBM Unica Campaign - Administrator's Guide
Code 13806 13807 13809 13812 13825 13833 13834 13901 13903 13904 13905 13906 13907 13909 13910 13911 13912 13913 13914 13915 13917 Version 8.5.0
Error Description SelectOpt process cell operation error. SelectOpt process table locking error. SelectOpt process report locking error. dbscore process completed with error(s). Duplicate Personalization Field Name specified. Personalization Field Display Name is blank. Personalization Field Display Name contains invalid character. Internal error. Connecting from process error. Cell locking error. Process stopped by user. Cell operation error. Table locking error. Unknown function tag error. Report locking error. No input is selected. No export table is selected. No fields are selected for export. No sort field is chosen. Invalid field name. Invalid field name. 463
E - Error Codes
Code 13918 13921 13923 13924 13925 13926 13927 13928 13929 13930 13931 13932 13933 13934 13935 14001 14003 14004 14005 14006 14008 464
Error Description No export file is selected. String conversion error. Selected cells have different audience levels. No delimiter is specified. No export data dictionary file name is specified. Selected Data Export Filename contains Invalid Path Selected Data Dictionary for Export File contains an Invalid Path. No skip duplicate field selected. Update Records require a base table with audience same as input. Snapshot process DOM creation error. Unknown parameter for Snapshot Process. Invalid parameter value for Snapshot Process. Empty or Duplicate Cell Codes. Selected Data Dictionary File does not exist. Command not allowed in Reader mode Model process internal error. Model process connecting from process error. Model process cell locking error. Model process stopped by user. Model process cell operation error. Model process report locking error. IBM Unica Campaign - Administrator's Guide
Code 14009 14010 14013 14014 14015 14016 14017 14018 14101 14103 14104 14105 14106 14107 14108 14110 14111 14112 14113 14114 14115 Version 8.5.0
Error Description No responder cell is selected. No non-responder cell is selected. Model file name is not selected. At least one variable has to be used for modeling. No responder and non-responder cells are selected. udmerun process completed with error(s). Selected Model Filename contains Invalid Path Command not allowed in Reader mode EvalOpt process internal error. EvalOpt process connecting from process error. EvalOpt process locking cell error. EvalOpt process stopped by user. EvalOpt process cell operation error. EvalOpt process table locking error. EvalOpt process unknown function tag. EvalOpt process locking report error. No responder cell is chosen. No non-responder cell is chosen. No responder field is chosen. No non-responder field is chosen. Unknown parameter for EvalOpt Process. 465
E - Error Codes
Code 14116 14117 14118 14119 14120 14202 14203 14204 14205 14206 14207 14208 14209 14210 14301 14303 14304 14305 14306 14307 14308 466
Error Description Set number not specified. Set number out of range. Set name is empty. Not supported options. Command not allowed in Reader mode PopulateSegment internal error. PopulateSegment cell locking error. PopulateSegment process unknown function tag. No input is selected. Segment name not unique within the specified folder. Segment name is not specified. Invalid segment name. Invalid security policy. Security policy not specified. TestOpt process internal error. TestOpt process connecting from process error. TestOpt process cell locking error. TestOpt process stopped by user. TestOpt process cell operation error. TestOpt process table locking error. No source cell is selected. IBM Unica Campaign - Administrator's Guide
Code 14309 14310 14317 14319 14320 14321 14322 14323 14324 14501 14502 14503 14504 14505 14701 14703 14704 14705 14706 14901 14902 Version 8.5.0
Error Description Number of tests to be optimized is zero. One of the financials is not configured. Report locking error. Error to get selected field index. Probability field value exceeds 1.0. Invalid field. No probability field is selected. No treatment is chosen. Command not allowed in Reader mode Custom macros internal error. The Custom Macro expression type is not specified. The custom macro name is empty. The Custom Macro expression is missing. Custom Macro unknown function tag. Stored field internal error. No variable name is specified. No expression is specified. There is already a stored derived field of the same name. Stored field unknown function tag. List box selection error Too many items selected 467
E - Error Codes
Code 14903 14905 14906 14907 14908 14909 14912 14913 14914 15101 15201 15202 15203 15204 15301 15501 15502 15503 15504 15701 15702 468
Error Description No items selected Selection not found Unrecognized tree view operation No cost information selected Dialog initialization error Specified cell name (process name + output cell name) is too long Creative ID may only contain alphanumerics and underscore Output Cell Names not unique. Overwrite current info? Dialog initialization error List box selection error Dialog initialization error Specified cell name (process name + output cell name) is too long Invalid cell size limit. Dialog initialization error String not found Minimum rate > maximum rate Dialog initialization error Invalid output cell name Dialog initialization error Specified cell name (process name + output cell name) is too long IBM Unica Campaign - Administrator's Guide
Code 15801 15802 15803 15804 15805 15901 15903 15904 15905 15906 15907 15908 16001 16002 16051 16053 16054 16055 16056 16101 16102 Version 8.5.0
Error Description Selected string not found Tree expansion error Dialog initialization error Segment name not specified Segment names can not be specified Selected string not found Dialog initialization error Specified cell name (process name + output cell name) is too long List box selection error Invalid cell/record size limit. Existing expression based on tables and fields will be lost. Existing criteria based on dimension hierarchy will be lost. Dialog initialization error No list box selection found Stored trigger internal error. The trigger name is empty. The trigger command is empty. There is already a trigger defined under the same name. Stored trigger unknown function tag. Selection error Multiple selection error 469
E - Error Codes
Code 16103 16104 16105 16106 16201 16202 16203 16302 16303 16304 16305 16306 16400 16401 16402 16403 16404 16405 16406 16407 16408 470
Error Description No items selected Selection style error Selection not found Dialog initialization error Dialog initialization error ListBox selection error Specified cell name (process name + output cell name) is too long Source table is not yet mapped. DimensionInfo Internal Error: Unknown Function. DimensionInfo Internal Error. Illegal number of levels. Required field missing in source table. It needs to be remapped. No data base source defined No table selected Internal Error: no table manager Bad Campaign Table index Internal Error Internal Error: New Table Unknown function No file name specified No data dictionary specified The selected table has no defined fields IBM Unica Campaign - Administrator's Guide
Code 16409 16410 16411 16412 16413 16414 16415 16416 16417 16418 16419 16420 16421 16422 16423 16424 16425 16426 16427 16428
Error Description Internal Error: No table created No name specified for new table Need a user name and password for the database The database type is not currently supported Table is not a base table -- no relations allowed Bad field index Record table ID not specified Internal Error: No dimension table with this name Table is not a dimension or general table Internal Error: No base table with this name Entry point not valid for this operation Mapping to an existing table not valid for this operation Error creating new Flat File Error - no file/table option selected Error - no database selected Error - table selected is invalid Error - bad key field index Error - blank key field name Error - Table Name is duplicate or invalid Field name must begin with a letter and may only contain alphanumerics and underscore
Version 8.5.0
471
E - Error Codes
Error Description Dimension table ID not specified Duplicate field names specified Table name must begin with a letter and may only contain alphanumerics and underscore Error - Dimension Name is duplicate or invalid Error - Folder not found Derived field internal error. Derived field unknown function tag error. Derived field not exist. Derived field report locking error. Derived field table locking error. Derived field cell locking error. Derived field already exists. Derived field getting all field information error. Internal Error. The authorized process's schedule period has expired. Selected string not found Parent window not found Filename not specified No fields selected Dialog initialization error
16432 16433 16501 16503 16504 16505 16506 16507 16508 16509 16601 16603 16701 16702 16703 16704 16705
472
Code 16706 16707 16708 16709 16710 16711 16712 16713 16714 16715 16716 16717
Error Description Specified Source File does not exist Remapping system table - are you sure? Overwrite old definition? Syntax check OK Discard changes to current expression? Specified Dictionary File does not exist Derived variable name not specified Query name not specified Trigger name not specified No field selected Illegal field name Invalid name: name must begin with a letter and must contain only alphanumerics or '_' Remove entry? Remove folder? All folder information (sub-folders etc.) will be lost. Name not specified Invalid Data Dictionary file. It may be a directory. Data Dictionary file exists. Do you want to overwrite it? File Not Found Overwrite Existing File? Audience level not specified
Version 8.5.0
473
E - Error Codes
Code 16726 16727 16728 16729 16730 16731 16732 16733 16734 16735 16736 16737 16738 16739 16740 16741
Error Description Audience ID Field(s) not specified Duplicate Audience ID Fields Invalid run state - operation will be terminated No table(s) selected No cell(s) selected Selected tables have different audience levels Selected cells have different audience levels Audience level is already defined as the table's primary audience Audience level is already defined for this table Base Table's related fields not compatible with Dimension Table's key fields The file path length has exceeded the allowed limit No fields are checked Table or field name not specified Derived variable name conflicts with Campaign Generated Field Required value missing. Unable to translate existing expression for Point & Click mode. Restart with empty expression? Unable to translate expression for Point & Click mode. Switch to Text Builder mode? Current expression is not valid. Switch to Text Builder mode anyway? Tree expansion error Folder already exists.
16742
474
Error Description About to execute trigger command. Are you sure? Derived variable name conflicts with an existing Persistent Derived Field No delimiter is specified. No derived variable name has been specified. Selected segments have different audience levels Illegal field name. User Variable values may only be set in a Select process The full name is too long. An administrator must define at least one audience level before a new table can be created. Remap of Optimized List table is not permitted. Audience ID Field not compatible: type mismatch. Output cell name is too long. Process name is too long. Output cell name is empty. Security policy not specified. Security policy is restored to the original policy. Start or end date missing. Invalid date specification. No dates selected. End date cannot be earlier than start date. Data Packaging internal error.
16755 16756 16757 16758 16759 16760 16761 16762 16763 16764 16765 16769
Version 8.5.0
475
E - Error Codes
Error Description Package name not specified. View Log permission is required to access log entries. Dictionary file name cannot be the same as data file name. Data Package folder already exists. Existing content within that folder will be deleted. Stored template internal error. The template name is empty. Stored template unknown function tag. Templates directory does not exist. Templates directory is invalid. There is already a stored template of the same name. Stored catalog internal error. The catalog name is empty. Stored catalog unknown function tag. Catalogs directory does not exist. Catalogs directory is invalid. The catalog file extension is invalid. Only 'cat' and 'xml' are allowed. Target catalog file extension is not same as original. Campaign Data Folder Identifier is empty. Campaign Data Folder Path is empty. Duplicate Identifiers in Campaign Data Folders.
16901 16903 16906 16908 16909 16910 17001 17003 17006 17008 17009 17012 17013 17014 17015 17016
476
Error Description There is already a stored catalog of the same name. Catalog name conflicts with an existing catalog on another security policy. Please choose a different name. Group process internal error. No input is selected. No audience is chosen. No query string. No filter query string. No based-on function is chosen. No based-on field is chosen. No level is selected. No count operator is chosen. Group process cell locking error. Group process unknown function tag. Group process report locking error. The chosen audience is not in the selected table. An invalid audience level is chosen. Unknown parameter for Audience Process. Command not allowed in Reader mode List box selection error Dialog initialization error
17101 17102 17103 17104 17105 17106 17107 17108 17109 17110 17112 17113 17114 17115 17116 17117 17201 17202
Version 8.5.0
477
E - Error Codes
Code 17203 17204 17205 17302 17303 17304 17306 17307 17308 17309 17310 17311 17312 17313 17314 17315 17316 17317 17318 17319 17321 478
Error Description Tree expansion error Combo box insertion error Invalid cell size limit. Optimize process internal error. Optimize process cell locking error. Optimize process table locking error. Optimize process unknown function tag error. Optimize process report locking error. No input is selected. No fields are selected for export. Invalid field name. String conversion error. Selected input cells have different audience levels. Empty or Duplicate Cell Codes. Proposed contact table is not defined in selected ACO session. DB source is not defined in selected UO session. Required field is missing from proposed contact table. Selected UO session is currently running. Database authentication required. No UO session is selected. Contact Date is invalid. IBM Unica Campaign - Administrator's Guide
Code 17322 17323 17324 17325 17326 17327 17328 17329 17330 17331 17332 17333 17334
Error Description Contact Date is expired. Command not allowed in Reader mode Selected offer not found. Channel not found for selected offer. Cell is missing offer assignment. Internal Error: Offer is missing. Internal Error: Channel is missing. Score field is not specified. Missing or retired Offer or Offer List detected. Tried to run flowchart while associated UO session was running. Failed while trying to write to the proposed attribute table. One or more export field is unmapped. Tried to delete optimize process box while associated UO session was running. Selection error Selection not found CreateSeg process internal error. CreateSeg process cell locking error. CreateSeg process unknown function tag. No input is selected. Segment name not unique within the specified folder.
Version 8.5.0
479
E - Error Codes
Code 17407 17408 17409 17410 17411 17412 17413 17452 17502 17503 17504 17505 17507 17509 17510 17511 17512 17513 17514 17515 17516
Error Description Segment name not specified. Invalid segment name. Invalid security policy. Security policy not specified. Selected input cells have different audience levels. Bin file creation is OFF and No Temp Table DS is specified. Invalid Data Source Name for Segment Temp Tables Segment name not specified Internal error. Cell locking error Table locking error. Unknown function tag error. Report locking error. No input is selected. Fulfillment page: No export table is selected. Personalization page: No export fields are chosen. Log page: No table is chosen to log contacts. Log page: No fields are chosen to log contacts. Getting cell field infomation error. No trigger is specified. Personalization page: no sort field is chosen.
480
Code 17518 17519 17521 17522 17523 17524 17525 17526 17527 17528
Error Description Invalid field name. Double to string conversion error. Fulfillment page: No export file is chosen. Contact list page: No delimiter is specified. Fulfillment page: No export dictionary file is chosen. Log page: No file is chosen to log contacts. Log page: No delimiter is specified for contacts. Log page: No dictionary file is specified for contacts. Fulfillment Page: Selected Data Export Filename contains Invalid Path Fulfillment Page: Selected Data Dictionary for Export File contains an Invalid Path. Personalization Page: No skip duplicate field is chosen. Fulfillment Page: Update Records require a base table with audience same as input. Log Page Contact: Update Records require a base table with audience same as input. Selected input cells have different audience levels. Empty or Duplicate Cell Codes. Log page: No skip duplicate field is chosen. Fulfillment page: Selected Data Dictionary File does not exist. Offer codes are not unique. Command not allowed in Reader mode
17529 17530
17531
Version 8.5.0
481
E - Error Codes
Code 17540 17541 17542 17544 17549 17550 17552 17553 17554 17555
Error Description Invalid Offer ID in eMessage Document Empty audience level. No offers are selected. Cell is missing offer assignment. Error returned from eMessage server during run. Internal error: unknown eMessage status. List box selection error Selection not found Offer name or code is empty. The specified records are cleared from Contact History, Detailed Contact History, and Treatment tables. You are about to permanently delete ALL contact history entries ever created by this process. Are you sure you want to continue? Invalid expiration duration specified. Document settings updated from eMessage server. Duplicate tracking codes not allowed. Cannot determine tracking audience level. Invalid number of contacts Invalid number of responses Invalid or missing start/end date Start date is later than end date
17557
482
Code 17566
Error Description You are about to permanently delete the selected contact history entries created by this process. Are you sure you want to continue? There are no contact history entries created by this process. Records for this process are cleared from Contact History, Detailed Contact History tables, and Treatment tables. Missing field assignment for document PF. Missing field assignment for offer parameter. Missing field assignment for tracking field. eMessage directory is invalid. Missing field assignment for content type. eMessage is still completing the last operation. Please try again later. No eMessage document selected. Unknown parameter. Invalid parameter. DOM creation error. Multiple cells selected. Assignment rule will apply to all selected cells. Internal Error: Offer is missing. Internal Error: Channel is missing. Contact History is tracked at a different audience level. All audience ID fields must be specified. No output queue selected. Output queue not found.
17567 17568
17570 17571 17572 17573 17574 17575 17576 17577 17578 17579 17580 17581 17582 17583
17584 17585
Version 8.5.0
483
E - Error Codes
Error Description Required field not found in output queue. Log page: Contact History Table is not yet defined for this audience level. Output page advanced settings: Contact History Table is not yet defined for this audience level. Output page advanced settings: Response History Table is not yet defined for this audience level. A new offer parameter name has been added to one of the offer URLs since the process box was configured. You must map a field to this offer parameter before you can begin the run. The process box needs to be reconfigured due to a Personalization Field change in the eMessage document. Missing or retired Offer or Offer List detected. Assigned Offer List does not contain any offers. Cannot clear contact history. Response history exists for the selected treatments. No contact history records found. Contact history exists for current run. History must be cleared before starting branch or process run. Specified contact status code is not defined in the system. Duplicate field names. Output table cannot be created. Response process internal error. Response process cell locking error. Response process table locking error. Response process unknown function tag error. Response process report locking error.
17589
17590
17591
17596 17597
484
Code 17608 17611 17613 17614 17615 17616 17617 17618 17620 17621 17622 17623 17624 17625 17626 17627 17628 17629 17630 17631 17632 Version 8.5.0
Error Description Response process getting cell field infomation error. Double to string conversion error. Empty audience level. No input is selected. Selected input cells have different audience levels. No offers selected. One or more offers are missing cell assignments. Offer Code Field is missing. Campaign Code Field is missing. Cell Code Field is missing. Channel Code Field is missing. Product ID Field is missing. No table is chosen to log for other destination. Update Records require a base table with audience same as tracking. No file is chosen to log for other destination. No delimiter is specified for logging to delimited file. No dictionary file is specified for logging. No fields are chosen to log for other destination. Invalid field name. Offer with selected response type is already added in this process. Response type(s) not specified. 485
E - Error Codes
Code 17633 17634 17635 17636 17637 17638 17639 17640 17641
Error Description Response channel is not specified. Response date field is not a date type field. Response date value is not in the specified format. No offer is selected Internal Error: Offer not found. Internal Error: Contact channel not found. Internal Error: Campaign not found. Offer field must be specified to track all incoming responses. When tracking at a different audience level from the input cell, all audience ID fields must be specified under 'Additional Fields' in the Log tab. Default response type not found in the User Response Type Table Default contact status not found in the Contact Status Table No treatment mapping specified. List box selection error Response name is empty Records for this Process are cleared from Response History and Tracking tables. About to clear Response History and Tracking table records for this Process. Are you sure? Response channel is not specified. Records for this Process are cleared from Contact History and Tracking tables. About to clear Contact History and Tracking table records for this Process. Are you sure?
17655
486
Code 17659
Error Description Contact History is tracked at a different audience level. All audience ID fields must be specified. Cube process internal error. Cube process cell locking error. Cube process unknown function tag. No input cell or segment. Segment name not unique. No output cube specified. Dimension no longer exists. Selected Segment is based on an unknown audience level. Report locking error. Invalid field name. Cube name is missing. There are no dimensions available. There are no dimensions specified for this cube. Invalid configuration: duplicate dimensions selected. Error formatting date for display. Error parsing user input date. Error formatting currency value for display. Error parsing user input currency value. Error formatting number for display.
17702 17703 17704 17705 17706 17713 17714 17715 17717 17718 17752 17753 17754 17755 17800 17801 17802 17803 17804
Version 8.5.0
487
E - Error Codes
Code 17805 17806 17807 17808 19000 19001 19002 19003 19005 19006 19007 19010 19011 19013 19014 19015 19016 19018
Error Description Error parsing user input number. Error formatting time for display. Client Stored List Internal Error. Error formatting datetime for display. Internal Error: Unknown function tag. Memory error DOM exception Pipe open error End date specified is earlier than start date Invalid Report name Invalid Attribute name Invalid character(s) were found in a Numeric Field. Segment is in use. Can not modify. Invalid cube specification Invalid Effective Date Invalid Expiration Date Expiration Date specified is earlier than Effective Date Folder names must be unique within the same folder. The specified folder name already exists in this folder. Cannot remove folder: folder contents (files/subfolders) must first be removed. Folder contains in use segment(s). Can not move.
19019 19020
488
Error Description Can not delete. Can not move. Folder contains active segment(s). Can not delete. Folder contains inactive segment(s). Can not delete. No destination folder was selected. Please select a destination folder and retry. Invalid folder ID specified. Session name must be unique within the same folder. The specified session name already exists in this folder. Cannot move Campaign/Session because it contains an active Flowchart. Cannot move. Move will result in duplicate segment names in destination folder. An object having the destination name already exists. Process internal error. String conversion error. Selected UO session not found. Internal Error: Unknown function tag. DOM exception Pipe open error Offer code not unique End date specified is earlier than start date Invalid Report name Invalid Attribute name
19028 19029
19030 19500 19501 19502 20000 20002 20003 20004 20005 20006 20007
Version 8.5.0
489
E - Error Codes
Code 20008 20009 20010 20011 20012 20013 20014 20015 20016 20017 20018
Error Description Offer is used. Can not delete. Folder contains used offer(s). Can not delete. Invalid character(s) were found in a Numeric Field. Segment is in use. Can not modify. Offer version name not unique Invalid cube specification Invalid Effective Date Invalid Expiration Date Expiration Date specified is earlier than Effective Date Offer version code not unique Folder names must be unique within the same folder. The specified folder name already exists in this folder. Cannot remove folder: folder contents (files/subfolders) must first be removed. Folder contains in use segment(s). Can not move. Can not delete. Can not move. Folder contains active segment(s). Can not delete. Folder contains inactive segment(s). Can not delete.
490