Working With Styling Resources and HTML Launch Pages
WebFOCUS configuration parameters which control the
location of styling resources and HTML launch pages should follow
the guideline below:
- The directories specified in WebFOCUS Administration Console/Configuration/Application
Directories/IBI_Approot_Directory and the application server web
deployment descriptor, approot.xml, should be the same. This value
should never be the same as that of the Reporting Server approot
configuration parameter.
HTML launch pages and styling resources such as StyleSheets,
cascading style sheets, images, JavaScripts, and similar resources,
are processed by both the Presentation Layer (front-end) and the
Reporting and Metadata Layer (Reporting Server).
x
For Managed Reporting based applications:
- Create HTML launch pages in the WebFOCUS repository.
- Store styling resources in the WebFOCUS repository. You can
use the Hidden Content folder, which is quite useful for referencing
resources that are required by applications, but remain hidden.
For non-Managed Reporting legacy self-service applications, styling
resources are referenced differently at design time and run time.
- Design (development)
time
- Create
HTML launch pages in Application Directories on the WebFOCUS Reporting Server.
This is the only option.
- Store styling resources in the location
specified by the WebFOCUS configuration parameter, WebFOCUS Administration
Console/Configuration/Application Directories/IBI_Approot_Directory.
Styling resources are exposed in the WebFOCUS development tools
under the Web node.
- Run time
- Copy HTML launch pages from the Application
Directories to the location specified by the configuration parameter
IBI_Approot_Directory and in the web deployment descriptor, approot.xml.
xReporting and Metadata Layer
Styling resources that are embedded in output generated
by the Reporting Server should reside in Application Directories.
Examples include:
- PDF output.
- HTML pages created when the setting SET HTMLEMBEDIMG=ON is in
effect.