Step 4: Redeploy J2EE Applications

A-2 System Administrators Guide for Oracle Business Intelligence Enterprise Edition Some parameters in NQSConfig.INI are centrally managed by Fusion Middleware Control and cannot be updated manually in NQSConfig.INI. Instead, use Fusion Middleware Control to change these parameters. Parameters that are centrally managed by Fusion Middleware Control are marked as such in this appendix, and are also identified by comments in the NQSConfig.INI file. See Appendix C, Mapping User Interface Labels with Configuration File Elements for additional information. Note the following rules and guidelines for NQSConfig.INI file entries: ■ The Oracle BI Server reads the NQSConfig.INI file each time it is started. ■ Each parameter entry in NQSConfig.INI must be within the section to which the parameter belongs Repository, Cache, General, and so on. ■ Each entry must be terminated with semicolon ; . ■ You can add comments anywhere in the NQSConfig.INI file. Comments must begin with either of the following: Any text following these comment characters up to the end of the line is ignored when the Oracle BI Server reads the file. ■ Any syntax errors prevent the Oracle BI Server from starting. The errors are logged to the nqserver.log file, which is located in: ORACLE_INSTANCE diagnosticslogsOracleBIServerComponentcoreapplication_obisn There might also be a summary message in the system log that relates to the error. If you get an error, then correct the problem and start the Oracle BI Server again. Repeat this process until the server starts with no errors. A.1.1 How to Update Parameters in NQSConfig.INI The following procedure explains how to update parameters in NQSConfig.INI. To update parameters in NQSConfig.INI: 1. Open the NQSConfig.INI file in a text editor. You can find this file at: ORACLE_INSTANCE configOracleBIServerComponentcoreapplication_obisn Make a backup copy of the file before editing. 2. Locate and update the parameter you want to change. 3. Save and close the file. Note: If you attempt to manually update NQSConfig.INI parameters that are centrally managed by Fusion Middleware Control, then the manually updated values are ignored, because the value set in Fusion Middleware Control overrides the value in the file. If you must manually update these settings, then you must disable all configuration through Fusion Middleware Control not recommended. NQSConfig.INI File Configuration Settings A-3 4. Restart the Oracle BI Server. For more information, see Section 4.1, About Starting and Stopping Oracle Business Intelligence. 5. If you have multiple Oracle BI Server instances, then repeat these steps in each NQSConfig.INI file for all Oracle BI Server instances. A.2 Repository Section Parameters The Repository section contains one entry for every repository that is loaded when the server starts. Syntax: logical_name = repository_name.rpd; Optional syntax: logical_name = repository_name.rpd, DEFAULT; In this syntax: ■ logical_name : A logical name for the repository. Client tools use this name to configure the ODBC data sources that connect to the repository. To use a reserved keyword for the name, such as OCI7 or OCI8, enclose it in single quotation marks. ■ repository_name.rpd : The file name of the repository. The file name must have the .rpd file extension, and the file must reside in the repository subdirectory. The demonstration repository file, SampleApp.rpd, is installed with the Simple installation type. When DEFAULT is specified for a repository, connections that do not specify a logical repository name in the DSN connect to the default repository. Example: Star = SampleApp.rpd, DEFAULT; A.3 Query Result Cache Section Parameters The parameters in the Query Result Cache Section provide configuration information for Oracle BI Server caching. The query cache is enabled by default. After deciding on a strategy for flushing outdated entries, you should configure the cache storage parameters in Fusion Middleware Control and in the NQSConfig.INI file. Note that query caching is primarily a run-time performance improvement capability. As the system is used over a period of time, performance tends to improve due to cache hits on previously executed queries. The most effective and pervasive way to Note: The default repository is centrally managed by Fusion Middleware Control and cannot be changed by manually editing NQSConfig.INI, unless all configuration through Fusion Middleware Control has been disabled not recommended. The Repository tab of the Deployment page in Fusion Middleware Control controls the default repository. The logical name of the default repository is always Star. See Section 10.2, Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location for more information. Note that you can manually add additional repository entries in NQSConfig.INI without having these entries overridden by Fusion Middleware Control. However, hosting multiple repositories on a single Oracle BI Server is not recommended for production systems.