Tag Archives: document services

Overview of the ADEP Document Services modules

Michael Steward

When LiveCycle became ADEP Document Services all of the existing modules were ported over but I thought it would be useful to revisit them all and see what as new.  This post gives a summary of the modules which are available to any Document Services solution (excluding the foundation services which come with all Document Services modules) and should be familiar to those who have worked with LiveCycle ES1/ES2 in the past.

Business Process Management

Adobe Digital Enterprise Platform Document Services – Process Management 10.0
Process Management allows the designer to create processes which assign and move tasks around a business.  End users can login using the Workspace web application to view and update any task assigned to them.  This module is commonly used in conjunction with the Forms modules in order to create workflows for forms built by the designer.  ADEP Mobile also comes as part of this module allowing your end users to interact with their tasks on the go.

Content Services
As described in one of my earlier posts this one has now been deprecated.  It’s still included for legacy purposes but you should really be using the new CRX service.

Forms Automation

Adobe Digital Enterprise Platform Document Services – Forms 10.0
The bread and butter of many ADEP solutions, Forms is what allows data to be merged and retrieved from forms rendered to PDF, HTML or Guides.  It also allows forms to be assembled from fragments.  If you are designing to form to be dynamic and it doesn’t have a fixed layout then you will almost certainly need the Forms module.  Together with the Process Management module it allows for some fancy data collection and presentation to your end users!

Adobe Digital Enterprise Platform Document Services – Adobe Reader Extensions 10.0
If you need to distribute those forms you’ve just designed to external parties then chances are you’ll probably run into the need for Reader Extensions.  A “rights-enabled” form opened in Adobe Reader allows the end user to perform tasks that are normally reserved for the commercial Acrobat software such as adding attachments, saving a PDF form locally (the most common use case) and digitally signing forms.  Can be used standalone or as part of a workflow.


Read the full blog post here.

Document Services Basics

I’ve uploaded a ‘dsBasics’ PDF Portfolio with seven short articles that cover the basics of creating, deploying and invoking document services. This has been covered before but I hope to have brought it “down to earth”. No guff. No extra mind-numbing details. Yet all you need to know both to “get ‘r done” and to understand what you are doing.

All the code is there, including the imports. That’s for a POJO DSC, and for Java and Flex clients. All of the classpaths, both compile time, and run time, are there including how to work out what those classpaths have to be. There are even some utility .bat files thrown in for good measure. How to deploy and undeploy is covered. How to invoke document services both from a Java client and a Flex client is also covered.

There is more to know. These are just the basics but with them you can extend your document services system and access its power from your client apps.

If there is anything in here that is not sufficiently clear or leaves a gap in your understanding of “what’s going on”, please, please comment so that I can address such issues.

Original article at http://blogs.adobe.com/livecycle/2011/05/document-services-basics.html.

Using the Belgian eid card for accessing a LiveCycle Rights Management protected document

– Peter Schellemans

Typically LiveCycle Rights Management (a.k.a. Policy) protected documents use a userid/password mechanism for authenticating towards the policy server, and consequently open the protected document. A more secure way of authentication can be obtained by using client certificates. A real strong way of authentication can be accomplished when the authentication certificate resides on a smartcard, protected by a PIN code. The authentication certificate on the Belgian eid card is such an example. How can that be used to authenticate towards a Policy protected document?

To achieve this follow these steps:
1) First of all the authentication certificate must be known/registered/uploaded to the LiveCycle server. Open the adminui –> Settings –> Trust Store Management –> Certificates.
When importing the .cer file, specify that you want to trust the certificate for “Certificate Authentication”, and provide an alias.

2) Next this certificate must be mapped to an existing user in LiveCycle.
Open the adminui –> Settings –> User Management –> Configuration –> Certificate mapping.
The mapping between a certificate and a user is done for a defined alias, and is accomplished by mapping a certificate attribute (Mail, CN, DN,… ) to a user property (Full Name, Given Name, Mail, login ID, …).

In the case of the Belgian eid card the CN on the authentication certificate contains also the word “Authentication”. In my case my CN = Peter Schellemans (Authentication). So in order to get a working certificate mapping towards an existing user, make sure you have a user with a similar Full Name. In my case I have a user (adminui –> Settings –> User Management –> Users and Groups) with First Name = Peter, Last Name = Schellemans (Authentication).

3) Next add this user as part of your Policy. When opening the policy protected document you will now get the choice between userid/password authentication and client certificate authentication.

Tip to stay healthy:
If you want a higher level of security when authenticating towards a policy protected document, Adobe LiveCycle allows you to map certificates towards users, used in a policy definition.

Original article at http://www.drflex.eu/2009/01/using-the-belgian-eid-card-for-accessing-a-livecycle-rights-management-protected-document/?utm_source=rss&utm_medium=rss&utm_campaign=using-the-belgian-eid-card-for-accessing-a-livecycle-rights-management-protected-document.

Working around a “Turnkey service JBoss for Adobe LiveCycle does not exist” error

Waldo Smeets

After installing a new Jboss turnkey instance of Adobe LiveCycle, some people run into an issue when the LiveCycle Configuration Manager is doing it’s work. At about 40%, the configuration manager might display the following error:


Failed on ‘Verifying JBoss for Adobe LiveCycle ES service is installed’
Windows turnkey service JBoss for Adobe LiveCycle ES does not exist

When checking in the Windows Service Panel, indeed there is no such service defined, even though the installer should have created it. I have not been able to replicate this issue, but it happened to me at a customer site and by searching Google it seems that others have run into it as well.

The Google search results tells us that some people forget to set the Java_Home system variable and that you should be using the right version of the JDK. However, this did not seem to be the problem in this case.

Through the install documentation you can find the steps needed to re-create the JBoss for Adobe LiveCycle ES service (page 62). You can use those to try and create the service ‘manually’. For our install, the problem seemed to be in the [LC_INSTALL_ROOT]jbossInstallJBossService.bat script file. Somehow the username / password did not seem to work, whatever we tried it failed. Well, sort off: strangely enought the command prompt output first mentions that there was an error, though still reports that the script was executed succesfully. Still no service created though.

The solution was too simple to come up with: just remove the username / password parameters from the script and execute it. This time the script did not fail and as expected created the service for us. Next thing to do is go into the service panel, select the ‘JBoss for Adobe LiveCycle’ service, right click to go to it’s Properties and in the Log On tab specify Log In As This Account. Then specify the username password (in my case “.administrator” and the password), click OK and you are done.

Now run the LiveCycle Configuration Manager again and most likely it won’t fail anymore cause of the missing service. This seemed to have overcome our issue.

Tip to stay healthy:
When installing the turnkey solution, it is highly recommended to keep the right documentation at hand: Installing and Deploying LiveCycle® ES Using Turnkey.

Did you run into this issue as well? Please let us know if this worked for you or if you have additional tips for our readers.

Original article at http://www.drflex.eu/2009/03/turnkey-service-jboss-for-adobe-livecycle-does-not-exist/?utm_source=rss&utm_medium=rss&utm_campaign=turnkey-service-jboss-for-adobe-livecycle-does-not-exist.

e-Invoicing with Adobe

– Marcel Van Espen

As many people know, e-Invoicing is gaining a lot of traction these days in order to save money. In general many of the solutions use PDF as the format for the electronic invoice. But there is PDF and PDF. We have created a sample electronic Invoice in PDF format that is more then just a digital invoice, and also focuses on the experience of the recipient in addition to the ability to exchange structured data. Have a look at a video that includes a demo. If you would like to download the sample and play with it yourself, here it is.

Original article at http://www.drflex.eu/2009/05/e-invoicing-with-adobe/?utm_source=rss&utm_medium=rss&utm_campaign=e-invoicing-with-adobe.

Change the GDS (Global Document Storage) location of a Production LiveCycle ES System

Important Remark:
Within the LiveCycle Documentation you will find the following on the GDS:
“The global document storage (GDS) is a directory used to store long-lived files such as PDF files used within a process or DSC deployment archives. Long-lived files are a critical part of the overall state of the LiveCycle ES environment. If some or all long-lived documents are lost or corrupted, the LiveCycle ES server may become unstable. Input documents for asynchronous job invocation are also stored in the GDS and must be available in order to process requests. Therefore, it is important that the GDS is stored on the redundant array of independent disks (RAID) and backed up regularly.”
So the GDS is the cornerstone of a LiveCycle system. Changing this location should be carefully executed by product experts. Take a back-up before you start and don’t try this at home …
For whatever reason you want to change the location of the GDS. As explained above this is possible but should be very carefully executed.
Disclaimer: This section will describe the different steps to execute in order to move the location of the GDS. These steps should be considered as a Guideline and not as a by Adobe Supported set of actions. You are encouraged to execute this first in a Test environment before doing this in a Production environment. The different Steps are:
  1. Alert and Ask the End-Users to get out of the LiveCycle Application/Server
  2. Put the LiveCycle Application/Server in ‘Operate in safe backup mode’. In Adminui go to Settings > Core System > Backup Settings – select the ‘Operate in safe backup mode’ and hit the OK button.
  3. Backup the GDS folder
  4. Zip or Tar the GDS folder
  5. Change the location of the GDS folder. In Adminui go to Settings > Core System > Core Configurations and change the location of the GDS Directory. Hit the OK button; you will get a second page and hit the OK button again
  6. Shutdown the LiveCycle Application/Server
  7. Check whether the LiveCycle Application/Server system user has access to the new GDS folder
  8. UnZip or UnTar the files in the new GDS folder
  9. StartUp the LiveCycle Application/Server
  10. Do some basic validations. In Adminui go to Services > Applications and Services and choose Archive Management and Endpoint Management and check visually whether you get the expected information
  11. Deactivate the ‘Operate in safe backup mode’. In Adminui go to Settings > Core System > Backup Settings – unselect the ‘Operate in safe backup mode’ and hit the OK button

Tip to stay healthy:
Make sure that you have the final location of the GDS available, before you install LiveCycle in a Production environment.

Original article at http://www.drflex.eu/2009/06/change-the-gds-global-document-storage-location-of-a-production-livecycle-es-system/?utm_source=rss&utm_medium=rss&utm_campaign=change-the-gds-global-document-storage-location-of-a-production-livecycle-es-system.