This user hasn't shared any profile information

Posts by moderator

10 Top Tips for using Mobile PDF Forms

Having worked with a few clients to deliver mobile PDF form solutions for tablet devices and using the Adobe Reader for Mobile we thought we would list 10 top features which can make your use of electronic PDF forms and PDF documents in general on Android and iOS useful.

This list is available from in this blog post.

Learning AEM Forms and Documents

Want to learn how to work with AEM (Adobe Experience Manager) Forms and Documents, powered by Adobe LiveCycle? Adobe TV has a great series that will get you up to speed in no time!

From Adobe TV:

“This video series introduces AEM forms and documents powered by LiveCycle. It demonstrates how to develop applications to capture and process information via forms, communicate with customers, and secure documents.”

Check it out here: Learning AEM Forms and Documents Powered by LiveCycle

Displaying PDF documents/forms from Adobe LiveCycle in the browser

Users of Adobe LiveCycle quite regularly interact with PDF documents. Some examples are:

  • Rendering customised documents for print purposes
  • Creating PDF forms for on- and offline use to collect data for further processing
  • Rendering pre-filled PDF forms to send out to customers/users for completion and physical signature etc.

In a lot of cases those PDF documents are what’s called an XFA-based PDF form/template. XFA is Adobe’s XML Forms Architecture and a proprietary technology to describe form information. I spare you the technical details, but essentially quite often those XFA-based forms get wrapped into a PDF document, this is done by rendering the XFA information over a PDF page background.

Read the issue and steps to fix it at this blog.

The Adobe LiveCycle Portable Protection Library: an SDK to Manage your Rights Management Server

First, a little background information about Adobe LiveCycle

Adobe LiveCycle is an enterprise suite of server based software products that are meant to help structure business processes. One of its key features is the ability to protect a document (of the following types PDF, Microsoft Word, Microsoft Excel, Microsoft PowerPoint, text, and more!) with a policy to restrict access to a subset of users. Adobe LiveCycle offers this ability through one of its components called, Rights Management.

After a certain point large organizations or organizations that have been using Adobe LiveCycle for an extended period of time may accumulate a significant number of policies and documents, these can become tiresome to manage through the web interface for the Rights Management component of LiveCycle. Users of LiveCycle can also fall into performing the same action over and over, such as protecting documents with the same policy again and again. What if there was a programmatic way to apply these policies to new documents? What if there was a programmatic way to use a policy from one document in another? What if there was a programmatic way to manage these?

Read the complete post here.

Adobe Digital Rights Management Technologies – ACS vs. LCRM

When we meet with companies we get a substantial number of questions about how to protect digital content. Adobe has at least 2 offerings in the Digital Rights Management space, Adobe Content Server and Adobe LiveCycle Rights Management. These products both fall into the DRM category, but they solve very different problems for very different markets. This article will discuss the capabilities and licensing of each and what problems they are targeted at solving.

Adobe Content Server – DRM for Commercial eBooks

This product, also known as ACS, is capable of securing content in the ePub and PDF file formats. The product is sold by Adobe partners as a server license, and there are transaction charges incurred for each individual content license granted.

The target market for this offering is eBook or other digital content distributors such as Sony, Kobo, Barnes & Noble or Google. Content is licensed on a one to one basis and rights are applied at the time a specific item is purchased. More specifically, content is licensed to an individual with a specific Adobe ID or Vendor ID, and may not be consumed on reading devices that are not registered with that ID. ACS provides granular control over the rights that may be granted with each content license. For example a book store may sell a popular title for one price with the rights to read it on multiple devices, re-download it a future date and print a range of pages, and may also have the same book listed at a different price with more restrictive rights. Once rights are applied, generally at purchase time, these rights cannot be modified or revoked.


Read the complete post at Datalogics Blog.

Debugging Livecycle Data Services in Livecycle ES

The other day I was spending some time with a client of mine who ran into an issue with a Flex Remoting endpoint in Livecycle/ADEP

Essentially what happened was that within an object tree supposed to be sent from the Flex application to a Livecycle endpoint contained a lot of unexpected null references. Monitoring the AMF remoting traffic with Charles showed however that the data was serialised fine on the Flex side of things. At the other end of the wire though, something clearly went wrong. Even more confusing was that the serialisation seemed to work fine for non-complex data types which led us to the suspicion that the conversion of ArrayCollections to Java generics was setup incorrectly.

Without elaborating on details of coding and configuration switches that can modify how all that works in depth (hint: IExternalizable and are your friends…), I rather want to explain some other configuration settings that a lot of people wouldn’t be aware of, but that are extremely helpful when you run into a possible serialisation problem.


Read the complete post at Blog In Black.

Accessing .properties files within a Livecycle ES/ADEP DSC

The other day Darren asked about how to access a properties file with some settings from within a Livecycle ES resp. ADEP DSC on the livecycle developers mailing list. I responded there, but I thought it’d be useful to post the solution here as well.

Essentially a Livecycle/ADEP DSC is nothing else but a .jar file that’s been crafted in a certain way. Darren wanted to have the .properties file within the DSC and needed to know how to access the file from Java code within the DSC. Here’s a working approach how this can be done:


Read the complete post at Blog In Black.

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.

Testing LiveCycle Workspace

- Ameeth Palla, Technical Account Manager, Adobe

A topic that has come up several times in the recent past is about testing Adobe LiveCycle Workspace. I thought it will be useful to provide some information around this for the benefit of a larger LC community.

If the objective is Load testing, in-house Adobe uses a commercial tool call Silk Performer which can capture and replay the AMF3 interactions between Workspace and the server for scalable load generation. There are other tools that work with AMF3.Some people have asked if QTP can be used for load testing – It is unlikely that QTP is a good fit, since it is not suited to scalable load generation.

Adobe recommends using Silk Performer or Neotys Neload for load testing of Workspace. Check out the links below that may provide more insight into this topic:

If the objective is Functional testing then Workspace is configured for QTP testing out of the box.  If you install QTP, restart your computer, then install the Flex plug-in for QTP, restart your computer then you can start automating your Workspace tests.  However for QTP automation you should use the Workspace automation URL rather than the default URL.  So rather than http://server:port/Workspace/Main.html you would use http://server:port/Workspace/Main-auto.html.



Read the complete post at

FIPS Validation Certificate for LiveCycle ES3

Adobe LiveCycle ES3 includes a FIPS 140 Certified RSA BSAFE Crypto-J 3.5 (cert#590) encryption module.  FIPS mode is configured in the product installer.

Original article at

moderator's RSS Feed
Go to Top