Adobe has posted the following blog regarding the future of LiveCycle. It indicates a promising future for the product:
http://blogs.adobe.com/ADEP/2012/01/the-future-of-livecycle.html
Adobe has posted the following blog regarding the future of LiveCycle. It indicates a promising future for the product:
http://blogs.adobe.com/ADEP/2012/01/the-future-of-livecycle.html
Depending on your renderer version you might run into an issue where a page header is being bumped back to the bottom of the previous page. This is a known issue with version 2.6 of the XFA specification which was fixed in version 2.7. The tricky part is there's no Target Version for version 2.7. If you aren't familiar with Target Version, click on File then open Form Properties and check the Defaults tab.
The easiest solution is simply setting your Target Version to Acro/Reader 9.0 (which uses XFA version 2.8), but this will cause problems for people still running Reader 8.
We did some digging and found an easy way to trick the form into using XFA 2.7 to render the form. Open the XML view of the document and find the following line:
<?originalXFAVersion http://www.xfa.org/schema/xfa-template/2.6/?>
And change it to this:
<?originalXFAVersion http://www.xfa.org/schema/xfa-template/2.6/ v2.7-layout:0?>
After that you'll want to make sure Keep With is set to Next in the headers pagination settings.
If you're currently having difficulties running Office after installing the Rights Management plugin there's a very good chance you also have the Microsoft Office Live plugin installed as well.
These two plugins simply do not work together and you'll need to remove one of them until either Microsoft or Adobe fix the conflict.
We recently encountered an issue when merging XML data into a form. Specifically, rich text was being properly displayed in the form fields, but we noticed that any floating fields placed in those text fields displayed their value in plain text.
This can be resolved by manually changing the embedMode tag in the forms XML. Click on the object containing the floating field then open the XML Source view. Inside the object you'll be looking for this:
We recently encountered an issue when merging XML data into a form. Specifically, rich text was being properly displayed in the form fields, but we noticed that any floating fields placed in those text fields displayed their value in plain text.
This can be resolved by manually changing the embedMode tag in the forms XML. Click on the object containing the floating field then open the XML Source view. Inside the object you'll be looking for this:
xfa:embedMode="raw"
You'll want to change it to:
xfa:embedMode="formatted"
As always, if you run into any problems be sure to give us a call!
A common issue when designing large forms is getting the Custom Tab Order tool to behave properly. There comes a point where it becomes completely unusable.
My recommended workaround is to redesign the form for use with Automatic Tabbing. Take the following example:
View imageAutomatic tabbing always goes top/down, left/right. So in order to get the tabbing to work its way down each client section, we just need to wrap them inside their own subforms:
View imageNow this works for most forms, but what if you wanted the tabbing to go from Client1 to Client3? The answer is more subforms ! Selecting the subforms for Client1 and Client3 I wrap them both into yet another subform, I then wrap Client2 and Client4 into their own subform. The result is this:
View imageWe've dealt with a variety of issues relating to multi-threaded conversions and the root cause always seems to be the same: the users were added through the configuration manager. A bug has been logged with Adobe, so this should be gone by the time ADEP releases later this year.
In the meantime we have a simple workaround: add your users through the adminUI instead (http://help.adobe.com/en_US/livecycle/9.0/adminHelp/admin.htm?content=000159.html)
We've received a few reports of Reader not being able to submit e-mail requests to the new Outlook2010 64bit. We did some research and found that this is a known with Microsoft that is affecting any application that makes 32bit MAPI requests to the suite.
There is no word on a fix yet, but we do have a workaround you can use in the meantime. It tricks Outlook into using the 32bit MAPI driver already included with the software:
Adobe LiveCycle and CRX's name will be changed to Adobe Digital Enterprise Platform for the next release of the product.
More here: http://www.adobe.com/solutions/customer-experience/enterprise-platform.html
The following is an FAQ that may have some answers to your questions: http://www.adobe.com/products/livecycle.html
If you have PDF Generator already installed without Acrobat, and you decide to install Acrobat at a later date, you will need to install Acrobat on the LiveCycle server, and then run the following steps in order to configure it to run with PDF Generator:
1. Run the PDFG configuration utility that comes with the LiveCycle installation. You'll find it at:
[LC Install Folder]\pdfg_config\Acrobat_for_PDFG_Configuration.bat
2. Double check to see if the Acrobat Environment variable were actually added (the batch file should have added them).
3. Once all of this was done re-run the config manager, but only select the option to configure the installed LiveCycle components and you would not select Content Services if you do not wish to have it on there.
At this point Acrobat should be fully configured with PDF Generator.
There are of course many things that could cause this issue, but I would like to bring up an interesting case I encountered. The system was running ES2 on Jboss/MySQL. The issue presented itself as rights enabled documents taking 30-40 seconds to open. Upon examining the logs we found several recurring errors, the following being the most noteworthy:
WARN [org.jboss.resource.connectionmanager.TxConnectionManager] Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@178c7cf[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1b9c3be handles=0 .....
The last packet successfully received from the server was XXXXX milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.
...
When we restarted the server, the logs were clean for 10 minutes or so when connection errors started appearing at increasing rates. This of course pointed to a database connectivity issue, but the connectors appeared to be in good order, and more importantly, we were able to login to the adminUI with no delays. We then disabled security software, reviewed permissions and redeployed all components to Jboss yet the issue persisted.
Upon closer inspection of the clients MySQL installation I found that several .ini files were missing. How these files went missing aside, my expectation is that MySQL would fail to start in such a scenario (which would have generated very different errors). Based on this, it would be safe to assume that this error could also be caused by damaged/corrupted .ini files.
From there it was just a matter of backing up the clients
tables through the command prompt, reinstalling, and then restoring the tables.
We have a new hotfix available from Adobe. This one addresses an issue when running a query against a database using
the JDBC component in Workbench/Livecycle 9.5. If any of the returned values are null the component
will return a null pointer exception (java.lang.NullPointerException) instead of simply returning blank values. The hotfix installs easily into Workbench 9.5.
If you're currently experiencing this issue (and on a maintenance and support plan) just give us a call and we'll make the hotfix available to you.
Problem:
When attempting to add a new user in : adminui -> services -> LiveCycle PDF Generator ES2 -> User Accounts, it results in the following error:
ALC-PDG-030-003-User account information for user pdfg1 is not valid for the machine......
The system.log shows this:
ERROR [STDERROR] sudo
ERROR [STDERROR] : sorry, you must have a TTY to run sudo
Reason:
The reason for this is an update along the way with sudo locked it down further by adding the below line to /etc/sudoers configuration file:
1 Defaults requiretty
Solution:
To allow a remote script to login and run a command via sudo simply comment out that line as shown below:
1 # Commented out so remote script can login and run a command without a tty
2 # Defaults requiretty
1. Create a new keystore using the same name and password as the existing one running on the system (note: CN, the user's first and last name, must be the URL for which the keystore is being created):
keytool -genkey -keyalg RSA -alias tomcat -keystore <keystore_name>.keystore
2. Create a certificate request (CSR):
keytool -certreq -alias tomcat -keyalg RSA -file <cert_request_name>.csr -keystore <keystore_name>.keystore
3. Send the CSR to a CA and in return you will receive the CA's root cert path and the cert for your URL.
4. Import into the keystore the CA's root cert (for the certification path):
keytool -import -file <CA_cert>.crt -keystore <keystore_name>.keystore
5. Import into the keystore the cert that the CA generated in response to the CSR:
keytool -import -alias tomcat -trustcacerts -file <new_cert_from_CA>.crt -keystore <keystore_name>.keystore
6. Copy the resulting keystore into jboss/server/all/conf
7. Modify the server.xml by adding the name of and password for the keystore. In your server.xml file, the keystore and keystorePass should look something like the following:
keystoreFile="${jboss.server.home.dir}/conf/lces-ssl.jks" keystorePass="password"
8. Restart JBoss.
My take on this is that social media engagement itself has to have a reason....No kidding. It's not a touchpoint in a campaign, it is not another piece of collateral. Watson goes on to state:
Treating it as an experiment or side project makes it even harder to integrate down the road. We need to accept and embrace that we live in a multi-channel world and a multi-screen universe and that each one has strengths and weaknesses, but more importantly that each one needs to be able to 'see' the other.



