Timer in Weblogic Cluster: What we need ...

Timer in Weblogic Cluster: What we need ...

Timer in Weblogic Cluster: Abstract

Timer in Weblogic Cluster: Abstract

What we need ...

- Weblogic 10.3
- RDBMS (for example, Oracle)
- JDK (1.5/6)

A singleton service component will start the timer(s) in a node of the cluster. Therefore, the Timer will be running in one node in the cluster at a time. If the server fails, stops, etc., the Singleton component will be moved to another node
and start the Timer there. The TimerService components must be deployed homogeneously
in the cluster, so that, the SingleServer can start the Timer in another node
in case of server failure.

A custom object can be bound to Local JNDI where the Timer is currently running- this is to determine the correct job host by EJB Timer call backs.

A leasing table will be used by the SingletonService in the cluster.

In short, using SingetonService Component, EJBTimer, and Database leasing, we will create the robust clustered job framework, that will provide full control over each process, distribute task according to the load balance algorithm, and fail over. recoveries.

1. SingletonService
2. EJBTimer
3. Java Message Service
3. Database Leasing

Coming soon ...

Abstract

Running Timers in a cluster environment is often challenging. However, there are ways you can design, implement, and run Timers in weblogic to run periodic jobs.

In this blog, I am going to discuss, how you can create a Job Framework in Web-Logic 10.3 server, where the jobs can be started, stopped, standby, resume, etc.

Details coming soon ...