FO Processing Properties

The table below describes the properties that control FO processing.

Property Name Description Default Configuration Name

Use BI Publisher's XSLT processor

Controls the use of parser. If set to "false", uses the non packaged XDK parser. If set to "true", uses the 11g parser packaged in Publisher. If set to "12c", uses the 12c parser packaged in Publisher.

You can set this property at the server level or at the report level.

If the data size is more than 2GB, set to "12c".

If you set this property to "12c" at report level, ensure that you set the Set ACCESS_MODE to FORWARD_READ on XSLT processor property to '"false" at the server level and '"true" at the report level.

true xslt-xdoparser

Enable scalable feature of XSLT processor

Controls the scalable feature of the XDO parser. The property "Use BI Publisher's XSLT processor" must be set to "true" or "12c" for this property to be effective.

The value of this property should be "true" at both server level and report level. If you set to "false", FO processor uses memory (heap) instead of disk, and might cause out-of-memory issues.

false xslt-scalable

Enable XSLT runtime optimization

When set to "true", the overall performance of the FO processor is increased and the size of the temporary FO files generated in the temp directory is significantly decreased. Note that for small reports (for example 1-2 pages) the increase in performance isn't as marked. To further enhance performance when you set this property to true, set the Extract attribute sets property to "false".

true xslt-runtime-optimization

Enable XPath Optimization

When set to "true", the XML data file is analyzed for element frequency. The information is then used to optimize XPath in XSL.

false xslt-xpath-optimization

Pages cached during processing

This property is enabled only when you specify a Temporary Directory (under General properties). During table of contents generation, the FO Processor caches the pages until the number of pages exceeds the value specified for this property. It then writes the pages to a file in the Temporary Directory.

50 system-cache-page-size

Bidi language digit substitution type

Valid values are "None" and "National". When set to "None", Eastern European numbers are used. When set to "National", Hindi format (Arabic-Indic digits) is used. This setting is effective only when the locale is Arabic, otherwise it's ignored.

National digit-substitution

Disable variable header support

When set to true, prevents variable header support. Variable header support automatically extends the size of the header to accommodate the contents.

false fo-prevent-variable-header

Disable external references

When set to true, disallows importing of secondary files such as subtemplates or other XML documents during XSL processing and XML parsing. This increases the security of the system. Set this to "false" if the report or template calls external files.

true xdk-secure-io-mode

FO Parsing Buffer Size

Specifies the size of the buffer for the FO Processor. When the buffer is full, the elements from the buffer are rendered in the report. Reports with large tables or pivot tables that require complex formatting and calculations may require a larger buffer to properly render those objects in the report. Increase the size of the buffer at the report level for these reports. Note that increasing this value affects the memory consumption of the system.

1000000 fo-chunk-size

FO extended linebreaking

When set to true, punctuation, hyphenation, and international text are handled properly when line breaking is necessary.

true fo-extended-linebreaking

Enable XSLT runtime optimization for sub-template

Provides an option to perform XSL import in FOProcessor before passing only one XSL to XDK for further processing. This allows xslt-optimization to be applied to the entire main XSL template which already includes all its subtemplates.

The default is true. If you call the FOProcessor directly, the default is false.

true xslt-do-import

Report Timezone

Valid values: User or JVM.

When set to User, Publisher uses the User-level Report Time Zone setting for reports. The User Report Time Zone is set in the user's Account Settings.

When set to JVM, Publisher uses the server JVM timezone setting for all users' reports. All reports therefore display the same time regardless of individual user settings. This setting can be overridden at the report level.

User fo-report-timezone
Set ACCESS_MODE to FORWARD_READ on XSLT processor If you set the Use BI Publisher's XSLT processor property to "12c" at report level, ensure that the Set ACCESS_MODE to FORWARD_READ on XSLT processor property is set to "false" at the server level and "true" at the report level. false xslt-forward-read

PDF Bidi Unicode Version

Specifies the Unicode version (3.0 or 4.1) used to display the BIDI strings in the PDF output.

4.1 pdf-bidi-unicode-version