There are several performance options that you can set in Fusion Middleware Control.
This section contains the following topics:
You can use Fusion Middleware Control to allow or prevent updates to the default repository file.
Setting this parameter affects whether you can update the repository when the Administration Tool connects in both online and offline mode. It also affects whether you can perform other repository update operations using other utilities, such as biserverxmlcli. Note that the aggregate persistence feature is not available when repository updates are prevented.
Preventing repository updates can improve Oracle BI Server performance, because in this mode the Oracle BI Server does not need to handle lock control.
If you choose to prevent repository updates, then when the Administration Tool opens a repository in either online or offline mode, a message informs the user that the repository is read-only.
Before you begin this procedure, ensure that you are familiar with the information in Using Fusion Middleware Control.
For information about corresponding configuration file elements, see Mapping User Interface Labels with Configuration File Elements.
You can override the time to elapse, in minutes, before a user is automatically logged off.
Before you begin this procedure, ensure that you are familiar with the information in Using Fusion Middleware Control.
For information about corresponding configuration file elements, see Mapping User Interface Labels with Configuration File Elements.
This procedure describes basic configuration options for data in tables and pivot tables.
Advanced configuration settings are described in Configuring for Displaying and Processing Data in Views.
Before you begin this procedure, ensure that you are familiar with the information in Using Fusion Middleware Control.
For information about corresponding configuration file elements, see Mapping User Interface Labels with Configuration File Elements.
You can override the maximum number of rows that can be fetched and processed from the Oracle BI Server for rendering a table.
Reducing the number of rows in a table can significantly improve performance by reducing the system resources that can be consumed by a given user session.
Advanced configuration settings are described in Configuring for Displaying and Processing Data in Views.
Note the following when setting this value:
This specification applies to tables, not to pivot tables.
The default value is 65000. The minimum value is 50. If the user exceeds the maximum value, then the server returns an error message when the table view is rendered. The maximum value is at least 16 bits, which varies by platform. The system is likely to consume all its memory before approaching a number larger than this value.
Before you begin this procedure, ensure that you are familiar with the information in Using Fusion Middleware Control.
For information about corresponding configuration file elements, see Mapping User Interface Labels with Configuration File Elements.