High Level Architecture
- Overview
The diagram above shows a high level view of the architecture used in CW. The typical interaction of the various components on the various tiers is described below: - Tier 1 — Web Client
HTML (with JavaScript) is sent to the web browser. Optionally, a file upload applet is used to facilitate support of the various editors. There is more information on this applet in other sections of this document. - Tier 2 — Web Server/APIs
- Tier 3 – Contenta Server/database server
The API communicates with the Contenta Server, which in turn communicates with the database server. - Security
- Session management and scalability
- CW Web Application Directory Structure
CW is composed of several different web applications. The directory structure for the CW web applications follows the J2EE standard for web application directory: - CW Logging
CW and CW tools use a common error handling/logging mechanism. The debug level is set by checking for a flag in the registry under a setting calledappid_debugLevel(e.g.cw_debugLevel,cw_di_debugLevel...). By default the debug level is set to 0. CWAssignlistview.jsp and CW.jsp have examples of how the error handling should be done. - CW and Contenta API Memory Management
CW is a cross-platform application that runs on both Windows and UNIX and uses the Contenta API. On Windows, the Contenta API is COM-based. For Java applications (e.g. CW), the following guidelines must be followed: - CW and multithreading
CW is a multi-threaded Java application that shares a single connection to a Contenta Server. The Contenta Server has state, that is, it maintains focus on the currently selected object. Therefore, CW must synchronize access to the server to ensure the correct focus. CW synchronizes Contenta Server access via the PCMSync class. - CW Tool Support
This section highlights the tool support in Contenta Web. - Tool Notes