General information on Infor Process Automation properties

Configuring some of the properties can take trial and error. For example, the maximum number of processes that you might need to run simultaneously is 5. To ensure that processes would always have the database connections they need, you might initially set the parameter for number of database connections in the pool "pfi.dispatcher.AccessPoolSize" to 10 to 15. If you begin receiving messages that database requests were being rejected, it might indicate that you need to increase the number of connections in the access pool. If, on the other hand, you never receive messages that database requests have been denied but your system performance is not what you want it to be, it might indicate that you have allocated more connections in the AccessPool than you need.

Many of these properties work in conjunction with another parameter. For example, the pfi.dispatcher.KeepAliveTime parameter determines how long to keep an idle thread in the core pool. The pfi.dispatcher.CorePool parameter reads the KeepAliveTime parameter and "kills" threads in the pool that have been in the pool longer than the specified timeframe.