|Bookshelf Home | Contents | Index | PDF|
In the Siebel Web Client, the report instance is obtained by the client in DHTML rather than ROI format, and the report is viewed using a Web browser window. In the Siebel Mobile Web Client, the Actuate Viewer is called the Siebel Report Viewer.
The current business object (obtained from the view) and the current query create a context that determines which data is sent to the report. In Mobile Web Client reporting mode in Windows, the data is passed through variables across the interface between the Siebel application and the embedded Actuate viewer, and it is accessed using methods in the report design. In Web Client reporting mode, the object interface is between the Object Manager and the Siebel Reports Server.
When the user is running a report from the Siebel Mobile Web Client, a corresponding report executable (ROX file) is invoked locally and the resulting instance (ROI file) appears. When a user is running a report from the Siebel Web Client or scheduling a report from the Siebel Mobile Web Client, the report executable is invoked on the Siebel Reports Server at the appropriate time, and the instance is stored on the Siebel Reports Server. It may also be obtained automatically from the Siebel Reports Server for local display, depending on the environment and the user's request.
NOTE: A Sun Java runtime environment (JRE) is required to view reports with a Developer Web Client or Mobile Web Client. For more information about the required Java Runtime Environment (JRE) version, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.
|Siebel Reports Administration Guide||Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices.|