Cotrix configuration and deployment scenarios
From D4Science Wiki
TODO, include also the scenario's for local publication channels and external publication channels.
Deployment scenarios for 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. |
GWT, VocBench, Cotrix and Vox
Option | VocBench gwt client | VocBench services | Cotrix gwt client | Cotrix services | Vox gwt client | Vox services |
1 | war + jar | jar | war + jar | jar | jar | jar |
2 | jar | jar | jar | jar | war | NA |
3 | war | NA | war | NA | jar | jar |
In GWT you can choose to develop a client or an application. In order to make a an application for VocBench or Cotrix, you alway need at a certain point a GWT application, e.g. a war file. The GWT application will be written in Java and generated in JavaScript.
The services which are needed by the client are Java and will not be generated in JavaScipt. The services can be native GWT services or REST services.
Cotrix standalone and in the iMarine infrastructure
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. | ||
|
|
|
||||
|
|
|
|
|
|
|