Features and Benefits
Java Job Scheduling
Schedules with Precision Down to the Hour, Minute, and Second
You can create simple and complex schedules. Simple schedules include daily at 10:30, Monday through Friday at 18:00, once per hour, and once per minute. More complex schedules include the last Friday of the month at 9:30; from 8:30 to 16:45 every 7 minutes; and from 22:00 until 2:15 the next morning, every 15 minutes.Schedules can include business days, holidays, working hours, non-working hours, etc (see below).
Business Days, Holidays, Working Hours, Non-Working Hours
Define your business days and holidays so that jobs and workflows run on working days and skip over holidays. However, you do not need to limit yourself to "whole" days. You can define working hours and non-working hours.
EXAMPLE: Suppose your working hours are Monday through Friday, except holidays, from 8:30 to 16:15, except the lunch hour from 11:30 to 12:30. You can define schedules that fire jobs only during these working hours. You can also define schedules that fire jobs only outside working hours.
Schedule Java Software Processes, POJOs, EJBs, JMS Messages, Software Processes, Scripts, and Other Software
Flux has over 40 actions that you can call. In addition to these 40+ actions, you can also extend any of these actions and make your own custom actions.
Once you have defined your schedule, define what software processes need to be called. You can call any software program or script on schedule. Call any kind of Java software — Java classes, POJOs (plain old Java objects), RMI servers and objects, EJB session beans, and EJB entity beans. You can also publish JMS messages.
Bring Workflow into Job Scheduling
When you are ready to bring the advantages of Workflow into your Job Scheduling, just incorporate Flux Workflow into your Flux Job Scheduling. In a single product and a unified architecture, Flux handles Job Scheduling, Workflow and Managed File Transfer.
Complex Error Handling
Flux allows you to build entirely separate jobs that can be used in the event of an error in the processing of your job. You can also build complex error handling behavior directly into your job design. When a job encounters an error, you can monitor the error and recover your job directly through the Operations Console.
Agents
Flux also allows you to integrate agent calls into your workflow. An agent allows you to run processes and scripts on a distant, resource-specific machine or helps balance the process load in your environment.