Oracle B2B Design patterns

• B2B Gate way(Async): Use B2B as a gateway for all trading partner integration. Gateway solution should persist data in EIS( using File,DB, JMS) and B2B processing system can take it further.
• Fault tolerant
• Increase Reuse
• Extendable
• Guaranteed delivery can be designed
• Scalable
• Time to market

• B2B processing hub(Async): Will take care of end-to-end processing of B2B messages
• Handles each message uniquely
• Would require complex error handling mechanism
• Single point of failure

• B2B Message forwarding(Async): Combination of B2B Gateway and Processing system; B2B gateway should work as explained above however B2B processing should be design to handle further processing of B2B message.
• Moduler
• Extendable
• Scalable 
• Reusable  
• Time to market

• Orchestration: Is similar to B2B processing hub but it should be sync
• Extend B2B processing beyond EDI
• Fault and error handling
• Reusable
• Moduler

• Gateway+orchestration

• B2B Translator: Use of B2B is limited to translating the EDI's.

• B2B Poller: Advance File adapter(poll file and parse it to XML).

Known issues with B2B: 

• De-batch the EDI and in some cases requirement can be to process whole batch, in such cases there aggregator component.
• Out of box XML translation(Sync), it is very handy however again it processes only one EDI txn at one time.
• B2B can not be used as webservice.