How can the performance of the outbound SAP adapter be improved?
Article ID: KB0089969
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | - |
| Not Applicable | - |
Description
Resolution:
(1) The performance of the adapter would be much better when we use None mode instead of Exploded mode.
In case of "exploded" mode, the received IDoc is expanded and serialized into a hierarchical ActiveEnterprise message structure, called the ActiveEnterprise Message format, using IDoc metadata i.e. The adapter converts the flat structured records into a parent-child tree-structure recursively using IDoc metadata. The time taken by the adapter will depend upon the number of IDOC segments, and multi-level hierarchical structure of the IDOC schema.
"None" mode means that the IDoc message is processed in native RFC table format without inclusion of the IDoc metadata. SAP publishes IDOC in native RFC table format which has one control field and data fields. The IDoc data is most efficiently transmitted in this format, because no additional processing is required to expand the IDoc segments and fields. For best performance the decompression (exploding) step is left for the stage when the data is actually consumed. To receive an IDOC in "none" mode, the mapper task in BW should be using the schema "IDOC_INBOUND_ASYNCHRONOUS" found under "/tibco/public/class/ae/SAPAdapter40/classes".
(2) We can improve the performance on outbound side by publishing only the required fields. Most of the fields might not be relevant and these would have blank values. So, by filtering these fields (use IDoc Filtering feature), we can publish only the used fields.
(3) Please use multithreaded outbound adapter
(4) On outbound side, use multiple program ids (add two connections under ‘R3Connections’ folder and use two different program ids for the same gateway.
(1) The performance of the adapter would be much better when we use None mode instead of Exploded mode.
In case of "exploded" mode, the received IDoc is expanded and serialized into a hierarchical ActiveEnterprise message structure, called the ActiveEnterprise Message format, using IDoc metadata i.e. The adapter converts the flat structured records into a parent-child tree-structure recursively using IDoc metadata. The time taken by the adapter will depend upon the number of IDOC segments, and multi-level hierarchical structure of the IDOC schema.
"None" mode means that the IDoc message is processed in native RFC table format without inclusion of the IDoc metadata. SAP publishes IDOC in native RFC table format which has one control field and data fields. The IDoc data is most efficiently transmitted in this format, because no additional processing is required to expand the IDoc segments and fields. For best performance the decompression (exploding) step is left for the stage when the data is actually consumed. To receive an IDOC in "none" mode, the mapper task in BW should be using the schema "IDOC_INBOUND_ASYNCHRONOUS" found under "/tibco/public/class/ae/SAPAdapter40/classes".
(2) We can improve the performance on outbound side by publishing only the required fields. Most of the fields might not be relevant and these would have blank values. So, by filtering these fields (use IDoc Filtering feature), we can publish only the used fields.
(3) Please use multithreaded outbound adapter
(4) On outbound side, use multiple program ids (add two connections under ‘R3Connections’ folder and use two different program ids for the same gateway.
Issue/Introduction
How can the performance of the outbound SAP adapter be improved?
Feedback
Yes
No
Powered by
