- Livecycle Designer 8.0 Save Fillable Form
- Adobe Livecycle Designer Tutorial Pdf
- Adobe Live Cycle Designer Tutorial
Version 8.0.1
Adobe® LiveCycle® Designer 8.0 Scripting Basics for Microsoft® Windows® Edition 1.0. LiveCycle Designer Scripting Basics Related documentation 8. Should I remove Adobe LiveCycle Designer 8.0 by SAP? Learn how to remove Adobe LiveCycle Designer 8.0 from your computer.
Release Notes | July 2007 |
Adobe® LiveCycle® Designer ES4 software helps you easily author form and document templates that combine high-fidelity dynamic presentation with sophisticated XML data handling. LiveCycle Designer ES4 lets you create form templates that can output to paper, PDF, and HTML5 without having to write scripts. Core support for Adobe LiveCycle ES4 ends March 2018. Consider upgrading from LiveCycle to Adobe Experience Manager Forms today Learn more Adobe® LiveCycle® Enterprise Suite 4 is an enterprise document and form platform that helps you capture and process information, deliver personalized communications, and protect and track.
Edition 1.1
Copyright 2007 Adobe Systems Incorporated. All rights reserved.
This file contains important information that was not available when the product documentation was written. Review this information before running this version of Adobe® LiveCycle® ES.
Contents
System Requirements
LiveCycle ES requires that you have the following software:
- Adobe Flash Player 9.0.45.0 for LiveCycle Workspace ES or for using form guides in LiveCycle Workspace ES
- Flex Builder 2.0.1 Hot Fix 2 or higher or Flex SDK 2.0.1 Hot Fix 2 or higher for the following:
- using LiveCycle Data Services ES
- customizing form guides in LiveCycle Designer ES
- customizing LiveCycle Workspace ES
- creating Flex applications for LiveCycle Workspace ES
- calling LiveCycle APIs using Flex
For a complete list of system requirements, see the 'System requirements' section in Preparing to Install LiveCycle ES.
Microsoft .NET version requirements
For Guide Builder to install and function correctly, you must ensure that .NET version 1.1 Service Pack 1 or higher is installed on the computer running LiveCycle Designer ES. .NET version 1.1 is available from the LiveCycle Designer ES installation wizard. You can download .Net 1.1 Service Pack 1 from www.microsoft.com. Developing drivers windows driver foundation pdf converter.
Note: Multiple versions of .NET can exist concurrently on the same computer without overwriting each other.
Installation Issues
General Installation Issues
(UNIX, Linux) Installer binary files have the wrong permissions
The installer binary files on computers running UNIX and Linux do not have execute permissions. After these files are copied to your computer, you must change the file permissions by using the chmod command to include execute permissions.
Cannot uninstall LiveCycle ES components
It is recommended that you do not uninstall any LiveCycle ES components, such as endpoints, individually. If you want to uninstall LiveCycle ES, see the 'Uninstalling LiveCycle ES' section in the Installing and Deploying LiveCycle ES document for your application server.
Canceling LiveCycle Workbench ES installation does not cancel LiveCycle Designer ES installation
During the installation of LiveCycle Workbench ES, if you click Cancel after the progress bar has indicated that LiveCycle Designer ES is being installed, an error is thrown when the installation wizard closes and LiveCycle Designer ES is still installed. You must manually uninstall LiveCycle Designer ES.
Subsequent installations fail to display expected dialogue
When an installation has failed or been canceled, the VPD files may have become corrupt. A VPD (Vital Product Data) file is an InstallShield database that is used to maintain user data during an installation. These files must be deleted to run a successful, subsequent installation.
The VPD files that must be deleted are in the following locations:
- (Windows) C:Program FilesCommon FilesInstall ShieldUniversalAdobeLC8
- (UNIX) /home/USERNAME/installshield/universal/adobe/lc8
- (Windows or UNIX) Delete the Gen1 directory from the LC8 directory
This directory paths assume you have installed in the default location.
Note: Ensure that you do not run the uninstall program after you delete the VPD files.
If you run the uninstall program after you delete the VPD files, a message similar to this one will be displayed:
engine is missing (C:Program FilesCommon FilesInstall ShieldUniversalAdobeLC8Gen1): run installation from source media
The message displayed indicates that LiveCycle ES must be manually removed from the computer before a subsequent installation can be performed:
- (Windows or UNIX) Delete the directory [LiveCycleES root]
- (Windows) Delete the registry key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstalleb6e469e8f49062609d2f6082e34d944-1213923530
Clicking Cancel at language selection returns error message
An error message similar to the one below is displayed when you click Cancel instead of choosing an installation language.
2007/06/09 5:23:03 run main .
Click OK and ignore this message. The installation will cancel normally.
LiveCycle Configuration Manager
Some screens in LiveCycle Configuration Manager require updating
Some areas of LiveCycle Configuration Manager Help (accessible by pressing F1 when viewing any screen in LiveCycle Configuration Manager) require updates, including these:
- On the Initializing the LiveCycle ES Database screen, in the associated Help dialog box, the Port field states that port 7001 can be used for WebLogic. The HTTP service port entered must be the port that the administrator assigned to the WebLogic managed server. This may be port 7001 or it may be a different port number, depending on the port number assigned by the administrator when the managed server was created.
- On the LiveCycle ES Database screen, the associated Help dialog box states that the information required pertains to the LiveCycle 7.x database. This is incorrect; all the information on this screen pertains to the LiveCycle ES database.
- On the Copy Shared Compatibility Layer screen, the associated Help dialog box states that you need to copy the adobe-bmc-client.jar file to the [app_server root]/lib directory. This is incorrect. Instead, you must copy the file to the [appserver_domain]/lib directory. The instructions on the LiveCycle Configuration Manager screen itself are correct.
- On the Application Server Configuration Details screen, the associated Help dialog box states that the WebLogic version is 8.1. This is incorrect; we are using WebLogic version 9.2.
When you are upgrading from LiveCycle 7.x to LiveCycle ES, LiveCycle Configuration Manager Help is not as current as the upgrading PDF documentation. LiveCycle Configuration Manager Help is correct, but more information for some screens may be included in the Upgrading to LiveCycle ES document for your application server and Upgrading to LiveCycle ES for JBoss Using Turnkey.
Additionally, F1 help is not available on the Upgrade MySQL Relational Database screen in LiveCycle Configuration Manager, which may appear when you upgrade from LiveCycle 7.x using the turnkey method. This screen is described in Upgrading to LiveCycle ES for JBoss Using Turnkey.
(AIX) Cannot enter values into text fields in LiveCycle Configuration Manager when using VNC
If you are remotely connected to a computer running AIX and using VNC, when you open LiveCycle Configuration Manager, you cannot enter any values in the text fields. You should use an X-Windows Manager, such as Hummingbird, to connect to the AIX to that computer.
Entering invalid JNDI port requires LiveCycle Configuration Manager to be restarted
If you enter an invalid JNDI port in LiveCycle Configuration Manager when upgrading LiveCycle Policy Server, you will receive the following exception:
javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: 'iiop://localhost:2809'
If you navigate back through the LiveCycle Configuration Manager screens to change the JNDI port, the exception will persist. You must restart LiveCycle Configuration Manager and run the configuration and upgrade process from the beginning to include the correct JNDI port.
(Solaris 9) Cannot edit some fields in LiveCycle Configuration Manager due to limitations of Xclients
Some Xclients, such as Xbrowser, intermittently lead to non-editable fields on the LiveCycle Configuration Manager screens. This may occur when you restart a LiveCycle Configuration Manager session and the fields become non-editable as they have inherited values from the previous session or the configuration xml file.
To make the fields editable for the new session, you must browse away from LiveCycle Configuration Manager session to the system and then return to the LiveCycle Configuration Manager session.
Existing MySQL 4.1 database is not upgraded
The Upgrade MySQL Relational Database screen states that it will upgrade MySQL 4.1 to MySQL 5.0. This is incorrect. We actually install MySQL 5.0 and then migrate the MySQL 4.1 data to the new version.
EARs deployment continues after user exits LiveCycle Configuration Manager prematurely
When LiveCycle Configuration Manager has started the execution of the IBM Websphere's JACL deployment scripts, you cannot stop the deployment even if you exit or cancel LiveCycle Configuration Manager prior to deployment completion. No user action is required because the product EARS will be successfully deployed.
(Linux, BEA JRockit 1.5.0_6) LiveCycle Configuration Manager fails to start when not started locally
When you run the following commands on the local computer, LiveCycle Configuration Manager will not start:
x – query Linux_server
LCM GUI
LCM GUI
To start LiveCycle Configuration Manager in this environment, use BEA JRockit 1.5.0_6 with Telnet or use BEA JRockit 1.5.0_5.
WebSphere deployment fails when using virtual hosts
If you created a new, stand-alone application server from the Deployment Manager and configured it to generate unique ports, and then you create a new virtual host and map it to the ports, the LiveCycle Configuration Manager EARs deployment will fail. It fails because there is no field to enter the virtual host alias.
To deploy using virtual hosts, you must manually deploy WebSphere. (See 'Manually Deploying WebSphere' in Installing and Deploying LiveCycle ES for WebSphere.)
(SQLServer) Trust store initialization fails if database schema does not match database user name
When you create a SQLServer user name (for example, admin1), and you create a schema for the database (for example, admin2) and configure it to be the default schema for the SQL Server account, trust store initialization will fail and a message similar to the one below will appear:
[7/5/07 10:46:35:251 IST] 00000027 TrustStoreBoo E POF is not installed, Trust Store cannot bootstrap unless POF is installed.
Ensure that the SQLServer use rname (for example, admin1”) and database schema name (for example, admin1) match in order for the trust store to initialize successfully.
JBoss Installation Issues
(JBoss Turnkey) Java options example is incorrect
The example provided in the adobe-component-ext.properties file incorrectly states that -D must be entered at the beginning of the java options line:
-Dcom.adobe.idp.dsc.sample.bean_shell.beanShellComponent_1.0.ext=C://dev/dependency.jar
Use the following example instead:
com.adobe.idp.dsc.sample.bean_shell.beanShellComponent_1.0.ext=C://dev/dependency.jar
LiveCycle PDF Generator and Turnkey JBoss
With the Turnkey JBoss installer, if you install LiveCycle PDF Generator and select the Native File Conversion functionality, the JVM option for UTF8 encoding is set incorrectly. You must correct this issue to ensure that LiveCycle PDF Generator functions correctly.
After you complete the LiveCycle PDF Generator turnkey installation, complete these steps:
1. Open the Windows registry Editor.
2. Go to HKEY_LOCAL_MACHINE > SYSTEM > Current Control Set > Services > JBoss for Adobe LiveCycle ES v8.0> Parameters.
3. Select 'JVM Option Number 11’ and right-click Modify, and then change the value data for this key from:
-Dfile.encoding-utf8
to:
-Dfile.encoding=utf8
4. Click OK.
5. Restart “Jboss for Adobe LiveCycle ES v8.0 Service” from services panel.
WebSphere Installation Issues
WebSphere Administrative Console Deployment of WebSphere 6.1, DB2 8.2 on Windows 2003 R2 fails
The deployment EARs process of this implementation will reach approximately 16%, where the afteradobe-livecycle-websphere.ear will fail to deploy. This process should reach 100% to ensure a successful deployment. You must complete the following steps for successful deployment of this implementation:
1. Install WebSphere 6.1.0.0 and update to 6.1.0.5.
2. Install LiveCycle ES and start LiveCycle Configuration Manager.
3. Configure LiveCycle ES and create the EAR files.
4. Close LiveCycle Configuration Manager when EAR creation is complete.
5. Manually deploy EARs using the WebSphere Administrative Console.
6. Install DB2 8.2 and create a database.
7. Start LiveCycle Configuration Manager again.
8. In the Task Selection window, do not select Deploy LiveCycle ES EARs. (For example, 0618sec_continue_LCM.JPG.)
9. Continue the unfinished steps as identified in Installing and Deploying LiveCycle ES for WebSphere.
2. Install LiveCycle ES and start LiveCycle Configuration Manager.
3. Configure LiveCycle ES and create the EAR files.
4. Close LiveCycle Configuration Manager when EAR creation is complete.
5. Manually deploy EARs using the WebSphere Administrative Console.
6. Install DB2 8.2 and create a database.
7. Start LiveCycle Configuration Manager again.
8. In the Task Selection window, do not select Deploy LiveCycle ES EARs. (For example, 0618sec_continue_LCM.JPG.)
9. Continue the unfinished steps as identified in Installing and Deploying LiveCycle ES for WebSphere.
Deployment of Livecycle ES EAR files causes many warnings
A warning similar to the following one may be recorded many times in the System.out log file during deployment of Livecycle ES EAR files:
[24/07/07 14:01:06:423 EDT] 0000002e BackendIdSele W ADMA0091E: The resource com.ibm.ejs.models.base.bindings.ejbbnd.impl.MessageDrivenBeanBindingImpl@37da37da (jndiName: null, ejbName: null) (listenerInputPortName: AdobeMDBPATListener, activationSpecJndiName: <unset>, activationSpecAuthAlias: <unset>, destinationJndiName: <unset>) that is defined in URI META-INF/ibm-ejb-jar-bnd.xmi for module adobe-wkf.jar is not valid. The resource has a cross reference org.eclipse.jst.j2ee.ejb.internal.impl.MessageDrivenImpl(null) that cannot be resolved.
WebLogic Installation Issues
Database user name restrictions for Oracle databases
(WebLogic, all platforms) Output service fails to deploy if LiveCycle Forms is not also being deployed
If you are deploying the Output service along with LC Forms ES,it will deploy correctly. However, if you deploy it alone or with another service (excluding Forms), you will receive the following error at the deploy stage when the adobe-output-dsc.jar is being deployed.
Failed to deploy component …/working/deployLC/deploy/adobe-output-dsc.jar.
Please use the following workaround to complete your deployment:
1. After the installation is complete, do not run LiveCycle Configuration Manager.
2. Go to the <installDir>AdobeLiveCycle8deploy directory.
3. Copy the adobe-output-weblogic.ear file to a <temp-location>. In addition, you should keep a backup of this file.
4. Run the following commands:
2. Go to the <installDir>AdobeLiveCycle8deploy directory.
3. Copy the adobe-output-weblogic.ear file to a <temp-location>. In addition, you should keep a backup of this file.
4. Run the following commands:
Windows:
cd <temp-location>
jar xf adobe-output-weblogic.ear adobe-forms-cache-utils.jar
mkdir APP-INF
cd APP-INF
mkdir lib
cd .
move adobe-forms-cache-utils.jar APP-INFlib
jar uf adobe-output-weblogic.ear APP-INFlibadobe-forms-cache-utils.jar
cd <temp-location>
jar xf adobe-output-weblogic.ear adobe-forms-cache-utils.jar
mkdir APP-INF
cd APP-INF
mkdir lib
cd .
move adobe-forms-cache-utils.jar APP-INFlib
jar uf adobe-output-weblogic.ear APP-INFlibadobe-forms-cache-utils.jar
UNIX:
cd <temp-location>
jar xf adobe-output-weblogic.ear adobe-forms-cache-utils.jar
mkdir APP-INF
cd APP-INF
mkdir lib
cd .
mv adobe-forms-cache-utils.jar ./APP-INF/lib/
jar uf adobe-output-weblogic.ear ./APP-INF/lib/adobe-forms-cache-utils.jar
cd <temp-location>
jar xf adobe-output-weblogic.ear adobe-forms-cache-utils.jar
mkdir APP-INF
cd APP-INF
mkdir lib
cd .
mv adobe-forms-cache-utils.jar ./APP-INF/lib/
jar uf adobe-output-weblogic.ear ./APP-INF/lib/adobe-forms-cache-utils.jar
5. Copy back the new adobe-output-weblogic.ear file to <installDir>AdobeLiveCycle8deploy. If you are prompted to overwrite the existing file, click Yes.
6. Run LiveCycle Configuration Manager by executing this file:
Windows:
<installDir>AdobeLiveCycle8configurationManagerbinConfigurationManager.bat
<installDir>AdobeLiveCycle8configurationManagerbinConfigurationManager.bat
UNIX:
<installDir>/Adobe/LiveCycle8/configurationManager/bin/ConfigurationManager.sh
<installDir>/Adobe/LiveCycle8/configurationManager/bin/ConfigurationManager.sh
Upgrade Issues
If you are upgrading, you should also refer to the Installation Issues section. The installation issues also apply to the upgrading process.
Important Information: LiveCycle Workflow 7.x to LiveCycle ES upgrade
Before attempting to upgrade your LiveCycle Workflow 7.x environment to LiveCycle ES, you need to contact Adobe Enterprise Solutions Customer Service for assistance. Several issues that exist in LiveCycle ES version 8.0.1 prevent upgrading from LiveCycle Workfow 7.x from being successful. The fixes that you obtain from Adobe Enterprise Solutions Customer Service provide solutions to the following issues (as of July 13, 2007).
Workspace ES tasks are saved as drafts upon submitting
In LiveCycle ES environments that were upgraded from LiveCycle 7.x environments, some Workspace ES tasks are always saved as drafts when they are submitted, and the process instance is unable to progress. This behavior occurs under the following conditions:
- The process instance to which the task belongs was created in the LiveCycle 7.x environment and upgraded to the LiveCycle ES environment.
- The User action that generates the task has the Include Route Names In Form Data option and the User Has To Select A Routename To Complete This Task option selected.
The behavior does not occur for new process instances that are created after the upgrade to LiveCycle ES is performed.
Form Server Render Form QPAC throws exceptions
In LiveCycle ES environments that were upgraded from LiveCycle 7.x environments, processes that include the Form Server Render Form QPAC throw exceptions when they are exectuted.
External files required for LiveCycle Workbench ES when upgrading from LiveCycle Workflow 7.x for WebSphere
If you are upgrading LiveCycle Workflow 7.x to LiveCycle Process Management ES for use with WebSphere and are installing Workbench ES to work with the upgraded system, you must obtain and install several IBM-provided files from Adobe before you can run LiveCycle Process Management ES with Workbench ES on WebSphere. These files enable compatibility between Workbench ES and WebSphere.
For information about obtaining and installing the files, refer to the technical article “Obtaining Files Required for Upgrading LiveCycle Workflow 7.x for WebSphere with Workbench ES”. The article will be available from the LiveCycle Knowledge Center at the following URL: www.adobe.com/go/kb402384
Additional fixes that are not listed here may also be provided. For information about how to obtain the fixes, contact Adobe Customer Support.
Installation and Configuration
Memory must be increased in LiveCycle Configuration Manager start-up file before beginning upgrade on Windows
Before starting LiveCycle Configuration Manager to run an upgrade on Windows, you must modify the memory setting in the Configuration Manager start-up file. Otherwise, an error occurs during component deployment, and the upgrade fails.
To modify the memory setting:
- After installing LiveCycle ES, navigate to the [LiveCycleES root]/configurationManager/bin directory and open the ConfigurationManager.bat file in a text editor.
- Find the line set JAVA_OPTS=-Xms128m -Xmx512m and change 512 to 784 so that the line reads:
set JAVA_OPTS=-Xms128m -Xmx784m - Save and close the ConfigurationManager.bat file.
- Double-click the ConfigurationManager.bat file to start LiveCycle Configuration Manager to begin the upgrade
Cannot deploy LiveCycle ES EAR files on Solaris and WebLogic
In the LiveCycle Configuration Manager guided upgrade for a Solaris and WebLogic application server combination, the LiveCycle ES EAR files cannot be deployed. The current workaround is to manually restart the admin and managed server after the database configuration steps, but before the deployment steps.
LiveCycle Configuration Manager
Entering invalid JNDI port requires LiveCycle Configuration Manager to be restarted when upgrading LiveCycle Policy Server 7.x
If you enter an invalid JNDI port in LiveCycle Configuration Manager when upgrading LiveCycle Policy Server, you will receive the following exception:
javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: 'iiop://localhost:2809'
If you navigate back through the Configuration Manager screens to change the JNDI port, the exception will persist. You must restart Configuration Manager and run the configuration and upgrade process from the beginning to include the correct JNDI port.
Existing MySQL 4.1 database is not upgraded
In LiveCycle Configuration Manager, the Upgrade MySQL Relational Database screen states that it will upgrade MySQL 4.1 to MySQL 5.0. This is incorrect. LiveCycle Configuration Manager installs MySQL 5.0 and then migrates the MySQL 4.1 data to the new version.
Support of multiple credentials in a PKCS #12 PDX file
When upgrading from LiveCycle 7.x to LiveCycle ES, a PKCS #12 PFX file containing multiple credentials will not automatically be imported; you must manually import the file.
Form rendering issues
PDF version of forms created for LiveCycle Forms 7.x changes when rendered using LiveCycle Forms ES
An interactive form created using LiveCycle Designer 8.0 and rendered using LiveCycle Forms 7.2.2 has PDF version 1.6. After upgrading to LiveCycle Forms ES, the same form is rendered as PDF version 1.7.
PDF default is now tagged for PDFForm renditions
In LiveCycle 7.x releases, the PDF created by default for PDFForm renditions was non-tagged. In LiveCycle ES, tagged PDFs are now created by default.
Developer issues
Silent failure occurs when target encryption and decryption are attempted when upgrading to LiveCycle ES
If you selected the upgrade option when you installed LiveCycle ES, the usage of the following LiveCycle 7.x Reader Extensions and Document Security APIs fail silently instead of notifying the programmer that target encryption and decryption are not supported in LiveCycle ES:
PDFFactory.openPDFWithCredentials()
PDFDocument.encryptForRecipients()
PDFDocument.encryptForRecipientsEx()
PDFDocument.encryptForRecipients()
PDFDocument.encryptForRecipientsEx()
Searching for users with a 7.x canonical name does not work
The LiveCycle Rights Management ES 8.x database uses an identifier value as a canonical name. If you are using the PrincipalSearchFilter.setCanonicalName method, which is part of the Rights Management 7.x Java SDK (formally named LiveCycle Policy Server) to search for principals by canonical name, you cannot use the 7.x syntax which is cn=abc.
LiveCycle Workbench ES
Problems installing or patching service components (WebSphere environments)
Errors occur when installing or patching service components using the Components view in LiveCycle Workbench ES when the following conditions exist:
- You have enabled EJB connections in the server configuration that you are using to log in to Workbench ES. EJB connections are used for supporting LiveCycle 7.x QPACs in LiveCycle ES environments.
- The LiveCycle ES server is deployed to a WebSphere Application Server.
To successfully install or patch service components under these conditions, you can either modify the workbench.ini file or use an instance of Workbench ES that was not installed with support for upgrading LiveCycle 7.x processes.
Note: If you decide to use an instance of Workbench ES that was not installed with support for upgrading LiveCycle 7.x processes, you do not need to modify the workbench.ini file.
To modify the workbench.ini file:
- Open [install location]AdobeLiveCycle ESWorkbench ESWorkbenchworkbench.ini in a text editor.
- Add the following text in a new line at the bottom of the document:
- Save workbench.ini
-Dcom.adobe.process.unsupported.componentinstall.usingbytes=true
Upgrading exposes a sensitive file in the Resources view
After upgrading your LiveCycle 7.x environment, which includes an instance of LiveCycle Form Manager 7.x, to LiveCycle ES using LiveCycle Configuration Manager, a file named categories.xml in the FormManager folder appears in the Resources view of LiveCycle Workbench ES. The categories.xml file contains information about the form categories that were persisted from the LiveCycle Form Manager 7.x installation.
Users who are assigned the following roles can see the file:
- Super Administrator
- Process Administrator
- Resource Administrator
Because the categories.xml file reveals information about form categories, you should limit the ability to see this file to users who are assigned the Super Administrator role. To prevent Process Administrator and Resource Administrator users from seeing the file, add access permissions to the file using the Resources view after the upgrade is performed. For more information, see the 'Adding access permissions' topic in LiveCycle Workbench ES Help.
Shared tasks are not shared after upgrading (move to upgrading)
After migrating LiveCycle 7.x environments to LiveCycle ES, tasks that were located in shared worklists can no longer be accessed by users who have access to the worklists.
LiveCycle Business Activity Monitoring ES
(Solaris, WebLogic, Oracle) Data is not displayed in Historical Process Volume and Historical Process Timing dashboards
When you start LiveCycle Business Activity Monitoring ES for the first time after upgrading from LiveCycle Business Activity Monitor 7.x, data appears only in the Historical Top Activities and Historical Activity Timing dashboards. Complete the following steps to ensure data appears in all four dashboards:
- Using the Oracle account, log in to the server where the LiveCycle database is stored.
- Delete all rows in tb_bam_calendar by using the following database command:
delete from tb_bam_calendar - From BAM Workbench, navigate to Workbench > Application Workbench > Events.
- Stop all events except for system events that are prefixed with 'VC' by clicking the event Status arrow and then selecting Disable Dependencies. Repeat this step for each event.
- Start all events except for system events that are prefixed with 'VC':
- Select ActivityInstanceStartedEvents Status arrow and click Enable Only This Object.
- Select ActivityInstanceCompletedEvents Status arrow and click Enable All.
- Select ProcessInstanceStartedEvents Status arrow and click Enable Only This Object.
- Select ProcessInstanceCompletedEvents Status arrow and click Enable All.
- Select QueueEvents Status arrow and click Enable All.
- Select TaskCompletedEvents Status arrow and click Enable All.
- Select ReassignedEvents Status arrow and click Enable All.
- Select TaskSpentTimeOnQueueEvents Status arrow and click Enable All.
- Wait 5 to 10 minutes for tb_bam_calendar to fully populate. Ensure that tb_bam_calendar is fully populated by running the following command against the LiveCycle database:
select count(*) from tb_bam_calendar
When the constant result is determined, continue with the next step. - Refresh the BAM Dashboards to verify the data is correct.
Upgrading Policy Server 7.x issues
Offline access of protected documents after upgrade from LiveCycle 7.x
When you upgrade LiveCycle Policy Server 7.x to Rights Management ES, you may not be able to access offline documents that are secured with LiveCycle Rights Management ES if the character encoding methods in Rights Management ES are different from those used in LiveCycle Policy Server 7.x.
To ensure that you can access policy-protected documents properly offline, you must configure the encoding method in LiveCycle ES to match the encoding method used in LiveCycle 7.x.
If you determine that the encoding method in LiveCycle Policy Server 7.x and LiveCycle Rights Management ES are not the same, you can modify the encoding method in the config.xml file for Rights Management ES after completing the upgrade to LiveCycle ES. When you perform a key rollover with the updated config.xml file, users can access offline documents properly.
To determine the encoding method used in LiveCycle 7.x:
- Obtain the LiveCycle 7.x patch for determining the encoding method. Contact Adobe Customer Support.
- Apply the patch to your LiveCycle Policy Server installation by following the instructions included with the patch.
- Log in to LiveCycle Policy Server as any valid user.
- Search the application log file for the line containing the string DoCharacterEncodingEvaluation. For example:
2007-07-15 23:18:41,098 INFO [com.adobe.edc.server.spi.storage.StoreProviderFactory] Thread: http-0.0.0.0-8080-Processor24, hashcode: 4455272 -----DoCharacterEncodingEvaluation---
The line immediately following this contains either the KeyDecodeCharacter parameter that need to be set in LiveCycle ES, or it indicates that no change is needed in the LiveCycle Rights Management configuration.
To modify the encoding method in the config.xml file:
- Log in to the LiveCycle Administration Console and click Services > LiveCycle Rights Management ES > Configuration > Manual Configuration.
- Export the config.xml file and open it in a text editor.
- Under the KeyManagement node, add the following element and value:
<entry key='KeyDecodeCharacterSet' value='[PS7value]'/> (Where [PS7value] is the encoding method used for Policy Server 7.x.) - Save the config.xml file and import it using the Manual Configuration page in LiveCycle Administration Console.
- In LiveCycle Administration Console click Services > Right Managemenet ES > Configuration > Key Management.
- Click Roll Over Keys Now.
Administration Issues
Archive Administration
Endpoints with the same name are not recommended
If you create multiple endpoints with the same name, an error does not appear. However, it is recommended that you do not do this because it can create confusion.
Errors when importing LCA files that include files with double-byte characters
Errors can occur when you import LCA files using Archive Administration under the following circumstances when the LCA file was created:
- LiveCycle ES was deployed to a WebLogic Server.
- The process that the LCA file contains uses resources that are named using double-byte characters, and/or the process diagram of the process uses double-byte characters, for example in operation names and annotations.
If you are using LiveCycle Workbench ES with a WebLogic Server, avoid using double-byte characters in the names of resources and process diagram elements.
The errors can occur when you import the LCA file regardless of the type of application server that hosts LiveCycle ES.
Database Management
(JBoss, MySQL) Extended periods of server inactivity causes exceptions
When using the JBoss Applications Server configured with MySQL (the JBoss turnkey), extended periods of server inactivity will cause the following exceptions to be reported in the server log:
code: java.net.SocketException MESSAGE: Software caused connection abort: socket write error.
The reported exception is raised by background processing during internal database management and its presence is expected. This exception does not affect the LiveCycle ES server's processing and may be safely ignored.
Domain Management - MySQL and DB2 Enterprise Domains cannot be deleted when domain ID is too long
When you create an Enterprise Domain ID, ensure that it is less than 17 characters for MySQL and less than 34 characters for DB2. Otherwise, a message similar to the this one is displayed when you attempt to delete the Enterprise Domain:
The following domains could not be deleted
Limitation on document usage in processes for MySQL databases
The MySQL database limits the amount of data that can be stored in a table row. Processes that involve multiple instances of documents can require more storage space than the MySQL row size limitation. Because LiveCycle ES stores data for a process instance in a single table row, processes that involve large amounts of data can exceed the MySQL limitation on row size, causing errors to occur.
If you are running a process that involves many instances of documents and errors occurring in the database, you can redesign the process so that the operations that handle documents execute in several subprocesses. For example, you can redesign your process so that its operations are executed in two processes. The first process includes the first half of the operations of the original process, and the second process includes the last half of the operations. The first process needs to include the invoke operation of the second process so that the second process runs as a subprocess.
Email Provider
Limitations to Email endpoints with multiple file attachments
The following limitations exist when using email endpoints to invoke services:
- If the service request message includes multiple file attachments, you cannot use the %F and %E parameters in values for the Output Parameter Mappings property of the endpoint.
- If the service response returns multiple file attachments, you cannot specify the same file name for more than one attachment.
If you attempt to configure email endpoints as described above, the invoked service creates the names for the returned files, and the names are not predictable.
Batch size for email endpoint must be greater than 1
If you set the batch size for an email endpoint to a value equal to or less than 1, only one email message is read at each poll instead of all available messages. The current workaround is to set the batch size to a value greater than 1.
LiveCycle Business Acitivity Monitoring ES
Problems with Internet Explorer and LiveCycle Business Activity Monitoring ES
When you use BAM Workbench and BAM Dashboard in Internet Explorer 6.0 and you have Security Update for Windows XP (KB918899) installed, using drop-down menus causes the web browser to close.
To use BAM Workbench and BAM Dashboard in Internet Explorer 6.0, you need to uninstall Security Update for Windows XP (KB918899) by using Windows Add or Remove Programs.
Drillback limitation
- Cannot have spaces or special characters in table and column names in views that are used for drillback with view persistence.
- Column names for views should be in all caps as a best practice when using drillback; otherwise, drillback to detail might not work.
- A drillback with a filter on a dimension column of type TIMESTAMP does not work if the dimension context is stored in an Oracle database.
- If the user who creates the cube has filtered access to the fact view, the cube is not enabled for drillback.
- Drillback to detail is only supported on cubes that are build on a stateless view.
Folders cannot be deleted
Folders that a user creates in the dashboard navigation tree cannot be deleted and can be seen by all other users. Folders that do not contain any objects are not displayed in the tree. Future releases will allow a user to delete folders.
Default settings for recovery logger are disabled
The recover settings for the recovery logger are disabled by default. You must specify the recovery log directory to enable the recovery logger. See the Installation and Configuration documentation for details on how to set the recovery logger.
Pre-existing watchpoints are private
Watchpoints created to prior to version 8 are private and the public watchpoint checkbox is disabled in the Watchpoint Manager. To change the availability of the watchpoint, the watchpoint must be deleted and recreated as a public watchpoint.
Must use AS clause for alias name in a JDBC query
In a SELECT statement, you cannot omit the AS clause for the alias name in a JDBC query. For example, SELECT x+y AS z will work as expected, but SELECT x+y z causes an error.
Issues with Oracle as context database
If a query has descriptor as one of the columns, the query will fail because descriptor is a Oracle keyword. To solve this problem, do the following:
- Import the adobeimport_oracle.jar.
- Go to Business Activity Monitoring Workbench.
- Go to Events and disable the Adobe_Event.
- Edit Adobe_Event.
- In the Configure Event - JDBC Source window, update the JDBC query by putting descriptor in double quotes. For example:
- Click Resubmit Query.
- Under the Polling tab make sure that update_time is selected for “Incrementing Field.”
- Click Save Event.
- Enable the Event. Enable all dependencies.
select uuid,major_version, minor_version, “descriptor” ,state, service_uuid,component_oid
update_time, create_time from tb_sc_service_configuration
Note: When you enable the Adobe EVent, errors will occur on the console the very first time. Ignore the errors.
LDAP Referral System Setting is undocumented
A drop-down menu for LDAP Referral has been added to LDAP Synchronization configuration under the System Settings of the Workbench Administration Console. This drop-down menu lets you Indicate to service providers how to handle referrals. Set the referral to one of the following:
- Follow — Referrals are followed.
- Ignore — Referal entries are ignored and returned as plain entries. (Default)
- Throw — Each referral encountered results in an exception.
Multiple Role Base DNs for LDAP Role Mapping is undocumented
The LDAP Role Mapping configuration window under System Settings of the Workbench Administration Console now allows you to enter more than one Role Base DN for LDAP Syncronization.
Caution: Do not enter a blank line between rows.
BAM does not show the data after restarting the application server
To prevent data from not being shown in the dashboard after restarting the application server, you must do the following:
Livecycle Designer 8.0 Save Fillable Form
- Make sure both checkpoints and the recovery log are enabled before starting the server. (Use the properties text file.) Checkpointing is used to maintain a reasonable size for the recovery log. That is, the recovery log contains the data from the last checkpoint to the current time. If checkpointing is not enabled, all events in the recover log will replayed when the server is restarted, flooding the system and causing a failure condition.
- Before restarting the server, make sure you click “Run Checkpoint Now” button. Checkpoints occur on a schedule (for example, every 30 minutes). If the server is restarted between scheduled checkpoints, events will replayed every event from the last checkpoint to the point where the server was restarted. By clicking the “Run Checkpoint Now” button, only the events from the point where the button was clicked will be replayed.
- Disable then enable all data events (except AdobeEvent) if dashboard objects do not display any data. If you have an existing instance of LC8 with a lot of orchestration, then install BAM and restart the server, you might not see data from any of the existing orchestration but still see new views and dashboard objects created that do not show any data. The reason is probably because the polling interval for the data events and the metadata event (that is, the event which creates the views and dashboard object) is 15 seconds. This means that the polling for the data event could have happened before the metadata event, which causes the “initial value” of the data event to change to current time even though the views and dashboards are not created. That is, the dashboard objects are 15 seconds behind the events and do not see the data. Disabling and enabling all data events makes it possible for the dashboard objects to “catch up.”
Historic Process Volume chart shows only one line
If the Process Volume chart displays only one line, this is probably because the number of process started is same as the number of process completed. In this case, the second line overlaps the first, and you only see a single line. To se the complete details of all the process started and completed, navigate to the detail view and to see the table, which contains the data for both started and completed processes.
LiveCycle ES Connector for EMC Documentum
Validation of EMC Documentum user credentials
When you configure the Connector for EMC Documentum service using LiveCycle Administration Console, you must provide a valid user name and password with super-administrator privileges on the following LiveCycle Administration Console page:
- Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings
If you enter incorrect information, you will get the following results, depending on whether the service is currently running:
- If the Connector for EMC Documentum Repository Provider service is stopped, when you save the service configuration information, no error appears. However, the next time you start either the EMC Documentum Repository Provider service or the EMC Documentum Content Repository Connector service, an exception will be thrown and the service will not start.
- If the Connector for EMC Documentum Repository Provider service is started, when you save the service configuration information the service attempts to validate the credential information immediately. In this case, an error occurs and the configuration information is not saved.
Removing LiveCycle ES Archives (LCAs) with assets stored in EMC Documentum Content Server
To remove LiveCycle ES archives (LCAs) that have assets such as forms or images stored in either an EMC Documentum repository, you must perform the following actions:
- Delete the LiveCycle archives using Archive Administration within LiveCycle Administration Console.
- Delete the asset files from the ECM repository using LiveCycle Workbench ES.
For more information about accessing ECM repository content using LiveCycle Workbench ES, see either the 'Configuring the Connector for EMC Documentum service' section in the Installing and Configuring LiveCyle ES document for your application server.
LiveCycle ES Connector for IBM FileNet
Validation of the IBM FileNet user credentials
When you configure the Connector for IBM FileNet service using LiveCycle Administration Console, you must provide a valid user name and password on the following LiveCycle Administration Console page:
- Services > LiveCycle ES Connector for IBM FileNet
If you enter incorrect information, you will get the following results, depending on whether the service is currently running:
- If the Connector for IBM FileNet Repository Provider service is stopped, when you save the service configuration information, no error appears. However, the next time you start the service, an exception will be thrown and the service will not start.
- If the Connector for IBM FileNet Repository Provider service is started, when you save the service configuration information, the service attempts to validate the credential information immediately. In this case, an error occurs and the configuration information is not saved.
Removing LiveCycle ES Archives (LCAs) with assets stored in IBM FileNet Content Manager
https://coldever415.weebly.com/blog/chrome-dark-mode-on-macos-download-bar. To remove LiveCycle ES archives (LCAs) that have assets such as forms or images stored in an IBM FileNet object store, you must perform the following actions:
- Delete the LiveCycle archives using Archive Administration within LiveCycle Administration Console.
- Delete the asset files from the ECM repository using LiveCycle Workbench ES.
For more information about accessing ECM repository content using LiveCycle Workbench ES, see the 'Configuring the Connector for IBM FileNet service' section in the Installing and Configuring LiveCyle ES document for your application server.
Livecycle Output ES
Need to restart service after changing cache settings
When you change the cache settings for LiveCycle Forms ES or LiveCycle Ouput ES in LiveCycle Administration Console, a message indicating that you need to restart the service does not appear. However, you must restart the service before the changes will take effect.
To restart the service:
- In LiveCycle Administration Console, select Services > Archive Administration > Service Management.
- Select the service and click Stop.
- When the State for the service is 'Stopped', click Start.
Running a service on Windows
If you deploy the Output service with LiveCycle ES that was installed using the Turnkey JBoss installation on Windows, the JBoss service is installed to run in the context of the Local System account. Services that run in this context do not have access to network resources such as printers because they are not authenticated on the network. This means that network resources are not visible to the service. For example, when using the Output IVS installation verification sample to send a document to a network printer, you would get an error message such as this one:
Printer serverqueue not found
To solve this problem, enable JBoss to run in the context of a valid user. To perform this task, change the properties of the JBoss service by clicking the Log On tab and selecting This account. You must supply a valid user name and password. The service must be restarted for this change to take effect.
Restarting WebSphere after adding a new printer
If you are running the Output service on LiveCycle ES that is deployed on Windows with an IBM WebSphere Application Server, you must restart the application server after adding a new printer. If the application server is not restarted, the print queue will not be effective.
LiveCycle PDF Generator ES
Adobe PDF settings in LiveCycle Administration Console do not apply to image-to-PDF and OpenOffice-to-PDF conversions
Although Adobe PDF settings are displayed in LiveCycle Administration Console on the Create PDF page, these settings are not used during image-to-PDF and OpenOffice-to-PDF conversions.
' failed="" to="" delete="" a="" directory'="" message="" may="" be="" displayed="" in="" the="" server="" log="" when="" running="" conversions="" to="" pdf="">The following warning may be displayed in the Server log on running conversions to PDF format:WARN [Document] DOCS007: Failed to delete a directory 'C:DOCUME~1ADMINI~1LOCALS~1TempAdobeDocumentStoragelocalremoveOn2006Y08M31D18h16m15s.1157028375000' after 60 attempts. The file(s) under this directory could still be locked. If this message is consistent, consider restarting the server.'Conversion exceptions in the server log; increase conversion timeout
The following conversion exception may appear in the server log when performing conversions using the Generate PDF service: “ConversionException: ALC-PDG-011-029-c0000005”. Because the default conversion timeout for the Generate PDF service is 270 seconds, it is recommended that you increase the default conversion timeout to 450 seconds. For more information, see the Installing and Deploying LiveCycle ES guide for your application server.Only the current layout of AutoCAD files are converted to PDF
LiveCycle PDF Generator converts only the default layer of AutoCAD files to PDF instead of all of the layers within the file. The current workaround is to perform the following task:- In LiveCycle Administration Console, click Services > LiveCycle PDF Generator ES > Configuration Files > Export Configuration.
- Select Download Entire Configuration and click Download.
- In a text editor, open the downloaded file and, under the AutoCAD tag, within the PDFMaker tag, add this text: convertAllPages='true'.
- In LiveCycle Administration Console, click Services > LiveCycle PDF Generator ES > Configuration Files > Import Configuration.
- Select Import An Existing Configuration File and specify the updated file.
- Click Import.
Any AutoCAD files converted using the modified configuration file will have all of the layers converted.LiveCycle Process Management ES
Cannot specify {$action_instance.create_time$} in email settings
If you specify {$action_instance.create_time$} in the Text field on the Stalled Branch tab of the Email Settings page for LiveCycle Process Management ES, the value is not substituted with the creation date (for example, 2007-06-30 10:00:00). The literal value {$action_instance.create_time$} is returned instead. Administrator must configure email settings for Process Management ES
If a user other than the administrator tries to configure the email settings for the Process Management ES service, an error occurs. Search problems using LiveCycle Process Management ES when user names begin with the # character
Performing task searches using LiveCycle Administration Console returns no results for user names that begin with the number sign (#). If possible, avoid creating user names that begin with the number sign.Task searches are performed using the Task Search page that LiveCycle Process Management ES provides in LiveCycle Administration Console.Cannot filter search by unassigned or completed tasks for LiveCycle Process Management ES
When performing a task search based on User Name for LiveCycle Process Management ES, if you select the Show Unassigned Tasks checkbox, the search results include all of the assigned and unassigned tasks for the selected user. And, if you select Show Completed Tasks, the search results include both assigned and completed tasks. The crooked man download mac.Email settings for LiveCycle Process Management ES
When using LiveCycle Administration Console, you must log in as the administrator to set the email settings in Home > Services > LiveCycle Process Management ES > Server Settings > Email Settings. You will receive an error if another user attempts to configure this option.LiveCycle Reader Extensions ES
Need to increase timeout values to prevent jobs from failing
When working on a large number of PDF files in LiveCycle Reader Extensions ES, you must ensure that the following timeout values are set accordingly to prevent jobs from timing out and failing: Document Disposal Timeout: This value can be set in LiveCycle Administration Console. Select Settings > Core System Settings > Configurations and specify a value for Default document disposal timeout. User Manager LiveCycle Timeout: This value can be set by editing the config.xml file. In LiveCycle Administration Console, select Settings > User Management > Configuration > Importand export configuration files, and then click Export. Open the exported config.xml file and edit the following lines: <entry key='assertionValidityInMinutes' value='600'/>
<entry key='SessionTimeout' value='600'/>Save and then import the config.xml file back into LiveCycle Administration Console. Application Server Session Timeout: This value can be set on the application server. For more information, see the documentation provided with your application server.LiveCycle Rights Management ES
Cannot reinvite a user after deleting the user from Local Users
If a user has been deleted from the Local Users in LiveCycle Rights Management ES, you cannot reinvite the user again in LiveCycle Administration Console.LiveCycle Workspace ES
Error occurs whens email settings are not configured
If the email settings are not configured or an email endpoint is not set in LiveCycle Administration Console, when a user in LiveCycle Workspace ES completes a task and submits the associated form, a run-time exception error appears. You must ensure that the email settings are configured to avoid this error.Incorrect error message appears when importing existing search template
In the LiveCycle Workspace ES administration screens, if you try to import a search template and a template with the same name already exists, the following error message appears instead of an exception error:“LiveCycle Workspace Administration Exception.Unable to complete request. See error log for more detail.”Queue sharing form is not automatically routed
When users request access to another user’s queue, that user does not automatically receive the task in their To Do list in order to either approve or deny the request. To ensure that the user receives the task, you must select the Invoke Permissions for All Principles to the Queue Sharing Queue option for the DirectoryManagerService.Trust Store Management
Updating existing credentials
To update a credential using Trust Store Management, you must first remove the existing credential and then add the new credential using the same alias. Failure on import credential
When the error message “Failed to import credential due to either incorrect file format, or incorrect password” appears, ensure that you verify the password is valid.Updating an HSM credential
To update an HSM credential, you must delete the existing credential and then add the new HSM credential.User Management
Errors while creating multiple users and groups
The ability to create multiple local users and groups while an LDAP directory synchronization is in progress is not supported. Attempting this process may result in errors.User Management support of UTF-8 on MySQL
You can create domain or user names that contain extended characters; however, when a comparison is made between two strings such as abcde and âbcdè, they are considered the same. For example, when syncing, if a new user has been added to the database, a comparison is made to check if a user with the same name already exists in the database. If the user abcde exists in the database, and new user âbcdè is added, the comparison is unable to distinguish between the two names. It is assumed that the user has already been added to the database and the new user is ignored and not added.User names greater than 255 characters are not supported
If you are using a SQL Server database server and try to create a user with a name greater than 255 characters, a ClassNotFoundException is thrown instead of an IDP Exception with the message 'String exceeds max length 255.' Unique identifier
A non-dn attribute should be used as the unique identifier. This value is dependent on the directory server. The value of the unique identifier is objectSID for Active Directory and nsuniqueID for SunOne directory server. For Novell eDirectory, the value is guid and for IBM Tivoli, the value is ibm-entryuuid.Unique user IDs required
For LDAP users, ensure that the user ID is unique. Do not use a user ID that was assigned to a deleted user. When a user ID that was assigned to a deleted user is used, the new user will assume the roles and permissions of the deleted user.Distinguishing between principals sharing a user identifier and canonical name
When two principals in a particular domain share a user identifier and canonical name, if one principal has been accessed using its user identifier and a search was then executed for the other principal using its canonical name, the system cannot distinguish between the two and the first principal will be returned. However, if the first principal was not accessed using its user identifier, the search for the second principal, using its canonical name, will yield the correct result. Attempting to delete DefaultDom domain in User Management gives contradictory resultsYou cannot delete the DefaultDom domain in the User Management’s Domain Management page in LiveCycle Administration Console. If you attempt to do this, you are warned that the Domain cannot be deleted. However, when you search for DefaultDom using Users and Groups > Find in User Management, it cannot be found.If this occurs, you can return the DefaultDom to the system:On Domain Management page open the DefaultDom domain for editing, and click OK. This causes the DefaultDom domain to appear in the system and you can search for users in this domain.Domains: limitations on multibyte characters and number of domains
The length of a domain identifier can be up to 50 characters. This limit is applicable only if the domain identifier contains ASCII characters. If the domain identifier contains multibyte characters, this limit will be reduced. For example, if you create a domain whose identifier contains 3-byte characters, the limit would be 16 characters. In addition, domains containing 4-byte characters cannot be created. Also, there is a limit to the number of both enterprise domains and local domains that may be created within LiveCycle ES, and that limit is dependent on the length of each of the domain names.Deleting domains containing extended ASCII character
When creating domains with User Management, if domain names contain extended ASCII characters, attempting to delete those domains may cause an exception to be thrown. It is therefore recommended that you do not use extended ASCII characters in domain names.Single sign-on fails when both 'Domain mapping' and 'HTTP header for domain' are not specified
On the portal single sign-on screen, both 'Domain mapping' and 'HTTP header for domain' must to be specified in order for authentication using HTTP header (Netegrity) to work.Incorrect error message appears when user account is locked
If you try to log in to your account multiple times by using the incorrect credentials, the following error message appears instead of an error indicating that the account is locked as a result of too many unsuccessful login attempts: “None of the Auth Provider could authenticate the user. Authentication Failed'Watched Folder
Watched Folder may process input files before they are completely copied to the folder
File locking is not mandatory on Unix as it is on Windows. For this reason, when a file is being copied to a watched folder, Watched Folder may move the file to stage without waiting for the file copy to complete. This behavior causes only a portion of the input file to be processed. There are currently two workarounds:Workaround 1
- Specify a pattern for Exclude File Pattern, such as temp*.ps.
- Copy files that begin with temp (for example, temp1.ps) to the watched folder.
- After the file has been completely copied to the watched folder, rename the file to correspond with the pattern specified for Include File Pattern. Watched Folder then moves the completed file to stage.
Workaround 2
If you know the maximum length of time it will take to copy your files to a watched folder, then specify the time in seconds for Wait Time. Watched Folder then waits the specified length of time before moving the file to stage. This is not an issue for files on Windows, because Windows locks a file when one thread is writing. However, this is an issues for folders on Windows. For folders, you must follow the steps in Workaround 1. Staging directory not cleaned out when Preserve Folder Name set to null
If the Preserve Folder Name endpoint attribute for Watched Folder is set to a null directory path, the staging directory is not cleaned out as it should be. The directory still contains the processed file and temporary folder.Need to prevent a watched folder from including Windows Thumbs.db file
If you have a watched folder on Windows that is processing any image files, you need to specify values for the Include File Pattern or Exclude File Pattern option to prevent the Windows auto-generated Thumbs.db file from being polled by the watched folder.Web Browser
(Windows, Japanese, IE) Some LiveCycle Administration Console links fail when server name contains underscore
While running LiveCycle Administration Console from an IE browser, you may encounter the following errors:Practical Design to Eurocode 2. Design crack width is w k Note: slabs ≤ 200mm depth are OK if As,min is provided. Calculation Crack control. The first model is a modification of the conventional crack spacing model presented in Eurocode 2 and is valid for the case when cracking is caused by an external load. The second model, which is based on a bond-slip relationship and a compatibility requirement, is valid for cracking caused by restraint stresses. Feb 27, 2013 Hello to everybody!!Does anybody have example of calculation crack width in concrete section applied to bending moment and compression? Eurocode 2: Crack width calculation crack width calculations according to eurocode 2 Eurocode 2 (EN1992-1-1) proposes equations for the calculation of crack width, taking into account several parameters, like the concrete and steel strain and reinforcing bar. Crack width calculation euro code 2 examples. Calculations using the Eurocode EN 19921-1:2004, Section 7.3.4 are shown - below as well as a comparison of the SAFE and hand calculated results. A one-way, simply supported slab is modeled in SAFE.- Clicking a link returns you to the login page and not to the expected link
- Clicking a link displays a permission error
Run LiveCycle Administration Console from another browser, such as FireFox, to ensure that no links will fail.Development Issues
ActionScript documentation
Discrepancies between the ASDoc comments found in the reference source and LiveCycle ES ActionScript Reference
LiveCycle ES ActionScript Reference is generated from reference source; however, discrepancies exist between the ASDoc comments that appear in the LiveCycle Workspace ES source in the adobe-workspace-src.zip file and the LiveCycle ES ActionScript Reference available at www.adobe.com/go/learn_lc_fgActionScript. The version on the web is the most recent and correct version. The adobe-workspace-src.zip file is stored in these locations:- On the LiveCycle ES server, if the samples are deployed during configuration, at [server install directory]LiveCycle_ES_SDKmiscProcess_ManagementWorkspace, where [server install directory] represents the location where the LiveCycle ES server was installed.
- On a workstation that has installed Workbench ES at [workbench install directory]LiveCycle ESWorkbench ESLiveCycle_ES_SDKmiscProcess_Management
Workspace, where [workbench install directory] represents the location where LiveCycle Workbench ES was installed.
Assembler service
Reapplying a Header, Footer, Watermark, Background, PageOverlay, or PageUnderlay to a PDF file causes the file to grow in size
For the Assembler service, reapplying a Header, Footer, Watermark, Background, PageOverlay, or PageUnderlay to a PDF file will cause the file to grow in size. This growth occurs even if you set the PDF element’s save attribute to Full, as shown in the example below.The reason the file grows is that the Header, for example, references an optional content group (OCG) in the PDF document. Because different PDF objects may reference the same OCG, it is assumed that the OCG associated with the Header may be needed by other PDF objects. For this reason, reapplying the Header will not result in the associated OCG being removed, but rather in the addition of a new OCG associated with the new Header.For example, the following DDX will cause the file to grow in size each time it is applied to the file:<PDF result='result.pdf' save='Full'>
<PDF source='input.pdf' />
<Header> <Center>
<StyledText>
<p>For review</p>
</StyledText> </Center>
</Header>
</PDF>Exceptions thrown when PDF files contain invalid XMP metadata
If a PDF file contains invalid XMP metadata, the Assembler service will throw an exception when processing that file. The error message will indicate that a “SyncMetadataTask task failed for document.”Such errors may have occurred because of the use of outdated software, such as old versions of Distiller or FrameMaker; therefore, you can attempt to prevent such errors from occurring by regenerating the input PDF document using updated software.Barcoded Forms service
Supported image file extensions for barcoded forms
When decoding image files using a watched folder, the image files must use one of the following file name extensions: .pdf, .PDF, .tif, or .tiff. The decoder is case-sensitive and, therefore, you cannot use any other variation (for example, PDF or TIF).ECM repository
Deleting resources transactions do not roll back
When using the com.adobe.repository.bindings.dsc.client.ResourceRepositoryClient.deleteResources() method with ECM repository (EMC Documentum Content Server and IBM FileNet P8 Content Manager), the transaction will not be rolled back if the deletion fails for one of the specified resources, which means that those files that have been deleted cannot be undeleted.Torrent kodak capture pro software. With KODAK Capture Desktop you’ll receive “out of the box” production and have the immediate ability to capture, edit and output anything from single documents to larger batches in distributed or departmental environments. KODAK Capture Desktop Software is an intuitive and easy-to-use capture software application, specifically designed to make processing and sharing scanned documents simple. • Publisher: EASTMAN KODAK Company • Home page: • Last updated: December 9th, 2011 Kodak capture pro 3.1 torrent in Description.Email Provider
Invoking the Generate PDF service or the Distiller service using email provider
Only one document is converted by the Generate PDF service or the Distiller service when multiple documents are submitted as file attachments in a single email message to an email provider.Encryption service
Unlocking a PDF document using web services
The Encryption service WSDL exposes a web method named unlockPDF that returns a PDF document. However, the PDF document that is returned remains locked. If you attempt to perform another LiveCycle ES operation on the PDF document, you will create an exception.Form Data Integration service
Comments and notes associated with stamps are not imported when XFDF data is imported in an Acrobat form
Comments and notes annotations associated with stamps are not imported when XFDF data is imported into an Acrobat form.Differences in fonts
When merging XFDF data into an Acrobat form that contains CJK fonts, there may be a slight difference in text size rendition.Form Guides
Default form guide layout styles are automatically saved as a SWC file
If a form guide does not include any custom styling applied using the Customize Appearance options in Guide Builder, a default SWC file containing the default form guide styles is automatically saved to the same folder where the form design is saved. You must deploy this SWC file with the form design and any other assets. For example, if you are rendering a form guide as part of a process created in LiveCycle Workbench ES, the SWC file must exist in the same folder as the associated form design within the LiveCycle ES repository. Microsoft Internet Explorer security warning displays when viewing a rendered form guide
When previewing a form guide or viewing a rendered form guide in Internet Explorer, a security warning may be displayed, depending on the security settings a user has set. If the security warning is displayed, users must manually allow the blocked content to display the form guide.To automatically display a form guide:- Start Internet Explorer.
- Click Tools > Internet Options.
- Click the Security tab and click Custom Level.
- Ensure that the Scripting > Active Scripting option is set to Enabled.
Forms service
Fonts may not be displayed properly when rendering forms based on fragments
When rendering forms based on fragments (and where the fragments are located on other computers that are accessible using HTTP), you must specify the DNS name for a computer without WINS configuration. If the computer has WINS configuration, use its WINS name instead of the IP address or DNS name. Otherwise, the fonts located within fragments may not be displayed properly.Customizing the HTML Digital Signature button's UI properties
If you want to customize the look of the HTML Digital Signature button on an HTML form, you must change the following properties in the fscdigsig.css file (within the adobe-forms-ds.ear > adobe-forms-ds.war file):.fsc-ds-ssb: This style sheet is applicable in case of a blank sign field.
.fsc-ds-ssv: This style sheet is applicable in case of a Valid sign field.
.fsc-ds-ssc: This style sheet is applicable in case of a Valid sign field but data has changed.
.fsc-ds-ssi: This style sheet is applicable in case of a invalid sign field.
.fsc-ds-popup-bg: This style sheet property is not being used.
.fsc-ds-popup-btn: This style sheet property is not being used.PDF default is now non-tagged for PDFF renditions
In LiveCycle 7.x releases, the PDF default for PDFF renditions was tagged. Non-tagged PDFs are now created by default to improve performance. Data is not merged properly into dynamic PDF documents
If XML or XDP data (with repeated subform datasets) is merged into a dynamic PDF document when the RenderAtClient run-time option is No, only the first dataset is merged and the subform is not repeated. To merge the entire dataset, set the RenderAtClient run-time option to Yes.Embedded images not showing in HTML renditions
Embedded images are not shown in HTML renditions when they are placed in the 'area' container. The embedded images can be seen when the form is changed such that images are moved from the 'area' container to the 'subform' container.Fields within a document may not properly account for the fact that certain fields should not be modified during a certification workflow
In document certification workflows, it is possible to specify a subset of fields that are allowed to be modified. However, when XFDF, FDF, and XML data is imported, the appearance of the document’s fields may not properly account for the fact that certain fields should not be modified because they were under the control of a signature field lock when the digital signature was applied. Forms rendered as HTML containing tables are not XHTML 1.0 compliant
When rendering HTML forms using the Forms service that contains tables, the form is not XHTML 1.0 compliant. HTML toolbar is not accessible or readable by JAWS
The HTML toolbar that can be rendered with an HTML form cannot be accessed through the keyboard and is not readable by JAWS. Issues with LiveCycle Forms ES output in various browsers
HTML rendition of tables is not correct in Firefox, Safari, and NetScape browsers. The HTML generated by LiveCycle Forms ES does not comply to XHTML 1.0 standards when the form contains a table object. For related information specific to the Firefox browser, see https://bugzilla.mozilla.org/show_bug.cgi?id=63895.Rendering text fields when nested in a table cell
Text fields are not rendered properly in HTMLs when they are nested inside a table cell. The alignment of the text fields is not proper inside a table. Form is not rendered using web services button in FormsIVS when the web server is SSL-enabled
On a Digital Signature setup, when you access a Forms service application deployed on a J2EE application server using a SSL-enabled web server, you cannot render a form using the Use WebServices button from FormsIVS. This situation applies only when the web server is SSL-enabled not the J2EE application server.Manual procedure is required to customize digital signature user interface
You can modify the text and the user interface for the HTML digital signature dialog box. To customize this dialog box, you must follow these steps:- Undeploy the adobe-forms.ds.ear file.
- Using a tool such as WinRAR, open the adobe-forms-ds.ear file, open the adobe-forms-ds.war file, and extract the SignDialog.jsp file.
- Modify the SignDialog.jsp file and replace the modified file back into the adobe-forms-ds.war file, and then add the modified WAR file back into the adobe-forms.ds.ear file.
- Using a tool such as WinRAR, open the adobe-forms-ds.ear file and extract the dsmsg.properties file.
- Modify the dsmsg.properties file and replace the modified file back into the adobe-forms-ds.ear file.
- Redeploy the modified adobe-forms.ds.ear file.
Foundation
Exception thrown when using ComponentRegistry WSDL
When directly consuming the ComponentRegistry WSDL on native SOAP stacks, the modify web method, which is used to modify a component, may throw an exception.Memory loeak using com.adobe.idp.Document object
To prevent a memory leak in WebLogic while using a com.adobe.idp.Document object, you must read the document information in chunks of 2048 bytes or less. For example, the following code reads the document information in chunks of 2048 bytes:// Set up the chunk size to prevent a potential memory leak
int buffSize = 2048; // Determine the total number of bytes to be read
int docLength = (int) inDoc.length();
byte [] byteDoc = new byte[docLength];// Set up the reading position
int pos = 0;// Loop through the document information, 2048 bytes at a time
while (docLength > 0) {// Read the next chunk of information
int toRead = Math.min(buffSize, docLength);
int bytesRead = inDoc.read(pos, byteDoc, pos, toRead); // Handle the exception in case data retrieval failed
if (bytesRead -1) {inDoc.doneReading();
inDoc.dispose();
throw new RuntimeException('Data retrieval failed!'); }// Update the reading position and number of bytes remaining
pos += bytesRead;
docLength -= bytesRead;}// The document information has been successfully read
inDoc.doneReading();
inDoc.dispose();Invoking the getComponents method using web services
You can create Java proxy classes for the Service Registry service using Apache Axis. Normally, these classes let you invoke this service using its exposed web service. However, a java.lang.StackOverflowError is thrown if you invoke the getServiceConfigurations method. Invoking the getServiceConfigurations method using web services
You can create Java proxy classes for the Service Registry service using Apache Axis. Normally, these classes let you invoke this service using its exposed web service. However, a java.lang.StackOverflowError is thrown if you invoke the getServiceConfigurations method. Generate PDF
When retrieving the generated output file through direct consumption of the WSDL, a URL is normally returned instead of binary data
When using binary data for submitting a source file for conversion through direct consumption of the WSDL on native SOAP stacks, the generated output file is normally posted on the server, and a URL of the file is returned to the client in order to minimize the amount of data returned to the client. To retrieve the binary data instead of a URL, see LiveCycle ES SDK Help.LiveCycle Workbench ES
Create Relationship operation throws java.lang.NullPointerException
Create Relationship operations that the Content Repository Connector service (for EMC Documentum) provides throw java.lang.NullPointerException exceptions if an invalid value or no value is specified for the Relationship Type property. The operation is supposed to throw RepositoryException exceptions.At run time, if a java.lang.NullPointerException is thrown when Create Relationship operations are executed in a process instance, ensure that a correct value is specified for the Relationship Type property.Configurations for using JMS service operations in clustered environments (WebSphere)
To use JMS service operations in clustered WebSphere environments, you need to configure the operation properties using different values than what is described in LiveCycle Workbench ES Help. If the process version is a short-lived process, you also need to configure the transaction settings for the process version.If you do not apply the configurations described in this article, the JNDI browser dialog boxes that you use for configuring JMS service operations do not function properly.Connection Factory propertyFor the Publish Message On Topic, Receive Message From Queue, and Send Message To Queue operations, use the following value for the Connection Factory property:cell/clusters/[cluster name]/[queueConnectionFactory]where [cluster name] is the name of the cluster, and [queueConnectionFactory] is the name of the connection factory.Queue Name propertyFor the Receive Message From Queue and Send Message To Queue operations, use the following value for the Queue Name property:cell/clusters/[cluster name]/queue/[queue name]where [cluster name] is the name of the cluster, and [queue name] is the name of the targeted queue.Transaction propogationFor short-lived processes, you need to configure the transaction settings of the process version so that transaction propogation is not supported. To configure the transaction settings:- On the processes view, right-click the process version and click Properties.
- Click the Advanced tab.
- In the Transaction Settings area, select NOT SUPPORTED for the Propagation property, and then click OK.
- If the process version is open for editing, save the process version.
Japanese characters do not display correctly in email responses to offline task completions
When LiveCycle ES is installed on a computer that uses an English version of Windows and the Japanese locale, email messages that are sent to Workspace ES users after they complete tasks offline do not correctly display japanese characters.Pro tools 9 crack windows 7 rar extract. Avid Pro Tools 11 Crack Free Download. Avid Pro Tools 11 crack is 100% free with full features. Avid pro tools 11 crack.rar avid pro tools 11 crack win 7-8 64bits. Avid pro tools 11 crack windows avid pro tools 11 crack mac avid pro tools 11 crack with patch only avid pro tools 11 crack final 2014-rar password.txt avid pro. Pro tools 9 crack for windows free download, Windows Live Messenger 2011 15.4.3555, Windows Live Messenger 2011 15.4.3538.0513, Pro Tools HD 8.0 CS3.If the application server that hosts LiveCycle ES uses UTF-8 character encoding, the user's client email software needs to be configured to use UTF-8 character encoding If the application server that hosts LiveCycle ES uses ISO2202JP character encoding, the folloiwng configurations need to be applied: - The operating system of the computer where the application server is installed must use the Japanese locale.
- The application server must be running on the international version of the Java SDK. If the international version is installed, the Java SDK directories include the jrelibcharset.jar file and the jrelibextlocaledata.jar file.
- The email endpoint uses iso-2022jp character encoding.
- The Java virtual machine that runs the application server uses the -Dfile.encoding=ISO2022JP java option.
Installed processes may need changes to the Character Set Encoding property of Email service operations
The Send With Document operation and the Send With Map of Attachments operation that the Email service provides include the Character Set Encoding property. This property sets the character set that is used to encode email messages that are sent. If no value is specified for the Character Set Encoding property, the character encoding that is set on the application server that hosts LiveCycle ES is used. If your LiveCycle Workspace ES users need a different character encoding than that which is set on the application server, you need to set the character encoding in the operation properties. For example, if your application server is set to use UTF-8 character encoding and your users need to read Japanese characters in email messages, you need to set the character encoding to ISO-2022JP in the operation properties. Some processes that are installed for implementing LiveCycle Process Management ES features use the Send With Document operation and the Send With Map of Attachments operation. These processes send email notifications to LiveCycle Workspace ES users when they are assigned new tasks, when they receive reminders about tasks, or when deadlines occur for their tasks. If required, you need to configure the Character Set Encoding property on the operations in the installed processes.The following table lists the installed processes and the operations that you may need to configure.
<entry key='SessionTimeout' value='600'/>
Workspace, where [workbench install directory] represents the location where LiveCycle Workbench ES was installed.
<PDF source='input.pdf' />
<Header> <Center>
<StyledText>
<p>For review</p>
</StyledText> </Center>
</Header>
</PDF>
.fsc-ds-ssv: This style sheet is applicable in case of a Valid sign field.
.fsc-ds-ssc: This style sheet is applicable in case of a Valid sign field but data has changed.
.fsc-ds-ssi: This style sheet is applicable in case of a invalid sign field.
.fsc-ds-popup-bg: This style sheet property is not being used.
.fsc-ds-popup-btn: This style sheet property is not being used.
int buffSize = 2048;
int docLength = (int) inDoc.length();
byte [] byteDoc = new byte[docLength];
int pos = 0;
while (docLength > 0) {
int toRead = Math.min(buffSize, docLength);
int bytesRead = inDoc.read(pos, byteDoc, pos, toRead);
if (bytesRead -1) {
inDoc.dispose();
throw new RuntimeException('Data retrieval failed!');
pos += bytesRead;
docLength -= bytesRead;
inDoc.doneReading();
inDoc.dispose();
Installed process | Operation label | Operation name |
---|---|---|
Task Assignment | Send no attachments | Send With Document |
Task Assignment | Send Mail | Send With Document |
Task Assignment | Send With Map Of Attachments | Send With Map of Attachments |
Task Reminder | Send with no attachments | Send With Document |
Task Reminder | Send Mail | Send With Document |
Task Reminder | Send With Map Of Attachments | Send With Map of Attachments |
Task Deadlined | Send Deadline Notification | Mail Send With Document |
Use XDP files for sample data files
The 'Configuring form fields to appear in XPath Builder' topic in LiveCycle Workbench ES Help indicates that the sample data file that you use to expose the form's data model in XPath Builder is an XML file. However, the sample data file needs to be an XDP file. Use the Default Data property of the the xfaForm or Form variable to specify the sample data file to use. When you browse for the data file, the Open dialog box filters the file list for XML files by default. To view XDP files in the file list, you need set the Files Of Type property of the dialog box to *.*.
Activity elements cause processes to stall
If you activate a process that contains Activity elements, the process stalls at the Activity element upon execution. Before you activate your processes, ensure that all Activity elements have been implemented with service operations.
Errors dragging large files to the repository
OutOfMemoryError errors can occur when dragging large files, such as 50MB, to the Resources view. Increasing the transaction time-out period that is configured on the application server can increase the size of files that can be dragged to the Resources view without causing the error.
For information about increasing the transaction time-out on the application server, see the 'OutOfMemoryError: Java heap space error' topic in the troubleshooting section of Installing and Deploying LiveCycle ES for your application server.
Cannot use external editors to modify resources
You cannot use software that is external to Workbench ES to edit files that are in the repository. To modify a file, drag the file from the Resources view to the local file system and open it with the external software. After modifying the file, drag it back to the Resources view.
Installed processes and forms
The installation process for LiveCycle Workbench ES installs several processes and forms that the product requires to function correctly. You should not modify these processes and forms.
The installed processes appear on the Processes view. The installed forms appear on the Resources view.
The following table lists the processes that are installed.
Process category | Process name |
---|---|
Process Management | Queue Sharing |
Process Management | Complete Task |
Process Management | Default Render |
Process Management | Task Assignment |
Process Management | Task Deadlined |
Process Management | Share Tasks For Shared Queues |
Process Management | Task Reminder |
Output | PrintPDFPackage |
The following table lists the resources that are installed.
Folder | Resource name |
---|---|
Process Management/Workspace | QueueSharing.swf |
Enter Password dialog box opens behind Workbench ES
When opening a password-protected PDF file, the Enter Password dialog box opens behind Workbench ES. You need to enter a password in the dialog box to view the PDF file.
To see the Enter Password dialog box, hold down the Alt key and press the Tab key repeatedly until the icon for the dialog box is highlighted.
Workbench ES locking issues
Workbench ES allows users that have the correct permissions/roles assigned to lock, edit, and unlock another user's processes, including processes that another user created and has locked. When a user attempts to open a locked process version for editing, a warning message prompts the user to confirm that they want to edit a locked process. However, the user who originally locked the process is unaware that a different user is editing the process.
Web Services QPAC
When you deploy the LiveCycle server with a proxy server and you use the web services QPAC, proxy exceptions are not picked up correctly for web services.
LiveCycle Workbench ES (LiveCycle Designer ES)
You cannot import XFT files using the Tools > Import command
FormFlow 99 files (XFT files) are not associated with LiveCycle Designer ES within LiveCycle Workbench ES. To import XFT files into LiveCycle Designer ES within LiveCycle Workbench, change the file name extension from .xft to .xdp. The first time the file is opened, it is upgraded to an XDP file.
Support of digital signatures in repeating subforms
LiveCycle Forms ES does not support forms that have digital signatures in repeating subforms when they are rendered as HTML forms.
Dragging XDP files that contain multiple fragments onto a form design may cause unexpected results
When you drag an XDP file that contains two or more fragments or script fragments from the repository onto a form design, you may get unexpected results. Instead, select Insert > Fragment and then select the fragment.
Tabbing order in PDF files imported as artwork
Changing the PDF structure or tabbing order in PDF files imported as artwork may cause unexpected behavior in the tabbing order. Save the PDF file before you preview or publish it.
HKSCS - 2001 support for Microsoft Windows 2000 and Windows XP
Hong Kong Supplementary Character Set (HKSCS) rendering is supported by LiveCycle Designer ES. If the correct HKSCS font is selected for the object, HKSCS characters should be displayed correctly in the form design as well as in the Preview PDF tab. However, HKSCS extended characters may not be displayed correctly in LiveCycle Designer ES.
Multiline tool tips
To create multiline tool tips, click the Accessibility palette. In the Tool Tip box, type the first line and then press Ctrl+Enter to go to the next line.
Namespaces and data binding
You cannot use the following namespaces when binding to data through a data connection:
- http://ns.adobe.com/xfdf-transition/
- http://www.w3.org/XML/1998/namespace
- Any namespace prefixed with and including: http://www.xfa.org/schema/xfa-package/
Publishing a form to a web folder in Microsoft Vista
Microsoft Windows Vista™ does not currently support access to an authenticated server that is using basic authentication over HTTP. If you need to set up a web folder and authentication, use HTTPS.
LiveCycle Designer ES XDC file needs to be saved as UTF-8 when paper type name contains extended characters
Using extended characters in the paper type name may cause the Designer.xdc file not to load. Save the file as UTF-8 encoded instead of ANSI encoded.
Previewing PDF files
Clicking the Preview PDF tab opens Adobe Acrobat in its own window when the Display PDF In Browser option is deselected in Acrobat.
When the Display PDF In Browser option is not selected in the Edit > Preferences > Internet dialog box in Acrobat, clicking the Preview PDF tab in LiveCycle Designer ES starts Acrobat in its own window instead of embedding it within the Preview PDF tab. By default, the Display PDF In Browser option is selected.
List boxes display the default value when previewed as print documents
If you specify item values for a list box and then preview the form as a print document, only the default value is displayed.
Barcodes
Delimiter should not be part of textual content
If you choose the delimited format for a paper forms barcode, make sure that the delimiter is not a part of your form's textual contents. For instance, if you choose Tab as the delimiter, the contents of the form fields you are encoding cannot contain tabs because it will confuse the decoder. To avoid this confusion and to ensure that the encoder will work correctly, if the character originally chosen to be the delimiter becomes a part of the contents, you can choose a different character (such as a pipe or a comma) as the delimiter instead.
Paper forms barcode collection name should be different from the object collection name
Make sure that paper forms barcode name is different from the object collection name. Otherwise, the paper forms barcode will not update at run time.
Paper forms barcode in subforms with default names may cause unexpected results
When you include a paper forms barcode in multiple unnamed subforms, you may get unexpected results. Rename the subforms instead of using the default name.
Saving forms that include the paper forms barcode object
The Paper Forms Barcode object encodes data that users type in a fillable PDF form. Use of paper forms barcodes for paper forms processing requires Adobe LiveCycleBarcoded Forms ES (separate license required).
Users must use Adobe Reader® 7.0.5 (or later) or Acrobat 7.0.5 or later to fill a form using QR Code or Data Matrix Paper Forms Barcode. Therefore, form authors must not save the form as either Acrobat 7.0 Compatible or Acrobat 6 Compatible.
Users must use Adobe Reader 7.0 (or later) or Acrobat 7.0 (or later) to fill a form that includes the PDF417 Paper Forms Barcode. Therefore, form authors must not save the form as Acrobat 6 Compatible.
Barcodes that have either a tab-delimited or an XML format are not updated
Barcodes that have either a tab-delimited or an XML format are not updated when the encoded data includes only the subform.
Supported image file name extensions for barcoded forms
When decoding image files using a watched folder, the image files must use one of the following file name extensions: .pdf, .tif, or .tiff. The decoder is case-sensitive and therefore you cannot use any other variation (for example, .Pdf or .Tif).
Acrobat users need to activate LiveCycle Designer ES (8.1)
You may encounter problems when opening XDP files if you have multiple instances of LiveCycle Designer ES (8.1) installed. If an Incompatible LiveCycle Designer Version error occurs when you open an XDP file using LiveCycle Workbench ES, you need to activate the version of LiveCycle Designer that is installed with LiveCycle Workbench ES. After you activate it, the error no longer occurs.
For example, you install Acrobat version 8.0, which also installs LiveCycle Designer 8.0. You then install LiveCycle Workbench ES, which installs LiveCycle Designer ES (which is version 8.1), the version that is compatible with LiveCycle Workbench ES. The Incompatible LiveCycle Designer Version error occurs if the instance of LiveCycle Designer that is installed with Acrobat is activated instead of the instance that is installed with LiveCycle Workbench ES.
To activate LiveCycle Designer ES (8.1):
- Open LiveCycle Designer ES (8.1) using one of the following methods:
- Click Start > All Programs > Adobe LiveCycle Designer ES 8.1.
- Double-click FormDesigner.exe in the [workbench install folder]/Designer ES folder.
- In the Check For Default dialog box, click Yes.
Documentation
Conditional breaks in subforms are not updated when the referenced fragment in the subform is updated
LiveCycle Designer ES Help should state that if you have a conditional break that refers to a subform or fragment and you change the subform or fragment name, the conditional break is not updated.
Invalid properties for subform objects
In LiveCycle Designer ES Help, the maxH, minH, maxW, and minW properties are incorrectly listed as being valid for subform objects.
Type property options in the Value tab
In LiveCycle Designer ES Help, the User Entered - Required option for the Type property should read as follows:
Adobe Livecycle Designer Tutorial Pdf
User Entered - Required: A user must enter a value in the field. If the user leaves the field empty and moves to another place on the form, an empty message box appears (if you have typed a custom message for prompting the user to enter data). The custom message appears only if there was a value in the field, the value was deleted, and the user exited the field without reentering a value. If the user never attempts to enter a value in the field and tries to submit the form, a 'field is required' message appears instead of the custom message.
Target version of Acrobat and Adobe Reader
In LiveCycle Designer ES Help, the target versions Acrobat and Adobe Reader 6.0 and Acrobat and Reader 7.0 should read Acrobat and Reader 6.0.2 and Acrobat and Reader 7.0.5.
LiveCycle Remoting
Cannot access enum values when using LiveCycle Remoting
When using LiveCycle Remoting to invoke services, you cannot access enum values that are part of a Java complex data type. For example, you cannot access the PDFSignatureAppearanceType.Graphic enum value that is a required parameter value for the PDFSignatureAppearanceOptionSpec.setAppearanceType method. The reason is because Flex supports Java 1.4x and enum values require Java 1.5x.
Because you cannot access enum values, you cannot invoke service operations that require Java enum values. It is recommended that you create a process using LiveCycle Workbench ES that invokes service operations that require Java enum values and invoke the process using LiveCycle Remoting.
Output service
Restarting applications when XDC files are modified
If you modify an existing XDC file, you must restart the LiveCycle ES application that uses it in order for the updated XDC file to be reloaded and used.
Invoking the Output service using email messages
You can attach multiple PDF documents to a single email message that invokes the Output service. For example, you can convert PDF documents to PDF/A documents by sending an email message that contains PDF file attachments. For each file attachment, a separate email message is returned to the email recipient that sent the message. Each email message contains one file attachment and each file attachment has the same file name.
Reader Extensions service
Warning when applying usage rights to large numbers of documents
When you are applying usage rights to a large number of documents, the following warning can occur: ALC-RES-001-028: Unable to access the use count of the credential specified. Perform the following configuration to work around this problem:
·If you are using the Java API, set the isModeFinalparameter of the ReaderExtensionsOptionSpec object to false.
·If you are using the Apply Usage Rights operation in LiveCycle Workbench ES, in the Apply Usage Rights Options area of the Input properties for the operation, select Draft.
When using this configuration, the warning will not occur; however, LiveCycle Reader Extensions ES does not increment the Forms Processed counter.
Rights Management service
Policy or document owner unable to access document using Rights Management Document Service API
Currently, the API logic only checks for hasMyPolicyPermission when it checks whether a user has permission on a user policy user document. Because hasMyPolicyPermission is not sufficient, the user will not be provided access to the document.
The two methods affected by this problem are PolicyManager.getPolicy and PolicyManager.deletePolicy.
Instead of using the PolicyManager.getPolicy, you should use the PolicyManager.getPolicies when you are an administrator trying to retrieve a user's policy as shown in the following pseudo code:
User user = aMethodThatReturnsTheUserBasedOnUserId( 'tbuser' )
if( user null) throw new Exception( “Could not find a user” );
PolicySearchFilter filter = new PolicySearchFilter();
filter.setName( “My Policy” );
filter.setOwner( user );
Policy[] policies = policyManager.getPolicies( filter, 2 );
if( policies 0 ) throw new Exception( “Could not find the policy.” );
if( policies > 1 ) throw new Exception( “Found more than one policy matching the search filter.”);
Policy policy = policies[0];
if( user null) throw new Exception( “Could not find a user” );
PolicySearchFilter filter = new PolicySearchFilter();
filter.setName( “My Policy” );
filter.setOwner( user );
Policy[] policies = policyManager.getPolicies( filter, 2 );
if( policies 0 ) throw new Exception( “Could not find the policy.” );
if( policies > 1 ) throw new Exception( “Found more than one policy matching the search filter.”);
Policy policy = policies[0];
Instead of using the PolicyManager.deletePolicy, you should use the PolicyManager.changePolicyOwner when you are trying to delete a user’s policy, as shown in the following pseudo code:
User user = aMethodThatReturnsTheUserBasedOnUserId( 'tbuser' );
User admin = aMethodThatReturnsTheUserBasedOnUserId( 'administrator' );
if( user null || admin null) throw new Exception( “Could not find a user.” );
policyManager.changePolicyOwner( “My Policy”, user, admin );
deletePolicy( null, “My Policy” );
User admin = aMethodThatReturnsTheUserBasedOnUserId( 'administrator' );
if( user null || admin null) throw new Exception( “Could not find a user.” );
policyManager.changePolicyOwner( “My Policy”, user, admin );
deletePolicy( null, “My Policy” );
For more code examples, see the LiveCycle ES SDK Help.
Security
Email service sends passwords in clear text
The Send With Document operation of the Email service allows you to send an email message with a document attached to it. To configure the operation, you can specify the user name and password required to authenticate with the SMTP server. You should be aware that the password is sent to the SMTP server in clear text.
Security service
Certificate authentication error
Certificate Authentication fails when the certificate's canonical name is mapped to the user's full name. The authentication request fails with the error 'Authentication failed since certificate info does not map to a unique user.'
Signature service
Using an nCiphernShield HSM credential
When using an nCiphernShield HSM credential to sign or certify a PDF document, the new credential cannot be used until the J2EE application server on which LiveCycle ES is deployed is restarted. However, you can set a configuration value, resulting in the sign or certify operation working without restarting the J2EE application server.
You can add the following configuration value in the cknfastrc file, which is located at /opt/nfast/cknfastrc (or c:nfastcknfastrc):
CKNFAST_ASSUME_SINGLE_PROCESS=0
After you add this configuration value to the cknfastrc file, the new credential can be used without restarting the J2EE application server.
Scaling signature field text
The text within the signature appearance may not get scaled fully to fit the size of the signature field.
Signing or certifying an invalid PDF document
If you attempt to sign, certify, or verify an invalid PDF document using the Signature service, you may encounter exception messages or problems when processing the input PDF document, and such exception messages may vary for bad or invalid PDF documents.
Certifying documents concurrently
In some situations, a java.net.SocketTimeoutException is thrown while running certifying documents concurrently. To avoid this situation, it is recommended that you increase the socket time-out value to 300 seconds using the LiveCycle Administration Console.
Using HSM credentials to sign and certify documents
A Sign or Certify operation will fail when the HSM service is restarted. For these operations to work, the J2EE application server on which LiveCycle ES is deployed must be restarted.
Rotating the appearance of a signature
The orientation of the signature appearance is not in accordance with the rotation value of the page. That is, if you print a Microsoft Word document in landscape mode as a PDF document, apply a signature field, and then sign the document, the orientation of the signature appearance does not take page rotation into account. It is not possible to rotate the signature appearance of a PDF page set in the landscape mode.
Certify signatures are not trusted
When certifying and signing the same PDF document, if the certify signature is not trusted, a yellow triangle appears against the first sign signature when opening the PDF document in Acrobat or Adobe Reader. The certifying signature must be trusted in order to avoid this situation.
Signature service does not support XDP files with embedded PDF data
The Signature service in LiveCycle Digital Signatures ES does not support XDP files with embedded PDF data as input to an operation such as certifying a document. This action results in the Signature service throwing a PDFOperationException. To resolve this issue, convert the XDP file to a PDF file by using the PDF Utilities service and then pass the converted PDF file to a Signature service operation.
Task Manager Query service
Exception using TaskManagerQuery Service WSDL
When directly consuming the TaskManagerQueryService WSDL on native SOAP stacks, the taskSearch web method, when used to set the TaskSearchFilter, will throw an exception.
Invoking the taskList method using web services
You can create Java proxy classes for the Task Manager Query service using Apache Axis. Normally, these classes let you invoke this service using its exposed web service. However, an exception is thrown if you invoke the taskList method.
User Management
Errors while creating multiple users and groups
Creating multiple local users and groups while an LDAP directory synchronization is in progress is not supported. Attempting this process may result in errors.
Consuming the WSDL for Generate PDF on a WebSphere Application Server cluster causes an authentication error
If the server time zone is different from the client time zone, when consuming the WSDL for the LiveCycle ES Generate PDF service on a native SOAP stack using a .NET client on a WebSphere Application Server cluster, the following User Management authentication error may occur:
[com.adobe.idp.um.webservices.WSSecurityHandler] errorCode:12803 errorCodeHEX:0x3203 message:WSSecurityHandler: UM authenticate returns exception : An error was discovered processing the <wsse:Security> header. (WSSecurityEngine: Invalid timestamp The security semantics of message have expired).
Invoking the getComponents method using web services
You can create Java proxy classes for the Service Registry service using Apache Axis. Normally, these classes let you invoke this service using its exposed web service. However, a java.lang.StackOverflowError is thrown if you invoke the getServiceConfigurations method.
User Management may throw an exception when more than 1000 local users are created
For all services on all platforms, when invoking the User Management API createLocalUsers, an exception may occur when the number of users is approximately 1000 or more. This exception occurs because the activity is expected to occur within a single transaction, which will time out according to the limit configured in the production environment.
Watched Folder
Creation of watched folders for import and export operations does not allow file name extension abstraction
When invoking the Form Data Integration service using watched folders, the file name extension type for the output file may not match the intended output format for the document object type. For example, if the input file to a watched folder that invokes the export operation is an XFA form that contains data, the output should be an XDP data file. To obtain an output file with the correct file name extension, you can specify it in the output parameter mapping. In this example, you can use %F.xdp for the output parameter mapping.
Watched Folder may process input files before they are completely copied to the folder
File locking is not mandatory on UNIX as it is on Windows. For this reason, when a file is being copied to a watched folder, Watched Folder may move the file to stage without waiting for the file copy to complete. This behaviour causes only a portion of the input file to be processed. There are currently two workarounds:
Workaround 1
- Specify a pattern for Exclude File Pattern, such as temp*.ps.
- Copy files that begin with temp (for example, temp1.ps) to the watched folder.
- After the file has been completely copied to the watched folder, rename the file to correspond with the pattern specified for Include File Pattern. Watched Folder then moves the completed file to stage.
Workaround 2
If you know the maximum length of time it will take to copy your files to a watched folder, specify the time in seconds for Wait Time. Watched Folder then waits the specified length of time before moving the file to stage.
This is not an issue for files on Windows because Windows locks a file when one thread is writing. However, this is an issue for folders on Windows. For folders, you must follow the steps in Workaround 1.
Staging directory not cleaned out when Preserve Folder Name set to null
If the Preserve Folder Name endpoint attribute for Watched Folder is set to a null directory path, the staging directory is not cleaned out as it should be. The directory still contains the processed file and temporary folder.
Performance Issues
Improving the performance of the Reader Extensions service when applying usage rights to PDF documents
When applying usage rights to PDF documents using the applyUsageRights method, which is part of the Java API, you can set the isModeFinal parameter of the ReaderExtensionsOptionSpec object to false. This results in the forms processed counter not being updated and an improvement in performance. If you are not concerned about updating the forms processed counter, it is recommended that you set the isModeFinal parameter to false.
Output service
LiveCycle Output ES cannot format arbitrarily large XML data files. Throughput is limited by available application server memory. Large data files can contain many smaller records that will create a single output file that contains many smaller documents (batch records/many small documents) or sometimes one large data record that will produce one output file with one large document (big record/one big document).
Throughput limitations are not discreet and will vary, depending of the complexity of the form design, available memory, options chosen and other activity on the application server. Errors generated when such a limitation is reached may identify lack of memory as being the problem, but not always, and may seem unrelated. You should be aware of this limitation and use the Output service within safe page generation number guidelines.
For a medium complexity form (the PO form in Output IVS; 2-page records for batch case) on a typical entry level business server, we have observed the following approximate safe page generation number guidelines.
Format | Batch records/many small documents | Big record/one big document |
---|---|---|
PDF (not tagged) & PDF/a-1b | 10000 pages | 500 pages |
PDF (tagged) & PDF/a-1a | 5000 pages | 250 pages |
PostScript | 10000 pages | 500 pages |
PCL (using True Type or printer fonts) | 10000 pages | 500 pages |
There are a few things to note in order to maximize throughput performance. Only select tagging for PDF if it is required. Be aware that PDF/A-1a is always tagged; PDF/A-1b is not tagged. For PCL printing; the use of Adobe OpenType fonts in form designs will format properly but will decrease throughput, generate a larger output file, and will not deliver optimal performance. For increased performance, use or map properly licensed TrueType fonts or use printer resident fonts.
When processing large data files or operating on a busy server, it may be necessary to increase the Output service time-out; the default time-out is 180 seconds. To change the time-out value, ensure that hardware servers have adequate memory and that the memory is available to the Java Application Server heap.
When processing a big record/one big document case, throughput will be maximized when the XML data is structured so that a recordLevel run-time option of 2 can be used.
When processing a big record/one big document case, throughput will be maximized when the XML data is structured so that a recordLevel run-time option of 2 can be used.
For example, rather than structuring your data file this way:
<datafile>
<field>123</field>
…
</datafile>
<datafile>
<field>123</field>
…
</datafile>
Structure it this way, adding another level:
<datafile>
<record>
<field>123</field>
…
</record>
</datafile>
<datafile>
<record>
<field>123</field>
…
</record>
</datafile>
To change the time-out value:
- Log into the LiveCycle ES Administration Console.
- Click Services > Archive Administration > Service Management > Output Service: 1.0.
- Select Configuration, and change the Transaction Time Out value.
- Restart the service for the change to take effect.
The Output service has a setting to control the number of parallel asynchronous jobs that can run at one time in order to ensure that jobs do not overwhelm the server. Any additional jobs are queued and will be initiated only when a job is finished, and thus will not time out. This setting must be less than the XMLForm BMC pool-max value to allow room for synchronous jobs initiated by the Output service and the Forms service. If this setting is greater than the XMLForm BMC pool-max value, additional asynchronous requests will be put on hold but can be in a started state and may time out. For more information about changing the XMLForm BMC pool-max value, see the 'Advanced Production Configuration' chapter in the Installing and Deploying LiveCycle ES document for your application server.
To control the number of parallel asynchronous jobs:
- Log into the LiveCycle ES Administration Console.
- Click Services > Archive Administration > Service Management > Output Service: 1.0.
- Select Configuration, and change the setting for Maximum Concurrent Invocations for Asynchronous Jobs.
- Restart the service for the change to take effect.
Quick Starts and Samples Issues
Form is not rendered using web services when the web server is SSL-enabled
On a Digital Signature setup, when you access a Forms service application deployed on a J2EE application server using an SSL-enabled web server, you cannot render a form when you click the Use WebServices button from FormsIVS. This situation applies only when the server, and not the J2EE application server, is SSL-enabled.
Sample XDC Files in LiveCycle Workbench ES(Samples - Ghis)
When you try to open any of the XDC files listed below the Samples/Output directory in the Resources view, Workbench ES displays an error. To view and edit any of the XDC files provided with LiveCycle ES, follow the instructions described in the XDC Editor Help at www.adobe.com/go/learn_lc_xdcEditor.
End User Issues
General Items
Opening a drop-down list within a form
If the drop-down list within a rendered form contains data items that cannot be opened, you must perform the following action within Adobe Reader or Acrobat. Select Edit > Preferences > Forms and deselect Keep forms data temporarily available on disk.
Adobe Reader 7.x and Forms
When you enter data in a form field using Adobe Reader 7.x, you must be sure to press Enter after entering the data and before you submit the form. If you do not press Enter, the data that you entered in the form field is not submitted with the form.
LiveCycle Reader Extensions ES
Cannot use form in Adobe Reader 7.x after saving in Adobe Acrobat 7.x
For some forms, after adding usage rights to the form, if you open and save the form in Adobe Acrobat 7.x and then open the PDF form file in Adobe Reader 7.x, an error occurs indicating that the usage rights are no longer valid. This may indicate that Acrobat 7.x has identified a problem and automatically repaired the form when it was first opened and saved.
The current workaround is to open the PDF form in Acrobat 7.x, optimize the form, and then reapply the usage rights. Optimizing the form prior to applying the usage rights ensures that Acrobat does not need to repair the file on subsequent saves.
Cannot apply usage rights to files using some special characters in file name
Acer aspire 4520g drivers for mac. When applying usage rights to a PDF file, if the file name contains an escape sequence, the operation hangs. An escape sequence is a series of characters that generally contain these characters: & # ;
The current workaround is to remove any of the above characters from the file name.
LiveCycle Rights Management ES
Special characters in Policy Name and Policy Description fields
When creating a policy using Acrobat Professional 7.x, the special characters > < ' ' & : cannot be used in the Policy Name and Policy Description fields.
LiveCycle Workspace ES
Attachment order for tasks submitted in email messages
When you submit a LiveCycle Workspace ES task using email, the XDP file that represents the task form must be the first attachment in the email message that is an XDP file. If the email message includes several attachments and the XDP form file is not the first XDP file, the LiveCycle ES server does not process the task. Other files can precede the XDP form file in the attachments list if they are not XDP files.
Data selected in drop-down lists is not displayed after the form is submitted
In Acrobat 8.1, if you are working with a form that has drop-down lists, after the form is submitted, any selections made in the drop-down lists are not displayed if you reopen the form. This is because the data is no longer needed; however, the data is retained in the actual PDF file.
Changes are not preserved when made to a form before a task is consulted on
If you make changes to a form associated with a task and then consult on the task with another user, the changes to the form are not preserved. This allows the consulted user to see the form without your changes. To preserve your changes, you must save the form as a draft before consulting on the task with the other user.
Deadline icon does not appear on consulted task
Adobe Live Cycle Designer Tutorial
When the deadline has passed on a task that you have consulted on with another user, the deadline icon does not appear on the task.
Error dialog box does not appear when task associated with a deactivated process is submitted
When a process is deactivated in LiveCycle Administration Console, the tasks currently associated with instances of the process remain in LiveCycle Workspace ES. When the task is submitted, an exception appears in the log file, but an error dialog does not appear.
Cannot track processes if you forwarded initial task to another user
When you start a process, if you forward the initial task in the process to another user and the second user completes and submits the task, the second user is considered the initiator of the process. Because you are not considered the initiator, you cannot view and track the tasks in the process.
A future version of LiveCycle Workspace ES will correct this issue; however, this feature will not be backwards-compatible with LiveCycle 8.0.x when it is corrected.
Save in draft folder button is unavailable for some forms
In LiveCycle Workspace ES, the Save In Draft Folder button is unavailable for some forms, depending on the form design of the form associated with the process that you are working on.
Older images used for processes are preserved
An image used for a process is stored for 24 hours. If the image is changed in the process definition, you cannot view the image immediately unless you clear the cache in your web browser.
Reclicking a forwarded task causes a persistent error
When you forward a task to another user, it takes a moment for the task to disappear from your task list. If, during this time, you reclick the task, an error appears that indicates that the form could not be created. The error is false because the task was indeed forwarded. Unfortunately, that error continues to appear when you view your task list even after the forwarded task has been removed.
The current workaround is to log out and log in again.
Error occurs when searching for process instances for a deactivated process
If you search for process instances for a process that has been deactivated, the following error appears:
'An error occurred retrieving process instances (process null). (ALC-WKS-007-044)'
Search results are not displayed based on the settings in the search template
When searching for a process or task using a search template, the search results are not displayed based on the following settings defined in the search template:
- If the Process Status and Task Owner elements are listed in the Columns to Report list for the search template definition in LiveCycle Administration Console, when you perform a search in LiveCycle Workspace ES using the search template, the two columns are not displayed in the search results.
- If the checkbox beside an element that is listed in the Sort Order list for the search template definition is deselected (which indicates to sort the column in ascending order), when you perform a search in LiveCycle Workspace ES using the search template, the search results are sorted by the column in descending order.
(Firefox) Cannot type double byte characters for user names
If you are accessing LiveCycle Workspace ES through a Firefox web browser, you cannot type user names with double byte characters into the User Name field on the Login screen.
The current workaround is to copy and paste the user name into the User Name field in Firefox or to access LiveCycle Workspace ES through an Internet Explorer web browser.
Error occurs when opening tasks that have been claimed from shared queues
If you attempt to unlock a task that has already been claimed from a shared queue, there is no response. There should be a message indicating that the task has been claimed. If you then open the task, the following error appears:
“The attempt to claim task 151 has failed. (ALC-WKS-007-075)'
The Documentation Set
For LiveCycle ES, all of the product documentation is now available online on the Adobe website at www.adobe.com/go/learn_lc_documentation. The information on the website is available in PDF files, downloadable ZIP files, or HTML/LiveDocs format. LiveDocs are HTML files to which you can directly add comments on the documentation content.
Additional Documentation Notes
URL in copyright page does not exist
In the Copyright and Trademark Notices for each of the documents, the http://jaxen.werken.com URL that is provided does not exist. This URL should not appear in the notices and will be removed in the next release.
Updated information for PDF Generator Administration Help
The following updates for PDF Generator Administration Help were not available when the Help was written:
- The http://whatis.techtarget.com link in the 'HTML to PDF settings' topic does not work. This URL should not appear in the Help and will be removed in the next release.
- The default time-out value in the 'Converting HTML Settings to PDF Settings' topic is incorrectly stated to be 570 seconds. The correct default value is 270 seconds.
- The titles of the 'Converting HTML Settings to PDF Settings' and 'Configuring PDF Export Settings' topics are incorrect. The correct titles are 'Converting HTML to PDF' and 'Exporting PDF to text and image file formats'.
Updated topic for User Management Help
The following procedure from the 'Configuring the LDAP bind password' topic in the User Management Help contains some updated steps that were not available when the Help was written:
To configure the LDAP bind password:
- On the User Management page, click Configuration.
- On the Configuration page, click Import and export configuration files.
- To export the current configuration setting to a file, click Export and then save the configuration file in another location.
- Find the following node in the file:
- Find the following node in the file:
- To import the file, in User Management, click Configuration, click Import and export configuration files, click Browse to find the file, and then click Import.
- Click OK.
<node name='>
<map>
<entry key='bindanonymously' value='false' />
<entry key='basedn' value='dc=corp,dc=adobe,dc=com' />
<entry key='batchSize' value='200' />
<entry key='binduser' value='cn=Directory Manager'/>
<entry key='bindpassword' value=' />Type a value for bindpassword and binduser and save your changes.
<node name='LDAPUserConfig'>
<map>
<entry key='bindanonymously' value='false' />
<entry key='batchSize' value='200' />
<entry key='basedn' value='dc=corp,dc=adobe,dc=com' />
<entry key='bindpassword' value=' />
<entry key='binduser' value='cn=Directory Manager' />
</map>Type a value for bindpassword and binduser and save your changes.
Updated information for the Archive Administration Help
The following option descriptions for the 'Taskmanager connector endpoints' topic in the Archive Administration Help were not available when the Help was written:
- User Can Forward Task: Allows user to forward the initial task.
- Show Attachment Window: Allows user to see the attachment window.
- Allow Attachment Adding: Allows user to add attachments and notes.
- Task Initially Locked: Locks the initial task.
- Add ACLs for Shared Queues: The initial task is created with ACLs for shared queue users.
Support for FIPS mode
The What’s New for LiveCycle ES document contains inaccurate information about the supported FIPS mode encryption module. The second sentence should read as follows:
'The FIPS option restricts data protection to FIPS 140-2 approved algorithms using the RSA BSAFE Crypto-C 2.1 encryption module.'
Additional Licenses and Copyrights
By installing this product, in addition to the Adobe license terms, you also agree to be bound by the third-party terms specified in the product documentation and at www.adobe.com/go/thirdparty. Adobe recommends that you review these third-party terms.
Release Notes -- Adobe LiveCycle ES (8.0.1) -- 08/10/2007 14:55
November 22, 2012
Copyright 2012 Adobe Systems Incorporated and its licensors. All rights reserved.
This file contains important information about the supported platform combinations for Adobe® LiveCycle® Enterprise Suite 3, version 10.0.4.
Contents
Third-Party Patch Support
Third-party reference platforms described in this document represent a specific patch level of third-party infrastructure that was current during the development and release of this version of Adobe LiveCycle and were used for product verification.To review Adobe’s policy regarding third-party patch support and software compatibility, see the knowledge base article on our Third-party Patch Support Policy.
LiveCycle
This table lists the supported operating systems, application servers, Java Development Kit (JDK), and database configurations.
Operating System | Application Server | Database | JDBC Driver | Architecture | JDK |
IBM AIX 6.1 | IBM WebSphere 7.0.0.15 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
IBM AIX 6.1 | IBM WebSphere 7.0.0.15 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
IBM AIX 6.1 | IBM WebSphere 8.0.0.3 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
IBM AIX 6.1 | IBM WebSphere 8.0.0.3 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
Microsoft Windows Server 2003 R2 SP2 | IBM WebSphere 7.0.0.15 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
Microsoft Windows Server 2003 R2 SP2 | IBM WebSphere 7.0.0.15 | Microsoft SQL Server 2005 SP2 / 2008/ 2008 R2 | Microsoft SQL Server JDBC driver 3.0 (sqljdbc4.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
Microsoft Windows Server 2003 R2 SP2 | IBM WebSphere 7.0.0.15 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
Microsoft Windows Server 2008 R1/R2 | IBM WebSphere 7.0.0.15 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
Microsoft Windows Server 2008 R1/R2 | IBM WebSphere 7.0.0.15 | Microsoft SQL Server 2005 SP2 / 2008/ 2008 R2 | Microsoft SQL Server JDBC driver 3.0 (sqljdbc4.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
Microsoft Windows Server 2008 R1/R2 | IBM WebSphere 7.0.0.15 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
Microsoft Windows Server 2008 R1/R2 | IBM WebSphere 8.0.0.3 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
Microsoft Windows Server 2008 R1/R2 | IBM WebSphere 8.0.0.3 | Microsoft SQL Server 2005 SP2 / 2008/ 2008 R2 | Microsoft SQL Server JDBC driver 3.0 (sqljdbc4.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
Microsoft Windows Server 2008 R1/R2 | IBM WebSphere 8.0.0.3 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
Microsoft Windows Server 2008 R1/R2 | JBoss 5.1 (EAP 5.1.0) | Microsoft SQL Server 2005 SP2 / 2008/ 2008 R2 | Microsoft SQL Server JDBC driver 3.0 (sqljdbc4.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Microsoft Windows Server 2008 R1/R2 | JBoss 5.1 (EAP 5.1.0) | MySQL 5.1.30 | Connector/J 5.1.14 (mysql-connector-java-5.1.14-bin.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Microsoft Windows Server 2008 R1/R2 | JBoss 5.1 (EAP 5.1.0) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Microsoft Windows Server 2008 R1/R2 | Oracle WebLogic Server 11g (10.3.3) | Microsoft SQL Server 2005 SP2 / 2008/ 2008 R2 | Microsoft SQL Server JDBC driver 3.0 (sqljdbc4.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Microsoft Windows Server 2008 R1/R2 | Oracle WebLogic Server 11g (10.3.3) | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Microsoft Windows Server 2008 R1/R2 | Oracle WebLogic Server 11g (10.3.3) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Microsoft Windows Server 2008 R1/R2 | Oracle WebLogic Server 11g (10.3.5) | Microsoft SQL Server 2005 SP2 / 2008/ 2008 R2 | Microsoft SQL Server JDBC driver 3.0 (sqljdbc4.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Microsoft Windows Server 2008 R1/R2 | Oracle WebLogic Server 11g (10.3.5) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Microsoft Windows Server 2008 R1/R2 | Oracle WebLogic Server 11g (10.3.6) | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Microsoft Windows Server 2008 R1/R2 | Oracle WebLogic Server 11g (10.3.6) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Microsoft Windows Server 2008 R1/R2 | Oracle WebLogic Server 11g (10.3.6) | Microsoft SQL Server 2005 SP2 / 2008/ 2008 R2 | Microsoft SQL Server JDBC driver 3.0 (sqljdbc4.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Oracle Solaris 10 08/07 (SPARC) | JBoss 5.1 (EAP 5.1.0) | MySQL 5.1.30 | Connector/J 5.1.14 (mysql-connector-java-5.1.14-bin.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Oracle Solaris 10 08/07 (SPARC) | JBoss 5.1 (EAP 5.1.0) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Oracle Solaris 10 08/07 (SPARC) | IBM WebSphere 7.0.0.15 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
Oracle Solaris 10 08/07 (SPARC) | IBM WebSphere 7.0.0.15 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
Oracle Solaris 10 08/07 (SPARC) | IBM WebSphere 8.0.0.3 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
Oracle Solaris 10 08/07 (SPARC) | IBM WebSphere 8.0.0.3 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
Oracle Solaris 10 08/07 (SPARC) | Oracle WebLogic Server 11g (10.3.3) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Oracle Solaris 10 08/07 (SPARC) | Oracle WebLogic Server 11g (10.3.5) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Oracle Solaris 10 08/07 (SPARC) | Oracle WebLogic Server 11g (10.3.6) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Red Hat Enterprise Linux Server & AP 5.5 (x86_64) | Oracle WebLogic Server 11g (10.3.3) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Red Hat Enterprise Linux Server & AP 5.5 (x86_64) | Oracle WebLogic Server 11g (10.3.5) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Red Hat Enterprise Linux Server & AP 5.5 (x86_64) | Oracle WebLogic Server 11g (10.3.6) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle JRockit Java 6 (R28) |
Red Hat Enterprise Linux Server & AP 5.5 (x86_64) | IBM WebSphere 7.0.0.15 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
Red Hat Enterprise Linux Server & AP 5.5 (x86_64) | IBM WebSphere 7.0.0.15 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
Red Hat Enterprise Linux Server & AP 5.6 (x86_64) | IBM WebSphere 8.0.0.3 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
Red Hat Enterprise Linux Server & AP 5.6 (x86_64) | IBM WebSphere 8.0.0.3 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
Red Hat Enterprise Linux Server & AP 5.5 (x86_64) | JBoss 5.1 (EAP 5.1.0) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Red Hat Enterprise Linux Server & AP 5.5 (x86_64) | JBoss 5.1 (EAP 5.1.0) | MySQL 5.1.30 | Connector/J 5.1.14 (mysql-connector-java-5.1.14-bin.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
SUSE Linux Enterprise 11 (x86_64) | IBM WebSphere 7.0.0.15 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
SUSE Linux Enterprise 11 (x86_64) | IBM WebSphere 7.0.0.15 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR9 |
SUSE Linux Enterprise 11 (x86_64) | IBM WebSphere 8.0.0.3 | IBM DB2 9.1 or later | IBM DB2 Universal JDBC driver 3.50.152 (db2jcc.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
SUSE Linux Enterprise 11 (x86_64) | IBM WebSphere 8.0.0.3 | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | IBM WebSphere Java SDK 1.6 SR1 FP1 |
SUSE Linux Enterprise 11 (x86_64) | JBoss 5.1 (EAP 5.1.0) | MySQL 5.1.30 | Connector/J 5.1.14 (mysql-connector-java-5.1.14-bin.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
SUSE Linux Enterprise 11 (x86_64) | JBoss 5.1 (EAP 5.1.0) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Microsoft Windows 7 32-bit and 64-bit | Turnkey installations, supported only for evaluation and development of the server | ||||
Microsoft Windows Vista32-bit and 64-bit | Turnkey installations, supported only for evaluation and development of the server. |
This table lists the supported operating systems, application servers, Java Development Kit (JDK), and database configurations for upgrading JBoss 4.x based installations.
Operating System | Application Server | Database | JDBC Driver | Architecture | JDK |
Microsoft Windows Server 2008 R1/R2 | JBoss 4.2.1 (EAP 4.3) | MySQL 5.1.30 | Connector/J 5.1.14 (mysql-connector-java-5.1.14-bin.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Microsoft Windows Server 2008 R1/R2 | JBoss 4.2.1 (EAP 4.3) | Microsoft SQL Server 2005 SP2 / 2008/ 2008 R2 | Microsoft SQL Server JDBC driver 3.0 (sqljdbc4.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Microsoft Windows Server 2008 | JBoss 4.2.1 (EAP 4.3) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Microsoft Windows Server 2003 R1 SP2/R2 SP2 | JBoss 4.2.1 (EAP 4.3) | MySQL 5.1.30 | Connector/J 5.1.14 (mysql-connector-java-5.1.14-bin.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Microsoft Windows Server 2003 R1 SP2/R2 SP2 | JBoss 4.2.1 (EAP 4.3) | Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Microsoft Windows Server 2003 R1 SP2/R2 SP2 | JBoss 4.2.1 (EAP 4.3) | Microsoft SQL Server 2005 SP2 / 2008/ 2008 R2 | Microsoft SQL Server JDBC driver 3.0 (sqljdbc4.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Red Hat Enterprise Linux Server & AP 5.0 (x86_64) | JBoss 4.2.1 (EAP 4.3) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Red Hat Enterprise Linux Server & AP 5.0 (x86_64) | JBoss 4.2.1 (EAP 4.3) | MySQL 5.1.30 | Connector/J 5.1.14 (mysql-connector-java-5.1.14-bin.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Oracle Solaris 10 8/07 (SPARC) | JBoss 4.2.1 (EAP 4.3) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Oracle Solaris 10 8/07 (SPARC) | JBoss 4.2.1 (EAP 4.3) | MySQL 5.1.30 | Connector/J 5.1.14 (mysql-connector-java-5.1.14-bin.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
SUSE Linux Enterprise 10 (x86_64) | JBoss 4.2.1 (EAP 4.3) | MySQL 5.1.30 | Connector/J 5.1.14 (mysql-connector-java-5.1.14-bin.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
SUSE Linux Enterprise 10 (x86_64) | JBoss 4.2.1 (EAP 4.3) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
SUSE Linux Enterprise 11 (x86_64) | JBoss 4.2.1 (EAP 4.3) | Oracle 10g R2 Oracle 11g R1/R2 | Oracle Database 11g Release 1 JDBC driver 11.2.0.3 (ojdbc6.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
SUSE Linux Enterprise 11 (x86_64) | JBoss 4.2.1 (EAP 4.3) | MySQL 5.1.30 | Connector/J 5.1.14 (mysql-connector-java-5.1.14-bin.jar) | 64-bit OS / 64-bit JVM | Oracle Java 6 update 26 or higher |
Notes:
- It is recommended to install JBoss 5.1 for fresh installation. However, use JBoss 4.2.1 if you are upgrading from a previous version of LiveCycle running on JBoss 4.x or your applications use the custom Java code that might fail with JBoss 5.1.
- JBoss 4.2.1 is not supported for Correspondence Management.
- The Correspondence Management Solution user interfaces (Manage Assets and Create Correspondence) are supported on a machine with a minimum resolution set to 1024 × 768.
- Minimum RAM required for LiveCycle, version 10.0.3 is 4 GB.
- Production environment for LiveCycle, version 10.0.3, supports only 64-bit operating systems.
- Microsoft Windows Server 2003 R2 SP2 and Microsoft Windows Server 2008 R1/R2 includes standard and enterprise editions.
- Oracle 11g includes Oracle 11g R1/R2 Standard, Real Application Clusters (RAC) and Enterprise editions.
- Oracle 10g includes Oracle 10g R2 Standard, Real Application Clusters (RAC) and Enterprise editions(10.2.0.1 and above).
- LiveCycle ES3 supports only Oracle Real Application Clusters (RAC). LiveCycle ES3 does not support cluster/failover architecture for any other supported database.
- IBM WebSphere 7.0.0.15 includes Base and Network Deployment editions.
- Oracle WebLogic Server 11g R1 (10.3.3 and 10.3.5) includes Standard and Enterprise editions.
- IBM WebSphere clusters are only supported in Network Deployment editions.
- The phrase “or later” includes all minor revisions. For example, “IBM DB2 9.1 or later” also covers IBM DB2 9.2, 9.3 and later.
- Microsoft SQL Server includes Standard and Enterprise editions.
- IBM DB2 includes WorkGroup and Enterprise editions.
- Oracle Solaris 10 8/07 (Update 4) includes all minor revisions. Oracle Solaris 10 8/07 (Update 4)(SPARC) and all updates above it are supported. For example, this also covers Oracle Solaris 10 05/08 (Update 5).
- Red Hat Enterprise Linux Server & AP 5.5 (x86_64) includes all minor revisions. Red Hat Enterprise Linux Server & AP 5.5 and all updates above it are supported. For example, this also covers Red Hat Enterprise Linux Server & AP 5.6 and later.
- For EAP 5.1.0 , you can move from EAP 5.1.0 CP1 to EAP 5.1.0 CP2. However, moving from one micro version to another is not supported. For example, moving from 5.1.0 to 5.1.1 is not supported.
- LiveCycle ES3 supports only English, French, German, and Japanese versions of the supported operating systems and applications.
LDAP Server
This table provides a summary of the LDAP servers that are supported.
Certified LDAP List |
Sun ONE 5.2 |
Sun ONE 6.3 |
Microsoft Active Directory 2003 |
Microsoft Active Directory 2008 |
IBM Tivoli Directory Server 6.0 |
Novell eDirectory 8.7.3 |
Lotus Domino v8.x |
ADAM 1.1.3790.2075 |
OpenLDAP 2.3.43-12.el5_5.3.i386 |
Email Server
This table provides a summary of the email servers that are supported.
Email Server Support |
Microsoft Exchange 2000 |
Microsoft Exchange 2003 |
Microsoft Exchange 2007 |
Microsoft Exchange 2010 |
Lotus Notes/Domino 6/7 |
SendMail (bundled with Red Hat 5) |
Novell GroupWise 6/7 |
Adobe LiveCycle Workbench 10
This table provides a summary of the operating systems, and architectures, that Adobe® LiveCycle® Workbench 10 supports.
Operating System | Architecture |
Microsoft Windows XP Professional SP3 and above | 32-bit OS |
Microsoft Windows Vista Business | 32-bit and 64-bit OS |
Microsoft Windows Vista Home (Basic/Premium) | 32-bit and 64-bit OS |
Microsoft Windows Vista Ultimate | 32-bit and 64-bit OS |
Microsoft Windows Server 2003 R1 SP2 / R2 and above | 32-bit and 64-bit OS |
Microsoft Windows 2008 Server R1/R2 | 32-bit and 64-bit OS |
Microsoft Windows 7 Home (Basic/Premium) Editions | 32-bit and 64-bit OS |
Microsoft Windows 7 Professional Edition | 32-bit and 64-bit OS |
Microsoft Windows 7 Enterprise Edition | 32-bit and 64-bit OS |
Notes:
- The target version of Eclipse and RCP is Eclipse 3.6.
- Workbench requires JRE 1.6.0_26 or later updates of JDK 1.6.
Adobe LiveCycle Designer 10
View a complete list of the minimum system requirements for Adobe® LiveCycle® Designer 10 in the Designer Release Notes.
Adobe LiveCycle PDF Generator 10
Adobe® LiveCycle® PDF Generator 10 supports only English, French, German, and Japanese versions of the supported operating systems and following applications.
Applications |
Adobe® Acrobat® X Pro |
Microsoft Office 2007, 2010 (DOC,DOCX XLS,XLSX PPT,PPTX, RTF, TXT, Microsoft Office open XML Formats) |
Microsoft Office Visio 2007, 2010 (VSD) |
Microsoft Publisher 2007, 2010 (PUB) |
Microsoft Project 2007, 2010 (MPP) |
AutoCAD 2005, 2006, 2007, 2008 (DWG, DXF, DWF) |
Adobe PageMaker® 7.0 (PMD, PM6, P65, PM) |
Adobe FrameMaker® 7.2, 8.0 (FM) |
Adobe Photoshop® CS2 (on Microsoft Windows Server 2003 R2 SP2 only) |
Corel WordPerfect 12, X4 (WPD) |
OpenOffice 3.3 (ODT, ODP, ODS, ODG, ODF, SXW, SXI, SXC, SXD, SXM) |
Notes:
- LiveCycle supports only 32-bit editions of all the above mentioned software.
- Use Acrobat for converting file types DWG, DXF, and DWF. These conversions are are supported on both 32-bit and 64-bit platforms.
- Adobe Photoshop CS3 and later versions are not supported.
- The OCR PDF (Searchable PDF) feature is supported only on Microsoft Windows.
Client Support
LiveCycle ES3 platform provides the following client software:
End user
End user interfaces include:
- Adobe® LiveCycle® Workspace 10 (Flash required)
- Adobe® LiveCycle® Reader® Extensions 10 (Flash required)
- Adobe® LiveCycle® Rights Management 10(Browser only)
- PDF Generator (Browser only)
- ContentSpace (Browser only)
- Adobe® LiveCycle® Launch Pad 10 (AIR Required)
- Admin UI (Flash Required)
- Correspondence Management (Flash Required)
This table provides a summary of the operating systems, Adobe Flash Player versions and web browsers that the LiveCycle ES3 end user clients support.
Operating System | Flash Player version | Browsers |
Microsoft Windows XP | Flash Player 11.1 or later | Windows Internet Explorer 7.0 or later |
Firefox 9 or later | ||
Microsoft Windows Vista | Flash Player 11.1 or later | Windows Internet Explorer 7.0 or later |
Firefox 9 or later | ||
Microsoft Windows Server 2003 R2 | Flash Player 11.1 or later | Windows Internet Explorer 7.0 or later |
Firefox 9 or later | ||
Microsoft Windows Server 2008 R1 | Flash Player 11.1 or later | Windows Internet Explorer 7.0 or later |
Firefox 9 or later | ||
Microsoft Windows Server 2008 R2 | Flash Player 11.1 or later | Windows Internet Explorer 8.0 or later |
Firefox 9 or later | ||
Macintosh OS X v10.5.x (PowerPC) | Flash Player 11.1 or later | Safari 4.x with latest updates |
Safari5.0.4 with latest updates | ||
Firefox 9 or later (Not for Workspace) | ||
Macintosh OS X v10.5.x/10.6.x (Intel) | Flash Player 11.1 or later | Safari 4.x with latest updates |
Safari 5.0.4 with latest updates | ||
Firefox 9 or later (Not for Workspace) | ||
Microsoft Windows 7 | Flash Player 11.1 or later | Windows Internet Explorer 8.0 or later |
Firefox 9 or later |
Notes:
- The phrase “or later” includes all major revisions. For example, “Windows Internet Explorer 7.0 or later” also covers Windows Internet Explorer 8.0 and 9.0 and 'Firefox 9 or later' also covers Firefox 4.0 and 5.0.
- The phrase “with latest updates” includes all minor revisions. For example, 'Safari 5.0.4 with latest updates' also covers Safari 5.0.5.
- Adobe LiveCycle Workspace 10 supports Internet Explorer and Firefox on Windows but only Safari on Macintosh. Safari 5.1 not supported on Mac OS X 10.6 and 10.7. For more information about Safari 5.1 compatibility with Adobe Reader, Acrobat, see http://helpx.adobe.com/x-productkb/multi/safari-5-1-incompatible-reader.html.
- Adobe LiveCycle Workspace 10 does not support Google Chrome.
Adobe LiveCycle Forms 10
This table provides a summary of the operating systems and web browsers that Adobe® LiveCycle® Forms 10 support.
Operating System | Browsers |
Microsoft Windows XP/Vista/Server 2003 R2/Server 2008 R1 | Windows Internet Explorer 7.0 or later |
Firefox 9.0 or later | |
Microsoft Windows 7/ Microsoft Windows Server 2008 R2 | Windows Internet Explorer 8.0 or later |
Firefox 9.0 or later | |
Linux/Intel | Firefox 9.0 or later |
Macintosh OS X v10.5.x (PowerPC) | Safari 4.x.x with latest updates |
Macintosh OS X v10.5.x/10.6.x (Intel) | Safari 4.x.x and Safari 5.0.4 with latest updates |
Apple iOS 4.2 (iPad) | Embedded Safari browser |
Notes:
- Forms supports Internet Explorer and Firefox on Windows but only Safari on Macintosh. For more information about safari 5.1 compatibility with Adobe Reader, Acrobat, seehttp://helpx.adobe.com/x-productkb/multi/safari-5-1-incompatible-reader.html.
Administration Console
This table provides a summary of the operating systems and web browsers that the Administration Console supports.
Operating System | Browsers |
Microsoft Windows 7 | Windows Internet Explorer 8.0 or later |
Firefox 9.0 or later | |
Microsoft Windows Server 2008 R2 | Windows Internet Explorer 8.0 or later |
Firefox 9.0 or later | |
Microsoft Windows Vista | Windows Internet Explorer 7.0 or later |
Firefox 9.0 or later | |
Microsoft Windows Server 2008 R1 | Windows Internet Explorer 7.0 or later |
Firefox 9.0 or later | |
Microsoft Windows XP | Windows Internet Explorer 7.0 or later |
Firefox 9.0 or later | |
Microsoft Windows Server 2003 R2 | Windows Internet Explorer 7.0 or later |
Firefox 9.0 or later | |
Linux/Intel | Firefox 9.0 or later |
Oracle Solaris 10 | Firefox 9.0 or later |
IBM AIX 6.1 | Firefox 3.5.8 or later |
Notes:
- The phrase “or later” includes major revisions. For example, “Windows Internet Explorer 7.0 or later” also covers Windows Internet Explorer 8.0 and 9.0 and 'Firefox 9 or later' also covers Firefox 4.0 and 5.0.
- The phrase “with latest updates” includes all minor revisions. For example, 'Safari 5.0.4 with latest updates' also covers Safari 5.0.5. Safari 5.1 not supported on Mac OS X 10.6 and 10.7.For more information about safari 5.1 compatibility with Adobe Reader, Acrobat, seehttp://helpx.adobe.com/x-productkb/multi/safari-5-1-incompatible-reader.html.
Flex SDK specific version support
LiveCycle, version 10.0.3 supports Flex SDK 4.1, 4.5 and, 4.6.
Correspondence Management Solution, version 10.0.3 supports only Flex SDK 4.5
Adobe® LiveCycle® Workspace 10 Supports only Flex SDK 3.4.1.
Note:Flex SDK 3.4.1 is available on LiveCycle ES3 DVD. Navigate to <LiveCycle ES3 DVD>additionalFlex_SDKflex3flex_sdk_3.zip folder for Flex SDK 3.4.1.
Note:Flex SDK 3.4.1 is available on LiveCycle ES3 DVD. Navigate to <LiveCycle ES3 DVD>additionalFlex_SDKflex3flex_sdk_3.zip folder for Flex SDK 3.4.1.
Adobe AIR specific version support
LiveCycle, version 10.0.3 supports Adobe AIR 3.1.
Acrobat/Reader support
This table provides a summary of the Adobe Acrobat and Adobe Reader versions supported LiveCycle ES3.
Tasks | Acrobat/Adobe Reader version |
Form filling and form submission | 8.0 or later |
9.0 or later | |
10.0 or later (Recommended) | |
Workspace | 8.0 or later |
9.0 or later | |
10.0 or later (Recommended) |
Notes:
The phrase “or later” includes major revisions. For example, “Acrobat 8.0 or later” also covers Acrobat 8.1 and 8.2 and so on.
Change History
Last updated October 18, 2016
- Added supported version of Flex SDK for LiveCycle Workspace.
- Updated supported version of Creative Suite for LiveCycle ES3.
- Added Microsoft SQL Server 2008 in the list for supported Databases.
- Added Adobe LiveCycle does not support Google Chrome.
- Changed supported version of JBoss Enterprise Application Platform from EAP 5.1 to EAP 5.1.0.
- Added supported editions of Microsoft Windows Server 2003 and Windows Server 2008.
- Added support for Windows XP the list of supported end user clients.
- Added LiveCycle ES3 supports only Oracle Real Application Clusters (RAC).
- Added the OCR PDF (searchable PDF) feature is supported only on Microsoft Windows.
- Added IBM WebSphere 8.0.0.2 and Oracle WebLogic 11g (10.3.6) in the list of supported application servers.
- Updated supported vesion of Oracle Database 11g Release 1 JDBC driver.
- Added IBM WebSphere 8.0.0.3 and IBM WebSphere Java SDK 1.6 SR1 FP1.
Adobe LiveCycle ES3, version 10.0.4 -- October 18, 2016