File Watcher allows the processing of a task only when a given file is present in a particular location. It is assessed before the processing of each occurrence of the task.
For example, a database administrator posts a text file to signal the successful reload of a data warehouse; when the text file is in the specified location, Broadcast Agent refreshes and distributes the documents.
You can use any kind of file with File Watcher. The file can be located anywhere: on a server, on the client, or on a file system. The only restriction is that the Broadcast Agent machine must be able to access the file.
With File Watcher, Broadcast Agent can work with all existing systems, including legacy systems, anywhere on the network. For example, a legacy system creates a file that Broadcast Agent is watching. Broadcast Agent then executes the scheduled task. This would create a new document that in turn triggers the creation of another document. This cascading chain of reactions and documents—tied to predetermined conditions—is called “report chaining.”
Access rights
In order to use File Watcher, the BOManager used for a particular task must have access rights to the specified file and location.
When a Broadcast Agent Scheduler detects a document in the repository that is due to be processed, it contacts the least busy BOManager on the cluster. This launches a BusinessObjects session (busobj.exe), which extracts the
document from the repository and processes it.
Each BOManager is configured with the user name and password of a Windows or UNIX user, and therefore has specific access rights to machines, disks, and directories.
For example, if you enter x:\Temp\Business Objects\file.txt in the
File Watcher box on the Scheduling Options page, the BOManager associated with the Broadcast Agent you selected must have read rights for server x and for the directory Temp\Business Objects on that machine.
See the Installation and Configuration guide for more information on configuring server rights.
Task scheduling How to set File Watcher
1. In the Task Properties dialog box, click the Scheduling tab. 2. Select the File Watcher checkbox.
3. Enter the path or browse for the file you want.
4. Choose the delete option you want from the drop-down list-box. 5. Click OK.
You can use either of two path naming conventions: • A standard local or remote pathname, such as
c:\Program Files\Business Objects\Demo\file.txt
- or -
x:\Temp\Business Objects\file.txt
• A valid UNC
UNC is a format for the location of resources on a LAN. UNC uses the following format:
\\<server name>\<shared resource pathname>
Business Objects recommends that you use a UNC because Broadcast Agent is distributed; therefore, a scheduled job may run on one of any number of servers. If you use a remote pathname, the drive must be properly configured on the BOManager server. When you use a UNC, however, the name of the server or machine on which the file is located is included, thereby ensuring that the Broadcast Agent server can find it.
If the Broadcast Agent can’t locate the file at task execution time, it will not run the task. However, Broadcast Agent will periodically try to refresh the document. How often it looks for the file is determined by the Scanning Repository Delay parameter, which you set when configuring the software on the server side. The default setting is 10 minutes.
EXAMPLE
Using File Watcher to control a task execution order
You have five tasks that you want to send to Broadcast Agent. You submit Job1, Job2, Job3, Job4, and Job5 at the same time, and want them to finish in numerical order, Job1 first and Job5 last. Of course, Job1 may take more time than Job2, so you must make sure each begins only after the previous job is completed.
To make all jobs submitted at the same time finish in a specific order, you use File Watcher. When selecting the actions for each job, you save each one as a text file and then set each job to watch for the previous report’s text file. For example, Job2 watches for job1.txt (which is then deleted to allow this solution to continue more than once) while Job3 watches for job2.txt, and so on.
Overview
This chapter provides solutions to a range of problems that may occur when using Broadcast Agent. Among the issues covered:
• Failed connection to the repository • Not all documents displayed in InfoView • Problems with printing performance
• Dates and times don’t match during international operations • Cartesian products
• Data from user-produced objects not appearing
Where you can get more troubleshooting information
If you receive an error message, the Error Message Guide can help you resolve the problem. This guide provides descriptions and solutions to the error messages returned by Business Objects products, including Broadcast Agent. For installation issues, see the Installation and Configuration Guide.
See Maximizing Your Information Resources on page 7 for a list of other useful documentation and information sources.
Resolving database connection failure