Bookshelf Home | Contents | Index | Search | PDF

Siebel Reports Administration Guide > Getting Started > How the Siebel Application and Actuate Interact >

Run-Time Behavior

---

You can demonstrate the relationships (in Dedicated Web Client reporting mode) among a Siebel application, the Actuate software components, and an Actuate report designed for the Siebel environment.

To see the relationship between a Siebel report and the Actuate and Siebel software

If a Siebel application is running on your desktop, close it. Open the Actuate e.Report Designer Professional software.
Choose File >Open and navigate to Aclist.rod in C:\Siebdev\rptsrc\enu.

If your installation uses a non-English version of Siebel eBusiness Applications, you do not have an \enu folder. Instead, you have a folder in the appropriate language code for your installation, such as \deu for Germany.

See Global Deployment Guide for a list of three-letter International Standards Organization (ISO) language extensions.

Click the run button to compile and execute the report.

You see an error message such as:

OLE Server couldn't be started.

Click OK.

You see another error message such as:

This message is available only in English: A fatal error has occurred while generating the report. Please contact your administrator.

Close this error message box and halt the report execution.
Open Siebel Sales from the Start menu.
From the application-level menu, choose View > Site Map > Opportunities > My Opportunities.

The wrong view is intentionally being opened to demonstrate the result.

Return to Actuate e.Report Designer Professional with the Siebel application still open.
Run the report again by clicking the run button.

This time you see a different message, such as:

Finishing...
Idle
There is no data to display.

Close the Actuate Output message box and return to Siebel Sales.
From the application-level menu, choose View > Site Map > Accounts > My Accounts.
Return to Actuate e.Report Designer Professional and click the run button.

This time, the Account List report should run successfully.

This exercise demonstrates that a Siebel report does not run locally in Actuate unless two conditions are met:

A Siebel application is running, making the Siebel software available as an OLE container.
The current view in the application is based on the correct business object for supplying data to the report being run. In the case of the example, a report listing account data requires that a view based on the Accounts business object be active.

Since a user executes Siebel reports only from the views in which they are designed to be run, these kinds of errors do not occur in a properly configured Siebel application.

Note that when the user restricts the data in the view with a query, only the data meeting the query constraints appears in the report. The Siebel application passes only the data from the current query to the Actuate viewer.

Bookshelf Home | Contents | Index | Search | PDF