Logical vs. physical implementations

Consider the logical vs. physical implementations of Trading Manager. Trading Manager uses Post Offices to define the sources and destinations of data. They are logical sources and destinations that can match the same physical locations. If you have external processes to get the data from partners (either via a VAN or direct connect) you probably define a single Get Post Office in Trading Manager, the default location being:

install_dir\tmgr_vn.n\mmgr\mail.

The performance of the system can be increased if multiple GET Post Offices are defined (instead of one) even if they point to the same ...\mail folder, as long as the GET Post Office name can be easily derived from the input data. Message Manager handles trade link information by GET Post Office and defining multiple GET Post Offices spreads the trade link information, thus reducing overhead. For example, you can use a VAN for most of the inbound EDI traffic, but you can also have numerous other partners that connect via FTP. The best configuration is to create a single GET Post Office for the VAN transmissions and group all of the FTPs into another GET Post Office. There is no advantage in breaking up the transmissions retrieved from a VAN into multiple GET Post Offices since the overhead of breaking up the transmission, in most cases, overshadows the benefits.