In Jedox, there are actions that have to be executed repeatedly and/or regularly, such as specific Integrator jobs for loading data. In the Scheduler component of Jedox, you can start and stop tasks, edit and delete them, depending on your user rights. You can create new PDF batch jobs in the Reports component and organize new Integrator jobs in the Integrator component. For tasks, you can also define a user context in which the task is generated. You can also select multiple tasks at once and execute or delete them.
Note: You cannot execute a batch PDF task for reports that use OLAP connections to external OLAP instances where the “Use Login credentials” option is set.
You can start up to 16 tasks at the same time. If you want to start more tasks at the same time, you can increase the default value in the file
Look for the following line:
org.quartz.threadPool.threadCount = 16
Increase the value of the entry on the right and then restart Jedox Suite TomcatService.
The start/stop times for a task are applied in the time zone that the server is in. This time zone may be different from that of the user who is scheduling the task.
For example, say a Jedox server is physically located in Bucharest (GMT+2). It serves a company located in Berlin (GMT+1). If a user in Berlin schedules a task to begin at 18:00, the task will begin at 18:00 in Bucharest (which would be 17:00 in Berlin). For more information, see Time Zones in Jedox Components.
The times shown in the Scheduler Logs (described below) show the local time of the user, i.e., the time zone of the machine where the Web browser is running. In the example above, the Scheduler Logs for the user in Berlin would show that the task began at 17:00.
You can view all executed tasks in the Scheduler Logs, available by clicking Show logs in the navigation pane under Scheduler:
The Scheduler Logs show the start and end time for each executed task, as well as status. If all goes well with your scheduled tasks, you will see something like this:
See Scheduler Task Status Codes for other status results. If the task was unsuccessful, the Logs will describe the problem in the Message column:
For more information, see the following articles: