Introduction | Information Center
To access the PDF Reports dialog, which opens in a new browser window, follow these steps:
Note: PDF Reports is only for use with PDF file generation when using the DHTML client.
The General Information section of the PDF Reports dialog allows you to configure your PDF generation to be performed either on the same server as IBM Alphablox or on a remote server. The following settings are available:
Displays either Available or Unavailable. Should always be Available for the internal server. If Unavailable for the PDF Report Server, IBM Alphablox cannot establish communication.
Displays either PDF Report Server or Internal Server. Internal Server means it is using the same process as IBM Alphablox. PDF Report Server is the remote server you define for processing PDF files. By default, IBM Alphablox uses the internal server. To change the setting, click on the Edit button.
PDF Report Server only. The PDF Report Server’s host name or IP address.
PDF Report Server only. The PDF Report Server’s port number.
PDF Report Server only. Compression level value can be 0 –
none
or 1 – minimum
to 9 – full
).
Default is 0 - none
. The level used to compress the XHTML sent
to the PDF Report Server and the level for the PDF Report Server to send the
PDF file to IBM Alphablox. This setting can be useful with limited
bandwidth between IBM Alphablox and the PDF Report Server.
The Activity Information section of the PDF Reports dialog allows you to view current information about the PDF processor:
The time the displayed information was retrieved.
The total amount of time spent processing PDF requests.
The total amount of requests processed (including successful and failed requests).
The total amount of request that could not be processed.
The current amount of active requests being processed at this time.
Applies to PDF Report Server only. The amount of free memory and total memory
available to the PDF Report Server. The Total number may not be a solid limit if
the –Xmx
Java setting was used). If there are no active requests,
the memory is garbage collected before getting memory information.