This section describes the differences between Oracle Essbase ports and connections when running this release of Financial Reporting.
A 100 concurrent user license for Oracle Essbase means 100 Oracle Essbase ports are licensed.
An unlimited number of connections is allowed on each of those ports.
The number of connections you open to Oracle Essbase is not relevant for licensing purposes. What matters is the number of Oracle Essbase ports.
When a user runs a report in Financial Reporting, connections are opened to Oracle Essbase. For performance optimization purposes, these connections are cached. When the connections become idle, a process is run periodically to close them.
The system administrator can modify the length of time before a connection is considered inactive (MinimumConnectionInactiveTime, default of 5 minutes) and the length of time before inactive connections are closed (CleanUpThreadDelay, default of 5 minutes) in the JConsole.exe file.
Note: | for information on JConsole, see the “Property Information” topic in the Oracle Hyperion Financial Reporting Workspace Administrator's Guide. |
The number of ports used by Financial Reporting varies, depending on the configuration, as follows:
If a Report Client such as the Windows UI runs a report, two Oracle Essbase connections are made; one for the Report Client, and one for the Report Server.
If the Report Client and Report Server are on the same computer, two Oracle Essbase connections using one Oracle Essbase port are made.
If the Report Client and Report Server are on two different machines, two Oracle Essbase connections using two Oracle Essbase ports are made.
The Report Client keeps the Oracle Essbase connection until the window with the report displayed is closed.
The Report Server keeps this Oracle Essbase connection until the process is run to close idle open connections.
When the Report Client connection is closed, the corresponding port for that connection is released.
When the Financial Reporting connection is closed, the corresponding port for that connection is released.
When a Reporting Studio user such as the Browser UI runs a report, two Oracle Essbase connections are made: one for the web server and one for the Report Server.
If the web server and Report Server are on the same computer, two Oracle Essbase connections using one Oracle Essbase port are made.
If the web server and Report Server are on two different computers, two Oracle Essbase connections using two Oracle Essbase ports are made.
The web server keeps the Oracle Essbase connection until the process is run to close idling open connections.
The Report Server keeps this Oracle Essbase connection until the process is run to close idling open connections.
When the web server connection is closed, the corresponding port for that connection is released.
When the Report Server connection is closed, the corresponding port for that connection is released.
The recommended configuration is as follows:
The Report Server and web server are installed on the same computer.
The Report Client is installed on several other computers. In this case, you must take two Oracle Essbase ports only for users working with the Report Client. All users connecting to view reports in EPM Workspace take a single Oracle Essbase port for each Oracle Essbase user, because the web server and Report Server are on the same computer.