...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
public Date scheduleProcess(String processRunLogID, String processRunLogNum, String EJBName, String processRunFunction, String processRunDesc, Date executionDate)
As we can see, the first parameter, processRunLogID is actually the parameter which passed in the method processRunFunction (fourth parameter) to been execute whilst EJBName is the ejb class which includes this method. Also, processRunLogNum as we can see from the screen below is the number of the task which been processed and processRunDesc is the description of the process accordingly. Lastly, executionDate is simply the date of the task execution. Thus, this method can be called with some values as below:
sceduleProcess("1245672", "12", "CRMProcessNormalBillingRun", "execute", "Normal Billing Run", "2016-06-16")
...
| Panel | ||
|---|---|---|
| ||
This section describes how a task can be sent to the scheduler.
What does this section cover?
|
public Date scheduleProcess(String processRunLogID, String processRunLogNum, String EJBName, String processRunFunction, String processRunDesc, String cronExpression)As you can notice, the method parsing exactly the same parameters, except from the last one.Date executionDate)
The cronExpression parameter is used for complex triggers which defines date and time of task execution. The following forms are valid for cronExpression :
| Expression | Meaning |
| 0 0 12 * * ? | Fire at 12pm (noon) every day |
| 0 15 10 ? * * | Fire at 10:15am every day |
| 0 15 10 * * ? | Fire at 10:15am every day |
| 0 15 10 * * ? * | Fire at 10:15am every day |
| 0 15 10 * * ? 2005 | Fire at 10:15am every day during the year 2005 |
| 0 * 14 * * ? | Fire every minute starting at 2pm and ending at 2:59pm, every day |
| 0 0/5 14 * * ? | Fire every 5 minutes starting at 2pm and ending at 2:55pm, every day |
| 0 0/5 14,18 * * ? | Fire every 5 minutes starting at 2pm and ending at 2:55pm, AND fire every 5 minutes starting at 6pm and ending at 6:55pm, every day |
| 0 0-5 14 * * ? | Fire every minute starting at 2pm and ending at 2:05pm, every day |
| 0 10,44 14 ? 3 WED | Fire at 2:10pm and at 2:44pm every Wednesday in the month of March. |
| 0 15 10 ? * MON-FRI | Fire at 10:15am every Monday, Tuesday, Wednesday, Thursday and Friday |
| 0 15 10 15 * ? | Fire at 10:15am on the 15th day of every month |
| 0 15 10 L * ? | Fire at 10:15am on the last day of every month |
| 0 15 10 ? * 6L | Fire at 10:15am on the last Friday of every month |
| 0 15 10 ? * 6L 2002-2005 | Fire at 10:15am on every last friday of every month during the years 2002, 2003, 2004 and 2005 |
| 0 15 10 ? * 6#3 | Fire at 10:15am on the third Friday of every month |
As example, we perform a normal billing run which is send to the scheduler as a task. In the beginning, we create a new normal billing run (BILLING>BILLING>PERFORM NORMAL BILLING RUNS>NEW), we define when it will be billed and also to the filter tab at subscription sub section, we choose random subscription to execute the normal billing. After we save the new normal billing run, we choose to execute up to formatting action and send the task to the scheduler. In addition, going to the scheduled tasks (FOUNDATION>UTILITIES>MANAGE SCHEDULED TASKS), we can see the billing task that been processed. As we can see below, some of the parameters which are passed in the methods are also illustrated as fields.
| Expand | ||
|---|---|---|
| ||
|
...