If you have installed a patch or service pack for LiveCycle ES you may need to uninstall this at a later date, or you may have a requirement to document this process fully as part of your installation/configuration documentation.
This information is outlined in the readme file provided with each patch or service pack, and I will just expand on that giving some more detail here. In this example I will discuss uninstalling LiveCycle ES Update 1 SP4 (22.214.171.124), to go back to LiveCycle ES Update 1 SP3 (126.96.36.199) on Windows.
Before installing/uninstalling any patch you should take note of the current versions installed so you can verify your steps have been successful later. Take a screenshot of the About screen, and the Service Management screen from the AdminUI.
AdminUI > About screen (note the Patch version “SP4″ and Service Pack version “8.1.5192.1.284202.47”, and the Patch level of each deployed component “SP4″):
AdminUI > Services > Applications and Services > Service Management screen (note the Component Versions “8.1.5192.1.284202.47”, “8.1.5193.1.279333.70”, etc…):
Before running through the uninstallation process it would advisable to make a backup of your existing configuration in case any unexpected problems should arise. To do this, you should make a copy of the entire LiveCycle installation directory (excluding the MySQL folder if it exists within the LiveCycle directory).
You should also take note of the following configuration properties from AdminUI > Settings > Core System Settings > Configurations:
- Location of temp directory
- Global document storage root directory (Changing this value will result in data loss unless you also manually move the data)
- Location of the Adobe Server Fonts directory
- Location of the System Fonts directory
If you have LiveCycle Content Services ES installed, you should also have the location of the Content Services root directory which you entered during the original installation/configuration process.
1. It is possible to leave your application server running for the moment, however you should stop your application server (JBoss, WebSphere, Weblogic) if possible.
2. Delete any files listed in <LiveCycle_HOME>\patch\SP4\backup_SP4\FilesAddedDuringServicePack_RemoveOrReplaceToRevert.txt from the <LiveCycle_HOME> directory. These are new/updated files which were added with this service pack/patch. To go back to a pre-SP4 state, we need to remove these files.
3. Copy all files under <LiveCycle_HOME>\patch\SP4\backup_SP4\ and paste them into their corresponding folder under the <LiveCycle_HOME> directory. This will overwrite the files which were updated by SP4 and restore them back to the SP3 state. This can include files in the configurationManager, deploy, LiveCycle_ES_SDK, and jboss folders.
4. Goto <LiveCycle_HOME>\licenses and edit each of the xxx.properties files. You will have a .properties file for each component installed, so you will need to perform the 2 steps below for each .properties file.
i). Delete the last PatchID section from the bottom of each file (in this case the entire SP4 section highlighted):
ii). Change the PatchVersion value at the top of the file to match the last PatchID now at the bottom (in this case SP3, as we just deleted SP4):
5. As we have now restored all the files in the <LiveCycle_HOME> directory, and have a backup of the SP4 configuration, we can now delete the EAR files in the <LiveCycle_HOME>\configurationManager\export directory.
6. Run Configuration Manager (LCM) and select the LC components you wish to configure.
7. Select the following tasks on the task selection dialog:
- Configure LiveCycle ES
- Deploy LiveCycle ES EARs (optional, you can also deploy the EARs manually once they are configured in the export folder, before initializing the DB)
- Initialize LiveCycle ES database
- Deploy LiveCycle ES components
- Validate LiveCycle ES component deployment
8. Follow all the dialogs and check the values of the local folders which you noted in the preparation tasks.
9. Once LCM has successfully completed deploying the EARs and components, you should check the version numbers again in the AdminUI to ensure they now show the original version numbers (in this case SP3).
AdminUI > About screen:
AdminUI > Services > Applications and Services > Service Management screen:
Note: if you see NoSuchMethodErrors in the server log, this would indicate that the DSC components do not match the version of the EARs deployed (e.g. the components are still SP4, whereas the EARs are SP3 or vice versa). Ensure you have successfully completed the EAR and component deployment, and you may need to restart your application server and perhaps even clean the application server temp folders to resolve such exceptions that appear in the server log.