Adobe releases service packs for LiveCycle ES roughly once a quarter. There are separate service packs for LiveCycle Designer, Workbench as well as the Server. The Server service packs are usually about 1 GB in size. Since the older service packs are backed up, your server’s disk space requirements will keep going up as you apply more service packs.
At a high level, the following are the steps you need to perform to update your LiveCycle installation with a new service pack:
1) Apply the service pack to your existing LiveCycle installation
2) Using LCM, re-build the EAR files
3) Undeploy the existing EAR files from the appserver(s)
4) Deploy the newly-built EAR files
5) Re-start the appserver instances
6) Using LCM, re-deploy the DSCs. Those DSCs that haven’t changed will be left alone while others would be updated.
7) Perform basic validation tests
There is NO NEED to re-bootstrap the database.
If a DSC was changed, the lcm.0.log file at $LIVECYCLE_INSTALL_ROOT/configurationManager/log/ will have entries such as this:
com.adobe.livecycle.lcm.feature.deployment.DeployDSCs, DSC already installed but at a different version. DSC will now be updated with: com.adobe.livecycle.Assembler:8.2.3026.1.197218.8
Otherwise, the entries would look something like this:
com.adobe.livecycle.lcm.feature.deployment.DeployDSCs, DSC already installed. Skipping update for: com.adobe.repository.bindings.dsc.RepositoryService:8.2.2176.1.183920.1