SystemAck in integrated configuration

[Former Member]

Hello all.

I have configured an integrated configuration for a proxy -> soap scenario.

The sender adapter - is SOAP with XI 3.0 protocol.

in the section: HTTP Destination (from NWA) - I have written the ECC HTTP destination

(defined with url: http://<ecc server>:8000/sap/XI/engine/?type=entry )

The messages go out ok, but when I look in the ECC - the proxy doesn't get a system ack.

When I look in the message monitoring in the PI - I can see the SystemAck in successful, and in Transport part it says:

Loopback - so it seems that the ack is not being sent out of the PI.

Is there anything else to configure to make the ack to be sent back to the ECC?

Any help will be appreciated.

[former_member184681 · Accepted solution]

Hi,

Did you request this acknowledgement while calling the proxy from the backend system? This is a prerequisite to receiving it there. See an example of how to do it here:

http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm

Also, see section 5. Limitation of this document below - it says that acks are not supported by ICO.

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b

However, I remember setting it up once and acks were sometimes sent properly. In particular, System OK acks were sent. But when an error occurred during mapping, no ack reached the backend system.

Hope this helps,

Greg

[Former Member · Accepted solution]

first of all - thanks for the quick reply.

Venkata - I can't really understand the connection to my scenario.

The one mentioned is CRM -> ECC with BDOC. my case is ECC -> PI -> WS with soap.

Greg - The proxy is asking for systems ack automatically. I have checked this in the ReliableMessaging part of the soap header in ECC

about the limitations - they are relevant to PI 7.11, but are they also relevant to PI 7.3?

also - there is a note mentioned there: "NOTE 1329319 SOAP adapter in XI 3.0 mode does not return a system"

it says what need to be configured in order that the soap sender will be able to return the ack.

In PI 7.3 - it is configured automatically when creating the soap sender adapter.

of course - if the message doesn't get to the receiver adapter - there will be no ack (it is only generated by the receiver adapter - otherwise it will be meaningless)

Please - any other information about this will be welcome.

[Former Member · Accepted solution]

I did some more digging in the rwb - and found this in the message monitoring of the ack message:

this was in the message content:

<sap:Info>localejbs/sap.com/com.sap.aii.af.soapadapter/SOAPAckHandler</sap:Info>

this was in the audit log:

Message was successfully transmitted to endpoint <local> using connection SOAP_http://sap.com/xi/XI/System

it seems it uses an adaptermodule named: SOAPAckHandler

also - it seems that it indeed manage to send the ack - but the endpoint is <local> instead of the ECC.

Anyone know of a parameter for the adapter module to change this?

or maybe my HTTP connection in the soap sender adapter is wrong?

[Former Member · Accepted solution]

Hi Imanuel,

Did you ever find a solution to this problem? Cause guess what: I am having the same problem.

Kind regards,

Emil

[Former Member · Accepted solution]

Hello.

The problem was that I also used split message (2 receivers at the end)

When I use only one receiver - the ack returns ok now.

Is this is your situation as well?

[Former Member · Accepted solution]

Hi Imanuel,

Thanks for replying. Unfortunately, that is not my case. I only have a single receiver, but no tech ack is returned to ECC. I use ftp adapter, but I have also tested against a SOAP adapter. Neither seems to work. I assume you did an async ES Proxy Service -> SOAP async service using ICO.

Any special config besides that? I followed the guide mentioned by Grzegorz, adding a couple of module configuration parameters (ignoreDuplicate and generateSysAck) - otherwise the sceario is straigh forward. Specified the http destination maintained in NWA, which I gave same parameters as a normal proxy http connection in abap.

Regards,

Emil

[Former Member · Accepted solution]

I'm not sure if the following step was necessary, but I did it for some reason...

I have created a channel called: Ack_ECC (it is important that it will start with Ack - with capital A)

The HTTP Destination is defined in SM59 of the PI (I assume you have dual stack)

Try to define those objects and retry your scenario.

Otherwise consult SAP - you might need to install an SP.

[Former Member · Accepted solution]

Thanks for the screenprints. We are using dual stack, but I was hoping to get rid of all dependencies to the ABAP stack. Either way, it is still not working after following your set up.

I do get a nice log in the receiver channel:

but nothing is returned to the sending proxy/SOAP.

I will just have to keep looking.

Thanks for your help.

Emil

[Former Member · Accepted solution]

Thanks for the screenprints. We are using dual stack, but I was hoping to get rid of all dependencies to the ABAP stack. Either way, it is still not working after following your set up.

I do get a nice log in the receiver channel:

but nothing is returned to the sending proxy/SOAP.

I will just have to keep looking.

Thanks for your help.

Emil

[Former Member · Accepted solution]

Thanks for the screenprints. We are using dual stack, but I was hoping to get rid of all dependencies to the ABAP stack. Either way, it is still not working after following your set up.

I do get a nice log in the receiver channel:

but nothing is returned to the sending proxy/SOAP.

I will just have to keep looking.

Thanks for your help.

Emil

[Former Member · Accepted solution]

Thanks for the screenprints. We are using dual stack, but I was hoping to get rid of all dependencies to the ABAP stack. Either way, it is still not working after following your set up.

I do get a nice log in the receiver channel:

but nothing is returned to the sending proxy/SOAP.

I will just have to keep looking.

Thanks for your help.

Emil

[Former Member · Accepted solution]

Thanks for the screenprints. We are using dual stack, but I was hoping to get rid of all dependencies to the ABAP stack. Either way, it is still not working after following your set up.

I do get a nice log in the receiver channel:

but nothing is returned to the sending proxy/SOAP.

I will just have to keep looking.

Thanks for your help.

Emil

[Former Member · Accepted solution]

Thanks for the screenprints. We are using dual stack, but I was hoping to get rid of all dependencies to the ABAP stack. Either way, it is still not working after following your set up.

I do get a nice log in the receiver channel: "SOAP Ack Sent"

but nothing is returned to the sending ECC proxy/SOAP.

I will just have to keep looking.

Thanks for your help.

Emil

[Former Member]

Hi,

Check this thread.[;

Regards,

Venkata S Pagolu