Skip to Content
0
Former Member
Feb 12, 2007 at 10:52 PM

Usage of Abstract Message Interface for non-BPM

27 Views

Hi,

I have a message that I am using as both as an inbound and an outbound for 2 different mapping. I am not using BPM. Is it better to create 2 message interfaces one for outbound and one for inbound or should I just create 1 abstract message interface that can be used in both mappings? What are the advantages and disadvantages of using 2 message interfaces (1 inbound and 1 outbound) against 1 abstract message interface? Would using abstract cause a lot of problems or performance problems in the future?

Thanks in advance.

Regards,

Elbert