This page explains the configuration files which are used to manage and configure Fiorano Servers for a particular environment, and also provides links to the sections which give better idea about the configuration.
Server Configuration
Fiorano Servers are pre-configured to run on a single System.
Providing Permissions on Windows Servers
For Fiorano 10 to work flawlessly and efficiently, the installer directory needs to have Administrator privileges. To grant permissions to specific/all users:
- Go to the directory where Fiorano 10 is installed.
- Right-click the FIORANO_HOME directory and open the Properties.
- Go to Security tab and click Edit.
- Select the desired user and then enable Allow check box against Full Control present under Permissions for Users section.
- Click Apply and click OK to grant permission.
Properties and Security settings for FIORANO_HOME
Turning Off or Excluding Fiorano Processes from Antivirus Checks
Fiorano Servers access various files in its installation directory, for all the processes to be able to run properly, we recommend excluding FIORANO_HOME from the antivirus checks.
On the Firewall level, Fiorano uses a set of fixed default ports that needs to be allowed on the server firewall for Fiorano Servers to interact with each other. These ports are specified in the server profiles.
The specific ports (default) that needs to be allowed are as mentioned below:
Fiorano Enterprise Server Default Ports
Port Number | Port Name |
---|---|
2047 | RMI Communications |
1947 | External RTL Communications |
1948 | HA Secondary External RTL Communications |
2048 | RMI HA Secondary |
1980 | Enterprise Server Dashboard |
1847 | Internal calls |
1848 | Internal calls HA Secondary |
Fiorano Peer Server Default Ports
Port Number | Port Name |
---|---|
2067 | RMI Communications |
1867 | Internal calls |
1868 | HA Secondary Internal calls |
2068 | RMI HA Secondary |
1880 | Peer Web Server |
JVM Configuration File
Each script is associated with a specific configuration file (conf) ideally in the same location as the script file, with the name as that of the script file followed by .conf as the extension. This configuration file provides various configuration properties of server/tools as shown below:
Config Property/Block | Usage |
---|---|
<java.classpath> | Specify any additional jar files required to be in classpath in a separate line at the end of this block. |
<java.endorsed.dirs> | Specify the jars to be considered other than the default jars in a separate line at the end of this block. |
<java.ext.dirs> | Specify the external jar files to be loaded along with the default system jars, in a separate line as the end of the block. |
<java.library.path> | Specify the folders containing dll/so files that are to be loaded, in separate line at the end of the block. |
<java.system.props> | Specify any additional system properties, in separate a line at the end of the block. |
<jvm.args> | Specify any arguments to JVM like memory settings; debug info, in a separate line at the end of the block. |
Profile Configuration
Profile Management Perspective in eStudio can be used for Offline configuration of Fiorano profiles.
HA Configuration
High Availability (HA) Servers maximize system availability and eliminate any single point of failure.