Posts Tagged ‘cq’

h1

Ready for Sightly? The new AEM Templating Language

December 7, 2013

If you have been to one of the AEM Tech Events around the world you may have noticed Adobe is starting to heavily push their new templating language that hopefully will be available in AEM starting with the 6.0 release that’s scheduled for the beginning of next year. It also sounds like the templating language may be available for AEM5.6 as well. So what is it all about?

Have a look at the presentation by Gabriel Walt
http://www.adaptto.org/13_dontmessview.shtml

And some of the videos from the Adobe@Adobe blog by Senol Tas



It seems the templating language code-named sightly will bring quite a big change to the developers working with AEM (CQ). The work is more shifted towards the front-end developers – the backend developers will be focusing more on java based development.

Advertisements
h1

AEM 5.6 and Timewarp

March 31, 2013

Adobe CQ (AEM) comes with this handy feature called timewarp – in a nutshell, it allows you to see the page in different versions by adding a timewarp cookie or timewarp parameter to your page. Just go to the sidekick and go to the version tab. Expand the timewarp tab. select a date and time and click go (or timewarp to see a modal with a history of the edits.

If you want to access an older version of the page directly, add ?timewarp=(long) as a time to your URL and you should see the older version.

Starting with 5.6, you may want to exit the timewarp before you do anything else. Going back to the new touch UI projects screen while in the timewarp mode throws an exception (the timewarp is by default set as a cookie and filters the repository accordingly, so this may start to fail).

I’d say Adobe has some work to do here – somewhere along the lines of ‘let’s do the timewarp again’

h1

AEM (Adobe CQ) Performance on different Hardware

March 29, 2013

The other day we ran into a bit of a problem because of storage speed in one of the environments we were setting up CQ5.5 in. It was a VMWare environment with 10GB of ram, 8 CPUs and lots of storage configured for it – however, the storage was configured over NFS. The performance of the storage was very poor until the team mounted the NFS storage on the host operating system and configured a vmdk file as storage for the VM. Now CQ is running fast and smooth.

CQ has a handy tool in the Felix Console to measure disk speed. If I run it on my own computer I get the following output (you can find it at http://localhost:4502/system/console/diskbenchmark , click start, wait for a couple of minutes and then hit stop):

Operation Type Operations Per Second for Block Sizes
256 B 512 B 1 KB 2 KB 4 KB 8 KB 16 KB
write 297 569 1105 2858 16175 15915 14990
read 290468 285605 276539 265199 245365 194254 125938
write 16654 16955 16485 16294 16280 15868 15232
read 289515 285575 274960 260759 246216 192033 126604
write 16687 16481 16507 16076 16243 15812 15494
read 288390 282803 273778 263346 241982 192439 123351
write 16609 16585 16484 16630 16418 15811 15149
read 287073 282856 272822 263683 242169 192894 126518
write 16477 16370 16294 16412 16225 16034 15048

Note: Java7, CQ5.5, Sony Vaio with Intel i7-3682CM @2.2GHz, Win8 wirth a hard disk performance index of 5.9

I ran the same test in AEM5.6, the numbers are about the same. The disk speed test does not test true repository speed but the actual speed of reading and writing files from java to the directory that is specified.

Well, I shared my numbers – please share yours (I’ll post more as well soon) – Would be great to get a nice long list of different servers, developer boxes, os’s, etc compiled here.

Some more numbers

MacBook Air 1.7GHz Intel Core i5, 60GB Solid State Disk
Operation Type Operations Per Second for Block Sizes
256 B 512 B 1 KB 2 KB 4 KB 8 KB 16 KB
write 5097 6752 10098 13113 14913 14868 14419
read 522298 498729 479957 444013 386557 283406 175218
write 15102 15159 14810 14671 15023 14763 14234
read 519715 496583 480427 443306 383299 281750 176323
write 13236 14569 14770 15120 14971 14816 14390
read 524098 498535 484440 442899 389182 284113 175112
write 15251 14893 14755 14784 15086 14784 14429
read 528208 502405 484314 442884 387000 284755 174811
h1

Access to Adobe CQ Package Share without Adobe CQ

March 5, 2013

I meant to post this a while back. We did an install of Adobe CQ in an environment that’s pretty restrictive with internet access and thus we were not able to connect to the Adobe CQ Packageshare website from within CQ. After a bit of digging we found the following URL:

http://dev.day.com/packageshare/packages.html

after logging in you are able to download any of the packages on that site without accessing it through CQ.

Hope this will help others as well.

h1

Adobe CQ Problem Clinic on November 7 2012

October 4, 2012

If you live in Orange County/Los Angeles or the San Diego area and work with Adobe CQ then bring your laptop, your project and your problems with Adobe CQ. We will have a session where you can present the problem you are having and we’ll discuss solutions for the problems and try to find a way to solve them to make your CQ implementations a success.

Adobe support personnel will be at the meetup to help us get through the issues.

We are meeting Wednesday November 7  from 6:30pm to 9pm at the Lake Forest/El Toro Public Library.

For more information about the meetup group and this event go to http://www.meetup.com/OC-CQ-Sling-JCR-User-Group/events/85466292/

Hope to see you there.

h1

Using ticktick.sh to parse Json Responses from Adobe CQ5.5

April 24, 2012

ticktick.sh is a great little shell library that allows you to parse json responses from Adobe CQ. The following script is a simple example that pulls the current status of the installed, active and resolved bundles from the Felix System Console in Adobe CQ and presents the output. This can be used for example to check if the server is up and running. To use, download ticktick.sh, put it in the same folder as this script and run it.

The supported arguments are the credentials (admin:admin) and the url to the server root (http://localhost:4502).  You should see a nice pink status line with the information on how many bundles are active, resolved and installed as well as an error code of  zero if the server is up and a -1 if the server is still starting up.

curl -s -u $1 $2/system/console > /dev/null
if [ $? != 0 ]; then
	echo admin console on $2 not running
	exit -1
fi

. ./ticktick.sh

DATA=`curl -s -u $1 $2/system/console/bundles/.json`

tickParse "$DATA"

#echo ``status``
#echo current status total bundles: ``s[0]``, installed bundles: ``s[1]``, installed fragments ``s[2]``, bundles resolved ``s[3]``, bundles installed ``s[4]``

if [ ``s[4]`` = 0 ]; then

	echo ``status``: server fully up
	exit 0
else
	echo -e "33[2A33[35m"
	echo -n ``status``: server still activating bundles
	echo -e "33[K33[0m"
	exit -1
fi
h1

Developing the style and templates/components in parallel for Adobe CQ5

April 10, 2012

In order to speed up development of a site within CQ5, it helps adopting the following process:

  •  Devise templates and components for the site based on mockups
  •  Implement a standard HTML for all templates and components
  •  Develop the components necessary
  •  Develop CSS/JS necessary to support the components

Using this approach, the front end team can develop the CSS/JS necessary for the site in parallel with the developers implementing the components and templates for CQ5. Instead of using a waterfall model where the front end team develops the basic HTML structure first and then provides the code to the CQ5 developers, this approach makes sure the CSS/JS works well within Adobe CQ.

To further minimize the risk of browser incompatibilities and to make sure the site will also look good on mobile devices from the start, it helps adopting a basic CSS/JS framework, commonly known as grid systems.

Some grid systems to consider are:

The grid systems have a well known html structure and features such as reflow that help on smaller screens. Developing your components with a grid system in mind will also make sure the developed components can be reused in the future with a different stylesheet and make your CQ5 projects faster to implement and easier to adopt to a new site style and new features provided by the grid system.

The Adobe CQ5.5 version uses 960gs for the default geometrixx site, however, choosing twitter bootstrap will provide you with more out of the box functionality commonly found on today’s website.

update: we released a bootstrap templating integration for Adobe CQ 5.5 today. See the following link for more information