Tag Archives: WEM

Developer’s FAQ on CQ5.5

As you are aware the new cq5.5 has been released and below blog is reference to solutions of most frequently asked questions. Upgrade Path Paths for moving from an older version of CQ to CQ 5.5 is available at http://dev.day.com/docs/en/cq/current/deploying/upgrading.html API … Continue reading

Posted in Customer Experience Solutions | Tagged , | Comments Off

How to Rotate the TarJournal in Shared Nothing Clustering

Problem: Your tar journal is growing and consuming a lot of space. Solution: If you are using shared clustering, Please see this. For ‘Shared Nothing’ Clustering, you need the following configuration (If you want rotation to happen after every 24 … Continue reading

Posted in ADEP | Tagged , | Comments Off

Export CQ5.4/WEM Reports to Comma Separated Values (CSV)

The new Reporting Framework in CQ5.4 allows to generate customized reports on all available information. Example to help you monitor and analyze the state of your instance, CQ provides a selection of default reports, which can be configured for your … Continue reading

Posted in Customer Experience Solutions | Tagged , | 3 Comments

Configuring a Custom Location For The WEM Repository

When you install the CQ quickstart, or the ADEP Solutions Quickstart, the repository file structure (and initial repository contents) is created by default under drive:\quickstart installation directory\crx-quickstart\repository\ You can override this behaviour and have the repository created in a custom … Continue reading

Posted in ADEP | Tagged , , , | Comments Off

Configuring WEM to Use a Shared Datastore

If you use the “shared nothing” deployment model, each instance of the WEM content repository has it’s own set of data that is duplicated across all instances. The data storage is divided into three sections, Workspace Store, Journal and Data … Continue reading

Posted in ADEP, Experience Services | Tagged , , , | 1 Comment

What Happens When You Click on WEM / CQ Quickstart JAR File for the First Time (till CQ5.4)

1. The Quickstart is unpacked to the /crx-quickstart directory 2. CQSE is started (this can be accessed using host:port/admin) 3. CQSE starts the CRX webapp (this can be accessed using host:port/crx) 4. The CRX webapp starts the repository 5. During … Continue reading

Posted in ADEP | Tagged , | Comments Off

Some WEM Clustering Q&A

Assumption: The questions below assume that you are using CRX2.2 with Hotfix or greater. Question: Where does the crx.xxx file get created? Answer: On a slave node when it is first joined to the cluster. And this is current … Continue reading

Posted in ADEP | Tagged , , | Comments Off

Bringing Geo-Location to Web Experience Management

Written by Lars Trieloff An undisputed goal of Web Experience Management is the ability to provide meaningful experiences to web site visitors. The definition of “meaningful” is closely related to the context the vistor is operating in. With CQ5’s ClickstreamCloud, marketers and … Continue reading

Posted in Customer Experience Solutions, Experience Services | Tagged , , , , , , , , | Comments Off

WEM – PowerShell Script to Edit Multiple Apache conf Files

A typical Web Experience Management (WEM, formerly CQ5) solution deployment involves the Apache HTTP Server as a load-balancer as well as a caching proxy for the “publish” instance(s). Configuration is typically spread across multiple configuration files, in addition to the … Continue reading

Posted in ADEP, Customer Experience Solutions | Tagged , , , , | 4 Comments

HTML5 file upload in WEM

It’s not a secret feature in CQ/WEM/DAM, but it’s still comparatively unknown – the HTML5-based file upload capability. Editing content is so much more fun if you don’t have to open a dialog [click], navigate through your folder structure [click][click][click] … Continue reading

Posted in ADEP | Tagged , , , , | 1 Comment