Posts tagged LiveCycle

LiveCycle PDF Generator – Tips and Tricks

- Saurabh Kumar Singh, Computer Scientist @ Adobe

Following are a few tips and workarounds for LiveCycle PDFG. Please note that the workaround marked as unsupported are not officially supported by Adobe.

  • [Unsupported] On UNIX servers customers can use 64-bit OpenOffice to do OpenOffice based conversions. The obvious benefit from this is the performance improvement we get. To achieve this just point JAVA_HOME_32 to 64 bit version of Java. Same can achieved on widows too but you may observe immediate conversion failures for other native file formats.
  • [Unsupported] Any file which can be opened by Acrobat (like a text file) can be converted to PDF using LiveCycle PDF Generator. You just need to add the comma separated file extension (for example txt for text files) in XPS to PDF file-type setting.
  • A user/administrator can directly jump to PDF Generator UI by hitting http(s)://<server-name>:<port>/pdfgui. This way a user can skip couple of clicks on UI to land on PDF Generator user interface.

Extending Adobe LiveCycle through custom DSCs – some resources

Don’t worry – this is not going to be a lengthy, complicated, super-advanced tutorial. I thought about writing a post on Adobe LC DSCs for a while, but never got round to. Today, I got kind of pushed over the edge by seeing that my friend Duane and his partner Matt from Überity have published a super-simple DSC to integrate an LC process with the Twilio SMS/TXT services.

You have no idea what I’m talking about? Ok – here’s the gist: A DSC is a Document Service Component in LiveCycle. Basically it’s a component wrapper for some custom logic or external service integration that one can write and use within the LiveCycle Process Management Engine. One of my biggest complains about and issues with LiveCycle are the lack of community contribution and the lack of good and advanced documentation around the product. So, let’s take this opportunity to compile a few interesting resources around DSCs.

If you’re ever in the need of extending LiveCycle (and most serious users I know are at some point), writing a Document Service Component is one of the easiest ways. To get started, use a tutorial Adobe provides here:

Extending LiveCycle ES software through custom DSC development – Part 1: Create a basic service component

---

Read the complete post at Blog In Black.

LiveCycle ES: ALC-PDG-001-001 The Job Configuration either cant be obtained or is invalid

Issue

If you are using PDFG to process documents on your LiveCycle server you may encounter problems with the conversions accompanied by the following exception in the server log:

GeneratePDFIm A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-Job ID for the submitted createPDF job =CreatePDF-2012-07-23 12-05-26.643.docdfaed6-f564cb-14cb09-338b02-c5fd79-ba0c90

GeneratePDFIm E com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error.

AWS  E com.adobe.workflow.engine.PEUtil logFailedFaultRouting An exception was thrown with name com.adobe.livecycle.generatepdf.client.InvalidParameterException message:ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error while invoking service GeneratePDFService and operation CreatePDF2 and no fault routes were found to be configured.

WorkflowDSCIn E com.adobe.idp.workflow.dsc.invoker.WorkflowDSCInvoker logFailedFaultRouting An exception was thrown with name com.adobe.livecycle.generatepdf.client.InvalidParameterException message:ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error. while invoking service GeneratePDFService and operation CreatePDF2 and no fault routes were found to be configured.

JobManagerBea E com.adobe.idp.jobmanager.ejb.JobManagerBean doOnMessage JobManagerBean:onMessage():Exception:ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error.  Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI “#d6f16633df10d6efd649f0d2becce92c”

FileResultHan A com.adobe.idp.dsc.provider.service.file.write.impl.FileResultHandlerImpl tryPreservingFiles FileResultHandlerImpl —– preserved- source —-serverWatchedFoldersfolderstageWx840560ff8bdc142771fc0a18CreatePDF-2012-07-23 12-05-26.643.doc— to —serverWatchedFoldersfolderfailureCreatePDF-2012-07-23 12-05-26.643CreatePDF-2012-07-23 12-05-26.643.doc

---

Read the complete post at David's Blog.

Could not initialize class com.documentum.fc.client.DfClient while starting livecycle documentum connector services for documentum 6.7 SP1

If you are trying to configure documentum 6.7 sp1 with livecycle and while starting the services for livecycle connector for emc documentum you are getting the below error, then this post may be help ful to you.

java.lang.NoClassDefFoundError: Could not initialize class com.documentum.fc.client.DfClient     at com.documentum.com.DfClientX.getLocalClient(DfClientX.java:43)     at ……..

The cause of this error is that the classpath required for connecting for documentum 6.7 SP1 is not correct.

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle ES2: XMLForm.exe terminated abnormally with error code {3}

Issue

If you are using LiveCycle to process PDF documents you may encounter problems displaying/converting forms or PDF documents, accompanied by exceptions similar to the following in the server log:

ProcessResour W com.adobe.service.ProcessResource doProcessExitCleanup BMC024: Service XMLFormService: Process ProcessResource@f1f45(name=XMLForm.exe,pid=0) terminated abnormally with error code {3}

XMLFormAgentW E com.adobe.livecycle.formsservice.logging.FormsLogger logMessage ALC-OUT-002-004: Unable to find service: XMLFormService, error: Connection to failed service.

---

Read the complete post at David's Blog.

LiveCycle ES2: This scheduler instance (SchedulerName) is still active but was recovered by another instance in the cluster

Issue

If you are working with LiveCycle ES2 in a cluster you may notice the following message in the server log:

org.quartz.impl.jdbcjobstore.JobStoreSupport findFailedInstances “This scheduler instance (<SchedulerName>) is still active but was recovered by another instance in the cluster. This may cause inconsistent behavior”.

Reason

This exception often occurs when the clock times on the cluster nodes are not synchronized.  If the clock times on cluster nodes are more than 1.7 seconds out of synch you will start to see these Quartz messages in the log.

Solution

Synchronize the time on all cluster nodes and then restart the cluster.  The messages should no longer appear in the log.

reference: (1647846)

How to Fix Error Code 19457 BackingStoreException

Recently I worked on troubleshotting an issue for a customer who was encountering issues while deploying components.

The following error was seen in the LCM log and no error was seen in the server log:

============

[2012-06-29 03:55:54,681], SEVERE, main, com.adobe.livecycle.lcm.cli.LCMCLI, Failed to deploy component.

Cannot connect to service container.

com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-201]: Failed to deploy component.

Cannot connect to service container.

at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:303)

…..

…..

…..

at com.adobe.livecycle.lcm.cli.LCMCLI.main(LCMCLI.java:344)

Caused by: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.

at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.throwExceptionHandler(SoapAxisDispatcher.java:211)

…..

…..

…..

at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:292)

… 5 more

Caused by: com.adobe.idp.common.errors.exception.IDPException| [com.adobe.idp.um.config.util.CachedConfigManager] errorCode:19457

errorCodeHEX:0x4c01 message:Error occured while initializing the configuration

chainedException:java.util.prefs.BackingStoreExceptionchainedExceptionMessage:null chainedException

trace:java.util.prefs.BackingStoreException

at com.adobe.idp.config.AdobeLocalPreferences.flush(AdobeLocalPreferences.java:223)

…..

…..

…..

at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.doSend(SoapAxisDispatcher.java:127)

… 10 more

==============

Read the complete post at Adobe LiveCycle Blog.

Managing Process Recordings in LiveCycle

Process Recordings are stored in the /GDS/audit/workflow/ directory.

By default, the maximum number of recordings that can be stored is set to 50.

The value for maximum number of recordings can be configured via Workbench:

---

Read the complete post at Adobe LiveCycle blog.

LiveCycle SharePoint Connector option convert to pdf is not available on .xml or .aspx pages

Users keep facing the issue that the LiveCycle SharePoint connector options are not available on certain type of files like xml and aspx.

Solution:

To enable convert to pdf option for xml, aspx or any other type of documents (which are supported by LiveCycle PDF Generator component), you can follow the below steps:-

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle – Application Server Clustering Verification

When running Adobe LiveCycle in cluster mode, it is important to verify that the cluster is configured and started successfully. LiveCycle deployment has has twoclustering layers

  • Application Server Clustering
  • LiveCycle Clustering

LiveCycle runs on J2EE stack. J2EE level clustering should be configured as mentioned in LiveCycle cluster documentation. In this article we will go through each application server and based on logs determine if the clustering is successful or not, LiveCycle Clustering is described in the article – LiveCycle Cluster Verification.

---

Read the complete post at Adobe LiveCycle Blog.

Go to Top