Difference between revisions of "Virtual Layer"

From GreenVulcano Wiki
Jump to: navigation, search
(Created page with "It's the innovative and technological layer that provides to the entire platform the independence from any specific J2EE application server: - Makes no use of any proprietary...")
 
m
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
It's the innovative and technological layer that provides to the entire platform the independence from any specific J2EE application server:
+
It's the innovative and technological {{GVESB}} layer that provides to the entire platform the independence from any specific J2EE application server
    - Makes no use of any proprietary mechanisms of any Application Server
 
    - Performs ''virtual'' operations (such as dequeue, enqueue, forward and call) implemented by the core layer
 
    - Uses standard mechanisms for internal communication among components
 
  
Morover it separates the business analysis from the technical implementation and configuration
+
* Makes no use of any proprietary mechanisms of any Application Server
    - The business analyst can create the business flows through the Graphical Editor Console VulCon
+
* Performs ''virtual'' operations (such as dequeue, enqueue, forward and call) implemented by the [[Core]] layer
    - The technical specialist implements the flow through the configuration console GV Console
+
* Uses standard mechanisms for internal communication among components
 +
 
 +
Morever it separates the business analysis from the technical implementation and configuration
 +
* The business analyst can create the business flows through the Graphical Editor Console [[VulCon]]
 +
* The technical specialist implements the flow through the configuration console [[GV Console]]
 +
 
 +
 
 +
----
 +
 
 +
 
 +
[[File:GVExamplesTOUPPER4.jpg]]

Latest revision as of 13:58, 8 February 2012

It's the innovative and technological GreenVulcano® ESB layer that provides to the entire platform the independence from any specific J2EE application server

  • Makes no use of any proprietary mechanisms of any Application Server
  • Performs virtual operations (such as dequeue, enqueue, forward and call) implemented by the Core layer
  • Uses standard mechanisms for internal communication among components

Morever it separates the business analysis from the technical implementation and configuration

  • The business analyst can create the business flows through the Graphical Editor Console VulCon
  • The technical specialist implements the flow through the configuration console GV Console




GVExamplesTOUPPER4.jpg