| < Day Day Up > |
|
Working closely on the middle tier with the Forms Server is the Reports Server. They work in similar manners to each other, simply providing different outputs to the end user. Reports used to be called from the client with the data request simply being the transferred information, where now both the report interface as well as the end data has to be returned to the browser. Typical applications run as a combination of forms and reports (forms being the interactive and input agent into the database where inserts, updates, and deletes occur and reports being where static content data is returned for viewing). The reports engine is one of the components at the heart of Concurrent Processing along with PL/SQL stored procedures that drive many of the reports that users run.
Much like the Forms Server, you can start and stop the services with simple scripts and test the Oracle Reports Server from the Web.
To start up the server:
reports60_server start
To shut down the Reports Server:
reports60_server stop
To test the Reports Server's functionality from the Web:
http://server.your.company.com:8010/dev60html/ runrep.htm
Much like the Forms Server, the Reports Server's executables reside in the %ORACLE_HOME\bin directory and Table 6.2 provides a brief description of the components and the executables that are responsible for it.
Component | Executable Name |
---|---|
Reports CGI Executable | rwcgi60 |
Multi-Tier Server | rwmts60 |
Queue Viewer | rwrqv60 |
Reports Client | rwcli60 |
Reports WebCartridge | rwows60.so |
| < Day Day Up > |
|