IBM Support

IBM Unica Campaign 8.6.0 Fixes

Downloadable files


This page shows the fixes for IBM Unica Campaign.

Download Description

Product: IBM Unica Campaign
Version: Fix Pack GA Release
Date: August 17, 2015
Installation Instructions Files Included Installers Appendix A

  1. The OpenSSL library is upgraded to version 1.0.2d.
  2. If SSL is already configured and you are applying Campaign FP, you must disable SSLv3.0 support on WebSphere or WebLogic by applying the required patch or configuration for the application server. For details, see Section III, Task 3 - SSL Configuration below.

**Without the application server patch or configuration, SSL will stop working**

Security Fixes
  1. The OpenSSL library is upgraded to version 1.0.2d.

List of Fixes

(APAR PO04078, DEF 175123)
Copying text from within Oracle SQL Developer that contains an ASCII character and pasting it into a flowchart name was disallowing access to the folder in which the flowchart resides. This issue has been fixed.

(APAR PO03713, DEF 168430)
In certain scenarios, null values were handled inconsistently in Derived Fields using If-Else statement in the Derived Field. This has issue been fixed.

(APAR PO05216, DEF 196792)
A single process downstream from Extract was failing with an error that the table or view does not exist. This occurred if the Extract process was configured to take input from multiple data sources that pointed to the same DSN. This issue has been fixed.

(APAR PO04541, DEF 182192)
Syntax check was failing for Derived field expression created using Persistent Derived field for French locale. This issue has been fixed.

(APAR PO05256, DEF 197883)
10404 errors were seen while editing certain flowcharts. This issue has been fixed.

Known Issues
  1. Camapign listener crashes with error 10404 if user tries to save campaign having an invalid xml character it its Name field.
  2. While editing flowchart 'Name' from 'Properties' dialogue on Windows OS, if you enter an invalid xml character in Name field and try to save a flowchart, it shows 'Error 773 Access Denied' followed by Javascript error. On Unix, it shows invalid XML character error and blocks the access to the folder in which flowchart resides.
  3. (APAR PO05144, DEF 195071)
    Maillist process in IBM Campaign flowchart keeps waiting for synchronous trigger to complete though the script has completed. This happens on AIX OS when trigger process executes and exits in fraction of a second. This issue can be handled by putting wait of 1 second (sleep 1) in trigger process. No fix is required on Campaign server process.
  4. The log location of IBM Campaign and flowchart logs can be controlled by using the "allowCustomLogPath" configuration property. However, if the "logToSeparateFiles" parameter is turned on, the custom log path is not used for flowchart runs initiated from Distributed Marketing. In this scenario, flowchart logs are written to the default logging directory:
    CAMPAIGN_HOME\partitions\partition<n>\logs only.
  5. When you run some IBM Campaign reports, the IBM Cognos RQP-DEF-0177 error occurs. This error occurs with the Oracle patch version only. To resolve the issue, apply Oracle patch or higher.
    Published Technote Reference # 1692260

Issues fixed in previous fix packs on 8.6.0, included in this release

Note: Release Notes from Campaign 8.6.0 still apply to this fix pack release.

Fix Pack

(APAR PO03965, Defect 172827)
If a scheduled flowchart failed, two rows for the flowchart failed state appeared on Monitoring page when the flowchart was accessed before reaching the Monitoring page. This issue is fixed. Now there is now only a single row for a flowchart failed state.

(APAR PO04717, Defect 185793)
Error “11506 Selected table is invalid or corrupted” was reported when data was added to the OLT table from a Teradata table mapped as a dimension table. This issue is fixed.

(DEFECT 190668)
Performance degradation was observed while opening an Extract process box when eMessageInstalled = yes with millions of records in the UCC_ResponseAttr table. This issue is fixed. Now, records from UCC_ResponseAttr are not fetched while opening the Extract process. Records are fetched when the user selects the "eMessage Landing Pages" option in an Extract process.

Fix Pack

(APAR PO03528, DEF 164692)
The Detail column on the Scheduler run page was not properly displaying Unicode characters on successful completion of a schedule. This issue has been fixed.

(APAR PO03507, DEF 164383)
The Campaign monitoring page was not properly displaying flowchart names containing Unicode characters. This issue has been fixed.

(APAR PO04481 , DEF 181666)
Schedules created by a user remained active even after the user was disabled in IBM Marketing Platform. This issue has been fixed.

(APAR PO04114, DEF 175767)
Users were able to run trigger through flowchart even if 'Run Triggers' permission was Denied. This issue has been fixed.

(APAR PO04047, DEF 174315)
While re-running a Snapshot process box configured to export to an Extract table, a unique constraint violation was observed on the target-cell system table's ID field. This issue was fixed by regenerating ID fields if not found.

(APAR PO04497,DEF 181926)
The error "Campaign thwarted a potential cross-site request forgery (CSRF) attack. The user will be logged out of the system" was displayed while moving a campaign to another location from the search results for Campaigns. This issue has been fixed.

(APAR PO04720, DEF 185610)
After upgrading to IBM Campaign, when a user scheduled a flowchart whose details contained French characters, the flowchart failed to execute. This was because the French characters were garbled in the Scheduler window. This issue has been fixed.

OpenSSL is vulnerable to a denial of service, caused by a memory leak when handling failed session ticket integrity checks. By sending an overly large number of invalid session tickets, an attacker could exploit this vulnerability to exhaust all available memory of an SSL/TLS or DTLS server.

Fix Pack

(APAR PO04081, DEF 175200)
User was unable to access flowchart run logs for flowcharts having names containing special characters from UI. This issue has been fixed.

(DEF 176278)
Fixed width file exported using existing DCT file contained only one record. This issue has been fixed.

(APAR PO04095, DEF 175445)
Flowchart crash with error 10404 was observed while unmapping and remapping dimension and base tables. This issue has been fixed.

(PMR 176523, DEF 178405)
Performance degradation was observed during flowchart runs as a result of temp tables not being created for top level process boxes. This issue has been fixed.

(PMR 159559, DEF 159793)
An additional comma was being added while exporting fields to a mapped table or file in Snapshot and Mail List process boxes. This issue has been fixed.

(PMR 133343, DEF 168214)
Validation takes a long while to complete after clicking "Save and run flowchart" causing delay in flowchart run.
This issue has been fixed.

(APAR PO04253, DEF 177912)
User was unable to edit campaign session flowcharts directly from search results. This issue has been fixed.

(APAR PO04158, DEF 176457)
Scheduled flowcharts with expired schedule dates were running again after renaming the flowcharts. This issue has been fixed.

(APAR PO03806, DEF 169803)
Error 703 File Read Error was observed if Save or Save and Exit was performed while the MERGE, SAMPLE, or SEGMENT processes were running for a very long time.
This issue has been fixed.

(PMR 176829, DEF 175018)
”12608:INTERNAL ERROR: Invalid field specified” error was displayed while profiling dimension table fields. This has been fixed.

(PMR 165047, DEF 166140)
On renaming an offer, changes were not reflected in the Parameters tab of Mail List and Call List process boxes causing issues while running the flowchart through Unica Distributed Marketing. This issue has been fixed.

Additional steps required to run flowcharts, which contain renamed offers, through Unica Distributed Marketing:
  1. Once the offer name has been changed, update the process configuration of all the MailList process boxes which have the renamed offer assigned in Treatment tab by opening the process box and clicking OK. This will ensure that the modified offer name is saved in process box configuration.
  2. Save and publish flowcharts containing the MailList process boxes.
  3. Republish saved flowcharts in Unica Distributed Marketing.

(ENH 157339)
While using control datasource parameters, specific to DB2, for example, DB2NotLoggedInitiallyUserTables set to TRUE and at the same time using SuffixOnInsertSQL set to "with UR" to control isolation level, the SuffixOnInsertSQL was not taken into account. This issue has been fixed. Now Campaign generates separate queries for datasource parameters DB2NotLoggedInitiallyUserTables and SuffixOnInsertSQL for DB2 database.

Fix Pack

(ENH 120974)
Earlier, logs for flowcharts run from Distributed Marketing were written only to a single log file per flowchart under the IBM Campaign flowchart logs directory. This used to result in logs for multiple, simultaneous flowchart runs getting mixed together. To address this issue, the flowchart logs for multiple runs of individual flowcharts was split.

1. A new configuration parameter "logToSeparateFiles" is added under the "Affinium|Campaign|partitions|partition1|server|collaborate" node in the Platform configuration. By default, this parameter is not added to the configuration. To add this parameter, follow the steps in Appendix A below.
2. If the logToSeparateFiles parameter is turned on, flowchart logs for runs initiated from Distributed Marketing are logged to separate log files.
3. Log files are created under folders with the current date so that there are no excessive log files under a single folder. The format of the folder name is "FlowchartRunLogs_<YYYYMMDD>".
4. The format of the log file name is: <CAMP_NAME>_<CAMP_CODE>_<FC_NAME>_<PID>_<LIST_CODE>_<DATE>_<TIMESTAMP>.log
This ensures that each flowchart run is logged to a separate log file. The date format is "YYYYMMDD". The timeStamp format is "HHMMSS".
PID is the IBM Campaign server process ID, which runs the flowchart, and LIST_CODE is the object code of a Distributed Marketing list, ONDC, or Corporate Campaign from which the flowchart is run.
5. All of the user variables passed to a flowchart run process are logged in the log file for troubleshooting purposes.
6. If logToSeparateFiles is False, flowchart logging behaves as it is working currently.
7. Note that the campaign does not have all the necessary details when the flowchart is opened. Therefore, when the flowchart is opened, it will initially log to the traditional flowchart log file. When the flowchart receives a message to run, and if it is a Distributed Marketing run and the value of the property logToSeparateFiles is set to TRUE, logging will switch over to the new directory and file at that time.

(Defect 168714)
The flowcharts, upgraded from 7.5 to 8.6 for locale which have COMMA as decimal separator, and had derived field with macro "FORMAT" and "Substr " were failing upon execution due to bad syntax check. This has been fixed.

(Defect 158002)
In Maillist process box, "Skip Records with Duplicate IDs" was greyed out when "Enable Export To" option on fulfilment tab was unchecked. This has been fixed. Now, by Default "More" Button will be enabled and not linked to "Enable Export To" check box on fullfilment tab of Maillist process.

(APAR PO03679, Defect 167875)
CSRF error was seen on the eMessage mailing tab. This has been fixed.

(APAR PO03513, Defect 164482)
When table mapping with multiple dimensions hierarchies was used in a flowchart and one of base table was selected as input, opening of that flowchart process box took a long time. This has been fixed.

(APAR PO03052, Defect 157079)
Saving a flowchart name longer than 64 characters was previously allowed which caused errors when re-opening the template. Now you cannot save a template with a name that is longer than 64 characters.

(Defect 165065)
Error 10404 was seen in flowcharts when using global suppression on strategic segments and In-DB optimization was enabled. This has been fixed.

(APAR PO02199, Defect 130527)
Custom cell attributes were not ordered by Attribute Name on the Target Cells tab. This has been fixed. Now, Custom cell attributes will be ordered by Attribute Display Name.

Apache Struts could allow a remote attacker to execute arbitrary code on the system, caused by the failure to restrict the setting of Class Loader attributes. An attacker could exploit this vulnerability using the class
parameter of an ActionForm object to manipulate the ClassLoader and execute arbitrary code on the system. This could cause a partial impact to confidentiality, integrity, and availability. This issue has been fixed now.

Apache Commons FileUpload and Tomcat are vulnerable to a denial of service, caused by the improper handling of Content-Type HTTP header for multi-part requests. By sending a specially-crafted request, an attacker could exploit this vulnerability to cause the application to enter into an infinite loop. This issue has been fixed by incorporating newer version of the affected libraries.

Fix Pack

(APAR PO02130, Defect 129688)
When a flowchart run was started through the Scheduler or unica_svradm, a thread synchronization issue resulted in sporadic configuration-related errors. This has been resolved.

(APAR PO03015, Defect 156636)
The SQL used by MailList to clean up Contact History records was slow. To address this DEF in Campaign, MailList's default behavior has been changed to use EXISTS/ NOT EXISTS when deleting from UA_OfferHistAttrib and updating UA_OfferHistory while removing Contact History records (either after a failed run or in response
to the user's action in the GUI). Previously, MailList used IN / NOT IN. That old behavior can be re-enabled using the new data source property "UseNotInToDeleteCH".

Configuration category: Campaign|partitions|partition[n]|dataSources|dataSourcename

This property affects the IBM Campaign system table data source (UA_SYSTEM_TABLES). It affects the SQL query syntax for how the MailList and CallList processes remove records from the IBM Campaign system tables. 

The default value of FALSE typically improves database performance. The default behavior uses EXISTS / NOT EXISTS when removing Contact History records (either after a failed run or in response to the user's action in the GUI). The removal process involves deleting from UA_OfferHistAttrib and updating UA_OfferHistory.

You can change this value to TRUE if you prefer to use the SQL syntax of IN / NOT IN. Prior versions of IBM Campaign used IN / NOT IN.

Default value: FALSE

Valid Values: TRUE | FALSE

(APAR PO02489, Defect 133127)
CreateSeg inserted an empty or incorrect AudienceName into the UA_Segment table in some scenarios. This has been fixed.

(APAR PO02925, Defect 155708)
When a campaign or session folder is renamed, UA_Folder's UpdateDate field was not getting updated. This has been resolved.

(APAR PO02706, Defect 137006)
When unica_svradm was used to run a flowchart in synchronous mode (the RUN command with the -s option), extended delays in flowchart responses caused Error 1719. This has been resolved.

(APAR PO02388, Defect 131595)
Target Cell Spreadsheet (TCS) cell names were incorrectly labeled as Exact matches when a longer flowchart cell name began with the TCS cell name. Such matches are now correctly labeled Best; or, if only exact matches are allowed, such matches are avoided.

(APAR PO02628, Defect 135178)
Client machines with IE 8.0 and environment configured for SSL were unable to export the IBM Campaign cell reports when the environment was patched up to This has been resolved.

(APAR PO02263, Defect 131047)
When the IBM Campaign Interactive channel being deployed to the IBM Interact Runtime environment contained more than 1000 segments, the error message 'ORA-01795: maximum number of expressions in a list is 1000' used to appear. This has been resolved.

(APAR PO02043, Defect 120946 )
The control cell was not considered in IBM Campaign while extracting offers from Distributed Marketing. This has been resolved.

(APAR PO02251, Defect 130953 )
When IBM Marketing Operations published a blank value for a custom cell attribute, IBM Campaign was discarding the null value and was not updating the UA_CellAttribute table. This has been fixed and is consistent with the IBM Campaign TCS grid behavior.

(ENH 121385, Defect 129890)
Tables mapped with two audience levels resulted in 0 records if certain audience IDs were NULL. This has been resolved.

(APAR 131046, DEF 131047)
If the IBM Campaign Interactive channel being deployed to the IBM Interact Runtime environment contains more than 1000 segments, then the error message 'ORA-01795: maximum number of expressions in a list is 1000' will be raised. This is a standard Oracle error message when there are more than 1000 objects present in the where clause of a SQL statement. This has been fixed.

Fix Pack

(APAR 57942, DEF 57943)
Opening a flowchart in edit mode using Ctrl+click on the flowchart tab used to give an error if the user was viewing another flowchart. This has been resolved.

(APAR 91704, DEF 91706 )
After searching for a campaign, if you clicked the pencil icon in the search results for any campaign and clicked on a flowchart to open it in edit mode, the flowchart did not open. This is fixed.

(APAR 91865, DEF 91866)
A single-quote character (apostrophe) in an entry in the Recent menu (e.g., in a Campaign name) prevented the user from being able to create a flowchart due to a JavaScript error. This is fixed.

(APAR 84182, DEF 84184)
The option to schedule a mailing after scheduling a flowchart was grayed out. Users were unable to schedule a mailing after an already scheduled flowchart run. This has been resolved.

(APAR 74898, DEF 74899)
In the TCS tab of a campaign, the Cell Custom Attribute was not displayed in order of AttributeId in the UA_attributedef table. This has been resolved.

(APAR 66121, DEF 66125)
Distributed Marketing used to receive duplicate cells from Campaign where the cells had contact history. This was because Campaign used to send all of the target cells associated with a flowchart even if they were retired. This happened when cells with contact history were deleted from the flowchart. This caused the DM form to not be able to run the flowchart. This has been resolved.

(APAR 90981, DEF 90983)
Summary tab in Campaign having Interactive Strategy showed 'Error 404:Invalid path was requested' when accessed from a new browser. This is fixed.

(DEF 107016)
When Marketing Operations (UMO) was integrated with IBM Campaign, the selection of the segment/offer tab resulted in a HTTP error message. This is fixed.

(APAR 106617, DEF 103387)
Error 10038 was displayed when an Optimize process box with multiple inputs was Branch run. This is fixed.

(APAR 10510, DEF 10129)
Inconsistent behavior was observed for the parameterize offer attribute for in Post optimization flowchart and without having Post Optimization flowchart. This is now resolved.

(DEF 121948)
Previously, if there was an erroneous message after Campaign/... in the URL, that message was displayed to the user in an error page. This issue is fixed. Now the user sees "Error - 404" message on the web page.

(APAR 131053, DEF 131054)
When SiteMinder was integrated with Campaign, the ActiveX control did not handle Set-Cookie properly. Sometimes it gave 'ERROR 12035: Flowchart control is not compatible'. This is fixed.

(DEF 82692)
When the DB2 compatibility parameter was set on an existing DB2 database while upgrading to eMessage reports, and the data in the database contained some NULL values, the data was not seen in the reports after delta processing. This is fixed.

(DEF 130558)
In eMessage DB2 reports in and later fix packs, link reports show all LP names and all Link names extended by a long string of underscores. This can be fixed by performing some manual actions as listed in the technical note at the following URL:

Fix Pack

(APAR PO00701, DEF 67975)
Long numeric ID fields caused PDFs to become garbled when the ID fields came from a data source using the ODBC Unicode interface. This has been fixed.

(APAR PO01556, DEF 73560)
On the Monitoring page, if users tried to sort by any of the available fields, an error was thrown. This has been resolved.

(APAR PO01428, DEF 71934)
Flowchart processes (unica_acsvr) started by the unica_svradm RESUME command did not preserve the user's locale, instead using the environment's default locale. This has been resolved.

(DEF 67828)
When using HTTPS with WAS 7, ActiveX components were not getting installed or loaded for Campaign on Internet Explorer v8. This has been resolved.

-(APAR PO01302, DEF 66370)
If objects (offers) are moved from one folder to another, security policies were not getting changed accordingly. This has been resolved.

(APAR PO01255, DEF 65977, DEF 72066)
Display and processing issues related to Numeric and Integer User Variables greater than or equal to 1000 were identified and fixed.

(APAR PO00595, DEF 19094)
Campaign used to crash while trying to load a v7.5 XML catalog. This has been resolved.

(APAR PO01114, DEF 57960)
Campaign was unable to load a table catalog whose name contained non-ASCII characters. This has been resolved.

(APAR PO01111, DEF 57896)
The eMessage process box incorrectly invoked a database loader when the number of records selected for production was less than the minReq* property settings and no seed cell was configured. This has been resolved.

(DEF 21026)
Users were not able to use the Extract feature of the Segment process when the Segment process was configured to extract to a data source that converts field names into upper case. This has been resolved.

The eMessage UACE_ExecHistory table has been enhanced to provide details for email subject, sender address, users, and document description. To enable the system to populate this table, users must modify system configuration properties. For more information, see the IBM eMessage System Tables and Data Dictionary
with a publication date of August 16, 2013 or later.

Known Issues:

Note: Release Notes from IBM Unica Campaign 8.6.0 still apply to Fix Pack releases.

Cannot schedule a mailing based on a recurring scheduled flowchart.

This issue occurs in the following scenario:
  1. Create a flowchart that contains an eMessage process box.
  2. Run the flowchart.
  3. Create a mailing and reference the OLT created by the flowchart to the mailing.
  4. Schedule the flowchart. In the "Start at" field, do not change the "now" option. Set recurrences. For example, run the flowchart 10 times every 10 minutes.
  5. In the mailing, click "Schedule this Mailing". In the pop up, the "Schedule this mailing to run after the flowchart run" option does not provide a drop- down list to select the scheduled flowchart. Instead, it says "Flowchart is not scheduled to run".

Important :
After installation of this IBM Unica Campaign Interim Fix, the updated Active-X component will be downloaded to each client machine on first use.

Fix Pack

Campaign would produce incorrect results when the 'Save' button was clicked while a MailList or CallList process box was running. This has been resolved.

APAR PO01101, DEF57069
An offer configured to use the Offer Effective/Expiration Date attributes caused duplicate entries in the UA_OfferHistory table when the Offer Effective Date was set to Flowchart Run Date and the Offer Expiration Date was set to a constant date string. This has been resolved.

APAR PO00331, DEF11065
Campaign's listCampaignsByPage(...) API used to ignore the given attributes. This has been resolved.

APAR PO00716, DEF24065
When an output process was configured to skip records having duplicate IDs, NULL values in derived fields were not handled correctly. This has been resolved.

APAR PO00641, DEF24107
Deleting a Campaign would not delete the contact history data for all Audience levels. This has been fixed.

Previously, the Campaign GUI would trim spaces around parameterized custom offer attribute values. This has been fixed.

APAR PO00252, DEF10247
When Campaign 8.6 was configured for Japanese locale and there was an error while creating an offer (due to an incorrect parameter under offercodegenerator in the configuration), the error message used to appear in English instead of Japanese. This has been fixed.

APAR PO00839, DEF33939
Campaign used to throw an error while creating a linked Campaign with a blank description in a UMO project. This has been resolved.

Campaign creates columns in database tables based on the Display Name configured in the eMessage process. Since Campaign supports some data sources that limit column names to 18 characters, Campaign truncates the Display Name as necessary. However, Campaign was incorrectly truncating to 18 bytes instead of 18 characters.
This has been resolved.

Non-ASCII characters were not correctly displayed in the Windows Event Logs. This has been fixed.

APAR PO01222, DEF50497
Japanese Policy names were not displayed in the Security Policy list in Campaign. This has been resolved.

Campaign's macro syntax check failed to detect some incorrect parenthesis usages. This has been resolved.

APAR PO00914, DEF41848
In some scenarios, MailList substituted incorrect values for <CONTACTLIST> or <CONTACTLOG> tokens when the process was rerun after changing the list or log output settings. In addition, the tokens were not correctly removed when not writing to list or log - they were replaced with the partition path.
These issues have been resolved.

If the Campaign user logged out while in flowchart View mode, the flowchart server process remained active if waitForGracefulDisconnect was set to TRUE. This has been resolved.

APAR PO00073, DEF5771
In an integrated Campaign and UMO environment, if a shared Campaign attribute was created with a display name that exceeded 64 characters and this attribute was used on a form added to a project template, users would be able to create projects with this template. However, an error would occur when "Create Linked Campaign" was selected. This error was not descriptive enough. After this fix, Campaign will return a more meaningful message.

Against the Oracle database, while deleting offers having more than 1000 products associated, Campaign used to throw a database error. This has been fixed.

APAR PO00922, DEF41863
Saving a flowchart containing Extract processes was slow if eMessage was installed, the eMessage response table was mapped in Campaign, and the table contained many records. This has been resolved.

APAR PO00715, DEF 23757
An Extract process configured to have Dimension tables caused downstream Merge processes to select all fields from the Extract table and its Dimension tables. The behavior has been changed as follows: if a single Extract table passes through a Merge process, the Extract and its Dimension relationships will be available to
processes downstream from the Merge process; if multiple Extract tables pass through a Merge process, the Extract tables will be merged as expected, but any Dimension relationships will be lost.

APAR PO00378, DEF 11401
Bulk inserts uploaded skewed text data when the buffer size exceeded data-source-specific maximum widths (e.g. 32000 for Teradata configured with CharacterSet=UTF8). Campaign's table mappings no longer over-allocate text field buffers; note that affected tables must be remapped in order to correct the buffer sizes. This will make it less likely, although not impossible, for the maximum buffer widths to be reached.

APAR PO00847, DEF35207
Delimited files whose contents changed since the last time the number of records was calculated caused problems in Campaign. If records were removed, an error occurred; if records were added, the additional records were not read. These issues have been fixed. If Campaign detects that the delimited file has changed,
it will rescan the file before queries are run against the file. Note that this scan can take a long time for large delimited files.

APAR PO00609, DEF19469
In French locale, the run menu for Campaign or Flowchart was translated "Executer" in French and "Pause" was translated as "Suspendre". In Operational Monitoring - "Surveillance opérationnelle" in French - for any running Flowchart and hover over the "Suspend" button was also translated as "Suspendre". To avoid confusion we have translated Pause to "Mettre en pause" now.

APAR PO00689,DEF 23710
In the MailList process box, trigger drop down/textbox was still editable even if 'Send triggers' was unchecked. The trigger drop down/textbox should always be disabled if 'Send triggers' checkbox is not checked. This has been fixed.

DEF 30127
The unica_acclean utility searched only the top-level session directory when the "-w session" option was used. The utility now correctly searches the session subdirectories as well.

PMR 26657, DEF 23851
In some scenarios, pasting a template containing an Audience process caused the flowchart process to crash. This has been fixed.

APAR PO00814, DEF 28189
While a flowchart was running, some processes allowed changes to the Process Name. If the Process Name was the same as the Output Cell Name, Campaign also tried to apply the same change to the Output Cell Name. However, changes to the Output Cell Name were not allowed while the flowchart was running. Although the Process Name change was accepted, the Output Cell Name change was rejected, and an error message was displayed to the user. Campaign no longer allows Process Names to be modified while the flowchart is running.

APAR PO01200, DEF 65194
Previously, certain cookies were not properly secured in the client browser. Not securing cookies could have left the application vulnerable to man-in-the-middle and session hijacking attacks. This is now fixed. This fix
requires some additional configuration on the application server. Refer to "Securing Cookies" in this readme file for configuration steps to perform on the application server.

APAR PO01178, DEF 65118
Previously most of the URLs were hit to the server using GET request, which made it possible to steal the sensitive data that are sent unencrypted. To overcome this issue, we have changed the GET request to POST request which will hide the parameters that are sent to the server from user.

APAR PO01199, DEF 65191
Previously, if the application was configured to run in HTTPS mode, application content such as images and CSS were cached in the browser. This issue has been fixed by adding a no-cache header in the filter.

APAR PO01193, DEF 65171
Previously, authenticated users could access and modify pages or content for which they did not have explicit authorization, by directly accessing URLs instead of using application navigation. This issue is now fixed. Authorization checks have been added for all application URLs.

APAR PO01177, DEF 65115
Previously, the application used to allow upload of potentially malicious file types. As part of this fix, users can upload only attachments conforming to type and size specified by the admin as configuration parameters
(allowedFileTypes and fileMaxSize). If the attachment does not conform to these parameters, it can not be uploaded and the user receives an error describing why the upload failed.

Fix Pack

Snapshot should create NVARCHAR column on Netezza for non Latin data. A datasource configuration property "DefaultTextType" is provided to set the output column data type as NVARCHAR.

The Target Cell Spreadsheet (TCS) performance slowed down with a large number of cell attributes and cells in a TCS. This has been resolved.

A Merge process using IDs from multiple data sources produced incorrect results in some scenarios when in-DB optimization was enabled. This has been resolved.

Permissions for a flowchart's Run menu were not applied correctly when multiple security policies were involved. This has been resolved.

Using UCGFs in complex macro expressions sometimes resulted in syntax errors during configuration that would not occur during runtime. This has been resolved.

Although Campaign does not support Oracle's NVARCHAR2 data type, Campaign used NVARCHAR2 when creating fields based on NVARCHAR fields from other data sources.Campaign now correctly creates fields using Oracle's VARCHAR2 data type.

Campaign's model process failed to run if All Algorithms was selected by a user whose Platform language preference is non-English. This has been resolved.

Campaign's Offer API only validated the first offer code in an array instead of validating all of the offer codes. This has been resolved.

(APAR PO00063, DEF 5219)
Campaign was not consistent in its naming of Affinium ID fields associated with multi-field audiences. This potentially caused issues when the Affinium ID fields were profiled or selected in processes having multiple input cells or were passed through a Merge process. Affinium ID fields associated with multi-field audiences are now named according to the audience definition, thus providing the consistency necessary to allow the audience fields to be identified regardless of their origin. Processes configured using previous versions of the software (and therefore possibly using different Affinium ID field names) will continue to function as before; newly configured processes will use the new Affinium ID naming convention.

Deadlock was observed in the Campaign web application. The code was refactored in order to avoid the possibility of a deadlock.

Flowchart ActiveX client versions were changed to consider the 6 digit versioning system adopted by IBM Unica products. This will help Microsoft Internet Explorer to differentiate between the new and the installed ActiveX client libraries. Note: If the existing ActiveX libraries are already in use, user will not be able to upgrade the libraries. So while updating ActiveX client libraries, it is recommended that all the Microsoft Internet Explorer instances should be closed and the installation should be initiated from a new browser window.

A very specific Audience Process misconfiguration resulted in an internal error (Error 17101), which prevented the flowchart from opening. The Audience Process now instead becomes unconfigured and allows the flowchart to be opened, thereby providing the user the opportunity to correct the configuration.

When Target Cell Spreadsheet has more cells than the page can display, the vertical scroll bar was not visible. This has been resolved.

unica_acclean failed to remove files whose full path length exceeded 200 bytes.This is now fixed.

unica_acclean accumulated open file descriptors, causing the process to eventually run out of available file descriptors. Flowchart files are now properly closed by releasing the file descriptors when unica_acclean has retrieved the necessary information from them.

(APAR PO00053, DEF 4418)
UA_Campaign's UpdateDate/UpdateBy fields were modified when the LastRunDate and RunBy fields were modified as a result of a flowchart run. This is now resolved.

(APAR PO00110, DEF 7925)
Printing the flowchart caused the browser to crash in some cases. This is now fixed.

(APAR PO00064, DEF 5228)
A memory leak in the eMessage process box, related to Derived Fields, was identified and fixed.

When Campaign was asked to copy a flowchart from one campaign to another, the back-end work (file system, database) was performed prior to verifying user privileges. As a result, although a warning was issued when privileges were lacking, the flowchart still was copied. Campaign now properly verifies user privileges prior to performing any back-end work.

A copied flowchart name was limited to 31 characters by the Fix Duplicates dialog. The dialog now limits the flowchart name according to the size of the Name field in the UA_Flowchart system table.

In some scenarios, Campaign used a temp table after releasing the temp table to the temp table pool. This has been fixed.

When a Custom Attribute with Select Box-string was created with a string having spaces, the spaces between words were suppressed automatically. This has been resolved.

When multiple users published separate Target Cell Spreadsheet grids around the same time in separate Unica Marketing Operations projects containing linked Campaigns, a publish error would be produced. This is now fixed.

When multiple flowcharts with long names were added to a session, the tabs for these flowcharts were not displayed consistently, depending on which flowchart was being viewed at the time. This is now fixed.

(APAR PO00359, DEF11260)
The response process produced an error or incorrect results when its input cell's numeric ID used a different internal type from the internal type used by Response History's numeric ID fields. For example: Response History's numeric IDs are typically stored in Campaign as text in order to preserve precision; if the input cell used a numeric ID field whose precision was less than or equal to 15, values would be stored in Campaign as numeric. This type difference caused an error or incorrect results in the response process. This has been fixed.

(APAR PO00275, DEF10445)
The list processes (MailList, CallList) validated the optional contact history field mappings even when configured not to write to contact history. The processes now validate the optional contact history field mappings only when configured to write to contact history.

The Response process failed to run when Response Date was set to a derived field that returned a Date (but not a DateTime) when system tables resided in DB2. This is fixed.

(APAR PO00205, DEF 9748)
"Save" and "Save & Exit" action did not identify changed order of cells in the Target Cell Spreadsheet (TCS). As a result the user was not able to change the order of any cell in the TCS. This is fixed.

unica_acsesutil's flowchart XML did not include CellSizeLimit for Segment processes. Segment XML now includes CellSizeLimit for those segments that are not unlimited.

(APAR PO00131, DEF 8336)
In some scenarios, a Select process returned an incomplete list of IDs when its criteria compared string field values to strings created using Campaign date macros and the data contained some duplicate ID values. This is fixed.

(APAR PO00142, DEF 8479)
Process boxes displayed no error at configuration time or during runtime if the Skip Duplicates field became invalid (e.g. because the field was removed from its table). This is fixed.

(APAR PO00160, APAR PO00177, DEF 8862)
The flowchart lost keyboard focus after a template was pasted, after which the Delete key could not be used to delete components of a flowchart such as process boxes or links. This is fixed.

(DEF 9785)
Invalid data was produced by an offer attribute UCGF when the attribute was set to a derived field which used a raw SQL Custom Macro. This is fixed.

(APAR PO00315, DEF 10618)
Campaign's LIKE macro produced incorrect results in some scenarios. This is fixed.

(INC09535, DEF010889)
Campaign's CrossTab report crashed with large settings for # bins when processing data containing a large number of unique values. Number of bins is now silently limited to a maximum of 500.

Campaign's plus (+) and minus (-) operators did not correctly handle the time component of datetime values. This is fixed.

When unica_acsesutil was asked both to print table mappings and to recompute table counts, the counts were recomputed after the tables mappings were printed, thus showing the obsolete counts. The code is now reordered so table mappings are printed after count recalculation.

(APAR PO00106, DEF 7896)
Values in the Target Cell Spreadsheet's Last Run Time column displayed English, regardless of the user's locale preference. Values in the Last Run Time column are now displayed according to the pattern configured in the file associated with the user's locale.

(APAR PO00117, DEF 8014)
On Campaign's Summary tab, although the Description and Objective fields allow multi-line entry, text was collapsed into a single line when saved. This is fixed.

Breadcrumbs for "Segment Crosstab Reports" was not working and clickable. This is fixed.

If a flowchart was run via unica_svradm using . or .. in the path, another instance of unica_acsvr was started if the GUI was used to access the same flowchart, causing potential system table issues. This is fixed - the GUI will now correctly connect the user to the unica_acsvr process associated with the flowchart started through unica_svradm.

When the Campaign listener was installed as a Windows service, the listener always restarted in recover mode, regardless whether the -n option was included when the service was installed. This is fixed.

Fix Duplicates dialog rejected certain non-ASCII characters when they were typed. The per-character check was removed to fix this.

Multiple instances of the listener were able to bind to the same port, causing communication disruptions. This is fixed.

WebSphere includes ciphers that caused failures in the third-party library used by Campaign's code to communicate via HTTPS to the web applications. To resolve the issue, the problematic ciphers are now ignored by Campaign.

Numeric UserVars displayed incorrect values when multiple values were selected or entered for initial or current value. This is fixed to behave like Int UserVars: only the first value is preserved; the other values are discarded.

For some operations, Campaign ignored the MaxItemsInList setting, causing Oracle failures when the IN clause exceeded 1000 items. When an IN clause would exceed the number of items specified by MaxItemsInList, Campaign now splits the SQL into multiple statements in order to keep the number of items in the IN clause
below the limit.

(APAR PO00382, DEF 11445 (Interact fix))
Custom Attributes defined for an offer which will be used within an interaction strategy were not displayed correctly when the offer was defined for an eligible segment. This is fixed.

(APAR PO00163, DEF 8941 (Interact fix))
Interactive Flowchart creation permissions were not being respected. This is fixed.

(APAR PO00382, DEF 11445 (Interact fix))
Interaction Strategy offer attributes were not displayed correctly within segments. This is fixed.

(DEF 9412 (Interact fix))
When user visited the Interact reports page from the following path Analytics > Campaign Analytics> ‘Interact Reports’ folder and then clicked on ‘Help for this Page’ link, then instead of Interact Eeports help, Campaign
Report help page was opened. This is fixed.

(APAR PO00381, DEF 11442 (Interact fix))
Clicking on Interactive channels with many objects caused the GUI to hang. This is fixed.

(APAR PO00179, DEF 9296 (Interact fix))
Error occured when selecting offer attributes while creating advanced rules in the interactive strategy module. This is fixed.

(DEF063770 (eMessage fix))
Triggered scheduled tasks did not appear when trying to schedule a mailing. This is fixed.

(APAR PO00144, DEF 8507 (eMessage fix))
eMessage mailings failed to start when the serverURLInternal parameter was used and a NumberFormatException was generated in Mailing UI. This is fixed.

Fix Pack

As the number of cells and attributes increase, so does the time it takes to view, edit, and save the TCS. This growth is exponential, while the addition of cells and attributes are linear. This has been resolved.

When Target Cell Spreadsheet has more cells than the page can display, the Up and Down scroll bar was not visible. This has been resolved.

When a Custom Attribute with Select Box-string was created with a string having spaces, the spaces between words were suppressed automatically. This has been resolved.

Breadcrumbs for "Segment Crosstab Reports" was not working and clickable. This has been resolved.


Important! It is mandatory that all IBM Unica Products installed should be at the same fix pack level.

For fix pack all IBM Unica products must be at fix pack level

Base Product Version Dependency:
This fix pack requires IBM Unica Campaign base 8.6.0 or any fix pack on 8.6.0.x or any Interim Fixes on these releases.

Installation Instructions

Note: See the IBM Unica Campaign 8.6.0 Installation Guide for additional information.

For AIX 6.1 with WebLogic 11g, make the following changes to the campaign.war file:

  1. Unwar the campaign.war file, and locate the xercesImpl.jar file in the WEB_INF/lib directory.
  2. Build the campaign.war file before deploying it.

Installation Steps:

Task 1 - Before you begin:
  1. Ask all users to log out of IBM Unica Campaign, and stop all running campaigns. (Make sure all Campaign Server processes are stopped.)
  2. Stop the Campaign listener process:
    • Windows: CAMPAIGN_HOME\bin\svrstop -p 4664
    • Unix: CAMPAIGN_HOME/bin/rc.unica_ac sto.
  3. If the eMessage Response Contact Tracker is running, stop it using "rct stop":
    • Windows: EMESSAGE_HOME\bin\rct.bat stop
    • Unix: EMESSAGE_HOME/bin/ stop
  4. Make sure that the "Campaign.war" file is not locked for update by the Web application process on which it is deployed. On certain systems, this may require undeploying the IBM Unica Campaign web app, stopping the web application server (WebLogic or WebSphere), and re-starting the web application server to bring back up the IBM Unica Marketing Platform web app.
Note: Make sure the IBM Unica Marketing Platform web application is still running.

Task 2 - IBM Unica Campaign Fix pack Installer:
  1. Run the IBM Unica Campaign Fix Pack installer through the Unica Installer on all servers where IBM Unica Campaign resides (web side and analytic server side). (Please refer to IBM Unica Campaign 8.6 Install Guide for details.)

Note: As this is a Fix Pack installer, it is expected that the appropriate release (i.e., 8.6.0) has already been installed on the current machine by the same user running the Fix Pack installer. If the Fix Pack installer cannot find a previously installed release, please contact IBM Technical Support for assistance.
Task 3 - SSL Configuration:
If you are upgrading from version IF02, skip this task entirely. For upgrades from versions earlier than IF02, follow the steps below to update your SSL configuration.

Note: This issue is applicable only if HTTPS is configured for communication between the web server and the listener application. Note that the OpenSSL library is automatically consumed if the application server is configured with HTTPS and SSL is enabled for the listener application.

3.1. For WebLogic Application Server

Append the following option to the JAVA_OPTIONS variable:

For Details:

3.2. For WebSphere Application Server

For IBM WebSphere Application Server and IBM WebSphere Application Server Hypervisor Edition:

Instructions are summarized below. For details, see:

Download and apply the interim fix APARs below, for your appropriate release:

-- For through --

Apply Interim Fix PI28438: Will upgrade you to IBM Java SDK Version 6R1 Service Refresh 8 Fix Pack 1 + APAR IV66110 for change to disable SSLv3 by default


Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 10
( or later.

-- For V7.0.0.0 through --

Apply Interim Fix PI28439: Will upgrade you to IBM Java SDK Version 6 Service Refresh 16 Fix Pack 1 + APAR IV66110 for change to disable SSLv3 by default


Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 37 ( or later.

Task 4 - Regeneration of SSL keys and certificates:

Follow the steps below to secure your application against OpenSSL security vulnerabilities.

Note: This issue is applicable only if HTTPS is configured for communication between the web server and the listener application. Note that the OpenSSL library is automatically consumed if the application server is configured with HTTPS and SSL is enabled for the listener application.
  1. After successful install regenerate all SSL keys and certificates. Use PEM file generation through openssl. Update the existing .pem file that contains the newly generated keys. If you save the keys in a file with a different name from your original, update the config.xml in the <Campaign_Home>/conf folder to use the new .pem file name.
Task 5 - Instructions for cleaning web server cache:

Stop the webserver and clean web server cache.
  1. For Weblogic, delete contents of <WeblogicDomain>\servers\AdminServer\tmp andWeblogicDomain>\servers\AdminServer\cache
  2. For Websphere, delete contents of <ProfileLocation>\wstemp and <ProfileLocation>\temp
  3. Start the webserver

Task 6 - Restart the IBM Unica Campaign components:
  1. Redeploy the IBM Unica Campaign web app if it has been undeployed
  2. Start the IBM Unica Marketing Platform and IBM Unica Campaign web apps.
  3. In IBM Unica Marketing Platform, confirm that the version information for this installation of IBM Unica Campaign has been properly updated. To find this information, select Help > About Unica. If the About page is not accessible, you can obtain the version number of any IBM Unica application by viewing the version.txt file in each application's installation directory.
  4. Restart the IBM Unica Campaign listener:
    • Windows: CAMPAIGN_HOME\bin\cmpServer.bat
    • Unix: CAMPAIGN_HOME/bin/rc.unica_ac start
  5. If eMessage is configured, restart the Response Contact Tracker using "rct start" and check the connectivity.
    1. Start the response and contact tracker (RCT).
      • Windows: EMESSAGE_HOME\bin\rct.bat start
      • Unix: EMESSAGE_HOME/bin/ start
    2. To check the connectivity run the rlu script.
      • Windows: EMESSAGE_HOME\bin\rlu.bat -c
      • Unix: EMESSAGE_HOME/bin/ -c

Task 7 - Make configuration changes:

If you are upgrading from version, skip this task entirely. For upgrades from versions earlier than, follow the steps below to update your configuration.
  1. Modify ODBC datasource configurations as follows:
    a. Export Configuration
    configTool.bat -x -p
    "Affinium|Campaign|partitions|partition1|dataSources|<Your Datasource name>"
    -f DataSrc.xml

    b. Edit the xml and insert the following lines just after the
    "DefaultScale" property:

    <property name="DefaultTextType" type="radio">
    <value selected="false" predefined="true">VARCHAR</value>
    <value selected="true" predefined="true">NVARCHAR</value>

    For example:
    <property name="DefaultScale" type="integer">
    <property name="DefaultTextType" type="radio">
    <value selected="false" predefined="true">VARCHAR</value>
    <value selected="true" predefined="true">NVARCHAR</value>

    c. Import the configuration

    configTool.bat -i -p
    "Affinium|Campaign|partitions|partition1|dataSources" -f DataSrc.xml

    d. Navigate to the data source and verify that the new property was added.
2. A new configuration property "legacyMultifieldAudience" has been added for DEF 5219 fixed in This property defaults to FALSE and should be set to TRUE only if existing flowcharts with multi-field audiences do not work as expected with it set to FALSE. Setting it to TRUE will revert to the legacy way of handling multi-field audiences. It can be added to the configuration as follows:
    1. Export Configuration
    configTool.bat -x -p
    "Affinium|Campaign|partitions|partition1|server|flowchartConfig" -f

    b. Edit the xml and insert the following lines just after the "replaceEmbeddedNames" property:

    <property name="legacyMultifieldAudience" type="radio_property">
    <value selected="false" predefined="true">TRUE</value>
    <value selected="true" predefined="true">FALSE</value>

    c. Import the configuration

    configTool.bat -i -p
    "Affinium|Campaign|partitions|partition1|server" -f fcconfig.xml -o

    d. Navigate to the flowchartConfig category and verify that the new property was added.

Task 8 - eMessage system table changes:

If you are upgrading from version, skip this task entirely. For upgrades from versions earlier than, follow the steps below to update your eMessage system tables.
  1. Run the following SQL commands on the Campaign system database:

ContChannelTypeID int NOT NULL,
Description varchar(256) NOT NULL

ADD ContactPhone varchar(16);

ALTER TABLE UCC_Container ADD ContChannelTypeID int NOT NULL default 1;

INSERT INTO UCC_AttributeType (AttributeTypeID, Description)
VALUES (13, 'SMS');

Insert into UACE_ResponseType (ResponseTypeID, Description)
VALUES (15, 'SMS aggregator rejected');
Insert into UACE_ResponseType (ResponseTypeID, Description)
VALUES (16, 'SMS carrier failed to deliver');
Insert into UACE_ResponseType (ResponseTypeID, Description)
VALUES (17, 'SMS delivered');
Insert into UACE_ResponseType (ResponseTypeID, Description)
VALUES (18, 'SMS reply message');

INSERT INTO UACE_ContChannelType (ContChannelTypeID, Description)
VALUES (1, 'Email');
INSERT INTO UACE_ContChannelType (ContChannelTypeID, Description)
VALUES (2, 'SMS');

ResponseID bigint NULL,
RespDateTime datetime NOT NULL,
SMSCode varchar(45) NOT NULL,
SMSMessage varchar(256) NOT NULL,
OriginatingNumber varchar(45) NOT NULL,
CarrierName varchar(45) NULL,
CustomerStatus int NULL,
CorrelationID bigint NOT NULL DEFAULT -1

REFERENCES UCC_Response (ResponseID);

DocumentSubject varchar(1024) NULL,
DocumentMailFrom varchar(1024) NULL,
MailingUpdatedBy varchar (64) NULL,
DocumentDescription varchar(1024) NULL,
MailingUpdateDate datetime NULL;

insert into UACE_AppVersion(versionNumber, schemaUpdate, firstMailingInstId, createDate)
values ('', 1, 0,

Reports Pack Campaign Installation Instructions:

To update Campaign reports, complete the following steps. To also update eMessage reports, see the steps in the 8.6.0-UC-FP07_eMessageReports_Readme.txt.

Task 1 - Before you begin:
  1. Ask all users to log out of IBM Unica Campaign, and stop all running campaigns. (Make sure all Campaign Server processes are stopped.
Note: Make sure the IBM Unica Marketing Platform web application is still running.

Task 2 - IBM Campaign Report Installer:
  1. Run the IBM Unica ReportsPackCampaign_8.6.0.11 Installer on servers where IBM Campaign Report Pack base version resides.
  2. Select the install set which includes Reporting Schema and IBM Cognos package for IBM Unica Campaign
  3. Choose base or Custom Schema to install.
Note: As this is a patch installer, it is expected that the appropriate release (i.e., 8.6.0) has already been installed on the current machine by the same user running the patch installer. If the patch installer cannot find a previously installed release, please contact IBM Unica Technical Support for assistance.

Task 3 - Deploy and Publish Campaign Report model using IBM Cognos framework

Task 4 - Configure Cognos URL in IBM Platform (Please refer to the IBM Unica Campaign Administration Guide for details)

Task 5 - Restart Application server:
  1. Stop the Web application server (WebLogic or WebSphere), and re-start the Web application server to bring up IBM Unica Marketing Platform and IBM Unica Campaign.

Appendix A: Securing Cookies:

Certain cookies may not be properly secured in the client browser. Not securing cookies leaves the application vulnerable to man-in-the-middle and session hijacking attacks. To fix this issue, we suggest the following configuration:

1. Enforcing the use of SSL at all times may reduce the risk of cookies being intercepted on the wire.
2. The "secure" flags should be set on all cookies.

For WebLogic:
Secure flag: This flag tells the browser to only send the cookie back over an HTTPS connection.
This ensures that the cookie ID is secure and should only be used on Websites that use HTTPS. SessionCookies over HTTP no longer work if this feature is enabled.
Hence, by default, this flag is set to false. If the user wants to enable this flag, they will have to un-war, set this flag to true & re-war again.
a. Stop the server if already started.
b. Undeploy the Campaign war/ear from the server if deployed already.
c. Open the Campaign.war archive in using tar or zip utility.
d. Open the weblogic.xml file located in WEB_INF folder. Any text editor can be used for this purpose.
e. Add the parameter <cookie-secure>true</cookie-secure>
under the tag <session-param>. The place under <param-value> is ideal to put this tag.
e.g. -
f. Bundle the modified weblogic.xml into Campaign.war again.
g. Clear the cache in weblogic application server.
h. Redeploy the changed Campaign.war on the server.
i. Start the server.

For WebSphere:
WAS 7:
Secure flag:
a. In the administrative console, click on "WebSphere enterprise applications" under "Applications." All installed applications will open up on the right side.
b. Click on the "Campaign" application link.
c. Click Session Management.
d. Click the enable cookies link.
e. Enable "Restrict cookies to HTTPS sessions" option. Apply & save changes.

3. Disable HTTP Communication ports on Campaign JVM. Previously we were able to access HTTP URL over HTTPS setup. To prevent this, we should add following settings:

WebSphere Application Server Guidelines:
a. Log in to WebSphere console.
b. Go to Servers
c. Select Server Types -> WebSphere Application Server.
d. Click the server name you are using to deploy the campaign application
e. Click the Ports link.
f. Click "View associated transports" for "WC_defaulthost".
g. Disable transport chain for "HttpQueueInboundDefault" and "WCInboundDefault".
h. Restart Application Server.

WebLogic Guidelines:
a. Log in to WebLogic console.
b. Click on Environment > Servers - This will open Settings for Server.
c. Clear the check box for "Listen Port Enabled".
Make sure the check box for "SSL Listen Port Enabled" is checked.
d. Save the changes.
e. Stop Application server.
f. Clear WebLogic cache.
g. Start Application server.

Setting HttpOnly Flag On Cookies:

HttpOnly flag: If the HttpOnly flag is included in the HTTP response header, the cookie cannot be accessed through client side scripts. This flag
is supported only from WL 10.3.2 (WL Server 11gR1 PS1 - November 2009), and its default value is true. So, for the previous versions to WL 10.3.2, this flag is not supported.

For WebSphere:

For WAS 7:

httpOnly flag: WebContainer custom property " .httpOnlyCookies" needs to be set to *.
To set a webcontainer custom property on IBM WebSphere Application Server
Version 7:
  1. In the administrative console, click Servers > Server Types > WebSphere application servers.
  2. Click on the server to which the custom property is to be applied.
  3. Under "Configuration," click Container settings > Web Container Settings > Web container.
  4. Under "Configuration" and "Additional Properties," click "Custom Properties."
  5. In the Custom Properties page, click "New."
  6. In the settings page, enter the name of the custom property to be added in the "Name" field and the value to be set for the custom property in the "Value" field. Note that some properties are case sensitive.
  7. Click "Apply" or "OK."
  8. Click "Save" in the "Messages" box that appears.
  9. Restart the server for the custom property to take effect.

Refer to the following URLs for more details:

For WebLogic:
For WebLogic 11g, make the following changes to the campaign.war file:
  1. Unwar the campaign.war file, and locate the weblogic.xml file in the WEB_INF directory.
  2. Open weblogic.xml in a text editor and add the following line: <cookie-http-only>false</cookie-http-only> in the session-descriptor section of the file. For example, your finished session-descriptor section should look similar to this:
3. Save the weblogic.xml file.
4. Build war campaign.war to include the changes you made before deploying it.

Download package

Fix Pack Installers:

IBM Unica Campaign:

IBM Unica Campaign Report Pack Installer:

IBM Unica Installer:

Files Included in Fix Pack Installers:


Document information

More support for: IBM Campaign

Software version: 8.6

Operating system(s): AIX, Linux, Solaris, Windows

Reference #: 4035565

Modified date: 21 August 2015

Translate this page: