This document describes the architecture and server sizing for IBM Cognos Controller 8.5.
This guideline was written by an IBM Cognos Support analyst to give an overview of the technical architecture of the Controller system and to describe best practices on server sizing for IBM Cognos Controller 8.5, based on feedback to IBM Cognos Support. It applies to Controller 8.5 and states that the official product documentation, such as the architecture and deployment guide (ctrl_arch.pdf), takes precedence over this document.
The document describes the three main architecture components - Gateway, Web Services Server and Report Server - and the path a typical report request takes through them. It then covers the benefits and drawbacks of a multi-server design, virtual platforms and 64-bit operating systems, software requirements, database storage sizing, hardware recommendations for individual boxes, multi-server configurations for different numbers of concurrent users, optional features such as Data Marts and Financial Analytics Publisher (FAP), and real-life customer examples.
| Main architecture components | Gateway, Web Services Server, Report Server |
|---|---|
| Web Services Server | Main COM+ system |
| Report Server | Cognos 8 BI reporting engine |
| Example four-server virtual deployment | One CPU and 1 GB RAM allocated per server |
The request goes to the gateway, which forwards it to the Controller Web Services Server. If a gateway is not part of the installation, the request is sent directly to the Web Services Server.
It gives an overview of the technical architecture of the Controller system and describes best practices on server sizing for IBM Cognos Controller 8.5, based on customer feedback.
No. The document warns against using underpowered servers and gives the example of four VMware servers with only 1 CPU and 1 GB RAM each, which offered no more performance than a single server with 4 cores and 4 GB RAM.
The official documentation that comes with the product, for example ctrl_arch.pdf, the architecture and deployment guide, takes precedence over this guideline.