Hierarchy
SAP_GWFND (Software Component) SAP Gateway Foundation⤷
OPU-FND-CS (Application Component) IWF Common Services⤷
/IWFND/COS_SHARED_OBJECTS (Package) GW Framework - Shared Objects among Package /IWFND/COS 
Attribute
| Message class |  |
/IWFND/CM_COS | |
| Short Description |  |
SAP NetWeaver Gateway - Common Services | |
| Message Number |  |
250 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20131127 |
Message Text
Help Document
Diagnosis
A parallelization of read entityset to several backend systems in case of Multiple Origin Composition should be used for better performance.
Configuration parameters
- "Minimum Number of Backend Systems" can have following values:
0: No parallelization
n: Parallelization will only be done if at least "n" backend systems are involved.
- The maximum number of parallel backend calls always bases on current resources of the gateway hub system. Additionally, you can use parameter "Maximum Number of Parallel Backend Calls" to limit the use of current system resources. Zero (0) means it only depends on current system resources. Default: 0.
Performance Improvement
In serialization case the duration of a read entityset within a hub system is the sum of all backend's calls. Contrary to this, the total duration in parallel mode is just the maximum duration of all backend calls and a minimal overhead for parallelization.
Parallelization and Skiptoken
If server paging is realized in any backend data provider than the odata consumer will only receive a result up to this backend including a skip token. The next call with this skip token or any other call with a skip token won't be parallelized because the result has to be continued by the backend system returned the skip token before.
System Response
Procedure
Procedure for System Administration
History
| Last changed on/by | |
20141120 | SAP |
| SAP Release Created in | 100 |
