New features and changes in version 10.0

Upgrade paths

Because version 10.0 is a major release, you can upgrade from 8.6.x, 9.0.x, or 9.1.x. For instructions, see the IBM Campaign Upgrade Guide.

Enhanced user interface for Marketing Platform, Campaign, Interact, and Contact Optimization

This release updates the user interface so that it is easy to use, offers a clean, modern design, and delivers improved inline text and error messages. The new look does not change how the product works, and you can get updated documentation from the Help menu.

Context-sensitive help for Configuration properties

When you view configuration properties under Settings > Configuration, you can choose Help > Help for this page to display context-sensitive help. For example, if you request help for the Campaign | caching page, you see a help topic that specifically describes all of the caching options. You must have an internet connection to use this feature.

EMM files and directories renamed to IMS

Files and folders that included "EMM" have been changed to IMS. For example, the default top-level directory is now C:\IBM\IMS and the names of the installers are IBM_Marketing_Software_Installer_10.0.0.0_linux.bin, IBM_Marketing_Software_Installer_10.0.0.0.sh, and IBM_Marketing_Software_Installer_10.0.0.0_win.exe.

Integration with IBM Engage in the IBM Marketing Cloud

IBM Campaign v10.0 can be integrated with IBM Engage in the IBM Marketing Cloud. IBM Engage provides digital marketing and lead management solutions incorporating email, SMS, and mobile push, along with embedded analytics. The integration provides digital marketers with the ability to personalize and track each customer interaction, communicate over multiple channels, and protect sensitive personal data. Marketers can use the IBM Campaign segmentation capabilities together with IBM Engage to target specific audiences, personalize communications, and reach customers through email, SMS text messaging, and mobile push campaigns. For details, see the IBM Campaign and Engage Integration Guide for IBM Marketing Cloud.

Integration with IBM Journey Designer

IBM Campaign customers can now use IBM Journey Designer to design and view high-level journey maps to empathetically understand the messaging and touchpoints that their customers go through. IBM Campaign users can use Journey Designer to strategically plan out the ideal customer journey and the different interactions that happen across that journey. As you create journeys, you can link a particular interaction to an existing campaign, assign requests to a particular user to execute and collaborate on what needs to be included in that particular campaign. For information, see the separate Journey Designer documentation.

Advanced search for campaigns, sessions, offers, segments (181352, 211268)

You can search for flowcharts and flowchart-related objects, including names of process boxes, configuration details, descriptions, owners, user variables, user database tables, segments, associated offers, and any other objects that are stored in campaign session files (.ses).

1. Go to any of the following locations:
   • The All campaigns page
   • The All sessions page
   • Any flowchart tab in View mode
2. Click Search flowcharts.

When you do a search, all flowcharts in all campaigns in the current partition are searched. Searching is not case-sensitive. Currently, the search results persist until you explicitly clear the results. For more information, see the IBM Campaign User's Guide.

Make flowcharts searchable by indexing the .ses file

Existing indexes are not updated automatically. To ensure accurate search results, follow these guidelines:

1. Run advSrchUtil immediately after upgrading IBM Campaign, to index all existing flowcharts in a partition.
2. Run advSrchUtil periodically to create or update search indexes on all flowcharts in a partition.
3. If you want to affect just a single flowchart, run the unica_acsesutil session utility with the -J option.

When advSrchUtil runs for the first time, it processes all flowcharts in the given partition by serializing them into JSON and indexing them.

The next time advSrchUtil runs, it processes only the flowcharts that were modified or added since the last run.

For this reason, the first run takes longer than subsequent runs. A very large flowchart can take several minutes to process, so if there are many flowcharts the tool may take a long time to finish. Best practice is to run the tool regularly. For example, if you typically add or modify hundreds of flowcharts per week, consider running the tool twice a week.

The following examples summarize how to run the commands. For complete information, see the IBM Campaign Administrator's Guide.

• Unix/Linux: <Campaign_Home>/bin/advSrchUtil.sh <partition> <campaignSharedHome if clustered>
• Windows: <Campaign_Home>\bin\advSrchUtil.bat <partition> <campaignSharedHome if clustered>

The utility interactively prompts for a user name and password that has permission to access all of the flowcharts in the given partition. The campaignSharedHome is required only if the IBM Campaign listener is clustered.

• unica_acsesutil -s <Flowchart ses file> -h <partition_name> -J -o <output_file_or_directory_path> -y <user_id> -z <password>. You must include -s to indicate the session file. The options -y and -z are optional; if you omit them, the tool prompts for user ID and password. All options are case-sensitive.

GSKit replaces OpenSSL as the cryptography standard. (Epic 130497, Story 199501, Task 211566)

Hortonworks ODBC driver support (211291)

The Apache Hortonworks 64-bit ODBC driver for HDP 2.3 (v2.0.5) is now supported as a driver for Hive-based Hadoop big data (user data sources only).

New environment variable for listener script: STALE_CONN_TIMEOUT (204453)

A new environment variable, STALE_CONN_TIMEOUT, is available for the listener script file for IBM Campaign and Contact Optimization. The listener script file is rc.unica_ac/cmpServer.bat (for Campaign) and ACOServer.sh/.bat (for Contact Optimization), located in <CAMPAIGN_HOME>\bin.

The STALE_CONN_TIMEOUT variable was introduced to enable long-running campaigns to continue without losing connection to the back-end database. If a connection is idle for the number of seconds defined, the connection will be re-opened. For example: STALE_CONN_TIMEOUT=<seconds>. If you add or change this environment variable, you must restart the listener. If a connection is lost, the following debug message appears in the Campaign flowchart or Contact Optimization server log file: [DB QUERY] Connection is stale, so re-opening DB connection.

Hive ODBC.ini file requires additional parameter GetTablesWithQuery=1 (206508)

If you are using a Hive-based Hadoop big data source as a user database, the ODBC.ini file for your Hive ODBC driver must include the line GetTablesWithQuery=1. This line is necessary to address a Hive limitation of the GetTables ODBC API. Omitting this line can result in a connection timeout error for the Hive Hadoop datasource. This change applies to all Hive ODBC drivers. For more information, see the IBM Campaign Installation Guide.

New configuration property in Teradata data source template: UseGroupByForDistinct

A new property, Campaign|partitions|partition[n]|dataSources|dataSourcename| UseGroupByForDistinct, was added to the Teradata datasource template. By default, this property is FALSE. When this property is enabled, <select query> uses a GROUP BY statement instead of DISTINCT.

The reason for this addition: Flowcharts execute the query "select DISTINCT <audience id> from <table>" to fetch unique records when a table is not mapped as a normalized table in IBM Campaign. When such queries are submitted against Teradata, it causes additional sorting of data on the database and high CPU consumption. The Teradata DBA recommendation is to use GROUP BY instead of DISTINCT, because GROUP BY can take advantage of Teradata multi AMP processing architecture.

New configuration property: cacheSystemDSQueries

A new configuration property, Campaign|partitions|partition[n]|server|optimization|cacheSystemDSQueries, was added to improve performance. When set to TRUE, this property reduces multiple execution of queries on the IBM Campaign system tables by caching the query results. When set to FALSE, query results are not cached. The default value is TRUE.

Ability to enable trace logging in unica_aclsnr.log for diagnostic purposes

You can enable trace logging for diagnostic purposes, when working with IBM Support. When you enable trace logging, trace events are written to both the listener log unica_aclsnr.log and the flowchart log <flowchart>.log. Trace events are identified in the log file by [T].

To enable trace logging:

1. Add the following entry to the setenv.sh or setenv.bat file: UNICA_ACTRACE=Trace
2. Restart the listener.

Web application clustering Suite-wide

Previously, Web application clustering was supported only for stand-alone Campaign. Now, web application clustering is supported for IBM Campaign along with other integrated products in the Suite. For example, if Campaign is deployed in a web application cluster then the user can configure IBM Marketing Platform, Contact Optimization, Marketing Operations, or eMessage in the same web application cluster. Even though Interact does not support web application clustering, it can also be configured with the IBM Campaign application deployed in a web application server cluster. Only Sticky sessions are supported. No session replication is done, as the focus is on scalability. Failover is not implemented.

Performance enhancement (195323)

For Campaign+Marketing Operations integrated environments, performance has been improved on Save and Exit Flowchart.

New option during installation to create a system table data source connection in the web application server

You can allow the installer to create the connection to the Campaign system tables in the web application server. To enable automatic data source creation during installation, on the Datasource Creation panel, select the Create Campaign Datasource check box and supply information about your application server.

• The installer creates the data source using campaignPartition1DS as the JNDI name.
• The installer creates the data source connection for one partition only. If you have multiple partitions, you must create additional connections manually.
• Note that, if you are using WebLogic, you must add the JDBC driver to your web application server classpath manually even if you allow the installer to create the data source. The installer does this automatically for WebSphere.