CCTS Deployment Architecture
From CTMS_WIKI
Contents |
Introduction
Background
The caBIG Clinical Trials Suite (CCTS) is an enterprise clinical trials system being designed primarily for use in trial sites. The suite is comprised of a collection of interoperable modules covering a broad range of key areas in cancer clinical trials management. These include patient registration via C3PR, patient scheduling via PSC, adverse events reporting via caAERS, lab analysis via LabViewer, and clinical data management via C3D. Integration between these applications is centered around five key scenarios: Study Creation, Register Subject, Load Labs in CDMS, Lab-driven AE Creation, and AE-Triggered Schedule Change. The implementation is based upon the caGrid infrastructure with caXchange as the Enterprise Service Bus for reliable message routing and GAARDS providing robust security.
Scope
This document is a work in progress used strictly for planning for the CCTS 2.0 release. Up until that release, it could be altered in any way.
Related Documentation
Requirements
| Req. ID | Requirement Description |
| CCTS-DEPLOY-001 | Wherever possible, virtual machines should be allowed in place of hardware |
| CCTS-DEPLOY-002 | In the interest of a separation of concerns, separate machines should be allocated for grid, database, and applications |
| CCTS-DEPLOY-003 | The deployment should utilize a minimum number of machines and containers while still meeting other requirements |
| CCTS-DEPLOY-004 | Each grid component (Dorian, GTS, CDS, etc.) should be deployed as a separate user |
| CCTS-DEPLOY-005 | Dorian may be deployed on real hardware, not on a virtual machine |
| CCTS-DEPLOY-006 | Applications must be deployable to the same container |
| CCTS-DEPLOY-007 | Applications should be deployed to the same container |
| CCTS-DEPLOY-008 | caXchange should be deployed to a different container than the applications |
Architecture
CCTS has a number of deployment recommendations that are discussed in the Installation Guide. The following production deployment view provides for a separatation of security, application, and other grid functionality.
