Asynchronous Write (dm_AsynchronousWrite)

When users import documents in asynchronous mode, there may be instances where some or all content may not be immediately replicated from BOCS to ACS. This might happen if the Documentum Messaging Services (DMS) server was not available or there were network issues between BOCS, DMS, and/or ACS.

The Asynchronous Write job polls for content still in a parked state and generates new messages for the DMS server to pass to BOCS to request the upload of the parked content. After execution, the job lists all content objects that had yet to be moved from the parked state and for which messages were sent to the DMS server. If a BOCS server receives a request to migrate content that is has already processed, it will ignore the request.

This job is inactive by default, but should be enabled whenever asynchronous mode is allowed. The job is scheduled to run daily at 2:00 a.m. by default.