IBM Cognos v12 Admin study plan
IBM Cognos v12 Admin · Give each week a clear focus.
8 weeks · About 6 hours per week
Installation, Upgrade, and Deployment Planning
Map the full Cognos Analytics v12 install topology (gateway, dispatcher, content manager, application tier) and list which component runs on which host for a two-server and a single-server scenario
Enumerate the prerequisite checks performed before installation (supported OS and database versions, Java runtime, ports, disk and memory sizing) and write them as a pre-install checklist you can reuse
Compare silent versus interactive installation and identify the response file parameters that must be set for an unattended install
Describe the difference between a full installation, an application-tier-only install, and adding a component to an existing install, and state when each is appropriate
Your checkpoint
A one-page pre-install and topology checklist covering prerequisites, component-to-host mapping, and silent install parameters, verified against your own lab notes
Installation, Upgrade, and Deployment Planning
Sequence the upgrade path from an earlier Cognos version to v12, including content store export, schema upgrade, and post-upgrade validation steps in the correct order
Identify what must be backed up before an upgrade (content store, configuration files, customizations, security provider settings) and how to restore each
Plan a deployment from development to test to production, listing which artifacts move (reports, packages, data source connections, schedules) and which are environment-specific
Distinguish deployment export/import from content store copy and explain when each is the right tool
Your checkpoint
A written upgrade and deployment runbook with ordered steps, rollback points, and a list of environment-specific settings that must be re-applied per environment
Architecture, Components, and Server Topology
Draw the request flow from browser through the gateway to the dispatcher and content manager, labeling each hop and the protocol used
Explain the role of the content store database versus the notification and logging databases, and state what breaks if each is unavailable
Describe dispatcher and service tuning knobs (processing capacity, queue behavior, report service settings) and when to add a dispatcher versus increase capacity
Plan a topology for high availability, identifying single points of failure and how to remove each
Your checkpoint
An annotated architecture diagram of a multi-server, high-availability deployment with request flow arrows and a table of failure points and mitigations
Security, Authentication, and Authorization
Configure an external authentication namespace end to end and verify that a test user can sign in with the expected group membership
Explain the difference between authentication namespaces and the Cognos namespace, and describe how groups and roles map to capabilities
Set object-level permissions on a folder and a report, then verify effective access for a user who inherits from multiple groups
Identify the built-in roles and what each grants, and describe how to grant administrative access without over-privileging
Your checkpoint
A security configuration worksheet showing namespace settings, group-to-role mapping, and a tested permission matrix for at least three users with different access levels
Content Store, Configuration, and Metadata Management
Locate and describe the key configuration files and what each controls, and explain how configuration changes are applied and validated
Describe content store maintenance tasks (backup, growth monitoring, cleanup of orphaned or stale entries) and how to perform each safely
Explain how metadata from a data source is imported, stored, and refreshed, and what happens to reports when metadata changes
Plan a content store migration between environments, listing the steps and the checks that confirm success
Your checkpoint
A content store maintenance and migration checklist with backup, validation, and rollback steps, plus a table of configuration files and their purpose
Performance Tuning, Caching, and Monitoring & Troubleshooting, Logging, and Support Diagnostics
Identify the caching layers in the product (report, data, metadata) and describe how to tune or invalidate each
Set up monitoring of key health indicators and describe how to interpret a slow-report complaint using logs and runtime metrics
Locate and configure the main log files, set log levels for a targeted component, and describe how to reproduce and capture an issue
Assemble a support case package including logs, configuration export, version details, and reproduction steps
Your checkpoint
A troubleshooting playbook with a symptom-to-log-to-cause table for at least five common issues, plus a monitoring checklist of metrics and thresholds
Administration of the Analytics Interface and User Experience & Scheduling, Jobs, and Delivery Administration
Configure the user-facing experience settings (portal, navigation, default entry point, themes) and verify the effect for a non-administrator user
Administer schedules and jobs: create, pause, reschedule, and check run history, and explain how credentials are used at run time
Configure delivery destinations and describe what must be set for email and file-based delivery to succeed
Diagnose a failed scheduled job by tracing its run history and logs to the failing step
Your checkpoint
A scheduling and delivery administration guide covering job creation, credential handling, delivery setup, and a documented diagnosis of one deliberately failed job
Data Source Connections and Data Access Administration & Installation, Upgrade, and Deployment Planning & Security, Authentication, and Authorization
Create and test data source connections for at least two source types, including sign-on configuration and connection-pool settings
Describe how data access is governed (signons, credentials, data source security) and how to restrict who can use a connection
Re-run the pre-install checklist and the security worksheet against your lab to confirm retention of domains 1 and 3
Take two timed practice sets weighted by domain percentage and review every missed item to a root cause
Your checkpoint
A data source administration reference plus a scored practice-exam log with a remediation list for every missed question
Milestones
Week 2: You can explain the upgrade sequence and rollback points from memory and your runbook has been walked through once end to end without gaps
Week 4: A test user from the external namespace signs in and sees exactly the folders and reports your permission matrix predicts, with no over-exposure
Week 6: Given a slow-report symptom, you can name the log to open, the metric to check, and the first three diagnostic steps without notes
Week 8: You score at least 80 percent on a timed mixed practice set and can map every missed item back to a specific domain and study note