DSC deployment takes a variable time due to which it might fail. To change the timeout of DSC operations such as Install, Load, Start, and Stop, you need to set the adobe.component.registry.timeout using the JVM argument with the -D option. The value for the key is specified in seconds. For example: -Dadobe.component.registry.timeout=300
You can also change the timeouts at the component level using the following three properties:
- adobe.all-component.timeout: overwrites the timeouts of all the Services of the Product.
- adobe.<serviceName>.timeout: overwrites the timeout only for the service (<serviceName>) mentioned in the key. If the value at service level is set, then using this command only overwrites the timeout value for the specified service if it is set at Application level.
- adobe.<serviceName>.<operationName>.timeout: It only overwrites the timeout for the specific service's operation(<serviceName>.<operationName>) mentioned in the key. If the value is set at Operation level, then using this command only overwrites the timeout value for the specified service if it is set at Application level or Service level.
Use the following commands to set the timeout at component level:
- To set all services's operations timeout to 600 sec:
set "JAVA_OPTS=%JAVA_OPTS% -Dadobe.all-component.timeout=600"
- To set the DesigntimeService operation values timeout to 500 sec, use:
set "JAVA_OPTS=%JAVA_OPTS% -Dadobe.DesigntimeService.timeout=500"
- To set the DesigntimeService's previewLCA operation values timeout to 700 sec, use:
set "JAVA_OPTS=%JAVA_OPTS% -Dadobe.DesigntimeService.previewLCA.timeout=700"
- To set the DSC operations such as load, install, and so on to 600 sec, use:
set "JAVA_OPTS=%JAVA_OPTS% -Dadobe.component.registry.timeout=600"
- Take a backup of the <LiveCycle_root>/deploy folder. It is required if you decide to uninstall the quick fix.
- Stop your application server.
- Extract the QF archive file to your hard drive.
- In the directory named according to the operating system that you are using:
Navigate to the appropriate directory on the installation media or folder on your hard disk where you copied the installer, and double-click the lces4_qf_install.exe file.
- (Windows 32-bit) CDROM_Installers\Windows\Disk1\InstData\VM
- (Windows 64-bit) CDROM_Installers\Windows_64Bit\Disk1\InstData\VM
- Linux, Solaris, AIX
Navigate to the appropriate directory, and from a command prompt, type ./lces4_qf_install.bin.
- (Linux) CDROM_Installers/Disk1/InstData/NoVM
- (Solaris) CDROM_Installers/Disk1/InstData/NoVM
- (AIX) CDROM_Installers/Disk1/InstData/VM
This launches an install wizard that guides you through the installation.
- On the Introduction panel, click Next.
- On the Choose Install Folder screen, verify that the default location displayed is correct for your existing installation, or click Browse to select the alternate folder where LiveCycle ES4 SP1 is currently installed, and click Next.
- Read the Quick Fix Patch Summary information and click Next.
- Read the Pre-Installation Summary information and click Install.
- When the installation is complete, click Next to apply the quick fix updates to your installed files.
- The Start Configuration Manager checkbox is selected by default. Click Done to run the Configuration Manager.
To run Configuration Manager later, deselect the Start Configuration Manager option before you click Done. You can start Configuration Manager later using the appropriate script in the [LiveCycle root]/configurationManager/bin directory.
- (JBoss only) If you are using connectors, edit the classpath mentioned in the following files and update the version of commons-collections-3.1.jar with commons-collections-3.2.2.jar:
- Depending on your application server, choose one of the following documents and follow the instructions in the Configuring and Deploying LiveCycle section.
- (JBoss only) After installing the patch and configuring the server, delete
tmpand work directories of JBoss application server.
- Restart the server machine.