If you are upgrading from a previous version of LiveCycle
and changing your LiveCycle Server, you may disrupt any processes
that use the document form variable or digital signatures. This
is because these forms are rendered only once, setting the submit
URL. Changing the server breaks the certificate.
Choose the solution that is most appropriate for your LiveCycle
environment from the following solutions:
Solution 1: Complete all processes that use a form document
variable before you upgrade or move to the remote server. Use this
method if you maintain legacy LiveCycle servers after the upgrade.
This approach also eliminates the need for throw-away work
to be done to manage the redirection of the form submissions. This
method is not practical if you have many outstanding processes.
Solution 2: If the server being upgraded is not being
decommissioned, a reverse proxy approach is preferable. With this
method, you maintain the reverse proxy on the old system until all
the migrated processes are completed.
Solution 3: You can use the Apache mod_rewrite module
to modify the embedded URLs in each form as they are delivered to
the client.
Note: If your LiveCycle implementation is on IPv6,
clients using EJB invocation for PDF creation report exceptions.
This is a
known issue attributed to Sun JDK
6.