My scenario is soap-pi- soap axis sync. . with dynamically url generation using soap axis.. end to end scenario is working properly with classical configuration but when I'm using ICO to increase the performance i'm getting error in both request and response.. while testing from rwb if i'm triggering from integration engine->test message then i'm getting error as"no receiver could be determined " and if i'm triggering from adapter engine->test message then i'm getting error as"no receiver agreement found ". My doubt is that can ico support dynamic url generation??
The same axis adapter is working fine with classical configuration ie. by creating determinations and agreements but not with ICO. If it had been problem with axis adapter then it would not have worked in any configuration. As far as i know dynamic configuration is done on abap stack and ICO bypasses abap stack so I have doubt whether this functionality has been added in ICO for PI 7.31 or not... because when I'm triggering payload from rwb->ae->test message i'm getting the following error " Error While Sending Message: Additional error text from response: com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=TESTDB;TS=;AN=MI_ApplicationSummary_Sync;ANS=urn:sce-com:xi:dev:offshore; in the current context [Unknown]. " Please help PI experts..
try by deleting ICO and recreating again....i faced same issue couple of times i tried this approach and it worked for me. we are on PI 7.31 java only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.