– Samartha Vashishtha, Content and Community Lead @ Adobe
Sometimes, you may want to create Correspondence Management solution assets that contain special characters in their names. To do so, you must first define the list of special characters that you want to use in the tbxeditor-config XML file.
Read the complete post at https://blogs.adobe.com/samartha/2012/05/enter-special-characters-in-correspondence-management-asset-names.html.
– Ameeth Palla, Technical Account Manager, Adobe
A topic that has come up several times in the recent past is about testing Adobe LiveCycle Workspace. I thought it will be useful to provide some information around this for the benefit of a larger LC community.
If the objective is Load testing, in-house Adobe uses a commercial tool call Silk Performer which can capture and replay the AMF3 interactions between Workspace and the server for scalable load generation. There are other tools that work with AMF3.Some people have asked if QTP can be used for load testing – It is unlikely that QTP is a good fit, since it is not suited to scalable load generation.
Adobe recommends using Silk Performer or Neotys Neload for load testing of Workspace. Check out the links below that may provide more insight into this topic:
If the objective is Functional testing then Workspace is configured for QTP testing out of the box. If you install QTP, restart your computer, then install the Flex plug-in for QTP, restart your computer then you can start automating your Workspace tests. However for QTP automation you should use the Workspace automation URL rather than the default URL. So rather than http://server:port/Workspace/Main.html you would use http://server:port/Workspace/Main-auto.html.
Read the complete post at http://blogs.adobe.com/livecycle/2012/03/testing-livecycle-workspace.html.
Adobe LiveCycle ES3 includes a FIPS 140 Certified RSA BSAFE Crypto-J 3.5 (cert#590) encryption module. FIPS mode is configured in the product installer.
Original article at http://blogs.adobe.com/livecycle/2012/03/fips-validation-certificate-for-livecycle-es3.html.
Moderator’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/.
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/.
– 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.
– David McMahon
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.Class.forNameImpl(Native Method)
This error can occur if you are not using the correct Oracle DB driver, or the correct Java JDK for your platform.
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:
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/.