Oracle BI Presentation Services Message Structure

9-2 System Administrators Guide for Oracle Business Intelligence Enterprise Edition This section contains the following topics: ■ Section 9.1.1, Setting Up Direct Insertion to Collect Information for Usage Tracking ■ Section 9.1.2, Setting Up a Log File to Collect Information for Usage Tracking

9.1.1 Setting Up Direct Insertion to Collect Information for Usage Tracking

Direct insertion is the recommended method for setting up usage tracking. To set up direct insertion, update the following parameters in the Usage Tracking section of the NQSConfig.INI file: ■ ENABLE. Set this parameter to YES to enable usage tracking. ■ DIRECT_INSERT. This parameter determines whether the query statistics are inserted directly into a database table or are written to a file for subsequent loading. Set this parameter to YES to enable direct insertion. ■ PHYSICAL_TABLE_NAME. To insert query statistic information into a table, you must provide the name of the table and the connection pool that is used to access the table see the CONNECTION_POOL parameter. The fully qualified physical table name consists of as many as four components database name, catalog name, schema name, and table name. Each component is surrounded by double quotation marks and separated by a period .. The physical table name must be fully qualified. This fully qualified physical table name must match a table name in the physical layer of the loaded repository. The following is an example of a physical table name for the Usage Tracking table in the Oracle Business Intelligence repository: PHYSICAL_TABLE_NAME = Oracle BI Usage.Catalog.dbo.S_NQ_ACCT ; In this example, Oracle BI Usage represents the database component, Catalog represents the catalog component, dbo represents the schema component, and S_NQ_ACCT represents the table name. ■ CONNECTION_POOL. The fully specified connection pool name has two parts: database name and connection pool name. Each part is surrounded by double quotation marks and separated by a period .. The fully qualified connection pool name should match a connection pool name in the physical layer of the loaded repository. For an example, see the following connection pool name in the Oracle Business Intelligence repository: CONNECTION_POOL = Oracle BI Usage.Connection Pool ; In this example, Oracle BI Usage represents the database component and Connection Pool represents the actual connection pool name. For Usage Tracking insertions to succeed, the connection pool must be configured with a user ID that has write access to the back-end database. See Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for information about configuring connection pools. Note: It is recommended that the connectivity type supports international data.