Future of Flex – Whitepaper from Adobe
0Moderator’s note: Although this blog post is not specific to LiveCycle, the Adobe enterprise community will likely find it useful. We’re taking the liberty of sharing it (with due thanks to Holly Schinsky).

There have been a lot of questions about the viability and future of Flex recently, and Adobe has published an official whitepaper today detailing their support for Flex going forward. The paper also contains details regarding Flash runtime support, Flash Builder support and other Apache contributions including the Falcon compiler. I believe the paper is a must read and can be found HERE.
——-
Original article at http://devgirl.org/2012/02/15/future-of-flex-whitepaper-from-adobe/.
Understanding MEAP – Mobile Enterprise Application Platforms
0When I see value though, I want to point it out. MEAP is one of those rare acronyms that seems to be vastly underestimated by the majority of the industry. The term itself seems to have come from Analyst firm Gartner in a paper published in April 2011 (Gartner, Magic Quadrant for Mobile Enterprise Application Platforms, Michael J. King, William Clark). I believe I read somewhere that Gartner believes over 95% of the technology industry will use some form of MEAP by 2012. When I try to research this topic on Google, very little information comes up. Regardless of the title, let’s explore what a MEAP is and what it does.
In their paper, “The rule of three” is used as a quantifier for identifying when this functionality might be of interest. Quoting from Gartner (via Wikipedia):
The Rule of Three refers to a concept developed by analyst firm Gartner, whereby companies are encouraged to consider the MEAP approach to mobility when they need their mobile solutions to:
- Support three or more mobile applications
- Support three or more mobile operating systems (OS)
- Integrate with at least three back-end data sources
According to Gartner, using a common mobility platform, like a MEAP, brings considerable savings and strategic advantages in this situation.
——-
Read the full article at http://technoracle.blogspot.com/2012/02/understanding-meap-mobile-enterprise.html.
LiveCycle Output ES2: “Failure to automatically determine column ’5′ width”
0Issue
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 logMessage ALC-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 logMessage ALC-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/.
How to Fix com.adobe.idp.scheduler.SchedulerException: Failure Occurred During Job Recovery
0Problem Scenario: LiveCycle uses Quartz scheduler. Typical use case is when “watched folder” endpoint related schedules get translated as quartz triggers. Quartz takes care of executing the trigger based on frequency and updates a table with the latest execution count. … Continue reading →
——-
Full article at http://blogs.adobe.com/ADEP/2011/12/com-adobe-idp-scheduler-schedulerexception-failure-occured-during-job-recovery.html.
ADEP/LiveCycle v10 SP1 Now Available
0- Neal Davies
I’m pleased to announce that the first service pack for ADEP/LiveCycle v10 is now available. It is made up of two parts; Document Services SP1 for the LiveCycle Modules (Forms, Output, Reader Extensions, Process management …) and Experience Services SP1 … Continue reading →
——-
Complete article at http://blogs.adobe.com/ADEP/2011/12/adeplivecycle-v10-sp1-now-available.html.
The Future of LiveCycle
0- Arun Anantharaman
Since Adobe announced its increased focus on Digital Marketing and Digital Media, the LiveCycle team has met with dozens of customers and partners to discuss the future of LiveCycle. They are all passionate about our technology and the solutions we …
——-
Read the full article at http://blogs.adobe.com/ADEP/2012/01/the-future-of-livecycle.html.
Postprocessing your correspondence
0Correspondences created in enterprises would typically have to be integrated to a back-end process for further distribution (via email, fax, print), document processing (apply digital signatures, encryption, etc.) or archival of the correspondence.
The Adobe Correspondence Management solution provides a convenient way to achieve this by leveraging orchestrations/processes on the ADEP Document Services platform for defining the back-end process (that can use one or more Document Services, based on the enterprise requirements), and providing the ability to easily bind them to a given correspondence template.
Read more about creating a postprocess for the CM solution on the Document Server.
Once such processes are created on the Document Server, can then be mapped to a Letter template in the Postprocess drop down of the Letter Template Editor (as shown below), where the available postprocesses (as defined on the Document Server) are listed:
Tip: If you create a new process, with an existing Manage Assets UI session opened, your process will not be listed in the Postprocesses dropdown until you relaunch or refresh (F5) the Manage Assets browser window (or open the Manage Assets UI in a new browser window).
When the correspondence creation is complete (using the Create Correspondence UI), users can Submit the correspondence (see snapshot below indicating the Submit button), which invokes the associated/mapped postprocess for that Letter template, with the final correspondence PDF and XML data (used to generate the PDF). The postprocess, which would be an orchestration, can then act upon the document (PDF) as necessary.
——-
Original article at http://blogs.adobe.com/saket/cm-postprocess/.
Configuring LiveCycle JDBC Data Sources in WebLogic for DB Failover
0For 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
Set ‘Inactive Connection Timeout‘ to 0 seconds
9) Set ‘Connection Reserve Timeout‘ to 10 seconds
——-
Original article at http://blogs.adobe.com/livecycle/2011/04/configuring-livecycle-jdbc-data-sources-in-weblogic-for-db-failover.html.
LiveCycle ES2: UnsupportedClassVersionError: (oracle/jdbc/OracleDriver) bad major version at offset=6
0Issue
If you are attempting to configure Adobe LiveCycle server using the LiveCycle Configuration Manager (LCM) with an Oracle database, you may encounter the following exception during the DB configuration step:
Caused by: java.lang.UnsupportedClassVersionError: (oracle/jdbc/OracleDriver) bad major version at offset=6 at java.lang.ClassLoader.defineClassImpl(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:258) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:151) at java.net.URLClassLoader.defineClass(URLClassLoader.java:589) at java.net.URLClassLoader.access$400(URLClassLoader.java:123) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1034) at java.security.AccessController.doPrivileged(AccessController.java:279) at java.net.URLClassLoader.findClass(URLClassLoader.java:491) at java.lang.ClassLoader.loadClass(ClassLoader.java:631) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:597) at java.lang.Class.forNameImpl(Native Method) at java.lang.Class.forName(Class.java:130) at com.adobe.livecycle.cdv.validator.DBValidator.validateDB(DBValidator.java:174)
Reason
This error can occur if you are not using the correct Oracle DB driver, or the correct Java JDK for your platform.
Solution
You should check the Oracle DB driver and JDK version required in the relevant platform matrix. With LiveCycle ES2 for example the platform matrix is located here:
http://help.adobe.com/en_US/LiveCycle/9.5/supported_platforms.html
So if you were to install LiveCycle ES2 on AIX 5.3 with WebSphere 7, you should be using the 64-bit JDK 1.6 SR7 provided by WebSphere (WAS_HOME/AppServer/java), and the ojdbc6.jar Oracle driver.
Be sure to set the JAVA_HOME and PATH environment variables as instructed in http://help.adobe.com/en_US/livecycle/9.0/prepareinstallsingle.pdf
——-
Original article at http://blogs.adobe.com/dmcmahon/2012/01/21/livecycle-es2-unsupportedclassversionerror-oraclejdbcoracledriver-bad-major-version-at-offset6/.
Dynamically Rendering PDFs from the LiveCycle Repository
0While not as complex a process as Barcoded Forms the process of dynamically rendering PDFs from the LiveCycle Repository is a common process that gets used very often. There may be instances where an application needs a simple static PDF. Perhaps it’s a form that’s not quite ready for online submission. You could store these files on a web server and access them directly but it would be better and easier for future development to store them in the LiveCycle Repository and render them with a call to a REST service that is created when the process is deployed. The path to the document to render is passed into the process via a URL variable and the static PDF or the XDP file converted to PDF is returned to the browser.
For this LiveCycle Hands On the process is very simple. Besides rendering a simple static PDF, it’s also setup to render a simple XDP using LiveCycle Output ES.
Download the LCA here: Render_Form_Demo.lca_.zip

(Right click and select View Image to see the full size image)
——-
Complete article at http://www.underprise.com/2011/06/01/dynamically-rendering-pdfs-from-the-livecycle-repository/.

