How to Avoid LiveCycle Content Services Cluster Deployment Problem When Content Store is on a Shared Drive

LiveCycle Content Services is based on the Alfresco Content Management system.

For a successful installation of LC Content Services in a cluster, you need to have a shared location for content storage. All nodes of a cluster should be able to read/write from this shared content storage location.

Content services also uses the filesystem to store Apache Lucene indexes. The Lucene index directory should be local to each node in a cluster.

In this particular environment, the customer had created a shared network directory on machine1 (/shared_lccs_data) with write permission granted to the JBoss service user. This was a Windows-based installation, with 2 JBoss nodes running on 2 different machines.

In such a situation when LiveCycle Configuration Manger asks for the location of the content store directory, you should specify the shared location in the UNC format. e.g. \\machine1\shared_lccs_data

If you map a network drive on each machine to the shared location, you could run into problems where the Content Services EAR fails to deploy. Example below assumes that Z: on both machines is mapped to the shared directory.

In such cases typical log message you would see in contentservices.log file is:

Caused by: org.alfresco.service.cmr.repository.ContentIOException: Failed to create store root: Z:\shared_lccs_data\contentstore
at org.alfresco.repo.content.filestore.FileContentStore.(

JBoss logs would show something like:

org.jboss.deployment.DeploymentException: URL file:/C:/Adobe/Adobe LiveCycle ES2/jboss/server/lces2/tmp/deploy/tmp6999661586287322315adobe-contentservices.ear-contents/contentservices-exp.war/ deployment failed
at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(

It’s important to note that you should also choose UNC paths to specify the GDS location, if you are using file system based Global Data Storage (GDS) for LiveCycle.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

About Santosh Tatke

Santosh Tatke is a Sr. Support Architect at Adobe Systems. He specializes in ADEP (formerly LiveCycle) technology stack and works closely with customers, solution consultants and partners to troubleshoot, analyze and resolve technical challenges during POC, implementation, deployment or upgrade. He is a Certified LiveCycle ES2.5 Process Management Expert.
This entry was posted in Adobe LiveCycle ES2 (9.0.x), General Interest and tagged , , , , . Bookmark the permalink.

Comments are closed.