Known Issues with EDI and AS2 Performance

 

This topic describes known issues with the performance of BizTalk Server EDI and AS2 solutions.

When you activate EDI or AS2 status reporting, the performance of your system may be affected by the number of messages that status reporting is performed for. When you select the "Store transaction set/payload for reporting" property for either EDI or AS2 processing, the performance of your system may be affected by the size of the messages that status reporting is performed for.

The tables used in the BAMPrimaryImport database for EDI or AS2 status reporting are optimized. No further optimization is required. You can, however, increase the rate at which data from the BAM primary import database is archived by changing the time window for archiving activity instance data in the BAMPrimaryImport database. For more information, see "Archiving Primary Import Database Data" in the BizTalk Server documentation.

Transaction set/payload data is stored in the BizTalkDTADb database. For more information about the performance of this database, see "Understanding DTA Tracking Performance Behavior" in the BizTalk Server documentation.

Performance of your system may also be affected by the degree of status reporting enabled in the configuration of your system. You may be able to improve performance by disabling a specific type of status reporting.

Troubleshooting EDI and AS2 Solutions

Community Additions

ADD
Show: