IBM Cognos v12 Admin key terms

The relational database that holds Cognos Analytics metadata such as reports, folders, security entries, and schedules, but not the report output or the source data itself.

The Cognos Analytics service that reads and writes metadata in the content store, coordinates locking, and serves metadata requests to other components such as the dispatcher.

The routing component that receives incoming requests, authenticates them, and forwards work to the appropriate application services running on servers in the same dispatcher group.

The layer of Cognos Analytics that runs the Java-based services, including Content Manager, dispatcher, report and batch services, and the gateways that accept client requests.

A lightweight web server component, such as IBM HTTP Server or Apache, that forwards client requests to a dispatcher URI and can be configured for load balancing across multiple dispatchers.

Configuration files generated during installation that record the content store connection, cryptographic keys, and dispatcher URIs needed to start the Cognos Analytics services.

Encryption material stored in the content store and bootstrap files that protects stored credentials and sensitive metadata; losing or mismatching keys can make encrypted values unreadable.

A database-level export of the content store schema and data taken with native database tools, used for recovery and required before upgrades or significant configuration changes.

A packaged archive of Cognos Analytics content, such as folders, reports, and data source references, that can be exported from one environment and imported into another.

The process of selecting content and options, such as references and access permissions, and writing them to a deployment archive for transfer to another environment.

The process of loading a deployment archive into a target environment, choosing conflict resolution and whether to preserve or overwrite existing entries and permissions.

The controlled movement of content and configuration through stages such as development, test, and production, typically using deployment archives and documented change procedures.

A copy of the configuration directory, including bootstrap files and service settings, taken before changes so that a working state can be restored quickly.

The file system location holding Cognos Analytics configuration files, logs, and bootstrap information for an installation, referenced by environment variables during startup.

The root directory where Cognos Analytics binaries and shared files are installed, distinct from the configuration directory that stores instance-specific settings and logs.

An unattended installation driven by a response file that supplies installation options, useful for repeatable builds and for deploying identical software across multiple servers.

A text file containing installation parameters and selections that the installer reads in silent mode, replacing interactive prompts and enabling scripted deployments.

A cumulative update applied to an existing Cognos Analytics installation to correct defects; it must be applied consistently across all servers in the environment.

The process of moving an existing installation and its content store to a newer release, including backing up, installing new binaries, and upgrading the content store schema.

The requirement that all Cognos Analytics servers in an environment run the same release and fix pack level so that services interoperate and metadata remains compatible.

A configured authentication source, such as LDAP or Active Directory, that Cognos Analytics queries to authenticate users and retrieve groups and attributes for authorization.

The external system or service that verifies user credentials during sign-in, configured as a namespace and optionally integrated with single sign-on or trusted credentials.

The built-in Cognos Analytics namespace that stores its own users and groups in the content store, often used for administrative accounts independent of external directories.

An authentication arrangement in which a user signs in once to an identity provider and is then recognized by Cognos Analytics without entering credentials again.

A configuration that allows an external application or gateway to pass an authenticated user identity to Cognos Analytics, which then trusts that assertion instead of prompting for sign-in.

A predefined set of permissions in Cognos Analytics, such as Server Administrator or Report Author, that grants a standard combination of capabilities to members.

A granular feature or action, such as creating a schedule or using a specific studio, that can be granted or denied to users, groups, and roles.

An authorization setting on a securable object, such as a folder or report, that controls whether a user or group can read, write, execute, or traverse it.

The effective right a user has to view or modify a specific object after inherited and explicit permissions from groups and roles have been combined.

A saved definition of how Cognos Analytics reaches a database, including the connection string, sign-on credentials, and driver, used by queries and reports.

A stored set of credentials, or a reference to external credentials, that Cognos Analytics uses when connecting to a data source on behalf of users.

A protected repository, either internal to Cognos Analytics or an external facility, where sign-on credentials for data sources and other services are stored encrypted.

A query execution mode that generates queries in the native language of the data source, enabling in-database processing and improved performance for supported sources.

The Cognos Analytics service that plans and executes queries against data sources, manages connection pooling, and returns results to reporting components.

The service that runs report specifications, coordinates with the query service for data retrieval, and renders output in the requested format for users or schedules.

A service dedicated to running reports and jobs in the background, typically used by schedules and burst deliveries so interactive users are not affected.

A stored definition that triggers a report, job, or delivery at specified times or intervals, with options for recipients, formats, and output destinations.

A container that groups multiple steps, such as reports, imports, or other tasks, and runs them in sequence under a single schedule and set of options.

A single report run whose output is split into separate deliveries per recipient or group, using a burst key to select the relevant data for each recipient.

A named collection of recipients, often email addresses, used as a delivery target for schedules and bursts instead of specifying recipients individually each time.

The temporary storage of query results, report output, or metadata so repeated requests can be served faster without re-querying the data source.

The practice of adjusting server resources, service settings, query behavior, and caching to meet response-time and throughput targets for users.

The ongoing observation of system health and activity, including service status, request throughput, queue lengths, and error rates, used to detect and diagnose problems.

The recording of component activity and errors to log files at configurable levels, providing evidence for troubleshooting and for confirming that settings behave as intended.

A record of user and system actions, such as sign-ins, report runs, and administrative changes, used for compliance review and investigation.

The collection of logs, configuration details, and environment information assembled for IBM support when an issue cannot be resolved locally.

A logical grouping of dispatchers that share the same services and content store, allowing requests to be balanced and services to be distributed across servers.

The distribution of incoming requests across multiple dispatchers or servers so that no single component is overwhelmed and availability is maintained.

A server placed in front of Cognos Analytics that forwards client requests to backend dispatchers, often terminating TLS and hiding internal topology from users.

The component interface through which clients and services read and modify content store metadata, including objects, properties, and security entries.

The rules that determine which users may use a data source connection and which credentials are applied, preventing unauthorized access to underlying databases.

The database-specific software library that Cognos Analytics loads to communicate with a data source, and whose version must match the supported database release.