ResponseOneway bean

[Former Member]

Hi All,

I am working on a IDoc_AAE-->Webservice-->IDoc_AAE interface using Request Response bean and Response oneway bean.

Getting below error in Sender IDoc channel -

Processing error =  while trying to invoke the method com.sap.aii.af.service.cpa.Channel.getChannelName() of an object loaded from local variable "Channel"

Same configuration is working when File Receiver channel is used instead of IDoc_AAE channel.

Thanks,

Jyothsna

[gagandeep_batra · Accepted solution]

Hi Jyothsna,

check the following blog:

and

try :

adapterType = IDoc_AAE

adapterNamespace = http://sap.com/xi/XI/System

if it work ok other wise

other option is you can check create one more ICO scenario and provide the sender as your receiver system of first scenario with dummy sender adapter and receiver as sender of first scenario and provide your IDOC adapter

Regards

Gagan

[Former Member · Accepted solution]

Thanks Gagan for quick response .

I followed the blog you mentioned ,and adapterType,adapteNamespace parameters are also provided.

And coming to your second suggestion,What should be the sender interface for 2nd ICO? (my reciever interface is synchronous proxy interface)

Here i believe modules should be added in Receiver channel.Am i right?

Any idea if "replaceInterface" parameter is a valid one in ResponseOneway bean for SAP PI 7.4 .Though i dont see this parameter in help.sap.com ,i could find this at http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/904db720-042f-3010-b6ba-e62a4192b...

Regards,

Jyothsna

[Former Member]

Hi,

Did you tried configuring the Modules at the receiver channel and checked whether it worked..

Actually configuring the Modules at the receiver channel has lot of benefits compared to the configuring at the sender level esp.. for the Async-Sync communications..

Here all you need is to configure the two ICO scenarios and have to select virtual receiver option while creating the second ICO and sender adapter can be dummy type...

Check the below for more details on this..

http://scn.sap.com/docs/DOC-34624

search SDN if yours is Sync/Async scenario there is a similar guide also..

HTH

Rajesh

[Former Member]

Hi Jyothsna,

I hope you are attaching the modules to the receiver SOAP adapter. Just a quick question regarding your statement,

"Same configuration is working when File Receiver channel is used instead of IDoc_AAE channel"\

What business system you used for File Receiver adapter. I hope that was different than the IDOC_AAE one right.

Regards

[Former Member]

Hi,

I am attching the modules to Sender IDoc channel not reciever.I used the same business system for IDoc and File.

Should i have to correct something here?

Thanks,

Jyothsna

[former_member194741]

Hi Jyoths,

         Your error seems to be in the commn channel created to get the response back is not working fine,In addition to that,want to know  whether u r using Bus.service or Bus.system in the sender side for Idoc communication.

And u mentioned its working for Idoc_AAE-----WS----FILE right, if u replace the File adapter by IDOC_AAE its not working,so it means may be the receiver idoc adapter cant able to determine the Receiver service or system,.so plz check that config.

  Regards,

karthick

[Former Member]

Hi Karthick,

I am using Bus.System for IDoc communication.

Created a file channel under same business system and used it in Response oneway bean.This is working absolutely fine.

The idoc receiver channel which i am using in module is used by other interfaces as well ,and they are working.So i dont see any issue in the channel configuartion.

Any other pointers please.

Thanks,

Jyothsna

[former_member194741]

Hi Jyothsna,

Please refer to my blog which done for JDBC

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/12/04/jdbc-to-jdbc-synchronous-scenario...

and I had shared the Audit log in that, likewise can you run your interface and check in RWB for ur sender IDOC_AAE, receiver SOAP & in particularly share the receiver IDOC_AAE log,so that we can get into depth.

Thanks,

Karthick