RegContent

Documentum Process Integrator

Process Integrator — shipped as Business Process Services (BPS) — is the integration layer for Process Suite. It moves messages inbound and outbound between workflows and the outside world (HTTP, SMTP, FTP, JMS). It replaces the older Integration Web Services (IWS) stack.

Where it sits

Inbound listeners accept a payload, correlate it to a waiting process instance (or start one), and continue the workflow. Outbound activities send from a process to an external endpoint. Outbound templates run over JMS on the Content Server host — the BPS runtime is not a second workflow engine; it is the transport and correlation front for the one you already have.

Correlation

Two styles. Transport-based puts the token on the channel itself (query string, JMS property, mail header) and matches dm_workflow.correlation_identifier. Content-based pulls a value out of the payload. Pick one per listener and keep the token unique for the life of the instance; reusing a correlation id across processes is how messages attach to the wrong workflow.

Configuration checklist

  1. Process variable that will hold the correlation value.
  2. Correlation set on the process, bound to that variable.
  3. On outbound HTTP, map the correlation token onto the request (query parameter or header the inbound side will read).
  4. Inbound URL suffix on the HTTP listener — this is the path segment after /bps/http/.
  5. Listener preferred_instance so a multi-node BPS farm pins the listener to one runtime.

Inbound HTTP shape (placeholders only):

http://hostname:port/bps/http/{url_suffix}?{corr_param}={corr_id}

Listeners in the docbase

select r_object_id, listener_act_id, preferred_instance
from dmc_bps_listener

update dmc_bps_listener object
set preferred_instance = 'input1'
where listener_act_id = '<id>'

r_object_id values are repository-specific; do not copy them between environments. Pin preferred_instance to a named BPS instance such as input1, not a hostname.

Email replies

SMTP inbound only routes a reply back into the waiting process if the outbound message carried a unique id the listener can recover — the correlation identifier, a unique Message-ID, or both. One id per instance. If two activities share a mailbox and send indistinguishable subjects, replies land unmatched or attach to the wrong workflow. Generate the token when the instance starts, stamp it on the outbound mail, and configure the SMTP listener to read that same token; do not rely on “reply to this folder” as the correlator.

Related