Adobe LiveCycle ES

Version 8.0.1.3

Release Notes 

September 2008

Edition 1.4

Copyright 2008 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

Installation Issues

Upgrade Issues

Administration Issues

Development Issues

Performance Issues

Quick Starts and Samples Issues

End User Issues

The Documentation Set

Additional Licenses and Copyrights

System Requirements

LiveCycle ES requires that you have the following software:

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.

Note: Multiple versions of .NET can exist concurrently on the same computer without overwriting each other.

Back to Contents

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.

Back to Contents

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.

Back to Contents

Canceling LiveCycle Workbench ES installation does not cancel LiveCycle Designer ES installation

During the installation of Adobe 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.

Back to Contents

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 Files\Common Files\Install Shield\Universal\Adobe\LC8
  • (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 Files\Common Files\Install Shield\Universal\Adobe\LC8\Gen1): 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_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\eb6e469e8f49062609d2f6082e34d944-1213923530

Back to Contents

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.

Back to Contents

Oracle 10g database drivers are required for service container deployment

You must perform the following steps for the successful service container deployment of Oracle® 9i or 10g:

  1. Create an Oracle database with the default character set AL32UTF8 and the national character set UTF-8. (See “Creating an Oracle database” in Preparing to Install LiveCycle ES.)
  2. Select the Oracle 10g database drivers when configuring the database connectivity for your application server. (See “Configuring Oracle database connectivity” in Installing and Deploying LiveCycle ES for your application server.)
  3. Bootstrap the database using the LiveCycle ES 8.0.1 SP1 build.

Back to Contents

LiveCycle Configuration Manager

Component deployment fails on Windows if Global Document Storage directory is at the drive root

Component deployment fails on a Windows environment if the Global Document Storage (GDS) directory is directly at the root of the drive (for example, D:\).

For GDS, you must make sure that the directory is not located at the root of the drive but is located in a subdirectory. For example, the directory should be D:\GDS and not simply D:\.

Back to Contents

LiveCycle Configuration Manager times out while deploying the EAR files after applying LiveCycle ES Service Pack 1

After applying LiveCycle ES Service Pack 1, when you are using Adobe LiveCycle Configuration Manager to configure and deploy the EAR files LiveCycle Configuration Manager may time out while deploying the files. This problem can occur if you are running BEA WebLogic Server® on Sun™ Solaris™ or IBM® WebSphere® on IBM AIX®.

If LiveCycle Configuration Manager times out while deploying the EAR files, you must undeploy the current EAR files, restart the application server, and run LiveCycle Configuration Manager again to deploy the files. The following EAR files must be undeployed from the application server:

  • WebLogic:
    • adobe-livecycle-native-weblogic-[OS].ear
    • adobe-livecycle-weblogic.ear
  • WebSphere
    • adobe-livecycle-native-websphere-[OS].ear
    • adobe-livecycle-websphere.ear
  • WebLogic and WebSphere
    • adobe-workspace-client.ear (only if you are installing or patching Adobe LiveCycle Process Management ES)

Complete these steps to ensure that the LiveCycle ES EAR files are deployed:

  1. Undeploy the LiveCycle ES EAR files from the application server using the application server's administration console. (See Installing and Deploying LiveCycle ES for WebLogic or Installing and Deploying LiveCycle ES for WebSphere.)
  2. Restart the application server.
  3. Run LiveCycle Configuration Manager to deploy the Service Pack 1 EAR files. (See the LiveCycle ES Service Pack 1 Readme, which is located on the page where you downloaded the Service Pack.)

Back to Contents

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.

Back to Contents

(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.

Back to Contents

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.

Back to Contents

(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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

(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

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.

Back to Contents

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.)

Back to Contents

(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.

Back to Contents

Cannot automatically start LiveCycle Configuration Manager from LiveCycle ES installer

If you select the Launch LiveCycle Configuration Manager option in the LiveCycle ES installer, LiveCycle Configuration Manager fails to start. You must manually start LiveCycle Configuration Manager by navigating to the [LiveCycleES_root]/configurationManager/bin directory and running either the ConfigurationManager.bat or ./ConfigurationManager.sh file (depending on your operating system).

Back to Contents

Adding Process Management ES or Business Activity Monitoring to an existing Forms ES environment requires uninstalling LiveCycle ES

When installing either Process Management ES or Business Activity Monitoring in an existing Forms ES environment, the appropriate EAR files do not install properly. To avoid this problem, you must uninstall LiveCycles ES, and then install all of the solution components at the same time.

Back to Contents

JBoss® Installation Issues

LiveCycle PDF Generator ES or LiveCycle Business Activity Monitoring on Turnkey JBoss

With the Turnkey JBoss installer, if you install Adobe LiveCycle PDF Generator ES and select the Native File Conversion functionality, or if you use LiveCycle Business Activity Monitoring, the JVM option for UTF8 encoding is set incorrectly. You must correct this issue to ensure that LiveCycle PDF Generator ES functions correctly.

After you complete the LiveCycle PDF Generator ES 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.

Back to Contents

Incorrect parameter in the adobe-component-ext.properties file

The LiveCycle ES JBoss Turnkey installation provides a sample adobe-component-ext.properties file. This file contains a comment with an example configuration:

For example, the following System parameter would be passed in in order to expand the class-path of the Bean Shell DSC to include a dependency.jar: -Dcom.adobe.idp.dsc.sample.bean_shell.beanShellComponent_1.0.ext=C://dev/dependency.jar.

Do not use the –D option in the above example. The corrected example is:

For example, the following System parameter would be passed in in order to expand the class-path of the Bean Shell DSC to include a dependency.jar: com.adobe.idp.dsc.sample.bean_shell.beanShellComponent_1.0.ext=C://dev/dependency.jar”

WebSphere Installation Issues

Deployment issue with WebSphere on French, German, or Japanese Windows operating system

If you are deploying LiveCycle ES components on a localized Windows operating system, an issue occurs where the LiveCycle Configuration Manager deployment process reaches approximately 16% completion and then the adobe-livecycle-websphere.ear fails to deploy. There are two known workarounds:

  • Use LiveCycle Configuration Manager to configure LiveCycle ES, but not to deploy the EAR file. And then, remove the –Dfile.encoding=utf8 JVM argument and manually deploy the EAR file. Once complete, reset the JVM argument to –Dfile.encoding=utf8. Use LiveCycle Configuration Manager to configure LiveCycle ES, but not to deploy the EAR file. And then, remove the –Dfile.encoding=utf8 JVM argument and manually deploy the EAR file. Once complete, reset the JVM argument to –Dfile.encoding=utf8. After completing this manual update, you can deploy other EAR files manually using the WebSphere Admin Console, however, adobe-livecycle-websphere.ear will fail to redeploy.
  • Contact IBM to obtain the FixPack that addresses the issue with their deployer with a localized Windows operating system when the –Dfile.encoding=utf8 JVM argument is set.
    •

Back to Contents

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 (it can be safely ignored):

[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.

Back to Contents

Deployment of LiveCycle ES EAR files causes many warnings

A warning similar to the following may be recorded many times in the System.out log during the deployment of the LiveCycle ES EAR files (it can be safely ignored):

ADMA0115W: Resource assignment of name jms/POFSchemaTopic and type javax.jms.Topic, with JNDI name topic/adobe_POFSchemaTopic is not found within scope of module Platform Bootstrapper with URI adobe-bootstrapper.war,WEB-INF/web.xml deployed to target WebSphere:cell=ap-aix4Node01Cell,node=ap-aix4Node01,server=server1.

Back to Contents

Correcting a WebSphere/Solaris out of memory error

If you are deploying LiveCycle ES to an IBM WebSphere Application Server on a Sun Solaris platform, WebSphere may generate the following memory error:

[9/27/07 10:00:21:292 PDT] 00000031 DeployEJBTask I ADMA0158I: [EJBDeploy] Error executing deployment: java.lang.OutOfMemoryError. Error is PermGen space.
[9/27/07 10:00:21:294 PDT] 00000031 DeployEJBTask I ADMA0158I: [EJBDeploy] java.lang.OutOfMemoryError: PermGen space

To correct this issue, modify the [WebSphere root]/deploytool/itp/ejbdeploy.sh script and change the Heap Size to 1024 MB and the MaxPerm size to 256m. Restart the application server for these changes to take effect.

Back to Contents

WebLogic Installation Issues

Broken link to JRockit JDK download site

The section "Installing the J2SE SDK" (for WebLogic Server) in the Preparing to Install LiveCycle ES guide provides a link to the BEA product site in order to obtain the JDK required by WebLogic. This link now returns a "File not found" error.

To obtain the correct version of the JRockit SDK for LiveCycle ES, that being JRockit 5.0 R26.4 CR302700 (for use with WLS 9.2 MP1)
Java Development Kit, contact BEA eSupport for more information.

Back to Contents

 

Database user name restrictions for Oracle databases

When using WebLogic and an Oracle database, ensure that the database user name does not have a number as the first character, nor a hyphen (-) within the user name. The database will not bootstrap correctly if the database user name contains a number as the first character or when the hyphen is part of the user name.

Back to Contents

 

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).

Upgrading from Microsoft SQL Server 2000 to SQL Server 2005

Instructions for upgrading Microsoft SQL Server 2000 to SQL Server 2005 are available in the technical article "Upgrading SQL Server 2000 to SQL Server 2005". The article is available from the LiveCycle Knowledge Center at the following URL: http://www.adobe.com/go/kb403166

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

Form data mappings properties are incorrect for upgraded User actions

When you are upgrading processes using the Process Upgrade Tool and the User operations that are based on the LiveCycle 7.x User QPAC are replaced with Assign Task operations (User service), the Input Form Variable property of the Assign Task operation is not configured correctly. The property is configured with the name of the workflow variable that was used for the Input Variable property of the LiveCycle 7.x User action. However, the Input Form Variable property requires values in the form of an XPath expression.

After upgrading to LiveCycle ES, for each Assign Task operation, you must change the value of the Input Form Variable property to an XPath expression that evaluates to the variable that represents the form to use.

To configure the Input Form Variable property:

  1. On the process map, click the Assign Task operation.
  2. In the Properties view, click Form Data Mappings.
  3. Click the "..." button for the Input Form Variable property.
  4. Use XPath Builder to create the expression that evaluates to the variable that represents the form you are using.

Back to Contents

LiveCycle Form Manager 7.x task assignment and reminder emails are not redirected after upgrading to LiveCycle Workspace ES

After upgrading LiveCycle Forms 7.x to LiveCycle Workspace ES, any links in task assignment or reminder emails that have already been sent to you do not redirect to the correct location in LiveCycle ES. Links in emails that were sent out by LiveCycle 7.x cannot be clicked. You must go directly to your task list in Workspace ES to see the task assignment or to view archived items. New emails sent by Workspace ES contain valid links (including those links for processes created in LiveCycle 7.x and running in LiveCycle ES).

Additional fixes that are not listed here may also be provided. For information about how to obtain the fixes, contact Adobe Customer Support.

Back to Contents

Installation and Configuration

LiveCycle ES services are inactive after applying Service Pack 2

There is a known issue that some LiveCycle ES services move to an inactive state after updating the LiveCycle ES database with Service Pack 2. To reactivate your services, open LiveCycle Administration Console, go to Home > Services > Archive Administration > Service Management  and browse to each page of services listed.

Back to Contents

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:

  1. After installing LiveCycle ES, navigate to the [LiveCycleES root]/configurationManager/bin directory and open the ConfigurationManager.bat file in a text editor.
  2. Find the line set JAVA_OPTS=-Xms128m -Xmx512m and change 512 to 784 so that the line reads:
    set JAVA_OPTS=-Xms128m -Xmx784m
  3. Save and close the ConfigurationManager.bat file.
  4. Double-click the ConfigurationManager.bat file to start LiveCycle Configuration Manager to begin the upgrade

Back to Contents

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.

Back to Contents

Additional data source required for LiveCycle Rights Management ES

During your preparation to install or upgrade LiveCycle ES, when you are configuring the data sources on the application server, if you are installing or upgrading to Adobe LiveCycle Rights Management ES, you must include the EDC_DS data source in the configuration. The instructions for adding this data source are provided in the "Configuring JBoss Application Server" section in the Preparing to Upgrade to LiveCycle ES guide.

For information about configuring the EDC_DS data source for WebSphere, see the "Manually Configuring WebSphere" section in the Upgrading to LiveCycle ES for WebSphere guide.

For information about configuring the EDC_DS data source for WebLogic, see the "Manually Configuring WebLogic" section in the Upgrading to LiveCycle ES for WebLogic guide.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

(WebSphere) Exception occurs during upgrade when incorrect JNDI port provided

If you enter an invalid JNDI port in LiveCycle Configuration Manager, the following exception occurs during the migrating critical data phase of the upgrade:

javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://localhost:2809".

When this exception occurs, you must restart LiveCycle Configuration Manager and enter the correct JNDI port. You cannot navigate back to the JNDI port input screen using the Back button.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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 Adobe 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()

Back to Content

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.

Back to Contents

LiveCycle Workbench ES

FTP over SSH is not supported by Workbench ES process invocations

When using the FTP service in a Workbench ES process to connect to an SFTP server (that is, FTP over SSH), the following error occurs:

Caused by: com.adobe.idp.dsc.ftp.FTPConnectionException: Cannot login to FTP Server at com.adobe.idp.dsc.ftp.FTPService.connectAndLogin(FTPService.java:150)

Currently, FTP over SSH is not supported by Workbench ES processes and there is no workaround.

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:

  1. Open [install location]\Adobe\LiveCycle ES\Workbench ES\Workbench\workbench.ini in a text editor.
  2. Add the following text in a new line at the bottom of the document:

    3. -Dcom.adobe.process.unsupported.componentinstall.usingbytes=true

  3. Save workbench.ini

Back to Contents

Enabling and patching upgraded QPACs in Workbench ES on WebSphere

During the Workbench ES installation, if you selected the Enable Workbench To View, Edit and Upgrade LiveCycle 7 Processes option, and your target application server is WebSphere, you need to perform the following additional tasks.

Note: If 7.x QPACs are already running successfully in your WebSphere environment and you only need to patch them, you can skip the first task below and go directly to the "To patch 7.x QPACs on WebSphere" task.

To enable LiveCycle 7 processes for WebSphere:

  1. Obtain the Application Client software for Windows from the following location:
    http://www14.software.ibm.com/webapp/download/search.jsp?go=y&rs=was60_trial&S_TACT=105AGX28&S_CMP=DLMAIN
  2. Install the Application Client software in the default directory: C:\Program Files\IBM\WebSphere\AppClient
  3. Obtain IBM JRE for Eclipse from the following location: http://www.ibm.com/developerworks/java/jdk/eclipse
  4. Install IBM JRE for Eclipse in the default directory: C:\DownloadDirectory\
  5. Start Workbench ES in a command line as follows (entered as a single line):

    workbench.exe -vm C:/DownloadDirector/eclipseDevelopmentPackage/ibm_sdk50/jre/bin/java.exe

There is a known issue that patching upgraded 7.x QPACs from the Workbench ES Components view fails on WebSphere. This is due to WebSphere requiring the IBM JRE instead of the Sun JRE that installs with Workbench ES. In order to patch 7.x QPACs successfully, you must perform the following task:

To patch 7.x QPACs on WebSphere:

  1. Start Workbench ES using the included Sun JRE.
  2. Connect to Workbench ES using a SOAP connection.
  3. Patch the 7.x QPACs from the Workbench ES Components view.
  4. Log out of Workbench ES and shut down the application.
  5. Locate and open the workbench.ini file in a text editor. (This file resides in the same install directory as the workbench.exe file.)
  6. In the workbench.ini file, remove the following line, and then save and close the file:
    -XX:MinHeapFreeRatio=40
    Note: You must remove this line entirely because this option is not recognized by the IBM JRE and causes Workbench ES to fail during startup, and then generate an error message.

  7. Revert to running Workbench ES using the IBM JRE after completing the upgrade.

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.

Back to Contents

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.

Back to Contents

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:

  1. Using the Oracle account, log in to the server where the LiveCycle database is stored.
  2. Delete all rows in tb_bam_calendar by using the following database command:
    delete from tb_bam_calendar
  3. From BAM Workbench, navigate to Workbench > Application Workbench > Events.
  4. 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.
  5. 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.
  6. 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.
  7. Refresh the BAM Dashboards to verify the data is correct.

Back to Contents

Upgrading Policy Server 7.x issues

Offline access of protected documents after upgrade from LiveCycle 7.x (1540945 - Heather)

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:

  1. Obtain the LiveCycle 7.x patch for determining the encoding method. Contact Adobe Customer Support.
  2. Apply the patch to your LiveCycle Policy Server installation by following the instructions included with the patch.
  3. Log in to LiveCycle Policy Server as any valid user.
  4. 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:

  1. Log into Adobe LiveCycle Administration Console and click Services > LiveCycle Rights Management ES > Configuration > Manual Configuration.
  2. Export the config.xml file and open it in a text editor.
  3. 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.)
  4. Save the config.xml file and import it using the Manual Configuration page in LiveCycle Administration Console.
  5. In LiveCycle Administration Console click Services > Right Managemenet ES > Configuration > Key Management.
  6. Click Roll Over Keys Now.

Back to Contents

Administration Issues

General

Cannot log into LiveCycle Administration Console or Workbench ES after the server is left idling

If the JBoss server is kept running for a period of time exceeding the wait_timeout on the MySQL database, the database server closes the connections from the client (JBoss server) and all of the authenications will fail. This issue can occur with the LiveCycle Administration Console, Workbench ES, and Workspace ES UI when using the JBoss/MySQL Turnkey install. To correct this issue, perform the following steps:

    1. Open the adobe-ds.xml and mysql-ds.xml files under the C:\server\all\deploy\ folder in a text editor.
    2. Add the following XML code to each file:

    <new-connection-sql>SELECT count(*) from DUAL</new-connection-sql>
    <check-valid-connection-sql>SELECT count(*) from DUAL</check-valid-connection-sql>
    <exception-sorter-class-name>com.mysql.jdbc.integration.jboss.ExtendedMysqlExceptionSorter</exception-sorter-class-name>
    <valid-connection-checker-class-name>com.mysql.jdbc.integration.jboss.MysqlValidConnectionChecker</valid-connection-checker-class-name>

    3. Save the files and restart JBoss.

    Back to Contents

Archive Administration

LiveCycle ES archive files may not be backward compatible

There is a known issue that LiveCycle ES archive (LCA) files from a future release are not necessarily backward compatible. While it may be possible to view and import LCA files from a future release of LiveCycle ES (for example, a preview release), doing so is not supported and may result in aberrant behavior.

Back to Contents

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.

Back to Contents

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.

Back to Contents

Backup and Restore

Backing up your LiveCycle ES environment

Information for backing up and restoring your LiveCycle ES environment is available from a number of sources.

The "LiveCycle ES database and GDS backup and recovery" document available at http://www.adobe.com/go/kb403016 describes how to back up and recover the LiveCycle ES application data.

The following knowledgebase articles provide guidance to basic database features for the backup and recovery of data:

"Oracle Backup and Recovery for LiveCycle ES"
"MySQL Backup and Recovery for LiveCycle ES"
"SQL Server Backup and Recovery for LiveCycle ES"
"DB2 Backup and Recovery for LiveCycle ES"

Note: These articles are not intended as all-inclusive technical guides of a specific vendor's database backup and recovery feature. They outline commands that are required to create a reliable database backup strategy for your LiveCycle ES application data.

Back to Contents

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.

Back to Contents

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

Back to Contents

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.

Back to Contents

(DB2) Default USERSPACE1 tablespace page size too small

The default page size (4 KB) of the DB2 tablespace USERSPACE1 is insufficient for LiveCycle ES. The database administrator must increase the page size to 8 KB:

  1. Define a buffer pool with an 8 KB page size.
  2. Create a new System Temporary tablespace using the 8KB buffer pool.
  3. Drop the USERSPACE1 tablespace.
  4. Re-create the USERSPACE1 tablespace using the new 8 KB buffer pool.

Back to Contents

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.

Back to Contents

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.

Back to Contents

Hardened Environments

LiveCycle ES dependencies on a hardened UNIX environment

The following information is intended to help you plan for a LiveCycle ES deployment in a UNIX environment. The ConvertPdf service that is part of LiveCycle ES 8.0.1 requires the following minimum system libraries:

Linux: Kernel 2.6

libpthread.so.0

libdl.so.2

libstdc++.so.6

/libstdc++.so.6 (0x00111000)

libm.so.6

libgcc_s.so.1

libgcc_s.so.1 (0x001f0000)

libc.so.6

/lib/ld-linux.so.2

Solaris 8

libintl.so.1

libpthread.so.1

libsocket.so.1

libnsl.so.1

libdl.so.1

libstdc++.so.5

solaris8/lib//libstdc++.so.5

libm.so.1

libgcc_s.so.1

solaris8/lib//libgcc_s.so.1

libc.so.1

libmp.so.2

libthread.so.1

Aix 5.3

/usr/lib/libpthread.a(shr_comm.o)

/usr/lib/libpthread.a(shr_xpg5.o)

/usr/lib/libC.a(shr.o)

/usr/lib/libC.a(shr2.o)

/usr/lib/libC.a(shr3.o)

/usr/lib/libC.a(ansi_32.o)

/usr/lib/libc.a(shr.o)

/usr/lib/librtl.a(shr.o)

/usr/lib/libpthreads.a(shr_comm.o)

/usr/lib/libc_r.a(shr.o)

/usr/lib/libC.a(ansicore_32.o)

/usr/lib/libC.a(shrcore.o)

/usr/lib/libcrypt.a(shr.o)

Back to Contents

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.

Back to Contents

Drillback limitation

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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:

  1. Import the adobeimport_oracle.jar.
  2. Go to Business Activity Monitoring Workbench.
  3. Go to Events and disable the Adobe_Event.
  4. Edit Adobe_Event.
  5. In the Configure Event - JDBC Source window, update the JDBC query by putting descriptor in double quotes. For example:

    select uuid,major_version, minor_version, “descriptor” ,state, service_uuid,component_oid
    update_time, create_time from tb_sc_service_configuration

  6. Click Resubmit Query.
  7. Under the Polling tab make sure that update_time is selected for “Incrementing Field.”
  8. Click Save Event.
  9. Enable the Event. Enable all dependencies.

Note: When you enable the Adobe EVent, errors will occur on the console the very first time. Ignore the errors.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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:

  • 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.”

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

Removing LiveCycle ES Archives (LCAs) with assets stored in IBM FileNet Content Manager

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.

Back to Contents

Livecycle Output ES

Need to restart service after changing cache settings

When you change the cache settings for LiveCycle Forms ES or Adobe 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:

  1. In LiveCycle Administration Console, select Services > Archive Administration > Service Management.
  2. Select the service and click Stop.
  3. When the State for the service is "Stopped", click Start.

Back to Contents

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 \\server\queue 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.

Back to Contents

LiveCycle PDF Generator ES

Converting Microsoft Excel files that contain add-ins to PDF

When PDF Generator ES converts an Excel file that contains add-ins, some fields are not converted properly. Specifically, result fields containing add-in calculations do not appear in the PDF.

To include the results of the add-in calculations, you must create and use a custom PDF Generator ES configuration file. Perform the following procedure to create and use a custom configuration file for Excel add-ins:

1. Open the LiveCycle Administration Console and click Services > LiveCycle PDF Generator ES > Configuration Files > Export Configuration.

2. Click Download entire configuration, click Download, and then save the configuration file.

3. Open the saved configuration XML file in a text editor.

4. Search under the <settings default="true" name="Standard" readonly="true"> tag for the <AddIns> tag, and replace the <AddIns> tag with the tags <AddIns>[path to add-in]</AddIns>. If the </AddIns> tag is not present, insert the tags <AddIns>[path to add-in]</AddIns> anywhere before the </MSExcel> tag.

Note: Replace the placeholder [path to add-in] with the full path to all add-ins that must be included, separated by semi-colons. For example:

<AddIns>C:/Program Files/Microsoft Office/Office11/Library/Analysis/ATPVBAEN.XLA;C:/Program Files/Microsoft Office/Office11/Library/Analysis/FUNCRES.XLA;C:/Program Files/Microsoft Office/Office11/Library/Analysis/PROCDB.XLA;C:/Program Files/Microsoft Office/Office11/Library/Analysis/Analys32.xll</AddIns>

5. Save the edited configuration file.

6. In the LiveCycle Administration Console, click Services > LiveCycle PDF Generator ES > Configuration Files > Import Configuration.

7. Click Import an existing configuration file, click Browse, navigate to the edited configuration file, and then click Import.

Note: Ensure that you configure File Type Settings = Standard when you convert Microsoft Excel files that contain add-ins to PDF. (See the LiveCycle ES Administration Console Help topic “Creating PDF Files”.)

Back to Contents

 

PDF Generator ES HTMLtoPDF does not show double-byte (Japanese) characters in the resulting PDF document

This service pack provides a fix for the issue where the HTMLtoPDF conversion in PDF Generator ES running on Solaris 10 did not show double-byte (Japanese) characters in the resulting PDF. To fully implement the fix, you must ensure that the double-byte fonts are present on the server running PDF Generator ES and are properly mapped in the deployed LiveCycle ES JAR file.

To implement the fix:

  1. Copy the Unicode font to one of the following directories, as appropriate for your deployment:

      2. •(Windows)
      [Windows root]\windows\fonts
      [Windows root]\winnt\fonts

      •(Unix)
      /usr/X/lib/X11/fonts/TrueType
      /usr/openwin/lib/X11/fonts/TrueType
      /usr/share/fonts/default/TrueType
      /usr/X11R6/lib/X11/fonts/ttf
      /usr/X11R6/lib/X11/fonts/truetype
      /usr/X11R6/lib/X11/fonts/TrueType
      /usr/X11R6/lib/X11/fonts/TTF
      /Users/cfqauser/Library/Fonts
      /System/Library/Fonts
      /Library/Fonts
      /Users/[User Name]/Library/Fonts where [User Name] is the name of the User
      [Java_HOME]/lib/fonts where [Java_HOME] is the location of the JRE

  2. Restart the server and run an HTMLtoPDF conversion. Open the application server log file, and then search the list of fonts logged from the HTMLtoPDF conversion performed in step 2 to determine the font name you must map. Unpack the [LiveCycle8.0 root]/adobe-generatepdf-dsc.jar file.
  3. Locate and open the cffont.properties file in a text editor.
  4. In the comma separated list of Java font names, add a map to your Unicode system font for each font type. For example, where kochi mincho is the name of your Unicode system font, add the font in the following manner:
    dialog=Arial, Helvetica, kochi mincho dialog.bold=Arial Bold, Helvetica-Bold, kochi mincho

    Note: To embed the font in the generated PDF files, you must set the embedFonts property in the cffont.properties file to true (default is false).

  5. Save and close the properties file.

    Note: On a Japanese operating system, you must specify the font mapping in the cffont.properties.ja file as well as the standard cffont.properties. The cffont.properties.ja file takes precedence over the standard cffont.properties file.

  6. Repackage and redeploy the adobe-generatepdf-dsc.jar file.

Back to Contents

Configuring PDF Generator ES to convert Microsoft Office files to PDF format

On some LiveCycle ES servers, a DCOM permission policy must be modified to use PDF Generator ES to convert Microsoft Office application files successfully. Otherwise, the following error is
returned:

INFO [STOUT] com.jniwrapper.win32.com.ComException: COM object method returns error code:
0x80004005; E_FAIL (Unspecified error)

Microsoft has documented the steps for modifying the policy in the knowledgebase article at http://support.microsoft.com/kb/288367.

Back to Contents

Anonymous access to LiveCycle PDF Generator ES not permitted

It is a known issue that users can no longer access LiveCycle PDF Generator ES anonymously.

Due to the security restrictions in LiveCycle ES, anonymous access to all LiveCycle services has been disabled. It is, therefore, mandatory for all users to log in to http://[hostname]:[port]/adminui before they can access PDF Generator ES functionality.

The easiest way for an organization to set up access to the PDF Generator ES service for all corporate users is to configure LiveCycle User Management to synchronize all the LDAP user accounts and assign the Administration Console User and PDFG User roles to all users.

This configuration will enable users to log in to http://[hostname]:[port]/adminui using their LDAP credentials and access the PDF Generator ES functionality.

Note: Users configured in this manner will not have access to the PDF conversion settings page.

Back to Contents

Adding native support for Microsoft Publisher to PDF Generator ES

The following instructions enable native support for Microsoft Publisher in PDF Generator ES.

1. Start LiveCycle Administration Console by entering the URL http://[host name]:[port]/adminui in a web browser.
2. Navigate to Home > Services > LiveCycle PDF Generator ES > Configuration > Export Configuration.
3. Select Download Entire Configuration and click Download.
4. Save the native2configpdf.xml file and then open it in an XML editor.
5. Locate the <filetype-settings>/<settings default="false" name="Standard OCR" readonly="true"> element and insert the following text within this element as the last entry: 

<MSPublisher extensions="pub">
     <method>PDFMaker</method>
     <PDFMaker createBookmarks="true" createDocInfo="true" createLinks="true" preserveSpotColor="true" preserveTransparency="true" printCropMarks="true"/>
</MSPublisher>

6. Locate the <filetype-settings>/<settings default="true" name="Standard" readonly="true"> element and insert the same text from step 5 within this element as the last entry.
7. Save and close the XML file.
8. Navigate to Home > Services > LiveCycle PDF Generator ES > Configuration > Import Configuration.
9. Select Import an existing configuration file, browse to the XML file you have updated, and click Import.

Back to Contents

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.

Back to Contents

"Failed to delete a directory" message may be displayed in the server log when running conversions to PDF format

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~1\ADMINI~1\LOCALS~1\Temp\AdobeDocumentStorage\local\removeOn2006Y08M31D18h16m15s.1157028375000" after 60 attempts. The file(s) under this directory could still be locked. If this message is consistent, consider restarting the server."

Back to Contents

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.

Back to Contents

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:

  1. In LiveCycle Administration Console, click Services > LiveCycle PDF Generator ES > Configuration Files > Export Configuration.
  2. Select Download Entire Configuration and click Download.
  3. In a text editor, open the downloaded file and, under the AutoCAD tag, within the PDFMaker tag, add this text: convertAllPages="true".
  4. In LiveCycle Administration Console, click Services > LiveCycle PDF Generator ES > Configuration Files > Import Configuration.
  5. Select Import An Existing Configuration File and specify the updated file.
  6. Click Import.

Any AutoCAD files converted using the modified configuration file will have all of the layers converted.

Back to Contents

LiveCycle PDF Generator ES on clustered JBoss web application servers may fail at heavy loads

If running at heavy loads, LiveCycle PDF Generator ES running on clustered JBoss web application servers may fail. Error messages similar to the following messages will appear:

WARN [com.adobe.workflow.AWS] ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error.
Caused by: com.adobe.idp.jobmanager.common.JobManagerException: java.lang.RuntimeException: JobManager:getQueueConnectionFactory():Error:
Caused by: javax.naming.NameNotFoundException: adobe_JmsQueueXA not bound

There is no known workaround.

%F, %E parameters not respected for multiple PDF files attached using an email endpoint

If you are generating and attaching multiple PDF files to an email using an email endpoint and the %F, %E parameters to establish the naming convention, the output filenames and extensions will not match the input files. This is a known issue with no workaround and only affects multiple file requests.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

LiveCycle Reader Extensions ES

Online commenting for Adobe Reader web browser plug-in

To enable the Comment and Markup toolbar in a PDF file that is viewed using the Adobe Reader web browser plug-in, there must be a collaboration backend in place, such as a review server. If there is no collaboration backend available, you must save the PDF fle to your computer, review and mark up the file in Adobe Reader, and send it back to the originator.

If online commenting is required in a non-collaborative environment, contact Adobe Support for more information.

Back to Contents

Need to increase timeout values to prevent jobs from failing

When working on a large number of PDF files in Adobe 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 > Import and 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.

Back to Contents

LiveCycle Rights Management ES

Incorrect login page appears

In Acrobat, when you select Secure > Adobe Rights Management (or Adobe Policy Server) > Manage My Account, a login page for LiveCycle Administration Console appears, rather than a login page for the LiveCycle Rights Management ES end-user web application. To access the LiveCycle Rights Management ES end-user web application, you must manually enter this URL in a web browser: http://[server]:[port]/edc/Login.do

Back to Contents

Securing documents with anonymous user policies

There is a known issue that creating policies using iterate or publishAs as an anonymous user will return error 1281 E_INVALID_ARG when used to secure a document. To fix this issue you must call requestAccess before iterate or publishAs.

Back to Contents

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.

Back to Contents

SSL Certificates with DSA keys are not supported

SSL ceritificates with DSA keys are not supported. You must use SSL certificates with RSA keys instead, since they are supported on all platforms.

Back to Contents

LiveCycle Workspace ES

Process Fields object displays incorrectly on forms displayed in LiveCycle Workspace ES

Forms created using LiveCycle Designer ES that contain the Process Fields objects (available from the Custom category of the Object Library palette) do not render correctly in LiveCycle Workspace ES. If the form connects to a WSDL data source, and an object exists on the form that contains scripting on its form:ready event, then you must import the WSDL data using the following script without forcing a remerging of the form itself:

  • xfa.connectionSet.DataConnection.execute(0); //JavaScript
  • xfa.connectionSet.DataConnection.execute(0) //FormCalc

If you choose to remerge the form and WSDL data, then the drop-down list named AWS_ACTION displays incorrectly on the rendered form in LiveCycle Workspace ES.

Back to Contents

Error occurs when 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.

Back to Contents

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. Unable to complete request. The template you are importing already exists. See error log for more detail."

Back to Contents

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.

Back to Contents

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.

Back to Contents

Updating an HSM credential

To update an HSM credential, you must delete the existing credential and then add the new HSM credential.

Back to Contents

User Management

Creating user accounts with identical user names and passwords

LiveCycle ES cannot differentiate between user accounts that have identical user names and passwords but that belong to different domains. To avoid this problem, do not create accounts that have the same user ID on multiple domains.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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."  

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

Attempting to delete DefaultDom domain in User Management gives contradictory results

You 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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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"

Back to Contents

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

  1. Specify a pattern for Exclude File Pattern, such as temp*.ps.
  2. Copy files that begin with temp (for example, temp1.ps) to the watched folder.
  3. 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. 

Back to Contents

Staging directory not cleaned out when Preserve Folder Name set to nul

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.

Back to Contents

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.

Back to Contents

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:

- 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.

Back to Contents

Development Issues

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>

Back to Contents

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.

Back to Contents

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).

Back to Contents

Convert PDF service

Tiff image conversion fails when the color space value is grayscale with any value for GrayCompression

When you invoke the com.adobe.livecycle.convertpdfservice.client.ConvertPdfServiceClient.toImage() method, an exception is generated if the toImageOptionsSpec parameter specifies a color space value of grayscale and any value for the grayscale compression.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

Forms service

Form designs with server-side calculations rendered to PDF forms cannot be certified using digital signatures in Acrobat

Any form designs with server-side calculations that are rendered to PDF forms using the Render PDF Form operation (Forms service) in LiveCycle ES SP2 cannot be certified using digital signatures in Acrobat 8.0, 8.1, or 8.1.1. When a form design contains server-side calculations (using FormCalc or JavaScript), a <formState> XDP packet is produced when the form design is rendered to a PDF form using the Forms service. Acrobat 8.0, 8.1, and 8.1.1 disallow certification for PDF forms that contain a <formState> packet, therefore, the rendered PDF form cannot be certified using digital signatures.

This problem does not occur when using Acrobat 7.x to certify such forms.

Back to Contents

LiveCycle Workspace ES invalidates certifying signatures in an XDP form based workflow when using standard process fields

When Adobe XML forms (XFA based PDF) are used in processes that involve users with Workspace ES, the forms invalidate certified signatures.This is because when Workspace ES loads a static PDF, it breaks certification. If you want to certify the form, you need to create a dynamic PDF.

If you have Acrobat 7.0 and later, you must use the default Render PDF Form process and render PDF options and create a dynamic XFA-based PDF.

Caution: After you create a new process version and activate it, all of the variables that use the Render PDF Form process will use the latest version.

To change the Render PDF Form process used for xfaForm variables:

1. In Workbench ES, select the Process Design perspective.
2. In the Processes view, right-click Process Management > Render PDF Form and select New Version.
3. In the New Process Version dialog box, select Copy An Existing Process and click Next.
4. (Optional) In the Major Version and Minor Version boxes, type versioning numbering. For example, you can type 2 and 0 in the Major Version and Minor Version boxes, respectively.
5. Click Browse and, in the Select Process To Copy dialog box, select Process Management > Render PDF Form > Render PDF Form – 1.0, and then click OK.
6. Click Finish.
7. In the process map for the new version of Render PDF Form, select the Render To PDF Form operation.
8. In the Properties view, in the PDF Form Render Options property, in the Acrobat Version option, change the value from Auto to an Acrobat Version that is Acrobat 7.0 or higher. It is recommended that you use the earliest version that is used by your users. For example, if the earliest version used by your users is Acrobat 8.0, then select Acrobat 8.0.
9. In the Render At Client option, change the value from Auto to Yes.
10. Select File > Save.
11. In the Processes view, select Process Management > Render PDF Form, right-click the new version of the process you created, and then select Activate.

If you have Acrobat 6 and earlier,you must modify the Presence field on the AWS_Submit button to prevent Workspace ES from invalidating the digital signature. The side effect of using these steps is that the form cannot be used offline.

To change the Presence field:

1. In Workbench ES, select the Form Design perspective.
2. In the Resources view, double click the form you want to want to modify.
3. From the Hierarchy palette in the form design, select AWS_SUBMIT.
4. In the Object palette, in the Presence list, change the value from Visible to Hidden (Exclude From Layout).
5. Select File > Save.

Note: The new form design will be used the next time you invoke a process that uses the form design.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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. 

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

 

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.

Back to Contents

Memory leak 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();

Back to Contents

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.  

Back to Contents

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.  

Back to Contents

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.

Back to Contents

LiveCycle Workbench ES

FTP over SSH is not supported by Workbench ES process invocations

When using the FTP service in a Workbench ES process to connect to an SFTP server (that is, FTP over SSH), the following error occurs:

Caused by: com.adobe.idp.dsc.ftp.FTPConnectionException: Cannot login to FTP Server at com.adobe.idp.dsc.ftp.FTPService.connectAndLogin(FTPService.java:150)

Currently, FTP over SSH is not supported by Workbench ES processes and there is no workaround.

Back to Contents

Large process maps in Workbench ES are slowed down when using drag-and-drop functionality

In Workbench ES when the drag-and-drop functionality is used in a very large process map, the ability to manipulate the operations in Process Designer is slowed down or halted. To prevent this, perform the following steps:

    1. Open [install location]\Adobe\LiveCycle ES\Workbench ES\Workbench\workbench.ini in a text editor.
    2. Locate the following setting and change the value to true:

    -Dcom.adobe.workbench.unsupported.process.editors.dragndrop.serialization.disabled

    3. Save and close the file.

    Back to Contents

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.

Back to Contents

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 property

For 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 property

For 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 propogation

For 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:

  1. 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.
  2. If the process version is open for editing, save the process version.

Back to Contents

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.

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 following 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 \jre\lib\charset.jar file and the \jre\lib\ext\localedata.jar file. The email endpoint uses iso-2022jp character encoding.

Back to Contents

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.

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

Back to Contents

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 *.*.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

Suspending a process does not suspend its child processes

When a process has invoked other processes (child processes) using their invoke operation, if you use LiveCycle Administration Console to suspend the process, the process is suspended but any child processes that are in the Running state continue to execute. The expected behavior is that suspending a process also suspends any active child processes, and the parent process is suspended only after all of the child processes are suspended.

To suspend a child process, you must manually suspend it instead of suspending its parent process. You can manually suspend a process from LiveCycle Administration Console by clicking Services > LiveCycle Process Management ES > Process Management and selecting a process and clicking Suspend.

Back to Contents

LiveCycle Workbench ES (LiveCycle Designer ES)

Bad parameter error occurs when setFocus scripting method is used in certain situations

If you use the docReady event in scripts that hide subforms, the layout of the form may not update when the setFocus script executes. You must avoid using the setFocus scripting method in scripts with form:ready, layout:ready, or initialize events. Also, you must avoid using the setFocus scripting method in the following situations:

You can solve the problem by performing one of the following tasks:

Back to Contents

Footers in the first row of a nested table may appear twice when rendered to PDF

A form design that contains a nested table with footers in the first row can appear correctly when seen in a PDF Preview, but it may not render correctly to PDF. When rendered to PDF, the first row may appear twice. This problem occurs when you have two subforms with the same name that can occur more than once. To resolve the problem, use a unique name for each subform.

Back to Contents

Preparing forms intended for use in Workspace ES

You must add the Form Bridge object to a form at design time if you want Workspace ES users to perform tasks such as saving PDF forms as drafts or taking PDF forms offline or want to offer Form Guide users the PDF view option. Use the Form Bridge object in either of the following cases:

Back to Contents

Using digital signatures in dynamic PDF forms

If you add a digital signature to a dynamic PDF form, you need to preserve the state of the form when it is signed. Preserving the form state ensures that scripting changes in a form are preserved when a form is saved. For example, if some fields are hidden when a form is signed, those fields should remain hidden when the form is saved and reopened.

The form state can be preserved automatically or manually. If it is automatically preserved, scripting changes are automatically preserved when the form is saved. If it is manually preserved, scripting changes are preserved through scripting when the form is saved.

If the form is not certified, you can preserve the form state automatically or manually. If the form is certified, you must manually preserve the form state. Automatically preserving scripting changes and restoring the form state invalidates the digital signature in a certified form.

Note: If the form is certified, you can use data binding instead of scripts to determine the form state.

You specify how the form state is preserved on the Form Properties dialog box.

1. To display the Form Properties dialog box, select File > Form Properties and click Defaults.
2. Select a Preserve Scripting Changes To Form When Saved option:

- If the form is not certified, select Automatically or Manually.
- If the form is certified, select Manually.

Back to Contents

Cannot add the Form Bridge object to PDF forms saved as Artwork

The complete button does not appear in Workspace ES when presented in Adobe Reader 8.1.1. To display the complete button in LiveCycle Workspace ES, do the following:

1. Open the PDF form that contains Artwork.
2. Select the root node.
3. Add a script object to it and name the object ContainerFoundation_JS.
4. Open a blank form and add the Form Bridge object to it.
5. Select the ContainerFoundation_JS object.
6. In the Script Editor, select the form ready event and the JavaScript language.
7. Copy the script into the ContainerFoundation_JS object of the PDF form you opened in step 1.
8. In the blank form, select the root node.
9 In the Script Editor, select the form ready event and the JavaScript language.
10. Copy the script into the root node of the PDF form you opened in step 1.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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/

Back to Contents

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. 

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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 LiveCycle Barcoded 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.

Back to Contents

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.

Back to Contents

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).

Back to Contents

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):

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.

2. In the Check For Default dialog box, click Yes.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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:

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.  

Back to Contents

Non-tagged PDF documents created by default; Tagged PDF documents are not completely flat

When you invoke the com.adobe.livecycle.output.client.OutputClient.generatePDFOutput() method, the Output ES service, by default, creates non-tagged PDF documents. If tagged PDF documents are created, they are not completely flat because they contain widgets to enable accessability behaviour in Adobe Reader.

Back to Contents

Output serviceintermittently throws an exception when LiveCycle Forms ES is not installed and batch printing is performed

When you perform batch printing using the Output service and LiveCycle Forms ES is not installed, the Output service intermittently throws an exception stating that the xmlform.xci file cannot be found. For information about performing batch printing, see http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/sdkHelp/outpuMultipleFiles.47.1.html.

To address this problem, you can perform one of the following two tasks:

  1. Restart the J2EE application server on which LiveCycle ES is deployed. This action creates a xmlform.xci file.
  2. Navigate to the default.xci file in the jboss\server\all\svcdata\XMLFormService folder (this path is specific to JBoss). Create a copy of this file in another folder, rename the file xmlform.xci, and place the xmlform.xci file in the jboss\server\all\svcdata\XMLFormService folder.

Back to Contents

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 isModeFinal parameter 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.

Back to Contents

Rights Management service

Invoking the getPolicies method with a policy search filter that has the type set to Organizational throws an exception

When invoking the getPolicies method to retrieve existing policies, you must ensure that a valid policy set exists and it contains enabled policies. If you invoke the getPolicies method and set the type to Policy.ORGANIZATIONAL_POLICY (and not set other policy search filter values), an invalid argument exception is thrown.

To ensure that an exception is not thrown when setting the policy type to Policy.ORGANIZATIONAL_POLICY, you must ensure that you set the policy set name in the search filter by invoking the PolicySearchFilter.setPolicySetName method.

Back to Contents

Invoking some Rights Management C++ functions for the first time results in an exception

When using the Rights Management C++ SDK and invoking the iterate or publishAs functions for the first time, an exception is thrown. These functions work properly when invoking them for a second time.

Back to Contents

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];

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” );

For more code examples, see the LiveCycle ES SDK Help.

Back to Contents

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.

Back to Contents

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

Problems with the Signature service on WebSphere and AIX or Linux, DB2

Problems occur if you are using the Sign Signature Field operation (Signature service), and LiveCycle ES is running in the following environments:

  • WebSphere Application Server
  • Linux or AIX operating system
  • LiveCycle database is a DB2 database

In these environments, processes that use the Sign Signature Field operation with a credential in the trust store fail the first time that the operation is executed. However, the operation completes successfully on subsequent executions.

The following error appears in the server log:

The XAResource for a transaction participant could not be recreated and transaction recovery may not be able to complete properly.

Using an nCipher nShield HSM credential

When using an nCipher nShield 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:\nfast\cknfastrc):

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.

Back to Contents

Scaling signature field text

The text within the signature appearance may not get scaled fully to fit the size of the signature field. 

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

Reason field may not be visible in a signed or certified PDF document

In some situations, the reason field may not be visible in the signature field in a signed or certified PDF document. To ensure that the reason field is visible, you must create a PDFSignatureAppearanceOptionSpec object:

PDFSignatureAppearanceOptionSpec appear = new PDFSignatureAppearanceOptionSpec();

After creating the object, you must invoke its setShowReason method and pass true. Then, when invoking the SignatureServiceClient object’s sign or certify method, you must be sure to pass the PDFSignatureAppearanceOptionSpec object.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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).

Back to Contents

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.  

Back to Contents

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. 

Back to Contents

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.

Back to Contents

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.

Back to Contents

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

  1. Specify a pattern for Exclude File Pattern, such as temp*.ps.
  2. Copy files that begin with temp (for example, temp1.ps) to the watched folder.
  3. 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. 

Back to Contents

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.

Back to Contents

Form Guides

Manual procedures for customizing the digital signature user interface

Each HTML rendered form that requires a signature has a button that the user must click in order to digitally sign the form. It is possible to customize certain properties of this button (such as height, width, and background color) as well as the button text and the text of the resulting message box.

Note: These customizations require unpacking, modifying, and redeploying an EAR file. You must test your changes in a staging environment before deploying to your production environment to ensure that the changes appear as intended.

To customize the signature button:

1. Locate and unpack the adobe-forms-ds.ear file.
2. Unpack the adobe-forms-ds.war file and open the SignDialog.jsp file in an editor.
3. Modify the property values as required, and then save and close the file.
4. Repackage the WAR file, and then repackage the EAR file.
5. If you are not customizing the message text at this time, redeploy the EAR file.

To customize the signature submit message text:

1. With the adobe-forms-ds.war file unpacked, open the //WEB_INF/classes/dsmsg.properties file in an editor.
2. Modify the text strings as required, and then save and close the file.
3. Repackage the WAR file, and then repackage the EAR file.
4. Redeploy the EAR file either manually or using LiveCycle Configuration Manager.

Back to Contents

Designing forms for XHTML output

When developing a process by using LiveCycle Workbench ES or developing a client application by using the Java API, you can instruct LiveCycle Forms ES to produce XHTML output, complying to XHTML strict 1.0. However, the following browsers may cause the form to not render correctly:

- Internet Explorer 7
- Safari 3.x

When you design a form where the target rendition is XHTML, it is recommended that you preview the XHTML output by using FormsIVS.

Back to Contents

LiveCycle ES form guides do not render with Adobe Flash Player versions earlier than 9.0.x

It is a known issue that LiveCycle ES form guides do not render if you have installed a version of Adobe Flash Player earlier than 9.0.x. Also, there is no prompt advising you to upgrade to Flash 9.0.x or later. To render LiveCycle ES form guides properly, you must obtain and install an appropriate version of Adobe Flash Player.

Back to Contents

Users Unable to Enter Data

In a form design that contains multiple form guides, only one form guide can be rendered at a time. If a form guide that is not rendered contains mandatory fields, the user does not have an opportunity to enter data into those fields. Mandatory fields that do not contain data generate an error when the user attempts to submit the form guide, which causes the form guide to be repeatedly re-rendered to the user.

To work around this issue, one strategy is to create an error handler that sets the mandatory property for the field to disabled, in the event that an error occurs. For example, the following JavaScript sets the mandatory property for a text field to disabled:

if (TextField1.mandatory == "error") {
                TextField1.mandatory = "disabled";
} else {
                TextField1.mandatory = "error";
}

Adding this script to the preSubmit scripting event will prevent the mandatory field TextField1 from generating an error if it does not contain any data when the user submits the form guide.

For more information on the mandatory property, see LiveCycle Designer ES Scripting Reference.

Back to Contents

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.

Back to Contents

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:

  1. Start Internet Explorer.
  2. Click Tools > Internet Options.
  3. Click the Security tab and click Custom Level.
  4. Ensure that the Scripting > Active Scripting option is set to Enabled.

Back to Contents

Repository service

LiveCycle ES archive files containing multiple xfaform variables pointing to the same resource may fail

Previewing a LiveCycle ES archive (LCA) file that contains a process and a subprocess, which both have an xfaform variable pointing to the same resource, may fail with the following error:

"Error previewing archive: 'ApplicationManagerService:invalid LCA archive:java.lang.NullPointerException'"

Back to Contents

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.

Back to Contents

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.

For example, rather than structuring your data file this way:
<datafile>
<field>123</field>
…
</datafile>

Structure it this way, adding another level:
<datafile>
<record>
<field>123</field>
…
</record>
</datafile>

To change the time-out value:

  1. Log into LiveCycle Workbench ES and open the Components view.
  2. Click the Output service, right-click the Active service.
  3. Select Edit Service Configuration, and then and change the time-out value
  4. 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:

  1. Log into LiveCycle Workbench ES and open the Components view.
  2. Click the Output service, right-click the Active service.
  3. Select Edit Service Configuration, and then change the setting for Max Concurrent Invocations for Asynchronous Jobs.
  4. Restart the service for the change to take effect.

Back to Contents

Convert PDF service fails immediately after a transaction time out occurs

The ConvertPDF service fails if a PDF file is provided for conversion immediately after a transaction time out error has occured.

Back to Contents

Quick Starts and Samples Issues

Changes in the “End-to-End Mortgage Application”

The “End-to-End Mortgage Application” process no longer uses the Adobe-Samples-LiveCycleES-End-To-EndMortgageApplicationReceiveAgreement.lca or the Adobe-Samples-LiveCycleES-End-To-EndMortgageApplicationReceiveCreditCheck.lca files. The process for configuring and running this sample has also changed.

To import required credentials and configure email:

  1. Log into LiveCycle Administration Console and click Settings > Trust Store Management > Local Credentials.
  2. Click Import on the Local Credentials page.
  3. Import the following credentials:
    • Reader Extensions Credential:

      alias
      GoodUbiquity
      password
      password

    • Document Signing Credential: alias TESTKEYUSAGE-DS.P12 password password
      Note: These credentials are shipped with LiveCycle ES.
  4. Click OK.
  5. Log into Workspace ES and click End-to-End Mortgage Application Generate Credit Check > Send Document.
  6. Configure the following email settings:
    • To Addresses > to youremail@yourserver.com
    • From Addresses > from youremail@yourserver.com
    • Connection settings use the email server settings of youremail@yourserver.com.
  7. Click End-to-End Mortgage Application > Receive PDF.
  8. Configure the following email filter settings:
    • Filter Subject RE: Credit Check
    • Filter From youremail@yourserver.com
    • Connection Settings use the email server settings of youremail@yourserver.com

To test the “End-to-End Mortgage Application” process sample:

  1. Log into Workspace ES and click Samples > End-to-End Mortgage Application.
  2. Fill in the mortgage application.
  3. Click Complete. The email you configured in step 6 above will receive an email and the TODO list will indicate that a credit check PDF is required. Do not click the check mark yet.
  4. Create a credit check PDF by editing the CreditCheckWithSchemaandBC.pdf file and inserting a credit score. For the credit scores and flow, see "End-To-End mortgage application".
  5. Reply to the email that you received in step 3 and attach the CreditCheckWithSchemaandBC.pdf file.
  6. After the email is received, click the check mark in the TODO list.
  7. Review the TODO list as further approval may be required by a Manager or Loan Approver.
    (See output in C:\Samples\LiveCycleES\LiveCycle ES\End-To-End Mortgage Application)

Back to Contents

Installing updates LiveCycle ES Samples

The LiveCycle ES Service Pack 1 provides updated samples. You must manually undeploy the LiveCycle ES 8.0.1 samples before you apply the service pack.

To undeploy the existing samples:

  1. Log in to the LiveCycle Administration Console.
  2. Select Services > Archive Administration > Archive Management.
  3. Delete all the samples in the archive.

Back to Contents

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.

Back to Contents

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.

Back to Contents

Image-to-PDF and OpenOffice-to-PDF conversions to PDF 1.5 only

Adobe PDF settings in LiveCycle Administration Console do not apply to image-to-PDF and OpenOffice-to-PDF conversions. These format types will always convert to PDF 1.5 version files.

Back to Contents

LiveCycle Reader Extensions ES

Review & Comment toolbar missing

When a user who has Adobe Reader 8.x (and not Acrobat) installed uses Workspace ES to open a rights-enabled PDF document that has the Commenting usage right applied to it, the Review & Comment toolbar may not be displayed. To avoid this probelm, apply the Digital Signatures usage right to the PDF document, in additon to the Commenting usage right.

Back to Contents

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.

Back to Contents

Cannot apply usage rights to files using some special characters in file name

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.

Back to Contents

LiveCycle Rights Management ES

Some events not logged for anonymous user access

When an individual policy permits anonymous user access, but the server-wide configuration does not permit anonymous user access, the anonymous user is denied access (the server-wide configuration prevails over the policy), and “access denied” event is not logged on the Rights Management ES server.

Reversing name order

By default, the Rights Management ES end-user web application displays user names as given_name surname. To reverse this order and display names as surname given_name, change a setting in the configuration file, as described in the following procedure. After making this change, all new users will have their names displayed as surname given_name. This setting does not change the order for existing users.

To display names as surname given_name:

1. In LiveCycle Administration Console, click Settings > User Management > Configuration > Import and export configuration files.
2. Click Export and save the config.xml file.
3. Open the config.xml file in a text editor.
4. Add the following section to the Adobe/LiveCycle/Config/UM node:

<node name="CommonNameOrder">

<map>

<entry key="ReverseOrder" value="true"/>

</map>

</node>

5. Save and close the file.
6. In LiveCycle Administration Console, click Settings > User Management > Configuration > Import and export configuration files.
7. Click Browse to find the config.xml file, click Import, and then click OK.

Back to Contents

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.    

Back to Contents

LiveCycle Workspace ES

Deadline icon does not appear on consulted task

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

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.

Back to Contents

(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.

Back to Contents

Error does not appear for failed button actions

If you are using Adobe Reader with Workspace ES, and the PDF form that you are viewing did not have any Reader Extensions ES usage rights applied to it, when you click a button on the form, the button action fails without an error appearing.

Back to Contents

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_SDK\misc\Process_Management\Workspace, 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 ES\Workbench ES\LiveCycle_ES_SDK\misc\Process_Management\
    Workspace, where [workbench install directory] represents the location where LiveCycle Workbench ES was installed.

Back to Contents

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.

For LiveCycle ES, 8.0.1.1 (SP 1) and 8.0.1.2 (SP2), the following documents have been updated:

Additional Documentation Notes

Correction to supported web browsers in Preparing to Install LiveCycle ES guide

The Preparing to Install LiveCycle ES guidestates that LiveCycle ES supports Microsoft Internet Explorer 7 or later and Firefox 2.0.0.1 or later. However, LiveCycle ES does not support the following web browsers:

  • Mozilla Firefox 3
  • Microsoft Internet Explorer 8

LiveCycle ES only supports Microsoft Internet Explorer 7 and Firefox 2.0.0.1 and maintenance versions of these releases.

Back to Contents

Correction to creating a LiveCycle ES database instructions

The section "Creating the LiveCycle ES database" in the Preparing to Install LiveCycle ES guide has the following cautionary note:

Caution: Ensure that you use the Latin1_General_CP1_CI_AS collation when you create the LiveCycle ES database. Any other collation may cause your database initialization to fail.

This note should read "use the SQL_Latin1_General_CP1_CI_AS collation" instead.

Back to Contents

Updated steps for enabling the JBoss JMX Console

The "To enable JBoss JMX Console" task in the Hardening and Security for LiveCycle ES guide provides incorrect instructions for steps 3 and 4. The correct instructions are as follows:

3. From the zipped archive file you downloaded in step 1, extract the jmx-console.war directory from the
    jboss-4.0.3SP1/server/all/deploy directory.

4. Place the jmx-console.war directory in the [LiveCycleES root]/jboss/server/all/deploy directory.

You can continue with steps 5 and 6 as provided in the guide.

Back to Contents

Updated information about configuring a SQL Server data source

The information provided in the "Configuring the SQL Server data source" section on page 52 of the "Preparing to Install LiveCycle ES" guide describes two methods for configuring the data source. You must use only the method that applies to your environment:

  • Use the "To create the SQL Server data source file" method to connect SQL Server to a defined database user.
  • Use the "Configuring Integrated Security on Windows" to connect using a Windows user.

Caution: If you configure the data source using both methods, exceptions will occur.

Back to Contents

File formats supported by PDF Generator ES

PDF Generator ES can convert many native file formats to PDF. The list of supported file formats included in the LiveCycle ES documentation is incomplete. The following file formats are supported:

Using PDF Generator ES, you can add support for native file formats in addition to those already supported. You can also determine how PDF Generator ES interacts with supported applications. For more information, see PDF Generator ES Administration Help, accessible in LiveCycle Administration Console.

Back to Contents

Using Kerberos as an authentication provider

In the "Adding domains" topic of User Management Help, step 3 is incomplete. The complete step is:

3. Add an authentication provider:

Back to Contents

Correction to Help regarding customizing the content of notifications

The "Customizing the content of notifications" topic in Process Management Administration Help lists "@@queueid@@" as a supported variable; however, it is not supported.

Back to Contents

Correction to Help regarding key rollover frequency

The "Setting the key rollover frequency" topic in Rights Management Administration Help states that the default key rollover period is 30 days. The default key rollover frequency is actually 20 days.

 Back to Contents

Correction to Help regarding event logs

The "Viewing event details" topic in Rights Management Help states that the details displayed include the document name and policy name; however, that information is not displayed.

Back to Contents

Explanation of the Collaborate option when specifying document privileges

In Rights Management ES, when you add users to a policy, you can specify document privileges for those users, including the Collaborate option. The Collaborate option enables the user to collaborate on a document that is protected with this policy. The functionality enabled depends on the application, but typically includes making additions to the file, such as annotations or filling in forms. However, it usually does not enable the user to modify the original content in the file.

Back to Contents

Enabling PDF/A-1a support

PDF Generator ES supports the creation of PDF/A-1a-compliant files from Microsoft Excel, Microsoft PowerPoint, and Microsoft Word files.

To enable PDF/A-1a support:

Back to Contents

Notes functionality does not work in a custom build of Workspace ES that contains no changes

When you compile the source code for Workspace ES, the notes functionality does not work correctly in the compiled build. You must include an additional parameter in the services-config.xml file.

The following procedure from the"Retrieving the Workspace ES source code"section in the Customizing the LiveCycle Workspace ES User Interface guide contains the updated steps (in boldface) that were not available when the Help was written:

To retrieve the source code:

1. On your computer, create a folder in which to place the files from the archived Workspace ES reference source. For example, create a folder called wsSource.
2. Access the LiveCycle ES SDK directory at one of the following locations:

- Workbench ES installation: Navigate to the Workspace folder in [installdir]\LiveCycle ES\Workbench ES\LiveCycle_ES_SDK\misc\Process_Management, where [installdir] represents where Workbench ES is installed on your computer.

- LiveCycle ES server: Navigate to the Workspace folder in [installdir]\LiveCycle_ES_SDK\misc\Process_Management, where [installdir] represents where LiveCycle ES is installed on a server.

For example, for a turnkey installation, navigate to the Workspace folder in \Adobe\LiveCycle8\LiveCycle_ES_SDK\misc\Process_Management.

3. Copy the adobe-workspace-src.zip file to the folder that you created in step 1.
4. Copy the services-config.xml to the folder that you created in step 1.
5. Using an archiving utility, extract the contents of the adobe-workspace-src.zip file to the folder you created in step 1.

The following procedure from the "Importing and compiling Workspace ES"section in the Customizing the LiveCycle Workspace ES User Interface guide contains the updated steps (in boldface) that were not available when the Help was written:

To import and compile the Workspace ES source code:

1. In Flex Builder, select File > Import.
2. In the Import dialog box, select Existing Projects into Workspace and click Next.
3. Verify that Select root directory is selected and click Browse.
4. In the Browse For Folder dialog box, navigate to and select the folder from which you extracted the source code, and then click OK. For example, select the wsSource folder.
5. Click Finish.
6. In the Navigator view, right-click Workspace and select Properties.
7. In the Properties for Workspace dialog box, select Flex Build Path and click the Library Path tab.
8. In the Build patch libraries area, select $(FRAMEWORKS)\libs\fds.swc and click Remove.
9. Click Add SWC and, in the Add SWC dialog box, click Browse.
10. In the Choose A SWC File dialog box, navigate to the folder where you copied the SWC files for customizing Workspace ES, select fds.swc, and then click Open. For example, fds.swc from the \forWSCustomization\SWCS folder.
11. When you return to the Add SWC dialog box, click OK.
12. When you return to the Properties for Workspace dialog box, in the left pane, click Flex Compiler.
13. In the Additional Compiler Arguments, type ../../services-config.xml before the –theme lc.css. The location is relative to the Main.mxml file in the project. After you have finished typing, the text in the Additional Compiler Arguments should look similar to the following text:

-locale en_US -namespace http://www.adobe.com/2006/livecycle namespace-manifest.xml -services ../../services-config.xml -theme lc.css

Note: When you add the –services parameter, the path of the services-config.xml file is the relative path from Main.mxml in the Workspace ES (or the main MXML file).

14. hen you return to the Properties for Workspace dialog box, click OK.
15. Select Project > Build Project to compile Workspace ES.

Back to Contents

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.

Back to Contents

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".
  • The "Configuring File Type Settings" topic states that modifying file type settings is supported on Windows only. This is incorrect. File type settings can be modified on Windows, UNIX, and Linux. However, the following file type settings are not available for UNIX and Linux:

    • Adobe PDF export settings
    • Microsoft Excel settings
    • Microsoft PowerPoint settings
    • Microsoft Project settings
    • Microsoft Word settings
    • AutoCAD settings
    • Microsoft Visio settings
    • Other applications' settings

Back to Contents

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:

  1. On the User Management page, click Configuration.
  2. On the Configuration page, click Import and export configuration files.
  3. To export the current configuration setting to a file, click Export and then save the configuration file in another location.
  4. Find the following node in the file:

    <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.

  5. Find the following node in the file:

    <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.

  6. 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.
  7. Click OK.

Back to Contents

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.

Back to Contents

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."

Back to Contents

Repository Service Provider can be configured forFileNet and not Documentum

In the LiveCycle ES Connector for IBM FileNet Administration Help for the French, German and Japanese locales, the "Configuring the Server Connection" topic incorrectly refers to Documentum. The following sentences contain the correct reference to FileNet:

  • "You can configure which repository service provider to use with IBM FileNet."
  • "IBM FileNet Repository Provider: Makes the FileNet repository provider the provider for the repository."

Back to Contents

Configuring LiveCycle Administration Console and application server settings for FileNet 4.0 support using CEWS transport

The following procedure from the "LiveCycle ES Connector for IBM FileNet" topic in the Administering LiveCycle ES guide contains new steps that were not available when the guide was written.

To modify the Content Engine and port number to use the CEWS transport:

If you use a JBoss,Weblogic or WebSphere application server, you must perform the following steps:

  1. In LiveCycle Administration Console, select Services > LiveCycle ES Connector for IBM FileNet.
  2. Under the FileNet DSC Configuration Information section, in the Content Engine box, type on one line:

    cemp:http://[contentserver_IP]:[contentengine_port]/wsi/FNCEWS40DIME?jaasConfigurationName=FileNetP8WSI

    where [contentserver_IP] and [contentengine_port] are values that correspond with your FileNet Content Server environment. This URL is used to create a session to FileNet Content Engine. The "jaasConfigurationName" is the JAAS login label used to authenticate a JAAS login. For more information, see the documentation provided with FileNet.

  3. Under FileNet DSC Configuration Information, in the Port Number box, enter the port number where Content Engine is running. The default ports are: JBoss - 8080, WebLogic - 7001, WebSphere - 9080. For information about other FileNet service configurations, see the "Configuring the Connector for IBM FileNet service section" in Preparing to Install LiveCycle ES for your application server.
  4. Click Save.

    5. To modify the application server configuration files to use the CEWS transport:

    Perform the following steps for your application server:

  5. Copy all of the files (including subfolders) from the [FileNet root]/ContentEngine/wsi folder on the FileNet Content Server computer to the /WASP folder on the LiveCycle ES computer. You may have to create the /WASP directory.
  6. Add the new location of the files as a java option to the application server start command:

    -Dwasp.location=/WASP

  7. Locate the adobe-component-ext.properties file in the [appserver root]/bin folder and add the paths of following FileNet JAR files:

    javaapi.jar
    log4j-1.2.13.jar
    soap.jar
    wasp.jar
    builtin_serialization.jar
    wsdl_api.jar
    jaxm.jar
    jaxrpc.jar
    saaj.jar
    jetty.jar
    runner.jar
    p8cjares.jar
    Jace.jar

Note: These jar files are included in the FileNet application and Content Engine installation.

(JBoss) Perform the following JAAS provider configuration:

Locate the login-config.xml file in the [JBOSS HOME]/server/all/conf folder and add the following application policy as a child of the <policy> node:

<application-policy name = "FileNetP8WSI">
  <authentication>
  <login-module code = "com.filenet.api.util.WSILoginModule" flag = "required" />
 </authentication>
</application-policy>

(WebLogic) Perform the following JAAS provider configuration:

If a custom JAAS configuration file is being used (as indicated by the value of the property -Djava.security.auth.login.config in the application server start command), then add the following lines in the custom JAAS configuration file. Otherwise, ignore these settings:

FileNetP8 {weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin=true;};
FileNetP8WSI {com.filenet.api.util.WSILoginModule required;};
FileNetP8Engine {weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin=true;};
FileNetP8Server {weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin=true;};

(WebSphere) Perform the following JAAS provider configuration:

Locate the JAAS Configuration file (wsjaas.conf) for WebSphere and add the following lines. By default, the file is located in the [WAS_HOME]/AppSrv01/properties/ folder:

FileNetP8 {com.ibm.ws.security.common.auth.module.WSLoginModuleImpl required;};
FileNetP8WSI {com.filenet.api.util.WSILoginModule required;};
FileNetP8Engine {com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy required   delegate=com.ibm.ws.security.common.auth.module.WSLoginModuleImpl;};
FileNetP8Server {com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy required   delegate=com.ibm.ws.security.common.auth.module.WSLoginModuleImpl;};
FileNetP8KerberosService {com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy required   delegate=com.filenet.engine.authentication.kerberos.login.KrbServiceLoginModule;  com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy required   delegate=com.ibm.ws.security.server.lm.ltpaLoginModule;  com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy required   delegate=com.ibm.ws.security.server.lm.wsMapDefaultInboundLoginModule;}

Back to Contents

Configuring LiveCycle Administration Console and application server settings for FileNet 4.0 support using EJB transport

The following procedure from the "LiveCycle ES Connector for IBM FileNet" topic in the Administering LiveCycle ES guide contains new steps that were not available when the guide was written.

FileNet 4.0 using EJB transport is only supported on Weblogic. It is not supported on JBoss and WebSphere. Use the CEWS Transport instead if you are using JBoss and WebSphere.

Perform the following steps for the LiveCycle ES server and FileNet Content Engine:

  1. In LiveCycle Administration Console, select Services > LiveCycle ES Connector for IBM FileNet.
  2. Under FileNet DSC Configuration Information, in the Content Engine box type on one line:

    cemp:t3://[contentserver_IP]:[contentengine_port]/FileNet/Engine?jaasConfigurationName=FileNetP8Engine

    where [contentserver_IP] and [contentengine_port] are values that correspond with your FileNet Content Server environment. This URL is used to create a session to the FileNet Content Engine. The "jaasConfigurationName" is the JAAS login label used to authenticate a JAAS login. For more information, see the documentation provided with FileNet.

  3. Under FileNet DSC Configuration Information, in the Port Number box, enter the port number where Content Engine is running. The default port for WebLogic is 7001. For information about other FileNet service configurations, see the "Configuring the Connector for IBM FileNet service" topic in Preparing to Install LiveCycle ES for your application server.
  4. Click Save.
  5. Locate the adobe-component-ext.properties file in the [appserver root]/bin folder and add the paths of following FileNet JAR files:

    javaapi.jar
    log4j-1.2.13.jar
    p8cjares.jar
    Jace.jar

    Note: These jar files are included in the FileNet application and Content Engine installation.

  6. If a custom JAAS configuration file is being used (as indicated by the value of the property -Djava.security.auth.login.config in the application server start command), then add the following lines in the custom JAAS configuration file. Otherwise, ignore these settings.

    FileNetP8 { weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin=true; };
    FileNetP8WSI { com.filenet.api.util.WSILoginModule required; };
    FileNetP8Engine { weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin=true; };
    FileNetP8Server { weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin=true; };

Back to Contents

Documentum repository and FileNet object store must be created before installing samples

The following steps for the "Configuring the Connector for EMC Documentum service" and "Configuring the Connector for IBM FileNet service" topics in the Installing and Deploying LiveCycle ES guide for your application server were not available when the guide was written.

  1. Complete all of the steps in the "Configuring the Connector for EMC Documentum service" or "Configuring the Connector for IBM FileNet service" topics.
  2. Create a Documentum repository or FileNet object store named Samples.
  3. Install the samples that come with LiveCycle ES into the Documentum repository or FileNet object store.

Back to Contents

Supported native file format conversion for AutoCAD in LiveCycle PDFG Generator ES

In the Preparing to Install LiveCycle ES guide, the “Native file conversion software installation” topic states that only AutoCAD 2005 is supported. This is incorrect and should state that AutoCAD 2005, 2006 and 2007 are supported.

Back to Contents

Updated information for LiveCycle Workbench ES Help

The File Utilities service provides two new operations: Read XML and Write XML. The following reference information for these two new operations was not available when the LiveCycle Workbench ES Help was written:

Read XML

Reads an XML file from the file system of the LiveCycle ES server, and saves the file as an XML document in the process data.

Input

Properties for specifying the file to read.

Filename: A string value that represents the fully qualified name of the file to read from the file system of the LiveCycle ES server. Filename can include the following parameters that are replaced with specific values at run time:

  • %Y = The current year (four digits)
  • %y = The current year (last two digits)
  • %M = The current month.
  • %D = The current day of the month.
  • %d = The current day of the year.
  • %H = The current hour using the 24-hour clock.
  • %h = The current hour using the 12-hour clock.
  • %m = The current minute.
  • %s = The current second.
  • %R = A random number between 0 and 9.

CharSet: A com.adobe.livecycle.fileutils.CharSet value that represents the character set that the file uses. The following values are valid:

  • Big_Five
  • GB_2312
  • ISO_8859_1
  • ISO_8859_2
  • ISO_8859_7
  • KSC_5601
  • Shift_JIS
  • US_ASCII
  • UTF_16
  • UTF_16BE
  • UTF_16Le
  • UTF_8

The default value is UTF_8. If you create a com.adobe.livecycle.fileutils.CharSet variable, you need to select Find Type in the Type list and search for the CharSet type.

Output

Properties for storing operation results.

Result: The location in which to save the file content that is read. The data type is org.w3c.dom.Document.

Exceptions

The exception event attached to this operation can receive FileUtilsException exceptions, which are thrown when an error occurs during the execution of the operation.

Write XML

Writes an XML document to the file system of the LiveCycle ES server.

Input

Properties that specify the file to write.

Pathname Pattern: A string value that represents the fully qualified name of the file to create on the file system of the LiveCycle ES server. Filename can include the following parameters that are replaced with specific values at run time:

  • %Y = The current year (four digits)
  • %y = The current year (last two digits)
  • %M = The current month.
  • %D = The current day of the month.
  • %d = The current day of the year.
  • %H = The current hour using the 24-hour clock.
  • %h = The current hour using the 12-hour clock.
  • %m = The current minute.
  • %s = The current second.
  • %R = A random number between 0 and 9.

XML Document: An org.w3c.dom.Document value that represents the content to write to the file.

CharSet: A com.adobe.livecycle.fileutils.CharSet value that represents the character set that the file uses. The following values are valid:

  • Big_Five
  • GB_2312
  • ISO_8859_1
  • ISO_8859_2
  • ISO_8859_7
  • KSC_5601
  • Shift_JIS
  • US_ASCII
  • UTF_16
  • UTF_16BE
  • UTF_16Le
  • UTF_8

The default value is UTF_8. If you create a com.adobe.livecycle.fileutils.CharSet variable, you need to select Find Type in the Type list and search for the CharSet type.

Make Unique: A boolean value that specifies whether the name of the file is to be made unique. A value of true indicates that the file name be made unique and a value of false indicates that the file name is not unique. The default value is false. To specify the literal value of true, select Make Unique. To specify the literal value of false, deselect Make Unique.

Over Write: A boolean value that specifies whether to replace a file of the same name provided for Pathname Pattern if it exists. A value of true indicates that the file is replaced and a value of false indicates that the file is not replaced. The default value is false. To specify the literal value of true, select Over Write. To specify the literal value of false, deselect Over Write.

Output

Properties for storing operation results.

Result: A string value that represents the actual path of the file that was created.

Exceptions

The exception event attached to this operation can receive FileUtilsException exceptions, which are thrown when an error occurs during the execution of the operation.

Back to Contents

Invalid file referenced in LiveCycle ES SDK Help

The "Unpackaging the dialog and script files" topic in LiveCycle ES SDK Help incorrectly references a file named appmondata.jar. The correct filename is adobe-appmondata.jar. You can find this file by searching on the J2EE application server on which LiveCycle ES is deployed.

Back to Contents

Workbench ES Eclipse support

The section called "Installing the Workbench ES Eclipse feature" in the Installing Your Development Environment document states that after you install Workbench ES, you can optionally add the Eclipse feature by downloading and installing Eclipse 3.2.1 from www.eclipse.org/downloads/.

Workbench ES only supports the use of Eclipse 3.2.1.

Back to Contents

Inaccurate documentation for Execute Script service

The information that LiveCycle Workbench ES Help provides about the Execute Script service is inaccurate. The patServiceContext, patServiceResult, and patExecContext QPAC environment variables are incompatible with the LiveCycle ES (8.0) environment. Furthermore, when upgrading processes, Script actions are replaced with executeScript operations that the Execute Script service provides. However, the script used in the Script action is not compatible with the executeScript operation and needs to be modified to function properly.

For information about creating a script for the Execute Script service, see the "New information about the Execute Script service in LiveCycle Workbench ES" technical article, which is available in the Adobe Knowledgebase at www.adobe.com/go/kb402587.

Back to Contents

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.3) -- 10/02/2008 9:23