The FioranoMQ Server implements a componentized model for various internal modules. Components can be clubbed together to form a deployment profile. Each deployment profile can be separately configured both in offline and online mode.
The FioranoMQ Server comprises of a number of components that implement functions independently.
A component:
-
Has a well-defined interface through which its life-cycle is controlled.
-
Is associated with a unique profile configuration object that defines its configuration needs.
-
Can expose configuration attributes and/or operations to the external world via JMX.
-
Defines dependencies upon other components.
A component is not a standalone executable application but can be hosted only within a Container.
A container:
-
Is an executable Java program.
-
Requires a list of components as input.
-
Resolves component dependencies by launching components in the correct order.
-
Provides access to a component's configuration upon its launch.
-
Encapsulates a JMX MBean Server to which all deployed components are bound.
Allows the invocation of operations and displays the change in exposed configuration parameters of a component
