Skip Headers
Oracle® Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition
11g Release 1 (11.1.1)

Part Number E10541-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

B Advanced Configuration Reference

This appendix provides advanced postinstallation configuration and administration procedures that are not specific to analyses, agents, dashboards, or the Oracle BI Presentation Catalog. Directions for configuring these components of Oracle Business Intelligence are in earlier chapters. Most administrators need not change the configuration settings that are described in this appendix.

This appendix includes the following topics:

B.1 Making Advanced Configuration Changes for Presentation Services

The Oracle BI Presentation Services process hosts most of the business logic of the Web server and provides the framework and interface for the presentation of business intelligence data to Web clients.

The instanceconfig.xml file stores the configuration settings that affect Oracle BI Presentation Services. Many configuration settings are available in Fusion Middleware Control and that is the preferred method for making configuration changes. If a particular settings is not available in Fusion Middleware Control, then you can change it using the instanceconfig.xml file. You can use the instanceconfig.xml file to customize various aspects of your deployment. You should make changes directly in this file only to change default elements, such as the name of the Oracle BI Presentation Catalog, or override internal default settings, such as those related to caches.

Several entries are present in the instanceconfig.xml file by default, including the path to the Oracle BI Presentation Catalog, and the name of the Oracle Business Intelligence Server data source name used by Presentation Services to access Oracle BI Server.


If you have previously made configuration changes by modifying the Windows registry, then you should migrate those changes to the instanceconfig.xml. In the Windows registry, entries under the Common key remain valid.

The following procedure provides information about general configuration changes that you can make. Before you begin this procedure, ensure that you are familiar with the information in Section 3.4, "Using a Text Editor to Update Configuration Settings."

To manually edit the settings for general configuration changes:

  1. Open the instanceconfig.xml file for editing, as described in Section 3.6, "Where Are Configuration Files Located?"

  2. Locate the section in which you must add the elements that are described in Table B-1.

  3. Include the elements and their ancestor elements as appropriate, as shown in the following example:

  4. Save your changes and close the file.

  5. Restart Oracle Business Intelligence.

Table B-1 Elements for General Configuration

Element Description Default Value


Specifies whether to allow the browser to save the password, using browser-specific password management software. If set to true, prompts the user to specify whether to save the password for future sign-ins.



Specifies domain information for a cookie that is sent to the browser.



Specifies the domain path to which cookies apply.



See Section B.1.1, "Protecting Pages in Oracle BI EE from Attack" for information.



Specifies the time to elapse, in minutes, before an unattended analysis is canceled. An unattended analysis is one that has not been accessed in the number of minutes specified by this setting. The minimum value is 2.

This element addresses the case where a user is editing an analysis and browses elsewhere, abandoning the analysis, at least temporarily. Do not set the value too small, however, as the user might return to the analysis.


B.1.1 Protecting Pages in Oracle BI EE from Attack

As the administrator, you must be aware of a security concern that is known as clickjacking. Clickjacking refers to the ability of attackers to subvert clicks and send the victim's clicks to web pages that allow themselves to be framed with or with JavaScript.

For example, suppose an attacker develops a Web site that uses an inline frame for an Oracle Business Intelligence Console application. When you visit this site, you are unknowingly clicking buttons on the inline-framed Console application. This vulnerability is very serious, because the attacker is not stopped by the same origin policy principles that apply to other Oracle Business Intelligence applications. You can find many examples of clickjacking documented on the Worldwide Web.

The term that describes preventing attackers from framing an application in an inline frame is frame busting. To affect frame busting, you use the InIFrameRenderingMode element in the instanceconfig.xml file. You can set the element to the following three values:

  • prohibit = Never allow content from Oracle BI Presentation Services to be rendered in an inline frame.

  • sameDomainOnly = (Default) Allow rendering of pages in an inline frame if the enclosing page was generated by the server in the same domain. By default, pages have the same domain if they were generated by the same server. See the Worldwide Web for information on the "same origin policy."

  • allow = Always allow content from Oracle BI Presentation Services to be rendered in an inline frame.

B.2 Using the JavaHost Service for Oracle BI Presentation Services

The JavaHost service gives Presentation Services the ability to use functionality that is provided in Java libraries to support the following components:

To configure the JavaHost service, you can manually edit the configuration elements for the service in its configuration file (config.xml), located in the ORACLE_INSTANCE\config\OracleBIJavaHostComponent\coreapplication_obijhn directory. See Table B-2 for a description of the elements. The elements are identified by their relative path starting from the JavaHost element.

The common subelements, such as InputStreamLimitInKB, do not apply to the MessageProcessor, Listener, or SSL loaders.

For information about manual editing, see Section 3.4, "Using a Text Editor to Update Configuration Settings."

Table B-2 JavaHost Service Configuration Elements in config.xml

Element Description


Contains the ListOfEnabledLoaders and Loader elements. These elements specify the components for the JavaHost service. Avoid editing the elements in the Loaders section.


Specifies the list of components (such as Oracle BI Scheduler and BI Publisher) to be enabled.

If this element is missing from the file, then all Loaders are enabled. If the element has an empty value, then all loaders are disabled.

Each component has a corresponding Loader element. The name of the component listed here must match the name that is specified in the corresponding Loader/Name element.


Contains the following elements, which specify configuration information for a specific component:

  • Name

  • Class

  • ConfigNodePath

  • ClassPath


Specifies the unique name of the component. Use this name in the ListOfEnabledLoaders element.


Specifies the main class for the component.


Specifies the XPath (starting from the JavaHost element) to the configuration information for the Loader.


Specifies the paths for the JAR files of libraries that the JavaHost service can use.


A subelement common to each loader that specifies, in kilobytes, the maximum input size for requests that are sent to JavaHost. A value of zero deactivates this limit. If the maximum size is exceeded, then an error message is displayed.

Default: 8192


A subelement common to each loader that specifies the name of the directory for the response files of requests.

Default: A default temp directory


A subelement common to each loader that specifies whether to create a response file when processing large requests.

Default: True


A subelement common to each loader that specifies whether to wait to process the request until a file is completely read.

Default: True


A subelement common to each loader that specifies, in kilobytes, the maximum size before using disk space for requests. For requests larger than this size, use disk space instead of memory to cache the requested data. The larger this value is the more memory that the JavaHost service might potentially use and the faster the request processing can occur. This setting also establishes the threshold for the LogLargeRequests element.

Default: 200


Contains the SocketTimeout element.


Specifies the idle timeout (in milliseconds) for the socket, after which the socket is returned to the idle sockets pool. JavaHost uses a socket polling mechanism to wait for new data on the whole set of idle sockets in a single thread. Initial messages in the idle pool are handled through Java NIO channels.

Default: 5000 (5 seconds)


Contains the following elements:

  • PermittedClientList

  • Port

  • Address

  • Secure


Specifies a list of IP addresses and host names from which JavaHost accepts incoming connections. Separate each client's IP address or host name by a comma. To accept all client connections, set this element to an asterisk (*).

Default: *


Identifies the JavaHost TCP/IP listening port.

Default: 9810


Specifies the network interface that JavaHost is to bind to. If this element has no value, then JavaHost binds to all available network interfaces.


Specifies whether to enable SSL encryption for the JavaHost service:

  • Yes: Enables SSL encryption

  • No: Disables SSL encryption

Default: No

For information about SSL, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.


Contains only the common subelements such as InputStreamLimitInKB, as they relate to converting SVG images to rasterized image formats.


Contains the following elements:

  • Enabled

  • DefaultUserJarFilePath

  • DefaultTempFilePath

  • DefaultPurgingPeriod


Specifies whether to enable the interaction of the JavaHost service with Oracle BI Scheduler:

  • True: Enables interaction with Oracle BI Scheduler

  • False: Disables interaction with Oracle BI Scheduler

Default: False


Specifies the default directory for storing JAR files for the Java extension utility.

When Oracle BI Scheduler is enabled, this element is required and accepts a single path.


Specifies the default directory for storing temporary files for Oracle BI Scheduler requests.

Default: the system temp directory


Specifies the default period (in seconds) for Oracle BI Scheduler requests to remove failed jobs.

Default: 300


Contains only the common subelements such as InputStreamLimitInKB and ReadRequestBeforeProcessing, as they relate to Oracle BI Publisher.


Contains elements that relate to SSL. Avoid modifying these elements.


Contains only the common InputStreamLimitInKB subelement by default, as they relate to graph generation. You can add other common subelements as necessary.