Fusion Architecture: Layers and Extensibility

Fusion is designed in such a way as to allow easy extension of the system, either by Javelin or by external partners. Adding components, rather than modification of the core system, allows new protocols, standards and formats to be easily added to the system. 

This is achieved through an extensible layer based architecture.

Fusion architecture

The Fusion Architectural layers are:

Event Monitor Interface

Transformation / Action Layer 

Data Source Layer 

Transport Layer

Physical Data Layer

The Physical Data Layer is the actual physical representation of the data - as a text file, EDI file or SQL data base for example. A Fusion data source knows how to interpret this data once it has retrieved it via a particular transport.

Fusion has been designed from the ground up to have a scalable, secure, distributable and extensible architecture. 

Scalable, in that Fusion may contain any number interacting hosts. To increase processing power the customer need only supply a new machine and assign workflows to the Fusion Host installed on that machine. 

Secure, in that all communications between Fusion components may be secured with SSL, and where the customer does not want direct, unsecured data access (for example JDBC over the network to the Oracle listener port) they may put another Fusion host onto the database machine itself and use secure SSL instead. 

Distributable, in that Fusion Hosts and Consoles may be distributable over multiple machines and operating systems, communicating via the Host Messaging System, and even using each other to relay or proxy messages and data. 

Extensible, in that Fusion provides many layers for internal and partner extension of the system. These layers allow Fusion to easily support new transport protocols, data sources, workflow actions and event monitoring protocols, by adding components rather than modifying the core system.