LiveCycle – WebSphere JVM Arguments Explained

The JVM arguments for a properly configured WebSphere 6.1 instance that hosts LiveCycle ES would look something like as follows (depending on the LiveCycle components you have licensed and chosen to deploy):

-Xgcpolicy:gencon -Xgcthreads3 -Xmnx750m -Xmox750m -Dadobeidp.RootDirectory=/opt/adobe/livecycle8.2/lc_adobeIDP_RootDirectory -Djava.io.tmpdir=/opt/adobe/livecycle8.2/lc_java_io_tmpdir -Dadobe.cache.cluster-locators=aix01.adobe.com[22345],aix02.adobe.com[22345] -Dfile.encoding=utf8 -Dalfresco.cluster.name=livecycle -Dalfresco.tcp.initial_hosts=etechaix01.can.adobe.com[7800],etechaix02.can.adobe.com[7800] -Dalfresco.tcp.start_port=7800 -Dalfresco.tcp.port_range=3 -Dindex.recovery.mode=AUTO -Dhibernate.dialect=org.hibernate.dialect.DB2Dialect

To learn more about IBM’s J9 JDK, see IBM’s JavaOne 2006 presentation (TS-3313 – you need a free registration with the Sun Developer Network).

Garbage Collection

-Xgcpolicy:gencon : Set the garbage collection mode fo the IBM J9 JDK to Generational Concurrent.

-Xgcthreads3 : Set the number of garbage collection helper threads to 3 since the server has 4 logical CPU cores

-Xmnx750m : Set the maximum size of the nursey area of the heap to 750 MB

-Xmox750m : Set the maximum size of the tenured (old) area of the heap to 750 MB

Note that for this particular JVM, the initial heap size (-Xms) was set to 512 MB and the maximum heap size (-Xmx) was set to 1536 MB.

Runtime Folder for LiveCycle’s Native (C++) Components

-Dadobeidp.RootDirectory=/opt/adobe/livecycle8.2/lc_adobeIDP_RootDirectory

Temporary File I/O

-Djava.io.tmpdir=/opt/adobe/livecycle8.2/lc_java_io_tmpdir : Set the temporary directory of the JVM to a specific folder

Gemfire Distributed Cache

-Dadobe.cache.cluster-locators=aix01.adobe.com[22345],aix02.adobe.com[22345] : Set up the Gemfire distributed data fabric (distributed cache) for TCP.

This assumes that the TCP Locator service is running on both aix01.adobe.com and aix02.adobe.com on port 22345. You can verify this by running the following command on those machines:
netstat -an | grep 22345
The expected response should be this:
tcp 0 0 *.22345 *.* LISTEN

Another verification command is this:
ps -ef | grep gemfire
The expected response should look something like this:
livecycl 331984 1 0 10:14:51 pts/0 0:03 java -cp ./gemfire.jar: -Dgemfire.license-type=production -Dlocators=localhost[22345] com.gemstone.gemfire.distributed.Locator 22345

File Encoding

-Dfile.encoding=utf8 : Set file encoding to Unicode

Content Services ES

-Dalfresco.cluster.name=livecycle : A name for the JGroups channel – set to the name of the WebSphere cluster that hosts LiveCycle

-Dalfresco.tcp.initial_hosts=aix01.adobe.com[7800],aix02.adobe.com[7800] : DNS names of the nodes on which the LiveCycle cluster members are running (aixo1.adobe.com and aix02.adobe.com) and the port to be used (7800) for JGroup group discovery and message communication (TCP transport)

-Dalfresco.tcp.start_port=7800 : Default port for JGroups group discovery and message communication using TCP

-Dalfresco.tcp.port_range=3 : If the default port (7800) is not available, try three more incrementally (7801, 7802, 7803) and then fail.

-Dindex.recovery.mode=AUTO : Set the Lucene indexes on all cluster nodes to stay in synch with one another

-Dhibernate.dialect=org.hibernate.dialect.DB2Dialect : Hibernate database dialect for DB2 which is the DBMS LiveCycle is using. org.hibernate.dialect.DB2Dialect allows Hibernate to generate SQL that is optimized for a particular relational database (DB2 in this case).

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.