Posting IDocs in Parallel
This is used for:
When IDocs are processed immediately, all dialog processes on the receiving application system are used for posting. This could block the application server. You cannot distribute inbound IDoc packets among one server group.
An IDoc packet can consist of one or more IDocs. A dialog process to execute the posting function module is started on the application server for every IDoc packet. If the IDoc packet consists of several IDocs and if the posting function module is not capable of mass processing, the ALE layer calls the function module several times in the same dialog process and each time transfers a single IDoc for processing.
Inbound IDoc packets are split into individual IDocs and stored on the database. The program RBDAPP01 transfers the IDocs to the application's posting function module. RBDAPP01 can be run manually from Distribution Administration (ALE), by choosing Periodic processing ® ALE inbound IDocs, then Posting. Alternatively the program can be run in a batch job.
All application servers in a server group can be used in parallel for updating IDocs in the background. There might be only one application server in a server group. If you do not specify a server group, all dialog processes in the local server are used in parallel. This could block the application server.
For mass data it is advantageous to process IDocs in parallel.
You must select the option Parallel posting on the screen Inbound processing of IDocs ready for transfer in the program RBDAPP01.
Specify a server group for parallel updating on several applications.
Because two dialog processes remain unused on every application server in a server group, make sure there are enough dialog processes available on the relevant application server.