joogy06/agent-foundry/cognos-admin

Name: cognos-admin
Author: joogy06

Claude Code and agent skill by joogy06/agent-foundry

Trust tier 2

community
ext:[{"type":"plugin","description":"Custom plugin integration"}]

LLM review pending

Source check pending

Checking that the SKILL.md file is still in the repository.

Use when administering IBM Cognos Analytics or using its APIs — installation and configuration, security (namespaces/roles/capabilities), content administration, report management, Framework Manager modeling, REST API (session/content/reports/dashboards), data source connections, scheduling and bursting, performance tuning, and Cognos on Cloud Pak for Data. Covers Cognos Analytics 12.x (11.2.x legacy — out of standard support 2026-04).

Install

npx vskill@latest install joogy06/agent-foundry/cognos-admin

Semi-extensibleMentions customization, but needs skill-specific knowledge. Read the extensible skills standard

SKILL.md

IBM Cognos Analytics — Administration & API

<HARD-RULE> Always back up the content store database before any Cognos upgrade or major configuration change. Use pg_dump, db2 backup, or the appropriate RDBMS tool, and verify the backup restores cleanly to a scratch instance before proceeding. </HARD-RULE>

<HARD-RULE> Never grant the System Administrator capability broadly — it bypasses all content security. Assign it only to a small, named group of platform administrators, and audit membership quarterly. </HARD-RULE>

<HARD-RULE> Always use Framework Manager security filters for row-level data security — report-level filters can be bypassed by users with authoring permissions. Security filters are enforced at the query layer regardless of how the data is accessed. </HARD-RULE>

<HARD-RULE> Never expose the Cognos dispatcher port (9300/9380) directly to the internet — always front with a reverse proxy (Apache, Nginx, or IBM HTTP Server) with TLS termination. The dispatcher protocol is not designed for untrusted networks. </HARD-RULE>

1. Architecture

Version lifecycle (verified 2026-06): Cognos Analytics 11.2.x exited IBM standard support on 2026-04-30 (extended/sustained support tiers continue per IBM lifecycle — verify current terms). New installs and upgrades should target 12.x; treat 11.2.x guidance below as legacy-maintenance only.

Core Components

Component	Role	Default Port
Gateway	Entry point — reverse proxy to dispatchers, handles HTTP/HTTPS	80/443 (web server)
Content Manager	Manages content store DB, security, sessions, configuration	9300 (internal)
Dispatcher	Routes requests to services, load balancing	9300/9380
Query Service	Executes queries against data sources	Internal
Report Service	Renders reports (interactive/HTML)	Internal
Batch Report Service	Runs scheduled/burst reports	Internal
Presentation Service	Serves Cognos Analytics UI (dashboards, stories, explorations)	Internal
Data Integration Service	ETL / data movement (if licensed)	Internal

Content Store

The content store is a relational database that holds all Cognos metadata — reports, folders, schedules, security policies, user preferences, deployment specs. Supported databases:

PostgreSQL (bundled with 12.x installer)
IBM DB2
Microsoft SQL Server
Oracle Database

The content store does NOT store report output data or data source data — only metadata and configuration.

Process Flow

Browser → Gateway (IHS/Apache/Nginx) → Dispatcher → Content Manager → Content Store DB
                                          ↓
                                    Query Service → Data Source (RDBMS/OLAP)
                                          ↓
                                    Report Service → Rendered Output

Authentication flow: Browser → Gateway → CAM (Cognos Access Manager) → Authentication Namespace (LDAP/AD/OIDC/SAML) → Session Token → Dispatcher.

2. Installation & Configuration

Prerequisites

bash

# RHEL/CentOS — required libraries
sudo dnf install -y libX11 libXext libXrender fontconfig freetype \
  libpng libjpeg-turbo libXtst libXi nss nspr \
  glibc.i686 libstdc++.i686
 
# Verify ulimits (add to /etc/security/limits.d/cognos.conf)
cognos  soft  nofile  65536
cognos  hard  nofile  65536
cognos  soft  nproc   16384
cognos  hard  nproc   16384

Silent Install (Linux)

bash

# Extract installer
tar xzf ca_server_12.0.x_linux_x86.tar.gz -C /tmp/cognos-install
 
# Create response file for silent install
cat > /tmp/cognos-response.properties <<'EOF'
INSTALLER_UI=silent
USER_INSTALL_DIR=/opt/ibm/cognos/analytics
LICENSE_ACCEPTED=true
CHOSEN_INSTALL_SET=Express
EOF
 
# Run silent install
/tmp/cognos-install/install.sh -i silent -f /tmp/cognos-response.properties

Content Store Setup — PostgreSQL

bash

# Create content store database (using bundled or external PostgreSQL)
sudo -u postgres psql <<'EOF'
CREATE ROLE cognos WITH LOGIN PASSWORD 'CognosCS!2024' VALID UNTIL '2028-01-01';
CREATE DATABASE cognoscs OWNER cognos ENCODING 'UTF8' LC_COLLATE 'en_US.UTF-8' LC_CTYPE 'en_US.UTF-8';
GRANT ALL PRIVILEGES ON DATABASE cognoscs TO cognos;
EOF

Content Store Setup — DB2

bash

# Create DB2 database for content store
db2 "CREATE DATABASE COGNOSCS AUTOMATIC STORAGE YES USING CODESET UTF-8 TERRITORY US COLLATE USING IDENTITY PAGESIZE 16384"
db2 "CONNECT TO COGNOSCS"
db2 "CREATE BUFFERPOOL BP16K IMMEDIATE SIZE 1000 AUTOMATIC PAGESIZE 16 K"
db2 "CREATE REGULAR TABLESPACE COGNOSTS PAGESIZE 16 K MANAGED BY AUTOMATIC STORAGE BUFFERPOOL BP16K"
db2 "GRANT DBADM ON DATABASE TO USER cognos"

Content Store Setup — SQL Server

sql

-- SQL Server content store
CREATE DATABASE cognoscs COLLATE Latin1_General_CS_AS;
GO
USE cognoscs;
CREATE LOGIN cognos WITH PASSWORD = 'CognosCS!2024';
CREATE USER cognos FOR LOGIN cognos;
ALTER ROLE db_owner ADD MEMBER cognos;
GO

cogconfig.sh — Configuration Tool

bash

# Launch configuration UI (X11 forwarding or VNC required)
/opt/ibm/cognos/analytics/bin64/cogconfig.sh
 
# Key configuration locations
# Config XML: /opt/ibm/cognos/analytics/configuration/cogstartup.xml
# Templates:  /opt/ibm/cognos/analytics/configuration/templates/

Key cogstartup.xml settings:

xml

<!-- Content store connection -->
<crn:parameter name="contentStoreURI">
  <crn:value>jdbc:postgresql://dbhost:5432/cognoscs</crn:value>
</crn:parameter>
 
<!-- Gateway URI (external-facing URL) -->
<crn:parameter name="externalDispatcherURI">
  <crn:value>http://cognos-server:9300/p2pd/servlet/dispatch</crn:value>
</crn:parameter>
 
<!-- Gateway settings -->
<crn:parameter name="gateway">
  <crn:value>http://cognos-server:443/bi/v1/disp</crn:value>
</crn:parameter>
 
<!-- Internal dispatcher URI -->
<crn:parameter name="internalDispatcherURI">
  <crn:value>http://localhost:9300/p2pd/servlet/dispatch</crn:value>
</crn:parameter>

Cryptographic Keys

bash

# Generate new cryptographic keys (required on fresh install)
/opt/ibm/cognos/analytics/bin64/cogconfig.sh -s
 
# Export keys for backup (critical — lost keys = inaccessible content store)
cp /opt/ibm/cognos/analytics/configuration/signkeypair/*.* /backup/cognos/keys/
cp /opt/ibm/cognos/analytics/configuration/encryptkeypair/*.* /backup/cognos/keys/

Start / Stop Cognos Service

bash

# Start Cognos Analytics
/opt/ibm/cognos/analytics/bin64/cogserver.sh -start
 
# Stop Cognos Analytics
/opt/ibm/cognos/analytics/bin64/cogserver.sh -stop
 
# Check status
/opt/ibm/cognos/analytics/bin64/cogserver.sh -status
 
# Tail the main log
tail -f /opt/ibm/cognos/analytics/logs/cogserver.log

Systemd Service (Production)

/etc/systemd/system/cognos.service:

ini

[Unit]
Description=IBM Cognos Analytics
After=network.target postgresql.service
Wants=postgresql.service
 
[Service]
Type=forking
User=cognos
Group=cognos
ExecStart=/opt/ibm/cognos/analytics/bin64/cogserver.sh -start
ExecStop=/opt/ibm/cognos/analytics/bin64/cogserver.sh -stop
TimeoutStartSec=300
TimeoutStopSec=120
LimitNOFILE=65536
LimitNPROC=16384
 
[Install]
WantedBy=multi-user.target

bash

sudo systemctl daemon-reload
sudo systemctl enable --now cognos

3. Security

Authentication Namespaces

Cognos supports multiple authentication providers configured in cogstartup.xml via Cognos Configuration:

LDAP / Active Directory:

xml

<crn:parameter name="AAA_Namespace">
  <crn:value>
    <crn:instance name="CorporateAD" class="NTLM">
      <crn:property name="connection">ldap://dc01.corp.local:389</crn:property>
      <crn:property name="baseDN">dc=corp,dc=local</crn:property>
      <crn:property name="userLookup">(sAMAccountName=${userID})</crn:property>
      <crn:property name="bindCredentials">CN=CognosSvc,OU=Service,DC=corp,DC=local</crn:property>
      <crn:property name="sizeLimit">500</crn:property>
    </crn:instance>
  </crn:value>
</crn:parameter>

OIDC (OpenID Connect) — Cognos 12.x:

Configure via Administration Console > Security > Authentication:

Provider URL (e.g., https://idp.corp.local/realms/cognos/.well-known/openid-configuration)
Client ID and Secret
Redirect URI: https://cognos.corp.local/bi/completeLogin.jsp
Claim mapping: preferred_username → Cognos identity
Scope: openid profile email

SAML 2.0:

Configure via Cognos Configuration:

Identity Provider metadata XML import
Service Provider entity ID and ACS URL
Certificate exchange (IdP signing cert, SP encryption cert)
NameID format mapping

Groups, Roles, and Capabilities

Built-in security objects hierarchy:
├── Cognos namespace (built-in)
│   ├── Everyone group
│   ├── All Authenticated Users group
│   ├── Anonymous
│   └── Built-in roles:
│       ├── System Administrators
│       ├── Directory Administrators
│       ├── Report Administrators
│       ├── Analytics Administrators
│       ├── Analytics Users
│       ├── Authors
│       └── Consumers
└── External namespaces (AD/LDAP/OIDC/SAML)
    ├── Groups (mapped from directory)
    └── Users (authenticated from directory)

Key Capabilities (Administration Console > Security > Capabilities):

Capability	Risk Level	Description
Administration	HIGH	Full admin console access
Manage content	HIGH	Create/modify/delete any content
Generate output	LOW	Run reports
Schedule	LOW	Create schedules
Burst reports	MEDIUM	Configure burst distribution
Create/delete	MEDIUM	Author new content
HTML items in report	HIGH	Can embed arbitrary HTML/JS
Adaptive Analytics	LOW	Use AI assistant features

Security Policy Best Practice:

Content → Properties → Permissions:
  ├── Traverse (see the folder in navigation)
  ├── Read (view/run the report)
  ├── Write (edit the report)
  ├── Execute (run schedules)
  └── Set Policy (change permissions on this object)
 
Apply at folder level, let child objects inherit.
Break inheritance only when a subfolder needs different access.

Multitenancy

Cognos 12.x supports multitenancy for SaaS/shared deployments:

Tenant ID mapped from authentication claim or LDAP attribute
Content isolation per tenant (each tenant sees only their folders)
Separate data source connections per tenant
Tenant-level theme/branding customization
Configure via Administration Console > Multitenancy

4. Content Administration

Administration Console

Access at: https://cognos-server/bi/v1/disp?b_action=xts.run&m=portal/admin/admin.xts

Or navigate: Manage > Administration Console (gear icon in Cognos Analytics UI).

Content Organization

Content store structure:
├── Team content (shared across organization)
│   ├── Packages (published FM metadata)
│   ├── Reports
│   ├── Dashboards
│   └── Data modules
├── My content (per-user private area)
├── Administration (admin-only)
│   ├── Configuration
│   ├── Distribution lists
│   └── Deployment
└── Samples (out-of-box demo content)

Content Deployment (Import/Export)

bash

# Export a deployment archive via command line
/opt/ibm/cognos/analytics/bin64/contentManagerService.sh \
  -export \
  -name "Q4_2025_Backup" \
  -archive "/backup/cognos/Q4_2025_Backup.zip" \
  -password "ExportP@ss!2024"
 
# Import a deployment archive
/opt/ibm/cognos/analytics/bin64/contentManagerService.sh \
  -import \
  -name "Q4_2025_Backup" \
  -archive "/backup/cognos/Q4_2025_Backup.zip" \
  -password "ExportP@ss!2024"

Via Administration Console:

Configuration > Content Administration > New Export / New Import
Select folders/packages to include
Choose conflict resolution (replace, keep existing, or rename)
Set password for archive encryption
Run immediately or schedule

Search Index

This is the start of the file. Read the full SKILL.md on GitHub.

Security

Security scanPassed, 100 of 100Pattern checks on the skill's files.
Model reviewNot runA model review is scheduled for the next rescan.

See the full security report

Quality evaluation

Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

See evaluation results

Source

SKILL.md in the repositoryCheckingskills/cognos-admin/SKILL.md

Popularity

Repository stars: 2
7-day trend score: 5

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Extension points

pluginCustom plugin integration

Learn the extensible skills standard

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

Claude Code
Cursor
GitHub Copilot
Windsurf
Codex
Gemini CLI
Cline
Amp
Roo Code
Goose
Continue
Kilo Code
Junie
Trae
OpenHands
Qwen Code
AI Agent
Tabnine Chat
Sourcegraph Cody
Amazon Q
Firebase Genkit
Sweep
Devin
Phind
Mentat
Claude Desktop
Aider
GPT Pilot
Plandex
bolt.new
v0
Replit Agent
Anse
TypingMind
BetterChatGPT
LibreChat
Warp AI
Pieces
Fig AI

Embed badge

[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/joogy06/agent-foundry/cognos-admin/badge)](https://verified-skill.com/skills/joogy06/agent-foundry/cognos-admin)

Something wrong with this skill or its page? Tell us.