Tag Archives: WebLogic

LiveCycle – Application Server Clustering Verification

When running Adobe LiveCycle in cluster mode, it is important to verify that the cluster is configured and started successfully. LiveCycle deployment has has twoclustering layers

  • Application Server Clustering
  • LiveCycle Clustering

LiveCycle runs on J2EE stack. J2EE level clustering should be configured as mentioned in LiveCycle cluster documentation. In this article we will go through each application server and based on logs determine if the clustering is successful or not, LiveCycle Clustering is described in the article – LiveCycle Cluster Verification.


Read the complete post at Adobe LiveCycle Blog.

LiveCycle Cluster Verification

On top of J2EE clustering, LiveCycle is clustered using Gemfire Distributed Cache. In cluster deployments, it is important that all the members of a LiveCycle cluster are able to find each other so that they can keep their individual caches in synchronization with one another. LiveCycle Cluster is configured properly or not can be identified based on two key indicators. The following are the key indicators.

  • Clustered Scheduler Service
  • Gemfire Logs


Read the complete post at Adobe LiveCycle Blog.

Configuring LiveCycle JDBC Data Sources in WebLogic for DB Failover

– Jayan Kandathil

For IBM WebSphere, see here.

LiveCycle ES2′s Configuration Manager (LCM) provides you two options for configuring JDBC data sources in WebLogic:

1) Package it inside the EAR files (more secure)
2) Create it in the WebLogic Admin Console

Choice #2 provides a lot more flexibility when it comes to configuring the data sources for database failover. Runtime configuration changes such as increasing the pool size can be done without having to un-deploy and re-deploy EAR files.

To ensure that the connections in the connection pool are valid, the following additional configuration changes are necessary. This is based on an actual customer deployment against an active-passive SQL Server database cluster. You can make changes as necessary to fit your IT environment.

1) In the ‘Connection Pool‘ tab for the JDBC data source, in the ‘Advanced‘ section, ensure that the checkbox for ‘Test Connections on Reserve‘ is checked

2) Set ‘Test Frequency‘ to 10 seconds

3) Set ‘Test Table Name‘ to “DUAL” or “EDCJOBENTITY”

4) Set ‘Seconds to Trust an Idle Pool Connection‘ to 5 seconds


6) Set ‘Connection Creation Retry Frequency‘ to 12 seconds

7) Set ‘Login Delay‘ to 0 seconds

8) Set ‘Inactive Connection Timeout‘ to 0 seconds

9) Set ‘Connection Reserve Timeout‘ to 10 seconds

Original article at http://blogs.adobe.com/livecycle/2011/04/configuring-livecycle-jdbc-data-sources-in-weblogic-for-db-failover.html.