Managing Process Recordings in LiveCycle

Process Recordings are stored in the /GDS/audit/workflow/ directory.

By default, the maximum number of recordings that can be stored is set to 50.

The value for maximum number of recordings can be configured via Workbench:

1. Open Component View in Workbench.
2. Right click on “Components/AuditWorkflowDSC/AuditWorkflowService:1.0”
3. Select “Edit Service Configuration…”
4. Change the value to increase/decrease max limit.
5. Restart service.

It is not recommended to turn on Process Recordings in a Production Environment.

Ameeth Palla is a Technical Account Manager for the Adobe Digital Enterprise Platform team. Previously he was in the role of a Technical Expert for LiveCycle for the the Technical Response Team (what is now the Sr.Support Architect role). In both roles, Ameeth handled several technical issues for various customers and worked closely to aid with Sales POC's, Development/Implementation and Manitenance of LiveCycle/ADEP Projects. In the current role he handles several high profile customer accounts and provides guidance in all aspects of LiveCycle/ADEP. Also he is a Certified LiveCycle ES2.5 Process Management Expert. He was nominated for the 'Adobe Founders Award' and the 'Excellence Matters' award for LiveCycle/ADEP BU.

View the original article here

LiveCycle Cluster – WebLogic Unicast Clustering

LiveCycle deployment is supported on both unicast and multicast based appserver clusters. LiveCycle documentation provides steps for default application server cluster configuration, usually multicast based cluster. In this blog, we will go through steps for creating unicast based WebLogic cluster. Steps for creating members of the cluster and assigning servers to the cluster are same as mentioned in the LiveCycle WebLogic Cluster documentation. Please refer the same for installation and other configurations.

The following are steps for creating unicast based WebLogic cluster:

 In the WebLogic Server Administration Console, under Domain Structure, click Environment > Clusters.Under Change Center, click Lock & Edit.In the Clusters table, click New and configure these options:In the Name box, enter your cluster name (for example, livecycle_cluster).In the Messaging Mode box, select Unicast.In the Unicast Broadcast Channel box, enter the Unicast Broadcast Channel. This channel is used to transmit messages within the cluster. If you do not specify a channel, the default channel is used. To create custom network channel refer WebLogic documentation(click here)Click OK and then click Activate Changes.

View the original article here

LiveCycle forums have gone thinner!

Adobe LiveCycle forum is a platform where LiveCycle community meets, learns, and discusses experiences about using LiveCycle. We are committed to provide the best user experience to the community when they are on the forum, and we have taken a step in that direction.

The LiveCycle forum, until sometime ago, comprised of 70 forums and sub-forums. We monitored the forums and found that the unnecessary bulk is making it difficult for the community to manage discussions and participate on the forum. As a result, most of the are inactive as it was unintuitive to drill-down to the correct forum for discussions.

As we understand the importance of a close-knit community, we have optimized the forum structure, so that it is easier for the community to search, post, and participate on the forum. The new forum structure is thin, focused, searchable, and easy to manage.

In its new look, the LiveCycle forum has relatively flat hierarchy, but with a logical grouping of discussions. The streamlined new structure includes seven top-level forums, including one forum with 14 sub-forums. The flat hierarchy relies on the tags for filtering discussions related to a specific area of LiveCycle.

---

Read the complete post at Adobe LiveCycle Help blog.

This entry was posted by Vishal Gupta on August 29, 2012 at 12:58 pm, and is filed under LiveCycle Enterprise Suite. Follow any responses to this post through RSS 2.0. You can skip to the end and leave a response. Pinging is currently not allowed.

View the original article here

LiveCycle ES2: LCMException[ALC-LCM-030-200]: Failed to deploy component

LiveCycle ES2: LCMException[ALC-LCM-030-200]: Failed to deploy component « Adobe enterprise product blog – David McMahon function clearSearch() {document.search_form.s.value = "";} .recentcomments a{display:inline !important;padding:0 !important;margin:0 !important;}adobe.com      Adobe enterprise product blog – David McMahon / LiveCycle ES2: LCMException[ALC-LCM-030-200]: Failed to deploy componentby dmcmahonALC-LCM-030-200 (1)LCM (2)NoClassDefFoundError (3)  

View the original article here

LiveCycle Output ES2: “Failure to automatically determine column ’5′ width”

Issue

If you are using LiveCycle Output to generate PDF documents using XDP files as input, you may encounter the following exception and no PDF will be returned:

0000012a XMLFormAgentW E com.adobe.livecycle.formsservice.logging.FormsLogger logMessageALC-OUT-002-017: mid,tid: 29435,23593162.1 sev: f text: Failure to automatically determine column '8' width.0000012a FormServerExc E com.adobe.livecycle.formsservice.logging.FormsLogger logMessageALC-OUT-002-013: XMLFormFactory, PAexecute failure: "(com.adobe.document.xmlform.ReturnStatus@39133913)Failure to automatically determine column '5' width."

If you load the same XDP file in Designer ES2 and goto PDF Preview, you may notice the same message as a warning in the log, but the PDF will be correctly rendered and displayed:

Failure to automatically determine column '5' width

——-

Read the full article at http://blogs.adobe.com/dmcmahon/2012/02/04/livecycle-output-es2-failure-to-automatically-determine-column-5-width/.

This entry was posted by moderator on February 10, 2012 at 7:08 am, and is filed under FAQ, LiveCycle Enterprise Suite. Follow any responses to this post through RSS 2.0. You can skip to the end and leave a response. Pinging is currently not allowed.

View the original article here

LiveCycle ES: how to uninstall a patch or service pack

– David McMahon

Issue

If you have installed a patch or service pack for LiveCycle ES you may need to uninstall this at a later date, or you may have a requirement to document this process fully as part of your installation/configuration documentation.

This information is outlined in the readme file provided with each patch or service pack, and I will just expand on that giving some more detail here.  In this example I will discuss uninstalling LiveCycle ES Update 1 SP4 (8.2.1.4), to go back to LiveCycle ES Update 1 SP3 (8.2.1.3) on Windows.

Preparation

Before installing/uninstalling any patch you should take note of the current versions installed so you can verify your steps have been successful later.  Take a screenshot of the About screen, and the Service Management screen from the AdminUI.

AdminUI > About screen (note the Patch version “SP4? and Service Pack version “8.1.5192.1.284202.47?, and the Patch level of each deployed component “SP4?):

AdminUI > Services > Applications and Services > Service Management screen (note the Component Versions “8.1.5192.1.284202.47?, “8.1.5193.1.279333.70?, etc…):

Before running through the uninstallation process it would advisable to make a backup of your existing configuration in case any unexpected problems should arise.  To do this, you should make a copy of the entire LiveCycle installation directory (excluding the MySQL folder if it exists within the LiveCycle directory).

You should also take note of the following configuration properties from AdminUI > Settings > Core System Settings > Configurations:

Location of temp directoryGlobal document storage root directory (Changing this value will result in data loss unless you also manually move the data)Location of the Adobe Server Fonts directoryLocation of the System Fonts directory

If you have LiveCycle Content Services ES installed, you should also have the location of the Content Services root directory which you entered during the original installation/configuration process.

——-
Read the full blog post at http://blogs.adobe.com/dmcmahon/2011/12/20/livecycle-es-how-to-uninstall-a-patch-or-service-pack/.

This entry was posted by moderator on January 26, 2012 at 4:54 pm, and is filed under Document Services, FAQ. Follow any responses to this post through RSS 2.0. You can skip to the end and leave a response. Pinging is currently not allowed.

View the original article here

LiveCycle ES2: Unexpected exception. Failed to create directory: \\<cluster>\GDS

LiveCycle ES2: Unexpected exception. Failed to create directory: \\\GDS « Adobe enterprise product blog – David McMahon function clearSearch() {document.search_form.s.value = "";} adobe.com      Adobe enterprise product blog – David McMahon / LiveCycle ES2: Unexpected exception. Failed to create directory: \\\GDSby dmcmahonALC-DSC-033-000 (1)cluster (1)create (1)directory (2)failed (2)gds (2)WebSphere (6)  

View the original article here

LiveCycle Forms ES: Select which fonts get embedded at render-time

LiveCycle Forms ES: Select which fonts get embedded at render-time « David McMahon function clearSearch() {document.search_form.s.value = "";} adobe.com      David McMahon / LiveCycle Forms ES: Select which fonts get embedded at render-timeby dmcmahonalwaysEmbed (1)Embedding (1)Font (1)neverEmbed (1)  

View the original article here

LiveCycle Mobile ES2 now available on BlackBerry PlayBook!

LiveCycle Mobile ES2 now available on BlackBerry PlayBook! « Mobile Matters function clearSearch() {document.search_form.s.value = "";} adobe.com      Mobile Matters / LiveCycle Mobile ES2 now available on BlackBerry PlayBook!by John B Harris  

View the original article here

Configuring LiveCycle JDBC Data Sources in WebLogic for DB Failover

For IBM WebSphere, see here.

LiveCycle ES2's Configuration Manager (LCM) provides you two options for configuring JDBC data sources in WebLogic:

1) Package it inside the EAR files (more secure)
2) Create it in the WebLogic Admin Console

Choice #2 provides a lot more flexibility when it comes to configuring the data sources for database failover. Runtime configuration changes such as increasing the pool size can be done without having to un-deploy and re-deploy EAR files.

To ensure that the connections in the connection pool are valid, the following additional configuration changes are necessary. This is based on an actual customer deployment against an active-passive SQL Server database cluster. You can make changes as necessary to fit your IT environment.

1) In the ‘Connection Pool‘ tab for the JDBC data source, in the ‘Advanced‘ section, ensure that the checkbox for ‘Test Connections on Reserve‘ is checked

2) Set ‘Test Frequency‘ to 10 seconds

3) Set ‘Test Table Name‘ to “DUAL” or “EDCJOBENTITY”

4) Set ‘Seconds to Trust an Idle Pool Connection‘ to 5 seconds

5) Set ‘Init SQL‘ to “SQL SELECT * FROM DUAL” or “SQL SELECT COUNT(*) FROM EDCJOBENTITY”

6) Set ‘Connection Creation Retry Frequency‘ to 12 seconds

7) Set ‘Login Delay‘ to 0 seconds

8) Set ‘Inactive Connection Timeout‘ to 0 seconds

9) Set ‘Connection Reserve Timeout‘ to 10 seconds

View the original article here

Changing the multicast port for LiveCycle

Changing the multicast port for LiveCycle « Tai's F.W.A. function clearSearch() {document.search_form.s.value = "";} .recentcomments a{display:inline !important;padding:0 !important;margin:0 !important;}adobe.com      Tai's F.W.A. / Changing the multicast port for LiveCycleby an_tai  

View the original article here