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 a better idea about the configuration.

Server Configuration

Fiorano Servers are pre-configured to run on a single System.


Please refer to the Configure Enterprise and Peer Servers section for detailed information on Server Configuration.

Providing Permissions on Windows Servers

For Fiorano 11 to work flawlessly and efficiently, the installer directory needs to have Administrator privileges. To grant permissions to specific/all users:

  1. Go to the directory where Fiorano 11 is installed.
  2. Right-click the FIORANO_HOME directory and click Properties.
  3. Go to the Security tab and click Edit.
  4. Select the desired user and then enable the Allow check box against the Full Control option present under the Permissions for Users section.
  5. 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 present in the installation directory. For a seamless execution of various processes, Fiorano recommends excluding FIORANO_HOME from antivirus checks.


Exclude FIORANO_HOME from McAfee antivirus checks, since McAfee intercepts the requests by blocking them.

Fiorano uses a set of fixed default ports that needs to be allowed through the server firewall for Fiorano Servers to interact with each other. These ports are specified within the server profiles.

The specific ports (default) that need to be allowed on the server are:

Fiorano Enterprise Server Default Ports

Port NumberPort Name
2047RMI Communications
1947External RTL Communications
1948HA Secondary External RTL Communications
2048RMI HA Secondary
1980Enterprise Server Dashboard
1847Internal calls
1848Internal calls HA Secondary

Fiorano Peer Server Default Ports

Port NumberPort Name
2067RMI Communications
1867Internal calls
1868HA Secondary Internal calls
2068RMI HA Secondary
1880Peer Web Server

Allow connections from all ports between the servers. Allow IP based communication and do not configure the firewall in a port-specific manner.


For information regarding Fiorano API Management server port numbers, refer to the IP Ports Reference Matrix section.

JVM Configuration File

Each script is associated with a specific configuration (conf) file ideally in the same location as the script file, with its name the same as that of the script file followed by the .conf extension. This configuration file provides various configuration properties of server/tools as shown below:

Config Property/BlockUsage


Specify any additional jar files required to be present in the classpath in a separate line at the end of this block.


Specify the jars other than the default jars to be considered in a separate line at the end of this block.


Specify the external jar files to be loaded along with the default system jars, in a separate line as the end of the block.


Specify the folders containing dll/so files that are to be loaded in a separate line at the end of the block.


Specify any additional system properties, in separate a line at the end of the block.


Specify any arguments to JVM such as memory settings and debug info in a separate line at the end of the block.

  • Comments can be written within the .conf file. A line starting with '#' is treated as a comment. 
  • A .conf file can have empty lines. These empty lines are simply ignored by the launcher.
  • Environment variables can be used in conf files (Using environment variables makes the .conf file platform dependent).
  • Wildcard such as lib/*.jar are not supported.

Profile Configuration

The Profile Management perspective in eStudio can be used for Offline configuration of Fiorano profiles.


Please refer to the Profile Management section to learn more about Profile Management.

HA Configuration

High Availability (HA) Servers maximize system availability and eliminate any single point of failure.


Please refer to the Configuring High Availability Servers to understand how to configure HA servers.

Adaptavist ThemeBuilder EngineAtlassian Confluence