Troubleshooting
Problem
SAP response is not constant and sometimes even the data value is changed from one request to another when the data should remain the same when using IBM WebSphere Adapter for SAP.
Symptom
SAP response is not constant and sometimes even the data value is changed from one request to another when the data should remain the same when using IBM WebSphere Adapter for SAP. This happens in case of outbound BAPIs.
Cause
When the adapter creates a client connection, some values are retrieved from the SAP system and cached in the connection. When an SAP administrator changes the flows on the SAP side or makes other modifications that causes these values to change; these cached values are not updated on the connection. This is because the Adapter was not designed to handle these sorts of dynamic changes.
A request that goes through a new connection behaves as expected but when the same request goes through an older connection with the old cached values then you see the problem.
Environment
Resolving The Problem
To address this issue SAP adapter implemented the "Reset JCo Client after closing Connection Handle" which invokes the reset method on the JCo client to make sure changes on the SAP EIS are reflected in the client during an outbound transaction. This property is not a required property and by default it is set to false. When the property is set to True, the adapter invokes the reset method on the JCo client to make sure changes on the SAP EIS are reflected in the client during an outbound transaction.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21444760