Running Multiple LiveCycle Environments

Most customers end up running at least four distinct LiveCycle environments – DEVELOPMENT, TEST, STAGING and PRODUCTION.

Apart from the obvious requirements of having separate tablespaces (or databases), db users/schemas, JMS clusters etc, one requirement is often overlooked. It is the multicast address used by LiveCycle’s Gemfire distributed cache. LiveCycle Configuration Manager (LCM) gives you an option to set it and offers you a default value. This has to be unique for each of your LiveCycle environments. If not, unpredictable results will occur such as not being able to login to the AdminUI of some of your LiveCycle environments. In the server log, you might see entries such as these:
ALC-DSC-000-000: com.adobe.idp.dsc.DSCAuthorizationException: Internal error

If you missed this, you can change this after the fact by passing in JVM arguments. Here is an example:
-Dgemfire.mcast-address= -Dadobe.multicast-port=35001

You don’t have to change the port number as long as your different LiveCycle environments run on separate physical boxes or virtual instances.

JBoss uses aditional JGroups which all need to be configured.

More about the use of IP multicasting by LiveCycle here and here.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)
This entry was posted in Adobe LiveCycle ES and tagged . Bookmark the permalink.

Comments are closed.