The Distribution tab in the Basic Scheduling tool provides the options available for distributing the report output for the scheduled report procedure (FEX). After selecting the option from the shortcut menu of a procedure, you can distribute a report output using one of the following methods.
Note:
Topics: |
How to: |
Reference: |
When you distribute a report through email, you can include the report in the body of the email (known as an inline email message) or send it as an attachment. Only the DHTML, DOC, GIF, HTML, JPG, PNG, SVG, and WP formats can be distributed as an inline email message.
Note: You must be authorized to distribute by Email in order to create a schedule that uses Email distribution.
Distributing a report as an inline email message is particularly useful when the report is distributed to mobile devices or through email systems that do not support attachments.
You can also distribute a report to a fax machine, as explained later in this section.
Note:
SET FOCEXURL='hostname:port/ibi_apps/'
SET FOCHTMLURL='hostname:port/ibi_apps/ibi_html'
Styling options include:
When you create a schedule that uses email distribution, you can type email addresses in the To field, as shown in the following image.
If you type multiple email addresses in the To field, you can use a semi-colon or comma symbol between each email address, to designate how the Distribution Server delivers information.
If you use the comma symbol to separate email addresses, all email addresses are visible to every email recipient.
The following image shows the email addresses EmailA@ibi.com and EmailB@ibi.com separated by a comma.
The schedule will distribute a report named Sales_Metrics_YTD.htm to these email addresses. When you run the schedule, the log report states that one report named Sales_Metrics_YTD.htm has been distributed to both email addresses through a single email, as shown in the following image.
If you use the semi-colon symbol to separate email addresses, each recipient only sees their own email address.
The following image shows the email addresses EmailA@ibi.com and EmailB@ibi.com separated by a semi-colon.
The schedule will distribute a report named Sales_Metrics_YTD.htm to these email addresses. When you run the schedule, the log report states that two reports named Sales_Metrics_YTD.htm have been distributed to EmailA@ibi.com and EmailB@ibi.com through separate emails, as shown in the following image.
Note: You can use parameters (amper variables) when specifying values in the Email settings of a schedule. These parameters can be system variables, such as &YYMD, or any amper variable for which a value is returned by the Reporting Server when the scheduled procedure is executed. To use the dot file extension separator after a variable, terminate the variable with the '|' character (for example, &YYMD|.htm). Similarly, to use the ampersand character itself, follow the ampersand with the '|' character (for example, Smith&|Jones). If a value for a parameter specified in a schedule is not returned by the Reporting Server when the procedure executes, the schedule will fail with a "No report to distribute" error. If the scheduled task is burst, you can also use the '%BURST' symbol to include the burst value. If the Packet Email setting is Yes, the burst value will not be substituted in the Zip filename.
The Basic Scheduling tool appears.
Additionally, you can use group mail lists (defined on your mail server) with the Email Address(es) option. You can use group mail lists to distribute a report or notification to multiple recipients without having to maintain multiple email addresses in the Repository. The format of the group mail list depends on the mail server being used. For example, if you are using a Microsoft Exchange Server and your group mail list is defined as #group1, you would enter group1@listdomain in the Email Address(es) field. If the group mail list contains a space within its name, enclose the space with double quotation marks ('' ''). For more information, see your mail server administrator.
When Dynamic Distribution List is selected, the To field is enabled to facilitate the selection of the Procedure Name. Once a procedure is selected, you can pass a parameter on the command line of the fex.
Note:
Note: If a default Mail Reply Address was not provided in the ReportCaster Configuration tool, the default Reply Address used for this field is the email address of the user that is signed in to WebFOCUS. ReportCaster obtains the email address of the user from the WebFOCUS security system.
Note: You can also provide a custom default distribution message using the Email Distribution and Notification settings in the ReportCaster Configuration tool in the ReportCaster Console. This allows you to override the default message, Please see attachment(s), by enabling you to create a custom message specific to your organization. The message displays when creating a schedule using Email distribution. The new message will not affect existing schedules.
Note: When you use the file option, the information can be maintained in one common place. It can also be revised among multiple schedules. There is no size limit to the contents of the file, other than what the email client and server support.
You have the option of converting your distributed report into a password-protected compressed file. By default, the Add Report to Zip File check box is not selected and the report will not be compressed. You can optionally password protect a zipped file by including a password in a Distribution File or Dynamic Distribution List.
Note: Support of Unicode characters in a Zip file name and content within a Zip file on Windows 7 and Windows 2008 Server R2 requires the following hotfix from Microsoft: http://support.microsoft.com/kb/2704299/en-us. Without this hotfix, file names are corrupted after you decompress a .zip file in Windows 7 or in Windows Server 2008 R2.
Note: Compression of files larger than 4 GB requires zip64 extensions. For more information, contact customer support.
The Email Distribution Options dialog box enables you to view and assign the Mail Server Name, select an SSL connection for the server, select a TLS connection for the server, require authentication for the server, and assign Account Name and Password. Click the Email Server icon to access Email Distribution Options.
Mail Server Name. The name of the mail server to be used by this schedule. The default value is set in the WebFOCUS configuration tool.
This server requires a secure SSL connection. Check this box if the specified mail server uses SSL.
This server requires a secure TLS connection. Check this box if the specified mail server uses TLS.
This server requires Authentication. Check this box if the specified mail server requires authentication with a user ID and password.
Account Name. A valid user ID for the specified mail server.
Password. The password for the specified user ID.
How to: |
This section provides information about distributing scheduled output using File Transfer Protocol (FTP). FTP distribution options can be accessed by clicking the FTP Server button in the Options group on the ribbon. The FTP Distribution Options dialog box is shown in the following image.
If the FTP Server requires SFTP, select the This server requires a secure SSH File Transfer Protocol (SFTP) check box. Select one of the following options to specify an authentication method:
Note:
SET FOCEXURL='hostname:port/ibi_apps/'
SET FOCHTMLURL='hostname:port/ibi_apps/ibi_html'
Styling options include:
Note: You can use parameters (amper variables) when specifying values in the FTP settings of a schedule. These parameters can be system variables, such as &YYMD, or any amper variable for which a value is returned by the Reporting Server when the scheduled procedure is executed. To use the dot file extension separator after a variable, terminate the variable with the '|' character (for example, &YYMD|.htm). Similarly, to use the ampersand character itself, follow the ampersand with the '|' character (for example, Smith&|Jones). If a value for a parameter specified in a schedule is not returned by the Reporting Server when the procedure executes, the schedule will fail with a "No report to distribute" error. If the scheduled task is burst, you can also use the '%BURST' symbol to include the burst value. If the multiple reports are distributed in one archive file, the burst value will not be substituted in the Zip filename.
The Basic Scheduling tool appears.
Distribution List. The report will be sent to all FTP addresses in the selected Distribution List. For more information, see Creating a Distribution List.
Note:
Note:
Without this hotfix, file names are corrupted after you decompress a .zip file in Windows 7 or in Windows Server 2008 R2.
How to: |
The report formats that support printing are DOC, PDF (when you configure ReportCaster to enable PDF to print and the printer has the appropriate driver), PS, and WP.
Note:
Note: You can use parameters (amper variables) when specifying a value for the Printer Name field of a schedule. These parameters can be system variables, such as &YYMD, or any amper variable for which a value is returned by the Reporting Server when the scheduled procedure is executed. To use the dot file extension separator after a variable, terminate the variable with the '|' character (for example, &YYMD|.htm). Similarly, to use the ampersand character itself, follow the ampersand with the '|' character (for example, Smith&|Jones). If a value for a parameter specified in a schedule is not returned by the Reporting Server when the procedure executes, the schedule will fail with a "No report to distribute" error. If the scheduled task is burst, you can also use the '%BURST' symbol to include the burst value.
The Basic Scheduling tool appears.
queue@printserver
where:
Is the name of the printer queue.
Is the host name or IP address of the printer.
ReportCaster can differentiate between the printer queue and the printer host name or IP address due to the presence of the '@' separator. Although ReportCaster supports specifying only the host name or IP address of the printer, we recommend that you specify both the printer queue and host name or IP address when distributing ReportCaster output to a printer. The maximum length of this field is 800 characters.
How to: |
The Report Library provides secure access to distributed report output stored in the Repository and allows you to save multiple versions of the same report output, set an expiration date, and keep a specified number of versions. The Report Library is only available to users who are authorized to access and view the Library reports in the folder location in which they are stored.
You can send an email notification informing users authorized to access the Library report of its availability. This will notify these users each time a new version is distributed and provide a URL to directly access the new version.
When creating a schedule for distribution to the Report Library, you select the folder to which the report output will be distributed. Using the Advanced button, you can optionally specify a subfolder to which the output will be distributed. If the subfolder does not exist, it is created dynamically during distribution of the initial schedule execution. During subsequent executions of the schedule, reports are distributed to the existing Library item where it is located. You must specify a pattern to be used for the title of the subfolder when the subfolder is created. The pattern can contain text, parameters (amper variables) and, if the scheduled task is burst, the ‘%BURST’ symbol. If the ‘%BURST’ symbol is used, a new subfolder is created for each burst value. You can also select the option to compress a library report when it is stored in the Repository.
You also have the option to specify a Category value to help you further organize the listing of Library reports within the ReportCaster Explorer. In the ReportCaster Explorer, a Category column is available that can be selected to sort Library reports by the Category values.
Note: A Library report in XML format must be opened in a new window.
When scheduling a report procedure (FEX) stored in the Repository, the default location the report output will be distributed to is the same as the report procedure (FEX) being scheduled. The best practice when distributing reports to the Library is to create and specify a different folder location for each Library report to avoid name conflicts when creating multiple schedules for the same report procedure (FEX). This is important so the security access can be defined and managed at the folder level, and when selecting to burst the distributed report output because the burst value is assigned as the title value to each report section that is distributed. The title value is the value that displays in the Resources tree.
For example, the Regional Product Sales (Quarterly) report is located in the Product Information folder. It is scheduled to distribute burst reports by region to the Regional Product Sales (Library Reports) folder, in the Library, on a quarterly basis. The Regional Product Sales (Library Reports) folder contains a library report for each region value included in the report request results. When creating additional schedules for the regional product sales report with the burst option, create and specify a different folder location because the burst report descriptions will be the same region values.
Note: You can use parameters (amper variables) when specifying values for the Library fields of a schedule. These parameters can be system variables, such as &YYMD, or any amper variable for which a value is returned by the Reporting Server when the scheduled procedure is executed. To use the dot file extension separator after a variable, terminate the variable with the '|' character (for example, &YYMD|.htm). Similarly, to use the ampersand character itself, follow the ampersand with the '|' character (for example, Smith&|Jones). If a value for a parameter specified in a schedule is not returned by the Reporting Server when the procedure executes, the schedule will fail with a "No report to distribute" error. If the scheduled task is burst, you can also use the '%BURST' symbol to include the burst value.
The Basic Scheduling tool displays in a new window.
Note:
Use the following information to set these options:
Note: If you distribute a compressed report to the Library, consider that this may impact the response time in viewing the report. A compressed report must first be decompressed before it is sent. You should evaluate the benefits of saving repository space against the impact of the time it takes to retrieve a compressed report from the Library.
Note: When the Access Option of an existing schedule is changed, it will be applied to all versions of the private Library report the next time a new version is distributed. Access options specified in the Library schedule are not applied to published Library Reports.
Use the up and down arrows to select the number of versions.
You can store up to 9,999,999 versions of a report in the library.
Note: The actual number of times a report can be run is 2exp(31) -1.
Note:
When you select this option, the following fields appear:
Note: You can configure ReportCaster to not send a link containing a URL. For more information, see ReportCaster Configuration.
Note:
When limiting Report Library distribution to values in an Access List, note the following:
How to: |
When creating a schedule with Report Library distribution, you can select the Domains folder in the Resources tree as the top-level folder location to which the sub-folders containing library reports will be burst.
You can schedule a library report to be placed in a sub-folder without having to create the sub-folder first. When you schedule a library report to be burst to a top-level folder, the distribution server will automatically create new sub-folders containing the burst library reports.
A library report does not have to be distributed to a single folder. Depending on which sub-folder pattern is used, a user can distribute library reports into multiple sub-folders based on the burst values defined by the chosen variable.
Note: In order to burst library reports to top-level folders, you must be authorized to create new sub-folders in the Domains folder.
The Distribution tab within the Basic Scheduling tool opens.
The Browse for Folder dialog box opens.
The Library Advanced Options dialog box opens.
For more information on WebFOCUS Variables, see ReportCaster Internal Variables.
New sub-folders containing your burst library reports are now created in the Domains top-level folder.
Note: The sub-folder structure is contingent on the variable that is used.
How to: |
When distributing scheduled output to Repository in the Basic Scheduling tool, specify the Repository folder location to which to distribute the report output.
Note: You must be authorized to distribute to the Repository in order to create a schedule that uses Repository distribution. You must also be authorized to distribute content to your selected folder. For more information, see the WebFOCUS Security and Administration manual.
The best practice for recurring and burst schedules is to create and specify a different folder location for each report being distributed for the same report procedure (FEX). This is important so the security access can be defined and managed at the folder level and when opting to burst the distributed report output because the burst value is assigned as the title value to each report section that is distributed. The title value is the value that displays in the Resources tree.
When the report output is distributed using the Repository distribution option, the Day, Date, and Time information is prepended to the Save Report As value specified in the schedule task information. For example, the Schedule for the Product Packaging & Price report is assigned the default Save Report As value 'Product_Packaging_Price.htm' (blanks and special characters are replaced with an underscore character).
The report output distributed to Managed Reporting on Monday December 19, 2011 at 1:35pm EST is assigned the description: Mon, 19 Dec 2011 01:35 PM EST Product Packaging Price.
The Basic Scheduling tool displays in a new window.
The Distribution Server adds Day, Date, and Time to the beginning of the Save Report As value specified in the Task tab.
Verify that the folder location is the folder to which you want to distribute the report output. The folder location defaults to the same folder as the report procedure (FEX) being scheduled. Users can select a different folder to distribute the report output to by clicking the Folder Location button, which will display a dialog box of the Resources tree from which a folder location can be selected, as shown in the following image.
Note: You must also be authorized to distribute content to your selected folder.
The Repository File System Distribution function allows you send reports to a directory accessible by the distribution server. When you distribute to the Repository with the File System configured, you can choose a File System folder, as shown in the following image.
Note:
A user must be granted the Distribute to File System privilege to use this distribution method. In addition, an Administrator must populate the File System Distribution Directories field in the Application Directories section of the Administration Console with a valid path for the folder. Users must be authorized to see these folders, which is done by granting users the list command on the File subsystem. For more information, see the WebFOCUS Security and Administration manual.
Once authorized, a user can schedule content to be distributed to a configured folder.
WebFOCUS | |
Feedback |