A report that uses the iServer API returns the expected results only when it is run on iServer. When the report is run in Actuate BIRT Designer, the report cannot access the iServer to retrieve the server information, and the report typically returns null values. Therefore, you cannot debug the iServer API calls in the same way you debug other event handlers in Actuate BIRT Designer.
To debug iServer API calls, use the appendToJobStatus( ) method to write a debugging message for each event handler. For example, if you write a JavaScript event handler for the beforeFactory event, add the following line of debugging code:
reportContext.getAppContext().get("ServerContext").appendToJobStatus("Debugging: beforeFactory called.\n");
scontext = (IServerContext) reportContext.getAppContext().get("ServerContext");
The appendToJobStatus( ) method writes a specified string message in the status section of a job-completion notice. After running the report on iServer, you can view these messages in either iServer Management Console or iServer Information Console.
In Management Console, choose Jobs—Completed, then choose the job’s details. The job’s Status page displays the debug messages in the Status section, as shown in Figure 24-3.
In Information Console, choose My Jobs—Completed, then choose Details next to the job whose status you want to review. The debug messages appear in the Status section in the job details page, as shown in Figure 24-4.
|
Figure 24-4
|
Debug message in the status section in the job detail page in Information Console
|
