How to improve the performance of subscription service of TIBCO ActiveMatrix Adapter for SAP while publishing iDocs from TIBCO end to SAP.
Article ID: KB0091543
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | - |
| Not Applicable | - |
Description
Resolution:
Description:
===========
In some situations, the subscription service of TIBCO ActiveMatrix Adapter for SAP is required to publish the iDocs from TIBCO end to SAP faster.
Environment:
===========
TIBCO ActiveMatrix Adapter for SAP 5.x, 6.x.
Resolution:
===========
Changing the inbound parameters to ‘Trigger by background program’ on Partner Profile on SAP (by Transaction Code ‘BD82’ or ‘WE20’).
When the background processing is enabled, Adapter will not wait for handling the inbound iDocs finished by SAP and the invocation of the RFC which is used for publishing the iDocs will be returned instantly when the iDocs are published to SAP.
When above setting takes effect, no time spent would be observed between log entry ‘AER3-000094’ and ‘AER3-000095’ in adapter log which would have saved the time for publishing inbound iDocs to SAP.
On the SAP end, the inbound IDocs and IDoc packets are first saved in the database. IDoc packets are split into single IDocs beforehand. The program RBDAPP01 later releases the saved IDocs for processing. Single IDocs will be put into packets and then processed.
Description:
===========
In some situations, the subscription service of TIBCO ActiveMatrix Adapter for SAP is required to publish the iDocs from TIBCO end to SAP faster.
Environment:
===========
TIBCO ActiveMatrix Adapter for SAP 5.x, 6.x.
Resolution:
===========
Changing the inbound parameters to ‘Trigger by background program’ on Partner Profile on SAP (by Transaction Code ‘BD82’ or ‘WE20’).
When the background processing is enabled, Adapter will not wait for handling the inbound iDocs finished by SAP and the invocation of the RFC which is used for publishing the iDocs will be returned instantly when the iDocs are published to SAP.
When above setting takes effect, no time spent would be observed between log entry ‘AER3-000094’ and ‘AER3-000095’ in adapter log which would have saved the time for publishing inbound iDocs to SAP.
On the SAP end, the inbound IDocs and IDoc packets are first saved in the database. IDoc packets are split into single IDocs beforehand. The program RBDAPP01 later releases the saved IDocs for processing. Single IDocs will be put into packets and then processed.
Issue/Introduction
How to improve the performance of subscription service of TIBCO ActiveMatrix Adapter for SAP while publishing iDocs from TIBCO end to SAP.
Feedback
Yes
No
Powered by
