std.CreateCPMessages

This job creates up to three new content/processing messages in the server-side oscpmqueue for a DMS object: one each for full-text indexing, filter pre-processing and rendition creation. Which messages are created is controlled by boolean flags in the call.

Several flags may be set in a single call; for every true flag one separate message is created — same object reference, different queuename. If all flags are false, the call has no effect.

The complete lifecycle of a CP message is described under Capture and Processing Messages (CP).

This job is not listed in the official enaio® standard engine overview (std).

1. Input Parameters

Name Type Required Description

ObjectID

INT

Yes

Numeric ID of the DMS object the created messages refer to. Stored as osid on each created message.

ObjectType

INT

Yes

Object type ID of the DMS object. Stored as ostype on each created message.

CreateFulltextIdxMessages

BOOL

Yes

true — create a message in the FULLTEXTIDX queue (indexing registration).

CreateFulltextFilterMessages

BOOL

Yes

true — create a message in the FULLTEXTFILTER queue (filter / pre-processing step).

CreateRenditionMessages

BOOL

Yes

true — create a message in the RENDITION queue (creation of the searchable PDF/text rendition).

Flags

INT

Yes

Reserved; always pass 0.

2. Return Value

(INT): 0 = job successful, otherwise error code. The MessageGUID values of the created messages are not returned — they only become visible on later pickup through std.GetNextCPMessage.

3. Notes

  • No caller-side deduplication takes place: every requested message is created, even if an unreserved message for the same object already exists in the same queue. The implicit collapse happens only on pickup — see Coalescing of redundant messages.

  • The call returns immediately after the messages have been inserted; the actual processing happens asynchronously through the respective worker services.

  • Only the queues FULLTEXTIDX, FULLTEXTFILTER and RENDITION can be addressed directly through this job. The remaining known queues (FULLTEXTDOC, FULLTEXTLOCATION, FULLTEXTDELETE, RENRESET, PAGECOUNT) are filled by other server-internal paths.