Job scheduling is used on many software projects to enable both internal jobs and third-party integration. Clustering can provide a huge boost to reliability by providing fail-over and load-sharing. I believe that clustering should be implemented for reliability on just about all software projects, so I’ve decided to outline how to go about doing that … Read more
At Carfey Software, we love our flagship product, Obsidian Scheduler. We believe that Obsidian is the best choice for most scheduling needs. Why? Because Obsidian is carefully designed to meet both simple and complex requirements. We think it stacks up well whether you are struggling with an existing scheduler or investigating if you should once … Read more
We’ve completed an incremental release for Obsidian Scheduler. Version 1.3 is now available here. Some of the highlights: Sent notifications view Free groovy job for reflectively calling existing code – New jobs without builds! Annotation for class/method of job Bug fix on LogCleanupJob Implementation details can always be found on our wiki.
If you need to schedule jobs in Java, it is fairly common in the industry to use Quartz directly or via Spring integration. Quartz’ home page at the time of writing claims that using quartz is a simple 3-step process: Download, add to app, execute jobs when you need to. For any of you that … Read more
While we’ve already written a post on our scripting support in Obsidian, this post will focus specifically on our Groovy support, what we use it for and what it makes possible for you. Given that Groovy is built for the JVM and almost any java code will work as is in a groovy script/class, supporting … Read more
Obsidian Scheduler provides enterprise scheduling features while natively supporting pooling and clustering, or in other words, load balancing and fault tolerance. But Obsidian does so in a way that is painless and non-invasive. In fact, you don’t have to do anything. Load balancing and fault tolerance are built into each instance of Obsidian Scheduler whether … Read more
When we started working on our Obsidian Scheduler, one of the primary motivations was to give our clients full control over the configuration of their server runtime and total control over job configuration, including schedule, state, parameterization, etc. More than just full control, we wanted the configuration of said items to take effect immediately across … Read more
Here at Carfey, we’ve used Java’s native scripting API in our upcoming job scheduler to allow our clients to deploy new scripts at any time they wish, without redeploying their applications. Combined with our advanced configuration support, we think we’ve found a killer combination of flexibility and power. The scripting API was outlined in JSR … Read more
A challenge that many software organizations face is how to license your software, and the corresponding controls to make sure it is not abused. The vendor wants a solution that protects their product and gives them multiple ways to sell it. Users want something that just works and doesn’t interfere with up-time or reliability of … Read more
As software professionals, we need our job schedulers to be reliable, easy to use and transparent. When it comes to job schedulers, transparent means letting us know what is going on. We want to have available to us information such as when was the job scheduled to run, when did it start, when did it … Read more