In this section:
With Server Side Graphics, a servlet generates graphs on the web or application server and delivers them to the browser as bitmap images (such as .png, .gif, or .jpg) or in a vector format embedded in a PDF document.
There are two options when using servlet. They can be set in cgivars.wfs through the WebFOCUS Administration Console.
Graphs are generated by threads of existing application server processes. This is the default and normally is recommended.
A new Java VM process is launched when generating graphs.
With HOLD graphs, the WebFOCUS Reporting Server uses the graph engine to create the graphs either locally or through an HTTP call to the application server. Graphs are then stored on the WebFOCUS Reporting Server. This is required when ReportCaster must distribute graphs in a PDF, but you may find other reasons to use it. The following options are available for HOLD graphs.
The WebFOCUS Reporting Server makes an HTTP call to the application server in order to generate the graphs. When the graph is created, it is stored in a directory on the WebFOCUS Reporting Server machine.
GRAPHSERVURL is enabled by default and normally requires no configuration.
The WebFOCUS Reporting Server uses its JSCOM3 service to generate graphs. JSCOM3 is a listener installed with the WebFOCUS Reporting Server and it handles the Java code needed to generate server-side graphs. Procedures run as threads of the JSCOM3 process.
JSCOM3 is used if GRAPHSERVURL is not set in cgivars.wfs or a procedure. It can also be used if GRAPHSERVURL is overridden in a procedure. It is not used if you set an IBIJAVAPATH environment variable.
If you do not wish to use GRAPHSERVURL or JSCOM3, you can use the IBIJAVAPATH method where the server launches Java processes to generate server-side graphs.