Archive for November, 2011

Adding user images in ICR Solution Interface

This blog post is part of the series on customizing the Adobe Integrated Content Review solution.


Any entity of the Integrated Content Review solution like, a campaign, a project, or an asset, includes many participants or team members. The participants at any level in the campaign hierarchy include participants from lower levels. In other words, a campaign includes all the participants of a project. A project, in turn, includes all the participants of the assets within it. Additionally, at any level in the campaign, a participant can be added directly to the team list.

To view/add team members at any level in a campaign, click an entity in the Gantt chart and then click the Resources tab. A newly added team member may not have an avatar image. An instance is shown below:

Newly added user does not have an avatar

Newly added user does not have an avatar

Understanding the naming convention of the image files

The images display only if the image files are named using the canonicalname_domainname convention. To know the value of domain name and canonical name, follow these steps:

  1. Navigate to http://localhost:4502/crx/index.jsp.
  2. Log in using the credentials of the user whose domain name and canonical name is to be determinded.
  3. The UserID is displayed of the format lcu::domainname::canonicalname. Note the domain and canonical names from the string.

For example, for an administrator the name is displayed as lcu::DefaultDom::SuperAdmin. Hence, the domain name is DefaultDom and canonical name is SuperAdmin.

Adding an image

Let us add an image for a newly-added user named Shashank Kapoor.

  1. Navigate to ICR_SOURCE/integratedcontentreview/package_data/content/icr/assets/user-images.
    Note: ICR_SOURCE folder is the folder where you extract the provided source code of the solution interface. Refer to this help page to read more.
  2. Add an image with the file name shakapoo_DefaultDom.jpg.
    Note: To update an existing image, replace the image file with a new image file. The image file is scaled to 45 x 58 pixels in size. The image filenames are case sensitive.
  3. Create a directory named shakapoo_DefaultDom.jpg.dir.
  4. In this directory create a file named .content.xml. Add the following code to it:
    <?xml version=”1.0″ encoding=”UTF-8″ ?>
    <jcr:root xmlns:jcr=”″ xmlns:nt=”″ jcr:primaryType=”nt:file”>
    <jcr:content jcr:primaryType=”nt:unstructured” />
  5. Save and deploy the customized solution interface. To know more, refer to this article.

After updating the image for the above instance it shows in the solution interface as shown below:

User with an avatar image added

User with an avatar image added

Read more about adding team members here, in the ICR solution guide.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Adobe Digital Enterprise Platform | Documentation Updates | October, 2011

This October carries festivities galore, the onset of winter, and, not to forget, a fresh set of important documentation updates for Adobe Digital Enterprise Platform. Here’s a summary of all the updates that are now live and accessible on the ADEP Documentation Home Page.

  • Upgrading to Document Services: The upgrade documents had significant updates, particularly concerning topics related to Business Activity Monitoring. As the cookie crumbles, ADEP Document Services is the last release to support Business Activity Monitoring and, hence, the BAM server cannot be upgraded, but it can certainly be reused to work with the new Document Server. See the Upgrade to Document Services documentation.
  • Connector for SharePoint: All sites on the SharePoint server are available for configuration for all Document Services features by default. A new feature for the Connector for SharePoint allows you to restrict configuration and usage of Document Services features on a specified SharePoint site. The Configure ADEP Document Services – Connector for SharePoint tells you how you could do this.
  • Plug-in for Hyperic HQ: Hyperic HQ allows you to monitor and manage your web infrastructure, server, services, and devices of ADEP Document Server. See Using the plug-in for Hyperic HQ, a new document, to know more about Hyperic HQ, its installation and usage procedures.
  • Action Script Reference was refreshed with addition of new Packages and APIs for Customer Experience Solutions (Correspondence Management and Integrated Content Review in particular).
  • Correspondence Management Developer’s guide had significant updates. The guide now has download locations of all jar files’ required to set up your development environment for the Correspondence Management solution.
  • Disaster recovery for Correspondence Management explains how to back up and restore your Correspondence Management data.

Until the next time we have more updates, Adios!

ADEP Community Help and Learning Team

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)