Customers have reported erratic behavior of the BusinessConnect Interior Server at various times.  Some of the symptoms include batching not occurring as scheduled, duplicate files being picked up by the file poller, delays in transaction processing, transaction processing not completing, etc.

A number of these cases have been traced to incorrect configuration of the BC Interior Server engine.  Here is a process for checking out the BusinessConnect configuration.

Customers have reported erratic behavior of the BusinessConnect Interior Server. This article discusses fundamentals to check.

Linux: Red Hat 7.1

1.  Check the basic engine configuration.  The initial setting for the BC engine (thread count of 16 and Max heap size of 640 MB) are adequate for light BC transaction loads, but not for production level loads, especially with the EDI protocol.  The BusinessConnect Interior Server needs at least 2048 MB of heap memory, at least 40 threads, and a thread stack size no greater than 256 KB to operate successfully.  

These changes can be made under the Process Configuration tab of the engine deployment in the Administrator.  If you would like to change these settings without redeploying, opened the deployed engine TRA file, and modify:

Engine.ThreadCount=

for the Interior Server engine thread count,  and 

java.heap.size.max=2048M

to set the maximum heap size.  

In a muiltiple BC engine environment, these changes can be made, and the engines can be restarted in a rolling manner to minimize downtime.

2.  Make sure your BC engines have been performance optimized.  Chapter 4 of the BusinessConnect EDI Protocol User's Guide contains a section called "Tuning for Improved Peformance".   Review that section and implement the changes suggested in that document.

3.  Also, review KB article https://support.tibco.com/s/article/Tibco-KnowledgeArticle-Article-43806 for more suggestions how to optimize the BC engine

 

FTP poller, X12, delete remote, duplicate