IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > SAP Software > Troubleshooting and support
Frequently Asked Questions
This section provides you with answers to common questions about WebSphere Adapter for SAP Software.
- How to use the Reset JCO Client?
- What are the mandatory fields while deploying an adapter at the node level?
How to use the Reset JCO Client?
The reset property (Reset the JCO client after closing the connection handle) is used to obtain the latest changes of the ABAP definition (BAPI) dynamically. The changes can be any logical change in the ABAP code or a parameter change in the function module. This property is applicable only for BAPI Outbound modules.
Following are the advantages of using the Reset JCO client feature:
- Obtain the latest changes to the ABAP definition on the SAP system by discarding the cached contents in JCO repository.
- Get the changes of the BAPI definition dynamically, without restarting the adapter.
What are the mandatory fields while deploying an adapter at the node level?
When you deploy the adapter at the node level and manually create the activation specification and the managed connection factory properties ensure that you specify the mandatory fields as indicated below.
For ALE inbound, the following example indicates the mandatory properties that you need to specify in the activation specification properties. You can locate the following properties in the .export file.
<properties> <BONamespace>http://www.ibm.com/xmlns/prod/websphere/j2ca/sap</BONamespace> <applicationServerHost>9.184.167.115applicationServerHost>9.184.167.115> <assuredOnceDelivery>falseassuredOnceDelivery>false> <client>100client>100> <gatewayHost>9.184.167.115gatewayHost>9.184.167.115> <gatewayService>sapgw10gatewayService>sapgw10> <language>ENlanguage>EN> <password>saperp03password>saperp03> <rfcProgramID>TESTRFCSERVERrfcProgramID>TESTRFCSERVER> <systemNumber>10systemNumber>10> <userName>TESTuserName>TEST> </properties>For BAPI inbound, the following example indicates the mandatory properties that you need to specify in the activation specification properties. You can locate the following properties in the .export file.
<properties> <BONamespace>http://www.ibm.com/xmlns/prod/websphere/j2ca/sap</BONamespace> <applicationServerHost>9.184.167.115applicationServerHost>9.184.167.115> <assuredOnceDelivery>falseassuredOnceDelivery>false> <client>100client>100> <gatewayHost>9.184.167.115gatewayHost>9.184.167.115> <gatewayService>sapgw10gatewayService>sapgw10> <language>EN (English)language>EN (English)> <password>saperp02password>saperp02> <rfcProgramID>TESTRFCSERVERrfcProgramID>TESTRFCSERVER> <systemNumber>10systemNumber>10> <userName>TESTuserName>TEST> </properties>For BAPI outbound, the following example indicates the mandatory properties that you need to specify in the activation specification properties. You can locate the following properties in the .import file.
<resourceAdapter> <connection type="com.ibm.j2ca.sap.SAPManagedConnectionFactory" interactionType="com.ibm.j2ca.sap.SAPBapiInteractionSpec"> <properties> <adapterID>001<,adapterID> <applicationServerHost>9.184.167.115applicationServerHost>9.184.167.115> <language>ENlanguage>EN> <password>saperp02password>saperp02> <systemNumber>10M/systemNumber> <userName>TESTuserName>TEST> </properties> </connection>