There is a known issue with the LiveCycle ES SP3 installer wherein on some Linux systems, when running the installer you will get an OutOfMemoryError despite having more than 1 GB free memory (you probably don’t need that much, but it’s always safe on a server to have some leeway…)
To get around this issue, you can use a Windows staging platform for a Linux target system to perform the installation, deploy manually, and remotely run the Configuration Manager. This is also useful for locked down Linux systems where the app server is installed and accessible (for JBoss this means at least RW permissions in JBoss’s deploy directory), but you do not have the administrative rights to run the LiveCycle installer.
1. What does the patch/SP installer do?
Unlike your average Windows installer or Nix package installer, simply running and completing the LiveCycle Service Pack or patch installer will not have applied it to your live system. What the installer does is copy a series of JAR files to the LiveCycle installation’s holding directory, ready to be packged into EAR files for deployment – but does not do the packaging for you.
The packaging is left to the LiveCycle Configuration Manager which when launched will load the configurations from your previous installation run, and package the EARs accordingly, taking into account local system paths and parameters.
2. What’s the staging platform?
A Windows staging platform allows you to run the patch installer on a mock LiveCycle installation. You can thus run a patch installer on Windows and compile EARs for Nix, and then upload these files from the Windows box to the Nix box.
To setup a Windows staging platform, run the LiveCycle installer on a Windows machine and select a manual install. It will then ask you whether you want a regular installation or a staging installation. Select the staging option for the target operating system of your choice and complete the install, using the same parameters as you would use if installing natively on your target system.
Now you can run patch installations for your target LiveCycle live system from this “dummy” system.
3. Steps required for installing via a staging platform
- Copy the installer packages for LiveCycle and the Service Pack to a Windows machine (Win 2003 Server, Win XP Pro, Win7, Win 2008 Server)
- Run the LC installer – this is provided both with Windows and Linux executables, the actual significant code is Java so the same ZIP as used for Linux install can be used for Windows install
- Select a manual install, and then select a staging platform for your target operating system
- Once the components are “installed”, run the configuration manager to compile the EAR files
- When prompted to deploy the EARs, deploy the EAR files to the application server and restart it
- Continue with the configuration manager pointing to hte LiveCycle server’s IP address
Information is available from page 12 of the following guide: