Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Why delete [appserverdomain]/null folder during the Livecycle Es4 configuration


Level 1

Deploying LiveCycle EARs


This operation may take several minutes to complete. When the deployment has completed successfully, click



After this step, ensure that you stop the managed server, node manager, and admin server, and then start them in the reverse order. Ensure that a directory named adobe is created in [appserverdomain] after the restart. This is required so that the [appserverdomain]/null directory does not get created, which can lead to the run time issues. Delete the [appserverdomain]/null directory if it gets created.

On the Deploy LiveCycle ES4 EARs screen, select the EAR files to deploy and then click Deploy 

Why is that folder created if we just delete it and why do we delete it?  The null folder has an abobe folder in it that looks identicle to the [appserverdomain]/adobe.

0 Replies


Level 3

This issue does not occur when deploy the EARs manually.

It occurs intermittently when deploying the EARs using LCM and it is specific to Weblogic only. Reason behind this is Weblogic (as opposed to JBoss and Websphere) does not guarantee a particular start-up order of WARs within an EAR.

The initialization does rely on a particular start-up order.

Thus the null folder gets created sometimes.

Hence it is always suggested to restart the server in a particular order to ensure that intialization happens properly. In case the [appserverdomain]/null directory gets created earlier, remove it.

Hope this answers your question.

~ Varun Nohria