Query in PI7.1 Service Interface

[rajasekhar_reddy14]

Hi Friends,

I recently started working on PI7.1, its really good compare PI7.0 and XI 3.0.

Now my query is when i am creating service interface(message interface) i found some new options added.

can anyone explaina about

1) Interface Pattern its having different options Stateless , statefull , TU&CC and Stateless(XI 3.0 Compatible.

2) Operation Pattern its having different options commit,roll back,confirm,compensate,tentavi update

please explain when we will use pattern and different types.

Thanks

Raj

[former_member556412 · Accepted solution]

Hi,

When referring to stateless communication, this is a type of communication in which the messaging runtime does not support the saving of a status

of a message at the provider once the messaging runtime has completed the message exchange successfully.

In contrast, when we refer to stateful communication, this is a type of communication in which the messaging runtime does support the saving of a

status at the provider once the messaging runtime has completed the message exchange successfully.

Note that the messaging runtime can explicitly support or not support such a procedure. If the messaging runtime supports stateful communication,

the application programmer can use the corresponding methods of the messaging runtime.

Furthermore, when talking about interface patterns of a service interface, these terms (stateless and stateful) relate to the state at the provider and

not on the Integration Server (in the case of enhanced communication). Therefore, when selecting a stateless interface pattern you can still enhance

the communication using the Integration Server to include the execution of a stateful integration process that permits message correlation. So this is

to say that these terms are not to be confused when the Integration Server is involved in mediated communication, especially when a stateless

interface pattern and a stateful integration process (e.g. using message correlation) is used in the same scenario.

In terms of how an interface pattern is related to which runtime is used, the stateless (XI 3.0-compatible) pattern uses the XI runtime via the XI

adapter and the rest of the interface patterns (stateless, stateful, and tu&c/c) use the web service runtime (and WS adapter in mediated scenarios).

Note that the stateful interface pattern is never supported in mediated scenarios via the Integration Server.

Finally, the selected interface pattern determines how an application developer programs communication in the back end, thus the interface pattern is

tightly coupled to the application communication. If you change the interface pattern, the application program in the back end must also be changed.

For example, this applies if the interface pattern is changed from Stateless (XI 3.0-Compatible) to Stateless, and for any other interface pattern

change.

Tentative Update & Confirm/Compensate (TU&C/C)

Reliable means to make synchronous update calls

Single or multiple update calls treated as one transaction

Based on guaranteed delivery concept/mechanism for asynchronous messages

Requires at least three messages:

one or more for the Tentative Update calls (synchronous)

exactly one Compensate (asynchronous)

exactly one Confirm (asynchronous)

additional Normal operations can be added (asynchronous or synchronous)

Synchronous update calls are tentatively recorded until one of either Confirm

(COMMIT) or Compensate (ROLLBACK) message is finally received.

[rajasekhar_reddy14]

thanks u guys

[sunil_singh13]

Hi Raj,

Interface Pattern its having different options Stateless , statefull , TU&CC and Stateless(XI 3.0 Compatible.

Stateless : Status of message is not persisted in IE applicable for synch and asynch transfer.

statefull : Status of message is persisted in IE applicable for synch transfer

TU&CC : transitive update compansate and confirm enables the feature of assured delivery for synch scenarios (which was only in case of asynch scenario)

XI3.0 comapatible : For backword compatibility with PI7.0 and XI 3.0.

Operation patterns depends on Interface pattern.

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0ed3b8c-698c-2a10-fbaf-b1df0c82...

you can also take help of SAP Help

thanks

Sunil Singh

[former_member187563]

hi,

For detailed explanation of these things you search sdn with pi 7.1 as keywords you will get all the docs.

these docs will be helpful:

Mostly we go for stateless interface pattern only,others are used in rare cases.

For interface pattern:

http://help.sap.com/saphelp_nwesrce/helpdata/en/11/e8179b247e4720882512a04041491d/frameset.htm

/people/daniel.bianchin/blog/2007/12/19/all-you-wanted-to-know-about-sap-netweaver-pi-71-and-more

For TU&C/C

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00ffdb4d-e869-2a10-7688-891d7eea...

regards,

ujjwal kumar