Difference between revisions of "Virtual Layer"
G.iannello (talk | contribs) m |
G.iannello (talk | contribs) m |
||
| (One intermediate revision 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 | * Makes no use of any proprietary mechanisms of any Application Server | ||
| Line 8: | Line 8: | ||
* The business analyst can create the business flows through the Graphical Editor Console [[VulCon]] | * 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]] | * The technical specialist implements the flow through the configuration console [[GV Console]] | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | |||
| + | [[File:GVExamplesTOUPPER4.jpg]] | ||
Latest revision as of 11: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
