...
Figure 1 illustrates how different entities of the platform interact with each other in carrying out their respective functionalities.
Figure 1: The Fiorano System Architecture
- The Fiorano Peer Server Network is the Enterprise Class, centrally managed Peer-to-Peer messaging backbone.
- The Fiorano ESB Server is the Administration Gateway to the ESB Peer Server network.
- The Fiorano Service components are either the interfaces to units of the Enterprise IT Infrastructure or implementations of commonly used integration elements (such as transformations, content based routers, and so on). The Fiorano Service components implemented in Java are either pure JMS or JCA components. Custom service components can be built in C#,
- The Fiorano Tools Interface is provided via the Fiorano eStudio which offers intuitive visual interfaces for the implementation of ESB Server capabilities for end Users.
...
The exact topology architecture for each solution varies and is determined based on specific customer requirements. All Servers on the Same Machine
Typical Development Topology
Fiorano Platform installation (Enterprise Edition) can be installed on a single machine. The default Peer Server profile is configured to work with the Enterprise Server available on the local machine. As such, no further configuration (other than JVM settings, like setting the heap size) is needed to launch the Servers. The Fiorano eStudio also comes pre-configured with the local Machine Enterprise Server connectivity information.
A single machine installation is the simple and fast way to get acquainted with the software. If the 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 Typical Production/Testing Topology
Typical production or a testing environment topology of Fiorano Servers has all the servers configured in High Availability mode on different machines. There can be multiple peers in HA mode which are distributed across other machines. The machines can be in the same network or in cloud provided the latencies are manageable. With this approach it is possible to distribute the load across multiple mid-range machines as compared to using a single high-end machine.
For example, the Figure 2 illustrates an installation topology spread across five multiple machines.
Figure 2: Installation Topology
ESB Server
The Enterprise Server is the centralized management and repository Server which manages the various components of the Fiorano Network.
System Requirements
The ESB Server is a 100% Java product and can be deployed on any platform with a JRE version 1.5 or above. For optimum performance, a minimum of 1 GB RAM is recommended. A complete Enterprise Edition installation requires 600 MB of disk space.
Installation Steps
The windows installer is wizard driven on which the default installation directory can be configured. The non-windows installer includes a wizard driven approach or a tar file that can be easily unzipped into a directory and then untarred.
Solaris Platform installation instructions:
- Use gtar in Solaris to untar
- GNU tar is bundled as: /usr/sfw/bin/gtar
Check the link below for further information: http://forum.java.sun.com/thread.jspa?threadID=5106899&messageID=9363883
ESB Peers
The ESB Peer Server is a runtime container for service components. The Peers communicate with each other directly in a Peer-to-Peer method without going through the Enterprise Server.
System Requirements
The Peer Server is a 100% Java product and can be deployed on any platform with a JRE 1.7 version. For optimum performance a minimum of 1 GB RAM or above is recommended.
The actual RAM and the hard disk space required for deployment depends on the number of Business Services running on a single node, complexity of the Business Services deployed on a single node, CPU requirements by the Business Services, anticipated data flow, expected performance from the system, and so on.
Installation Steps
The Windows installer is wizard driven on which the default installation directory can be configured. The non-windows installer includes a wizard driven approach or a tar file that can be easily unzipped into a directory and then untarred.
Solaris Platform installation instruction:
- Use gtar in Solaris to untar
- GNU tar is bundled as: /usr/sfw/bin/gtar