Tag Archives: LiveCycle

Canonical name ‘vs’ User ID


Recently I worked on a customer issue where in they were seeing an error when the user logged into their AIR client on MAC and was unable to access the application.

The error seen was :

LC_AuthenticateUser Error: com.adobe.idp.um.api.UMException| [com.adobe.idp.um.api.impl.AuthenticationManagerImpl] errorCode:16386 errorCodeHEX:0×4002 message:user_identifier:Z027223 domain:DefaultDomcom.adobe.idp.common.errors.exception.IDPException| [com.adobe.idp.um.businesslogic.directoryservices.DirectoryServicesManagerBean] errorCode:13316 errorCodeHEX:0×3404 message:user_identifier: Z027223 domain:DefaultDom;


Read the complete post at Adobe LiveCycle Blog.

Managing User Access

You must have the Application Administrator role assigned to your LiveCycle ES2 user account in order to develop applications. In this role, you can assign limited access to the application development environment for users who have other roles assigned. You can permit other users to have the following type of access:

  • Read: The user can view the application.
  • Delegate: Although the user is not the Application Administrator, that user can extend read/write permissions to another user.
  • Write: The user can modify the application and save the changes.

Essentially one can classify user permissions under the following two categories:

  1. Role Based Permissions
  2. Resource Level Permissions

Role Based Permissions typically would cover the roles that the user has been assigned via the Role Assignment interface and this supersedes the “Resource Level Permission ” which are assigned via the Manage Access interface as described in the following link.

In order to achieve the above scenario one would need to ensure that the user has not been assigned any such permissions which would otherwise allow the user to perform the Read/Delegate/Write operations on an application.


Read the complete post at https://blogs.adobe.com/livecycle/2012/07/managing-user-access.html.

LiveCycle Cluster Verification

On top of J2EE clustering, LiveCycle is clustered using Gemfire Distributed Cache. In cluster deployments, it is important that all the members of a LiveCycle cluster are able to find each other so that they can keep their individual caches in synchronization with one another. LiveCycle Cluster is configured properly or not can be identified based on two key indicators. The following are the key indicators.

  • Clustered Scheduler Service
  • Gemfire Logs


Read the complete post at Adobe LiveCycle Blog.

Re-build lucene indexes for Content Services

- Abhijit Ghosh, TRT Engineer @ Adobe

Content services uses the filesystem to store Apache Lucene indexes (/lucene-indexes). At times we are faced with the need of re-building indexes hence just wanted to summarize the ways in which the same can be achieved:

1. Include the JVM argument –Dindex.recovery.mode=FULL and restart the server.

2. Stop the server, delete the lucene indexes under the index root directory and restart the server.

3. Change the index directory to a different location during restart so that indexes are re-built again.

LiveCycle ES3 – FileNet Connector for FileNet 5.0 – Documentation Clarification


For LC ES3 – the “Preparing to Install Adobe LiveCycle ES3″ Guide – section 2.2.9 (Additional requirements for Connector for IBM FileNet) – for FileNet Connector configuration is unclear.

The section reads as below -


IBM FileNet 5.0

If LiveCycle is connecting to IBM FileNet 5.0 Content Engine, you must install the Content Engine Java Client. Use the IBM FileNet 5.0 content engine client installer located by default in C:Program FilesFileNetCEClient. During installation, select at least one of the components from Application Engine or Process Engine on the component selection screen.

For IBM FileNet 5.0 Process Engine, you must install the IBM FileNet 5.0 Process Engine Client located by default in C:Program FilesFileNetBPMClient. During installation, select the Other option on the component selection screen.



The above text in red does not clearly answer the below questions:

- Does this mean that during the Java Client installation, the user needs to point to an existing Application Engine installation (which maybe be on a different server than LiveCycle)?

- Or does this mean that the Java Client has to be installed where the Application Engine resides (which it already is) and so this step can effectively be skipped?

- Or does this mean that another instance of Application Engine needs to be installed on the same server as LiveCycle?


Read the complete post at Adobe LiveCycle Blog.

Process ID value comes up as “-1″

- Ameeth Palla, Technical Account Manager @ Adobe

Issue: Recently I worked on an issue for a customer who reported a problem with Process ID value becoming “-1″.

Scenario: Customer had a process where they were naming the output file using a combination of “Process ID + time-stamp”. They reported that the value of the output filename was coming up as “-1+time-stamp” for some files.

Trouble-shooting: Upon reviewing their process, the design was – A long-lived process takes an input from a watched-folder end-point and checks to see if the incoming file is a TIFF, MS Word document or XML data file. If the input was any other format other than XML, then these files would be converted to PDF’s and the output file would be named as “Process-ID+timestamp” and stored in a directory. If the input file was an XML data file then it would be sent to a sub-process and merged with a form-template and flattened and then named as “Process-ID+timestamp” and stored in the same output directory. By running some tests, we could see that the file name would come out as “-1+timestamp” only when the input file was an XML data file.


Read the complete post at Adobe LiveCycle Blog.

Calling custom code implementation during LiveCycle Server Startup

- Abhijit Ghosh, TRT Engineer @ Adobe

We were recently working on a customer scenario who wanted to make a custom code call during server startup.In order to achieve the same you would need to implement theLoad interface in your custom component as described below:

In the component.xml you would need to use the load-class tag in for the classes which implement the same and are to be loaded.


Read the complete post at Adobe LiveCycle Blog.

LiveCycle Cluster – TCP based JBoss Clustering

- Pankaj Parashar, Lead Softweare Engineer @ Adobe

Adobe LiveCycle comes with pre-configured JBoss (Community Edition only) . The preconfigured JBoss has both standalone and cluster-enabled configurations. All cluster-enabled configurations are based on UDP by default. Various enterprise organizations have very restrictive network policy and don’t allow multicasting in their networks. For such organizations, TCP based clustering is recommended option. JBoss instances belonging to different subnets require TCP based clustering only. In this article, we will go through detailed instructions to configure TCP based JBoss cluster. These instructions are applicable for both preconfigured JBoss and downloaded JBoss (Version 5.1 only).

The Following are the detailed instructions for TCP Clustering:


Read the complete post at Adobe LiveCycle Blog.

Store Content to FileNet server using LiveCycle Java APIs

- Pankaj Gakhar, Software Engineer @ Adobe

You should have LiveCycle server installed and LiveCycle connector for IBM FileNet should be configured with it.

Follow the steps below to store content to FileNet server using LiveCycle’s Java APIs:

1. Create ServiceClientFactory Object.

2. Create an object of IBMFileNetContentRepositoryConnectorServiceClient class using the object of ServiceClientFactory class.


Read the complete post at Adobe LiveCycle Blog.