Education
Abstract
When fetching large documents from Documentum Content Server, IBM Content Integrator exhibits Out Of Memory (OOM) issues.
Content
These issues can be addressed in one of two ways. The recommended approach is to modify the IBM Content Integrator client application code to use the latest methods of the IBM Content Integrator API for retrieving native content. The alternative approach is to modify the Java heap size of the Documentum Content Server connector and ensure that a 64-bit JVM is used if the underlying operating system is 64-bit. The two approaches are described in more detail below.
If the IBM Content Integrator client application code is using the deprecated methods in the IBM Content Integrator API for retrieving native content (for example, Content.getNativeContent()), then the client code should be modified to use the non-deprecated method in the Repository class for retrieving native content as a file or as a stream (for example, Repository.getNativeContentAsFile() or Repository.getNativeContentAsStream().
If it is not possible to modify the IBM Content Integrator client application code, then first modify the Java heap size of the Documentum Content Server connector to an optimal level to ensure that there is enough space to retrieve large documents. If the problem persists, ensure that a 64-bit JVM is used if the underlying operating system is 64-bit.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27039631