Archive for March, 2013

Quick and Easy steps to run Author & Publish Systems of Correspondence Management ES4

Steps to setup Correspondence Management system with author and publish instances configured

It’s recommended to perform these steps on your development system where you would like to  have a setup in less amount of time to get started with the application

For stage, UA or prod systems please follow the detailed install & config guides

 

  1. Run LiveCycle installer and complete installation , before running LCM follow as mentioned in next step
  2. 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)
  3. 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
  4. LCM creates a folder with name crx-repository under <LC_Home_Directory> which is used as a repository for author instance
  5. 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\
  6. 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
  7. 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]
  8. 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
  9. Author Manage Assets UI – http://hostname:8080/lc/cm , Publish Manage Assets UI – http://hostname:8180/lc/cm (You can login as default super admin i.e administrator/password – Change the password if needed)
  10. One last setting before you are done – Go to http://authorinstancehostname:8080/lc/etc/replication/agents.author/publish.html  , Login as admin\admin , Click Edit , Go to Transport tab and modify URL to http://localhost:8180/lc/bin/receive?sling:authRequestLogin=1 , Click OK , Click Test Connection and ensure that you see success message

Now you have running Correspondence Management system with author instance running on port 8080 and publish instance running on port 8180

 

Santosh

Adobe LiveCycle ES4 is now GA

 

We have proudly announced the release of LiveCycle ES4 last month and now it is now GA (available to general market via web and physical media)

Adobe LiveCycle ES4 extends the business processes to clients using smart phones or tablets.

 

Watch this five-minute video to check out the major new features available in LiveCycle ES4

(refresh the browser in case you are unable to view the video preview below)

 

LiveCycle ES4 has two new modules – LiveCycle Forms Pro and LiveCycle Forms portal. An all-new PhoneGap based Mobile Workspace app is delivered with ES4.

There are loads of features that are included across the LiveCycle modules. These are new features and also some features which were delivered as CCRs on previous releases.

There are numerous additions to platform matrix. LiveCycle is now supported on AIX 7.1 and RHEL 6 in addition to the list of OSes that we already certified and supported till ES3. ES4 is certified on a new version of Oracle Weblogic application server (12.1.1 ) in addition to all the application servers and specific versions that were certified till ES3. Official support is added for lot of new LDAP servers. Chrome is now in the list of officially certified and supported browsers. Check the platform matrix for the full list.

 

The current version of LiveCycle provides a better ROI (than earlier versions of LiveCycle) to the existing and new customers.The customers who are on earlier LiveCycle releases can quickly contact support and plan for the upgrade. 

 

Links to some important resources:

  1. What’s new in ES4
  2. Full Product Documentation
  3. Install Docs
  4. Platform Matrix
  5. Trial Download site
  6. LiveCycle Forums

 

Correspondence Management Letter Preview Issues in Chrome and Firefox

 

If you are unable to preview the letter in Correspondence Management Create Correspondence UI and wondering what might have happened – this blog tries to explain the reason behind it

If you are using Chrome , you may be seeing the issue as shown in the below screen shot

Letter preview in Chrome

Chrome Preview

 

 

 

 

 

 

 

 

If you are using Firefox , you may be seeing the issue as shown in the below screen shot

 

Letter preview in Firefox

Letter preview in Firefox

 

 

 

 

 

 

 

 

When a letter is opened for preview the Create Correspondence UI opens and this UI is split in to two halves

On the left hand side the contents that are used in the letter are shown in the Flex UI and on the right hand side the preview of final correspondence is shown as PDF

In order to display the PDF on RHS one would need PDF plug-in in the browser that is being used.

The latest versions of modern browsers like Chrome and Firefox have their own in-built PDF Viewers

Chrome’s inbuilt PDF viewer is Chrome PDF Viewer , Latest versions of Firefox has a PDF.js plug-in which shows the PDF in html form

 

The PDF that is shown on the right hand side of create correspondence UI is an XFA form based PDF and the built-in PDF viewers of Chrome and Firefox do not support the preview of these PDFs

The solution to resolve this issue is to set Adobe’s Acrobat/Reader plug-in as the default plug-in to open PDF files inside the browser

 

Follow the below steps to set Acrobat/Reader plug-in as default plug-in to open PDFs in Chrome

1. Open Chrome browser

2. type chrome://plugins in omnibar and press Enter

3. If Chrome PDF Viewer is enabled , you should see something as below in your browser (Notice the Disable on Chrome PDF Viewer – which means it is currently enabled , user can click the link to disable it)

Chrome Plugins

Chrome Plugins

 

 

 

 

 

 

3. Disable Chrome PDF Viewer and Enable Adobe Reader PDF plug-in , after Reader plug-in is enabled you should see something as below in your browser (In this example Adobe Reader is shown but if you have Acrobat installed on your system , the Acrobat plug-in should be enabled)

Chrome Plugins

Chrome Plugins

 

 

 

 

 

 

4. Try to preview the letter again after Reader plug-in is enabled , The letter should render fine now

 

Letter preview

Letter preview

 

 

 

 

 

 

 

 

Follow the below steps to set Acrobat/Reader plug-in as default plug-in to open PDFs in Firefox

 

1. Open Firefox browser

2. type about:config  in address bar

3. type pdfjs in the browser search box

4. In the preferences, select pdfjs.disabled – the option would be enabled by default , set it to false

aboutconfig

aboutconfig

 

 

 

 

 

5. Also in the preferences , ensure that the Acrobat/Reader is selected as the application to open PDF files

6. Restart the browser

 

If the above steps are followed to set Acrobat or Reader PDF plug-in as the default of Chrome or Firefox then the XFA form based PDF would appear properly on the RHS of the Correspondence Management Create Correspondence UI

Letter preview

Letter preview

 

 

 

 

 

 

 

 

Note : In case if the PDF viewer is properly configured to Acrobat or Reader plug-in but if you still see issues in viewing letters there could be some other issue.

 

I will post a seperate blog to investigate how the letter preview issues can be debugged … stay tuned….

 

 

 

 

 

 

Create Correspondence UI view preferences

 

Correspondence Management create correspondence UI is split in to two columns.

LHS shows the contents that are used in the letter and RHS shows the PDF preview.

CCR view has a drop down that changes the view on left hand side to data entry view or content view based on value selected in the drop down

Create Correspondence UI

Create Correspondence UI

 

 

 

 

 

There is some logic that determines the default view on left hand side (Flex UI) and shows content view or data view depending specific to letter

If a letter contains only layout fields that are user fillable – default view is data entry view

If a letter contains any content (like text , condition , image and/or list ) – default view is content view

There are some customer use cases where they always want the default view to be data even if the letter has content data modules.

To enforce Create Correspondence UI to always show data entry view (by default) follow the steps mentioned below :

 

  • Log on to CRX DE Lite http://hostname:port/lc/crx/de/index.jsp as admin
  • Navigate to /content/cm/tbxeditor-config.xml
  • set ccr default view as DATA (default would be AUTO , change it to DATA)

<!– In Create Coorspondence UI, LHS should default to what view: DATA|CONTENT|AUTO–>

<CCRDefaultView>DATA</CCRDefaultView>

  • Click Save All
  • Repeat the above steps on all instances (author & publish)
tbxeditor-config

tbxeditor-config

 

 

 

 

 

 

 

Now for any letter preview the default view would be data entry view (data is selected in the drop down by default) but users can switch to content view by changing the value of drop down to content

some customers had a requirement to completely hide the content tab , I will blog a separate post to select the default view to data and completely hide the data/content drop down

stay tuned…