LiveCycle on WebLogic Domains with No Node Manager

LiveCycle Configuration Manager (LCM) assumes that you are running your WebLogic instances using Node Manager. There are several large deployments out there where this is not the case. If yours is one of them, this is for you.

After configuring the WebLogic instance with JDBC and JMS, LCM will try to restart the instances. It will succeed in shutting them down but will fail to start them. This is because it needs the Node Manager to be runing in order to do this.

At this stage, do NOT run LCM again.

Add the changes made by LCM in the WebLogic Admin Console to the startup script of the managed server that hosts LiveCycle (startManagedWebLogic.sh). You can view these changes in the WebLogic Admin Console by navigating to [your_domain_name]->Environment->Servers->[your_managed_server_name]->Configuration->Server Start. The fields of interest are ‘Class Path’ and ‘Arguments’.

In a typical non-clustered managed server, the script addition will look as follows (WebLogic 10 on Solaris 10 example used):

JAVA_OPTIONS=”-Dadobeidp.RootDirectory=”/opt/bea_home/user_projects/domains/livecycle” ${JAVA_OPTIONS}”
JAVA_OPTIONS=”-Dfile.encoding=”utf8″ ${JAVA_OPTIONS}”
JAVA_OPTIONS=”-Djava.net.preferIPv4Stack=”true” ${JAVA_OPTIONS}”
JAVA_OPTIONS=”-Djava.io.tmpdir=”/opt/bea_home/user_projects/domains/livecycle/lc_java_io_tmpdir” ${JAVA_OPTIONS}”
JAVA_OPTIONS=”-Djava.security.policy=”/opt/bea_home/wlserver_10.0/server/lib/weblogic.policy” ${JAVA_OPTIONS}”
CLASSPATH=”/opt/bea_home/user_projects/domains/livecycle/lib/pop3.jar:
/opt/bea_home/wlserver_10.0/server/lib/weblogic.jar:
/opt/bea_home/jdk150_11/lib/tools.jar:
/opt/bea_home/user_projects/domains/livecycle/lib/ojdbc14.jar:”

If you are copy-pasting this, make sure that the line breaks in the CLASSPATH are all removed.

In addition, edit the setDomainEnv.sh script and add the following (lc_server1 is the name of the managed server, minimum and maximum heapsize is being set to 1 GB):

if [ "${SERVER_NAME}" = "lc_server1" ] ; then
MEM_ARGS=”-Xms1024m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m”
export MEM_ARGS
fi

Start the managed server using the script. Ensure that the changes prescribed in the starup scripts have taken effect by verifying the managed server log. The heap size setting is very important, so is the setting for adobeidp.RootDirectory. The default heapsize is too low and will cause OutOfMemoryExceptions during the deployment of the DSCs or of the sample orchestrations.

Continue with the rest of the steps (initialize database, deploy DSCs etc).

For WebLogic 9.2, the CLASSPATH entry in startManagedWebLogic.sh will not work. In this case, add it to setDomainEnv.sh as follows:

PRE_CLASSPATH=”/opt/bea_home/user_projects/domains/livecycle/lib/pop3.jar:
/opt/bea_home/wlserver_10.0/server/lib/weblogic.jar:
/opt/bea_home/jdk150_11/lib/tools.jar:
/opt/bea_home/user_projects/domains/livecycle/lib/ojdbc14.jar:”

If you are copy-pasting this, make sure that the line breaks in the CLASSPATH are all removed.

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. Bookmark the permalink.

Comments are closed.