CQ Cloud Manager July 2012 version released!

The July release of Adobe CQ Cloud Manager is now out! This version rolls out the following new features/enhancements:

  • Full support for Rackspace Cloud Hosting (backup, scale, and delete CQ clouds)
  • Scale Publish tiers with auto-replication
  • Support for 7 Amazon Web Services (AWS) regions and 4 instance types
  • You can now remove CQ clouds with backups
  • Some UI enhancements

Refer to the documentation for more information.

Viewing CQ server logs for a system hosted on Cloud Manager…

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.

New CQ best practice articles now live!

We’ve just published the following three CQ best practice articles:

These articles are the first few in the CQ best practices series. In the days to come, we’ll post more best practices, tips, and tricks that you can apply to your work.

Stay tuned!

 

Cloud Manager: How are Pause and Stop operations different?

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.

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.

CQ Cloud Manager is here!

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.

Correspondence Management: Adding custom asset action buttons

The Correspondence Management solution lets you add new actions to the Manage Assets UI for a particular asset type. The following broad steps are involved in this process:

  1. Modify the asset FML
  2. Extend the asset handler
  3. Register the modified asset handler
  4. Rebuild and redeploy the solution template

Details, including code snippets, are available here.

Correspondence Management: Move active assets betwixt systems

Correspondence Management 9.5 now lets you conveniently move active assets from one system to another. You can export the selected assets from the source system as a ZIP package and import the ZIP package into the target system.

This functionality is useful in several scenarios; for example, when you’re moving assets from a development environment to a production environment.

Some important considerations to keep in mind:

  • Only active assets can be exported. Further, all the assets to be exported must be on the same Correspondence Management system.
  • For optimal performance, select a maximum of 100 letters for export and ensure that the exported ZIP package size does not exceed 50 MB.
  • The export operation fails if one or more dependent assets for a selected asset are in the archived state. To resolve this issue, refer to the log and modify the selected asset such that it is dependent on the active version of the offending asset instead of the archived version.

You can access the documentation for this new feature here.

Enter special characters in Correspondence Management asset names

Sometimes, you may want to create Correspondence Management solution assets that contain special characters in their names. To do so, you must first define the list of special characters that you want to use in the tbxeditor-config XML file.

Follow these steps:

  1. Log in to the CRX console at http://<servername>:<port>/crx/de/index.jsp as an admin. The default admin credentials are admin/admin.
  2. Edit the content/cm/tbxeditor-config.xml file.
  3. Enter the special characters within the customAssetNameCharset tag. For example, to enable the French character set, enter the special characters À, Î , Ù, etc within the tag.
  4. Save the XML file.
  5. Now, to use any character in the Editor Properties dialog, enter Alt + <ASCII value of the special character>.

Author-instance clustering for Correspondence Management

We’ve added a brand new section to the Installing the Correspondence Management Developer’s Guide explaining how you can set up author-instance clustering for Correspondence Management.

When the Correspondence Management solution is deployed, the author instance runs on the same server as LiveCycle ES3. However, setting up the LiveCycle cluster doesn’t automatically configure the Correspondence Management author-instance cluster. You must set up this cluster manually.

Author-instance clustering has no dependency on LiveCycle clustering. The LiveCycle cluster acts as a backend system for author instance clustering when LiveCycle is integrated with the Correspondence Management solution. The shared nothing mode of clustering is supported for Correspondence Management.

You can read the full technical article here.