Sterling B2B suffers in terms of human/document oriented workflow features and long time document archiving. Create a direct connection between Sterling B2B and ECM without using the file system adds great benefit: Sterling can delegate ECM for human oriented workflow like approval processes and Sterling can retrieve back the updated and approved document.
ECM can provide (typically out-otb) searching features by which with 1 property we can correlated a set of documents even if they are stored into different folders and from different types. This feature can be used to enhance document visibility into Sterling.
Furthermore, Sterling could benefit of out-of-the-box ECM's web portal able to implement EDI features like supplier portal.
CMIS is a standard (OASIS) currently supported by the major ECM like FileNet P8.
The request is to create a CMISClient adapter able to store, search and retrieve documents from an ECM (able to provide CMIS interface).
Why CMIS? because it is a standard, it is supported by the most important ECMs
Why not File system? because file system integration is tight to the ECM (eg, the xml index file to provide), it is not scalable, it is not easy to implement a bi-directional integration (eg, ECM has to export documents into file system and name them accurately), it is not easy to implement a query protocol. It provides NO differentiation against the competition.