Difference between revisions of "Cotrix configuration and deployment scenarios"

From D4Science Wiki
Jump to: navigation, search
(Cotrix standalone and in the iMarine infrastructure)
Line 29: Line 29:
  
  
=Cotrix standalone and in the iMarine infrastructure=
 
 
{| border="1" cellpadding="1" cellspacing="1"
 
{| border="1" cellpadding="1" cellspacing="1"
 
|-
 
|-
 
| '''Scenario'''  
 
| '''Scenario'''  
 
|  
 
|  
'''Fronted'''
+
'''iMarine front-end'''
 
+
'''gwt portlet'''  
+
  
 
|  
 
|  
'''Frontend '''
+
'''standalone front-end'''
 
+
'''plain gwt'''  
+
  
 
|  
 
|  

Revision as of 15:02, 27 September 2012

CodelistManager


TODO, include also the scenario's for local publication channels and external publication channels.

Cotrix and VocBench

Scenario Cotrix VocBench Description
1 * The instance contains only VocBench functionality
2 * The instance contains only Cotrix functionality
3 * * The instance has all the VocBench and all the Cotrix functions. 


Scenario

iMarine front-end

standalone front-end

Backend:

proprietary persistence (embedded/external)

Backend:

iMarine persistence layer

iMarine virtual platform Description
1 * * No iMarine integration here
2 * * Cotrix fronted can be anywhere, using iMarine persistence services. Cotrix is a iMarine client.
3
* * * Cotrix is deployed in the iMarine virtual platform, bringing its own persistence services. 
4
* * * Cotrix is deployed in the iMarine virtual platform, using iMarine persistence services. 
5 * * Cotrix frontend is a gCube portlet, using Cotrix persistence solutions. Is this possible?
6 *
* Cotrix frontend is a gCube portlet, using iMarine persistence services.