Integration

Hi All,

Here is my requirement :

Our org. receives EDI documents in various versions of EDIFact/X12 from Customers/Vendors.
Our internal systems only accept EDI X12 3060 in NATIVE format.

So before sending it to internal systems, I need to convert all the incoming documents to EDI X12 3060.

Here are the options I know to do this :
Use Case : Customer sends EDI X12 850 in 4010. Need to convert it to X12 850 3060

1. Use Mapbuilder - to create EDI Mappings
Create 4010_850.ecs
Create 3060_850.ecs
Create MAP_4010_3060.ems

Invoke the map in the agreement using Callout. Use XEngine API to invoke the map. Configure XESelectorConfig-generic.xml to invoke correct map depending on the document types.
The 3060 document is available in the APP Message. Forward this message to target system.


2. Use SOA Composite
Accept the B2B document in 4010 format in SOA Composite using B2B Receive
Use 4010, 3060 XSD files created using B2B Document editor to create XSLT map.
Do the mapping in the BPEL Process.
Convert the document to native format (Not sure how, probably using FileAdapter)
Send the document to Target System.

I'm planning to create single SOA Composite for all the incoming messages.
Accept the doc...use some configuration to identify versions and apply appropriate map.
Forward the resulting document to target system.
Not sure how to configure XSLT maps depending on the incoming message type/version.

This is what I'm not sure about :
1. I've seen all the tutorials on B2B for building SOA composite. But there is no documentation on how to use Mapbuilder and how/where to invoke ems maps.
2 There is no way to configure mappings for Agreements in B2B. How to handle the situation when Partners in an agreement are using different Standards.
3. I've done a little research on XEngine API and invoking Mapbuilder maps. But doesn't fit in the B2B/SOA architecture easily.

I want everyone's views/ideas on how to handle this situation. Let me know if I'm missing something.
I would assume that this is a pretty much common requirement and something should be available out of the box.

Thanks,
Ambadas.