Adobe LiveCycle ES Update 1 Service Pack 3

Version 8.2.1.3

Edition 2.0

Copyright 2009 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 you run this version of Adobe® LiveCycle® ES (Enterprise Suite) Update 1 and additional Service Packs.

Contents

Installation Issues

General Installation Issues

Configuring multiple DB2 schemas for use with LiveCycle Content Services ES on a server cluster ** New for LiveCycle ES Update 1 Service Pack 3 **

When you are configuring LiveCycle Content Services ES to run on a server cluster using multiple schemas on a single DB2 database instance, Content Services ES deployment succeeds on the first node but fails on all subsequent nodes. DB2 is case-sensitive and expects to receive values in uppercase letters. To avoid this problem, you must add the following JVM argument to your application server:

-Dhibernate.default_schema=<SCHEMA_NAME>

Important: <schema_name> must be replaced by the schema name using uppercase letters.
Back to Contents

Multicast UDP use on LiveCycle ES vertical WebSphere or WebLogic server clusters ** New for LiveCycle ES Update 1 Service Pack 3 **

On a vertical server cluster, a UDP port is required for cache discovery. The port is defined by the JVM argument adobe.cache.multicast-port in the following format -Dadobe.cache.multicast-port=<port number>. The <port number> value can be any available port between 1 and 65535.

Note: Only the cache discovery mechanism uses UDP. Cache messaging occurs via TCP. On a horizontal cluster, a TCP locator service can be used to avoid the use of UDP discovery packets.
Back to Contents

Incorrect password used by the mysql-ds.xml file during the JBoss turnkey installation ** New for LiveCycle ES Update 1 Service Pack 2 **

When installing the LiveCycle ES turnkey installation, the user-specified password is not stored in the mysql-ds.xml file, which instead contains a default value of password for the MySQL database. To fix this issue, you must add write permissions to the read-only file and then update the mysql-ds.xml file with the user-specified password.
Back to Contents

Workbench ES supported on Windows Vista ** New for LiveCycle ES Update 1 Service Pack 1 **

LiveCycle Workbench ES now runs on both the 32-bit and 64-bit versions of Microsoft Windows Vista^(R) operating systems.
Back to Contents

Installed XDC Editor file has incorrect name

After you install the LiveCycle ES server and Adobe LiveCycle Workbench ES, you must rename the com.adobe.livecycle.xe.editor-8.2.0 jar file in the [LiveCycleES root]\LiveCycle_ES_SDK folder to com.adobe.livecycle.xe.editor-8.2.1.jar.
Back to Contents

Permission denied after copying jboss or jboss_4.2.0 folder

If you copy the /third_party/jboss or /third_party/jboss_4.2.0 folder from the installation media, you must set executable permissions on the installation file by typing the following command at the command prompt:

chmod 755 /jboss/bin/run.sh

or

chmod 755 /jboss_4.2.0/ bin/run.sh

Otherwise, permission is denied when you try to start the run.sh file.
Back to Contents

Characters that are not supported in the installation path

When installing LiveCycle ES Update 1, cannot use double byte or extended latin characters (such as àâçéèêëîïôùûÄÖßÜ€) in the installation path.
Back to Contents

MD5 encryption for LiveCycle ES ESD download

For UNIX® or Linux® environments, you can use any MD5 encryption utility to verify that the ESD file has downloaded properly. The checksum number is posted on the Adobe Prerelease download site at https://prerelease.adobe.com/login.html.
Back to Contents

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

During the installation of LiveCycle Workbench ES, if you click Cancel after the progress bar indicates that Adobe LiveCycle Designer ES is being installed, an error occurs when the installation wizard closes and LiveCycle Designer ES is still installed. You must manually uninstall LiveCycle Designer ES.
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

LiveCycle Configuration Manager Installation Issues

LiveCycle ES and IPv6 support ** New for LiveCycle ES Update 1 Service Pack 1 **

This change only applies to IPV6 networks.

In order to deploy LiveCycle ES on a server configured to use the IPv6 protocol, you must modify the LiveCycle Configuration Manager startup script by completing the following steps:

1. In a text editor, open the <LiveCycleES_root>\configurationManager\bin\ConfigurationManager.bat (Windows) or ConfigurationManager.sh (for Unix) file.
2. Locate the JAVA_OPTS section.
3. Add the IPv6 option: -Djava.net.preferIPv6Stack=true. (For example: JAVA_OPTS="$@ -Xms128m -Xmx768m -Djava.net.preferIPv6Stack=true com.adobe.livecycle.lcm.gui.LCMGUI")
4. Save the changes.

Back to Contents

Need to use correct host name format when configuring application server in LiveCycle Configuration Manager

On the Application Server Configuration Details screen in LiveCycle Configuration Manager, the format to use for the host name of the application server depends on the value in the Listen Address box in LiveCycle Administration Console. If the Listen Address box is empty, you must leave the default 'localhost' as the host name. If the Listen Address box contains an IP address, you must use the same IP address for the host name.
Back to Contents

LiveCycle Configuration Manager uses existing run-time values for some settings

When running LiveCycle Configuration Manager, the settings on the Configure LiveCycle ES (2 of 3) and the Configure LiveCycle ES (3 of 3) panels display default values. If you are configuring a new installation of LiveCycle ES, the values specified on these panels are used to configure LiveCycle ES. If you are configuring an existing deployment of LiveCycle ES, the existing run-time values are used instead.

After the configuration and deployment is complete, you can change these settings from the Core Systems Settings page in LiveCycle Administration Console.
Back to Contents

LiveCycle Configuration Manager application server configuration using IP addresses

If you are using LiveCycle Configuration Manager to configure your application server and you enter the host name as an IP address, you must continue to use the IP address for any related access to the application server.
Back to Contents

Configuring LiveCycle ES application in WebLogic causes error

When running LiveCycle Configuration Manager in a WebLogic environment, the following error message may appear when you are configuring the application server: "Failed on Configuring JVM". This message appears if an edit session is already running on the server, which is indicated by a dimmed Lock&Edit button. You can click the Release Configuration button to release the session and allow the server configuration to complete successfully.
Back to Contents

LiveCycle ES User Manager with Oracle bootstrapping error

LiveCycle ES User Manager bootstrapping to Oracle® fails if NLS_LENGTH_SEMANTICS is set to ‘CHAR’. Before bootstrapping, ensure that the value of NLS_LENGTH_SEMANTICS is set to BYTE.
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 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 because 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 from the LiveCycle Configuration Manager session to the system and then return to the LiveCycle Configuration Manager session.
Back to Contents

Deployment of EAR files continues after the user exits LiveCycle Configuration Manager prematurely

When LiveCycle Configuration Manager has started the execution of the IBM® Websphere 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

(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 fails and a message similar to the one below appears:

[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

JBoss Installation Issues

PDF Generator ES requires manual change to JBoss Logon settings for Service Pack 3 ** New for LiveCycle ES Update 1 Service Pack 3 **

There is a known issue that the LiveCycle ES 8.2 Service Pack 3 JBoss turnkey installer changes the log on account for the JBoss for Adobe LiveCycle ES service. This change causes PDF Generator ES operations to fail. Fix this issue by manually changing the log on account as follows:

1. Open the Windows Services panel.
2. From the Services list, select JBoss for Adobe LiveCycle ES and click Stop.
3. Right-click the service name and select Properties from the popup menu.
4. Click the Log On tab and select the This account option.
5. In the This account box, enter “administrator” (or the account name used to install JBoss) and in the password boxes enter the account password.
6. Click OK to close the panel and restart the JBoss service.

Back to Contents

Updates required to the preconfigured JBoss 4.2.0 cluster ** New for LiveCycle ES Update 1 Service Pack 1 **

If you are using the Adobe preconfigured JBoss 4.2.0 cluster provided on the DVD, you must update the hajndi-jms.xml file with the updated version provided in Service Pack 1.

To update the hajindi-jms.xml file:

1. The hajndi-jms.xml file that you need to replace is located under the <LC8.2.1_JBoss_EFGJ_DVD>/third_party/jb42cluster/server/all/deploy/jms folder in LiveCycle ES 8.2.1.
2. Replace this file with the updated version provided under the on the <LC8.2.1.1_JBoss_EFGJ_DVD>/third_party folder on the LiveCycle 8.2.1.1 disk. Note: If you copied the preconfigured JBoss cluster onto your local hard drive, the location of the file that needs to be replaced is: <JBOSS_HOME>/server/all/deploy/jms/ hajndi-jms-ds.xml
3. Complete step 1 for each node in the cluster.
4. Restart the cluster for the changes to take effect.

Back to Contents

Out of Memory errors with JBoss and MySQL installations ** New for LiveCycle ES Update 1 Service Pack 2 **

Out Of Memory (OOM) errors may occur on a LiveCycle ES Update 1 (Service Pack 2) JBoss and MySQL installation. This issue is related to the MySQL JDBC driver version and the data source connection settings. For a full description and resolution, see article # kb408643.
Back to Contents

 

JBoss 4.2.0 starts in cluster mode if other JBoss Application Server installations are detected

JBoss® Application Server 4.2.0 starts partially in cluster mode if it detects other JBoss Application Server installations on the same network. Currently, there is no workaround to correct this behavior. If you use JBoss 4.2.0 for a single (stand-alone) JBoss Application Server installation, you will experience reduced performance and receive log entries about communication failures, which you can ignore.
Back to Contents

WebLogic Installation Issues

Only five computers can access LiveCycle ES components through a URL

When LiveCycle ES is installed using the WebLogic turnkey option, only five different computers can access the WebLogic Server Administration Console, the LiveCycle Administration Console, or the LiveCycle end-user applications such as LiveCycle Workspace ES, LiveCycle Reader Extensions ES, LiveCycle Rights Management ES, LiveCycle ES Business Activity Monitoring, and LiveCycle Contentspace ES.
Back to Contents

Specifying a full computer name during installation prevents PDF Generator ES from working correctly

During a JBoss or WebLogic turnkey installation, if you specify a full computer name (for example, abc.elemental.adobe.com), LiveCycle PDF Generator ES does not work properly. You must specify a short computer name instead (for example, abc).
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. Otherwise, the database does not bootstrap properly.
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.

General Upgrade Issues

Upgrade Java SDK compatibility error ** New for LiveCycle ES Update 1 Service Pack 3 **

If you are invoking a LiveCycle ES 8.2 operation using the LiveCycle ES 8.0 Java API, you may encounter a Java SDK compatibility error. The error message states that a resource for bundle java.util.PropertyResourceBundle key 128 cannot be located. This error is the result of a message key that exists in LiveCycle ES 8.2, but not in LiveCycle ES 8.0. As a result, an exception is thrown. To avoid this issue, ensure that you upgrade to LiveCycle ES 8.2 JAR files in your client Java application’s class path.
Back to Contents

New location for LiveCycle 7.x QPACs

The LiveCycle 7.x QPACs that are required for LiveCycle 7.x compatibility are not installed with the LiveCycle Workbench ES installation. You can download a ZIP file that contain the required QPACs from the LiveCycle Developer Center at http://www.adobe.com/devnet/livecycle/. On this page, click the Downloads tab and scroll to the SDKs/QPACs section at the bottom of the page.
Back to Contents

Render and Submit process needs to be redeployed when upgrading from LiveCycle ES 8.0.1 to 8.2.1

If you upgraded from LiveCycle Workflow 7.x to LiveCycle 8.0.1, and are now upgrading to LiveCycle 8.2.1, the Render and Submit processes used in your application may not work properly. To resolve this issue, in LiveCycle Administration Console, remove any currently deployed LiveCycle 7.x Render and Submit processes and deploy LiveCycle 7.x Render and Submit processes that are installed with LiveCycle ES 8.2.1.

This problem does not affect users who upgraded directly from LiveCycle Workflow 7.x to LiveCycle ES 8.2.1.
Back to Contents

User Management directory synchronization must be performed after upgrading

When upgrading to LiveCycle ES Update 1, you must ensure that the User Management domain configuration for LDAP (specifically, the settings for Directory Users and Directory Groups in the specific enterprise domain) are not changed after upgrading until you complete a full directory synchronization.

These settings are accessible through the LiveCycle Administration Console by navigating to the Directory Users tab and Directory Groups tab in User Management: Home > Settings > User Management > Domain Management > [directory_name] > Edit Directory.

If these settings are updated after upgrading to LiveCycle ES Update 1 but before a directory synchronization is performed, the synchronization hangs indefinitely.
Back to Contents

LiveCycle Configuration Manager Upgrade Issues

Support of multiple credentials in a PKCS #12 PFX file

When upgrading from LiveCycle 7.x to LiveCycle ES, a PKCS #12 PFX file that contain multiple credentials is not automatically imported; you must manually import the file.
Back to Contents

General Developer - Upgrade issues

Searching for users that have 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 cn=abc.
Back to Contents

LiveCycle Workbench ES - Upgrade Issues

LiveCycle 7.x process types may be renamed during upgrade to avoid naming conflicts

LiveCycle 7.x process types may use the same names as core services in LiveCycle ES. To prevent naming conflicts during and after upgrading to LiveCycle ES, the characters _lc7 are appended to the LiveCycle 7.x process type names during upgrade. For example, the LiveCycle 7.x process type WebService is renamed WebSevice_lc7.
Back to Contents

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

LiveCycle ES Process Management - Upgrade Issues

Email settings set back to default values when upgrading from 8.0.1 ** New for LiveCycle ES Update 1 Service Pack 1 **

When upgrading LiveCycle Process Management ES from LiveCycle ES 8.0.1 to LiveCycle ES 8.2, the Task Assignment and Reminder email settings are set back to the default values.

To reset these values:

1. Log into LiveCycle Administration Console.
2. Select Home > Services > LiveCycle Process Management ES > Server Settings > Task Notifications.
3. Set the Task Assignment and Reminder settings as required.

Back to Contents

LiveCycle ES Business Activity Monitoring - Upgrade Issues

(Solaris, WebLogic, Oracle) Data is not displayed in Historical Process Volume and Historical Process Timing dashboards

When you start LiveCycle ES Business Activity Monitoring 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 that 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 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 that the data is correct.

Back to Contents

Administration Issues

General Administration Issues

Performing searches in LiveCycle ES ** New for LiveCycle ES Update 1 Service Pack 2 **

Do not use backslash characters (\) when performing searches in LiveCycle ES.
Back to Contents

Deployment issue with WebSphere on French, German, or Japanese Windows operating system ** New for LiveCycle ES Update 1 Service Pack 1 **

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. After completing this manual update, you can deploy other EAR files manually using the WebSphere Administrative 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

Underscore characters not allowed in host name

If you access LiveCycle Administration Console using the URL http://hostname:port/adminui, the specified host name cannot contain underscore characters. Otherwise, links to some areas of the LiveCycle Administration Console may not work properly.
Back to Contents

IPv6 format for a literal host address on UNIX is unsupported

Although the Internet Protocol version 6 (IPv6) allows the lower part of a literal host address to be specified in the Internet Protocol version 4 (IPv4) format, do not use this format on the UNIX platform. You must use a regular IPv6 format instead.
Back to Contents

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 that exceeds the wait_timeout on the MySQL database, the database server closes the connections from the client (JBoss server) and all of the authentications will fail. This issue can occur with the LiveCycle Administration Console, LiveCycle Workbench ES, and LiveCycle Workspace ES UI when using the JBoss/MySQL turnkey installation. 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

(Windows, Japanese, IE) Some LiveCycle Administration Console links fail when server name contains underscore

While running LiveCycle Administration Console from an Internet Explorer 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

Archive Administration - Administration issues

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

Errors when importing LCA files that include files whose names have double-byte characters

Errors can occur when you import LCA files from the Applications and Services web pages in the LiveCycle Administration Console. The errors occur under the following circumstances when the LCA file was created:

• LiveCycle ES was deployed to a WebLogic Server that was installed using a turnkey installation. The turnkey installation installs WebLogic 10 running on the Java™ virtual computer (JVM) that the BEA JRockit JDK provides (jrockit_150_11).
• The process that the LCA file contains uses resources or processes that have names using double-byte characters, and/or the process diagram of a process uses double-byte characters (for example, in operation names and annotations).

If you are using LiveCycle Workbench ES with a WebLogic Server that is installed using a turnkey installation, avoid using double-byte characters in the names of resources, processes, and process diagram elements. Errors can occur when you import the LCA file regardless of the type of application server that hosts LiveCycle ES.
Back to Contents

Database Management - Administration Issues

Oracle database maximum open cursors threshold

To configure a maximum value for open cursors in Oracle, you may have to tune this value to a number that is appropriate to your application. It is evident that under a moderate load, the average cursors open was 2700. It is recommended that you start with an upper limit of 3000. For more information, go to http://www.orafaq.com/node/758.
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 has less than 17 characters for MySQL and less than 34 characters for DB2. Otherwise, a message appears that is similar to the one displayed when you attempt to delete the Enterprise Domain:

The following domains could not be deleted

Back to Contents

Email Provider - Administration Issues

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

LiveCycle ES Business Activity Monitoring - Administration Issues

For a complete list of known issues related to Business Activity Monitoring, see the BAM Release Notes.
Back to Contents

LiveCycle Forms ES - Administration Issues

Enhanced features for LiveCycle Forms ES, version 8.2.1.3 ** New for LiveCycle ES Update 1 Service Pack 3 **

This release of LiveCycle Forms ES (version 8.2.1.3) introduces the following enhanced features:

New HTML formats

AccessibleXHTML and NoScriptAccessibleXHTML: Similar to the existing XHTML and NoScriptXHTML formats, the relative units measurements (em) used in these new formats improve zoom-in and zoom-out functionality within a browser.

New Forms ES options

generateTabIndex - Setting this true/false option governs whether TabIndex information is generated in the output HTML. When this option is set to true, tab indexes are generated, creating values that dictate the flow when the user tabs through form fields. When this option is set to false, the TabIndex information is not generated in the output HTML and the tabbing is controlled by the browser.

styleGenerationLevel - This enum option has three values:

• InlineAndInternalStyles - This is the default value that renders all inline and internal styles (inside the <head> tag) present on the HTML page as defined.
• OnlyInlineStyles - This value removes all the internal styles (inside the <head> tag) rendering the HTML page with inline styles only.
• NoStyles - This value removes all the inline and internal styles, rendering the HTML page without any style information. Only the styles passed through the external CSS files are applied.

Back to Contents

Text Size options in Internet Explorer do not affect XHTML forms rendered by LiveCycle Forms ES

When you use LiveCycle Forms ES to render a form as XHMTL in Microsoft® Internet Explorer, the Text Size options available from the View menu in Internet Explorer do not affect the size of the text in the form.
Back to Contents

LiveCycle PDF Generator ES - Administration Issues

Embed3DContent configuration settings

By default, when you install LiveCycle PDF Generator 3D ES and use the Generate PDF service to convert a DWG file to PDF, a 3D PDF file is produced. If you change the embed3DContent setting in the LiveCycle PDF Generator ES configuration file from true (the default value) to false, any DWG conversions that you perform produces a 2D PDF file. For details about accessing the configuration file, see the Generate PDF Administration Help.
Back to Contents

Anonymous access to LiveCycle PDF Generator ES not permitted

Users can no longer access LiveCycle PDF Generator ES anonymously by logging in to http://[hostname]:[port]/pdfgui. All users must log in to http://[hostname]:[port]/adminui before they can access the functionality of PDF Generator ES.

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

With this configuration, users can log in to http://[hostname]:[port]/adminui by using their LDAP credentials and access the PDF Generator ES functionality.

Note: Users configured in his manner do not have access to the PDF Conversion settings page.
Back to Contents

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

The following warning may be displayed in the Server log when running conversions to PDF:

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 may still be locked. If this message is consistent, consider restarting the server."

Back to Contents

Conversion exceptions in the server log; increase conversion time-out

The following conversion exception may appear in the server log when performing conversions by using the Generate PDF service: "ConversionException: ALC-PDG-011-029-c0000005".

Because the default conversion time-out for the Generate PDF service is 270 seconds, it is recommended that you increase the default to 450 seconds. For more information, see the Installing and Deploying LiveCycle ES document for your application server.
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 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

Back to Contents

Native conversions fail after a few conversions with Evaluation version of Acrobat

To address this issue, refer to the following Knowledge Base article: http://kb.adobe.com/selfservice/viewContent.do?externalId=kb407228&sliceId=2

 Back to Contents

LiveCycle Process Management ES - Administration Issues

OutOfMemoryError running Process Management ES with Oracle 10g ** New for LiveCycle ES Update 1 Service Pack 3 **

You may encounter an OutOfMemoryError when running LiveCycle Process Managment ES with an Oracle 10g database on WebLogic or WebSphere platforms. To avoid this problem, change the application server's Prepared statement cache setting to 20. For more details, see your application server documentation.
Back to Contents

Process does not stall when escalation user does not exist

Errors occur when using escalations with the Assign Task operation (in the LiveCycle ES User service) under the following circumstances:

• The Assign Task operation is configured to escalate the task to another user after a specific period of time.
• The escalation user is deleted after the Assign Task operation executes but before the escalation occurs.

When these situations occur, the state of the process and task does not change at the configured escalation time, and the escalation does not occur. The following message appears in the server log:

"The principal specified for escalation is not valid, for taskID: number, queue specified: number."

If the escalation user is deleted before the task is generated (before the Assign Task operation executes), the process stalls or the InvalidPrincipal exception event is thrown.
Back to Contents

Search problems using LiveCycle Process Management ES when user names begin with the # character

Performing task searches by 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 from 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  check box, 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 - Administration Issues

Online commenting for Adobe Reader web browser plug-in

To enable the Comment and Markup toolbar in a PDF file that is viewed by using the Adobe Reader® web browser plug-in, a collaboration back end must be in place, such as a review server. If a collaboration back end is not available, you must save the PDF file 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 time-out 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 time-out values are set accordingly to prevent jobs from timing out and failing:

Document Disposal Timeout: This value can be set in LiveCycle Administration Console. Click 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, click 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="&gtassertionValidityInMinutes" 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 - Administration Issues

Do not use new line characters in descriptions of policies or policy sets ** New for LiveCycle ES Update 1 Service Pack 3 **

As a security enhancement, you can no longer use new line characters (added by pressing the Enter key) in the descriptions of the policies and policy sets that you create in LiveCycle Rights Management ES.
Back to Contents

Invited users who are deleted only through User Management cannot be reinvited

Invited LiveCycle Rights Management ES users who were deleted only through the User Management interface cannot be reinvited. To reinvite a user deleted through User Management, delete the user again on the Rights Management Invited Users page in LiveCycle Administration Console. You can then re-add the user.
Back to Contents

Rights Management ES does not support UTF-8 characters on MySQL

You can create policy and policy set names that contain extended characters; however, when a comparison is made between two strings, accented and non-accented characters such as "e" and "é" are considered to be the same. When someone creates a policy or policy set, a comparison is made to check whether a policy set with the same name already exists. The comparison cannot distinguish between names that are the same except for accented characters. It is assumed that the policy or policy set is already added to the database and the new one is not added.
Back to Contents

User Management - Administration Issues

Corrected description of the Assertion Threshold setting

In the User Management user interface, the description for the Assertion Threshold setting is incorrect. To view this setting, log in to LiveCycle Administration Console and click Settings > User Management > Configuration > Configure Advanced System Attributes. The correct description for the setting is as follows:

This value specifies a buffer time to offset delays due to system time differences between LiveCycle ES application servers in a cluster. A user's login time is backdated by the amount of time (in seconds) specified in this property.

Back to Contents

Distinguishing between principals who share a user identifier and canonical name

When two principals in a particular domain share a user identifier and canonical name, if one principal was accessed by using its user identifier and a search was then executed for the other principal by using its canonical name, the system cannot distinguish between the two and the first principal is returned. However, if the first principal was not accessed by using its user identifier, the search for the second principal by using its canonical name yields the correct result.
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 Folders - Administration Issues

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 Microsoft 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 is completely copied to the watched folder, rename the file to correspond with the pattern that is 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

Need to prevent a watched folder from including Windows Thumbs.db file

If you have a watched folder on Windows that is processing 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

Development Issues

General Development Issues

An exception occurs when invoking the ApplicationManager or TaskManager services using web services ** New for LiveCycle ES Update 1 Service Pack 2 **

If you invoke the ApplicationManager or TaskManager services using a web service proxy created in a previous version of LiveCycle ES, an exception occurs. For example, if you created a web service proxy for LiveCycle ES 8.0.1, and then use that proxy to invoke the ApplicationManager service that is part of LiveCycle ES 8.2.1 or 8.2.1.2, an exception occurs.

To resolve this issue, create a web service proxy using LiveCycle ES 8.2.1 or 8.2.1.2, and ensure that you use the lc_version parameter. For more information, see the “Accessing new functionality using web services” section in Programming with LiveCycle ES.
Back to Contents

FTP server path specified in the FTP service must include a closing slash

In the FTP service's Put and Put Multiple Documents operations, if the path specified in the Path on FTP Server property does not contain a closing slash (for example, /temp/input), the specified files are not placed on the FTP server. You must include a closing slash with the path (for example, /temp/input/) for these operations to work correctly.
Back to Contents

Resources with long file names do not get resolved

Resource file names that exceed 256 characters do not get resolved by the LiveCycle ES services. For example, if an XDP file contains an image or fragment reference that has a fully qualified name that exceeds 256 characters, the Forms service cannot locate the resource file and the form is not rendered. To render the form successfully, you must reduce the length of the resource file name.
Back to Contents

Content transformations do not work in LiveCycle ES installed on WebLogic 10

When LiveCycle ES is installed on WebLogic 10 (using a turnkey or manual installation), content transformations do not work. A patch that will fix this problem will be available soon.
Back to Contents

GetListOfFiles does not return files created on a leap year day

The GetListOfFiles operation that the File Utilities service provides does not return files that were created on February 29 of a leap year. For background information about this issue, see https://issues.apache.org/jira/browse/NET-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573746#action_12573746.

Back to Contents

Problems occurs when Kerberos authentication is set up on the LiveCycle ES server

When Kerberos authentication is set up on the LiveCycle ES server, the following problems may occur:

• A user account that is created in LiveCycle ES is not properly synchronized with LiveCycle Contentspace ES. The home folder for the new user is not created, and the user name does not appear on the Invite User page.
• Document Management service operations do not work properly.

Back to Contents

Problems with exporting complete LiveCycle Contentspace ES repositories

An error occurs when exporting a complete repository from the LiveCycle Contentspace ES administration console. However, you can successfully export the complete Company Home and its children.
Back to Contents

Submit button of type URL Encoded Data must not be used in the LiveCycle Content Services ES samples

If a form that is used in the LiveCycle Content Services ES samples contains a Submit button of type URL Encoded Data, the submit action fails and an error message appears. With these samples, you need to use another type of Submit button or create a servlet that processes the submitted data and invokes the Samples - Content Services - ArchiveData process.
Back to Contents

LiveCycle Content Services ES does not index policy-protected documents

When a document is policy-protected, LiveCycle Content Services ES does not index the document.
Back to Contents

Service WSDL into a Java class conversion

When converting a service WSDL into a Java class by using the Apache Axis WSDL2Java tool, you must create a log4j configuration file and add it to your Java project's class path.

A sample log4j.properties file is provided:

# Set root category priority to INFO and its only appender to CONSOLE.
log4j.rootCategory=INFO, CONSOLE
#log4j.rootCategory=INFO, CONSOLE, LOGFILE

# Set the enterprise logger category to FATAL and its only appender to CONSOLE.
log4j.logger.org.apache.axis.enterprise=FATAL, CONSOLE

# CONSOLE is set to be a ConsoleAppender using a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.Threshold=INFO
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=- %m%n

# LOGFILE is set to be a File appender using a PatternLayout.
log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=axis.log
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.Threshold=INFO
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n

For more information about how to configure the log4j.properties file, go to http://logging.apache.org/log4j/1.2/index.html.
Back to Contents

Assembler service - Development Issues

FileAttachments DDX element does not replace file attachments in the parent document

If the DDX FileAttachment element is a child of a PDF source element, file attachments in the parent document are not replaced.
Back to Contents

Use of DDX overlay feature changes PDF version ** New for LiveCycle ES Update 1 Service Pack 2 **

The DDX PageOverlay element directs Assembler to overlay a PDF document with content obtained from another PDF document. When Assembler overlays a PDF document whose version is 1.3 or earlier, it changes the document to version 1.4. There is no workaround.
Back to Contents

Barcoded Forms service - Development Issues

The Barcoded Forms service fails to decode barcode data when the line delimiter and field delimiter parameters have the same value ** New for LiveCycle ES Update 1 Service Pack 2 **

When using the Barcoded Forms service’s extractToXml method to decode data, you cannot specify the same values for the line delimiter and field delimiter parameters. Otherwise, the service fails to decode the barcode data. For example, you can specify Delimiter.Carriage_Return for the line delimiter parameter and Delimiter.Tab for the field delimiter parameter.
Back to Contents

Supported image file name extensions for barcoded forms

When decoding image files by 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

Encryption service - Development Issues

Extracting form data from an encrypted PDF document ** New for LiveCycle ES Update 1 Service Pack 3 **

When you use the Encryption service Java API to encrypt a PDF document, you can set permissions to extract form data. You set permissions using a java.util.List object. To extract form data, you must set the following permissions:

• PASSWORD_EDIT_ADD
• PASSWORD_EDIT_MODIFY

The following code example shows how to set these permissions using the Encryption service Java API:

PasswordEncryptionOptionSpec passSpec = new PasswordEncryptionOptionSpec();
List encrypPermissions = new ArrayList();
encrypPermissions.add(PasswordEncryptionPermission.PASSWORD_EDIT_ADD);
encrypPermissions.add(PasswordEncryptionPermission.PASSWORD_EDIT_MODIFY);
passSpec.setPermissionsRequested(encrypPermissions);

Back to Contents

Invoking Encryption service operations using JAX-WS

When using the JAX WS tool to generate proxy classes to encrypt a document, a javax.xml.bind.JAXBException is thrown. This issue is related to how these proxy classes handle enum permission arrays. To resolve this issue, you must set the string representation of the enum constant as follows:

MyArrayOfXsdAnyType paramArray = new MyArrayOfXsdAnyType();
paramArray.getItem().add("PKI_EDIT_ADD");
Back to Contents

Forms service - Development Issues

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.

Executing form scripts within HTML forms

When rendering HTML forms that contain both page navigation functionality and form scripts (for example, assume that a script retrieves field data from a database each time the form is rendered), you must ensure that the form script is located in the form:calculate event instead in of the form:readyevent.

Form scripts that are located in the form:ready event are executed only once during the initial rendering of the form and are not executed for subsequent page retrievals. In contrast, the form:calculate event is executed for each page navigation where the form is rendered.
Back to Contents

Extra column separator line appears in tables in Netscape and Internet Explorer 6

An extra column separator line appears in tables after every two columns in Netscape and Internet Explorer 6. The result is that tables are not displayed properly in these web browsers. This issue does not appear in Internet Explorer 7, Firefox, and Safari browsers.
Back to Contents

Dotted borders are rendered as curved lines between table cells

Dotted borders for cells inside a table are not rendered correctly. The borders shared between two cells appear as curved lines; however, dotted borders are rendered correctly along the table border.
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 forms) are used in processes that involve users with LiveCycle Workspace ES, the forms invalidate certified signatures.This is because when LiveCycle Workspace ES loads a static PDF, it breaks certification.

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

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 LiveCycle 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, respectively.
5. Click Browse and, in the Select Process To Copy dialog box, select Process Management > Render PDF Form > Render PDF Form – 1.0
6. Click OK and then 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 later. It is recommended that you set the value to the earliest version that your users use.
9. In the Render At Client field, 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 that 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 LiveCycle Workspace ES from invalidating the digital signature. The consequence of using the following procedure is that the form cannot be used offline.

To change the Presence field:

1. In LiveCycle Workbench ES, select the Form Design perspective.
2. In the Resources view, double-click the form you 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 next time you invoke a process that uses the form design, the new version of the form design will be used.
Back to Contents

Customizing the HTML Digital Signature button's UI properties

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

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 correct 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 by using an SSL-enabled web server, you cannot render a form by using the Use WebServices button from FormsIVS. This situation applies when only the web server is SSL-enabled, not the J2EE application server.
Back to Contents

Manual procedure is required to customize digital signature user interface

You can modify the text and the user interface for the HTML digital signature dialog box. To customize this dialog box, you must follow these steps:

1. Undeploy the adobe-forms.ds.ear file.
2. Using a tool such as WinRAR, open the adobe-forms-ds.ear file, open the adobe-forms-ds.war file, and extract the SignDialog.jsp file.
3. Modify the SignDialog.jsp file and replace the modified file back into the adobe-forms-ds.war file and then add the modified WAR file back into the adobe-forms.ds.ear file.
4. Using a tool such as WinRAR, open the adobe-forms-ds.ear file and extract the dsmsg.properties file.
5. Modify the dsmsg.properties file and replace the modified file back into the adobe-forms-ds.ear file.
6. Redeploy the modified adobe-forms.ds.ear file.

Back to Contents

Generate PDF - Development Issues

Generate PDF service must use Acrobat WebCapture in Japanese Windows environment

In a Japanese Windows environment, when you use LiveCycle PDF Generator ES to convert HTML pages to PDF, the Generate PDF service must be configured to use Acrobat WebCapture. Otherwise, the generated PDF will not contain 2-byte characters.

To configure Acrobat WebCapture for HTML to PDF conversion:

1. Log in to LiveCycle Administration Console and select Services > Applications and Services > Service Management.
2. On the Service Management page, select PDF Generator from the Category list, click Filter, and then click GeneratePDFService.
3. In the Use Acrobat WebCapture (Windows Only) box, type true and click Save.

Back to Contents

When retrieving the generated output file through direct consumption of the WSDL, a URL is usually 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 usually 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 Programming with LiveCycle ES..
Back to Contents

LiveCycle Workbench ES - Development Issues

Workbench ES Start Page may not open ** New for LiveCycle ES Update 1 Service Pack 2 **

When you start Workbench ES after installing LiveCycle ES 8.2 Service Pack 2, the Start Page may not open automatically. This occurs if prior to installing Service Pack 2, you used Workbench ES and left the Start Page open.

To open the Start Page, in Workbench ES, select Help > LiveCycle Start Page.
Back to Contents

Changing string length to Unlimited causes errors ** New for LiveCycle ES Update 1 Service Pack 1 **

Errors occur on the LiveCycle ES server when, in an activated process, you change the maximum length of a string variable to Unlimited. The errors that occur cause the process to be deactivated, and prevent the process from becoming active again.

If you need a string variable that has no size constraints and the process is already activated, create a new string variable and select the Unlimited option in the variable properties. Do not modify an existing string variable to have an unlimited size rather than a maximum length.
Back to Contents

Process recordings can use large amounts of server memory

Playing recordings of processes that include many variables or many operations can require the use of large amounts of memory on the LiveCycle ES server. If the LiveCycle ES server becomes destabilized when you try to play a process recording, the Java Virtual Machine (JVM) that hosts the application server may require more memory than it is allocated. Also, you may need to restart the computer that hosts the server to establish stability.

To increase the memory that is allocated to the JVM, you can configure the -Xmx option of the JVM that runs the application server. For example, if the current option is -Xmx1024m, changing the option to -Xmx1280m increases the maximum amount of allocated memory by 256 MB.

For information about how to configure the JVM option, see the LiveCycle ES installation document for your application server:

JBoss: See the "Modifying the JBoss configuration files" topic in the Preparing To Install LiveCycle ES document.

WebSphere: See the "Configuring the JVM arguments and properties" topic in the Installing and Deploying LiveCycle ES for WebSphere document.

WebLogic: See the "1832627Configuring the JVM arguments" topic in the Installing and Deploying LiveCycle ES for WebLogic document.

Back to Contents

XML schema for the PDF conversion settings of the Generate PDF service

LiveCycle Workbench ES Help does not contain information about how to use XML code to configure the PDF conversion settings of the Generate PDF service operations. This information, as well as the XML schemas that dictate the structure of the XML, is documented in the "XML schema for the PDF conversion settings of the Generate PDF service" technical article, which is available in the Adobe Knowledgebase at http://www.adobe.com/go/kb403981

Back to Contents

Form caching disabled in LC7UpgradeRender process

The renderPDFForm operation in the LC7UpgradeRender process has the Cache Form On Server property set to False. This configuration is required so that form data is correctly merged with PDF forms.
Back to Contents

Value of wsfilename and basename attributes for task attachments

LiveCycle Workbench ES Help indicates that the wsfilename attribute for documents that are attached to tasks contains the file name of the attached document. However, the wsfilename attribute can include the entire path of the file as well as the file name. The basename attribute of document values contains only the file name.

For example, a process uses the Read Document operation (File Utilities service) to create a document from a file named file.txt, which is located in the C:\files directory of the LiveCycle ES server. An Assign Task operation (User service) is configured so that the file.txt is attached to the task that it generates. The value of the wsfilename attribute for the attachment is C:\files\file.txt, and the value of the basename attribute is file.txt.

Note: When LiveCycle Workspace ES users attach documents to tasks, the value of the wsfilename attribute includes only the file name, and not the path.
Back to Contents

Some double-byte characters are not allowed in the archive file name

LiveCycle ES fails to create an archive file if the file name includes the half-width katakana characters and the following double-byte characters: Çüé âäàåçêëèïîìÄÅÉ æ Æ ô ö ò û ù ÿ Ö Ü ¢ £ ¥ ₧ ƒ.
Back to Contents

Unsuccessful copying of resources when another window is activated

When copying a resource from the Resource view to a local folder by using the drag-and-drop method, if you click anywhere within the Windows workspace before the process is completed, the copy is not successful.
Back to Contents

One of the options for propagating permission changes does not work correctly

In the LiveCycle Workbench ES Resources view, when you assign access permissions to a folder in the Access Control panel, you must use the default option. The default option, This Folder And All Resources And Folders It Contains, propagates permission changes to the currently selected folder and all of the resources and folders that it contains. The second option, This Folder And Only The Resources It Contains, does not work and will propagate permission changes to the current folder and all of the resources and folders that it contains.
Back to Contents

Low memory warnings

If a low memory warning appears when you log in to LiveCycle Workbench ES (it is connecting to the LiveCycle ES server), you can increase the amount of memory that is allocated for running Workbench ES.

To configure the allocated memory, modify the workbench.ini file. The property that controls the amount of allocated memory is in the format -Xmx[number]M, where [number] is the number of MB of memory that is allocated. The default amount of memory that is allocated is 512, which is set by using the property value of -Xmx512M. You must increase the amount of memory in increments of 256. For example, if the warning appears when 512 MB of memory is allocated, increase the allocated memory to 768. If the warning occurs again, increase to 1024.

The workbench.ini file is located in the [install folder]/Adobe/LiveCycle ES/Workbench ES/Workbench folder, where [install folder] is the location where you installed LiveCycle Workbench ES.

To increase the allocated memory:

1. Open the workbench.ini file in a text editor, locate the line that contains the property that sets the amount of allocated memory, and modify the values of the property as required. For example, -Xmx768M allocates 768 MB of memory.
2. Save and close the workbench.ini file and restart LiveCycle Workbench ES.

If a low memory warning appears after extended use of LiveCycle Workbench ES, you must close and restart it.
Back to Contents

Performance of LiveCycle Workbench ES degrades when using drag-and-drop on large process diagrams

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

1. Open the [install location]\Adobe\LiveCycle ES\Workbench ES\Workbench\workbench.ini file in a text editor.
2. Locate the following setting and change the value to true:
   • Dcom.adobe.workbench.unsupported.process.editors.dragndrop.serialization.disable
3. Save and close the file.

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 LiveCycle 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 uses ISO-2202JP 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 from what 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
Email Notification	Send no attachments	Send With Document
Email Notification	Send Mail	Send With Document
Email Notification	Send With Map Of Attachments	Send With Map of Attachments

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

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	Email Notification
Process Management	Share Tasks For Shared Queues
Output	PrintPDFPackage

The following table lists the resources that are installed.

Folder	Resource name
Process Management/Workspace	QueueSharing.swf

Back to Contents

LiveCycle Workbench ES locking issues

LiveCycle Workbench ES allows users who 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 tries 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 another 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

Process Engine Connector service for IBM FileNet - Development Issues

Cannot set or retrieve values in the Step Parameter Mapping Table in the Set Workflow Step Parameters and Retrieve Workflow Step Parameters operations in a process

When creating a process by using LiveCycle Workbench ES, in the Set Workflow Step Parameters or Retrieve Workflow Step Parameters operations for the Process Engine Connector service for IBM FileNet service, if you use set or retrieve values using the Step Parameter Mapping Table, an arbitrary value prefixed with an “@” character is set or retrieved, respectively. The Set Workflow Step Parameters or Retrieve Workflow Step Parameters operations execute without an error in the process. However, invalid values are set or retrieved from the workflow step located in Connector for IBM FileNet. This occurs because the internal type for the Step Parameter Mapping Table property is an array data type, which is not currently supported for operations within LiveCycle Workbench ES.
Back to Contents

LiveCycle Workbench ES (LiveCycle Designer ES) - Development Issues

For complete list of known issues with LiveCycle Designer ES, see the LiveCycle Designer ES Release Notes
Back to Contents

Output service - Development Issues

Updated information about OutputException in the Output service ** New for LiveCycle ES Update 1 Service Pack 1 **

The operations that the Output service provides can throw OutputException exceptions when an error occurs during execution. The following table lists example situations that can cause the exceptions to occur for each operation.

Operation	Situation
Generate PDF Output	The Output service cannot locate the input form. For example the form name is incorrect, or the repository path that is created from the content root and the form name is incorrect. An incorrect value is provided for the Transformation Format property. The XDP data that is provided for the Input Data property is not valid. The type of data that is provided is not supported. The data that is provided contains malformed XML code. The form that is provided for the Form property is not valid. The file that is provided as the Form value is already a flat PDF document. The Meta Data Spec File defines no user-level meta attributes. The value for Record Name or Record Level does not match the actual name or level in the form data.
GeneratePrintedOutput	The Output service cannot locate the specified form. For example the form name is incorrect, or the repository path that is created from the content root and the form name is incorrect. The XDP data that is provided for the Input Data property is not valid. The type of data that is provided is not supported. The data that is provided contains malformed XML code. The form that is provided for the Form property is not valid. The file that is provided as the Form value is already a flat PDF document. The Meta Data Spec File defines no user-level meta attributes. The value for Record Name or Record Level does not match the actual name or level in the form data.
SendToPrinter	The Output service cannot locate the network printer. For example the printer name is incorrect, the URI of the print server is incorrect, or the printer is offline. The Output service cannot locate the input document. For example, the path to the document is incorrect. An error occurs on the print device.
TransformPDF	The Output service cannot locate the specified form or document. For example the path to the form or document is incorrect. The specified document to transform is not a PDF document. The specified document is not an XFA-based PDF or an Acrobat form. The specified XFA-based PDF form has been reader-extended, digitally signed, or certified.
For all operations	A required property value is not specified. Services that the Output service depends on are not started (XMLForm, FontManager). The value that is specified for an operation property is not valid. A problem occurred with the LiveCycle ES server, for example a JMS messaging error.

Back to Contents

Exception events are not always thrown for some Output service operations ** New for LiveCycle ES Update 1 Service Pack 1 **

The generatePDFOutput and generatePrintedOutput operations for the Output service have exception event throws attached to them when they are added to process diagrams. However, in some circumstances, the exception events are not thrown when failures occur. Instead, the returned Status Document includes information about the failure. The Status Document is an XML document that summarizes the results of the operation.

To handle all failure scenarios, you must include the following features in your process diagrams:

• To handle failures that are indicated in the Status Document, draw routes from the operation and add conditions to the route. The conditions evaluate the Status Document to see whether an exception has occurred.
• To handle failures that throw exception events, draw routes from the exception event throws. (See Handling event catches in LiveCycle Workbench ES Help.)

The Status Document includes a status element:

• If the operation was successful, the status element contains a zero (0).
• If an exception occurred, the status element contains any text other than a zero (0).

The XPath expression that retrieves the text in the status element is /process_data/XML variable name/printResult/status, where XML variable name is the name of the variable that stores the status document.

You can use routing conditions to evaluate the returned status document and determine whether an exception occurred. For example, the Status Document property of a generatePDFOutput operation is set to an XML variable named XMLvar. The following condition is true when an exception has occurred:

/process_data/XMLvar/printResult/status != 0 

To handle exceptions that are indicated in the Status Document:

1. Configure the generatePDFOutput or generatePrintedOutput operation so that the Status Document property is set to an XML variable. The returned document value will be automatically coerced from a document value (binary) to an XML value (text).
2. Draw a route from the generatePDFOutput or generatePrintedOutput operation to the operation that you want to execute when the exception occurs
3. Add a condition to the route that compares the text in the status element to zero (0).

To handle exceptions that throw exception events:

• Follow the instructions in Handling event catches in LiveCycle Workbench ES Help.

Back to Contents

Transaction time-out messages in the log file

When the Output Service API is invoked asynchronously for multiple requests, "Transaction Time Out" messages may appear in the log file for some of the requests even though the transactions were completed successfully.
Back to Contents

Rights Management service - Development Issues

An exception occurs when specifying a large value for the maxResult parameter ** New for LiveCycle ES Update 1 Service Pack 2 **

When invoking the PolicyManager object’s getPolicies method and passing a large number for the maxResult parameter, an exception may occur. Different databases have different limitations. For example, 50000000 is a limitation for the MySQL database.
Back to Contents

Modifying policy attributes using web services

To modify policy attributes using a web service (for example, using Java proxy classes that were created with AXIS), you must ensure that the policy is registered with the Rights Management service. You can then reference the existing policy by using the PolicySpec.getPolicyXml method and modify the policy attributes by using the applicable methods. For example, you can modify the offline lease period by invoking the PolicySpec.setOfflineLeasePeriod method.
Back to Contents

Security service - Development Issues

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."
Back to Contents

Signature service - Development Issues

Limitations to digital signatures and reverse proxies

LiveCycle ES topologies can include proxy servers that receive server requests and direct them to the LiveCycle ES server. A typical use of a proxy server is to receive requests from outside the firewall. In this topology, requests from users who are behind the firewall can be sent directly to the LiveCycle ES server.

When a process includes a PDF form that a user digitally signs and the form is subsequently routed to other users in a process, all of the users must access the LiveCycle ES server in the same way. They must all access the server either directly or through the same proxy server. If subsequent users access the server differently than how the signer accessed the server, the digital signature is invalidated and the form cannot be submitted.

For example, an external user digitally signs a PDF form and submits it to the proxy server. The process sends the form to an internal user who connects to the LiveCycle ES server directly. When the internal user opens the form, the digital signature is invalidated and an error occurs when the user tries to submit the form.
Back to Contents

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 that LiveCycle ES is deployed on 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 try to sign, certify, or verify an invalid PDF document by using the Signature service, you may encounter exception messages or problems when processing the input PDF document. 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

Certify signatures are not trusted

When certifying and signing the same PDF document, if the certifying signature is not trusted, a yellow triangle appears against the first 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 that have 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

User Management - Development Issues

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

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 - Development Issues

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 - Development Issues

Creation of watched folders for import and export operations does not allow file name extension abstraction

When invoking the Form Data Integration service by 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

Form Guides - Development Issues

Toggle PDF, Save, and Form Guide Help buttons not working correctly at runtime in Mozilla FireFox 3.0.x ** New for LiveCycle ES Update 1 Service Pack 3 **

This issue occurs when all of the following statements are true:

• You have created a form guide that uses the Workspace ES form guide layout.
• The form guide renders with a PDF of the associated form to allow users to switch between the form guide and the PDF while entering data.
• The form guide displays in FireFox 3.0.x.

At runtime, the browser overlays the form guide toolbar buttons at the bottom of the browser window in such a way that users cannot select any of the buttons. This is a known issue with the Workspace ES form guide layout running in FireFox 3.0.x.

To workaround this issue, do one of the following:

• Apply a different form guide layout to the form guide.
• Create a custom form guide layout, based on the Workspace ES layout, and relocate the toolbar buttons to the top of the layout. Relocating the buttons to the top of the layout allows them to display in FireFox 3.0.x. For more information on creating custom form guide layouts, see Customizing Form Guides Using Flex Builder.

Back to Contents

Form guide objects not displaying correctly on panel layouts that support repeating ** New for LiveCycle ES Update 1 Service Pack 3 **

Adding an exclusion group object to a form guide panel that uses one of the the Repeater Accordion, Repeater Grid, and Repeater Tab panel layouts causes some objects to be excluded from the output. When the form guide renders, the first instance of the repeating panel displays the appropriate set of objects. However, when users click Add to create a new instance of the repeating panel, the newly created instance will omit the exclusion group object and all other objects that appear after the exclusion group in the form guide hierarchy.

For example, if your form guide hierarchy for a panel includes the following objects, the second instance of the repeating panel displays only the Text object from the form guide hierarchy:

Panel (Repeater Accordion)
    Text
    Exclusion group
        Radio button
        Radio button
    Text Field
    Text Field
    Drop-down List

To work around this issue, add individual radio button objects from the exclusion group to your form guide, instead of adding the exclusion group as a single object.
Back to Contents

Non-English form guide samples included with LiveCycle Designer ES require updating ** New for LiveCycle ES Update 1 Service Pack 1 **

The Immunization and Purchase Order sample form designs, which are included with non-English versions of LiveCycle Designer ES, are not up-to-date. By default, these sample form designs are located in the \8.2\EN\Samples\Forms\FormGuide folder, where Designer ES is installed. You can obtain updated copies of these samples from the LiveCycle section of the Adobe Developer Center.
Back to Contents

Loss of data value formatting in multiline input fields on form guides ** New for LiveCycle ES Update 1 Service Pack 1 **

This information only applies to form guides to which you have manually added the FormBridge.xfo object.

If you manually add the FormBridge.xfo custom object to your form in LiveCycle Designer ES, and you include the PDF version of the form with your form guide at run-time, the formatting of data values in multiline input fields may not persist when switching between the PDF and form guide.

To correct this issue, you must make the following edits to the FormBridge.xfo custom object located in the \EN\Objects\Custom folder where LiveCycle Designer ES is installed (by default C:\Program Files\Adobe\LiveCycle Designer ES\8.2\EN\Objects\Custom).

1. Locate the getData() function and change the line:
   
      return xfa.datasets.saveXML().replace(/\n/g, "");
   
   to:
   
      return xfa.datasets.saveXML();


2. Locate the resolveSOMProperties() function and change the line:
   
      value = obj.saveXML().replace(/\n/g, "");
   
   to:
   
      value = obj.saveXML();


3. Save the file and restart LiveCycle Designer ES.
4. Open any forms to which you added the FormBridge.xfo object, delete the existing version of the XFO, and insert the updated version from the Custom tab of the Object Library. Alternatively, if you made changes to the FormBridge.xfo object that already exists on your form design, update the existing XFO with the changes described in steps 1 and 2.
5. Save the form design. The change will take effect the next time the form guide is rendered.

Back to Contents

Save button does not appear in Guide Builder in LiveCycle Workbench ES

If you start Guide Builder from LiveCycle Designer ES in LiveCycle Workbench ES when creating form guides, the Save button does not appear in the Guide Builder interface. To save your changes in Guide Builder, you must click Apply and then you must save your form design in LiveCycle Designer ES.
Back to Contents

Limiting text field data entry to the visible area does not apply to form guides

The LiveCycle Designer ES option Limit Length to Visible Area, which restricts a user from entering more data in the field than what is visible at any given time, does not apply to fields on a form guide. Due to the differences in the formats, the fillable portion of a field may be different, depending on whether the user is viewing a PDF version of a form or a form guide.

To restrict the amount of data a user can enter into a text field for both PDF and form guides, you can use the Max Chars option to limit the data input to a specified number of characters.
Back to Contents

Using an Image Field in a form guide

When adding a LiveCycle Designer ES image field object to your form guide, note the following behaviors:

• You must select the Embed Image Data option to properly display an image in the image field when the form guide renders.
• An Image Field object does not correctly appear or allow you to select alternative image files when you preview your form guide using Guide Builder. You must render your form guide by using the LiveCycle ES server in order to view an image field object correctly.

Back to Contents

Scroll bars do not appear when required for panel and form guide help

The default form guide and panel layouts included with Guide Builder use fixed area sizes for each region of the form guide. If you include an image file in the form guide help or the help for individual panels within a form guide, and the image file is larger than the size of the help area, the image will appear truncated. The help area does not display scroll bars to allow you to view the truncated content.

To work around this issue, you must either resize the image in Guide Builder or resize the original image file.
Back to Contents

Default form guide layout styles are automatically saved as a SWC file

If a form guide does not include custom styling applied by 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

Internet Explorer security warning appears 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

Performance Issues

General Performance Issues

Quartz Scheduler issue with a cluster and DB2 database

In a cluster running DB2, the Quartz Scheduler can cause the servers to fail while under constant load. The cause of this issue is that the Quartz tables start to back up and experience deadlocks. To correct this issue, you can add the following properties to the JVM arguments:

-Dorg.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.StdJDBCDelegate
-Dorg.quartz.jobStore.lockOnInsert=false

Back to Contents

Quick Starts and Samples Issues

General Issues

Using samples after installing Service Pack 2 ** New for LiveCycle ES Update 1 Service Pack 2 **

The samples deployed by the SP2 installer will only overwrite existing samples on the disk and will not not impact the samples already deployed using a previous version of LiveCycle ES. To use a sample with LiveCycle ES 8.2 SP2, first manually undeploy the existing process for the sample, and then deploy the new process.
Back to Contents

Error occurs when running the Assembler sample provided with LiveCycle ES (8.0.1) ** New for LiveCycle ES Update 1 Service Pack 1 **

The Assembler sample provided with LiveCycle ES (8.0.1) does not run on WebLogic 9.2, Solaris 9, and Oracle 10g. This is because the library commons-logging.jar file is missing. You can either add the missing library or use the Assembler sample shipped with LiveCycle ES Update 1 (8.2.1).
Back to Contents

Location of the properties file for all LiveCycle Content Services ES samples

The properties file (web-client.properties) for all LiveCycle Content Services ES samples is located in the adobe-contentservices-src.zip file. This ZIP file is installed under the [LiveCycle installation directory]\LiveCycle_ES_SDK\misc\ContentServices folder.
Back to Contents

Sample XDC files in LiveCycle Workbench ES

When you try to open any of the XDC files that are listed below the Samples/Output directory in the Resources view, LiveCycle Workbench ES displays an error. To view and edit any of the XDC files that are provided with LiveCycle ES, follow the instructions described in the XDC Editor Help at www.adobe.com/go/learn_lc_xdcEditor.

Back to Contents

End User Issues

General End User Issues

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 into a form field by using Adobe Reader 7.x, ensure that you press Enter after you enter the data and before you submit the form. If you do not press Enter, the data that you entered into the form field is not submitted with the form.
Back to Contents

LiveCycle Content Services ES - End User Issues

Generic Service Invocation returns many content attributes ** New for LiveCycle ES Update 1 Service Pack 1 **

The Generic Service Invocation in LiveCycle Contentspace ES now returns many content attributes. These strings are used as keys into the map of attributes that is available for the content:

{http://www.alfresco.org/model/content/1.0}versionLabel
{http://www.alfresco.org/model/content/1.0}title
{http://www.alfresco.org/model/content/1.0}name
{http://www.alfresco.org/model/system/1.0}node-uuid
{http://www.alfresco.org/model/content/1.0}qualified-path
{http://www.alfresco.org/model/content/1.0}parent-folder
{http://www.alfresco.org/model/content/1.0}creator
{http://www.alfresco.org/model/content/1.0}created
{http://www.alfresco.org/model/content/1.0}modifier
{http://www.alfresco.org/model/content/1.0}modified

These are the corresponding constants:

ContentManagementConstants.NODE_ATTRIBUTES.PROP_VERSION,
ContentManagementConstants.NODE_ATTRIBUTES.PROP_TITLE,
ContentManagementConstants.NODE_ATTRIBUTES.PROP_NAME,
ContentManagementConstants.NODE_ATTRIBUTES.PROP_UUID,
ContentManagementConstants.NODE_ATTRIBUTES.PROP_QUALIFIED_PATH,
ContentEventConstants.TYPE_PARENT_FOLDER,
ContentManagementConstants.NODE_ATTRIBUTES.PROP_CREATOR,
ContentManagementConstants.NODE_ATTRIBUTES.PROP_CREATE_DATE,
ContentManagementConstants.NODE_ATTRIBUTES.PROP_MODIFIER,
ContentManagementConstants.NODE_ATTRIBUTES.PROP_MODIFY_DATE

Back to Contents

Insert File into Current Document button does not work ** New for LiveCycle ES Update 1 Service Pack 1 **

In the LiveCycle Contentspace ES Office Plugin, the Insert File into Current Document button fails to insert a file within the current document.
Back to Contents

LiveCycle Content Services ES is not supported in IPv6

LiveCycle Content Services ES is not supported in the IPv6 environment.
Back to Contents

Connecting to LiveCycle Content Services ES using FTP

When connecting to LiveCycle Content Services ES by using FTP through a Mozilla Firefox web browser, you must specify the user ID in the URL (for example, ftp://<userid@<server>:<port>/). If you use ftp://<server>:<port>/, the connection fails.
Back to Contents

LiveCycle PDF Generator ES - End User Issues

PDF Generator ES with Acrobat 9 compatibility drops currency symbols ** New for LiveCycle ES Update 1 Service Pack 1 **

When you are running PDF Generator ES using the default option “Process documents with Acrobat 9 compatibility”, if the original file contains the currency symbols $ or ¢, they are not converted. The symbols do not appear in the generated PDF. There is no known workaround.
Back to Contents

LiveCycle Reader Extensions ES - End User Issues

Using Reader Extensions ES with certified documents ** New for LiveCycle ES Update 1 Service Pack 1 **

By default, the Full Save option is enabled in the LiveCycle Reader Extensions ES web application. When using Reader Extensions ES with certified documents, you must deselect the Full Save option; otherwise, the certifying signature will be invalidated.
Back to Contents

Review & Comment toolbar missing

When a user who has Adobe Reader 8.x (and not Acrobat) installed uses LiveCycle 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 problem, apply the Digital Signatures usage right and also the Commenting usage right to the PDF document.
Back to Contents

Cannot use a form in Adobe Reader 7.x after saving it 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 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 before 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 - End User Issues

Double-byte characters may appear incorrectly on Japanese operating systems when using Internet Explorer 6

When searching for LiveCycle Rights Management ES users on Japanese operating systems by using Internet Explorer 6, some double-byte characters in user names do not appear correctly.
Back to Contents

Reversing name order ** Updated for LiveCycle ES Update 1 Service Pack 3 **

By default, the LiveCycle 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 you make this change, all new users' names are 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. Edit the following section in 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 by using Acrobat Professional 7.x, the special characters > < ' " & : cannot be used in the Policy Name and Policy Description fields.    
Back to Contents

LiveCycle Rights Management Extensions - End User Issues

Unable to copy content into a PowerPoint 2003 file when the Office clipboard is open and the file has no copy permission applied ** New for LiveCycle ES Update 1 Service Pack 1 **

Generally, it is not possible to copy and paste content from a protected PowerPoint file into an unprotected file. However, with PowerPoint 2003, it is possible to copy and paste within a protected file except when these conditions apply:

• PowerPoint file is protected with "Write" permission and without "Copy" permission.
• Content is copied from a protected file.
• Content is pasted into an unprotected file.
• Content is pasted in the protected file.

With PowerPoint 2007, it is not possible at all to copy and paste within a protected file.
Back to Contents

LiveCycle Workspace ES - End User Issues

Safari 4.0 not supported for LiveCycle Workspace ES ** New for LiveCycle ES Update 1 Service Pack 3 **

Safari 4.0 is not a supported browser for Workspace ES.
Back to Contents

Modifying column settings for Tracking only affects the Audit tab ** New for LiveCycle ES Update 1 Service Pack 3 **

In LiveCycle Workspace ES, you can modify your column settings for the Audit  tab on the Tracking page by selecting Preferences > Manage Column Headings.(See Getting started with LiveCycle Workspace ES > Setting preferences in LiveCycle Workspace ES Help.)  The Audit tab is available when you select an active or completed task from a process in the Tracking page.

These settings do not affect the columns displayed in the list of all tasks for a process in the Tracking page.
Back to Contents

Review & Comment toolbar missing

When a user who has Adobe Reader 8.x (and not Acrobat) installed uses LiveCycle 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 problem, apply the Digital Signatures usage right and also the Commenting usage right to the PDF document.
Back to Contents

Form submission failure saves form to Draft folder

If you try to submit a form and receive an error message that the form submission failed, the form tab may be displayed blank after you close the error message. Although there is no indication, the form and data should be saved to the Drafts folder. You can open the form and try to resubmit it.
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 that have 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

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 that you can directly add comments to on the documentation content.

General Documentation Notes

Updated instructions for creating SSL credentials on WebSphere ** New for LiveCycle ES Update 1 Service Pack 3 **

The instructions provided in the "Creating an SSL Credential" section on page 26 of the Administering LiveCycle ES guide (version 8.2.1.2) contains incorrect information. Creating the credential as currently documented causes the connection from Acrobat to LiveCycle ES to fail.

To avoid this problem, step 9 should indicate that the value entered for the Common Name must be the fully qualified domain name for the LiveCycle server and not the local user account as documented.
Back to Contents

Updated information for the LiveCycle Configuration Manager Help ** New for LiveCycle ES Update 1 Service Pack 1 **

The "Providing the application server details" topic in the LiveCycle Configuration Manager Help incorrectly identifies the default Server Instance Name as 'server1' (for a WebLogic turnkey installation). The actual name is 'LCServer1'.
Back to Contents

 

Updates for LiveCycle Workbench ES Help

Missing information in the "Customizing record and playback behavior" topic ** New for LiveCycle ES Update 1 Service Pack 1 **

In the "Customizing record and playback behavior" topic in the LiveCycle Workbench ES Help, the description of the following two configuration properties for the AuditWorkflowDSC component is missing:

maxNumberRecordingInstances
default value: 50
description: Controls the total number of recordings that the server records.

maxNumberRecordingEntries
default value: 50
description: Controls the total number of steps collected for each recording.

Note: When the maximum is reached, the older recorded elements are removed. The total number of recordings is calculated for all of the processes involved.

Back to Contents

Missing information in the "Customizing record and playback behavior" topic ** New for LiveCycle ES Update 1 Service Pack 1 **

In the "Customizing record and playback behavior" topic in LiveCycle Workbench ES Help, the Preference table is missing the following information:

Preference	Default value	Description
-Dcom.adobe.workbench.unsupported.audit.maxNumberOfStepsToLoad	250	The maximum number of steps for each recording that can play back.

Back to Contents

Missing information in the "getAssociated" topic ** New for LiveCycle ES Update 1 Service Pack 1 **

In the "getAssociated" topic in the LiveCycle Workbench ES Help, the Association Type property is missing the following property description:

linkedToXML: An association between an XDP Document attachment and the XDP data XML file. The attachment must have the aspect xdpAttachment applied to it. This is a many-to-one association, which means that multiple XDP Document attachments can be associated with a single XML file.
Back to Contents

Note: In addition to these association types, the association, "{http://www.alfresco.org/model/content/1.0}contains}", can also be specified as the variable / XPath in the association type.This is an internal association between a space and its children (content and folders). When providing this association as the variable / XPath in the association type, and passing the path/ ID of a folder and the setting isParent = true, a list of node IDs of all of the children of the folder is returned.
Back to Contents

Using file attachments with the Web Services service

Livecycle Workbench ES Help does not contain information about including file attachments in SOAP messages when using the Web Services service in processes. This information is documented in the "Using the Web Services service to invoke LiveCycle ES web services with document parameter values" technical article, which is available in the Adobe Knowledgebase at http://www.adobe.com/go/kb403973.

The technical article describes how to specify document values as operation parameters and, for LiveCycle ES web services, how to specify the format of document values when they are returned in service response messages.
Back to Contents

Missing information in the "setContentAttributes" and "storeContent" topics in LiveCycle Workbench Help

The Aspects List property in the "setContentAttributes" and "storeContent" topics in the LiveCycle Workbench Help is missing the following information:

• An aspect title for each aspect name (the title is provided in brackets):
• document-modifier (Document Modifier)
• document-producer (Document Producer)
• document-consumer (Document Consumer)
• process-attributes (Process Attributes)
• rights-managed (Rights Managed)
• reference (Repository Reference)
• linkable (Adobe PDF Form Data)
• PDFToPDFLink (Associate Documents)
• AdobeForm (Adobe PDF Form)
• attachable (Adobe PDF Form Attachment)
• fillable (Adobe PDF Form Preferences)
• generalclassifiable (General Classifiable)
• dublincore (Dublin Core)
• effectivity (Effectivity)
• emailed (Emailed)
• summarizable (Summarizable)
• versionable (Versionable)
• Names and descriptions of the following aspects:
• XDP Document: Identifies an XDP document
• XDP Document Data: Applied to documents that are created as a result of an XDP Document fill
• XDP Document Attachment: Applied to XDP Document attachments stored in the repository
• Titled: Lets you add a title and description property to the Document Details for a content item

Back to Contents

Updated information for the LiveCycle Configuration Manager Help

• The "Configuring the global document storage directory" topic is missing the following note:
  Note: The DocumentStorage folder is automatically created when the service containers are deployed. You can also manually create this folder.
• The "Configuring LiveCycle Content Service ES for a cluster" topic is missing the description for the Index Root Directory field. In this field, you must specify the indexes directory that LiveCycle Content Services ES uses.
• The "Initializing the LiveCycleES database" topic provides an incorrect default WebLogic service port number. The actual default port number for WebLogic 9.2 is 7001, and the default port number for WebLogic 10 is 8001.
• The "Configuring LiveCycle Content Services ES for a cluster" topic is missing a description of the LiveCycle Content Services ES JVM arguments. This information is in the "Post-Deployment Activities" chapter of the Configuring LiveCycle ES Application Server Clusters document for your application server.
• The "Configuring LiveCycle Content Services ES for a cluster" topic does not provide the default port for the LiveCycle Content Services ES Cache Listener. The default port is 7800.
• The "Configuring LiveCycle Content Services ES" topic is missing a description of the WebLogic list, where the user needs to select the current version of their WebLogic environment. This topic also includes a description of the Database Type list, which does not appear on the LiveCycle Content Service ES Configuration panel.
• The "Configuring the LiveCycle ES Connectors" topic is missing this section that lists further configurations to be performed in LiveCycle Administration Console:
• IBM Content Manager
• Connection settings
• Principal credentials
• Name of the default IBM CM Datastore

Back to Contents

Updated information about Email Endpoint settings

The Applications and Services Administration Help describes how to configure Email Endpoint settings, including the Input Parameter Mappings settings. The updated description of the Input Parameter Mappings settings is as follows:

Input Parameter Mappings: Used to configure the input that is required to process the service and operation. The two types of input are literal and variable:

Literal: The email uses the value that is entered in the field as it is displayed.

Variable: You can map a string from the email subject, body, header, or sender's email address. To do this, use one of the following keywords: %SUBJECT%, %BODY%, %HEADER%, or %SENDER%. For example, if you use %SUBJECT%, the email subject content is used as the input parameter. To pick up attachments, you can enter a file pattern that the email endpoint can use to select the attached documents. For example, entering *.pdf selects any attached document that has a .pdf file name extension, * selects any attached document, and example.pdf selects any attached document named example.pdf.

Updated information about Signature service settings

The "Signature service settings" topic in the Applications and Services Administration Help lists incorrect default values for the two Revocation Check Style settings. The default value for these settings is BestEffort.
Back to Contents

Updated information for LiveCycle Rights Management ES

• The “About LiveCycle Rights Management ES users” topic in the LiveCycle Rights Management ES Administration Help includes a table listing the permissions that are available to each user. The “Access end-user web pages” permission should also be listed for these users:
  • LiveCycle Rights Management Administrator
  • LiveCycle Rights Management Policy Set Administrator
  • LiveCycle Rights Management Invite User
  • LiveCycle Rights Management Manage Invited and Local User
• The LiveCycle Rights Management ES Administration Help states: "When you delete a policy set, you can no longer view or edit the policies from the set or use those policies to protect documents. However, any documents that were protected by a policy in the set remain policy-protected."

That statement is partially incorrect. When you delete a policy set, policies that were part of the set cannot be applied to new documents. However, you can view the policy information in both the LiveCycle Administration Console and the end-user web pages for policies that are still in use. You can view the policy information from the document detail page for any document protected by the policy. Policies that are still in use can be edited.

• The "Revoking document access privileges" topic, in step 4 states that you can edit the default message text. This information is incorrect; the text cannot be edited.

Back to Contents

Updated information for LiveCycle Forms ES

The following updates for the "Configuring cache settings" topic in LiveCycle Forms ES Administration Help were not available when the Help was written:

• The "To configure in-memory template caching" and "To configure in-memory form rendering caching" procedures indicate that you must restart the Forms service after changing the cache size. You must also restart the Forms service if you select or deselect the Enabled option.
• In the "To configure template resource cache settings" procedure, you must restart the Forms service if you changed the cleanup interval.

Back to Contents

LiveCycle ES ActionScript Reference incorrectly excludes the AbstractProducer, WSDLLoadEvent, and XMLLoadEvent classes and incorrectly includes the CrossDomainRSLItem class

The CrossDomainRSLItem class was included in the Adobe LiveCycle ES ActionScript Reference

The AbstractProducer, WSDLLoadEvent, and XMLLoadEvent classes were excluded from the Adobe LiveCycle ES ActionScript Reference. Information on the missing classes can be found in the Flex 3 ActionScript Reference.

mx.messaging.AbstractProducer
mx.prc.events.WSDLLoadEvent
mx.rcp.events.XMLLoadEvent

Back to Contents

LiveCycle Data Services ES Documentation

The LiveCycle Data Service ES 2.6 Developer Guide and Javadocs have been provided with the LiveCycle ES Update 1 release for use with the new integrated Data Management Service feature. This feature allows you to package and deploy the LiveCycle Data Services ES Data Management service assemblers as LiveCycle ES components that can be called directly or used in LiveCycle ES processes. For more information about this feature, see the "Creating a Data Management Service Component" topic in Programming with LiveCycle ES.

Notice that the stand-alone LiveCycle Data Services ES server is not provided in this release, and only the Data Management Service topics in the Developer Guide and the Data Management Service APIs in the Javadocs are relevant to this release.
Back to Contents

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

When you compile the source code for LiveCycle 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 document 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 LiveCycle 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 LiveCycle 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.

Back to Contents

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

To import and compile the LiveCycle 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 that you extracted the source code from (for example, select the wsSource folder).
5. Click OK and then 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 LiveCycle Workspace ES, select fds.swc (for example, fds.swc from the \forWSCustomization\SWCS folder), and then click Open.
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 –theme lc.css. The location is relative to the Main.mxml file in the project. After you finish typing the text, 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 LiveCycle Workspace ES (or the main MXML file).

14. Return to the Properties for Workspace dialog box and click OK.
15. Select Project > Build Project to compile Workspace ES.

Back to Contents

LiveCycle ES Update 1 and Adobe AIR™

The Adobe AIR™ run-time lets developers use proven web technologies to build rich Internet applications (RIAs) that deploy to the desktop and run across operating systems. Adobe AIR offers an exciting new way to engage customers with innovative, branded desktop applications without requiring changes to existing technology, people, or processes.

LiveCycle ES Update 1 supports the latest version of Adobe AIR 1.1. You can download this version from http://get.adobe.com/air/

Additional resources:

Common questions related to Adobe AIR: http://www.adobe.com/products/air/faq/
System requirements for Adobe AIR: http://www.adobe.com/products/air/systemreqs/
Adobe AIR IT Administration Guide: http://www.adobe.com/products/air/it_administrators/

LiveCycle ES Update 1 provides support for the following use cases with Adobe AIR 1.1 by providing the ability to:

• Invoke LiveCycle ES services (for example, the PDF Generate service) or custom-developed services that are exposed through web services or remoting endpoints from an Adobe AIR application built using Flex 3 or Ajax.
• Render a PDF document or form that was generated by LiveCycle ES Update 1 in an Adobe AIR application built using Flex 3 or Ajax.
• Leverage LiveCycle Data Services ES. Using the SQL database contained in the Adobe AIR run-time, a developer can use the offline support that was introduced in the previous version of Data Services ES to persist data directly to a SQL database. With very little additional code,a developer can use an application that is written to use data management offline with complete access to any data and queries that you executed online by simply specifying a cache ID and either by using the auto-save option or explicitly saving queries or items that you want to persist offline for retrieval later.

Customers should evaluate their enterprise support and deployment requirements when evaluating building applications based on the support currently provided by Adobe AIR. Adobe LiveCycle Enterprise Support does not provide bug fixes or patches for the Adobe AIR run-time.

Additional information for IT administrators is available at http://www.adobe.com/products/air/it_administrators/

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.

Third-party software notices

LiveCycle Forms ES uses a cssparser to load and merge custom CSS provided by the user in HTML rendition. The cssparser is based on CSS2 grammar and is built using JavaCC (Java Compiler Compiler). Forms ES generates certain Mozilla browser specific styles where selectors start with a hyphen (for example, -moz-xxx), which CSS2 grammar does not permit. The cssparser’s grammar is modified to allow a selector to start with a hyphen, and then the parser is rebuilt using JavaCC.

For more information about the cssparser and this change, see the Technical Note posted at: http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403308&sliceId=1.

LiveCycle Output ES required modifications to the LGPL library, specifically, the JCIFS was modified for LiveCycle ES Update 1.

For more information about these changes, see the Technical Note posted at: http://kb.adobe.com/selfservice/viewContent.do?externalId=kb404133&sliceId=1

Back to Contents

Release Notes -- Adobe LiveCycle ES Update 1 (8.2) -- 08/12/2009 9:26 PM