Author Archive: sankumar

How to obtain EchoSign developer API key

One of the key features of AEM 6.0 Forms is integration with EchoSign service. Any XFA based adaptive form can be configured to be digitally signed using EchoSign service.

During development time you may want create an XFA based adaptive form to see the end-to-end signing workflow. For that one of the pre-requisites is to have an EchoSign API key. You may want to obtain a developer key during development phase before going to production.

I am listing down the steps to obtain an EchoSign Developer API key

  1. Register yourself as an EchoSign developer by filling up this simple form , select the checkbox if you agree to Terms of Use and privacy policy and Click Create my account
  2. You will receive an automated registration email from EchoSign to your registered email account, check your Inbox (spam folder if necessary) and activate the account by clicking the URL provided in the mail
  3. Log on to EchoSign
  4. Navigate to “Account tab” and click “EchoSign API” panel on left hand side tabbed panel items
  5. Copy the API key which needs to be provided when creating a cloud service configuration for EchoSign service in AEM 6.0
  6. The below image shows where to look for API key when logged on to EchoSign

 

EchoSign API Key

EchoSign

 

 

–Santosh

http://about.me/nskumar

Error while starting AEM Quickstart after installing AEM Forms

If you happen to see the following error while starting AEM 6.0 quickstart after installing AEM Forms add-on package (adobe-aemfd–pkg-1.0.78.zip)

 

*ERROR* [FelixDispatchQueue] adobe-aemfd-signatures FrameworkEvent ERROR (org.osgi.framework.BundleException: Activator start error in bundle adobe-aemfd-signatures [402].)
org.osgi.framework.BundleException: Activator start error in bundle adobe-aemfd-signatures [402].
at org.apache.felix.framework.Felix.activateBundle(Felix.java:2202)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2070)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1297)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoClassDefFoundError: com/rsa/asn1/ASN_Exception
at com.adobe.fd.signatures.activator.Activator.start(Activator.java:36)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:2152)
… 4 common frames omitted
Caused by: java.lang.ClassNotFoundException: com.rsa.asn1.ASN_Exception not found by adobe-aemfd-signatures [402]
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1550)
at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:77)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1973)
at java.lang.ClassLoader.loadClass(Unknown Source)
… 7 common frames omitted

 

It is because couple of boot delegation properties not being included in sling.properties file.

 

To resolve these errors , follow the steps mentioned :

  1. Stop AEM server
  2. Add these two properties in sling.properties file under /conf folder

sling.bootdelegation.class.com.rsa.jsafe.provider.JsafeJCE=com.rsa.*
sling.bootdelegation.class.org.bouncycastle.jce.provider.BouncyCastleProvider= org.bouncycastle.*

After restart ensure that there are no errors in error.log file and also status of  AEMFD Signatures Bundle (adobe-aemfd-signatures ) bundle should be in Active state.

 

For more information visit online help docs

 

–Santosh

http://about.me/nskumar

 

AEM 6.0 is live

We are proud to announce the availability of major release Adobe Experience Manager 6.0

AEM has Forms solution which has most of the LiveCycle capabilities running inside OSGi viz.

  • Forms Manager
  • Forms Portal
  • Document Services (Forms,Output,Assembler,DocAssurance [Encryption , Signatures , Reader Extensions] , Mobile Forms)

 

In addition to above capabilities Forms solution has introduced Adaptive Forms with which Form authors can a use browser based Form authoring tool to create HTML5 forms which are adaptive.

For more information about all the solutions of AEM 6.0 refer to blog on experiencedelivers.adobe.com

 

Check out this two and half minute video to know What’s new in AEM 6.0

 

Watch this six minutes video which explains features of AEM Forms

 

Some other useful links of AEM 6.0 :

 

–Santosh

http://about.me/nskumar

LiveCycle Home

There are numerous end user or administrator user web UIs for LiveCycle Enterprise suite  :

  • Correspondence Management Solution
  • Forms Manager
  • Workspace (Flex & HTML)
  • Reader Extensions
  • PDFG
  • Rights Management
  • Process Reporting

An administrator works with many of these web UIs and it is little difficult for administrator to remember the URLs for all these applications and prior to ES4 SP1 there was no single place for a specific user to see what all LC applications that particular user has access to.

In LiveCycle ES4 SP1 we have introduced LiveCycle Home or LiveCycle landing page – which is a single page that displays all the applications that any specific logged in user has access to and can launch those applications from that landing page, SSO is integrated so that the user is not challenged to provide username/password after the first login.

LiveCycle Home sample image :

LiveCycle Home

LiveCycle Home

One can log on to LiveCycle Home by hitting any of the following URLs :

  • http://servernameoripaddress:serverport/lc
  • http://servernameoripaddress:serverport/lc/home
  •  http://servernameoripaddress:serverport/lc/welcome

 

This page can also be customized to add URLs to any other applications that are integrated with LiveCycle

 

There are some self service options for learning (links to help resources) , LiveCycle Communities (Forums & blogs) , TroubleShooting (System Info Service) and link to support (to raise any product issues or contact support for help)

Note : This functionality will be available to only those users of LiveCycle who use CRX based components like Forms Manager or Correspondence Manager.

 

For more information about LiveCycle Home go through documentation on Adobe’s help

 

Content Services clear cache and index check

This blog is relevant to all LiveCycle Content Services customers who are using CS directly or might be using applications that use CS (like CM 2.5 or customized Workspace to use CS in background).

In case if you see any inconsistency in search results of the assets that are stored in Content Services then you may follow below steps to troubleshoot that issue.

I would recommend performing these on development and test environments and not on production system. These steps do not cause any side effects but it is advised to perform these in assistance with LiveCycle support if you are doing it on production systems ( just to avoid any user errors while performing these steps)

One of the reasons for search result inconsistency could be due to cache. Follow the below steps to clear cache and then use your application to check if search results are as expected.

Steps to clean cache :

  1. Log on to http://hostname:port/contentspace as administrator
  2. In the same browser session change the above URL in address bar to http://[hostname]:[port]/contentspace/wcservice/adobe/cms/cleancache/webscript
  3. Hit Enter
  4. You would see a success message after the cache is cleaned
  5. Check the search behavior now from customized workspace UI and/or from CM Manage Assets UI

If the issue still persists , check if the indexes are out of sync

  1. Go to http://hostname:port/contentspace/service/enterprise/admin/indexcheck URL, login as administrator
  2. Click on Check all txn ids (warning: this may take some time)

Note: This operation will take some time and is recommended to be performed when the load on the system is very low (post business hours) or during weekends when no one or not many people are using the system for development or testing.

Also if your development or test  system is cluster, perform these steps on all the nodes separately.

LiveCycle ES4 SP1 (a.k.a Service Pack 1) is now available for download

LiveCycle ES4 SP1 i.e service pack 1 is released and now available for download from Adobe’s Download page It is the first service pack that has been released on top of LiveCycle ES4 which was released in March 2013. This service pack includes numerous features across the product areas, some of those to mention are :

  • LiveCycle Connector for SharePoint 2013   –    LiveCycle connectors now supports integration with SharePoint 2007 , SharePoint 2010 & SharePoint 2013. Till ES4 release only 2007 & 2010 versions of MS SP were supported but many customers have requested us to support SharePoint 2013 as well so we have included that support with SP1 release.
  • MWS Startpoints  - Enterprises can now deploy processes and optionally choose to enable The Mobile Workspace Application now has enhanced UI and now allows users to start processes directly from MWS application.
  • Correspondence Management Solution –  cache functionality is implemented to enhance the performance of correspondence preview and submit. ES4 SP1 has significant performance improvements when compared to ES4. Another major functionality to mention is field and variable validations that have been introduced in create correspondence UI. Organizations can customize CM to include their custom validations as well.
  • LiveCycle Home  -  LiveCycle ES4 SP1 introduces a home page or a landing page for all LiveCycle users which is sort of landing page that displays all the applications that a specific user has access to with their shortcuts for easy accessibility so that one need not remember multiple URLs of various LC applications. User once logged on to LC home can hop to any LC application that he/she has access to without re-entering password via single sign-on
  • Process Reporting  - We have been receiving requests from various customer to provide a UI where they can have an overview of all the processes and tasks that are currently running or which have been completed. This is an all new functionality that has been introduced which gives LC administrators to have valuable business insights in to all the long-lived orchestrations that have been deployed on LiveCycle.

 

The above list is not complete there are numerous other additions like enhanced platform support (Java 7 specifically) , Form Portal integration Package , System Information Service and accessibility reporting.

 

Go to What’s new in ES4 SP1 for a complete list of all the features and enhancements that have been added in ES4 SP1

 

Video highlighting the new features and enhancements in ES4 SP1 (refresh the browser in case you are unable to view the video preview below)

 

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…