Adobe LiveCycle ES4 Service Pack 1 Install Instructions and Fixed

Adobe LiveCycle ES4 Service Pack 1 Install Instructions and Fixed
Adobe LiveCycle ES4 Service Pack 1
Installation Instructions and Fixed Issues
Service Pack 1, Version 11.0.1
December 2013
Copyright 2013 Adobe Systems Incorporated and its licensors.
All rights reserved.
Contents
●
“Purpose of this Service Pack” on page 1
●
“Service Pack overview” on page 2
●
“Prepare to install the Service Pack” on page 2
●
“Installing the service pack for LiveCycle Designer ES4” on page 3
●
“Install the Service Pack for Workbench and Designer” on page 3
●
“Install and configure the Service Pack for LiveCycle server” on page 4
●
“Install the Service Pack for LiveCycle server using GUI” on page 5
●
“Install the Service Pack for LiveCycle server using CLI” on page 6
●
“Run Configuration Manager” on page 8
●
“Upgrade to LiveCycle ES4 and install the Service Pack” on page 10
●
“Applying the Service Pack to an upgraded LiveCycle deployment” on page 11
●
“Known issues” on page 13
●
“Revert LiveCycle ES4 server installation to pre- Service Pack 1 state” on page 14
●
“Issues addressed” on page 15
●
“Service Pack 1 (11.0.1)” on page 15
Purpose of this Service Pack
This Service Pack provides a lot of new features such as Forms Portal, Process Reporting, Mobile
Startpoints, Home Page, System Information Service, and support for right to left languages along with
general fixes for Adobe® LiveCycle® Enterprise Suite 4 (ES4).
You can download the service pack installer from the Download Adobe LiveCycle ES4 Service Pack page. For
detailed information about Service Pack, see What's New in LiveCycle ES4 Service Pack 1
Apart from the above, LiveCycle ES4 Service Pack 1 contains support for new platform combinations. For
detailed information, see Adobe LiveCycle ES4 Supported Platforms.
1
Adobe LiveCycle ES4, 11.0.1
Service Pack Installation Instructions
Service Pack overview
2
Service Pack overview
To successfully install and deploy the Service Pack, you must complete the following steps:
1. In the application server JVM arguments, add the JVM arguments:
-Djdk.logging.allowStackWalkSearch=true
Note: Skip this step if you are using Adobe preconfigured JBoss EAP 5.2.0 supplied with this service
pack.
2. Install the Service Pack.
3. Rebuild the EAR files using Configuration Manager.
4. Deploy the new EAR files using Configuration Manager or manually.
5. Bootstrap the database.
Note: This step does not affect the existing data.
6. Deploy the LiveCycle Components (DSC) and LiveCycle Archives (LCA) using Configuration Manager.
7. (Mobile Forms only). If you have installed Mobile Forms, Install Mobile Forms Installation Verification
Sample (IVS).
8. (Forms Portal only) If you have purchased a license for Forms Portal, install the Forms Portal
Integration Package using Package Manager.
9. (Mobile Workspace only) If you are using the Mobile Workspace app, you must complete the
following steps in the given order:
a. Notify Mobile Workspace users to sync offline-data for all of their tasks.
b. Install and configure Service Pack.
c. Notify Mobile Workspace users to uninstall the older version of app and install the newer version
provided in Service Pack.
10. Verify the Service Pack installation.
Note: Click here for information about the supported platform combinations for LiveCycle ES4.
Prepare to install the Service Pack
Consider the following points before installing the Service Pack:
●
Ensure that you have a fresh or an upgraded instance of LiveCycle ES4 running. For information on
installing or upgrading to LiveCycle ES4, see the appropriate documentation at
http://www.adobe.com/go/learn_lc_documentation_11.
●
Use any MD5 encryption utility to verify that the Service Pack files are downloaded properly. The
checksum number is posted on the Adobe download site.
●
Ensure that your environment is backed up. To create a backup, follow the instructions at Backing up
the LiveCycle data.
●
Ensure that you have sufficient free disk space available to install the Service Packs.
●
Service Pack for LiveCycle server requires 6 GB of disk space.
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Installing the service pack for LiveCycle Designer ES4
●
●
3
Service Pack for Workbench and Designer requires 200 MB of disk space.
In the Application Server JVM argument list, add the JVM argument :
-Djdk.logging.allowStackWalkSearch=true.
Note: Skip this step if you are using Adobe preconfigured JBoss EAP 5.2.0 supplied with this service
pack.
Installing the service pack for LiveCycle Designer ES4
If you have installed LiveCycle Designer ES4, perform the following procedure to install the service pack for
LiveCycle Designer.
❱
To install the service pack for LiveCycle Designer ES4:
1. Run Designer11_English_SP1.exe. This step opens a wizard that guides you through the installation.
2. On the Welcome screen, click Update.
3. On the InstallShield Wizard Completed screen, click Finish to exit the wizard.
4. Start LiveCycle Designer, select Help > About LiveCycle Designer, and then verify the version number
is 11.0.1.20130826.2.901444.
Install the Service Pack for Workbench and Designer
There are two methods to incorporate Adobe® LiveCycle® Workbench 11 SP1 functionality into your
LiveCycle environment:
●
Default integrated development environment
●
As a plug-in to an existing Eclipse 3.6.2 environment
Perform the following procedure to install Workbench. This procedure installs Designer, LiveCycle samples,
and the Workbench Eclipse feature.:
1. Ensure that Workbench is not running.
2. If you have a version of Workbench 11 installed, uninstall it.
Note: Adobe® LiveCycle® Workbench 11 Service Pack 1 contains complete installer. Before continuing
with installation, ensure that you do not have Workbench 11 installed.
3. If you have a version of Adobe Designer 11 installed, uninstall it.
Note: Adobe® LiveCycle® Workbench 11 Service Pack 1 contains complete installer for Adobe Designer.
Before continuing with installation, ensure that you do not have Designer 11 installed.
4. Do one of these tasks:
●
Navigate to the \workbench directory on the install media and double click the
run_windows_installer.bat file.
●
Download and decompress the Workbench to your file system. After it is downloaded, navigate to
the \workbench directory and double click the run_windows_installer.bat file.
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Install and configure the Service Pack for LiveCycle server
4
Note: The Workbench installer only runs from a DVD or local drive. It cannot be run from a remote site.
5. On the Introduction screen, click Next.
6. Read the Product License Agreement, select I accept the terms of the License Agreement, and then
click Next.
7. (Optional) Select Install Designer 11.0.1 if you require this tool to create and modify forms.
Note: You can continue to use Designer installed with earlier versions of Acrobat by leaving this option
deselected.
8. Accept the default directory as listed, or click Choose and navigate to the directory where you will
install Workbench, and then click Next.
Note: The installation directory path should not contain # (pound) and $ (dollar) characters.
9. Review the preinstallation summary and click Install. The installation program displays the progress of
the installation.)
10. Review the installation summary. Select Start Adobe LiveCycle Workbench ES4 to launch Workbench
and click Next.
11. Review the Release Notes and click Done.
12. The following items are now installed on your computer:
●
Workbench: To run Workbench from the Start menu, select All Programs > Adobe LiveCycle ES4 >
Adobe LiveCycle Workbench ES4 SP1, if you chose to store the shortcut folder there.
●
Designer: You can access Designer from inside Workbench.
●
Workbench plug-in: To complete the plug-in configuration, follow the instructions provided in
Installing the Workbench Eclipse feature.
Install and configure the Service Pack for LiveCycle server
Perform the following procedures to install the Service Pack:
●
Install the Service Pack using the Graphical User Interface (GUI) (see “Install the Service Pack for
LiveCycle server using GUI” on page 5).
or
Install the Service Pack using the Command-line interface (CLI) (see “Install the Service Pack for
LiveCycle server using CLI” on page 6)
●
●
Configure and deploy LiveCycle for the Service Pack using LiveCycle Configuration manager (see “Run
Configuration Manager” on page 8).
(For LiveCycle clusters using TCP locators) Replace gemfire files (see “Replace gemfire files” on
page 10).
Note: Ensure that Configuration Manager is not running before you start the Service Pack installation
wizard.
Caution: While running Configuration Manager, ensure that you perform the Initialize LiveCycle
Database task to properly configure the Service Pack. This step does not affect the existing data.
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Install the Service Pack for LiveCycle server using GUI
5
Install the Service Pack for LiveCycle server using GUI
1. Run the appropriate installer for your operating system:
●
(Windows) server\Disk1\InstData\Windows_64bit\
VM/lces4_sp_install.exe
●
(AIX) server/Disk1/InstData/AIX/VM/lces4_sp_install.bin
●
(Linux) server/Disk1/InstData/Linux/NoVM/lces4_sp_install.bin
●
(Solaris)server/Disk1/InstData/Solaris/NoVM/lces4_sp_install.bin
This step opens a wizard that guides you through the installation.
Note: On a UNIX-like system, when you download files from the source, lces4_sp_install.bin might lose the
executable permissions. Ensure that you restore the write-execute permissions after downloading
the files.
2. When prompted, select the language to use for the installation and then click OK.
3. On the Introduction screen, click Next. s
4. On the Choose Install Folder screen, verify that the default location displayed is correct for your existing
installation, or click Choose to select the alternate folder where Adobe LiveCycle ES4 is currently
installed, and click Next.
5. If you are using the JBoss application server, perform the following instructions:
a. (Turnkey Only)On the Upgrade to JBoss EAP 5.2.0 screen, choose Upgrade to JBoss EAP 5.2.0,
and click Next.
b. If you have not upgraded to JBoss 5.2.0:
●
Add the -Dgemfire.disableManagement=true argument in the (Linux) [JBoss_root]\bin\run.conf
or (Windows) [JBoss_root]\bin\run.conf.bat file.
●
The existing Windows Service would not respect above JVM argument. Create a new
Windows Service for JBoss. For detailed information on how to create Windows Service for
JBoss, see Configuring JBoss as a Windows Service.
6. (Turnkey Only) Read the JBoss Application Server License Agreement, select I accept to accept the
terms of the license agreement and then click Next. If you do not accept the license agreement, you
cannot continue.
7. On the Service Pack Summary screen, review the information and, if it is correct, click Next.
8. On the Pre-installation Summary screen, review the information and, if it is correct, click Install.
Note: This step may take a few minutes to complete.
9. On the Apply Patch screen, click Next.
Note: (Turnkey only) On applying the patch, If on the Upgrade to JBoss EAP 5.2.0 screen the Upgrade to
JBoss EAP 5.2.0 checkbox is selected, the JBoss version is updated to 5.2.
Note: The typical time to apply patch updates is approximately 5 minutes. However, depending upon the
resources available on your system, applying patches may take as many as 15 minutes.
10. When the Installation Complete screen refreshes to indicate a successful installation, ensure that Start
Configuration Manager is selected and then click Done.
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Install the Service Pack for LiveCycle server using CLI
6
Note: On AIX, start Configuration Manager manually by running the ConfigurationManager.sh script from
the [LiveCycle root]/configurationManager/bin/ directory.
Note: (Non-turnkey Only)If you are using downloaded JBoss 5.2, add the JVM argument
-Dorg.jboss.net.protocol.file.useURI=false to the (Unix/Linux) [JBoss_root]\bin\run.conf or (Windows)
[JBoss_root]\bin\run.conf.bat file. For detailed information on configuring JBoss, see the Preparing to
install LiveCycle document.
Install the Service Pack for LiveCycle server using CLI
11. At the command line, navigate to the directory relevant for your operating system:
●
(64-bit Windows) server\Disk1\InstData\Windows_64bit\VM\
●
(AIX) server/Disk1/InstData/AIX/VM/
Note: AIX is supported only for WebSphere Application Server.
●
(Linux) server/Disk1/InstData/Linux/NoVM/
●
(Solaris) server/Disk1/InstData/Solaris/NoVM/
12. Execute the following command:
(Windows) lces4_sp_install -i console
(UNIX) ./lces4_sp_install -i console
13. Follow the on-screen instructions. For more information, see the table below.
Prompt
Description
Choose Locale
Select the locale for the installation to use by entering a value from
1 through 3. Type 1 for German, 2 for English or 3 for French and
then press Enter.
You can also select the default language by pressing Enter. English
is the default language.
Note: If you are using Japanese language OS, you may see an
option to select Japanese locale for the installation.
Choose Install Folder
On the Destination screen, press Enter to accept the default
directory or select the location where LiveCycle ES4 in currently
installed.
Default install folders are:
(Windows): C:\Adobe\Adobe LiveCycle ES4
(AIX, Linux, Solaris): /opt/adobe/adobe_livecycle_ES4
Note: Do not use accented characters in the directory name.
Otherwise, CLI will ignore the accents and create a directory
after modifying the accented characters.
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Install the Service Pack for LiveCycle server using CLI
Prompt
Description
Upgrade to JBOSS 5.2 or continue
with 5.1
(Turnkey Only) On the Upgrade to JBOSS 5.2 or continue with 5.1
screen, press Enter to upgrade to JBoss EAP 5.2.0.
Note: If you choose not to upgrade to JBoss 5.2.0, add the
-Dgemfire.disableManagement=true argument in the (Linux)
[JBoss_root]\bin\run.conf or (Windows)
[JBoss_root]\bin\run.conf.bat file.
(Turnkey only) EULA
Read the JBoss Application Server License Agreement, press Enter
to accept the terms of the license agreement. If you do not accept
the license agreement, you cannot continue.
Pre-Installation Summary
Review the installation choices you have made and press Enter to
continue installation with the choices you have made.
Tip: Type back to go back to previous steps and change any of the
settings.
Service Pack will be applied to the
following items
Review the list of items and and press Enter to continue
installation with the choices you have made.
Tip: Type back to go back to previous steps and change any of the
settings.
Ready To Install
Installer displays the installation directory.
Press Enter to start the installation process. During the installation
process, the progress bar advances to indicate the progress of
installation.
Tip: Type back if you want to change the settings, or quit to close
the installation.
Installing
The progress of the installation process is indicated.
Apply Patch
Press Enter to apply Service Pack and replace existing files with the
updated ones.
Note: (Turnkey only) On applying the patch, the JBoss version is
updated to 5.2.
7
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Run Configuration Manager
Prompt
Description
LiveCycle Configuration Manager
Press Enter to complete the installation.
8
You can run the Configuration Manager by running the following
script:
(Windows):
[LiveCycle_root]\configurationManager\bin\ConfigurationMan
ager.bat
(AIX, Linux, Solaris):
[LiveCycle_root]/configurationManager/bin/ConfigurationMa
nager.sh
For more information, see “Run Configuration Manager” on page 8.
For Configuration Manager steps relevant to clustered
configurations, see the Configuring LiveCycle Application Server
Clusters document that applies to your application server.
Installation Complete
The installation completion screen displays the status and the
location of install.
Press Enter to exit the installer.
Note: To correctly uninstall LiveCycle, run the uninstaller from the
command line, using the -i console flag.
Run Configuration Manager
Note: (SUSE Linux 11 only) Before running the Configuration Manager, delete the
[application_server_root]\server\<profile>\svcnative folder. For detailed information see, Known
issues
Note: When Jboss is upgraded to the version 5.2, the jboss directory along with the existing profiles and
crx_repository is replaced with a newer version. To recover information from the backup, see
Custom changes in the JBoss root folder are overwritten.
Note: If the Configuration Manager is running, Skip step 1 and 2 of the following procedure.
1. Before running the configuration manager, increase memory allocation limit of configuration manager.
To increase the memory allocation limit:
a. Navigate to [LiveCycle_installation_directory]\configurationManager\bin and open the following
file for editing:
●
(Windows) ConfigurationManager.bat
●
(Linux, UNIX) ./ConfigurationManager.sh
b. Locate the following text:
LAUNCH
set JAVA_OPTS=-Xms128m -Xmx1024m -Dfile.encoding=utf8 %LCM_USE_STACK%
c. Change the memory allocation limit from -Xmx1024m to -Xmx1536m.
d. (Solaris) In JAVA_OPTS, add the -d64 arguments.
e. Save and close the ConfigurationManager.bat/ConfigurationManager.sh file.
Adobe LiveCycle ES4, 11.0.1
Service Pack Installation Instructions
Run Configuration Manager
9
2. Start Configuration Manager manually by navigating to the [LiveCycle_root]/configurationManager/bin
directory and entering the following command:
●
(Windows) ConfigurationManager.bat
●
(Linux, UNIX) ./ConfigurationManager.sh
3. When prompted, select the language for the Configuration Manager and click OK.
4. On the Welcome screen, click Next.
5. On the Upgrade Task Selection screen, ensure that no options are selected, and then click Next.
6. On the Modules screen, keep the defaults or select the components that you have licensed. Click Next.
7. Depending on your application server, choose one of the following documents and follow the
instructions in the Configuring and Deploying LiveCycle section.
●
Installing and Deploying LiveCycle ES4 for JBoss
●
Installing and Deploying LiveCycle ES4 for WebSphere
●
Installing and Deploying LiveCycle ES4 for WebLogic
●
Configuring LiveCycle Application Server Clusters Using JBoss
●
Configuring LiveCycle Application Server Clusters Using WebLogic
●
Configuring LiveCycle Application Server Clusters Using WebSphere
●
Upgrading to Adobe LiveCycle ES4 for JBoss
●
Upgrading to Adobe LiveCycle ES4 for WebLogic
●
Upgrading to Adobe LiveCycle ES4 for WebSphere
8. (Content Repository Only) After deploying the EAR, when you are asked to restart the application
server, ensure that the CRX is up and running and before restart ing the application server. To ensure
that CRX is up and running, login to the CQ Welcome Page.
The CQ Welcome Page is at http://[hostname]:[port]/lc/welcome. A successful login to the the CQ
Welcome page implies the CRX is up and running.
Note: On some instances, CRX server might take longer than expected to be up and running and CQ
Welcome page might be slow in loading. Wait until the CRX server is up and running; try logging
to the CQ Welcome page after some time.
9. (Mobile Forms only) If you have installed Mobile Forms, you can verify the installation of Mobile Forms
service and how it renders forms using Mobile Forms Installation Verification Sample (IVS). For detailed
instructions to install Mobile Forms IVS, Set up the Mobile Forms Installation Verification Sample
application.
10. (Form Manager only) If you have installed Forms Manager, perform manual synchronization of assets.
For detailed information, see On demand asset synchronization.
11. (Forms Portal only) If you have purchased a license for Forms Portal, you need to install the Forms
Portal Integration Package using Package Manager. Forms Portal Integration Package is available on
Package Share. For detailed instructions, see Getting Started with Forms Portal Integration Package.
12. (Mobile Workspace only) Service Pack 1 includes a newer version of the Mobile Workspace app. If you
are using the Mobile Workspace app, uninstall the older version of app and install the newer version
Adobe LiveCycle ES4, 11.0.1
Service Pack Installation Instructions
Replace gemfire files
10
provided in Service Pack 1. For detailed installation instructions, see Migrating the Mobile Workspace
app.
Note: The older version of the Mobile Workspace app (Mobile Workspace app shipped along with
LiveCycle ES4) is not compatible with LiveCycle ES4 SP1.
13. Restart the application server.
Note: In a clustered configuration, restart each application server instance of the cluster.
Note: If you do not restart the application server after installing Service Pack, you may encounter error
"ALC-WKS-007-027" and PDF forms will fail to render.
Note: If you do not restart the application server after installing Service Pack, you may encounter error
"ALC-WKS-005-055" and the StartPoints will fail to initiate.
14. Log in to Administration Console by typing the URL http://[host name]:[port]/adminui in a web
browser.
Tip: To verify the Service Pack installation, log in to the Administration Console and select About. Ensure
that the Service Pack version indicates SP1. Also, ensure that all Installed Modules report SP1 under
the Patch column.
Replace gemfire files
For the LiveCycle Clusters configured to use TCP locators, perform the following procedure to replace
gemfire files:
❱
To replace gemfire files:
1. After installing and configuring the Service Pack, stop all the TCP locators.
2. Navigate to the [lc_root]/lib/caching directory.
3. Replace the gemfire.jar and GemFireVersion.properties files present in the TCP locator directory with the
gemfire.jar and GemFireVersion.properties files located in the [lc_root]/lib/caching directory.
4. Start the TCP locators.
5. Restart the cluster.
Upgrade to LiveCycle ES4 and install the Service Pack
Perform the following procedure to upgrade from LiveCycle version ES Update 1 or ES2 to LiveCycle ES4
and apply the Service Pack.
➤ To upgrade to LiveCycle ES4:
1. Upgrade to LiveCycle ES4 by following the instructions in the Upgrading to LiveCycle ES4 document for
your application server. (See the "Installing the product files" section.) Do not start Configuration
Manager.
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Applying the Service Pack to an upgraded LiveCycle deployment
11
2. Apply the Service Pack to the installed files by following steps 1 through 10 of the “Install the Service
Pack for LiveCycle server using GUI” on page 5 procedure.
3. Start Configuration Manager as instructed in steps a through 4 of the “Run Configuration Manager” on
page 8 procedure.
4. Complete the configuration, upgrade, and deployment by following the instructions in the
"Configuring LiveCycle for Deployment" chapter of the Upgrading to LiveCycle ES4 document for your
application server.
Applying the Service Pack to an upgraded LiveCycle deployment
If you have upgraded from LiveCycle ES Update1 or ES2 to LiveCycle ES4, perform the following steps to
apply the Service Pack:
➤ To apply the Service Pack to an upgraded LiveCycle Server:
1. Apply the Service Pack by following the steps 1 through 10 of the “Install the Service Pack for LiveCycle
server using GUI” on page 5 procedure in this document.
2. Start Configuration Manager as instructed in steps a through 4 of the “Run Configuration Manager” on
page 8 procedure.
3. On the Upgrade Task Selection screen, select one of the following, as required:
●
Upgrade from LiveCycle ES2 or LiveCycle ES 2.5
●
Upgrade from ADEP
●
Upgrade from LiveCycle ES3
4. On the Task Selection screen, select the following task options:
●
Configure EARs
●
Deploy EARs (if you are deploying to JBoss Turnkey, WebSphere, or WebLogic; otherwise, you can
manually redeploy the EAR files by following the instructions in the Installing and Deploying
LiveCycle document for your application server.)
●
Initialize database
●
Deploy components
●
Validate component deployment
●
(Optional) Configure the connectors for ECM, Reader Extensions, and PDF Generator
●
(Optional) Import Samples into LiveCycle
Note: Do not select the tasks to configure the application server or validate the application server.
5. Complete the configuration, upgrade, and deployment of the patched EAR files by following the
instructions in the Configuration Manager wizard and in the "Configuring LiveCycle for Deployment"
section of the Upgrading to LiveCycle ES4 document for your application server.
Note: If the LiveCycle 11.0.1 EAR files fail to deploy through Configuration Manager, manually
undeploy the LiveCycle EAR files for the components you are updating according to the
documentation. Restart the application server before you run Configuration Manager again.
6. Restart your application server.
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Correspondence Management : Author Publish configuration
12
Tip: To verify the Service Pack installation, log in to the Administration Console and select About. Ensure
that the Service Pack version indicates SP1. Also, ensure that all Installed Modules report SP1 under
the Patch column.
Correspondence Management : Author Publish configuration
Configure Correspondence Management Solution
The following steps are applicable only for the users, who have:
●
completed fresh installation of LiveCycle ES4 and LiveCycle ES4 Service Pack 1
●
never configured Correspondence Management Solution on the earlier installations.
Depending on your application server, choose one of the following documents and follow the instructions
in the Configure Correspondence Management Solution section.
●
Installing and Deploying LiveCycle ES4 for JBoss Turnkey
●
Installing and Deploying LiveCycle ES4 for Jboss
●
Installing and Deploying LiveCycle ES4 for WebSphere
●
Installing and Deploying LiveCycle ES4 for WebLogic
Note: If you have configured Author and Publish instances on a single JBoss server and you have
upgraded to JBoss 5.2, see Unable to pass command line arguments
Update the build on the Publish instance
You must run separate Author and Publish instances for Correspondence Management Solution. After
installing service pack 1 on Author, update the build on the Publish instance.
Note: Before configuring the Publish instance ensure that,
●
the LiveCycle ES4 Service Pack 1 is configured and deployed on the Author instance.
●
Publish instance is configured and running on ES4.
You can verify the above by successfully logging in to the solution template for Correspondence
management Solution.
Perform the following steps to update the build on publish instance:
1. On the author instance, navigate to the [LiveCycle root]/configurationManager/export/ crx-quickstart
directory.
2. On the Publish instance, navigate to location of the crx-repository. Delete the install folder inside the
crx-repository.
3. Copy the [LiveCycle root]/configurationManager/export/ crx-quickstart/install folder from the Author
instance to the Publish instance.
4. On the Publish instance, open the crx-repository/install folder. Keep the following packages and delete
all other packages from the install folder:
●
dataservices-pkg.zip
●
platform-common-pkg.zip
Adobe LiveCycle ES4, 11.0.1
Service Pack Installation Instructions
Known issues
●
platform-content-pkg.zip
●
platform-security-pkg.zip
●
solution-correspondencemanagement-pkg.zip
13
5. Start the Publish instance with -Dcom.adobe.livecycle.crx.home=<location for crx-repository>
parameter, where <location for crx-repository> is the path to the crx-repository for the Publish
instance.
6. Deploy adobe-livecycle-cq-publish.ear to the server.
Note: If you have configured Author and Publish instances on a single JBoss server and you have
upgraded to JBoss 5.2, see Unable to pass command line arguments
Known issues
The adobe-livecycle-native ear file is not deployed correctly
(SUSE Linux 11 only) On restarting the service, the adobe-livecycle-native ear file is not deployed correctly
and .so files and symlink are not deleted from the XMLFormService/bin directory. To resolve the issue, before
starting the Configuration Manager, delete the [application_server_root]\server\<profile>\svcnative
folder.
Unable to pass command line arguments
(JBoss 5.2 only) If you have configured Author and Publish instances on a single JBoss server and you have
upgraded to JBoss 5.2, JBoss server fails to accept argument from command line. To resolve the issue,
1. In the [JBoss_root]/bin folder, create a file publish.properties.
2. Open the file for editing and add the following parameters in the file:
jboss.service.binding.set=ports-01
com.adobe.livecycle.crx.home=<crx_repository_path>
Note: Use escape characters in the path. For example, C:\\Adobe\\crx-repository
3. Save and close the publish.properties file.
4. To include the property file in the startup of JBoss application server, run the following command:
run -c <jboss_instance> -b 0.0.0.0 -P publish.properties
Custom changes in the JBoss root folder are overwritten
On installing LiveCycle ES4 SP1, When JBoss is upgraded to version 5.2, the jboss directory along with the
existing profiles and crx_repository is replaced with a newer version.
LiveCycle creates a backup of JBoss 5.1 at [livecycle_root]\patch\SP1\backup_Jboss51.
Perform the following steps to recover information from the backup:
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Revert LiveCycle ES4 server installation to pre- Service Pack 1 state
14
1. To recover information for Author instance:
After installation is complete, copy the crx_repositoy located in the backup folder to the LiveCycle
installation directory. For example, if the crx_repository path is
<livecycle_root>\jboss\server\lc_turnkey\crx_repository then, before running the LCM, copy all the
content from <livecycle_root>\patch\SP1\backup_Jboss51\jboss\server\lc_turnkey\crx_repository to
<livecycle_root>\jboss\server\lc_turnkey\crx_repository.
2. To recover information for Publish instance:
a. Create a profile for the Publish instance.
b. Copy the Publish crx_repository from the backup folder to the existing JBoss installation.
c. Proceed with the crx package update and other configurations.
Revert LiveCycle ES4 server installation to pre- Service Pack 1
state
1. Open the FilesAddedDuringServicePack_RemoveOrReplaceToRevert.txt file located in the[LiveCycle ES4
root]\patch\SP1\folder.
2. From your existing LiveCycle ES4 installation, delete the files and folders listed in
FilesAddedDuringServicePack_RemoveOrReplaceToRevert.txt.
3. Replace the files/folders in the following directories under [LiveCycle ES4 root] with files from the
backup copy located at [LiveCycle ES4 root]\patch\SP1\backup_SP1:
●
configurationManager
●
deploy
●
docs
●
lib
●
pdfg_srt
●
plugins
●
sdk
Note: For more information, refer to the patch logs at [LiveCycle ES4 root]\patch\SP1\log.
4. After restoring the [LiveCycle ES4 root]\configurationManager directory, delete the EAR files in the
[LiveCycle ES4 root]\configurationManager\export directory.
Note: If , for LiveCycle ES4 Service Pack 1, you installed JDK 1.7, then for LiveCycle ES4 uninstall JDK 1.7
and install JDK 1.6 .
5. If you are uninstalling the Service Pack from JBoss Application server:
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Issues addressed
15
a. Stop the JBoss Application server.
b. (Turnkey Only)Take backup of existing [LiveCycle root]\jboss folder and replace its content with
the backup available at in [LiveCycle ES4 root]\patch\SP1\backup_Jboss51\jboss.
c. (Turnkey Only) Change value of Adobe_JAVA_HOME and JAVA_HOME_32 environment
variables to the installation location of JDK 1.6.
d. (Non-Turnkey Only) Change value of JAVA_HOME and JAVA_HOME_32 environment variables
to the installation location of JDK 1.6.
e. Remove the System info DSC connector component :
●
Connect to the server through the LiveCycle Workbench.
●
Open Components view in LiveCycle Workbench.
●
Stop the sysinfo component .
●
Uninstall the sysinfo component.
f. Clear the Work and Temp directories.
g. Restart the JBoss Application server.
6. Run LiveCycle Configuration Manager.
7. (Optional) If you do not require the SP1 patch files, delete the [LiveCycle ES4 root]\patch\SP1 directory.
Issues addressed
Service Pack 1 (11.0.1)
ECM Connectors
●
[Ref #3184517] SharePoint Connector’s temporary files of size 100 mb to 400 mb remain locked and
fail to delete.
●
[Ref #3542602] LiveCycle takes long time to create folders on Microsoft SharePoint servers.
Core - User Manager
●
[Ref #3557296] A large IDP metadata file fails to get imported when configuring SAML authentication
provider in an enterprise or hybrid domain.
●
[Ref #3527858] The LDAP process fails to synchronize users between user management and domain.
The impacted users fail to log in to the LiveCycle services.
●
[Ref #3293835] After a group member is removed, the User management LDAP logs show
inconsistent information.
Correspondence Management
●
[Ref #3568075] If the user selects an asset beyond the initial screen display, the screen is redrawn with
the first asset in the list being displayed at the top of the screen. The user then scrolls back down to the
selected asset to interact with it.
●
[Ref #3567411] If a user is currently in the last asset that is visible on the screen and the user presses
the Tab key, the panel should scroll to shift the focus to the next asset in the panel. However, the focus
shifts out of the panel to the next control in the Create Correspondence UI.
Service Pack Installation Instructions
Adobe LiveCycle ES4, 11.0.1
Service Pack 1 (11.0.1)
16
●
[Ref #3561446] In the Create Correspondence UI, if a user presses the Tab key, the next field in the tab
order is highlighted but the focus does not shift to the field. The user presses the Tab key twice to move
to the next field.
●
[Ref #3561445] If a field contains ligatures and the Left Arrow Key is used to navigate through the text
in the field, the cursor stops as soon as it encounters a ligature.
●
[Ref #3561439] The source information for fields and variables is displayed in the Data Panel of Create
Correspondence UI.
●
[Ref #3561297] If any of the placeholders contain accented characters, these accented placeholders
are grouped together and displayed first followed by the non-accented placeholders, also grouped
together.
●
[Ref #3560729] A user can mark as optional or mandatory fields or variables that are linked to
unprotected data dictionary elements.
●
[Ref #3488947] If a user creates a Free Form Text asset containing text and bullets, the asset does not
save.
Process Management
●
[Ref #3577583] Now, you can pre-fill fields of a HTML Form. It was not supported earlier.
●
[Ref #3569743] A process terminated in the LiveCycle Administration Console is displayed as
Completed. Such processes should be displayed as Terminated.
●
[Ref #3540698]
●
●
(In Mozilla Firefox)On opening a bookmarked HTML Workspace page, the page fails to load. When
the user refreshes the page, the login screen is displayed. On login, the user is presented with
default HTML Workspace screen instead of bookmarked HTML Workspace Page.
●
(In Google Chrome) On opening a bookmarked HTML Workspace page, the page fails to load.
When the user presses refresh, the login screen is displayed. On login, the user is presented with
following error messages:
●
Access Denied. You do not have enough privileges to run HTML Workspace
●
Error while initialization of: categorylistview[TypeError: Cannot call method ‘replace’ of
undefined]
[Ref# 3591135] On terminating a process instance, status of the process is changed to initiated,
running, or terminating; whereas, the correct status is terminated.
●
PDF Generator
●
[Ref #3567723, 3567727] PDF Generator fails to convert Password Protected Microsoft Excel
documents to PDF documents. Instead of reporting that the file is password protected, the conversion
times-out.
●
[Ref #3547459] Multithread conversion does not work on the customer environment. Even though
multiple users have been defined, only one user is used for all conversions.
HTML Forms (Mobile Forms)
●
[Ref# 3582872] Mobile Forms API renderPDFForm2 did not produce expected output.
●
[Ref# 3540890] The renderPDFForm API fails to merge XML data with reader extended PDF
documents.
Adobe LiveCycle ES4, 11.0.1
Service Pack Installation Instructions
Service Pack 1 (11.0.1)
17
Output
●
[Ref# 3540588] LiveCycle Central Migration Bridge fails with an error: ALC-CMB-001-002: jfmerge
returned with an error code: 2. The concurrent process cause jfmerge to fails with error: [2]Error opening
output device/file 'C:\Windows\TEMP\JFM142C.tmp'
●
[Ref# 3374963] PDF Generator fails to generate a PDF and returns a CORBA error:
com.adobe.printSubmitter.PrintException: org.omg.CORBA.COMM_FAILURE.
●
[Ref# 3341580] The XMLForm.exe service uses Operating Systems temporary directory instead of
LiveCycle temporary directory. Even after adding a redirection to use LiveCycle temporary directory it
uses Operating Systems temporary directory for files larger than 250 MB.
Rights Management
●
[Ref# 3578042] LiveCycle Rights Management user interface (UI) contains hyperlinks that refer to
Online Help. LiveCycle does not provide any mechanism to disable such links.
●
[Ref# 3573261] To search top 10 policies, backend database query uses CONTAINS search criteria
instead of IS EQUAL TO search criteria.
●
[Ref# 3572942] If an ampersand character is present in the Rights Management URL, Adobe Reader/
Acrobat do not open or follow the revocation URL link.
●
[Ref# 3539313] User is unable to set font size, color, and opacity for watermarks.
●
[Ref# 3537563] The autocomplete feature is not explicitly disabled in the Rights Management UI.
●
[Ref# 3526863] When an apostrophe symbol is used in the Custom Text field of the Watermark
configuration for a policy an error occurs: Custom Text contains invalid characters. HTML elements and
script tags are not allowed.
●
[Ref# 3500888] When a user activates offline access for documents protected with Rights
Management, then the user can open all protected documents, regardless of whether they have
previously been opened online mode or not.
●
[Ref# 3432254] Rights Management APIs does not support setting watermark position using points
specification.
Signatures
●
[Ref# 3583808] A signature marked valid in Adobe Acrobat is displayed invalid in Adobe LiveCycle.
●
[Ref# 3593825] On testing a query on JDBCService, the process file gets corrupted.
Designer
●
[Ref# 3344378] Designer does not translate UTC Time to GMT Time.
●
[Ref# 3520937] LiveCycle designer does not provide options to set the Initial View/Windows option
settings to display the document’s title.
●
[Ref# 3010587, 3010354] When designer imports a single-page word document that contains lists in
a 2 column layout, it generates an XDP with incorrect layout that spans multiple pages.
●
[Ref# 3010581] When a Microsoft Word document is imported, first line in list items is separated from
the rest of paragraph.
●
[Ref# 3010600] When a Microsoft Word document is imported, text and objects are not
auto-wrapped.
●
[Ref# 3010595] Users are unable to import a Microsoft Word document as a flow able editable layout.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement