Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This section explains the high-level system architecture of the Fiorano Enterprise Services Grid, which consists of Peer Service Containers installed across the network together with the centralized Management and Repository Server as well as Management tools. The topics discussed in this chapter include the ESB Server, ESB peers, the Web Gateway that manages Web Services and Fiorano Orchestration and Management tools.

Fiorano System Architecture

...

  1. Fiorano Peer Server Network
  2. Fiorano ESB Enterprise Server
  3. Fiorano Service Components
  4. Fiorano Tools Interface

Figure 1 illustrates how different entities of the platform interact with each other in carrying out their respective functionalities.

Image Modified
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 mostly in Java are either pure JMS or JCA components. Custom service components can be built in Java, C#,  C or 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.

...

ESB Server

...

The Fiorano ESB Server is the central controller of the Fiorano network. This control server acts as a monitoring agent for all other peers and ensures information coherence.
The various functions performed by the FES include:

  1. Control of launching as well as termination of Fiorano Components as part of an event process on any Peer of a Fiorano network.
  2. The update of status of all Peer Servers, Business Components and Event Processes running on Peers across the network.
  3. The Launch of a Business Component on a backup node, in case the primary FPS on which the Business Component is running goes down.

Fiorano Peer Server

The Fiorano Peer is a container for launching business components at network end-points of a Fiorano network and manages the life cycle of the components. The following are key functionalities of the Fiorano Peer:

...

to Peer

...

Server

...

ESB Server to Peer Server communication

All data communication at runtime in the ESB network happens in direct Peer to Peer fashion among Peer Servers. Only control data flows between the Enterprise and the Peers. The types of control events handed by the ESB Server include service component state notifications, event process state notifications, HA events, document tracking events and so on.

ESB Component and Process Repository

The ESB Server manages the following repositories:

  • The repository to maintain versions of registered and unregistered service components along with dependent resources and binaries.
  • The Meta data information of the event processes in XML format.
  • The repository of Peers in the ESB network and their configuration

Installation

The Fiorano Platform is available in two editions:

  1. Enterprise Edition: The Enterprise Edition includes the Fiorano Enterprise Server, Fiorano Peer Server, Fiorano Adapters, and all the Fiorano tools.
  2. Workstation Edition: The Workstation Edition includes the Fiorano Peer Server and all the Fiorano tools. The Workstation Edition is not bundled with the Enterprise Server. This edition requires an Enterprise edition to be installed on the Fiorano Network.

The Enterprise and Workstation Edition are available free for a 45-day evaluation period. The evaluation versions contain all the features of the licensed versions. The use of this software is defined in the Fiorano End-User License Agreement.

Different Topologies

The Fiorano Peer-to-Peer distributed model provides unmatched flexibility in deciding installation topology. Users can decide on an installation topology based on various parameters:

...

Adaptavist ThemeBuilder EngineAtlassian Confluence