Share
ReportHi there!
We have a customer that have quite a lot AIF outbound messages to be processed. Recently the number of msg's increased and the batch that is set up to process the gateway send service is not performing as expected. The msg's in the queue grow and grow during peak times.
We have the following batch setup:
2 batches are set up for the AIF outbound process.
- 1 for the processing service
- 1 for the gateway and send service
What did I already try in terms of setup to boost the performance
- I set up another batch for the gateway and send service running on another AOS -> This did only work for a very short time since 1 of these 2 batches hung up. This batch could not be stopped anymore without restarting the AOS (by killing the process). I think there AX 2009 is not designed to set 2 batches up for this process. While the 2 batches were running, the performance was of course much better.
- I started playing around with the Endpoint configurations. I set the outbound property parameter "Limit number of documents" to No --> no difference in the performance. Afterwards I limited it to 500 (default: 1000) --> no difference in the performance.
What questions do I have
- Does anybody have, out of experience, any suggestions on how to optimize the setup in terms of performance optimization? Any help is welcome…
- Do you have an idea how we could enhance the AIF framework in order to get a better performance? Currently I have the following idea: AX does not give any option to set up the gateway (or any other AIF related batch) per AIF Channel. Hence, I am not able to have more than 1 batch set up to handle the gateway. With this approach I would be able to set up a single batch for each channel. Each batch would take only the msg’s of its channel and writes it to the directory.
Thanks in advance!!
*This post is locked for comments
All responses (
Answers (
231,430
