Data Workbench 6.4 Release Notes

Data Workbench 6.4 release notes include new features, upgrade requirements, fixed bugs, and known issues.

To view previous features and fixes for past releases, see the release notes archive.

New Features

Data Workbench 6.4 includes these new features:

Device Atlas with In-Memory Cache

The DeviceAtlas.bundle file now uses an in-memory cache to greatly improve the performance of lookups

By default, Device Atlas will cache up to 100,000 user-agents and their properties. The LRU cache is entirely self-contained inside the DeviceAtlas.bundle, so any version of the server capable of using a bundle file will automatically benefit from the increased performance as soon as the new file is loaded.

Modifying the DeviceAtlas.cfg file

The maximum size of the LRU cache can be configured by modifying the Cached Elements Limit parameter in the DeviceAtlas.cfg file.

Starting with the Data Workbench 6.4 release, you can override the default Cached Elements Limit of “100000” by changing its value and saving the file. The default value has been selected to be sufficient for most needs.

component = DeviceAtlasComponent:
  DeviceAtlas Bundle File = string: Lookups\\DeviceAtlas\\DeviceAtlas.bundle
  Unsynchronized Bundle Extraction Path = string: Temp\\DeviceAtlas\\

<b> Cached Elements Limit = unsigned int: 100000</b>

Upgrade Requirements

Follow these requirements and recommendations when upgrading to Data Workbench 6.4.

• Add Excluded Processes for MS System Center Endpoint Protection in Windows 2012 Servers for the following executables:

  • InsightServer64.exe
  • ReportServer.exe
  • ExportIntegration.exe

  This will allow white-list rights for these interfacing executables.

• Update the Trust_ca_cert.pem certificate on the servers.

• Reorganization of Attribution Profiles.

  • The Attribution folder was renamed to Attribution - Premium (found in the default installation at Profiles \ Attribution - Premium).

  • The Premium profile was removed and the workspace moved to the new Attribution - Premium folder.

• Update Attribution-Premium settings. If you have customized profiles with parameter settings that override the default Adobe SC profile, then you need to update the custom fields in these configuration files:

  • Decoding Instructions.cfg
  • SC Fields.cfg

• Because of this reorganization, you will want to remove the old Attribution and Premium folders from your server installation.

  Change these settings

  Profile = profileInfo:
    Active = bool: true
    Directories = vector: 6 items
      0 = string: Base\\
      1 = string: Geography\\
      2 = string: Predictive Analytics\\
      3 = string: Adobe SC\\
      4 = string: Attribution\\
      5 = string: Premium\\
  

  to these settings:

  Profile = profileInfo:
    Active = bool: true
    Directories = vector: 5 items
      0 = string: Base\\
      1 = string: Geography\\
      2 = string: Predictive Analytics\\
      3 = string: Adobe SC\\
      4 = string: Attribution - Premium\\
  

• Update custom Meta.cfg files (if necessary).

  The Meta.cfg files in Base\Context and AdobeSC\Context folders have been updated in this release.

  If you override the meta.cfg file during installation, then your profile copy needs to be updated with this these parameters and the metadata vector appropriately entered:

  94 = meta:
    path = string: SegmentExport:CRS Configuration/CRS Attributes
    acceptable children = vector: 1 items
      0 = Template:
        name = string: CRS Attributes
        value = CRSAttributeConfiguration:
          Attribute Name = string:
          Attribute Type(int,string) = string:
          Field Name = string:
  
  95 = meta:
    path = string: SegmentExportQuery:CRS Configuration/Report Suite
    acceptable children = vector: 1 items
      0 = Template
        name = string: Add Report Suite
        value = string:
  

• Set Report Server permissions to generate Microsoft Excel reports On Windows 2012 servers.

  1. Set permission of the root folder (E:\ReportServer\) to Everyone = full control.

  2. Create the following folders with appropriate permissions:

     C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows\INetCac‌he
     C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\INetCac‌he
     C:\Windows\System32\config\systemprofile\Desktop
     C:\Windows\SysWOW64\config\systemprofile\Desktop
     

     NOTE

     If you are running Report Server on Windows Server 2012, you need to have Windows Server 2012 R2 installed.

  3. Assign “SYSTEM” as the owner for these folders.

• Add fonts to the Report Server. In the **ReportServer.cfg**file, add these fonts (for all languages):

  Fonts = vector: 3 items
    0 = string: Arial
    1 = string: SimSun
    2 = string: MS Mincho
  

• Update your version of Microsoft Excel (if necessary).

  With the release of Data Workbench 6.4, support for Excel 2007 has been discontinued. Also because Data Workbench only runs on Microsoft Windows for 64-bit architecture, it is recommended that you also install a 64-bit version of Microsoft Excel.

• 64-bit architecture required for Workstation (Client) installation.

• Run the Workstation Setup Wizard.

  Install the new version of the workstation (client) by downloading and launching InsightSetup.exe and stepping through the setup instructions. The setup wizard will install your files to a new location by default:

  Program files are now saved by default to:

  C:\Program Files\Adobe\Adobe Analytics\Data Workbench
  

  Data Files (profiles, certificates, trace logs, and user files) are now saved by default to:

  C:\Users\<username>\AppData\Local\Adobe\Adobe Analytics\Data Workbench\
  

• Add fonts to the Workstation.

  In the Insight.cfg file, add these fonts (for all languages):

  Fonts = vector: 3 items
    0 = string: Arial
    1 = string: SimSun
    2 = string: MS Mincho
  

System Updates

These features have been renamed, deleted, or the installation files or folders were restructured in this release:

• The Base.zip folder is no longer included in the version update package.
• The DeviceAtlas.bundle file now uses an in-memory cache to improve the performance of lookups.
• In the Log Processing.cfg file, the Chunk Size parameter under Log Sources was removed.
• In the Disk Files.cfg file, the Detect Disk Corruption parameter was removed in these locations:

\server\components\disk files.cfg

\server\components for processing servers\disk files.cfg

• New service descriptions for Adobe Analytics Premium Services and for Adobe Analytics Premium Report Services in the executable properties.
• The Master Marketing Profile Export feature in the Details Table was renamed to Profiles & Audiences Export.
• The Test and Target Export feature in the Details Table was renamed to Adobe Target Export.

Fixed Bugs

The following fixes were made in Data Workbench 6.4 (since the release of Data Workbench 6.31).

• Propensity score wasn’t resetting when rerunning different inputs in the same workspace. This now resets properly.
• No countable dimensions available when first opening the Correlation Matrix has been fixed.
• Export of Target segments were failing because the mboxPC field was missing. This is now fixed.
• ID request formatted correctly. Using the mbox3rdpartyId identification instead of default PCIDs caused Adobe Target to reject requests generated via the Target/Data Workbench integration (using the ExportIntegration.exe). This ID request is now being formatted correctly and throughput is successful.
• Report Server memory leak when exporting to Excel has been fixed.

Known Issues

The following are known restrictions in Data Workbench 6.4.

• ExportIntegration.exe requires command-line arguments in English. The output file name should be named in English for Adobe Target Export, Profiles and Audiences Export, and Customer Record Service Export.
• In the Profiles and Audience Export, entering unauthorized characters ([CR] or [TAB]) as column names generates incorrect logs resulting in data not exporting correctly.
• In Chinese and Japanese versions, Unicode character encoding issue might be encountered in the Path Browser.