LiveCycle on JBoss AS – Performance/Scalability Considerations

Since LiveCycle ES/ES2 is a J2EE application that runs in a J2EE appserver environment, a lot of the questions (but not all) regarding LiveCycle’s performance and scalability are really questions about the performance and scalability of the J2EE appserver platform it runs on.

For JBoss AS, which uses Apache Tomcat as its J2EE “Web Container”, there is a very good webinar on the subject available online by Mark Thomas, VMware Staff Engineer as well as a Committer for the Apache Tomcat project. His presentation is about VMware subsidiary SpringSource’s tcServer (based on Apache Tomcat with the addition of the management piece Hyperic HQ) but most of what he discusses is applicable to Tomcat as used by JBoss AS.

He discusses:
– Various connectors (HTTP, AJP)
– HTTP Keep-Alives
– Load-balancing based on IP address (layer 4) as well as SessionID (layer 7)
– Clustering
– Session replication
– Multicast node discovery in a cluster
– Multicast limitations when cluster nodes are in separate IP subnets

He recommends the use of the Apache Portable Runtime (APR) with OpenSSL for SSL performance reasons. LiveCycle requires SSL for Rights Management. Configuring APR for JBoss is discussed here. Configuring OpenSSL for JBoss is discussed here.

Please note that this webinar only covers Tomcat. It does not cover the clustering aspects of the JBoss EJB container or LiveCycle’s own clustering component (Gemfire).

For an additional webinar from VMware on running JBoss on a virtualized OS, see 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, General Interest and tagged . Bookmark the permalink.

Comments are closed.