1,126
edits
Difference between revisions of "Migrating From Filenet to Content Manager OnDemand"
Migrating From Filenet to Content Manager OnDemand (view source)
Revision as of 18:16, 6 September 2015
, 18:16, 6 September 2015Added section on batches, filled out other sections.
(Initial edit on ingestion.) |
m (Added section on batches, filled out other sections.) |
||
| Line 60: | Line 60: | ||
=== Group reports in chronological order === | === Group reports in chronological order === | ||
Due to the way table segmentation works in OnDemand, you'll want to load the data in chronological order. When you name files, consider including a date field in YYYY-MM-DD format, so it can be sorted numerically at load time. | Due to the way table segmentation works in OnDemand, you'll want to load the data in chronological order. When you name files, consider including a date field in YYYY-MM-DD format, so it can be sorted numerically at load time. This ensures that when the production server goes live, that end users will get speedy and fast database queries. | ||
=== Concatenate Reports === | === Concatenate Reports === | ||
Concatenating reports together means fewer loads (and less overhead, as each load can represent up to 10k in metadata). It also means you'll get better compression for storage. | Concatenating reports together means fewer loads (and less overhead, as each load can represent up to 10k in metadata). It also means you'll get better compression for storage. Depending on the volume of data for a particular report, you may be able to group reports together by month -- and this also works perfectly with the point above, keeping groups of data with similar dates together inside database tables. | ||
=== Produce output in manageable batches === | |||
When producing output, remember that you'll likely need to transfer this data between systems, possibly across the network, and onto different operating systems. There are limitations to different archiving and compression tools (32678 files for .zip archives, and 2GB file size limits for older versions of gzip and bzip2), and you don't want to lose too much time or effort if a file transfer is interrupted. It's best to produce managable, similarly-sized batches that you can use to develop Applications, test loads, and promote from your Development to Quality Assurance ("QA") and Production Servers. | |||
== Order of Operations == | == Order of Operations == | ||