Posts Tagged ‘adobe’

h1

AEM 6 SP2 Available

February 6, 2015

Adobe released Service Pack 2 for AEM6. The release notes indicate that jackrabbit oak was updated to version 1.0.9

The following statement in the release notes may also be of interest:

Preannouncement: Removal of CRX2 in next AEM release

AEM 6.0 ships with a compatibility option to run the server with the repository technology that is used in AEM 5.6.1. The documentation also refers to it as CRX2 or Apache Jackrabbit 2.x.

AEM 6.0 introduces the next generation Java Content Repository that the documentation refers to as Apache Jackrabbit Oak or CRX3. It comes with many significant improvements, mainly with regards to scalability, performance and optimizations for AEM capabilities. For more info, please see Introduction to Oak.

Adobe is planning to remove the compatibility option in the next release of Adobe Experience Manager. The update process of the next release will contain the option to switch to the Oak-based repository during the update, that can be used for customers that want to update from AEM 5.x or AEM 6.0 using the compatibility option.

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.

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

Touch Authoring Mode in CQ5.5

May 6, 2012

Since CQ5.4, communique supports a touch authoring mode. When you hit your site with either an iPhone or an iPad you will get a greatly different authoring experience in CQ. The login screen is still similar but when you hit the welcome screen you see a vastly different view:

As you can see above, the welcome screen features the ability to see your inbox and browse the content as well as some configuration tools for replication, workflows, could services and reports – all the features you want on a mobile device.

If you click on browse content you get a mobile tree explorer to navigate your sites and once you open a page, a slimmed down edit environment to review your site, make annotations, etc.

While this is all nice, the question that comes to mind is – is my current site I am working on supporting this feature? It’s a good idea to go and check if your templates still support this extra edit mode. I like to use the ‘user agent switcher’ plugin in firefox to switch my firefox to an iPhone mode and browse the authoring environment for a quick test.

To download the user agent switcher, go to http://chrispederick.com/work/user-agent-switcher/