By default, Financial Reporting components communicate with each other through Remote Method Invocation (RMI) on dynamically assigned Transmission Control Protocol (TCP) ports. To communicate through a firewall, you must specify the port of each Financial Reporting component separated by the firewall in the JConsole.exe file, and then open the necessary ports in your firewall.
In addition, you may need to open ports for the Reports Server RDBMs, for data sources that you report against, and for LDAP/NTMLM for external authentication.
Ports should be opened in the firewall only for Financial Reporting components that must communicate across the firewall. If the Financial Reporting components are not separated by a firewall, they can use the default dynamic port setting. |
The Scheduler server defaults to 8299, this can be changed by modifying the SchedulerServer property and restarting. The Print Server defaults to 8297. this can be changed by modifying the PrintServers property and restarting. Once connected, all RMI Services can use anonymous ports by default for communication. Alternatively a range of ports can be configured for communication by setting RMIPortRangeLower and RMIPortRangeUpper within the FR configuration The FR properties are now stored in the HIT registry and can be modified using JConsole or Enterprise Manager. You can change the port assignments to use in a firewall environment for servers in the JConsole.exe file using RMIPortRangeUpper and RMIPortRangeLower.
Note: | For information on JConsole, see the “Property Information” topic in the Oracle Hyperion Financial Reporting Workspace Administrator's Guide. |
Note: | If you are unable to connect to a Network Address Translated server from a Financial Reporting Studio install outside the firewall, the workaround is to add the DuseHostname=true JVM parameter on the foundation server, and add the following property in the default-domain.cfg: policies:iiop:server_address_mode_policy:publish_hostname="true". |