Posts tagged "DSC"

Importing LiveCycle DSCs using command-line

Ankush Kumar, Lead Software Engineer @ Adobe

Many a times, we have the requirement to deploy single or group of system or custom DSCs. System DSCs are deployed by LiveCycle Configuration Manager. However, in the case of custom DSCs, we need to manually deploy the component through LiveCycle Workbench. Sometimes, launching Workbench for solely deploying component seems like too much effort. Moreover, it’s not very easy to automate.

You can use the attached sample tool to deploy a DSC using command-line.

  1. Download and extract the tool archive on your machine. It contains a folder libs, a runme.bat file, and an ImportDSC.jar file.
  2. Place <LiveCycle Installation Dir>\sdk\client-libs\thirdparty\*.jar files in libs folder.
  3. Place adobe-usermanager-client.jar and adobe-livecycle-client.jar files in libs folder.
  4. Modify runme.bat accordingly.

The ImportDSC.jar is used in the following way in the runme.bat file (provided classpath is set):

java com.adobe.livecycle.sample.ImportDSC appserver=<websphere|weblogic|jboss> serverhost=<name of machine> port=<port of LC> username=<user to install DSC> password=<password of mentioned user> dscpath=<absolute path till DSC> force=<true|false>

The source code is also included in the archive. Please review it in case of any doubt and modify as per your requirements.

DISCLAIMER: This sample code is not officially delivered or supported as part of Adobe LiveCycle product. One should verify this on a testing environment before employing in production environment.



VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.0/10 (1 vote cast)

Error when attempting to interact with a service managed by the Livecycle DSC container

Siddharth Jain, Quality Manager @ Adobe


On WebSphere, errors are encountered on attempting to interact with a service managed by the Livecycle DSC container. The service is unexpectedly shown as inactive in the Livecycle administration console. Examination of the server logs (SystemOut.log) shows that the service failed to start due to class-loading issues (ClassNotFoundException errors).


The issue occurs as a result of a file-lock which prevents the DSC container from properly extracting the class files required by the DSC class-loader to a temporary directory on the local file-system. To confirm that this is the case, note the time-stamp of the ClassNotFoundException error thrown during service startup in the WAS SystemOut.log and then check that the WAS SystemErr.log contains warning messages of the form ‘The process cannot access this file because it is being used by another process’ around the same time.


To remove the lock, shut down the server and periodically try to manually delete the file for which the file-lock warning is appearing in SystemErr.log (the log file should contain the complete path of the file) . If the deletion succeeds within a reasonable amount of time, start the server and check that things are fine. If the file continues to stay locked for a long period of time, try restarting the machine.

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