Troubleshooting
Problem
When SAP Request Node is used to make BAPI outbound call to SAP, the data is not up to date. This could be due to modifications to the RFC/BAPI on SAP end dynamically while the module is running.
Symptom
Any changes to the SAP system that are not picked up by the adapter can indicate this issue is taking place.
Cause
When a first BAPI outbound call is made, the connection is returned to connection pool and reused for subsequent invocations. RFC/BAPI information is cached in the JcoRepository when connection is established first time. So when dynamic logical or parameter changes are made to RFC/BAPI on SAP end while module has already established a connection, the next call with still contain old data.
Resolving The Problem
To access updates to the SAP system, you can either restart them module after making changes or configure the adapter to not cache the connection and create a new connection each time. This can be done as described below:
There is a MFC (Managed Connection Factory) Property called "Reset JCo Client after closing Connection Handle" (parameter name "resetClient") which on setting to TRUE will reset the connection after each call/invocation and clear the JcoRepository, thereby enabling each invocation gets latest updates on SAP.
NOTE: It is a performance overhead to create new connection on each invocation, this property is recommend only in development environment where SAP side development is also in progress.
Further note that:
1. This property is available for BAPI outbound only.
2. Property can be set on the adapter from message broker toolkit. The property cannot be set from mqsi command.
3. Customer needs to set the property and redeploy the module.
There is currently no way to change this config at the moment apart from rebuilding the adapter outbound connection with the check box ticked for "Reset JCo Client after closing Connection handle" under the advanced Connection configuration section in Toolkit EMD wizard and redeploying it to the broker runtime. This setting is not available through the WMB configurable services dialog.
Details about the setting in Infocenter:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.sap.doc/doc/rbp_sap_j2c_conn_fact_props.html
Related tech notes:
- SAP response not constant when using IBM WebSphere Adapter for SAP
- Commit to the SAP system may not happen if reset property is set
Was this topic helpful?
Document Information
Modified date:
21 June 2018
UID
swg21595731