We currently have LiveCycle ES (v8.2 SP3)/JBOSS installed in our environment. We are looking to move to ES2.5 (v9.5) but dont know whether to upgrade the existing [ES --> ES2 + SP2] OR create a new instance of ES2 [+SP2] on our server?
Since all of our workbench processes are short lived and we do not use Rights management i've read we can do either.. Can anyone comment on why/which method is better and why?
Is a new install quicker?
Our production environment is clustered between ServerA and ServerB. Does the clustering of our prod env, change your answer?
Our intention for the prod upgrade is
Stop ServerA. All transactions goto Server B.
Upgrade Server A.
Restart Server A and stop Server B. All transactions will goto Server A.
Yes, in case you choose to upgrade, you'll have a downtime.
The downtime is required to take a consistent backup of the data associated with your current LiveCycle system.
This data will be used during the upgrade process, hence, you must have a copy of it and it is also required in the event you encounter an unexpected failure during upgrade.
However, this is the ONLY downtime required.
In a LiveCycle cluster, the global document storage (GDS) directory contents and the database is shared amongst the cluster nodes, hence you cannot do an upgrade per node.
If one node is upgraded, the other nodes will automatically have upgraded GDS and database contents. The only difference will be that upgraded node with have new EARs and the non-upgraded nodes will continue to run old EARs against upgraded GDS and database, which may result into errors.
Yes, you can leverage you existing processes through import/export. Sorry to have missed that in my earlier reply. But yes, you'll have to have knowledge to Application Model in that case too. In case of upgrade, you don't require to do anything at all.