About Actuate Information Console pages
Actuate Information Console uses JSPs to generate web pages dynamically before sending them to a web browser. These JSPs use custom tags, custom classes, and JavaScript to generate dynamic web page content. The JavaScript, classes, and tags provide access to other pages, JavaBeans, and Java classes. For example, application logic in Actuate Information Console can reside on the web server in a JavaBean.
Web browsers can request a JSP with parameters as a web resource. The first time a web browser requests a page, the page is compiled into a servlet. Servlets are Java programs that run as part of a network service such as a web server. Once a page is compiled, the web server can fulfill subsequent requests quickly, provided that the page source is unchanged since the last request.
The channels JSPs and custom tags support viewing reports submitted to channels. The channels pages reside in <context root>\iportal\activePortal\private\channels. Users access channels by clicking Channel in the sidebar.
The filesfolders JSPs and custom tags support accessing repository files and folders. These JSPs and custom tags reside in <context root>\iportal\activePortal\private\filesfolders.
The submit request JSPs and custom tags support submitting new jobs. The submit request JSPs reside in <context root>\iportal\activePortal\private\newrequest. For specific information about running jobs using Actuate Information Console, see Using Information Console.
The options JSPs and custom tags support managing user option settings. The options pages reside in <context root>\iportal\activePortal\private\options.
The viewing JSPs and custom tags support the following functionality, depending on the report type:
For specific information about viewing reports using Actuate Information Console, see Using Information Console.
Use the default pages, customize the pages, or create entirely new pages to deploy your reporting web application.
| (c) Copyright Actuate Corporation 2011 |
|