Difference between revisions of "Cotrix configuration and deployment scenarios"

From D4Science Wiki
Jump to: navigation, search
(→‎Cotrix standalone and in the iMarine infrastructure)
(→‎Cotrix standalone and in the iMarine infrastructure)
Line 25: Line 25:
  
 
=Cotrix standalone and in the iMarine infrastructure=
 
=Cotrix standalone and in the iMarine infrastructure=
−
 
 
{| border="1" cellpadding="1" cellspacing="1"
 
{| border="1" cellpadding="1" cellspacing="1"
 
|-
 
|-
Line 58: Line 57:
 
|  
 
|  
 
|  
 
|  
−
|  
+
| No iMarine integration here
 
|-
 
|-
 
| 2  
 
| 2  
Line 66: Line 65:
 
| *  
 
| *  
 
|  
 
|  
−
|  
+
| Cotrix fronted can be anywhere, using iMarine persistence services. Cotrix is a iMarine client.
 
|-
 
|-
−
| 3
+
| 3  
−
| *
+
| <br>
−
|
+
| *
−
|
+
−
|  
+
 
| *  
 
| *  
 
|  
 
|  
 +
| *
 +
| Cotrix is deployed in the iMarine virtual platform, bringing its own persistence services.&nbsp;
 
|-
 
|-
 
| 4  
 
| 4  
 +
| <br>
 +
| *
 
|  
 
|  
 
| *  
 
| *  
 
| *  
 
| *  
 +
| Cotrix is deployed in the iMarine virtual platform, using iMarine persistence services.&nbsp;
 +
|-
 +
| 5
 
|  
 
|  
 +
| *
 +
| *
 
|  
 
|  
 
|  
 
|  
 +
| Cotrix frontend is a gCube portlet, using Cotrix persistence solutions. Is this possible?
 
|-
 
|-
−
| 5
+
| 6
 
|  
 
|  
 
| *  
 
| *  
−
|  
+
| <br>
 
|  
 
|  
 
| *  
 
| *  
 +
| Cotrix frontend is a gCube portlet, using iMarine persistence services.
 +
|-
 +
| <br>
 +
|
 +
| <br>
 +
|
 +
|
 +
| <br>
 
|  
 
|  
 
|-
 
|-
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
 
| <br>
 
| <br>
 
|}
 
|}

Revision as of 10:55, 27 September 2012

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. 


Cotrix standalone and in the iMarine infrastructure

Scenario

Fronted

gwt portlet

Frontend 

plain gwt

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.










Retrieved from "https://wiki.d4science.org/index.php?title=Cotrix_configuration_and_deployment_scenarios&oldid=6847"