Using the Administration Console to View Metrics for Java Components

7-6 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

4. Complete the User Session Expiry option using the description in the Help topic

for the page. Click the Help button on the page to access the page-level help for the box. 5. Click Apply, then click Activate Changes to execute your changes and release the lock to enable another system administrator to make changes.

6. Return to the Business Intelligence Overview page and click Restart.

For information about using methods in the Oracle BI Systems Management API to change settings, see Chapter 22, Introducing the Oracle BI Systems Management API. 7.3.3 Using Fusion Middleware Control to Set Configuration Options for Data in Tables and Pivot Tables Advanced configuration settings are described in Section 18.3, Configuring for Displaying and Processing Data in Views. Before you begin this procedure, ensure that you are familiar with the information in Section 3.2, Using Fusion Middleware Control to Update Oracle Business Intelligence Configuration Settings. To use Fusion Middleware Control to set configuration options for views: 1. Go to the Business Intelligence Overview page, as described in Section 2.2.2, Using Fusion Middleware Control to Manage Oracle Business Intelligence System Components. 2. Display the Performance tab of the Capacity Management page.

3. Click Lock and Edit Configuration to enable changes to be made.

4. Complete the elements using the descriptions in the Help topic for the page. Click the Help button on the page to access the page-level help for the following options: ■ Maximum Number of Rows to Download option ■ Maximum Number of Rows Per Page to Include option The value of these options cannot exceed the value that is specified for the MaxVisibleRows element, as described in Table 18–1 .

5. Click Apply, then click Activate Changes.

6. Return to the Business Intelligence Overview page and click Restart.

For information about using methods in the Oracle BI Systems Management API to change configuration settings, see Chapter 22, Introducing the Oracle BI Systems Management API.

7.3.4 Using Fusion Middleware Control to Set the Maximum Number of Rows Processed to Render a Table

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 Section 18.3, Configuring for Displaying and Processing Data in Views. Managing Performance Tuning and Query Caching 7-7 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 Section 3.2, Using Fusion Middleware Control to Update Oracle Business Intelligence Configuration Settings. To use Fusion Middleware Control to set the maximum number of rows that are processed to render a table: 1. Go to the Business Intelligence Overview page, as described in Section 2.2.2, Using Fusion Middleware Control to Manage Oracle Business Intelligence System Components. 2. Display the Performance tab of the Capacity Management page.

3. Click Lock and Edit Configuration to enable changes to be made.

4. Complete the Maximum Number of Rows Processed to Render A Table View

option using the description in the Help topic for the page. Enter an integer value greater than 50. Click the Help button on the page to access the page-level help for the box. 5. Click Apply, then click Activate Changes. 6. Return to the Business Intelligence Overview page and click Restart. For information about using methods in the Oracle BI Systems Management API to change configuration settings, see Chapter 22, Introducing the Oracle BI Systems Management API.

7.4 About the Oracle BI Server Query Cache

You can configure the Oracle BI Server to maintain a local, disk-based cache of query result sets query cache. The query cache allows the Oracle BI Server to satisfy many subsequent query requests without having to access back-end data sources such as Oracle or DB2. This reduction in communication costs can dramatically decrease query response time. As updates occur on the back-end databases, the query cache entries can become stale. Therefore, you must periodically remove entries from the query cache using one of the following methods: ■ Manually. In the Oracle BI Administration Tool, in the Manage menu, select Cache to open the Cache Manager. The Cache Manager provides the most flexibility in choosing which cache entries to purge and when to purge them, but it requires manual intervention. See Section 7.7.4, Using the Cache Manager for more information. ■ Automatically. In the Administration Tool, you can disable cache for the system, set caching attributes for a specific physical table, and use Oracle Business Intelligence event tables to purge cache automatically. See Section 7.6, Monitoring and Managing the Cache for additional information.