Basic CQ5 code examples

- Feike Visser, Technical Architect @Adobe

In this blogpost I will go through some sample code that you can use in your components, all samples are available out of the box.

So there is no need to write custom code in OSGi bundles for these samples.

Make sure you have this line at the beginning of your component:

This global.jsp defines a set of global taglibs and makes a number of objects available that you can use via.

—————

Read the complete post at the Experience Delivers blog.

5.5 upgrade resets author password to author.

If you are upgrading to CQ 5.5, make sure you change passwords to all users.

Otherwise, you'll open up your author instance to the public.

For example, you can login here as author:author http://author:author@author.day.com

--------

Read the original blog post at My Day CQ Community.

Midnight at the lost and found

- Sensei Martin

Have you worked out that TAR Optimiser does not run at midnight? Normally, the OOTB default for running the TAR optimiser is 2am - 5am. This can be changed in the repository.xml/workspace.xml files. But, if you specify a start time of 00:00 it won't run. I'm sure I've posted this elsewhere but just to re-iterate you can make the TAR optimiser run faster & do more work by reducing the optimizeSleep parameter. We've managed to get away with 0.25 without any noticeable performance impact to the live servers (CQ 5.3).

-----------

This tip was originally posted at the My Day CQ Blog.

What’s new in Cloud Manager 1.1

Adobe has just released Cloud Manager 1.1, an enhanced version of the SaaS offering that enables reduced time and costs for provisioning, managing, and metering Web Experience Management (WEM) solutions for digital marketing initiatives. This new version rolls out the following major enhancements:

  • Rackspace support: In addition to Amazon EC2, Cloud Manager 1.1 now supports Rackspace Cloud Hosting.
  • Enhanced cloud deletion: You can now delete CQ clouds even if they have online backups. You can also remove failed or inconsistent clouds from the Clouds dashboard.
  • Numerous other bug fixes and improvements…

For more information about using Cloud Manager, refer to the documentation. If you have a question, post it on Adobe forums.

————

Read the original post at The Doc Fox.

Viewing CQ server logs for a system hosted on Cloud Manager

- Samartha Vashishtha

To understand how you can view logs for a CQ Cloud Manager authoring server, look no further than this useful forum topic.

For more top issues and FAQ related to Adobe CQ Cloud Manager, see this documentation article.

-------

Read the original post at The Doc Fox.

CQ5 – Command Line Admin

- Jochen Toppe

It’s so rare that I post here, it’s almost criminal. While researching how to best automate cloud-based installations of CQ5, I ran across these sweet command line tools to change passwords and setup replication agents. I figured they’d be worth sharin 8-)

They’re right here on github.

---------

Read the original post at Jochen Toppe's blog.

Handling DELETEs which flush the dispatcher cache

- Sensei Martin

I have been working on the following problemette, which was posted to the DAY-CQ mailing list on Google.com :-

Hi CQ Community,

Does anyone know how to stop the dispatcher invalidating on a DELETE command down a path?

The reason why I ask is because we have a lot of usergenerated content which is being reverse replicated. When the UGC is moved, for security, from /content/usergenerated to /content/mysite/blah/blah, then the /content/usergenerated/... node is deleted on the publish server. Each of these delete commands triggers the flush agent.

I have tried defining a rep:policy to deny jcr:all on a user in /content/usergenerated/. This works for node additions but, deletions are not recognised. So I cannot stop it here.

I have tried to alter the configuration in the /invalidate section of dispatcher.any file to no avail. Is this sdection defining what objects get invalidated rather than what objects trigger an invalidation?

I also noticed that in the release notes of the dispatcher the following, which makes me think that invalidate on delete might be hard-wired ...

Issues resolved in 4.0.5:

25169 - Support flush on every write

Any help would be greatly appreciated!

...

---------

Read the complete post at My Day CQ Blog.

Cloud Manager: How are Pause and Stop operations different?

- Samartha Vashishtha

When you pause a cloud, the cloud provider doesn’t charge for CPU cycles anymore. However, you are still charged for the allocated storage (for example, Amazon EBS volumes). Paused clouds are displayed in the Clouds dashboard with a yellow status.

However, when you stop a cloud, no memory, EBS storage, or instances remain allocated to it anymore. However, online backups for the stopped cloud are still retained and can be restored. The cloud provider continues to charge for the saved online backups. Stopped clouds are displayed in the Clouds dashboard with a red status.

For more FAQ related to Cloud Manager, refer to this documentation topic or consult this forum.

----------

Read the original post at The Doc Fox.

CQ Cloud Manager is here!

- Samartha Vashishtha

Adobe has announced the general availability of CQ Cloud Manager, Software-as-a-Service (SaaS) that enables reduced time and costs for provisioning, managing, and metering Web Experience Management (WEM) solutions supporting digital marketing initiatives. Cloud Manager takes advantage of cloud computing technology, such the Amazon Web Services (AWS) public cloud, to start up CQ clusters quickly and consistently.

Using CQ Cloud Manager, Digital Marketing organizations can provision and deploy instances of their Web environment without having to procure hardware or pay large upfront costs. This ease of provisioning allows enterprises to rapidly engage customers, drive market shares, and focus on innovation.

The infographic below captures the overall CQ Cloud Manager framework:

 

To know more about Cloud Manager or to learn how to use it, refer to the documentation.

------------

Read the original post at The Doc Fox.

Using JSONWriter objects to display Adobe CQ OSGi data

- Scott Macdonald

You can create an org.apache.sling.commons.json.io.JSONWriter instance to invoke Adobe CQ OSGi bundle operations and display data within a JSP. A JSONWriter instance lets you define value and key methods to retrieve data. You can create an Adobe CQ component that uses a JSONWriter instance to submit data to an OSGi bundle operation and get back the results. You can then display the results in a JSP. That is, you can dynamically display data based on user input.

For example, consider the OSGi bundle that uses web services to return weather information. (For information about this OSGi bundle, see  http://scottsdigitalcommunity.blogspot.ca/2012/05/creating-adobe-cq-bundles-that-consume.html.

Note: The OSGi bundle that returns weather data uses web services to expose various operations that return weather data. To follow along with this development article, you must create the weather OSGi bundle by following that article.

....

----------

Read the complete post at Scott's Digital Community.


Copyright © 2012 Adobe Systems Incorporated. All rights reserved.
Terms of Use | Privacy Policy and Cookies (Updated)