Release Notes

For CQ WCM, Version 5.3 and CQ DAM, Version 5.3

The release cycle for this release of CQX started April 1, 2009, went through 19 iterations of quality assurance and bug fixing, and ended January 27, 2009. The total number of customer related issues including enhancements and new features fixed in this release is 645 compared to the CQ 5.2.0 code base. Some of them were already released in the CQ 5.2.1 patch release.
CQ 5.3 is generally available since February 1, 2010.

CQ WCM 5.3 is a web content management system for enterprise-level organizations that have complex and interactive websites and large content authoring teams. CQ WCM 5.3 offers add-on modules that provide advanced content management with forms, offline editing and WebDAV, Portal and Personalization, Integration with Portal servers, Social Collaboration including Newsletters, Blogs, Wikis and Calendaring, LDAP and Single-Sign-On, Multi-Site-Management, Active Clustering and CIFS Support. CQ5 WCM 5.3 integrates with Day's CRX, Virtual Repository and Digital Asset Management products.

CQ DAM 5.3 is a digital asset management system for enterprise-level organizations that have large asset repository combined with complex and diverse uses for assets in different audiences. CQ DAM integrates with Day's CRX, Virtual Repository and Web Content Management products.

CQ  5.3 is a upgrade release to the CQ 5.2 and CQ 5.2.1 code base. It provides major add-ons, key customer fixes, high priority customer enhancements and general bug fixes oriented toward product stabilization. It also includes all CQ WCM 5.2 and 5.2.1 hot fix releases. Key enhancements are directed towards an even better usability for all users – authors, administrators, and developers –, to further facilitate all tasks related to the content live cycle in a global enterprise. Enhancements include:

• Improved online documentation on CQX and on docs.day.com
• Improved stability and performance
• Improved Digital Asset Management (requires CQ DAM)
• Improved Calendaring (requires CQ Social Collaboration)
• Improved Blog Authoring and Publishing (requires CQ Social Collaboration)
• In-Context Editing
• Improved Personalization (requires CQ Social Collaboration)
• All-new Targeting, Segmentation and Campaign Management (requires CQ Targeting)
• All-new Multivariate Testing (requires CQ Targeting)
• Integrated Tools for pervasive performance profiling
• An improved CRXDE (was CQDE) with Subversion Integration
• All-new web-based CRXDE lite with Subversion Integration as part of the CQ platform
  
• All-new Site Importer
• All-new Package Share
• Extended-CQ as a portal (requires CQ as a portal)

Day is using a customer focused development model that allows customers to contribute to all stages of the development process, during specification, development and testing. Our thanks goes to all contributing customers and partners in this process.

Day has the procedures and processes in place to enable collection, prioritization, and tracking of customer focused bug resolution and enhancement request development. The DayCare Issue Tracking System is loosely integrated with the Day Bug and Enhancement Tracking System. Customer issues are identified and resolved in DayCare where possible. When escalated to R&D, all customer information is captured, and used for prioritization and reporting purposes. Priority is given in development to paid support and warrantee issues and paid customer enhancements.

This process of prioritization has yielded more than 160 customer focused bugs fixed in CQ 5.3. Bugs here intend all issues captured in the Day Bug and Enhancement Tracking System, many of them actually being new features or enhancements. There are many more issues resolved at the DayCare level.

The CQX  feature-set is, as in earlier versions, dependent upon the requirements of the user. All customers are invited to increase and extend modular bundled features of CQX through Tech-preview projects. The advantage to the customer is that this offers them the chance to introduce their own requirements into the resulting features. These will then be incorporated in the official product module - with product support and maintenance. A limited number of Tech-Preview projects will be available, so contact Day Software as soon as possible to register your interest. Please see the list for running CQX Tech-Preview projects and contact your Day Software service representative if you would want to join one of these programs.

• Forum (Social Collaboration)
• Portal-Integration (Portal specific like SAP Enterprise Portal)
• Commerce
• Update Tool (Update from CQ3 and CQ4 to CQ5)
• CRXDE (was CQDE)
  

Customers will benefit from this release through a continued stabilization. This will lead to an even better efficiency and experience for users on all levels.

Main benefits therefore are:

• Better author experience and productivity
• Better administrator experience and productivity
• Better developer experience and productivity
• Better reliability
• Increased workflow performance

Additionally more than 100 new features and more than 800 enhancements to existing features were included in this release.

Main benefits therefore are:

• Add-on: Easier creation of targeted content and better segmentation of website users
• Support for complex cascading calendars with repeating events in multiple time zones
• A web-based development environment for faster component development
• An In-context editing that shows a 100% accurate preview of content on the live page
• Support for easy creation of multivariate tests
• Built-in profiling that allows developers to spot performance bottlenecks
• A site-importer that speeds up project creation from existing sites or HTML wireframes
• An integrated package share that allows customers to easily download, manage and install update packages

CQ DAM 5.3 significantly increases workflow processing performance, which means customers will benefit from shorter asset processing times. Additionally, customers will benefit from this release through a continued stabilization. This will lead to an even better efficiency and experience for users on all levels.

Main benefits therefore are:

• Better user experience and productivity
• Better administrator experience and productivity
• Better developer experience and productivity
• Higher reliability
• Increased workflow performance

Additionally more than 100 new features and more than 800 enhancements to existing features were included in this release.

Main benefits therefore are:

• Extended support for additional file formats such as EPS and PSD
• Support for RAW image file formats
• Integration of external command line programs for asset processing
• Increased extensibility for asset processing workflows
• Extensible, file-type specific Asset Editors
• Asset Editor pages that allow creation of asset centric applications that integrate with CQX-powered websites
• Better detection of popular XMP metadata schemata

In-Context editing allows editing of text-based components in the CSS context of the current page, which means that all formatting will apply exactly as it will appear on the published page, giving authors more immediate feedback about their creation and reduces feedback cycles.

The rich text editor (RTE) and the table editor have been extended to give authors more formatting options and greater control over their content. It is using a customizable plugin system, so that site owners can define what formatting options are made available to authors, so they can ensure overall visual consistency for their sites. Developers can use this plugin system to develop additional formatting plugins.

Components can now have default content, allowing quick drafting of content pages with pre-canned content components. Additionally this reduces the amount of time needed configuring more complex and powerful components.

CQ WCM includes a site importer that allows developers to quick-start the creation of new templates from existing HTML, for example from HTML wireframes or existing sites. This reduces the amount of time needed to initialize projects and allows authors to start creating content in a familiar environment in shorter time.

Pages activated in WCM can now automatically activate all referenced assets. This increases site consistency, reduces the effort needed to publish complex pages and leads to a more concise separation of DAM and WCM content life cycles.

Forms can now be used as parts of a workflow. Additionally a number of new, more powerful form controls have been introduced for example a tag field that allows tagging a form payload.

CRXDE and CRXDE lite include Subversion integration, which allows developers to create a Subversion working copy inside their CRX repository without having to synchronize to the file system as an intermediate step. This increases developer productivity.

CRXDE and CRXDE lite allow creation and compliation of OSGi bundles. This means no external build tool is neccessary and will cut down the overall development time.

CRXDE lite is an entirely web-based IDE featuring syntax highlighting, node editing, transactional development and plugin-based extensibility. This allows developers to extend and debug CQX instances even in cases where their accustomed development environment is not available.

CQ DAM 5.3 supports a greater variety of file types, most notably Adobe PSD, Photoshop EPS and numerous camera RAW formats. Additionally it offers optional command line asset processing that allows configurable support for additional file types and renditions. With this the range of files that can be stored, managed and interpreted by CQ DAM is extended and gives CQ DAM users a better understanding of their assets.

Customizable asset editors allow mime-type specific dialogs for editing only the metadata that is relevant for an specific file type. This will reduce the overall complexity of asset dialogs, thus increasing the productivity of DAM users. On the other hand, it allows organization to enforce a tigher metadata management, thus increasing the overall value of their asset collection.

An improved DAM finder application, the Geometrixx press center shows how media-rich interactive applications can be integrated into CQX-based websites. It features a new options predicate that allows users to filter metadata properties based on a predefined taxonomy of options, either flat or hierarchically.

The default asset processing workflows for DAM have been restructured for higher performance and greater extensibility. Customers looking to integrate custom steps into their asset processing workflows have now one single extension point, regardless wether the asset has been updated in DAM admin, DAM finder, WebDAV folder or an external application.

Workflow management in CQX has been optimized for high parallelism and throughput, so that it is now possible to run thousands of concurrent workflow instances without slowing down overall user experience.

DAM finder applications can now use customizable asset editor pages that include completely user-defined metadata-driven forms. These forms can be read-only or updateable, show metadata from a large selection of commonly used metadata schemata or custom-defined metadata schemata.

DAM comes with integrated lightboxes that can be accessed via DAM finder applications, asset editor pages or WebDAV. These lightboxes can be downloaded as a bulk ZIP file and integrated into the creative workflow with custom update and processing workflows.

DAM editors now show sub-assets, versions and references in tabbed panels, giving users an immediate overview over content, history and usage of their digital assets.

DAM allows seamless integration with CRX connectors, for example the Sharepoint connector. This allows management of digital assets residing in external repositories through one unified, familiar and extensible user interface.

All comments components now support Trackback and Pingback, which will also be used for Blog Trackback and Pingbacks. This will faciliate greater communication and allows for programmatic commenting.

A blog can now combine regular blog posts that will appear in the time line and unlisted blog pages. This allows for a deeper integration of blogging and classical web content management and more content-rich weblogs.

The blog is now using a full paragraph system, which supports drag and drop of all components that can be used in a website. Authors have now access to a greater range of content management options, leading to more attractive blog posts. Site owners can control which components are to be used in blog posts, allowing them to exercise greater control to achive higher content consitency.

The blog list component allows for more fine-grained paging configuration, so that blogs can be used in more flexible scenarios. Additionally it supports truncating of blog posts, so that "read more" links can be inserted easily by authors, allowing for more in-depth and content-rich blog posts.

Personalization is now using the Form Chooser framework, so that site owners can easily control, which personal information can be stored in a CQX user profile.

Personalization form fiels allow a read-only configuration, so that public user profiles can be implemented easily, giving users a community space.

The event component attached calendar event metadata to a CQX page, making it show up in calendars and allowing ICS download.

The querybuilder can now generate ICS output, allowing users to subscribe to any collection of events on the site or in calendars using Microsoft Outlook, Google Calendar or Apple iCal.

The polling importer's ICS import has been improved, allowing better roundtripping of calendar subscriptions.

The calendar component allows for one-time ICS import (additional to the polling importer), speeding up the migration from existing calendars to CQX.

The calendar component opens a customizable event form to view and edit event details. This gives site owners the ability to connect additional metadata such as descriptions, hyperlinks or images with their events.

The calendar component now includes a week and a day lens, giving a more detailed view into calendar events.

The calendar now handles recurring events properly, allowing custom recurrence rules and exceptions to these recurrence rules.

Calendar components can subscribe to other calendars, content trees or specific events, giving an aggregated view on the calendar data as part of a site.

Calendar detail forms can include start workflow buttons, which allows requesting the inclusion of one event in another calendar's subscription list. This allows creation of push-workflow set-ups.

CQ Wiki is being shipped with a standard installation of CQX.

CQ 5.3 increases the accuracy of built-in analytics and extends the choice of external analytics providers.

Segmentation allows creating per-site segments and sub-segments. Each segment is defined by a number of traits describing the visitors that fall into this segment. With this marketeers can express their market segmentation in a structured way and apply it automatically to their visitors.

Traits can be combined using AND and OR rules, allowing the creation of complex segments that describe specific parts of a target group that need customized messaging.

There are traits that access the user's profile properties (if used in combination with Social Collaboration), traits that use the visitor's behavior onsite and offsite (such as search keywords) and traits that use technical properties such as browser vendor and screen resolution.

Developers can create their own custom traits to allow site owners even more specific targeting.

Traits evaluation can be checked by marketeers using the Clickstream Cloud, which shows a specific user profile.

The Clickstream Cloud supports loading user profiles to simulate different user segments.

Marketeers can create Campaigns to promote their content. Campaigns are collections of teaser pages. With this users have a way of running site-specific campaigns and creating different campaigns that run at the same time.

Each teaser page can contain any number of content paragraphs. This gives users full flexibility when it comes to delivering their marketing message.

Each teaser page can be targeted towards specfic segments or tags. Additionally teaser can have a specific on- and off-time so that they run only a limited amount of time. This gives marketeers full control over the delivery of their content.

The teaser pagraph can be placed anywhere on the site, giving authors full flexibility where they want to deliver targeted content.

Every teaser paragraph will deliver one specific campaign, this gives authors full control over the targeted content they are delivering.

Teaser paragraphs support different selection strategies, so that authors can define how CQX delivers targeted content.

With Multivariate Testing (MVT) marketeers can test different creatives such as banner variants on their audience and make sure only banners with high conversion rate will be displayed once the test is completed.

The portal functionality has been extended to provide a Java standard compliant portlet container. This allows to use standard compliant portlets as components on CQ pages.

See installation instructions for setup requirements.

In order to see what platforms are certified to run with this release of CQ WCM and CQ DAM, please refer to the CQX online documentation: Supported platforms.

During the upgrade CRX will log warnings about unknown node types and that nt:unstructured is used instead:*WARN * NodeImpl: Fallback to nt:unstructured due to unknown node type '{internal}GrantPermission' of nodeThis is expected behaviour because CRX 2.0 comes with changed security node types and migrates the old security content to the new structure.

CQ specific user content is lost when upgrading a CQ 5.2.1 instance with Hotfix 23673 installed. This includes profile, preferences and privilege information. Hotfix 23673 stores CQ specific user information in a way that is incompatible with the regular user structure: the intermediate path to the user home is prefixed with 'cq:' when the hotfix is installed.

Additional user content must be migrated manually.

Upgrading to 5.3 will remove the groups surfer and uploader. Both groups are not needed anymore and membership of the anonymous user in either of the groups (uploader on an author instance and surfer on a publish instance) is not necessary anymore because permissions are now governed through the everyone group. Every user is implicitly a member of the everyone group. Additional permissions that have been set for the surfer or uploader group after the installation of 5.2.1 must be re-applied manually to the everyone group after the upgrade.

See upgrade documentation for more details and a step by step description.

• Digital Asset Management
• Miscellaneous
• Platform – Commons
• Platform – Development
• Platform – Graphics Engine
• Platform – Internationalization
• Platform – Packaging
• Platform – Quickstart
• Platform – Replication
• Platform – Rewriter
• Platform – Search
• Platform – Security
• Platform – Tagging
• Platform – Widgets
• Portal
• Social Collaboration - Wiki
• Social Collaboration – Blog
• Social Collaboration – Calendar
• Social Collaboration – Components
• Social Collaboration – Newsletter
• Social Collaboration – Social Network
• Upgrade Tool
• WCM – CMS
• WCM – Components
• WCM – Designer
• WCM – Forms
• WCM – Geometrixx
• WCM – Multisite Manager
• WCM – Targeting
• Workflow

List of known issues

Inplace Editing only works if Content Finder is present.

If non-root context is used, some components might not work as expected. Please test accordingly.

The default comment moderation workflow is not displayed properly in the model editor.

Translated Online Help is not shipped with the product. Translations will be provided through package share.

Unlike in CRX 1.4.x / CQ 5.2.1 the JAAS configuration e.g. ldap_login.conf provided on the command line when the JVM is started does not take precedence anymore over the LoginModule entry in the repository configuration. In CRX 2.0/CQ 5.3 one needs to remove or comment the LoginModule entry in the repository configuration when an external JAAS configuration should be used.

Authenticated users will not be able to login into any workspace when sync mode is set to 'none' and the default security configuration of CRX 2.0 is used. As a workaround use following configuration in repository.xml:

    <SecurityManager class="com.day.crx.core.CRXSecurityManager">
        <WorkspaceAccessManager class="org.apache.jackrabbit.core.security.simple.SimpleWorkspaceAccessManager"/>
        <UserManager class="com.day.crx.core.CRXUserManagerImpl">
            <param name="usersPath" value="/home/users"/>
            <param name="groupsPath" value="/home/groups"/>
            <param name="defaultDepth" value="1"/>
        </UserManager>
    </SecurityManager>

The SimpleWorkspaceAccessManager will give authenticated users access to any workspace. Please also read the regular CRX 2.0 LDAP Authentication documentation for additional changes and deprecated configuration parameters.

The access manager in the default repository configuration of CRX 1.4.x (com.day.crx.core.CRXSecurityManager) is deprecated. The configuration will still work, but the 'defaultSecurityLevel' configuration parameter is not supported anymore in CRX 2.0. The replacement class is org.apache.jackrabbit.core.security.DefaultAccessManager. As of CRX 2.0 one must use the WorkspaceSecurity configuration element to control the default permissions on a workspace. The default WorkspaceSecurity configuration (i.e. when missing) for CRX 2.0 is:

    <WorkspaceSecurity>
        <AccessControlProvider class="org.apache.jackrabbit.core.security.authorization.acl.ACLProvider">
            <param name="omit-default-permission" value="true"/>
        </AccessControlProvider >
    </WorkspaceSecurity>   

To configure CRX 2.0 that it grants read access to everyone per default, use the following configuration:

    <WorkspaceSecurity>
        <AccessControlProvider class="org.apache.jackrabbit.core.security.authorization.acl.ACLProvider"/>
    </WorkspaceSecurity>

It is recommended to install the Java Out-of-Box tool when using Communiqué on HP-UX. The tool is recommended by HP for running large, server-side applications. It tweaks the system's default configuration to provide better «Out of the Box» behavior for Java.

• Day Software at day.com
  
• CQ5 Product Page on day.com
  
• dev.day.com Developer Community
  
• CQ5 Documentation on docs.day.com

These sites are only available to customers. If you are a customer and need access, please contact your Day account manager.

• DayCare at daycare.day.com
• Product Downloads at daycare.day.com

Copyright © 1993-2010 Day Management AG, Switzerland - All rights reserved

This Software is protected by copyright law and international treaties. This Software is licensed (not sold), and its use is subject to a valid WRITTEN AND SIGNED Communiqué® License Agreement. The unauthorized use, copying or distribution of this Software may result in severe criminal or civil penalties, and will be prosecuted to the maximum extent allowed by law

Remote Verification. You acknowledge and agree that the Software may contain verification and reporting functionality that allows the remote reporting of your usage of the Software for the purpose of verifying your compliance with these terms and conditions. If remote verification reveals that you are using the Software in violation of these terms and conditions, you agree to cease such unauthorized use and to pay Day's reasonable expenses and a penalty fee associated with such remote verification and your unauthorized use.

DAY, the DAY logo, Communiqué, ContentBus and CRX Content Repository Extreme are registered trademarks and service marks, or are trademarks and service marks, of Day Management AG, Switzerland, in various countries around the world.

All other product names and company logos mentioned in the information, documents or other items provided or available herein may be the trademarks of their respective owners.