Exporting Reports and Dashboards
You can export reports to make them available to external applications, such as Microsoft Excel or if you’d like to generate a hardcopy, you can export them to a file, such as a PDF. The date on the report will be the date and time that the report was generated. Date and time are derived from the Portal Server’s time zone, which was determined when your administrator installed the Portal. Exporting data is limited to the first 20,000 rows. Reports longer than 20,000 rows are truncated when exported. The report output (PDF, HTML, CSV, etc.) displays the message “Data in this report has been truncated.” You can revise default number of rows by modifying the portal.properties file. See
Customizing the Maximum Number of Lines for Exported Reports.
Note: The exporting procedures described in this section should not be confused with exporting a Custom Report definition (created in the SQL Template Designer or Dynamic Template Designer). This information can be found in
Exporting/Importing SQL Templates.
To export report or dashboards
2. Click Actions and select Export with the report/dashboard displayed.
3. In the Export Report/Dashboard dialog box, choose the format. The report type dictates the available export options. Not all export types are available for all report types.
The following lists all potential options:
• CSV(.csv). Exports data to a spreadsheet or a database application such as Microsoft Access.
• Excel (.xls). Similar to the CSV export, this file supports MS Excel-specific features.
• XML (.xml). Accesses the web page components.
Note: XML is not available as an export type for dashboards.
• PDF (.pdf). This read-only file lends itself to easy distribution and printing.
• Text. A text file of the report. This selection provides the option to set a delimiter and use quotes in the exported file.
• HTML (.html). Exports this data as a web page, along with supporting files, in a zipped file.
The Export-to-HTML process produces a .zip file with all the necessary files. Extract the files and then click report.html to display the report. Depending on your browser’s settings, the file will be saved to your default location (typically, Desktop), or a dialog box launches and requires that you specify the location for the file.
4. Click Export Now.
5. Open or Save the file.
Note: For portals installed on Linux servers, reports that are emailed or exported as PDF files may produce output that includes a black box or that exceeds the size of the landscape. Verify that X Virtual Frame Buffer is installed. This graphical interface ensures that emailed and exported reports (PDF files) are rendered correctly.
Scheduling Exported Reports and Dashboards
You can only schedule exports for saved reports and dashboards.
Exporting data is limited to the first 20,000 rows. Reports longer than 20,000 rows are truncated when exported. The report output (PDF, HTML, CSV, etc.) displays the message “Data in this report has been truncated.” See
Customizing the Maximum Number of Lines for Exported Reports.
To schedule an export of a report and dashboard
2. Click Actions and select Export with the report/dashboard displayed.
3. On the
Export Report dialog box, choose the format. The report type dictates the available export options. Not all export types are available for all report types.
The following lists all potential options:
• CSV(.csv). Exports data to a spreadsheet or a database application such as Microsoft Access.
• Excel (.xls). Similar to the CSV export, this file supports MS Excel-specific features.
• XML (.xml). Accesses the web page components.
Note: XML is not available as an export type for dashboards.
• PDF (.pdf). This read-only file lends itself to easy distribution and printing.
• Text. A text file of the report/dashboard. This selection provides the option to set a delimiter and use quotes in the exported file.
• HTML (.html). Exports this data as a web page, along with supporting files, in a zipped file.
4. Click Schedule. When you schedule a report/dashboard to be exported on a regular basis, you must first configure a number of settings.
5. Define the schedule. Use the following table to configure a schedule:
Export | On a defined schedule - Master schedules can be configured and then applied to reports. Modifications to a master schedule are applied to all reports associated with that schedule. Hourly - Select 1, 2, 3, 4, 6, or 12 hours. Daily - At: hour/minute. Select a specific run time. Weekly: On every. Check the day(s) on which the report will run. At: hour/minute. Select a specific run time. Monthly: On the. Select the day on which the report will run. At: hour/minute. Select a specific run time. |
Export to the path* | Specify a sub-folder where the output will be saved. This sub-folder is relative to the default folder and it will be created if it does not already exist. If this field is left blank, the report will be saved in the base folder. The default base folder is set to: Linux: /opt/aptare/export Windows: C:\opt\aptare\export • For security reasons, the base folder for file exports is configured in the portal.properties file. Exporting to a network share requires that the share is already mounted on the Portal server and also configured in the portal.properties file. Note that this default base folder may have been changed by a Portal Administrator. • The sub-folder name that you enter is appended to the base folder path and the report is saved with a filename that matches the report name. Invalid characters will be replaced by an underscore. • To create a unique filename that will not be overwritten, use variables:
${month}-${year}-${hour}-${minute}. This will create a file in the base folder with a name similar to: 12-2015-21-1. • To separate the filename from the folder, use double slashes, similar to: myfolder//JobSummary-12-2015-21-1. FOR ADVANCED USERS: In some cases (for example, Managed Services Partners with hundreds of managed host groups), you may want to export to specific host group or report directories. Rather than configure each of these separately, use the following variables in the path specification to generate an individual report for each instance of the variable: ${hostGroup} For example: /opt/aptare/export/${hostGroup}/doc ${reportName} To overwrite/replace files each time the reports are exported, use the variables: ${day}, ${month}, ${year}, ${hour}, ${minute} where the day, month, year, hour, and minute are represented as 2-digits, such as 02. |
Run Status | Select Enabled or Disabled. This selection enables or disables the schedule for the report or dashboard to be exported. |
Generate reports for | Choose one of the following: • Existing scope - Creates a single report/dashboard based on the report’s scope. • Matching host groups - Creates multiple reports/dashboards, based on the list that results from the Expression Builder. See also Using the Expression Builder. |
Using the Expression Builder
6. Click Builder to create a regular expression to be used for searching for host group names with pattern matching.
7. Click Evaluate to view which host groups are selected.
Examples:
• .*NetBackup.* - the period specifies any character; the asterisk specifies zero or more of the preceding element.
• [abc] - simple alpha character match
• [a-zA-Z] - any alpha character in upper or lowercase
• [^abc] - any character except a, b, or c
• The Expression Builder is case-sensitive.
