on 07-16-2015 4:22 AM
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.
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!
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.
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.
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.
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.