How To Improve Archiver Performance And Document Export Throughput In WebCenter Content?
(Doc ID 2215677.1)
Last updated on SEPTEMBER 23, 2021
Applies to:Oracle WebCenter Content - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
How to improve the Archiver performance and hence document export throughput? Any document reference available to help improve throughput of Archiver components? Any options to run multiple Archiver services to boost document migration rate? Any known impact of Archiver, if used for document migration, on ongoing operations of WebCenter Content 11g instance?
Is replication better (in context of document export throughput and impact on current running server) then export/import? Any use case/document that help us build migration plan and strategy better for 12c migration? Can we run multiple standalone Archiver process for different archives on different node of WebCenter Content cluster? Or any way to multi thread Archiver .. e.g. Using API?
Is there any Archiver specific tuning configuration for java heap? Any recommendations for export config that may have positive impact on Archiver performance?
What is an impact/performance of DATABASE.FULLTEXT search index configuration, if enabled, on the source server for document export using Archiver? Any performance numbers about Archiver for document export and import?
Can Archiver export more then one archives at a time? Any known effect/impact of Archiver on WebCenter Content server, especially run during business hours? Any precaution to be taken to ensure no/minimal impact on live instance (source system)?
What is a trade off if using BatchLoader, in addition to or as a replacement of Archiver? Can BatchLoader run from the vault path directly to refer the primary files?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document