JPerformer adds Documentum support by way of its bespoke capture/convert/replay mechanism. JPerformer comes pre-packaged with a set of classes that utilise this technology to allow Documentum transactions to be simulated out of the box.

Documentum as a middleware has two separate streams of communication. One of these streams is specifically coded to bypass proxies. Therefore normal proxied capturing mechanisms will not record this data. JPerformer utilising packet sniffing technology as well as a proxied mechanism which enables this unproxied data to be recorded.

Documentum uses normal HTTP but its payloads are sometimes encoded binary types (i.e application/octet-stream, application/x-deflated-java-serialized-object) therefore packet sniffing based capturing processes will capture the data but not be able to understand the content. JPerformer's bespoke converter mechanism allows packets to be processed by an externally defined class which breaks down the content and creates java code to replicate the interaction.

The two sets of Documentum communications work independently to each other in a manner that does not lend itself well to a procedural script. JPerformer uses a multi-threaded synchronisation method that allows multiple requests to run consecutively and independently from each other allowing replaying of Documentum transactions to closely mirror that of actual usage.