This topic describes the advantages of bursting reports and how you can schedule bursting reports to generate bursting result and non-bursting result.
This topic contains the following sections:
- An Introduction to Bursting Reports
- Scheduling a Bursting Report to Generate Bursting Result
- Scheduling a Bursting Report to Generate Non-bursting Result
In a large enterprise reporting deployment, it is important to handle both large amounts of data as well as a large number of users. Report bursting enables running a report once and distributing it to multiple recipients who each will receive a subset of the report, subject to security rules.
Bursting reports can be distributed to email or FTP addresses, to disk, to the Logi Report versioning system, or to the security system members such as users, groups, and roles.
End users can submit a schedule task which contains only one bursting report on Logi Report Server. When a bursting task is activated, it will create a main bursting task and some sub bursting tasks. Logi Report guarantees that bursting tasks compete with normal tasks for system resources. The bursting tasks can be given lower priority if desired (set queue.policy to 1).
- Main bursting task: It is responsible for getting/splitting data and distributing work to the sub tasks. There can be only one main bursting task for a sub bursting task.
- Sub bursting task: It is responsible for generating the report outputs according to split data and sending the outputs to the addresses of the bursting recipients.
For more information, see Creating Bursting Reports in the Logi Report Designer Guide.
On Logi Report Server, the Run and Advanced Run actions are supported for normal reports but not for bursting reports. A page report containing only bursting report tabs cannot be run directly or in Advanced mode, it must be scheduled.
Scheduling is supported for both types of reports excluding the combination of the two types: for normal reports, multiple reports can be scheduled at a time; however, for bursting reports, only one can be scheduled. For a scheduled bursting task, you can use seven kinds of file formats: HTML, PDF, Excel, Text, RTF, XML, and PostScript. In addition, when scheduling to run a bursting report, you can make it generate not only the bursting result by applying bursting schemas but also the non-bursting result based on whole data without data splitting.
A bursting report may have one or more bursting schemas, and you need to apply one or more of them in order to get a bursting result, that is when you schedule a bursting report, you need to select the schemas in the General tab of the Schedule dialog box.
Then a tab named Bursting Result is displayed in the Publish tab and only the corresponding sub tabs that are defined in the selected bursting schemas' recipients in Logi Report Designer are available.
For example, a bursting report has three bursting schemas: Schema 1 defines recipient E-mail and Disk, Schema 2 defines recipient FTP, and Schema 3 defines recipient Logi Report Server Version. If Schema 1 and Schema 3 are selected, only To E-mail, To Disk, and To Version sub tabs will be shown in the Bursting Result tab of the Publish tab for the bursting result.
The following list shows which tab will be displayed in the Publish > Bursting Result tab of the Schedule dialog box for which recipient address specified in bursting schema.
|Recipient||Sub tab in the Publish tab|
|Logi Report Server Version||To Version|
|Logi Report Server User/Group/Role > User E-mail||To E-mail|
|Logi Report Server User/Group/Role > User Private Folder||To Version|
When scheduling a bursting report, you do not need to specify the destination in the Publish tab since the bursting schema has included the recipient addresses. However, you can give a file name to the subset of report instead of using the default name.
Sometimes you may not want to specify a file name for each bursting result when defining recipients. The bursting system will give it a default name. The default name format is: ReportName + "_" + BurstingKey + suffix (result format type). When there are multiple bursting key columns, they are connected by the character "_".
Converting to String
When a bursting key is of one of the following data types, Server converts it into String to make a valid result file name:
- Integer, Float, Character: Same as Java, Server transfers these data types to String directly.
- Date and Time: Server transfers all date and time formats to a date format: yyyy-MM-dd hh:mm:ss.
- Currency: Server transfers Currency to the number without the currency mark ($ or others).
In the Logi Report Server resource system, the resource name only supports up to 64-character length. If a bursting result file name is longer than that, the system will trim it down automatically.
To avoid the same name in the same path, Server appends an index to the result name, for example: report1_USA_Maryland1.pdf, report1_USA_Maryland2.pdf.
- All bursting sub results apply the security information of the bursting task submitter.
- When a busting report has applied with security policies or filters, Logi Report may not be able to obtain the bursting key from the specified bursting schema, in this case, it will not send the busting result.
Besides generating bursting result for a bursting report, you can also generate non-bursting result for the report without applying any bursting definition, which is based on full data without data splitting.
To generate non-bursting result, make sure the Non-bursting Result option is selected in the General tab of the Schedule dialog box. Then a tab named Non-bursting Result appears in the Publish tab, and all the publish types - To Version, To Disk, To E-mail, To Printer, To Fax, and To FTP - are available in this tab for the non-bursting result.