Fiorano has the concept of profiles, for example profile1, profile2, haprofile.

All these profiles can be run as either a Fiorano Enterprise Server or Fiorano Peer Server by specifying mode as 'fes' or 'fps'.

These profiles can be run as services on Mac OS X.

Any profile present under $FIORANO_HOME/esb/server/profiles can be made to run as a service.

Configuring Server JVM Settings prior to running as a service

The 'server.conf' file located under %FIORANO_HOME%/esb/server/bin contains various settings related to the JVM like bootclasspath,classpath,server memory,system properties etc. This file is used while creating configuration files required to run the server as a service.

The configuration files are generated under the following directories:

Please make sure you have made all the server JVM settings before installing the profile as a service.

Configuring Email Alerts for Server JVM Restart/Sudden Exit/JVM Hung Events

The Wrapper binary which is used to run the server as a service can generate email alerts when the server either restarts, exits unexpectedly or becomes hung.

Please refer to the file 'server.conf' located under %FIORANO_HOME%/launcher for the configurations.

Installing a Profile as a Service in Mac OS X

1. Open server-service.sh

2. Specify action of script as "ACTION=start"

3. Set FIORANO_HOME, uncomment it and uncomment "export FIORANO_HOME" line.

4. Set JAVA_HOME, uncomment it and uncomment "export JAVA_HOME" line.

5. Set the MODE of the server. Mode can either be 'FES' or 'FPS'. By default, it is 'FPS'.

6. Set the profile of the server. By default, the profile of the server is 'profile1'.

7. Set the DBPATH variable.The 'DBPATH' variable points to the location of the shared database. This parameter should be set if the user intends to run the server with a 'Shared High Availability' profile.

8. Uncomment 'cd $FIORANO_HOME/esb/server/bin/service' line.

9. Open com.fiorano.server.plist

10. For "ProgramArguments" key give the absolute path of server-service.sh in the <string> node.

11. copy com.fiorano.server.plist to /System/Library/LaunchAgents

12. To start as a service, restart the system or type "Launchctl load /System/Library/com.fiorano.server.plist" in the terminal.

13. If more servers are to be run as service, make copies of server-service.sh and com.fiorano.server.plist with different names.

    In plist files specify the "Label" key as the file name excluding plist extension. Follow the above steps to run as service.

Viewing Server Logs

Once started, console logs for FPS service can be viewed in the following log files:

Other logs pertaining to the server can be found under :

Once started, console logs for FES service can be viewed in the following log files:

Other logs pertaining to the server can be found under :

Uninstalling a Profile as a Service in Mac OS X

1. Go to /System/Library/LaunchAgents  directory.

2. Remove com.fiorano.server.plist and restart the system  

 OR

1. Go to %FIORANO_HOME%/esb/server/bin

2. Shutdown the server using 'shutdown-server.sh -mode <server name>' command.

2. type "Launchctl unload /System/Library/LaunchAgents/com.fiorano.server.plist" in the terminal.

3. Remove com.fiorano.server.plist from /System/Library/LaunchAgents folder.

Running Fiorano ESB Profiles as Services on Linux

Fiorano has the concept of profiles, for example profile1, profile2, haprofile.

All these profiles can be run as either a Fiorano Enterprise Server or Fiorano Peer Server by specifying mode as 'fes' or 'fps'.

These profiles can be run as services on linux operating systems.

Any profile present under $FIORANO_HOME/esb/server/profiles can be made to run as a service.

Configuring Server JVM Settings prior to running as a service

The 'server.conf' file located under %FIORANO_HOME%/esb/server/bin contains various settings related to the JVM like bootclasspath,classpath,server memory,system properties etc. This file is used while creating configuration files required to run the server as a service.

The configuration files are generated under the following directories:

Please make sure you have made all the server JVM settings before installing the profile as a service.

Configuring Email Alerts for Server JVM Restart/Sudden Exit/JVM Hung Events

The Wrapper binary which is used to run the server as a service can generate email alerts when the server either restarts, exits unexpectedly or becomes hung.

Please refer to the file 'server.conf' located under %FIORANO_HOME%/launcher for the configurations.

Installing a Profile as a Service in Linux

1. Open server-service.sh

2. Set FIORANO_HOME, uncomment it and uncomment "export FIORANO_HOME" line.

3. Set JAVA_HOME, uncomment it and uncomment "export JAVA_HOME" line.

4. Set the MODE of the server. Mode can either be 'FES' or 'FPS'. By default, it is 'FPS'.

5. Set the profile of the server. By default, the profile of the server is 'profile1'.

6. Set the DBPATH variable.The 'DBPATH' variable points to the location of the shared database.

   This parameter should be set if the user intends to run the server with a 'Shared High Availability' profile.

7. Uncomment 'cd $FIORANO_HOME/esb/server/bin/service' line.

8. Set RUN_AS_USER if you want to run the server as non root user

9. Copy the file server-service.sh to '/etc/init.d' directory.

10. To run this as a service with system startup, type "chkconfig --add server-service.sh". This will launch the service whenever the system starts up. The default priorities for the service to be started when the system starts up and the priority for the service to be shutdown when the system is shutting down are 20 and 80 respectively.The default run levels for the service are 2,3,4,5. The run levels and priorities can be configured as required by changing line 79 of server-service.sh i.e. '#chkconfig: 2345 20 80' .

11. Give Executable Permission, "chmod +x server-service.sh".

12. To start as a service, type "./server-service.sh start".

13. To stop the server, type "./server-service.sh stop".

Viewing Server Logs

Once started, console logs for FPS service can be viewed in the following log files:

Other logs pertaining to the server can be found under :

Once started, console logs for FES service can be viewed in the following log files: 

Other logs pertaining to the server can be found under :

Uninstalling a Profile as a Service in Linux

1. Go to '/etc/init.d' directory.

2. type the following commands:

 If chkconfig command is not supported by the Operating System, then install the profile as a service using the following command:

      Also the script file does not need to be copied to /etc/rc5.d directory in this case.

      'rc5.d' refers to run level 5 and 'S23' specifies that the service has a priority of 23 when the system starts up.

To uninstall the service type the following command: