Message failing in call adapter

[Former Member]

Hi Gurus,

I am testing teh interfaces in QA.

When the messages are going to the adapter framework in QA it is calling the wrong url and the message is failing with error status.

http://Devhost:50100/MessagingSystem/receive/AFW/XI and not the right URL http:/QAhost:50100/MessagingSystem/receive/AFW/XI .

The error thrown is

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=QASAPsystem;TS=BS_Mail_Receiver;AN=MI_IB_Mail;ANS=http://access/prototypes/Mailwebservice;</SAP:AdditionalText>

When I restarted teh message then teh message is going to teh right URL in call adapter and processed successfully.

Befor restart the trace is below

<Trace level="3" type="T" />

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">

<Trace level="3" type="T">Channel for adapter engine: RFC</Trace>

- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">

<Trace level="2" type="T">return old values from cache (lock found)</Trace>

<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>

<Trace level="3" type="T">URL = http://dev host:50100/MessagingSystem/receive/AFW/XI</Trace>

<Trace level="3" type="T">User = PIISUSER</Trace>

<Trace level="3" type="T">Cached = X</Trace>

<Trace level="3" type="T">Creating HTTP-client</Trace>

<Trace level="3" type="T">HTTP-client: creation finished</Trace>

<Trace level="3" type="T">Security: Basic authentication</Trace>

<Trace level="3" type="T">Serializing message object...</Trace>

<Trace level="1" type="T">Tuning - AFW_MAXREQUESTCONTENTLENGTH 2000000000</Trace>

<Trace level="1" type="T">HTTP Multipart document length: 15431</Trace>

<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>

<Trace level="1" type="T">HTTP-client: request sent</Trace>

<Trace level="3" type="T">HTTP-client: request sent</Trace>

<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>

<Trace level="1" type="T">HTTP-client: response received</Trace>

<Trace level="3" type="T">HTTP-client: checking status code...</Trace>

<Trace level="1" type="T">HTTP-client: status code = 200</Trace>

<Trace level="3" type="T">Deserializing message object...</Trace>

<Trace level="1" type="T">HTTP-client: parsed & response message object created</Trace>

<Trace level="3" type="T">HTTP-client: closing...</Trace>

</Trace>

</Trace>

</Trace>

After restart the cache

<- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">

<Trace level="2" type="T">old values in cache (no lock found) - start reading from SLD</Trace>

<Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>

<Trace level="2" type="T">Adapter Framework(s) found</Trace>

<Trace level="2" type="T">Service Port(s) found - take first one</Trace>

<Trace level="2" type="T">URL found</Trace>

<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>

<Trace level="3" type="T">URL = http://QAhost:50100/MessagingSystem/receive/AFW/XI</Trace>;

<Trace level="3" type="T">User = PIISUSER</Trace>

<Trace level="3" type="T">Cached =</Trace>

<Trace level="3" type="T">Creating HTTP-client</Trace>

<Trace level="3" type="T">HTTP-client: creation finished</Trace>

<Trace level="3" type="T">Security: Basic authentication</Trace>

<Trace level="3" type="T">Serializing message object...</Trace>

<Trace level="1" type="T">Tuning - AFW_MAXREQUESTCONTENTLENGTH 2000000000</Trace>

<Trace level="1" type="T">HTTP Multipart document length: 15431</Trace>

<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>

<Trace level="1" type="T">HTTP-client: request sent</Trace>

<Trace level="3" type="T">HTTP-client: request sent</Trace>

<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>

<Trace level="1" type="T">HTTP-client: response received</Trace>

<Trace level="3" type="T">HTTP-client: checking status code...</Trace>

<Trace level="1" type="T">HTTP-client: status code = 200</Trace>

<Trace level="3" type="T">Deserializing message object...</Trace>

<Trace level="1" type="T">HTTP-client: parsed & response message object created</Trace>

<Trace level="3" type="T">HTTP-client: closing...</Trace>

</Trace>

CAn you please tell if the adapter cache should be refreshed...Any help appreciated.

Thanks,

Jay.

Edited by: j r saithala on Nov 9, 2011 3:53 PM

[Former Member · Accepted solution]

Hi,

go for full cache refresh in Administration( Integration builder ).

That would solve the problem.

-santosh.

[rodrigoalejandro_pertierr]

hi,

where do you restart the message?manully, i asume if you restart it from the SXI_MONITOR its a async interface.?

also tomake sure, you can regenerate the WSDL from QAS system in the integration directory or just change it manully. to do it, open the source code of the WSDL and go to the bottom of it. Edit the <location> field. only change the host name, port and Business system.

Rgds

RP

Edited by: Rodrigo Alejandro Pertierra on Nov 9, 2011 1:37 PM