Run LiveCycle installer and complete installation , before running LCM follow as mentioned in next step
Go to <LC_Root_Directory>/jboss/server , create a copy of lc_turnkey under the same folder but with different name .. say lc_publish_turnkey (Publish instance needs a separate JBoss profile so this new profile can be used for publish instance)
Now run LCM and complete the configuration manager – After completing LCM run You will have Author instance of CM up and running , now you need to perform few more steps to have author and publish running on same machine and configured to talk to each other
LCM creates a folder with name crx-repository under <LC_Home_Directory> which is used as a repository for author instance
Create a new folder under <LC_Home_Directory> with name “crx-publish-repository” (without quotes) , Go to <LC_Home_Directory>\configurationManager\export\crx-quickstart and copy install folder along with it’s contents and paste it under <LC_Home_Directory>\crx-publish-repository such that the contents under publish repository would appear like this after pasting the contents <LC_Home_Directory>\crx-publish-repository\install\
Go to <LC_Home_Directory>\configurationManager\export Copy adobe-livecycle-cq-publish.ear file and paste it in <LC_Home_Directory>\jboss\server\lc_publish_turnkey\deploy folder
Start lc_publish_turnkey profile from command prompt using command as “run -c lc_publish_turnkey -Dcom.adobe.livecycle.crx.home=”C:/pathToLCHomeDirectory/crx-publish-repository” -Djboss.service.binding.set=ports-01 -b 0.0.0.0” [o is zero in case you try to copy paste this content]
For the first time start up of publish instance , It takes around ten minutes to completely start as it unpacks packages and creates repository , When the server is up and running You can use following URLs to log on to author and publish systems
LiveCycle Correspondence Management solution users often use text content from MS-Office applications like Word and Excel.
The text content can be copied from MS-Office applications and pasted to Rich Text Editor of Correspondence Management.
Currently the content copying is supported but any rich text formatting applied to the text in external applications like MS-Office applciations will not be retained.
If the user copies (to clipboard) below content from MS-Word
and pastes it in CM text content area of Rich Text editor , the text would appear like
Lot of customers are asking us to provide a functionality to copy paste content from MS-Office applications that supports copying of text content along with the formatting. This is currently on the roadmap but there are no fixed timelines when this feature would be available in the product.
First version of LiveCycle Correspondence Management solution was delivered along with LiveCycle ES2 service pack 2.
Based on the customer feedback and requirements from various existing and prospective customers lot of new features have been added and existing features have been improved in Correspondence Management solution.
If you are an existing customer of Correspondence Management but are on LiveCycle version earlier to ES3 , Here are the 20 reasons why you should consider upgrading to LiveCycle ES3 Correspondence Management.
If you are a LiveCycle ES or LiveCycle ES2 customer and considering to buy and implement Correspondence Management as well , Here are the same 20 reasons why you should consider upgrading LiveCycle as well in order to make use of latest Correspondence Management solution.
(Please click the image to enlarge it and clearly view the content)
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
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.
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 http://get.adobe.com/flashplayer/
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)
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
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 xx.xx.xxx.xxx 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 )
Once the above entries are made in hosts file one can access the author and publish instances as below
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.
If you are a user of Customer Experience Solutions and need any help/information about Customer Communications , Please post your queries or issues and get immediate responses from experts on CC user forums
Adobe® Digital Enterprise Platform (ADEP) offers an integrated set of capabilities and technologies that enable organizations to create Customer Experience Management solutions.
ADEP comprises of two servers :
Document Server : All the services related to documents and process (of earlier LiveCycle) are now part of ADEP Document Server
Experience Server : All Solutions (applications) and content are part of Experience Server [ Solutions like CM & ICR used Alfresco based Content Services to store all the content in earlier versions , now they use Day’s [now part of Adobe] CRX content repository to store all the content]
Architecture diagram :
For more information on understanding ADEP architecture refer documentation
Installation of Experience server is as simple as a double click.
What is Correspondence Management : Procedures established for systematic dispatch, receipt,filing, storage, retrieval, and disposition of communicationrecords. (source www.businessdictionary.com)
The Customer Communications Correspondence Management Solution (part of Adobe Digital Enterprise Platform ) streamlines personalized correspondence creation and management. It is an enterprise software for B2C , B2B , G2C applications. It can be used in wide array of industry sectors like BFSI and Government.
Correspondence Management Solution helps businesses & Governments meet all their correspondence management needs , both System generated correspondence like payment reminders , trade confirmations etc.,. and User Generated Correspondence like insurance policy , welcome kits etc.,.
It centralizes and manages the creation , assembly and delivery of correspondence, It helps organizations
Create personalized & tailored communications from predefined content to templates
Mitigate compliance and regulatory risk through usage of pre-approved content
Decrease IT dependency – Business users can create and manage correspondence templates, speeding up process significantly