Connectivity is generally one of the most difficult aspects of querying for end users to master. Client/server database applications rely on a complicated web of listeners, network addresses, and preferences that are difficult for anyone but a database administrator to troubleshoot.
Interactive Reporting users can sidestep these potential difficulties by using an Interactive Reporting database connection file (.oce files) to define the terms, conditions, and methods for connecting to data sources.
With a database administrator’s assistance, Interactive Reporting database connection files enable a stable connection to be set up once, and then distributed and reused. End users supply a database user name and password each time they log on to query a database.
Interactive Reporting database connection files retain all the information necessary to log on to a specific configuration of database and connection API software. In addition, Interactive Reporting database connection files retain DBMS‑specific connection preferences as well as specifications for automatic access to metadata (see Using Metatopics and Metadata ).
Interactive Reporting database connections store complete sets of connection parameters about:
Interactive Reporting database connections have significant advantages in network environments. One connection can be created for each database in the environment and shared with each end user.
Interactive Reporting database connection files simplify the connection process for company personnel by transparently handling host and configuration information. Each user can substitute their own database user name when using an Interactive Reporting database connection file (.oce), which enforces security measures and privileges that are centralized at the database server.
Because passwords are not saved, there is no danger that distribution provides unauthorized access to any user who receives the wrong Interactive Reporting database connection file or acquires it from other sources.
By default, no explicit Interactive Reporting database connection file is required to process Interactive Reporting document files or job outputs using the EPM Workspace or Interactive Reporting Web Client. That is, an user is not required to have specific access privileges to process an Interactive Reporting document file. However, a control setting of an Interactive Reporting document file or job access can be defined to require explicit access. For more information, see Oracle Hyperion Enterprise Performance Management Workspace Administrator's Guide and Oracle Hyperion Enterprise Performance Management Workspace User's Guide.