Our architecture has been designed around four components that provide a robust reporting infrastructure.
The four main components of the Captell solution are the Workbench, Service, Web and MS SQL Server. They are present in each version of Captell (CMC and Enterprise).
The Captell workbench is used to build and maintain Captell report objects (Tables, Charts, Documents etc.). The Captell Workbench is installed on the workstation of each user responsible for maintaining the reporting system.
Provides background scheduled updates to the Captell database including loading new data and building reports from document templates. The Captell Service is installed on the same hardware as the Captell database.
Captell utilises Microsoft Internet Information System (IIS) to support its web services. The Captell web components can be installed on any platform running IIS and present the reports found in the Captell database to web users.
MS SQL Server
Captell utilises the Microsoft’s SQL Server™ database. SQL Server may be installed locally on the Captell users desktop or on a windows server platform. Either SQL Server Standard, Enterprise or the included SQL Server Express edition may be used.
In a typical installation Captell will process vast amounts of data, for this reason we prefer to have all components installed on the one hardware platform. On the “Captell Server” an installation of the Captell workbench is required along with a single instance of SQL Server and SQL Server reporting Services with 3 databases (Production, Test and Development). The Captell Service, Captell web and Report Portal components should also be installed on the Captell Server.
On each users workstation a copy of the Captell workbench is required, alternatively users can connect to the server via MSTSC (or similar) and use the workbench installed there.
To cater for change control in the reporting environment 3 separate database are created within the same SQL Server instance. This allows for access to production data from both the development and test environments without duplication.
Installation and Configuration
The Captell system is installed using a purpose built Captell utility or standard windows installation packages. The Captell databases are created using utilities built into the Captell Administrator. Some minor manual configuration changes to Captell are required before use.
Justification for single server installation
Our preference for a single server installation for ALL Captell components is based on three factors:
- Generally Captell performs better in a single server installation. Captell processes vast amounts of data requiring to pass that data between the Captell database service and in some cases SQL Server Reporting Services. Having all components running on a single platform eliminates network latency and maximises caching benefits.
- Several components of the Captell system require changes to SQL Server and SQL Server Reporting Services. The Captell function pack provides sophisticated statistical functions to SQL Server, this is provided as a DLL and must be installed into the SQL Server environment. The Captell Report portal currently supports presentation of SQL Server Reporting Services reports and Captell documents, a future release will provide additional functionality to allow Captell charts to be presented within SQL Server Reporting Services reports. To affect this it will be necessary to install components directly into the SQL Server Reporting Services installation folders. These changes should not be made where SQL Server or SQL Server reporting services are in a shared or farm environment.
- Installation is generally easier. When all components are installed on a single platform the installation process is generally easier and quicker.