Launching Peer Server

The FPS can be launched from the Windows Start menu or by directly executing a script file.

When the peer server is launched, the enterprise server must be running on the configured machine for successful peer server startup. Please refer to section Configure Enterprise and Peer Servers in different Networks for instructions on how to configure the Enterprise Server URL for a Peer Server. If the Enterprise Server is not reachable by the Peer Server or if it is not running, the Peer Server keeps waiting until it can reach the Enterprise Server on a specific connection URL. The Enterprise Server starts successfully when the Peer Server is able to establish a connection with the Enterprise Server.

From Start Menu in Windows

Click Start > Programs > Fiorano > Fiorano Platform > Fiorano Servers > Fiorano ESB Peer

Using Script Files

Default Profile

To start the FPS server with the default profile (profile1), browse to the location <fiorano_installation_dir>\esb\server\bin and execute the following script:


By default , the server starts in FPS mode if 'mode' argument is not provided, that is, you can use the following script:

Specific Profile

To start the FES server with a specific profile other than the default profile, browse to the location: <fiorano_installation_dir>\esb\server\bin and execute the following script with the profile option as shown below:

Example: <profileName>=haprofile1/primary or <profileName>=haprofile1/secondary (This is to start servers in HA mode)

UNIX systems


In UNIX systems, servers will by default start in the background mode. Pass runtime argument –nobackground to the server startup script to run the server in console mode. If the servers are not to be run in background mode, modify the file %FIORANO_HOME%/launcher/ so that nobackground=“” is changed to nobackground=“true”.

Installing as Service

The batch/shell scripts required to run the Fiorano Servers as services are present at FIORANO_HOME/esb/server/bin/service.

To install FPS as a Windows NT service, run the command:


NT services will have to be re-installed if changes are made to any configuration files. This includes fiorano_vars.bat as well as server.conf.

To remove FPS as a Windows NT service, run the command:

UNIX Systems


To install/uninstall FPS as a service on UNIX, refer to ReadMeWrapperService.txt present under %INSTALL_DIR%/esb/server/bin/service directory.

Shutting Down the Peer Server

The FPS can be stopped from the Fiorano eStudio or by directly executing a script file. Shutting down the Peer Server automatically invokes a shutdown hook in the peer server’s JVM which cleans up any resources and connections used by the server’s JVM.

Using Fiorano eStudio

To shut down the peer server, perform the following actions:

  1. Open Server Explorer panel by navigating through Window > Show View > Other > Fiorano > Server Explorer.
  2. Expand Peer Repository, right-click fps node and click Shutdown.

    Figure 1: Shutting down FPS Server
  • Peer Server can be shut down only when you are already logged into it.
  • We recommend shutting down using command line (script files) than from eStudio (refer the section below).

Using Script Files

The Peer Server can be shutdown using the shutdown-server script present in <fiorano_installation_dir>/esb/server/bin folder.

  • Shutdown scripts cannot be used to shutdown both primary and secondary servers running in shared HA mode simultaneously using a RMI connection.
  • If HA profiles from previous versions are migrated to current version of the product, these profiles need to be re-configured to specify BackupRMIServerPort properties to make use of this functionality.

This script can be used to:

  • Shut down a standalone peer server.
  • Shut down both the primary and secondary HA servers simultaneously.

Options that can be specified within the script are:

  • -user: Name of the User trying to shutdown Fiorano server.
  • -passwd: Password of the User trying to shutdown Fiorano server.
  • -restart or –r: Restarts the Fiorano Server.
  • -ha: Used to shutdown both active and passive servers running in HA.
  • -mode: mode of the server, that is, fes or fps. Defaults to value fps.
  • -url: URL of the active Fiorano Enterprise Server to which the Peer Server has connected.
  • -fpsname: Fiorano ESB Peer name.
  • -? or –help: Prints help message.


To shut down a standalone Peer Server

To shut down both active/passive Peer Servers in HA


The default credentials are:

  • User name: admin
  • Password: passwd

The above examples of shutting down the Peer Server(s) involves connecting to an Active Enterprise Server, whose url is specified by the -url parameter.  

The following options can also be specified if a User wants to shutdown the Peer Server using a RMI connection. This involves connecting directly to the Peer Server to initiate the shutdown.

  • -connectorType: Connection type to server. Pass RMI for shutting down servers using RMI connection.
  • -address: IP Address of server
  • -rmiPort: RMI port of server

If the -ha option is given to shutdown both the servers of an ha pair, the address and rmiPort options can be specified as either the Primary or the Secondary server. This can be used if not certain of which server in the HA pair is the active one.


To shut down the Standalone Server

To shut down both active/passive servers in HA


The default credentials are:

  • User name: admin
  • Password: passwd

Clearing Peer Server Database

To clear the Peer Server database of the default profile (that is profile1), run the clearDBServer.bat executable file present in the <fiorano_installation_dir>\esb\server\bin folder or browse to this location and execute the following script:


The script by default clears the database of the Peer Server if an argument mode is not provided.

To clear the Peer Server database of a specific profile (other than the default profile), double-click the clearDBServer.bat file present in the <fiorano_installation_dir>\esb\server\bin folder or browse to this location and execute the following script with the profile option as shown below:

The following operations are available when this script is executed from which you may choose the option of your preference:

1. File BasedDatastoreClears the local cache of the Peer server.
2. Security DatastoreClears the Peer server's ACLs (Access Control Lists) and they will be recreated next time the peer starts.
3. Admin Datastore Clears the admin objects, that is, the JMS connection factories queues and topic destinations.
4. Cached Component Store Clears all the cached components stored in the Peer Server‘s runtime storage.
5. AllClears all five of the above.

Select the preferred number (from 1 to 5) corresponding to the datastore that needs to be cleared.

Figure 2: Options to clear datastore


Ensure that the Peer Server is shut down. If not you will get a message prompting to do the same (as in the figure above—"Please shutdown the Fiorano FPS Server")

This script can be executed in Quiet Mode as follows (sample):

  • -mode - to clear fps or fes runtimedata
  • -dbPath - runtime data directory for the profile
  • -profile - profile name for which runtimedata is to be cleared
  • -q - to run the script in quiet mode.

You can provide comma separated option values to the argument (as in the above sample script). Absence of an argument leads to the assuming the default option—option 5, ‘ALL’.

Adaptavist ThemeBuilder EngineAtlassian Confluence