on 02-08-2016 1:55 PM
We're currently using AIF in several inbound processes where we are taking anywhere from 1 to 100 records per run and sending them through AIF several times per day and everything is working well.
However, we are considering using AIF for a very important, high volume process - let's say 15,000 transactions per day.
Does anyone have experience using AIF for high volume processes who can comment?
thanks.
Hi Robert,
we uses web services as interface technology. We identified the problem that AIF starts in standard for every received message a single background job to process each message. The huge number of background jobs (more than 100K per day for one interface) could be reduced by run packages of messages in one background job with AIF runtime configuration. Please have a look into the document by David .
I heart from systems/companies which process more than 1 million messages per day. So it is more a question of sizing.
Kind regards
Christoph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Christoph, apparently I had seen that document on Delayed Processing before - I had 2 posts in the comments section just about a month ago!!
However, I also appreciate your input on how you're using AIF via web services. yes, triggering a job each time a message comes through would kill our Basis team.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.