cancel
Showing results for 
Search instead for 
Did you mean: 

AAE is not working in PI7.3

Former Member
0 Kudos

Hi All,

I am working on PI 7.3 which
has both java and abap stack, my scenario is synchronous Soap-PI-Soap…

We have sender  portal and receiver ECC(synch proxies). There
is no mapping transformation and we want to use AAE.

If we don’t use AAE and go with the regular configuration as
creating sender receiver agreement and interface and receiver determination…
taking XI adapter at receiver side, then things are working fine. Messages are
successfully flowing.

Instead that if we use AAE, what additional configurations
are required? I have created a G type connection taking the path prefix as “/XISOAPAdapter/MessageServlet?ximessage=true”
and used the same in SXMB_ADM.

I can see failed
messages in PI MONI, with error status as “RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC”As there are not much to do in ICO and I have cross checked
everything from configuration point of view its perfect, there is something
else where I am missing….

I have used option “No operation Specific” in interface
determination as we are not using any mapping.

Is there any configuration required at PI NWA related to JCO
RFC provider? Or any destination needs to be maintained there?

Please suggest.

Thanks

Shivanjali

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi All,

Thanks for your support.

My issue is resolved.

I configured the following property in the XI Service.

1. Open nwa > Configuration > Infrastructure > Java System Properties

2. Selectt Services tab and Filter for 'XPI Adapter: XI'

3. In the properties tab search for 'xiadapter.version.minor'

4. Change the value to 0

After this i re-created the scenerio.

Thanks

Shivanjali

Answers (3)

Answers (3)

markushardank
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Shivanjali,

there is a nice how to describing your setup (http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef4...). Additionally if you have classical configuration and integrated configuration and you changed the Interface Name for the last one please also consider to change your test case accordingly. I hope that this helps you with your setup. Otherwise more detailled information, what you have configured would be helpful.

best reagards,

Markus

Former Member
0 Kudos

Hi Markus,

I have already done these settings.

I have created a G type and H type RFC destinations as well as done with configuration in sxmb_adm.

Please suggest if I need to make any settings in nwa?

Thanks

Shivanjali

Former Member
0 Kudos

HI,

If u have configured ur scenario as ICO then u will not be able to see ur message in MONI..u have to check in RWB...

Did u followed the same steps provided by markus for ICO configuration.

Let me know what configuration you did apart from what you have mentioned above.

thanks

chirag

Former Member
0 Kudos

Hi Chirag,

I have done the same configurations... I have both java and abap stack... I checked in RWB and there i can find same error saying receiver can't be determined, as well as there is no message at soap receiver channel..

Thanks

Shivanjali

Former Member
0 Kudos

Hi Shivanjali,

Can you pls do dummy changes in the scenario and activate it again also do cache refresh...

Thanks

chirag

Former Member
0 Kudos

Hi Chirag,

Thanks for that comment, It totally slipped from my mind that these messages shold not be in moni....I triggered message from altova spy but getting an error "

com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]"

Any clue for same?

Thanks

Shivanjali

Former Member
0 Kudos

Hi Shivanjali,

It seems that ur getting empty response with exception...did u try with other sample data.

thanks

chirag

Former Member
0 Kudos

Hi Chirag,

No, I am not getting empty response, If I use regular process other than AAE, then response is coming back.

Thanks

Shivanjali

iaki_vila
Active Contributor
0 Kudos

Hi Shivanjali,

In addtion to Sahthi, If you are sure that your ico object is right the problem could be also a cache issue.

1. Try to refresh the sxi_cache

2. Try to refresh cpa cache because is where the  confirguration objects are  stored (http://<host>:<port>/CPACache/refresh?mode=full with PIDIRUSER).

Regards

Former Member
0 Kudos

Hi Inaki,

I have tried this, but no luck...

Regards

Shivanjali

sahithi_moparthi
Contributor
0 Kudos

Hi,

Have you Configured

Create two RFC Providers like

1) SAPSLDAPI_<PI SID>

2) LCRSAPRFC_<PI SID>

in JCo RFC Provider.The same has to be created in the SM59.

If you done the above settings just check SXMSIF Tcode whetehr you have your service interface name or not.

Former Member
0 Kudos

Hi Sahithi,

1) SAPSLDAPI_<PI SID>

2) LCRSAPRFC_<PI SID>

These both are in place as well as i have already done SXMSIF entries..

But things are not working.

Regards

Shivanjali