LiveCycle ES3 Trial downloads

The trial version of latest LiveCycle release i.e LiveCycle ES3 is available to partners and customers for download at livecycle devnet downloads

The trial download includes

  1. Installer for LiveCycle ES3 & LiveCycle ES3 Data Services
  2. Development tools — Workbench & Designer
  3. Reader Extension test credential
  4. Acrobat X Pro


For more information about What’s new in LiveCycle.

LiveCycle ES3 supported platform combinations

Adobe LiveCycle ES3 is supported on around 32 platform combinations (Operating System , Application server , Database , JDBC driver , OS architecture and JDK combinations)

Turnkey install , config and deploy is supported on two Operating Systems viz Microsoft Windows 7 and Microsoft Windows Vista (for evaluation and development purposes)

Full list of supported platforms combinations is available on Adobe LiveCycle help documentation

Adobe announces release of LiveCycle Enterprise Suite 3

Adobe has announced release of Adobe® LiveCycle® Enterprise Suite 3 (ES3) software on March 13  2012. Here is the link to press release

Document and DataServices capabilities of Adobe Digital Enterprise Platform (ADEP) are not part of Adobe LiveCycle ES3

Click here to access Online help documentation for ES3 is available

A link will be provided soon with details to download a trial for those who would like to try the new features of Adobe LiveCycle.

There are lot of new features in various document services of Adobe LiveCycle ES3 and it’s Correspondence Management Solution.


How to create post-process for Correspondence Management

Each letter in Correspondence Management can be associated with a post-process. A post-process is nothing but a LiveCycle orchestration with a specific requirement on the input/output parameters.

Sometimes one may wonder that the orchestration that one has created on LiveCycle does not appear in the drop-down of Letter Editor

If the orchestration has two input parameters i.e inPDFDoc , inXMLDoc & one output parameter i.e redirectURL then it will appear in the Letter Editor drop-down.

LiveCycle Correspondence Management Post-Process

LiveCycle Correspondence Management Post-Process


The above picture shows a sample post-process , The variables highlighted in a red rectangle are mandatory and are minimum requirements for Correspondence Management to recognise the orchestration as the one which is intended to be used with Correspondence Management Solution

One can add additional variables depending up on the logic and operations the orchestration does.

Fore more details on creating post-process visit our online help docs

Data Dictionary Best Practices

Correspondence Management DataDitionary provides a representation of the underlying data structure of a complex backend enterprise system in a simple and user-friendly manner which business users can easily understand.

In any enterprise implementation of Correspondence Management usually middle ware developers work on creation of data dictionary.

We get requests from our customers to understand the best practices for creation of DataDictionary.

The answer is try to Keep It Simple.

  1. Do not try to create a single Data Dictionary with tens of thousands of elements to cater to the needs of all the correspondences
  2. If there is a possibility to create multiple data dictionaries by logically separating the correspondences based on business units / business needs , prefer to create multiple data dictionaries.
  3. If a single complex data dictionary is created (even if there isn’t a real need) , there would be some trade-off in the form of performance for some operations like Publishing the datadictionary and preview of letters that use this data dictionary.
  4. Do not try to over complicate the data dictionary by creating too many levels down the hierachy and do not even use a DD which is completely flat.
In case of any confusion or more queries , feel free to post your queries on Adobe LiveCycle forums.


Flash player release or debug ?


LiveCycle Correspondence Management Solution has a Flex based user interface which works with Flash Player version of 10.2 or above.


Though Flash Player is installed almost on every internet connected PC , often some Correspondence Management solution users have following questions in their minds

1) What is the version of Flash Player plug-in installed in my browserr?

2) Is the Flash Player plug-in that is installed in my browser a release version or a debug version?

When users log on to Correspondence Management Solution http://hostname:port/cm/manageassets.html , Correspondence Management Asset Manager UI is loaded only if FlashPlayer 10.2 or higher is installed if not users are prompted with a URL in their browser to get a latest version of Flash from Adobe’s website.


latest version of Flash Player can be downloaded from

If FlashPlayer is already installed it’s easy to check which version of it is installed

1) If you are connected to internet just click here to check what version of Flash Player you currently have and what is the latest version available

2) If you are not connected to internet , Once you log on to CM solution , Right Click anywhere on Manage Assets UI , If the FlashPlayer is of debug version you would see a menu item ‘Debugger’ in context sensitive menu , If not it means the Flash Player that is installed is a release version. Version number of Flash Player is also displayed on the context sensitive menu (see the below image)


Connection Error


Developers who are working with Correspondence Management solution would have encountered these errors when working with author and publish instances (see the screen grab of error below).



These errors will be seen when Author and Publish instances of Correspondence Management solution are run on same machine and if one tries to work with both author and publish instances in two different tabs of same browser. This is quite common on a development system but not on production systems.

These errors can be avoided in different ways

1) Instead of accessing author and publish with same name or IP in browser’s address bar , One can use an IP address for one instance and FQDN for another instance i.e

http://fqdn:author-port/cm/manageassets.html (for author)

http://ipaddress:publish-port/cm/manageassets.html (for publish)

2) One can use two different browsers , one for accessing author instance and another for publish instance

3) Make two entries in hosts file with same IP address but different names , i.e if one’s client machine’s IP address is one can add following entries in the hosts file of client machine from where the author and publish CM instances are accessed via browser and access the author and publish instances with their names provided in hosts file

e.g entries in hosts file (If the system is Win XP the hosts file will be under %SystemRoot%\system32\drivers\etc\ folder )    author    publish

Once the above entries are made in hosts file one can access the author and publish instances as below




Future of Correspondence Management Solution

We ( Correspondence Management Solution team ) are currently working hard to add numerous features that are requested by various customers in to the solution. These features will be part of next Adobe LiveCycle release and available out-of-the-box to new customers and customers on previous versions can upgrade to this version to make use of these new features

We have recently released first service pack of ADEP Document Services which is available for download at this link

Adobe has recently outlined growth strategy with increased focus on Digital Marketing and Digital Media opportunities.

To know more about future investments and priorities on Adobe LiveCycle visit Arun’s (VP & GM) blog

ADEP Solutions YouTube Channel

If you are interested in learning about new features/functionality of ADEP solutions like Correspondence Management or Integrated Content Review you can go through this YouTube Channel


If you are interested in getting any updates related to ADEP Solutions you can follow ADEP Solutions facebook page







Deploying CM on production server

Experience Server Solutions QuickStart provides some sample collateral and creates some sample users so that developers can directly start using the OOTB reference application and make use of samples to know about and learn the product capabilities, *but* It is highly recommended to remove these sample assets and sample users when the solution is deployed on to a production server.


I will take you through the steps to remove:

1)      Sample assets from the system and

  1. By uninstalling them from package manager
  2. By Removing sample assets package from SQS

2)      Sample users from the system

  1. Removing sample users from CRX user administration
  2. modifying a configuration file


Removing Sample assets & sample users from a production system:

There are two ways to remove the sample assets from the system one can follow any way that suits them.

Steps to remove sample assets and sample users from a running server:

1.a. Removing Sample assets by uninstalling them from package manager [Please do not start SQS as a publish instance till the step it is specified to do so]

  • Go to http://[hostname:port]/crx  (on author instance)
  • Login as admin
  • Click Package Manager
  • Click on Package with name “”
  • Click More dropdown in action bar (This action bar has other actions like Edit Build etc.,. , More option is in the right most area of this bar)
  • Click Uninstall
  • Click Uninstall again on confirmation dialog
  • Wait for sometime till you see a message like “Package uninstalled in <some>ms” in the Activity Log
  • Now if you log on to CM Manage Assets UI , you will not see any sample assets. If you are still seeing them then clear your browser cache and then try.

2.a Removing sample users from CRX user administration

  • Go to http://[hostname:port]/crx (on author instance)
  • Login as admin
  • Click User Administration
    • CM creates following users OOTB
      • Todd Goldman (tgoldman)
      • Caleb Lopez (clopez)
      • Gloria Rios (grios)
      • Frank Kricfalusi (fkricfalusi)
      • Jocelyn Robinson (jrobinson)
      • Heather Douglas (hdouglas)
      • In user administration dialog , Navigate to each of these users and click Remove user , Now if you try to log on to CM Manage Assets UI with any of the above usernames , You are not allowed to login

After completing steps mentioned in 1.a & 2.a , You can start the publish instance , Follow the steps mentioned above in 2.a and remove sample users from publish instance as well.


Now I will take you through the steps 1.b & 2.b in order to stop creation of sample assets and sample users by making some changes in SQS jar

Steps to remove sample assets and sample users from SQS when server is down (or not even started once):

1.b Steps to stop sample assets creation

  • Open SQS jar using a zip utility
  • Navigate to <SQS jar>\static\repository\install
  • Open solution-correspondencemanagement-pkg-<version>.zip file
  • Navigate to solution-correspondencemanagement-pkg-<version>.zip\ jcr_root\etc\packages\adobe\aep\solutions
  • Select samples-correspondencemanagement-pkg-<version>.zip
  • Click Delete
  • Save the changes to jar
  • Re-open the SQS jar with any zip utility and validate that the samples-correspondencemanagement-pkg-<version>.zip is not shown in the location from where you deleted it
  • This package creates sample assets , If we delete it we can stop the creation of sample assets on production system

2.b Steps to stop creation of sample users

  • Open SQS jar using a zip utility
  • Navigate to <SQS jar>\static\repository\install
  • Open solution-correspondencemanagement-pkg-<version>.zip file
  • Navigate to solution-correspondencemanagement-pkg-<version>.zip\ jcr_root\etc\packages\adobe\aep\solutions
  • Open template-correspondencemanagement-pkg-<version>.zip
  • Navigate to template-correspondencemanagement-pkg-<version>.zip \jcr_root\apps\solutions\cm
  • Edit CMGroupsAndUsers.xml to make following changes
    • Remove the below section from xml [Remove block and lines highlighted here]


  • Use the modified xml in template-correspondencemanagement-pkg-<version>.zip
  • Save changes to SQS jar
  • Re-open the SQS jar with zip utility and check that the changes to CMGroupsAndUsers.xml are properly saved

Now use this SQS jar to run author and publish instances , Sample assets and sample users will not be created after these changes



These steps are just to give an overview, Please do not follow them as is on any production server. Contact ADEP Engineering/Support/PS before you try these on a production system so that they can provide more and in-detail steps to achieve this, which best suits your deployment topology and any other specific needs.