Troubleshooting
Problem
The WebSphere Adapter for SAP on version 7.0.0.x is not able to connect to SAP 4.6 when attempting to run the inbound adapter against an SAP Logon Group.
Symptom
The WebSphere Adapter for SAP throws an error message and fails to retrieve a listing of SAP Application Servers for the specified Logon Group. This is caused by the adapter's assumption that SAP has a BAPI called, 'TH_SERVER_LIST' with a structure called, 'LIST_IPV6'. However, the structure 'LIST_IPV6' was not added until a later release of SAP.
See the following stacktrace for the error message:
java.util.NoSuchElementException
at java.util.StringTokenizer.nextToken(StringTokenizer.java:183)
at com.ibm.j2ca.sap.inbound.SAPEventListenerManager.getAppServerInfos(SAPEventListenerManager.java:280)
at com.ibm.j2ca.sap.inbound.SAPEventListenerManager.startEventListeners(SAPEventListenerManager.java:127)
at com.ibm.j2ca.sap.inbound.EndpointManager.addEndpoint(EndpointManager.java:107)
at com.ibm.j2ca.sap.SAPResourceAdapter.endpointActivation(SAPResourceAdapter.java:208)
at com.ibm.broker.adapter.deploy.MbInboundAdapter.start(MbInboundAdapter.java:323)
at com.ibm.broker.adapter.deploy.MbInboundSession.start(MbInboundSession.java:373)
at com.ibm.broker.adapter.nodes.MbAdapterInputNode.onInitialize(MbAdapterInputNode.java:349)
...
Resolving The Problem
This is a known issue that has been resolved in APAR JR38117. This patch allows the adapter to use an alternate mechanism for listing the SAP Application Servers on older SAP releases. To resolve this issue please ensure that your using a build of the WebSphere Adapter for SAP that includes APAR, JR38117. Or contact IBM Support to obtain a build of the SAP Adapter with this APAR included.
See the link below for more details about APAR JR38117.
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21458580