cancel
Showing results for 
Search instead for 
Did you mean: 

Messages not getting processed from PI to BPM...HTTP call to IS unsupported in AEX case

former_member187447
Participant
0 Kudos

Hi Folks

I have seen couple of discussions on the same but none of them have proper resolutions suggested. The messages were passing into BPM earlier but all of a sudden I am starting to get these errors and the messages are failing before it could get into BPM.

Transmitting the message to endpoint http://XXXXXXXX:XXXX/XISOAPAdapter/MessageServlet using connection JPR failed, due to: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: HTTP call to IS unsupported in AEX case.

Regards

kalyan.

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member607993
Contributor
0 Kudos

kalyan.golla

In PI AEX you need to check if the Integrated configuration is activated for the failing automated activity which is XI based service type. If its not activated it throws a messaging exception 'HTTP call to IS unsupported in AEX case'.

Adding on, also check the Service reference in BPM is having the right sender business component under custom properties. Validate the port type name and port type namespace is matching with the Integrated configuration sender.

Thanks!

Former Member
0 Kudos

Hi Kalyan,

Did you refer the below discussions:

KIndly check these and revert back if installation is done as PO.

Regards,

Anurag

former_member187447
Participant
0 Kudos

We have PO Java stack only installation. and I have already checked "Error - HTTP call to IS unsupported in AEX case". I do see XPI (= full PI) in NWA for Usage _type property of XPI Service: All Config

Regards

Kalyan.

former_member187447
Participant
0 Kudos

Sorry, Actually the message processed through BPM but it is failing with the error at the receiver side from BPM to PI. I have verified the channel message protocol to be XI 3.0 and the interface configured is outbound interface.

Regards

kalyan.

former_member187447
Participant
0 Kudos

I got the issue resolved by maintaining the Party for the business Component. This party has to be configured along with the business component in the service reference of the outbound interface of the BPM. Earlier it used to work without the Party but now with the latest SP for 7.31 or 7.4 it is not working without configuring it.