1,126
edits
Difference between revisions of "Migrating From Filenet to Content Manager OnDemand"
Jump to navigation
Jump to search
m
Migrating From Filenet to Content Manager OnDemand (view source)
Revision as of 14:08, 30 July 2015
, 14:08, 30 July 2015added intermediate file transfer systems
m (Expanded Scope section.) |
m (added intermediate file transfer systems) |
||
| Line 38: | Line 38: | ||
=== Transfer in Original Formats === | === Transfer in Original Formats === | ||
For some Filenet installations, upstream servers convert report data (from EBCDIC to ASCII) and change the formatting of the report. Content Manager OnDemand doesn't need any data transformation, and can ingest EBCDIC reports (of fixed record length, stream, or variable record lengths) directly and without conversion. Some conversion tools (I'm looking at you, MQ Series File Transfer Edition) can be configured to change the report so drastically, that CMOD can't properly index it. | For some Filenet installations, upstream servers (or intermediate file transfer systems) convert report data (from EBCDIC to ASCII) and change the formatting of the report. Content Manager OnDemand doesn't need any data transformation, and can ingest EBCDIC reports (of fixed record length, stream, or variable record lengths) directly and without conversion. Some conversion tools (I'm looking at you, MQ Series File Transfer Edition) can be configured to change the report so drastically, that CMOD can't properly index it. | ||
Wherever possible, remove any data conversion and deliver report data to OnDemand in its original format. | Wherever possible, remove any data conversion and deliver report data to OnDemand in its original format. | ||