Sr. Technical Account Manager at Adobe Systems
Posts by dmcmahon
In LiveCycle ES it is possible to track the dependencies of parent forms to form fragments and vice versa using the functionality in Workbench ES.
In LiveCycle ES2 it is also possible to view the form fragments used by a parent form in Workbench > Form Design > Properties:
It is not possible to track the dependencies from a form fragment to see in which parent forms the fragment is used. This is due to the architectural changes related to the new application model in LiveCycle ES2.
In LiveCycle ES3 it is again possible to track the dependencies of parent forms to fragments and vice versa.
If you have a requirement to track the dependencies from fragments to parent forms in LiveCycle ES2, then you can do this using the LiveCycle API using code similar to below:
ResourceRepositoryClient repositoryClient = new ResourceRepositoryClient(myFactory); String fragmentUri = "/Applications/TestApplication/1.0/fragments/AddressFragment.xdp"; List relations = repositoryClient.getRelated(fragmentUri, false, Relation.TYPE_DEPENDANT_OF);
Here is a full sample class you can execute to test this functionality against a running LC server (you will need to adjust the settings for your environment): ListDependencies.java
If you are installing and deploying patches for LiveCycle ES2 using the command line version of LiveCycle Configuration Manager (LCM) you may encounter an error similar to the following while deploying components:
com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-200]: Failed to deploy component /opt/adobe/adobe_livecycle_es2/deploy/adobe-usermanager-dsc.jar. at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:419) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCs(DeployDSCs.java:151) at com.adobe.livecycle.lcm.headless.HeadlessLCMImpl.deployDSCFilesLFS(HeadlessLCMImpl.java:285) at com.adobe.livecycle.lcm.cli.DeployLCComponentsCLI.executeCommandLineImpl(DeployLCComponentsCLI.java:96) at com.adobe.livecycle.lcm.cli.LCMCLI.execute(LCMCLI.java:298) at com.adobe.livecycle.lcm.cli.LCMCLI.main(LCMCLI.java:344)
and the LC logs may contain the following exception messages:
Component: com.adobe.PDFServices version: 188.8.131.52.20120202.1.312922 introduced a new service, it should not be patched
This problem occurs if the order of operations in LCM is incorrect. For example, if you run the deploy components step (DSCs), before configuring and deploying the new EARs. This can occur when using the command line LCM as you call each operation separately. It can also occur using the UI LCM if you run the tool twice in succession and select to deploy components in the 1st run before deploying the EARs in the 2nd run.
You should re-run the LCM steps ensuring to configure and deploy the EARs first, before deploying the components.