Free C2090-623 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

By default, an IBM Cognos Content Store deployment (export) does not include global configuration settings, such as dispatcher settings or data source configurations. This is a deliberate design choice to prevent accidental overwrites of configuration in a target environment. To create a complete backup that includes these settings within the deployment archive, the administrator must explicitly modify the Content Manager service's advanced settings on the source environment. The parameter CM.DEPLOYMENTINCLUDECONFIGURATION must be added and set to true before the export operation is initiated. This ensures the resulting deployment archive contains all necessary components for a full restoration.

A. Configuration settings are explicitly excluded from deployments by default to protect the target environment's configuration. They are not included automatically.

B. While manual restoration of configuration (e.g., from a backed-up cogstartup.xml file) is a valid recovery method, it is possible to include settings in a deployment by changing a parameter, making this statement incomplete.

D. The decision to include configuration settings must be made at the time of export, not import. The parameter affects what is written into the archive file; if the settings are not in the file, they cannot be imported.

1. IBM Cognos Business Intelligence 10.2.2 Administration and Security Guide, Chapter 15: Server Administration, Section: "Advanced settings for Content Manager".

This section details the advanced parameters for the Content Manager service. It lists CM.DEPLOYMENTINCLUDECONFIGURATION and specifies its purpose: "Specifies whether to include global configuration settings in a deployment. To include these settings, set the value to true." This confirms the parameter must be set to include the configuration. The context implies this is done on the source environment prior to export.

2. IBM Cognos Analytics 11.0.x Administration and Security Guide, Part 6: Server administration, Chapter 28: Tune server performance, Section: "Content Manager advanced settings".

This document for a later version confirms the continued existence and function of the parameter: "CM.DEPLOYMENTINCLUDECONFIGURATION: Specifies whether to include global configuration settings in a deployment... To include these settings, set the value to true." This demonstrates the consistency of this administrative concept.

The described monitoring pattern (green → yellow → red → yellow) indicates a metric whose value can both degrade and subsequently improve. This behavior is characteristic of a "gauge" metric type, which reflects a current value that can increase or decrease over time. The Dispatcher: JVM: Current heap size is a classic gauge metric. Its value rises under heavy load (potentially moving from green to red) and falls after garbage collection runs or when the load subsides (potentially moving from red back to yellow), perfectly matching the observed pattern.

B. ContentManageService: Request: Number of failed requests

This is a "counter" metric. Its value is cumulative and can only increase or stay the same during a server session; it cannot decrease to move from a red to a yellow state.

C. ReportService: Process: Number of processes high watermark

This is a "high watermark" metric. It records the maximum value reached and, like a counter, its value cannot decrease during a server session.

D. BatchReportService: Request: Percentage of successful requests

While this is also a gauge metric that can fluctuate, JVM heap size is a more fundamental system resource metric whose value inherently and rapidly changes with load and garbage collection, making it the most typical example of the described behavior.

1. IBM Cognos Analytics 11.0 Administration and Security Guide, Chapter 11: Server administration, Section: System metrics.

Page 229 (PDF version): This section explicitly defines the different metric types. It states, "The value of a gauge metric can increase or decrease over time." It also states, "The value of a counter metric increases over time," and "The value of a high watermark metric increases over time." This documentation confirms that only gauge metrics (like options A and D) can exhibit the described behavior, while counter (B) and high watermark (C) metrics cannot.

The guide lists Current heap size and Percentage of successful requests as examples of gauge metrics, and Number of failed requests as a counter. This directly supports the elimination of options B and C.

IBM Cognos recommends an “architecture review” when an installation is not performing well.

The review focuses on three performance attributes:

• IBM Cognos implementation (how services, content and security are configured)

• Capacity (current and projected workloads, hardware sizing)

• Infrastructure (network, operating system, database, storage)

These factors collectively identify configuration or resource limits that degrade performance. The other options list hardware components or generic quality attributes, but omit one or more of the specific attributes IBM states must be examined in an architecture review.

A. Omits the IBM Cognos implementation attribute expressly required by IBM; availability is not listed for the review.

B. Lists architectural components, not performance attributes; misses capacity and infrastructure considerations.

D. Mixes components (gateways, application servers) with one attribute (scalability) and omits the “IBM Cognos implementation” attribute.

1. IBM Cognos Business Intelligence V10.2.2 Architecture and Deployment Guide, section “Conduct an architecture review”, p. 214–215: “The performance attributes considered are the IBM Cognos BI implementation, capacity, and infrastructure.” (GC27-4205-00)

2. IBM Cognos Analytics 11.1 Administration and Security Guide, Chapter “Performance tuning and review”, sub-section “Architecture review”, para 2: reiterates same three attributes.

3. IBM Knowledge Center, Cognos Analytics LTS 11.0.13 > Planning and Architecture > “Reviewing system architecture” (kcdocid=kccareviewarch): lists implementation, capacity, infrastructure as performance attributes to be assessed.

The correct procedure requires a two-step process to ensure no data is lost. First, a Content Archival task must be run on the "AP" folder. This task copies the report outputs from the primary Content Store to the external archive repository, securing the data. Second, a Content Removal task is run. This task is configured with the specific retention rules—keeping run history for 12 months while removing report outputs older than 30 days from the Content Store. This sequence guarantees that all report outputs are safely archived before any are removed from the Content Store, fulfilling all requirements of the request.

A. Running a Content Removal task first would permanently delete the report outputs from the Content Store before they could be archived, resulting in data loss.

B. A Retention Rule task is a form of content maintenance that removes content. Running this before the archival task would delete the outputs, making them unavailable for archiving.

D. This option incorrectly places the Retention Rule task first, which would delete the report outputs older than 30 days, preventing them from being archived as required.

1. IBM Cognos Business Intelligence 10.2.2 Administration and Security Guide, Chapter 13: Content Store Administration, Section: "Content Maintenance Tasks". This section details the different types of maintenance tasks.

The sub-section "Creating a Content Archival Maintenance Task" describes the process of exporting content to an archive. It states, "You can create a content archival maintenance task to export content from the content store to an archive." This supports the first step in the correct answer.

The sub-section "Creating a Content Removal Maintenance Task" explains how to delete content based on retention rules, including separate settings for run histories and report output versions. This supports the second step in the correct answer, highlighting the specific controls available. The logical sequence to prevent data loss is to archive before removing.

IBM Cognos BI achieves internal load balancing by distributing processing requests across multiple dispatchers. This is accomplished by installing the Application Tier Components on several servers and configuring each dispatcher to communicate with the same Content Manager, which uses a single content store. The IBM Cognos gateway is then configured with the URIs of these dispatchers. The gateway automatically performs round-robin load balancing, forwarding incoming user requests to the available dispatchers sequentially. This distributes the workload without requiring an external load-balancing mechanism.

A. Set up a standby Content Manager.

This configuration provides high availability (failover) for the Content Manager service, not load balancing for user report processing.

B. Install a gateway on each database server.

The physical location of the gateway component does not inherently create a load-balancing configuration. Load balancing depends on the gateway's configuration to route to multiple dispatchers.

D. Configure gateways to direct all traffic to a dedicated dispatcher.

This describes a single-server configuration or a bottleneck, which is the antithesis of load balancing. It concentrates all processing on one dispatcher.

1. IBM Cognos Business Intelligence 10.2.2 Installation and Configuration Guide:

Reference: Chapter 1, "IBM Cognos BI components and architecture", Section: "Load balancing IBM Cognos BI servers".

Content: "You can install more than one dispatcher on different servers. All dispatchers can be configured to talk to one Content Manager... The gateway component can then balance requests between the available dispatchers. The IBM Cognos gateway can perform load balancing by distributing requests to the available dispatchers in a round-robin fashion."

2. IBM Cognos Business Intelligence 10.2.2 Architecture and Deployment Guide:

Reference: Chapter 6, "Deployment scenarios", Section: "Scaling the IBM Cognos BI architecture".

Content: "To scale the application tier horizontally, you install the Application Tier Components on additional servers. You then configure each of these new instances to use the same Content Manager that the first instance uses... The gateway forwards requests to the dispatchers in the environment in a round-robin fashion."

3. IBM Redbooks: IBM Cognos 10 Report Studio: Practical Examples (SG24-7922-00):

Reference: Chapter 2.2.2, "IBM Cognos 10 architecture", Page 26.

Content: "For scalability, you can have multiple dispatchers on multiple servers. The gateway distributes the requests to the dispatchers. This is a form of load balancing."

The IBM Cognos Analytics Administration console exposes only a small set of Mobile-service properties. Among them is Credential cache timeout (minutes), which governs how long cached credentials are retained on the device. Options A, C, and D are not exposed as configurable properties; they are controlled by the mobile operating system or are hard-coded limits in the application and therefore cannot be managed by the Cognos administrator.

A. Saving credentials is a user-choice (“Remember me”) handled by the device key-store; there is no server-side or administration property to enable/disable it.

C. Screen-capture behavior is governed by the mobile OS; Cognos Mobile does not provide an administrative toggle for screenshots of Active Reports.

D. The app has a fixed limit (30) for offline Active Reports that cannot be altered by administration settings.

1. IBM Cognos Analytics 11.0.13 Administration and Security Guide – “Configure IBM Cognos Mobile > Set IBM Cognos Mobile service properties”, Property list, Credential cache timeout (minutes).

2. IBM Cognos Analytics 11.0.13 Knowledge Center – “IBM Cognos Mobile limitations”, paragraph “Active Reports: A maximum of 30 reports can be stored on a device; this value is not configurable.”

3. IBM Cognos Analytics 11.0.13 Knowledge Center – “IBM Cognos Mobile security”, subsection “Remember me”; explains saving credentials is a client feature, not an administrator-controlled setting.

IBM Cognos security principals (users, groups, roles) are identified internally by a unique Cognos Access Manager ID (CAMID), not by their name. When the administrator deleted the group, its original CAMID was permanently removed from the Content Store. Recreating the group, even with the identical name, generates a new, different CAMID. Since all access permissions are mapped to the original CAMID, the newly created group is not recognized by the existing security policies. The most effective and reliable solution is to restore the Content Store from a backup created before the group was deleted. This action restores the group with its original CAMID, which correctly re-links it to all its previously defined access permissions.

A. Re-implementing all permissions is a valid but highly impractical, time-consuming, and error-prone workaround, especially in a complex environment. It is not the standard recovery procedure.

B. The “Apply to all children” option is used to propagate permissions down a content hierarchy (e.g., from a folder to its sub-folders and reports) and does not resolve the underlying issue of a changed group identifier.

C. While the spelling must be correct, the core issue is the change in the internal unique identifier (CAMID), not the group's display name. Permissions are linked to the ID, not the name.

1. IBM Support Technote 1342133: "Why do users, groups or roles lose their security after being deleted and re-added to the authentication source?". This document explicitly states: "Each security object (user, group, role) in the Content Store is assigned a unique Cognos Access Manager ID (CAMID). ... When an object is deleted and re-added, it is assigned a new CAMID. ... The recommended solution is to restore a Content Store backup from before the object was deleted."

2. IBM Cognos Analytics 11.1.x Administration and Security Guide: In the chapter on "Administration," the section "Backup and Recovery" details the procedures for creating and restoring Content Store backups. It states, "You should back up the content store regularly to prevent data loss in case of a system failure." This procedure is the official mechanism for recovering from accidental deletions of critical objects like security groups.

3. IBM Cognos Analytics 11.1.x Administration and Security Guide: The chapter on "Deployment" explains how to use exports and imports for selective recovery. An administrator could use a deployment archive (a type of backup) to selectively import directory content, which includes users, groups, and roles, to restore the deleted object with its original CAMID.

The "Fast Startup" option is a specific configuration setting within IBM Cognos designed to reduce the service startup time. When enabled, it defers the initialization of certain components, such as the report and metadata services, until they are actively requested by a user for the first time. This allows the core Cognos service to become available more quickly, directly addressing the issue of a long startup period.

A. Set load balancing to cluster compatible.

This setting concerns how user session requests are routed in a multi-server environment to maintain session affinity. It affects runtime behavior, not the initial service startup time.

C. Increase the size of the JVM heap by selecting Large configuration.

Increasing JVM heap size provides more memory for runtime operations, which can prevent "Out of Memory" errors and reduce garbage collection overhead. However, it does not directly reduce startup time and can sometimes slightly increase it.

D. Reduce the size of the Content Store through archiving and removal.

While maintaining a lean Content Store is a best practice for overall system performance, and can contribute to faster startup, it is a general maintenance task. The "Fast Startup" option is a more direct and specific solution for the stated problem.

1. IBM Cognos Analytics 11.1.x Administration and Security Guide. In the section "Configuring advanced settings for the environment," the advanced.faststartup property is described: "When you enable the fast startup option, the startup time for the IBM Cognos service is reduced. The service defers the initialization of the report and metadata services until they are requested by the first user request." (This directly supports answer B).

2. IBM Cognos Analytics 11.0.x Installation and Configuration Guide. Chapter 10: "Advanced configuration settings" details the advanced.faststartup parameter, confirming its purpose is to decrease the time required to start the IBM Cognos service. (This further validates answer B).

3. IBM Redbooks: IBM Cognos Business Intelligence V10.1 Handbook (SG24-7912-01). Chapter 16, "Performance Tuning and Monitoring," section 16.2.2, "Content store," explains that a large number of objects can degrade performance. This supports the idea that option D is a valid performance tuning step but does not position it as the primary solution for startup time compared to a dedicated feature. The same chapter also discusses JVM tuning (related to option C) and load balancing (related to option A) in the context of runtime performance, not initial startup speed.

To log the activity for a single user's report executions, the administrator must configure an advanced setting for the Report service. The specific parameter, RSVP.REPORTUSER.LOG, is designed for this purpose. By setting its value to the user's ID (e.g., CAMID), Cognos will generate a separate log file containing detailed trace information exclusively for that user's report service interactions. This targeted approach avoids the performance overhead and log clutter of enabling trace-level logging for the entire service.

A. Set the Report service logging to Trace.

This enables verbose logging for all users and activities on the Report service, not just a single user, creating excessively large and difficult-to-analyze log files.

B. Modify the ipfcogconfig.xml file in the bin64 directory.

This file is for bootstrap and global configuration settings. User-specific logging is a dynamic, service-level setting managed through the administration console, not by manually editing this core file.

C. Use the Remote Process service for Java Management Extensions (JMX).

JMX is a framework for real-time monitoring and management of application components (MBeans), not for configuring persistent, user-specific file-based activity logging.

1. IBM Cognos Analytics 11.1.x Documentation: Administration and Security Guide, Chapter 10: Server Administration, Section: "Configure advanced settings for services". This section details the process of adding service-specific parameters. The RSVP.REPORTUSER.LOG parameter is a well-documented advanced setting for the Report Service. (Note: Specific parameter names are often detailed in supplementary Technotes).

2. IBM Support Technote 1344798: "How to trace a specific user's report execution". This document explicitly instructs administrators to set the advanced parameter RSVP.REPORTUSER.LOG for the ReportService to the user's ID to enable tracing for that individual. It confirms this is the correct and intended method.

3. IBM Cognos Analytics 11.0.x Documentation: Tuning and Serviceability, Section: "Logging Configuration". This documentation distinguishes between general audit/trace logging and specific diagnostic tracing. The use of advanced parameters for targeted diagnostics, such as for a single user, is a key concept covered. The method described in option D aligns with this principle of targeted serviceability.

The error XQE-JDB-0004 A problem occurred finding the driver class indicates the Java Virtual Machine (JVM) running the Dynamic Query Mode (DQM) service could not locate the specified JDBC driver JAR file in its classpath. In a hybrid or distributed environment, database drivers are often installed on a separate gateway machine. For the main application server to use these drivers, the JDBC data source connection must be explicitly configured with the Gateway URI. If this URI is missing, the DQM service attempts to load the driver locally. Since the driver is only on the gateway, the class is not found, and the connection fails.

A. 32-bit client driver installed

This is incorrect. The error is a "class not found" exception, which relates to the classpath, not a native library loading failure where bitness (32-bit vs. 64-bit) would be relevant.

B. 64-bit client driver installed

This is incorrect for the same reason as option A. Pure Java JDBC drivers are bitness-agnostic; the issue is that the driver's JAR file cannot be found by the class loader.

D. unsupported driver version installed

This is incorrect. An unsupported driver version would typically cause an error after the class is successfully loaded, such as during connection establishment or when executing a specific function, not an error finding the class itself.

1. IBM Cognos Analytics 11.1.x Documentation, "Setting up a gateway for data source connectivity": This document states, "For dynamic query mode, if you do not specify the gateway URI, the dispatcher that is configured to use the query service attempts a type 4 connection. If the database client is not installed on the same computer as this dispatcher, the connection fails." This directly explains the scenario where a missing Gateway URI causes a connection failure because the driver is not found locally.

2. IBM Cognos Analytics 11.0.x Documentation, "Using a gateway for data source connectivity": In the section for JDBC connections, it details the requirement of specifying the gateway URI for the connection string. It clarifies that without this, the connection is attempted from the dispatcher's local environment, which would lack the necessary drivers if they are installed only on the gateway tier.

3. IBM Support Technote KB0093193, "XQE-JDB-0004 A problem occurred finding the driver class": This technote explains that the root cause of this error is the absence of the required JDBC driver .jar file in the /drivers directory on the server running the report. In a gateway configuration, failing to specify the Gateway URI causes the system to look in this local directory instead of on the remote gateway where the driver resides.

The request flow for a Dynamic Query Mode (DQM) report begins when a user request is processed and communicated between services via the BI Bus (BIBus). The request is routed to the Query Service, which is the core engine for DQM. A defining architectural feature of DQM is its sophisticated query planner. It parses the report specification to generate a logical query plan (representing the business request) and then transforms it into an optimized physical query plan (representing how to retrieve the data). This process is often described as creating "two trees." The physical plan is then executed against the database via an RDBMS adapter, with results being retrieved and cached to optimize performance before the final report is generated.

A. This is incorrect because the BI Bus is the communication infrastructure, not the query execution engine. The Query Service performs the execution, and this option omits the critical query parsing step.

B. This is incorrect as it oversimplifies the process by omitting the fundamental DQM step of parsing the request into logical and physical query plans ("two trees"), which is a key differentiator.

C. This is incorrect because the request does not originate at the Query Service. It is routed to the Query Service from other services (like the Report Service) via the BI Bus infrastructure.

1. IBM Redbooks, "IBM Cognos Dynamic Query" (SG24-8121-00)

Page 8, Section 1.2.2, "Query execution": "The query service receives an abstract representation of a query from a client such as the report service. The query service plans the query by creating a logical plan... The query service then transforms the logical plan to a physical plan that is specific to the data sources that are being queried." This text directly supports the concept of parsing the request into two plans or "trees".

Page 7, Figure 1-3, "Dynamic query mode architecture": This diagram illustrates the interaction where the Report Service sends a request to the Query Service, which then interacts with data sources. The BI Bus facilitates this inter-service communication.

2. IBM Knowledge Center, Cognos Analytics 11.1.x, "Dynamic query mode"

Section: "Query execution": The documentation states, "The query service plans and executes queries in a series of steps... The query service validates the query and analyzes it to produce a logical query plan... The query service converts the logical plan into a physical query plan." This confirms the multi-stage planning process central to DQM and represented by the "two trees" concept in the correct answer.

To make a data source available for use in web-based modeling tools like data modules, the administrator must explicitly enable this capability within the data source connection properties. The "Allow web-based modeling" option configures the connection for use with the Dynamic Query Mode (DQM) service, which is required for creating and using data modules and dashboards in the Cognos Analytics portal. Without this setting enabled, the data source will not appear in the list of available sources when a user attempts to create a new data module.

A. IBM Cognos Configuration is used for core server settings like the content store, dispatchers, and cryptography, not for managing properties of individual data source connections for specific features.

B. IBM Cognos Transformer is a separate client tool used for creating PowerCubes (OLAP models) and is not involved in configuring relational data sources for web-based modeling.

C. Access permissions are managed in the administration console, not within the modeling tool itself. Furthermore, this setting controls who can create data modules, not which data sources are available for modeling.

1. IBM Cognos Analytics 11.1.x Documentation, Managing, "Creating a data source": In the section describing the properties for a new data source connection, the documentation states for the Connection tab: "Allow web-based modeling: Select this check box to allow the data source to be used in web-based modeling tools, such as data modules."

2. IBM Cognos Analytics 11.1.x Documentation, Data Modeling, "Data sources for data modules": This section explicitly states the prerequisite: "To be used in data modules, JDBC data sources must be configured to Allow web-based modeling in their connection properties. This setting is enabled by default for new JDBC data source connections."

The Status > System page in the IBM Cognos Administration console is the central dashboard for monitoring the overall health and activity of the Cognos environment. It provides administrators with real-time and historical metrics about servers, dispatchers, and services. A key feature of this page is the "Upcoming Activities" pane, which lists all scheduled reports, jobs, and other entries that are pending execution. This allows administrators to monitor future workload and proactively identify potential impacts on system resources, aligning directly with the task described.

A. Enabling and disabling schedules is a configuration task performed on the Configuration > Scheduling page, not a monitoring function on the Status page.

C. Stopping and starting individual services is managed within the properties of a specific dispatcher, located under Configuration > Dispatchers and Services.

D. Configuring data source connections is a fundamental setup task performed on the Configuration > Data Source Connections page.

1. IBM Cognos Analytics 11.0.0: Administration and Security Guide, Chapter 12: "Administering the System", Section: "Monitor system activities". This section details the components of the Status > System page, stating: "You can view current, upcoming, and past activities... The Upcoming Activities pane shows the entries that are scheduled to run." This directly supports the correct answer (B).

2. IBM Cognos Analytics 11.0.0: Administration and Security Guide, Chapter 10: "Managing Dispatchers and Services", Section: "Start and stop dispatchers and services". This section explicitly states that starting and stopping services is performed in the Configuration tab, which refutes option (C).

3. IBM Cognos Analytics 11.0.0: Administration and Security Guide, Chapter 7: "Data Sources", Section: "Create a data source". This chapter details the process of configuring data source connections, which is done under the Configuration tab, refuting option (D).

4. IBM Cognos Analytics 11.0.0: Administration and Security Guide, Chapter 9: "Scheduling", Section: "Manage schedules". This section describes how to create, disable, or enable schedules from the Configuration tab, refuting option (A).

A Benchmark task in IBM Cognos LifeCycle Manager is designed to create a baseline by capturing the output and performance metrics of reports from a source environment in their current state. The option to force reports to run in Dynamic Query Mode (DQM) is a specific setting within a Comparison task, not a Benchmark task. This allows a user to compare the output of reports running in DQM on a target server against the established benchmark, which typically represents the original Compatible Query Mode (CQM) output from the source server. Therefore, the ability to choose DQM execution is not a feature available during the creation of a Benchmark task itself.

A. A benchmark creates a reusable baseline. This baseline can indeed be selected as the source for comparison tasks in any LifeCycle Manager project.

B. This describes a primary use case for LifeCycle Manager: establishing a CQM benchmark to validate the output and performance after migrating reports to DQM.

D. This accurately describes the process of setting up a Comparison task, where a pre-existing Benchmark task is selected as the source for comparison against a target server.

1. IBM Cognos LifeCycle Manager 10.2.2 User Guide, Chapter 4: Working with tasks, Section: "Creating a comparison task", p. 25. This section details the properties for a comparison task and explicitly lists the "Run reports in dynamic query mode" checkbox as an available option. The corresponding section, "Creating a benchmark task" (p. 23), does not include this option.

2. IBM Documentation for IBM Cognos Analytics 11.1.7, Section: Managing > Validating and comparing report outputs > Creating a comparison task. The documentation states, "To run the reports in dynamic query mode, select the Run reports in dynamic query mode check box." This option is documented exclusively for comparison tasks.

3. IBM Documentation for IBM Cognos Analytics 11.1.7, Section: Managing > Validating and comparing report outputs > Creating a benchmark task. This document outlines the steps and properties for creating a benchmark task. The option to run reports in Dynamic Query Mode is notably absent from the available settings, confirming it is not a feature of this task type.

The Content Manager is the central service in the IBM Cognos architecture responsible for managing the content store database. This database is the primary repository for all application data, which includes report specifications, published models, scheduling information, security settings (such as users, groups, and roles), configuration data, and saved report outputs. It handles requests to retrieve, store, and manage these assets, ensuring the integrity and security of the Cognos environment.

A. Gateway: The Gateway is a web server extension that acts as the entry point for user requests, passing them to a dispatcher for processing. It does not store application data.

B. Dispatcher: The Dispatcher routes requests to the appropriate Cognos service (e.g., Report Service, Presentation Service) and manages the distribution of workload. It does not store persistent application data.

D. Presentation service: The Presentation service is responsible for rendering report specifications into viewable formats like HTML, PDF, or Excel. It processes data but does not store the core metadata or configuration.

1. IBM Cognos Business Intelligence 10.2.2 Architecture and Deployment Guide:

Page 14, "Content Manager": "Content Manager is the IBM Cognos BI service that manages the storage of customer application data, including security, configuration data, models, metrics, report specifications, and report output. Content Manager is needed to publish packages, retrieve or store report specifications, manage scheduling information, and manage the Cognos namespace."

Page 15, "Gateway": "The IBM Cognos gateway is the entry point for IBM Cognos BI requests."

2. IBM Knowledge Center, Cognos Analytics 11.1.x, Components of IBM Cognos Analytics:

Section: "Content Manager": "Content Manager is the IBM Cognos Analytics service that manages the storage of customer application data, including security, configuration data, models, metrics, report specifications, and report output." This confirms the role's consistency from Cognos 10 BI to Cognos Analytics.

Section: "Dispatcher": "A dispatcher runs the IBM Cognos service, which includes the Presentation Service, Batch Report Service, and Report Service." This shows the dispatcher as a host for services, not a data store.