Resolution:
BC/ebXML doesn't use BC_DUP table for duplicate detection and handling. Instead, it is relying on the BC_EBXML_RELIABLE_MSG table.

BC_EBXML_xxxx tables are updated at the various stages of a conversation between a host and its trading partner (both messages sent AND received).

Almost all inbound and outbound messages are logged in the BC_EBXML_RELIABLE_MSG table. BC_EBXML_MSG_BIN is really used when Duplicate Elimination is enabled. (If a duplicate request message is received and a response message was sent back before, the original response message will be fetched from the BC_EBXML_MSG_BIN table and sent back.)

Two other tables exist:
- BC_EBXML_SEQUENCE is used for sequencing of messages, though it is not yet supported
- BC_EBXML_CONTEXT is used internally by the engine for processing context. Frequency is one for every single job. We expect this table to be used a lot more as the software evolves. The number of rows will not likely grow but the binary data stored in the BC_EBXML_MSG_BIN table will grow in size. It is currently VERY small.

BC ebXML 1.2.0 ships ebxml_rm_cleanup utility to help clean out both BC_EBXML_RELIABLE_MSG and BC_EBXML_MSG_BIN reliable tables of any entries which "persist duration" has expired. There are plans to provide an additional maintenance script.

At the time this article is written (ebXML 1.2.0 is the latest version). We expect that one of the upcoming patches will provide a data compression feature for all data stored in the BIN table. This should help decrease disk space usage.