|
|
Release: 2.6.2 Previous Releases
Publish Date: July, 2008 |
rate-13500852-86182
| Article Rating? |
|
|
|
Typical Implementation Plan |
|
| Phase |
Pre-Requisites |
Typical Activities |
| Pre-Implementation |
Access to Application Architects, Developers (Typically no more than 1-2 business days) and Development Environment (stand-alone environment if possible) |
Application Architecture Discovery; Terracotta Training and Community/ Direct Support Resources; Terracotta (and Eclipse plugin) Installation on Dev Sand box. |
| Implementation |
Access to Application Architects, Developers (Typically no more than 2-4 business days) and Development Environment (stand-alone environment if possible) |
Functional Completion - Iterating over tc-config.xml; Operational Planning (Capacity, Failure analysis and Deployment Architecture (Servers, Disk Size, Disk Technology)); Provisioning of QA , Stage and Production Environments. |
| Quality Assurance |
Access to Dev/QA Engineers (Typically no more than occasional access over 2-4 business days) and QA/ Stage(Stress) Environments, Application Stress Scripts and Capacity Goals. |
Execute Functional and Stress Scripts (multiple runs); If needed - Iterate over tc-config.xml, any needed application refactoring, GC-tuning. |
| Production Deployment |
Access to Dev/Operational Engineers; Access to Production Environment (in case of trouble shooting needs) |
Application Deployment; Monitoring Scripts, Escalation and Recovery Processes |
|
|
|
