Fiorano has the concept of profiles such as profile1, profile2, and haprofile. All these profiles can be run as either Fiorano Enterprise Server or Fiorano Peer Server by specifying the mode as 'fes' or 'fps' respectively.
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 such as bootclasspath,classpath,server memory, and system properties. 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:
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 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 line "export FIORANO_HOME".
4. Set JAVA_HOME, uncomment it and uncomment line "export JAVA_HOME".
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 line 'cd $FIORANO_HOME/esb/server/bin/service'.
9. Open com.fiorano.server.plist
10. For "ProgramArguments" key provide 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 the plist files, specify the "Label" key as the file name excluding the plist extension. Follow the above steps to run as a service.
Viewing Server Logs
Once started, console logs for FPS service can be viewed in the log files in:
Other logs pertaining to the server can be found in:
Once started, console logs for FES service can be viewed in the log files in:
Other logs pertaining to the server can be found inunder :
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 the 'shutdown-server.sh -mode <server name>' command.
3. Type "Launchctl unload /System/Library/LaunchAgents/com.fiorano.server.plist" in the terminal.
4. 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, and haprofile. All these profiles can be run as either Fiorano Enterprise Server or Fiorano Peer Server by specifying the mode as 'fes' or 'fps'.
These profiles can be run as services on the 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 such as bootclasspath,classpath,server memory,and system properties. This file is used when creating configuration files required to run the server as a service.
The configuration files are generated under the directory below:
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 line "export FIORANO_HOME".
3. Set JAVA_HOME, uncomment it and uncomment line "export JAVA_HOME".
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 line 'cd $FIORANO_HOME/esb/server/bin/service'.
8. Set RUN_AS_USER if the server is to run as a non root user
9. Copy the server-service.sh file to the '/etc/init.d' directory.
10. To run as a service with system startup, type "chkconfig --add server-service.sh". This will launch the service whenever the system starts. The default priorities for the service to be started when the system starts up and 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, that is, '#chkconfig: 2345 20 80'.
11. To assign Executable Permission, provide "chmod +x server-service.sh".
12. To start as a service, enter "./server-service.sh start".
13. To stop the server, enter "./server-service.sh stop".
Viewing Server Logs
Once started, console logs for FPS service can be viewed in the log files at:
Other logs pertaining to the server can be found under:
Once started, console logs for FES service can be viewed in the ollowing log files at:
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 commands:
If chkconfig
command is not supported by the Operating System, then install the profile as a service using the command:
To uninstall the service type the command: