Skip to main content
Skip table of contents

Configuring Standalone Servers

Contents

All Servers on the Same Machine

If a single machine has more than the recommended RAM and processing capabilities, then the servers can be deployed on the same machine. However, if a large number of processes are required to run and the available hardware configuration does not support the memory requirements of the business process, then users have to consider distributed deployment of servers.
Enterprise Server on a Machine and Peer Servers on Separate Machines
Another popular installation strategy is to have a dedicated machine for the central controller – the Fiorano Enterprise Server. Peers can be distributed across other machines. With this approach it is possible to distribute the load across multiple mid-range machines as compared to using a single high-end machine.

Configuring FES and FPS Profiles

The pre-built profiles, with default configuration in FES and FPS, are ready to run on a single machine. A different profile can be created with customized property values for interacting with different connections.
Note that for all changes made on FES configuration, alter the corresponding FPS configuration as well. For example, if the MaxClientConnectionsCount property is changed in FES to accommodate more peer connections, the change has to be made in the corresponding FPS MaxClientConnectionsCount property as well.

Profile Management perspective

The Fiorano eStudio acts as the visual interface to the ESB Server function for the End-User.
Profile Management Perspective in eStudio can be used for Offline Configuration of Fiorano profiles. To enable communication between Standalone Enterprise Server (FES) and Peer Server (FPS), FES and FPS Profiles need to be configured.
The default profile is Profile1 (located at $FIORANO_HOME/esb/server/profiles); to load and open FES and PPS profiles from Profile1:

  1. Stop the FES and FPS as the properties will be disabled (cannot be edited) if the servers are running.
  2. In eStudio, open Profile Management perspective by navigating to the below path: Window > Open perspective > Other > Profile Management.



  3. To load FES profile, right-click Profiles node and navigate to: Load Profile > Fiorano ESB > profile1 > FES



  4. Click the Component tree panel (the panel in the middle) to view the Properties of FES panel.



  5. To load FPS profile, right-click Profiles node and navigate to: Load Profile > Fiorano ESB > profile1 > FPS.



  6. Click the Component tree panel to view the Properties of FPS panel.

When both the profiles are loaded, to open or switch between the profiles, do any one of the two options below under Profiles node:

  • Double-click FES/FPS.
  • Right-click FES/FPS and click Open.

FES Configuration

FES server communicates with Peer Servers and tools using different ports. The basic configuration required are mentioned in the below sections.

External Port

External Ports or External Server Ports facilitate the communication between FES and external tools. The FES checks these ports for any requests from external tools.
To configure External Port:

  1. In the Component tree panel of Profile Management perspective, navigate to: FES > Esb > Transport > FESTransportManager.



  2. Under ComponentInstanceConfiguration section in the Properties of FESTransportManager panel, change the port number in ServerUrl value. Note: The default External Port for FES is '1947'.

Server URL specifies the URL on which the Enterprise Server accepts client connections. If localhost or loopback address is specified, then Enterprise Server will not accept connections from external machines.
FES can accept connection using various transports, that is, TCP or HTTP with or without SSL(JSSE).

Transport

URL

TCP

tsp_tcp://localhost:1947

TCP with JSSE

tsp_tcp_jsse://localhost:1947

HTTP

tsp_

http://localhost:1947

HTTP using JSSE

tsp_http_jsse://localhost:1947

Internal Server Ports

Internal Server Ports or Internal Ports facilitate the communication between FES and FPS servers. FES checks these ports for any requests from external tools.
To configure internal Ports:

  1. In the Component tree panel of Profile Management perspective, navigate to: FES > Fiorano > socketAcceptors > port-1 > ConnectionManager.



  2. Under ComponentInstance Configuration section in the Properties of ConnectionManager panel, change the property values for the properties in the below table.

    Attribute Name

    Description

    Default Value

    Port

    Port used for binding the socket on server startup

    1847

    MaxClientConnectionsCount

    Maximum number of client connections for the Connection Manager

    1024

    ServerAddress

    Specific InetAddress of the local machine that the Server needs to bind to. This option is very useful when Server is executed on multi-homed machines.

    Blank (no value), randomly picking available IP addresses.

RMI Ports

RMI Server Port or RMI Port facilitate the communication between FES with JMX clients. It is in this port that the Mx4JConector server binds.
To configure RMI Ports:

  1. In the Component tree panel of Profile Management perspective, navigate to: FES > Fiorano > jmx > connector > RMIBasedJMXConnector.



  2. Under ComponentUnstance Configuration section in the Properties of RMIBasedJMXConnector panel, change the RMIServerPort property as required. Note: The default RMI Port for FES is 2047.

Jetty Port

Jetty Port is used by the embedded Jetty Server. This port helps to run Fiorano Dashboard.
To assign a different port:

  1. In the Component tree panel of Profile Management perspective, navigate to FES > Fiorano > Esb > Jetty > Jetty



  2. Under ComponentInstanceConfiguration section in the Properties of Jetty panel, change the port number in PortNumber property.

    Default Jetty port number is '1980'.

Making changes in FES Profile

  1. In the Component tree panel of Profile Management perspective, navigate to FES > Fiorano > Esb > Peer > Transport > FPSTransportManager > MQProvider



  2. Under Component Configuration section in the Properties of MQProvider panel, replace the anonymous user credentials with the known server credentials.

FPS Configuration

The FPS server communicates with the Enterprise Server using the Server Port and with the JMX interface through the RMI Port. Configuration of these ports is described in more detail below.

Server Ports

Server Ports facilitate communication between FPS and Enterprise server.
To configure server port:

  1. In the Component tree panel of Profile Management perspective, navigate to: FPS > Fiorano > socketAcceptors > port-1 > ConnectionManager.



Under ComponentInstance Configuration section in the Properties of ConnectionManager panel, change the values of the properties as given below.

Attribute Name

Description

Default Value

Port

Port used for binding the socket on server startup

1867

MaxClientConnectionsCount

Maximum number of client connections for the Connection Manager

1024

ServerAddress

Specific InetAddress of the local machine that the Server needs to bind to. This option is very useful when Server is executed on multi-homed machines.

Blank (no value), randomly picking available IP addresses.

RMI Ports

RMI Ports or RMI Server Ports facilitate the communication between FPS and JMX clients. It is in this port that the Mx4JConector server binds.

To configure RMI Ports:

  1. In the Component tree panel of Profile Management perspective, navigate to: FPS > Fiorano > jmx > connector > RMIBasedJMXConnector.



  2. Under ComponentInstance Configuration section in the Properties of RMIBasedJMXConnector panel, change the RMIServerPort property as required. 

    The default RMI Server Port number is '2067'.

Jetty Port

Jetty Port is used to run Fiorano Dashboard.
To assign a different port:

  1. In the Component tree panel of Profile Management perspective, navigate to: FPS > Fiorano > Esb > Jetty > Jetty.



  2. Under ComponentInstanceConfiguration section in the Properties of Jetty panel, change the port number in PortNumber property.

    Default Jetty port number is '1880'.

Changing to different ESB Network

To configure a Peer Server onto a different ESB Network or to connect FPS to the Enterprise Server running on some other machine:

  1. In the Component tree panel of Profile Management perspective, navigate to: FPS > Fiorano > Esb > Peer > Transport > FPSTransportManager > EnterpriseServer



  2. Under Component Configuration section in the Properties of EnterpriseServer panel, replace the UserName: "anonymous" and the default password with the credentials of the designated Server.

    Transport Configuration Attributes

    Attribute Name

    Description

    Default Value

    ServerName

    Name of the Fiorano Enterprise Server to connect to

    FES

    PrimaryURL

    Primary URL of the FES server

    http://<FES Primary IP>:1847

    BackupURLs

    Backup URLs separated by semicolons are used when FES is not available at the primary URL.

    http://<FES Secondary IP>:1848

    Username

    Username to be used to create a connection with the FES

    Anonymous

    Password

    Password to be used while connecting to the FES

    Anonymous

    ConnectionFactory

    TopicConnectionFactory to be used to create the JMS Connection with the Enterprise Server

    primaryTCF

    QueueConnectionFactory

    QueueConnectionFactory to be used to create the JMS Connection with the Enterprise Server

    primaryQCF

    ConnectionRetryCount

    Number of times the Peer should try to connect to the FES if the connection is not available

    1 implies infinite retries - -1

Creating Profiles

After changing the configurations in a profile, it can be saved as a separate profile, or can be done vice-versa, that is, a new profile can be created to configure it by opening the respective profile.

Creating a New FPS Profile

  1. Stop the FPS if it is running.
  2. Open the default FPS profile from Profile1 by following the steps in Profile Management perspective section above.
  3. Under Profiles node, right-click FPS and click SaveAs.



  4. In the Profile Location Dialog dialog box:
    • Parent Directory: Click Browse, to choose the main directory to save the new profile. Choose "$Fiorano_home/esb/server/profiles" where default profiles are available so that all the profiles are available in a single location.
    • Destination Directory: Provide a name for the new profile folder to differentiate it from the default profiles.

  5. Click OK to complete the new profile creation.



  6. In the Profile Saved dialog box, click Yes to load the new profile or click No to open it later.

Renaming the New FPS Profile

After loading the new profile, rename it to identify it easily because name of all the Enterprise Servers will appear as 'FES' and peer servers appear as 'FPS'.
To rename the profile,

  1. Right-click FPS present in the Component Tree panel and click Rename. In the Rename dialog box, provide a unique name that represents the custom configuration in the new profile.



  2. New name will get reflected in the Component Tree panel but to save the change in name, right-click FPS (or File > Save) under Profiles node and click Save.

Opening the New FPS Profile

After creating a new profile, to open this profile:

  1. Right-click Profiles node, go to Load Profile and click Other.



  2. In the Select Profile dialog box, navigate to the location where the new profile was saved and click OK; the new profile will be loaded.

Launching the server on the new profile

To launch the FPS on the new profile, use the following command at the location: "$Fiorano_home/esb/server/bin":

Linux:

CODE 
 server.sh -mode fps -profile <profilename>


Windows:

CODE 
 server.bat -mode fps -profile <profilename>

Running Fiorano Profiles as NT services

Profiles (default or new ones) can be run as NT services on Windows NT, Windows 2000 and Windows XP operating systems.

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, and so on. This file is used while creating configuration files required to run the server as an NTService.

Before installation of server profiles as services on Windows Server 2003/2008, add the following line under '<java.system.props>' tag in the server.conf file:
java.io.tmpdir=C:/Windows/temp

Installing Profiles as NT Service

To install a Profile as NT Service:

  1. In the Command Prompt, go to the Go to %FIORANO_HOME%/esb/server/bin/service directory.
  2. Use the following commands for FES and FPS respectively:
    • install-fes.service.bat -profile %PROFILE_NAME%
    • install-fps.service.bat -profile %PROFILE_NAME%
  3. Start the NT Service
    • using the following commands for FES and FPS respectively:
      • start-server.service.bat -mode fes -profile %PROFILE_NAME%
      • start-server.service.bat -mode fps -profile %PROFILE_NAME%

or

    • from Windows:Go to services.msc from Run and click Start link on Start the service.

The name in the service appears as:

    • FES: Fiorano ESB Server <%PROFILE_NAME%>
    • FPS: Fiorano Peer Server <%PROFILE_NAME%>
  1. To Stop the NT Service,
    • use the following commands for FES and FPS respectively:
      • stop-server.service.bat -mode fes -profile %PROFILE_NAME%
      • stop-server.service.bat -mode fps -profile %PROFILE_NAME%

or

    • from Windows:Go to services.msc from Run and click Stop link on Stop the service.

Logs for the NT service run can be viewed in the file:

  • %FIORANO_HOME%/runtimedata/EnterpriseServers/%PROFILE_NAME%/service/service.log for FES.
  • %FIORANO_HOME%/runtimedata/PeerServers/%PROFILE_NAME%/service/service.log for FPS.

Once the server is installed as a service, future changes to the file 'server.conf' will have no effect on the server as the configuration files will not be regenerated. The server profile needs to be uninstalled and then installed again for the changes to be effective. Make sure you have made the entire server JVM settings before installing the profile as a service.

Uninstalling the Profiles running as NT Service

To remove the NT service, use the commands for FES and FPS respectively:

  • uninstall-fes.service.bat -profile %PROFILE_NAME%
  • uninstall-fps.service.bat -profile %PROFILE_NAME%

This removes the NT service for the given profile from the services list.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close