Adobe LiveCycle ES2 Service Pack 2 and LiveCycle ES2.5

Version 9.0.0.2 and 9.5

Release Notes

October 22, 2010

© 2010 Adobe Systems Incorporated and its licensors. All rights reserved.

This file contains important information that was not available when the product documentation was written. Review this information before you run Adobe® LiveCycle® Enterprise Suite 2.5 (ES2.5) or LiveCycle ES2 and additional Service Packs.


Contents

Installation/Upgrade items

LiveCycle modules

Additional items

General

LiveCycle Content Services 9

Solution Accelerators

Installation

LiveCycle Digital Signatures 9 Assembler service

Upgrade

LiveCycle Forms 9

Email Provider
Administration LiveCycle PDF Generator 9 User Management
Performance Issues LiveCycle Process Management 9 XDC Editor

LiveCycle Reader Extensions 9

Documentation
  LiveCycle Rights Management 9

LiveCycle ES2.5 and Adobe AIR

  LiveCycle Workbench 9 & LiveCycle Workbench 9.5 Additional Licenses and Copyrights
  LiveCycle Workspace 9  

Release notes for related products:


General

LiveCycle ES2 Font Bundle Changes [Ref # 2608634]

The fonts included in LiveCycle ES2 Service Pack 1 contain a number of small changes. The Adobe Hebrew, Adobe Arabic, and Adobe Thai fonts contain hinting changes that will slightly improve the shape of some characters. However, while the character shapes may change by one pixel, the line or page spacing will not be affected. These three font families are also larger to reflect the new and improved hinting: Hebrew and Thai are approximately 15% larger; and the Arabic font is 60% larger due to a font optimization error we expect to resolve in a future release. These size impacts will be seen only when the font is embedded in a document.
Back to Contents

Opening a drop-down list within a form [Ref # 1503619]

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 Adobe Acrobat®. Select Edit > Preferences > Forms and deselect Keep forms data temporarily available on disk.
Back to Contents


Installation Issues

General Installation Issues

Stage deployment is not recommended on non-Windows remote servers ** New for 9.0.0.2/9.5 **

If you are installing LiveCycle ES2 Service Pack 1 or LiveCycle ES2 Service Pack 2 for a non-Windows operating system using Windows as the staging platform, the service pack installer downloads Windows-specific native files. Therefore, it is recommended not to perform a stage deployment on a a non-Windows remote server.
Back to Contents

Apple® Safari 5.0 not supported for Workspace [ Ref # 2699806] ** New for 9.0.0.2/9.5 **

Apple Safari 5.0 is not supported for accessing Adobe LiveCycle Workspace 8.2 and LiveCycle Workspace 9. For more information, see the Unexpected issues when using Safari 5.0 with LiveCycle Workspace ES and Workspace ES2 technical note.
Back to Contents

Uninstalling Service Pack 2 on Windows 7 [Ref # 2696782] ** New for 9.0.0.2 **

To revert your LiveCycle ES2 server installation on Microsoft® Windows® 7 to a pre-Service Pack 2 state, follow the instructions in the Adobe LiveCycle ES2 Service Pack 2 Install Instructions and Fixed Customer Issues document available from the LiveCycle ES2 Service Pack site.
Back to Contents

Installing Workbench to Eclipse on 64 bit systems [Ref 2696261] ** New for 9.5 **

To install Adobe LiveCycle Workbench 9.5 to Eclipse on a 64 bit operating system, you must use a 32 bit version of Eclipse.
Back to Contents

Form rendering issues when Package JDBC Modules option is used in WebLogic [Ref # 2615315]

You may experience form rendering issues for fragmented forms if you use the Package JDBC Modules (secure datasources) option when you configure your LiveCycle ES2 installation on WebLogic using Adobe LiveCycle Configuration Manager.

To secure data sources, use the alternative method described in the tech note: http://kb2.adobe.com/cps/844/cpsid_84435.html
Back to Contents

Additional libraries required for SUSE Linux 11 [Ref # 2576692]

If your LiveCycle ES2 installation is on SUSE® Linux® 11, you must also install the libstdc++-libc6.2-2.so.3 libraries on your SUSE Linux 11 server. SUSE Linux 11 does not include these libraries by default. For more information, see http://www.novell.com/products/linuxpackages/desktop11/x86_64/compat-32bit.html. These libraries are required for running Adobe Central Pro Output Server.
Back to Contents

install.bin fails to launch on Red Hat Enterprise Linux [Ref # 2471042]

When you try to run the install.bin executable from the LiveCycle ES2 DVD on a machine running Red Hat® Enterprise Linux, the following error message appears:

/bin/sh:bad interpreter: Permission denied

This occurs because Red Hat Enterprise Linux auto-mounts the DVD with noexec permissions. To resolve this issue and start the LiveCycle ES2 installation, perform these steps:

  1. Unmount the drive by entering the following command:
  2. umount /media/CDROM

  3. Remount the drive manually by completing the following tasks:
Back to Contents

Do not use special characters in DVD image path [Ref # 2463625]

If you copy the LiveCycle ES2 DVD image locally before installing the product, do not use special characters such as the number sign character (#) in the local path. Otherwise, the appropriate license information may not be displayed during the installation.
Back to Contents

Characters that are not supported in the installation path [Ref # 1809089]

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

MD5 encryption for LiveCycle ES2 ESD download [Ref # 1675320]

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

LiveCycle Configuration Manager Installation Issues

Errors to ignore while deploying the DSC component [Ref # 2704130, 2696040] ** New for 9.0.0.2 **

You can ignore the following errors when deploying the DSC component using LiveCycle Configuration Manager:

Back to Contents

LiveCycle Configuration Manager removes JDBC providers and data sources for clusters in the same cell [Ref # 2696184] ** New for 9.0.0.2 **

When you run LiveCycle Configuration Manager to configure data sources for a LiveCycle cluster in a cell that contains multiple LiveCycle clusters, LiveCycle Configuration Manager removes JDBC providers and data sources for other clusters in the cell.
Back to Contents

LiveCycle Configuration Manager may fail to deploy LCAs when using Express mode [Ref # 2475109]

LiveCycle Configuration Manager may fail to deploy LCAs when running in Express mode. If you receive this error, LiveCycle Configuration Manager will not allow you to proceed and the Next button will be disabled. To workaround this issue, rerun the LiveCycle Configuration Manager and select Custom mode. Then, select Configure Components and Import samples. You may encounter this issue when configuring Adobe LiveCycle Content Services 9 without Adobe LiveCycle Process Management 9.
Back to Contents

Need to use correct host name format when configuring application server in LiveCycle Configuration Manager [Ref # 1755731]

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

Deployment of EAR files continues after the user exits LiveCycle Configuration Manager prematurely [Ref # 1574469]

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 [Ref # 1574488]

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

JBoss restart issue with Mosaic.war [Ref # 2718415] ** New for 9.5 **

A JBoss Turnkey installation fails to start if you copy the Mosaic.war file to the <Adobe LiveCycle ES2>\jboss\server\lc_turnkey\deploy folder and try to restart JBoss. To fix this issue, update the Java JDK version to 1.6.0_21.
Back to Contents

JBoss issue causes incorrect text to appear during Japanese LiveCycle ES2 configuration [Ref # 2427415]

When running the Japanese version of LiveCycle Configuration Manager, the status text on the Database Initialization screen appears as "?????". This is due to a known issue with JBoss Web as discussed on this user forum: http://www.jboss.org/?module=bb&op=viewtopic&t=103446.
Back to Contents

WebLogic Installation Issues

Database user name restrictions for Oracle databases [Ref # 1489967]

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

WebSphere Installation Issues

Installation and configuration issues with WebSphere 7.0.0.7 [Ref# 2628686] ** New for 9.0.0.2 **

If you are using the WebSphere Application Server version 7.0.0.7 for your LiveCycle ES2 setup, then you may encounter the following issues:

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

NullPointerException in POFQuery when upgrading LiveCycle 7.x to LiveCycle ES2 [Ref # 2583736]

When you upgrade your LiveCycle 7.x server to LiveCycle 8.x, and later upgrade to LiveCycle ES2, workflows that use the POFQuery taskQry.addFilter(BOITask.A_ACTION_INSTANCE_ID, POFFilter.EQUALS, (String)null); fail with a NullPointerException.

To avoid this issue, modify this query to check for 0 rather than null on A_ACTION_INSTANCE_ID, as follows: taskQry.addFilter(BOITask.A_ACTION_INSTANCE_ID, POFFilter.EQUALS, 0);
Back to Contents

ClassNotFoundException in server logs after applying LiveCycle ES2 Service Pack 1 (9.0.0.1) [Ref # 2552540]

Several ClassNotFoundException errors related to applicationmanager appear in the server logs after applying LiveCycle ES2 Service Pack 1. A typical log message is

[com.adobe.idp.applicationmanager.service.TLOHandlerRegistryServiceImpl] ClassNotFoundException thrown while loading handler with class name:

You can safely ignore these errors. These errors do not appear after you restart LiveCycle server.
Back to Contents

Upgraded LiveCycle database on DB2 does not support hot backup [Ref # 2428516]

If you upgraded your LiveCycle system from LiveCycle ES (8.0.1.x) or earlier to LiveCycle ES Update 1 Service Pack 1 or later and your database is IBM DB2®, then the LiveCycle database schema for DB2 does not support hot backups and recoveries in case of a media failure.

For more information about this issue and a solution, see the tech note at http://kb2.adobe.com/community/publishing/521/cpsid_52128.html.
Back to Contents

Upgrading from JBoss 32-bit to 64-bit [Ref # 2468586]

If you are upgrading from a LiveCycle ES (8.x) configuration running on a 32-bit operating system with JBoss 4.2.0, you should upgrade to JBoss 4.2.1 with 64-bit JDK 1.6.0_14 on a 64-bit operating system rather than to JBoss 4.2.0 with 64-bit JDK 1.5. Upgrading to JBoss 4.2.0 with 64-bit JDK 1.5 may causes errors in LiveCycle ES2.
Back to Contents

New location for LiveCycle 7.x QPACs [Ref # 1666092]

The LiveCycle 7.x QPACs that are required for LiveCycle 7.x compatibility are not installed with the LiveCycle Workbench 9 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

LiveCycle Workbench 9 Upgrade Issues

Workbench appears frozen when editing operation properties for a 7.x process (WebSphere only) [Ref # 2420153]

When editing operation properties for a 7.x process in LiveCycle Workbench 9, if an incorrect value is entered, an error message appears. However, because this error message is displayed behind the Workbench window, Workbench appears to be frozen. You must acknowledge the error by pressing Alt+Tab to move the error message to the front and clicking OK.
Back to Contents


Administration Issues

New just-in-time provisioning of LiveCycle ES2 users [Ref # 2686868] ** New for 9.0.0.2/9.5 **

Beginning with LiveCycle ES2 Service Pack 2 (9.0.0.2), LiveCycle ES2 supports just-in-time provisioning of users that do not yet exist in User Management. Just-in-time (JIT) provisioning creates new users dynamically in User Management once an authentication provider has successfully authenticated their credentials. Additionally, relevant roles and groups are assigned on-the-fly to the new user.

Read this TechNote to understand and implement this feature.
Back to Contents

Indirect method for accessing Help for some LiveCycle ES2 or LiveCycle ES2.5 components [Ref # 2716898] ** New for 9.0.0.2/9.5 **

The following links on the LiveCycle Administration Console Help page do not work as intended:

To access Help for these components, follow these steps:

  1. Log into LiveCycle Administration Console and click Settings.
  2. Click User Management, Trust Store Management, or Core System Settings, as necessary.
  3. On the page that appears, click the Help link in the top-right corner of the page.

Back to Contents

0 is not a valid value for the Purge Completed Records Filter area [Ref # 2657165] ** New for 9.0.0.2 **

The "Purge records from the Job Manager database" topic in the LiveCycle ES2.5 Administration Help incorrectly states that 0 is a valid value for the Purge Completed Records Filter area on the Health Monitor > Job Purge Scheduler tab in LiveCycle Administration Console. 0 is not a valid value for the area.
Back to Contents

User credentials for running your application server [Ref # 2700939] ** New for 9.0.0.2 **

(Windows Server® 2008) Your application server can be run using any account with Administrator credentials (local or domain level). The restriction to use only the Local System Account no longer applies.
Back to Contents

Throttling: Batch size does not scale to multiple nodes in the cluster [Ref # 1578206]

In a cluster configuration, the batch size for a watched folder endpoint does not scale to multiple cluster nodes. For example, if the batch size is set to "2" for a two-node cluster and the Throttle option is selected, the nodes process files collectively in batches of two instead of each node processing two files at a time.
Back to Contents

Performing searches in LiveCycle ES2 [Ref # 1928895]

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

Underscore characters not allowed in host name [Ref # 1567895]

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

(Windows, Japanese, IE) Some LiveCycle Administration Console links fail when server name contains underscore [Ref # 15700808]

While running LiveCycle Administration Console from an Internet Explorer browser, you may encounter the following errors:

Run LiveCycle Administration Console from another browser, such as Mozilla Firefox, to ensure that no links will fail.
Back to Contents

LiveCycle ES2 archive files may not be backward compatible (Archive Administration) [ Ref # 1658103]

There is a known issue that LiveCycle ES2 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 ES2 (for example, a preview release), doing so is not supported and may result in aberrant behavior.
Back to Contents

Oracle database maximum open cursors threshold (Database Management ) [Ref # 1774883]

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


Performance Issues

General Performance Issues

Quartz Scheduler issue with a cluster and DB2 database [Ref # 1841089]

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

Process Management performance issue [Ref # 2536127]

Process Management throughput for Oracle databases deteriorates over time at moderate load levels.
Back to Contents


Solution Accelerators

Solution Accelerators cannot be installed on a vertical cluster ** New for 9.5 **

The Managed Review & Approval Solution Accelerator 9.5 and Correspondence Management Solution Accelerator 9.5 cannot be installed on a vertical cluster.
Back to Contents

Solution Accelerators datasource is not configured for JBoss Turnkey [Ref # 2714612] ** New for 9.5 **

Datasource for Solution Accelerators might not get configured successfully if you used the Turnkey mode while installing LiveCycle ES2.5 and configured a non-default port for your MySQL database. This is because when you run the Solution Accelerators installer, it configures the default port (3306) used for MySQL database in the datasource configuration file for Solution Accelerators.

To configure Solution Accelerators, you must change the port number in the adobe-sa-ds.xml file located at [appserver root]/server/all/deploy directory and restart JBoss.
Back to Contents

Correspondence Management Solution Accelerator

Zoom in the Create Correspondence UI **New for 9.5 **

When working in the Create Correspondence UI of the Correspondence Management Solution Accelerator, ensure that your browser displays the pages at the default (100%) zoom level. Zooming in or out will distort the page.
Back to Contents

Managed Review and Approval Solution Accelerator

Correction in a setting name for the Review, Commenting, and Approval service ** New for 9.5 **

In the "Review, Commenting, and Approval service settings" topic in the Managing Services section of the LiveCycle ES2.5 Administration Help, the reference to the "Name of the process to prepare a document for PDF shared review" setting should be "Name of the process to prepare a document before enabling it for shared review".
Back to Contents

New setting for the ReviewZoneProviderService ** New for 9.5 **

Refer to the "Review Zone Provider service settings" topic in the Managing Services section in LiveCycle ES2.5 Administration Help.

A new setting, Enable Contribute Permission, is available for this service. The default value for this setting is True.

Enabling this new setting lets you perform the following actions:

Note: Custom Review Zone Provider implementations for some content management systems may not support the Enable Contribute Permission.

For more information about this setting, refer to the Review, Commenting, and Approval Technical Guide.
Back to Contents

Interactive Statements Solution Accelerator

The <id > attribute and <name> child element are required for calling the Assembler service [Ref # 2701191] ** New for 9.5 **

When you manually create navigator files for interactive statements, you must add the <id > attribute and <name> child element in the navigator.xml file.

Read this TechNote for more information about this issue.
Back to Contents

Interactive Statements does not support using mixed versions of the Flex SDK when creating components [Ref # 2661169] ** New for 9.5 **

Using different versions of the Flex SDK or an incompatible version of the Adobe Flex® SDK for creating different components causes the interactive statement to fail. When creating components for Interactive Statements, use the Flex 3.0.1 SDK.
Back to Contents

Interactive Document Project option does not automatically appear in the File > New menu [Ref # 2635035] ** New for 9.5 **

When you install the Adobe Asset Placement Plug-in for Flash® Builder 4, the Interactive Document option does not appear when you select File > New. To see this option, select File / New / Other..., and select Interactive Document Project.
Back to Contents


LiveCycle Content Services 9

Incomplete export using the Export ACP functionality ** New for 9.0.0.2 **

The package (.acp/.zip) that is created while exporting a large set of content from a space may be incomplete and may not contain all of the content that was exported. Additionally, the application server may become unresponsive if the export is initiated on a large content set. In such an event, you may need to restart the server.

The size of the content that can be exported successfully depends on the system configuration. As a workaround, try to export content in smaller sets.
Back to Contents

Error while adding permissions to a group having a long group name [Ref # 2723531] ** New for 9.0.0.2 **

A com.mysql.jdbc.MySQLDataTruncation error is returned if you try to assign a permission to a user or group with a name longer than 100 characters, either through the Adobe LiveCycle ContentSpace 9 UI or through the Content Services APIs. To resolve this issue, reduce the length of the common name of the user or the group name of the group.
Back to Contents

Exceptions while importing an ACP [Ref # 2697573] ** New for 9.0.0.2 **

SQL exceptions are encountered while importing an Alfresco Content Package (ACP) using Contentspace for the DB2 database. Follow these steps to resolve the exceptions:

  1. Connect to the DB2 database instance using IBM Control Centre.
  2. In IBM Control Center, expand All Databases and then right-click your database instance. Select Configure Parameters from the context-menu.
  3. Log in using your credentials for the database instance.
  4. In the Database Configuration dialog box, click Logs.
  5. Navigate to LOGSECOND in the Logs tree and change its value to 240 or a higher number. Ensure that LOGPRIMARY + LOGSECOND <= 256.
  6. Click Apply, and then OK.
  7. Restart the database instance.

Back to Contents

Content Services EAR deployment failure on updating to LiveCycle ES2 Serivce Pack 2 [Ref # 2654394] ** New for 9.0.0.2 **

Important: This note is applicable only if you are updating from LiveCycle ES2 or LiveCycle ES2 Service Pack 1 to LiveCycle ES2 Service Pack 2.

While configuring Content Services using the LiveCycle Configuration Manager, you must specify the content storage root directory. In LiveCycle ES2 or LiveCycle ES2 Service Pack 1, LiveCycle Configuration Manager automatically creates a subdirectory, lccs_data, under the content storage root directory. For example, if you specified C:\test\ as the content storage root directory on a Windows machine, LiveCycle Configuration Manager creates the lccs_data subdirectory and specifies the path as C:\test\lccs_data\ in the Content Services EAR file. Note that lccs_data is appended only if you have not already specified it using the LiveCycle Configuration Manager GUI or command-line interface.

This behavior has been reverted in LiveCycle ES2 Service Pack 2. Now, LiveCycle Configuration Manager takes the value of the content storage root directory exactly as specified on the LiveCycle Configuration Manager GUI or command-line interface. Therefore, when you update to LiveCycle ES2 Service Pack 2 and redeploy the Content Services EAR file, LiveCycle may fail to find the content storage root directory path resulting in a Content Services EAR deployment failure.

To avoid the deployment failure, you must append lccs_data to your content storage root directory when configuring the Content Services EAR file using the LiveCycle Configuration Manager GUI or command-line interface for LiveCycle ES2 Service Pack 2.
Back to Contents

Content-based search within Microsoft Office 2007 documents requires PDF Generator [Ref # 2688938] ** New for 9.0.0.2 **

If Adobe LiveCycle PDF Generator 9 is not installed as part of your LiveCycle ES2.5 installation, content-based search does not work for Microsoft Office 2007 files (PPTX, DOCX, XLSX, etc.).
Back to Contents

Show In Contents icon does not work for localized Help [Ref # 2442397] ** New for 9.0.0.2 **

If you click the Show In Contents icon in the localized Help, the current open topic is not highligted in the Contents pane.
Back to Contents

Some documents in a space are not listed in Contentspace [Ref # 2586923] ** New for 9.0.0.2 **

If more than 10,000 documents are present in a space, some of them may not be listed when you browse that space in Contentspace.
Back to Contents

Navigating or deleting objects created using AssetManager [Ref # 2664780] ** New for 9.0.0.2 **

Do not use Contentspace to navigate or delete objects created using AssetManager. Instead, use AssetManager APIs to navigate or delete these objects.
Back to Contents

Search result behavior for strings containing tokenizers or stop words [Ref # 2709008] ** New for 9.0.0.2 **

Contentspace search does not return the expected results if the search string contains a tokenizer or stop word. The following sections document the search behavior for strings containing tokenizers and stop words.

Results for search strings containing a tokenizer

Dot(.), Colon(:), Single quote(‘), whitespace( ), hyphen(-), underscore(_), and double quotes(“) are tokenizers.

Assuming 'a' and 'b' are any valid strings, the following table summarizes the search result behavior for a search string containing a sample tokenizer, '.':

Search Query Query result Data example Result
a.b a.b a, a.b, a.c, b.a, ab, .b, a. a.b
a. All data with 'a' and a tokenizer or simply 'a' a, a.b, a.c, b.a, ab, .b, a. a, a.b, a.c, b.a, a.
.b All data with 'b' and a tokenizer or simply 'b' a, a.b, a.c, b.a, ab, .b, a. a.b, b.a, .b
a All data with 'a' and a tokenizer or simply 'a' a, a.b, a.c, b.a, ab, .b, a. a, a.b, a.c, b.a, a.
a*b “*” does not consider any tokenizer as part of the character set a, a.b, a.c, b.a, ab, .b, a. ab

Results for search strings containing a stop word

"a", "an", "and", "are", "as", "at", "be", "but", "by", "for", "if", "in", "into", "is", "it", "no", "not", "of", "on", "or", "such", "that", "the", "their", "then", "there", "these", "they", "this", "to", "was", "will", and "with" are stop words.

The following table summarizes the search result behavior for a search string containing a sample stop word, 'A':

Search Query Query result Data example Result
*A* or *a* All data except for stop words bac, bAc, A, Ac, cA bac, bAc, Ac, cA
A* or a*/ *A or *a Data with 'A' as a suffix or a prefix (corresponding to the query), but not A itself bac, bAc, A, Ac, cA Ac/cA respectively
A Empty bac, bAc, A, Ac, cA Empty

Note: Contentspace searches are case insensitive.

Back to Contents

Disabling automatic propagation of events [Ref # 2417727]

By default, Content Services events are automatically propagated to LiveCycle ES2. To improve performance, automatic propagation can be disabled by setting the JVM argument "propagateEventsToLC" to false.
For more information, see the "Configuring the JVM arguments" section of the "Manually configuring system name" appendix in the Installing and Deploying LiveCycle ES2 guide for your system.
Back to Contents

Content Services does not index policy-protected documents [Ref # 1837269]

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

WebDAV connections to Content Services repositories from Windows 7 clients are unsupported [Ref # 2673461, 2608923, 2643357] ** New for 9.0.0.2 **

You cannot connect to a Content Services repository from a Windows 7 client using the WebDAV protocol.
Back to Contents

No warning message to indicate that support for Reader Extensions is not specified [Ref # 2436487]

When initiating an ad hoc review, Contentspace does not notify you if support for Adobe LiveCycle Reader Extensions 9 has not been specified. You are only notified after you have finished initiating the review. If your review requires support for Reader Extensions, select Advanced Options > Apply Reader Extensions Process.
Back to Contents

Restricting viewing of comments to only the review initiator does not work [Ref # 2436729]

When creating a review, you can specify that only the review initiator sees all comments. This option does not work in the case where the initiator adds new comments or responds to comments provided by other reviewers. In this situation, all participants see the review initiator’s comments.
Back to Contents

Error when a large number of users are found by a search [Ref # 2411312]

In Content Services, when you search for users using a search criteria that returns more than 500 users in the results, the following error is displayed, ""Too many users match by your search. Please narrow your search and try again". For example, if your domain contains more than 500 users whose names begin with "T" and you search for all users whose names begin with "T", you see this error. Try using more specific search criteria to narrow the results.
Back to Contents


LiveCycle Digital Signatures 9

Server restart is required after revoking or assigning a partition to an HSM client [Ref # 2724659] ** New for 9.0.0.2 **

If you create a new Hardware Security Model (HSM) credential profile, a partition assigned or revoked to the HSM client does not reflect in the LiveCycle Administration Console until the LiveCycle server is restarted.
Back to Contents

Signature service does not support XDP files with embedded PDF data [Ref # 1374301]

The Signature service in Adobe LiveCycle Digital Signatures 9 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


LiveCycle Forms 9

SignablePrintPDF warning when flattening a form [Ref # 2612974] ** New for 9.0.0.2 **

If you are using an earlier version of Adobe Reader than 9.0, then the SignablePrintPDF warning is logged irrespective of whether or not your form contains a signature field. This is because, by default, the Retain Signature Field is set to True and needs to be reset explicitly.
Back to Contents


LiveCycle PDF Generator 9

Uploading local files to LiveCycle PDF Generator 9 [Ref # 2526963]

LiveCycle PDF Generator 9 enables you to convert HTML files to Adobe PDF. You can upload files using the HTML to PDF page in LiveCycle Administration Console.

In previous releases of LiveCycle, you could upload a file by specifying a URL in the format file:///c:/test.html. This behavior poses a security risk, so beginning in LiveCycle ES2, you can no longer specify a URL that opens a file on the local file system. To upload a file from the local file system, use the Upload File option on the HTML to PDF page.
Back to Contents

generatePDFOutput method does not specify the required Content Root URI structure [Ref # 2590586]

When you pick a form from your application, the Content Root URI path must have the correct structure. For example, if a form is picked from an application, SampleApp, and is placed at SampleApp/1.0/forms/Test.xdp, the Content Root URI must be specified as:

repository://authority/Applications/SampleApp/1.0/forms/ or repository:/Applications/SampleApp (when authority is null).

Then, the paths of all of the referenced assets in the form will be resolved against this URI.
Back to Contents


LiveCycle Process Management 9

Task assignments to a user or user group fail even though the user domains in the development and production environments are configured exactly the same [Ref # 2570872] ** New for 9.5 **

If a process that was tested in a development environment is executed in a production environment, the task assignment to a user or group fails even though the user domains in the development and production environments are configured exactly the same. The process is also not transferable to another computer (production environment) that had the same user or group added in the LiveCycle Administration Console. To resolve this issue, do one of the steps below:

Back to Contents


LiveCycle Reader Extensions 9

Extended features on a PDF form are disabled in Internet Explorer 8 when Adobe Reader 9.3.2 is installed [Ref # 2609256]

When you open a PDF document that has static forms and additional rights enabled with Reader Extensions in Internet Explorer 8, additional usage rights are disabled. This occurs when Adobe Reader 9.3.2 is installed on the computer. As a workaround, you can either make the form dynamic, or use compatibility mode for Internet Explorer 8 for the page URL.
Back to Contents

Review & Comment toolbar missing [Ref # 1649268]

When a user who has Adobe Reader 8.x (and not Acrobat) installed uses Workspace 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 apply usage rights to files using some special characters in file name [Ref # 1563953]

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 9

LiveCycle Rights Management does not support CATIA file format [Ref # 3126889]

LiveCycle Rights Management does not support the CATIA file format, contrary to what the documentation set mentions.
Back to Contents

Enabling automated testing of the pages based on Flash in Rights Management 9 [Ref # 2442835]

Some of the pages in the Adobe LiveCycle Rights Management 9 UI (such as the New Policy page) are based on Adobe Flash. To use these pages in automations created with QuickTest Professional, perform the following procedures.

To enable QuickTest Professional automation with the Rights Management pages in the LiveCycle Administration Console:

  1. Log into LiveCycle Administration Console.
  2. Click Service > LiveCycle Rights Management ES2.
  3. In the browser address bar, change the URL to http://[server]:[port]/edc/admin/enableQTP and press Enter. This enables you to use QTP automation in the current user session.
  4. To disable QTP automation for this user session, go to http://[server]:[port]/edc/admin/disableQTP.

To enable QuickTest Professional automation with the Rights Management end user web application:

  1. Log into the Rights Management end user web pages.
  2. In the browser address bar, change the URL to http://[server]:[port]/edc/enableQTP and press Enter. This enables you to use QTP automation in the current user session.
  3. To disable QTP automation for this user session, go to http://[server]:[port]/edc/admin/disableQTP.

Back to Contents

Limitations regarding Greek Latin and Greek Extended characters [Ref # 2415220]

Greek Latin or Greek Extended characters are not displayed properly in the policy name and description fields of the Rights Management policy creation page.
Back to Contents


LiveCycle Workbench 9 and LiveCycle Workbench 9.5

Configure applications with 50 assets or less [Ref # 2717377] ** New for 9.5 **

You can add various assets to a LiveCycle application that includes image files, DDX files, processes, and forms. It is recommended that each application contains 50 assets or less. For existing applications with 50 or more assets, partition them into smaller applications. When you keep the number of assets small, it improves application performance and maintainability.
Back to Contents

Properties panel for Chain QPAC component appears only for the first time in LiveCycle Workbench 9.5 [Ref # 2462874] ** New for 9.5 **

With LiveCycle ES2.5 on WebSphere, if you open a Chain QPAC component in a LiveCycle 7 application in LiveCycle Workbench 9.5, the Properties panel displays the component's properties for the first time. However, if you close the Properties panel, you are unable to reopen it. As a workaround, restart Workbench.
Back to Contents

Tasks from Assign Multiple Tasks not visible to Workspace users [Ref # 2720930] ** New for 9.5 **

Tasks are not visible to users the first time they log into Workspace. This occurs when the task assigned to users from a human-centric process contains an Assign Multiple Tasks operation (User 2.0 service) and those users are assigned more than once as a participant. In a subsequent execution of that human-centric process, users will see the tasks assigned as expected.

For example, ProcessA assigns User1 twice in an Assign Multiple Tasks operation in a process. User1 logs into Workspace for the very first time and will not see a task assigned from ProcessA. When ProcessA executes again, User1 will see the task appear in their To Do list.

To alleviate this problem, ensure that Workspace users log into Workspace before being assigned tasks, or ensure that you do not add a participant more than once in an Assign Multiple Tasks operation.
Back to Contents

Deploying a process with a byte variable crashes LiveCycle Workbench 9.5 [Ref # 2695071] ** New for 9.5 **

LiveCycle Workbench 9.5 crashes when deploying an application that contains a process with a byte variable set to a LiveCycle ES2 Service Pack 1 server. To resolve this issue, update the server to LiveCycle ES2 Service Pack 2.
Back to Contents

LiveCycle Workbench 9.5 hangs [Ref # 2700334] ** New for 9.5 **

Running more than one instance of LiveCycle Worbench 9.5 on a computer causes it to hang.You cannot run more than one instance of Workbench on the same computer, regardless if it is run with two different users profiles.
Back to Contents

Cannot import a LiveCycle archive file [Ref # 2695252] ** New for 9.5 **

Importing a LiveCycle archive file where the application contains a folder named components fails. To resolve this issue, rename the folder in the LiveCycle application to another name other than components, recreate the archive file, and reimport the file to the LiveCycle server.
Back to Contents

Cannot create link files to the file system in LiveCycle Workbench 9.5 [Ref # 2698682] ** New for 9.5 **

In LiveCycle Workbench 9.5, when the following steps are performed, an error occurs stating "Project '<Name of connected server>' is mapped to repository type 'com.adobe.livecycle.lcteam' which does not support linked resources.":

  1. Select File > New > Other.
  2. Select General > File.
  3. In the New File dialog box, in the File Name box, type a name, such as test.txt.
  4. Click Advanced and select Link To File In The File System.

You cannot link files directly to the file system.
Back to Contents

Preserving Relationships in your form after versioning your LiveCycle ES2 application ** New for 9.5 **

You must upgrade your LiveCycle ES2 server to LiveCycle ES2 Service Pack 2 to preserve the Relationships in your form when your application is versioned in LiveCycle Workbench 9.5.
Back to Contents

Error when previewing a Guide that references an image with a high ASCII or DBCS in the filename [Ref # 2664084] ** New for 9.5 **

The following error message appears when previewing a Guide that references an image with high-ASCII or double-byte characters in the filename, and the image does not display:

Error #2044: Unhandled IOErrorEvent:.text=Error #2124; Loaded file is an unknown type.

The error occurs only when previewing the Guide. When the Guide is deployed and rendered in Workspace, there are no errors and the image appears in the Guide.
Back to Contents

Unable to play a Help video that contains double-byte or extended characters in the filename [Ref # 2654909] ** New for 9.5 **

When a Guide includes a Help video that contains double-byte or extended characters in the filename, the video does not play. Before adding a video to a Guide, ensure the video plays and rename the video filename to remove any double-byte or extended characters.
Back to Contents

Preview fails when using Internet Explorer 8 if localhost is used for the Workbench connection [Ref # 2609381] ** New for 9.5 **

Previewing a Guide fails when Internet Explorer 8 is the default browser and you are connecting to the server using localhost.

Current workarounds include:

Back to Contents

Relative URIs are broken after upgrading to Service Pack 1 [Ref # 2599240]

The LiveCycle ES2 Service Pack 1 patch addresses problems encountered when using relative URIs (for example, far references or references to assets in other applications). An example would be a form that references a form fragment in another application. After upgrading, you must open the application or form, and manually re-create the URIs to incorporate the fixes.
Back to Contents

The New (asset) wizard displays an incorrect folder structure [Ref # 2590089]

In LiveCycle Workbench 9, while creating an asset of type Other (File -> New -> Other), the Enter Or Select The Parent Folder box displays a tree structure corresponding to the computer's file system, and not the Workbench Applications view.
Back to Contents

Referenced subprocess points to the previous version of the application [Ref # 2459254]

When creating a new version of an existing application, the main process correctly points to the subprocess in the new version. However, after updating the new version of the application, the main process incorrectly references a supbrocess in the original version of the application. This reference needs to be manually updated for the process to run.
Back to Contents

References broken in new process version created using Archive Wizard [Ref # 2451890]

When a process created using Archive Wizard references a document that is located in a local application, after creating a new version of this process, the reference is broken. You must manually update the reference to the correct version of the document.
Back to Contents

References in copied assets point to old location [Ref # 2450779]

When an asset that references another asset is copied to a different location (such as another folder or application), the reference still points to the asset at the old location. For example, if a process that has a variable referencing a document originally located in the same application or folder is copied to a new folder or application where the referenced document does not exist, the process will fail because the referenced document will not be found at runtime.
To avoid this issue, after copying an asset to a new location, update any existing references.
Back to Contents

Using assets from different LiveCycle versions in the same application [Ref # 2443017]

Imported LiveCycle ES (8.x) assets and assets created in LiveCycle ES2 must not be included in the same application. Otherwise, deployment and execution of the application may fail in certain circumstances.
Back to Contents

Referencing remote assets using variables [Ref # 2446602]

A document variable is used in the process to reference a remote asset located in another application. If this variable is marked as an input variable, and the user does not have sufficient rights to access the remote asset, the step in the application results in an error. To resolve this issue, either assign sufficient rights to the user or do not make the variable an input variable.
Back to Contents


LiveCycle Workspace 9

Customizing Workspace [Ref # 2611983]

You can customize Workspace after you apply LiveCycle ES2 Service Pack 1 or LiveCycle ES2 Service Pack 2. For information on how to obtain these service packs, refer to your Maintenance and Support welcome package or to the Customer Support portal for contact details.

For information about customizing Workspace, see Customizing the LiveCycle Workspace ES2 User Interface.
Back to Contents


Assembler service

Linked images in Designer applications are not resolved [Ref # 2591025, 2612440]

The images that you link to from Adobe LiveCycle Designer 9 by providing a relative path in an XFA template are stripped out when you flatten or convert the form to PDF or PDF/A format. The following workarounds are available:

Adobe is investigating the issue and will post an update once it is resolved.
Back to Contents

Assembler service for certificate removal drops currency symbols [Ref # 2536870]

When the Assembler service processes DDX that removes certificates from resultant PDF documents, it calls the Signature service. If the Signature service is configured to enable Acrobat 9 compatibility on the documents it processes (the default setting), then the currency symbols $ or ¢ from the original document are absent in the resultant document. There is no known workaround.


Email Provider

Limitations to Email endpoints with multiple file attachments [Ref # 1395020]

The following limitations exist when using email endpoints to invoke services:

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

Invoking the Generate PDF service or the Distiller service using email provider [Ref # 1569980]

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


User Management

Consuming the WSDL for Generate PDF on a WebSphere Application Server cluster causes an authentication error [Ref # 1573116]

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


XDC Editor

XDC file check in/check out issue [Ref # 2438722]

XDC Editor incorrectly allows you to save the changes that you made to an XDC file without checking it out. To avoid this, check out the file before you edit it.
Back to Contents

XDC file is not saved when changes are made after the file is checked in [Ref # 2438692]

You must save the XDC file before you check it into the LiveCycle application and deploy the application. Checking in without saving the XDC file does not automatically save any changes you have made.
Back to Contents


Documentation

The LiveCycle ES2 and LiveCycle ES2.5 product documentation is available online on the Adobe website at www.adobe.com/go/learn_lc_documentation_9.

LiveCycle does not support CATIA file format [Ref # 3126889]

LiveCycle does not support the CATIA file format, contrary to what the documentation set mentions.
Back to Contents

Error in Workspace help [Ref# 2609138] ** New for 9.0.0.2 **

In the "Starting new processes from existing task data" topic, step 2 incorrectly refers to a button named Start a new process with this Task data. In LiveCycle Workspace 9 Service Pack 1, the button was renamed Start. The sentence in step 2 should read: Click Start. The form and data for the task is displayed.
Back to Contents

Additional information about key rollovers [Ref # 2432580]

The "Configuring offline security" topic in the LiveCycle ES2.5 Administration Help describes how to roll over principal keys. If a principal key is believed to be compromised, key rollover can help limit damage. In order to invalidate all existing principal keys, you must roll over the keys twice because two generations of principal keys are valid at the same time. See the help for details on performing the key rollovers.

In the following example, Key1 is the older of the two principal keys, and Key2 is the newer one. When you click the Rollover Keys Now button the first time, Key1 becomes invalid, and a newer, valid principal key (Key3) is generated. Users will obtain Key3 when they synchronize with Rights Management, typically by opening a protected document online. However, users are not forced to synchronize with Rights Management until they reach the maximum offline lease period specified in a policy. After the first key rollover, users who remain offline can still open offline documents, including those protected by Key3, until they reach the maximum offline lease period.

When you click the Rollover Keys Now button a second time, Key2 becomes invalid, and Key4 is created. Users who remain offline during the two key rollovers are not able to open documents protected with Key3 or Key4 until they synchronize with Rights Management.

Back to Contents

Updated information about purging records from the Job Manager database [Ref # 2573791]

The following corrections apply to the "Purge records from the Job Manager database" topic in the LiveCycle ES2.5 Administration Help:

Back to Contents

Adobe Data Modeling Technology Reference

Length attribute cannot be set for strings in a collection [Ref # 2467782]

When working with application models, the length attribute can be set on strings,  but not on strings in a collection, even though the Modeler user interface provides this option. If you set the length attribute on strings in a collection, your model will be invalid.

The Application Modeling Technology Reference documentation does not state that the length attribute cannot be set on strings in a collection.
Back to Contents


LiveCycle ES2.5 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 ES2.5 supports the latest version of Adobe AIR. You can download the latest 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 ES2.5 provides support for the following use cases with Adobe AIR by providing the ability to:

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

Adobe LiveCycle Forms 9 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 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.

Adobe LiveCycle Output 9 required modifications to the LGPL library, specifically, the JCIFS was modified for LiveCycle ES2.

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 ES2 (9.0.0.2) and LiveCycle ES2.5 (9.5)-- 02/11/2011 11:31 AM