Issues with SAP Adapter
subsahuJan 28 2010 — edited Feb 16 2010Hi All
We are trying to call some SAP BAPIs from BPEL and hitting the below errors
Error1:
----------
For 1st BAPI invocation from BPEL console fails with :
The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: javax.resource.spi.EISSystemException: IWAFManagedConnectionFactory:Exception javax.resource.ResourceException: Configuration 'SAPHR' not available for adapter 'SAP'.
; nested exception is:
ORABPEL-12511
Checked the AS_HOME\adapters\application\config\XXXXX\log directory for the JCA logs and error is as below:
Thread[AJPRequestHandler-HTTPThreadGroup-55,5,HTTPThreadGroup] [error] [IWAF JCA] Error in creating IWAFManagedConnection:
java.lang.IllegalArgumentException: Configuration 'SAPHR' not available for adapter 'SAP'.
at com.iwaysoftware.af.container.AdapterManager.checkConfig(AdapterManager.java:450)
at com.iwaysoftware.af.container.AdapterManager.getActivatedAdapter(AdapterManager.java:238)
at com.iwaysoftware.af.container.IWAFContainer.getActivatedAdapter(IWAFContainer.java:491)
...
...
Error2:
---------
For another BAPI invocation from BPEL console fails with:
Thread[AJPRequestHandler-HTTPThreadGroup-55,5,HTTPThreadGroup] [error] [IWAF JCA MySAP] **** Error in parsing the input document.
oracle.xml.parser.v2.XMLParseException: Start of root element expected.
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:205)
at com.iwaysoftware.idom.XmlDocument.parse(XmlDocument.java:120)
at com.iwaysoftware.idom.XmlDocument.setRootXML(XmlDocument.java:77)
at com.ibi.afjca.cci.IWAFInteraction.execProcess(IWAFInteraction.java:195)
..
..
However we are able to get successful response from the JCA Test servlet with same request payloads. Any inputs on what maybe causing the above errors from BPEL console invocation.
Thanks
Subhankar