Samuels IBM Content Manager OnDemand Lab

Platform Overview

IBM_CMOD_DEMO / Archive / Records / Governance

IBM Content Manager OnDemand demonstration workspace: an engineering lab modeled on CMOD's high-volume report archive architecture. The lab follows the product's native object model—Application Groups, Applications and Folders—and the operational path from indexing and loading through storage management, retrieval, retention, expiration and modernization. This is an independent Samuels Enterprises lab, not an official IBM interface.

Documents Loaded24.8Mstatements / reports / correspondence

Application Groups18common index + storage policy sets

Applications32report / source definitions

Folders14search + retrieval entry points

Migration Queue147cache objects eligible for archive

CMOD Architecture — familiar Samuels shell, authentic OnDemand process

1 · SOURCE OUTPUTStatements · invoices · reports · policies · correspondence · line data · PDF · AFP

2 · INDEX + LOADIndexer extracts search keys; load process writes index rows and document objects

3 · LIBRARY SERVERDefinitions, security, application-group index tables and system metadata

4 · OBJECT / STORAGECache for active access; archive/object storage for long-term retention

5 · SEARCH + RETRIEVEFolders map user criteria to application-group fields and return original content

▤

High-Volume Report Archive

CMOD is built to capture, index, archive and retrieve large volumes of generated output—especially statements, reports, invoices and customer correspondence.

Application Group Model

Reports with common indexing and storage requirements are grouped together. The application-group database fields become the searchable index structure.

⌕

Folder-Based Retrieval

Users search through folders. Folder search fields map to application-group database fields such as account, customer, statement date or invoice number.

⇄

Storage Management

Documents can remain on cache for rapid access and migrate to archive storage according to application-group migration policy.

⏱

Retention + Expiration

Life of Data and Indexes, cache periods, expiration type and optional Enhanced Retention Management determine how content ages and when it can be removed.

☁

Modern Archive Targets

Modern deployments can use traditional storage and supported object-storage targets, enabling staged modernization without changing the familiar CMOD information model.

Statements / Reports: CMOD is report-centric rather than folder-centric in the traditional document-management sense. Each report or source is normally represented as an Application, assigned to an Application Group that supplies its shared index schema and storage policy.

▤

Outbound Statements

Archive periodic customer statements, bills and account communications at scale while preserving searchable business keys and the original presentation format.

▦

Enterprise Reports

Store computer-generated output and operational reports so users retrieve only the pages or document segments matching their business criteria.

◫

Transactional Correspondence

Policies, invoices, notices and other generated correspondence can share common application-group fields when they have compatible indexing and retention requirements.

Representative Report Definitions demonstration

Monthly Customer StatementApplication: MONTHLY_STMT · Group: CUSTOMER_FINANCIALS · Index: Account No / Statement Date / Customer ID Invoice RegisterApplication: AP_INVOICE · Group: FINANCE_REPORTS · Index: Vendor / Invoice No / Invoice Date / Amount Claims ExplanationApplication: CLAIM_EOB · Group: CLAIMS_OUTPUT · Index: Member ID / Claim No / Service Date Regulatory ReportApplication: REG_RPT · Group: COMPLIANCE_REPORTS · Index: Report Type / Period / Business Unit

Content Formats / Presentation

CMOD environments commonly manage formatted print output and enterprise reports, including line-oriented data, PDF, AFP and other generated content. Viewing behavior is defined with the application and presented through CMOD clients such as IBM Content Navigator or the OnDemand client.

Core object model: before loading a report, administrators define an Application Group and an Application; before users can search and retrieve, they define a Folder. This relationship is foundational to CMOD administration.

Application Group

Collection of reports with common index and storage-management requirements. It owns the database fields, security model, database organization and storage policy.

APP

Application

Defines one report/data source and tells indexing, loading and viewing programs how to interpret that source. Multiple applications may share one application group.

Folder

User-facing search definition. Folder fields map to one or more application-group fields, allowing a business search to span report definitions where designed.

Example Definition Chain

APPLICATION GROUPCUSTOMER_FINANCIALS

DATABASE FIELDScustomer_id · account_no · doc_date · doc_type

APPLICATIONSMONTHLY_STMT · TAX_FORM · ANNUAL_NOTICE

FOLDERCustomer Correspondence

USER SEARCHAccount + date range → matching documents

Indexing / Loading: CMOD separates the business search index from the stored document object. Indexers extract values from source output; load processing writes those values into application-group index tables and stores document data under the configured storage policy.

ACIF / Line-Data Indexing

Supports high-volume computer output where report boundaries and search keys are derived from structured print data.

PDF

PDF Indexer

Defines how index values and document boundaries are identified in PDF-based report streams.

XML

XML Indexer

Provides indexing support for XML-based source content where business keys can be extracted from structured markup.

Load Pipeline

RECEIVEReport file arrives from print, billing, ERP, policy or transactional system

INDEXExtract application-defined fields and segment the source into retrievable documents

MAPMap extracted fields to application-group database columns

STOREWrite index rows to the library database and content to object/cache/archive storage

VERIFYConfirm load status, document count, index values and searchability

Administrator Vocabulary

ARSLOAD is commonly associated with loading indexed data into CMOD. Advanced administration also uses ARSADMIN, ARSDOC, ARSMAINT and ARSXML for system, document, maintenance and object-definition operations.

Retention / Holds: standard CMOD retention is primarily application-group driven. Enhanced Retention Management adds document-level holds and implied holds for circumstances—such as litigation or policy obligations—where time-based expiration alone is insufficient.

Standard Retention Controls

Life of Data and Indexes controls how long documents remain addressable in CMOD.

Cache Document Data For n Days controls the active cache period.

Expiration Type determines the unit of expiration processing, such as load/segment/document depending on configuration and feature use.

Migration Policy controls when content moves from cache toward archive storage.

Enhanced Retention Management

Hold — applied to selected documents located through search.

Implied Hold — applied when documents are loaded into qualifying new application groups.

Multiple holds may apply to one document. A held document is not eligible for final expiration until the relevant holds are removed.

Governed Expiration Sequence

RETENTION CLOCKLife of Data / archive retention reaches eligibility

HOLD CHECKDetermine whether ERM hold or implied hold blocks expiration

ARSMAINTRun scheduled maintenance / expiration processing

INDEX EXPIRYRemove CMOD index references when criteria are satisfied

STORAGE CLEANUPStorage manager reclaims eligible cache/archive objects under aligned policy

Search / Retrieval: users do not need to understand the physical storage location. They open a Folder, enter business criteria, receive result rows from application-group indexes and retrieve the matching document from cache or archive storage.

Folder Search — Customer Correspondence simulated

Account Number004892771Customer IDCUS-101884Document Date2026-01-01 through 2026-09-21Document TypeStatement / Notice / Invoice

Open Folder

The folder exposes business search fields and hides the underlying application-group table complexity.

Search Indexes

Search criteria are mapped to application-group fields such as account, name, date, document type or transaction identifier.

Retrieve Original

The object server resolves the stored content and returns the original or transformed representation through the chosen client.

Client Access

IBM Content Navigator provides a modern web client experience. The OnDemand client remains part of many established environments. ODWEK Java APIs and REST Services support application integration and programmatic retrieval.

Storage Migration: in CMOD, migration means moving document data through the storage hierarchy—not simply exporting files. An application group's migration policy determines when content leaves high-speed cache and where the next archive copy is maintained.

Cache → Archive Lifecycle

LOADNew content enters cache for fast access

ELIGIBILITYMigration policy evaluates age / configured trigger

MIGRATEARSMAINT copies eligible objects to archive storage

EXPIRE CACHECache copy becomes removable after policy conditions are met

RETRIEVELater user request can be serviced from archive transparently

Cache Storage Manager

Maintains active document objects on disk for fast retrieval and supports cache-space reclamation after migration / expiration processing.

Archive Storage

Maintains long-term copies according to the storage set and retention policy; the physical storage implementation can be modernized independently of the business search model.

Maintenance Coordination

Migration and expiration are separate operations. Administrators schedule maintenance so index lifecycle, cache cleanup and archive retention stay aligned.

Cloud / Archive Modernization: modernization does not require abandoning CMOD's proven report model. The lab demonstrates preserving Application Groups, Applications, Folders and retrieval behavior while changing infrastructure, storage tiers and integration surfaces.

Deployment Patterns

On-Premises CMOD — traditional library/object server deployment with enterprise storage.

IBM Content Manager OnDemand on Cloud — secure single-tenant IBM Cloud service for reports, statements, transactional records and customer correspondence.

Hybrid Modernization — retain CMOD administration and retrieval while introducing supported external object-storage targets.

Modern Storage Targets

CMOD 10.5 supports multiple external object-storage options, including IBM Cloud Object Storage and S3-compatible targets, with additional supported platforms documented by IBM. WORM / immutable-object configurations can be used where supported to protect retained content from modification or deletion during its retention period.

Modernization Workstream

DISCOVERInventory applications, groups, folders, index fields, volumes and retention dependencies

BASELINECapture load rates, retrieval SLAs, cache sizing and archive growth

MAPMap current storage sets to target object / cloud tiers

VALIDATETest load, search, retrieval, hold, migration and expiration behavior

CUTOVERMove in controlled waves with reconciliation and rollback evidence

Operations / Maintenance: CMOD is an operational archive platform. Production familiarity includes scheduled loading, database/index maintenance, migration, expiration, system-log review, storage monitoring and recoverability—not only user-facing search.

ARSLOAD

Load report data and associated indexes into the configured application group / application environment.

ARSMAINT

Perform maintenance operations such as migration and expiration so cache, indexes and archive storage remain healthy.

ARSDOC

Administrative document operations, including searching / document-level tasks and hold-related operations in applicable environments.

ARSADMIN

Administrative utilities used for load/unload and other system-oriented operations.

ARSXML

Export and import CMOD object definitions, useful for controlled promotion of users, groups and system definitions.

LOG

System Log

Review server events, loads, retrieval issues and operational warnings as part of incident diagnosis and support readiness.

Retrieval Console: this view simulates the user experience CMOD is optimized for—enter precise business keys, search indexed metadata and retrieve a high-volume archive object without navigating a traditional directory tree.

Customer Correspondence Folder query profile

Account004892771Date Range2026-07-01 → 2026-09-21TypeMONTHLY_STMTStatus3 matching documents · retrieval path available

Search Results

2026-09-01 · Monthly Statement · Account 004892771 · 18 pages · Cache

2026-08-01 · Monthly Statement · Account 004892771 · 17 pages · Archive

2026-07-01 · Monthly Statement · Account 004892771 · 18 pages · Archive

⌕

Indexed Search

Optimized for business fields rather than brute-force scanning of every document.

↯

Fast Retrieval

Search returns index matches first, then the object server resolves the selected document from the appropriate storage tier.

◧

Original Fidelity

CMOD preserves report output for viewing and printing while enabling electronic access in place of large physical print archives.

Integration surface: modern CMOD environments can expose archive functions without forcing external applications to understand internal storage. IBM provides both the established ODWEK Java APIs and newer REST Services, while IBM Content Navigator supplies a feature-rich web client.

REST

REST Services

HTTP-based, stateless APIs can list folders and application groups, search, retrieve, store, update metadata and delete documents where authorized.

ODWEK

The OnDemand Web Enablement Kit provides Java APIs and transformation capabilities for web and enterprise integration scenarios.

ICN

IBM Content Navigator

Provides a modern browser experience for CMOD search, retrieval, viewing and related user tasks without exposing archive internals.

Enterprise Integration Pattern

ERP / BILLINGProduces reports and statements

CMODIndexes, archives and governs output

REST / ODWEKSecure programmatic access

PORTAL / CSRBusiness application requests content

VIEWOriginal or transformed document returned

Administration: CMOD administration is definition-driven. Administrators manage the library-server catalog, object-server storage paths, users and groups, application groups, applications, folders, storage sets and operational utilities that govern how enterprise output is indexed, loaded, stored, searched, retrieved, migrated and expired.

Library Server Administration

Maintains CMOD definitions, authentication and authorization context, application-group index tables, folder mappings, system metadata and the catalog information used to locate report objects.

Object Server Administration

Manages report objects and resources across cache and archive tiers, resolves retrieval requests and works with configured storage managers and storage nodes.

Application Groups

Define database fields, database organization, permissions, storage set, cache behavior, migration policy and retention characteristics shared by related report applications.

APP

Applications

Define the physical and logical characteristics of each report source, including data type, indexing parameters, load behavior, viewing, printing and resource requirements.

Folders / Field Mapping

Define the business-facing search experience. Folder fields are mapped to application-group database fields so users search with familiar values such as account, invoice number, customer ID or date.

Users / Groups / Authority

Assign folder and application-group access, administrative authority and function permissions. User-specific permissions can override broader group or default access where configured.

Administrator Operating Cycle

DEFINEUsers · groups · storage sets · application groups · applications · folders

LOADValidate index extraction and ARSLOAD processing

MONITORSystem log · load results · cache/archive availability · object access

MAINTAINARSMAINT · migration · expiration · database and cache housekeeping

VERIFYSearch · retrieve · permissions · retention · operational evidence

Security / Governance: CMOD governance is enforced through controlled access to folders and application groups, administrative authority, system logging, storage policy, retention configuration, document holds and scheduled maintenance. The purpose is to preserve trustworthy access to high-volume archived output while keeping index data, stored objects and lifecycle rules synchronized.

Authorization Model

Users authenticate to the CMOD environment and receive authority through user, group and default permissions. Folder permission determines whether a user can open the search definition; application-group permission determines whether the user can search and retrieve the underlying archived data. Administrative authority is separated from ordinary end-user access.

Governance Evidence

System-log entries, load history, application-group and folder definitions, storage-set assignments, migration and expiration processing, retention settings, hold activity and retrieval outcomes create an operational record of how content entered the archive, where it was maintained, who could access it and how long it remained protected.

Enhanced Retention / Holds

Enhanced Retention Management can place targeted documents under hold so they remain protected even when ordinary expiration criteria would otherwise make them eligible for removal.

Immutable / WORM Storage

Where supported by the selected storage platform, immutable or WORM controls can provide an additional physical enforcement layer for content that must not be altered or deleted during its retention period.

Lifecycle Alignment

Life of Data and Indexes, expiration type, cache policy, migration policy and archive-storage retention should be designed together so metadata and physical objects remain available for the required lifecycle.

Access Control Chain

IDENTITYUser authentication

GROUP / AUTHORITYAdministrative and functional rights

FOLDER ACCESSCan the search definition be opened

APP GROUP ACCESSCan archived data be searched and retrieved

EVIDENCESystem-log and operational traceability

IBM CMOD Support workspace: incident-readiness for a high-volume archive should identify the exact server role, CMOD object, load, storage tier and user-facing symptom before escalation.

Support Reference Areas

IBM Content Manager OnDemand 10.5 Documentation IBM Content Manager OnDemand Support IBM Content Manager OnDemand Product Reference IBM Content Navigator Documentation

Samuels Enterprises

Enterprise Portfolio — samuelsenterprisesllc.com/enterprise More Information — samuelsenterprisesllc.com Enterprise Support — support@samuelsenterprisesllc.com

Incident Intake Checklist

Product / VersionContent Manager OnDemand · platform / fix levelServer RoleLibrary server / Object server / Web / REST / ICN integrationObjectApplication Group / Application / Folder / Storage SetOperationIndex / Load / Search / Retrieve / Migrate / Expire / HoldEvidenceTimestamp · command · return code · system-log entry · affected load/document

Diagnostic Thinking

Load failure — validate application definition, index extraction, field mapping, permissions and storage availability.

Search misses — confirm folder mapping and loaded application-group index values.

Retrieve fails — isolate library lookup versus object, cache or archive access.

Migration issue — inspect migration policy, storage set and ARSMAINT scheduling.

Retention issue — compare Life of Data and Indexes, expiration type, storage-manager retention and Enhanced Retention Management holds.

Reference Set

IBM Content Manager OnDemand V10.5 documentation · Introduction and Planning · Administration Guide · Indexing Reference · Web Enablement Kit Implementation Guide · Enhanced Retention Management guidance · IBM Content Navigator documentation · CMOD system command utilities including ARSLOAD, ARSMAINT, ARSDOC, ARSADMIN and ARSXML.

Lab Disclaimer: This IBM Content Manager OnDemand Lab is an independent Samuels Enterprises engineering demonstration. IBM and IBM Content Manager OnDemand are trademarks of International Business Machines Corporation. The interface is not an IBM product screen; the goal is to demonstrate accurate architecture, terminology and process understanding inside the consistent Samuels Enterprise Lab experience.