Error - HTTP call to IS unsupported in AEX case

[former_member226695]

Hello Everyone,

We are on SAP PO 7.4 single stack.

We are getting below error in NWA message monitor when trying to send message from BPM to PI.

Information	Java proxy runtime (JPR) is transferring the request message to the messaging System
Information	JPR received "SAP_BPM_Service" as user
Information	Application attempting to send an XI message asynchronously using connection JPR
Information	Trying to put the message into the send queue
Information	The message was successfully retrieved from the send queue
Information	JPR transferred the request message to the messaging system successfully
Information	Message successfully put into the queue
Information	The application sent the message asynchronously using connection JPR. Returning to application
Error	Transmitting the message to endpoint http://<PISERVERHOST>:50000/XISOAPAdapter/MessageServlet using connection JPR failed, due to: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: HTTP call to IS unsupported in AEX case.
Information	Message status set to DLNG
Error	Message status set to NDLV

Based on some research, i tried below approach:

>>>>http://<server>:<port>/nwa > “Configuration” > “Infrastructure” > “Java System Properties” > Select the service “XPI Service: AII Config Service” > The property “com.sap.aii.ibrep.core.usage_type” was be set to “AEX” >>>> When we have changed it to "", there are other issues popping up in PI.

Does anyone know what we are missing?

Thanks,

Sai

[former_member607993]

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

Also Adding on, check the Service reference in BPM is having the correct sender business component under Custom properties. Under service reference details you need to validate the port type name and port type namespace and same is matching with the Integrated configuration Sender.

Thanks and Stay Safe!