Generating proxy from Service Interface with TUCC interface pattern

[Former Member]

Hello experts,

I have to implement a soap2proxy scenario, so from sproxy I generated an inbound proxy based on a service interface with TUCC interface pattern and three operations (tentative Update, Confirm and Compensate). But I can’t see differencies from a Service Interface with Stateless interface pattern and normal operation pattern. Is there anything I should set from sproxy to make this scenario work?

From the ESR side I created two service interfaces, both with the TUCC interface pattern and three operations (Tentative Update, Confirm and Compensate) for each SI. Is that correct to configure a TUCC based scenario?

Can anybody help out?

Thanks.

FDC

[venkatanarayana_vagu]

Stateless patterns can be implemented either as Integration Flows on PI (AEX) or as processes in BPM. As a general guideline, stateless patterns are best implemented as Integration Flows on AEX. If you are going for the pattern specific it is better for stateless / statefull based on the pattern recommended configuration.

refer this link: