on 06-29-2015 4:02 PM
Hi,
I am trying to configure ODATA receiver adapter channel on PI 7.4 SP 11 environment (Java -Single Stack). Message processing on that channel is throwing following error.
Message could not be forwarded permantely to the JCA adapter. Reason:
Message could not be forwarded to the JCA adapter. Reason: Permanent error: Adapter call failed. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException: |
JPR failed to transfer the request message to the messaging system. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException:
I followed the instructions from SCN Doc-PI.SFSF Integration.DOC – SFSF OData Dynamic query “$filter" clause at runtime.
I am passing below structure as request data for ODATA receiver channel and have set property dynamicQuery to true.
<ns1:QueryStringOptions xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://sap.com/xi/XI/OData">
<top>0</top>
<skip>0</skip>
<filter>$filter=firstName eq 'yyyyyy'</filter>
</ns1:QueryStringOptions>
Can you please tell me what could be wrong here..
Thanks
-Pradeep
Hi,
please I'm having the same issue!!! How did you solve it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Experts,
I have a scenario using Odata receiver adpater and I get the following error in CC monitoring. I get Bad Request Error as below. I use a dummy file sender which is polled at every 60 secs and this eventually calls the Odata Receiver. I want to use a sync/async bridge to write the data to file when Odata adapater gives me the data.
However its failing in the first step of getting data from Odata adapter.
Message could not be forwarded permantely to the JCA adapter. Reason: {0}
OData call failed.
com.sap.aii.adapter.lib.component.odata.exception.OsciException: 400 : HTTP/1.1 : Bad Request
Message could not be forwarded to the JCA adapter. Reason: Permanent error: Adapter call failed. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException:
Odata Service URL:
https://<host>/sap/c4c/odata/cust/v1/zcustomer/$metadata
address : https://<host>/sap/c4c/odata/cust/v1/zcustomer/CustomerCommonCollection
I have configured the Resource Path usning Ecilipse modeller:
CustomerCommonCollection?$select=ZeitungText,Zeitung,VoordeelmailText,Voordeelmail,VestigingvanoorsprongText,Vestigingvanoorsprong,VestigingsmailText,Vestigingsmail,Uitschrijfdatum,UitnodigingenText,Uitnodigingen,TripolisID,SortingFormattedName,Roepnaam
Modules on adapter:
Regards,
Amber
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
SAP says, url of the OData service has to be entered in the address field. refer below.
Configuring OData Adapter Receiver Channel - Creating HTTP Destination - SAP Library
the resource path you mentioned is the key here. as entity and field mentioned in the resource path, corresponding data will be fetched by the adapter.
reg, avinash
Hi Avinash,
I'm a step further now. I have the below error now after removing "CustomerCommonCollection" from the address field.
The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request. Please check the NWA logs for more details.',8:true}" ct="TV" bMarkedAsFocussed="true" bResetTabIndex="true"Error during message processing: <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code>00145E5B1CC71EE19AA7192A1CD80294</code><message xml:lang="en">The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request</message></error>. Please check the NWA logs for more details.
Hello,
Exit module is standard one, its not recommended to remove it.
at last try, I would suggest to play around with Address field by doing trial and error method.
Try different url text in 'Address field',
e.g. Keept http://host:port/xxxxxx keep host and port name unchanged keeping trying url with first / and second / and third /
reg, avin
I think, adapter should have handles 404 response gracefully instead of throwing exception. Do you know whether there are any new releases in near feature?
Thanks again for all your responses.
-Pradeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Avinash,
Our BASIS updated the ODATA version to latest service pack and dynamic filters seems to work. However, When ODATA service returns HTTP return code of 404, adapter is not able to handle it properly.
Using REST cleint when we try ODATA service, service returns following reponse.
For the same request ODATA adapter is not able handle the error response.
In the developer trace log i see below error
httpResponse Code : 404 : Not Found : HTTP/1.1: ReasonPhrase :Not Found,No Business Partners found for the specified search criteria. 404 : Not Found : HTTP/1.1 : Not Found
java.util.NoSuchElementException
[EXCEPTION]
com.sap.aii.adapter.odata.ra.xi.util.OdataAdapterException: OData call failed.
at com.sap.aii.adapter.odata.ra.xi.api.ODataAPICaller.processRequest(ODataAPICaller.java:190)
at com.sap.aii.adapter.odata.ra.xi.api.ODataAPICaller.processRequest(ODataAP...
Do you know how to handle both success and error response. looks like odata adapter not able to handle the errors.
Thanks again..
-Pradeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pradeep,
>> We are using the latest Connectivity add on 1.0. SP02. Is there release newer than this? YES.
AFAIK - Additional settings is not supported in ODATA adapter. its supports only in sfsf odata adapter.
I would suggest :
Configure the your resource path (refer the blog :
use kepler instead of Juno, you can configure resource path for top, skip, filter, use it in the channel.
p.s : Sending top skip value in a payload doesn't supported in ODATA adapter.
Hope this helps.
Please update the finding.
reg, avinash
we have ODATA adapter available in PO 7.4 SP11 please try with ODATA and see if it works.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
May I know why for you refering sfsf odata adapter configuration for ODATA adapter configuration?
reg, avinash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.