Difference between revisions of "Migrating From Filenet to Content Manager OnDemand"

m
Updated CMOD to IBM CMOD.
m (Clarified Application definition.)
m (Updated CMOD to IBM CMOD.)
Line 40: Line 40:
=== Converting Document Classes ===
=== Converting Document Classes ===


Content Manager OnDemand ("CMOD") has an entirely different architecture than the Filenet products.  In CMOD vernacular, an 'Application' is analogous to an individual report. But in CMOD, the top of the hierarchy is the 'Application Group' -- a grouping of Applications (aka 'reports') where the index fields, storage, and retention requirements are all the same.  Properly defined Application Groups can have multiple Applications (again, 'reports') that belong to it.  The most rational way to design Application Groups is to combine reports together that fulfill a specific business need.  Human Resources reports shouldn't intermingle with Accounts Payable (even if they have the same index fields), and are kept logically separate by keeping their reports in separate Application Groups.
IBM Content Manager OnDemand ("CMOD") has an entirely different architecture than the Filenet products.  In IBM CMOD vernacular, an 'Application' is analogous to an individual report. But in CMOD, the top of the hierarchy is the 'Application Group' -- a grouping of Applications (aka 'reports') where the index fields, storage, and retention requirements are all the same.  Properly defined Application Groups can have multiple Applications (again, 'reports') that belong to it.  The most rational way to design Application Groups is to combine reports together that fulfill a specific business need.  Human Resources reports shouldn't intermingle with Accounts Payable (even if they have the same index fields), and are kept logically separate by keeping their reports in separate Application Groups.


=== Quantify index usage ===
=== Quantify index usage ===