Operation Pattern and WS adapter

[Former Member]

Hi Everybody,

Can anybody plesae help me with the functionalities of the different operation patterns in SAP PI 7.1 while working with Service Interface like- Normal Operation,Commit.compensate,confirm , rollback etc.

I would also like to know about the WS adapter configuration. it would be very helpful if a document in this regard can be provided.

Thanks

Sugata

[rajasekhar_reddy14]

Hi,

WS Adapter is used the communication channel for which you have implemented the adapter type WS, you can configure the communication using Web service runtime.

Depending on whether you want to configure a Web service consumer or Web service provider, use the sender or receiver channel (adapter WS).

refer thsi link

http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/37d74180554c2ce10000000a1553f6/frameset.htm

Regards,

Raj

[rajasekhar_reddy14]

Hi,

Patterns it bit trick point as per my understadning,but What SAP Saying about patters is .

"The interface pattern determines how an application developer programs communication in the back end. If you change the interface pattern, the application program in the back end must also be changed."

Stateless Pattern:

For this interface pattern, the Web service runtime supports point-to-point communication using Web services as well as communication using the Integration Server with the help of the Web service adapter.

Stateful Pattern:

Successive calls use a state at the provider. This interface pattern is only needed for a few special technical scenarios. It does not guarantee a common update of data at the receiver.

You cannot use this interface pattern for enhanced communication using the Integration Server. Only synchronous stateful communication is supported.

TU&C/C Pattern:

An interface pattern that is based on the existing protocols for synchronous and asynchronous communication and enables cross-system ROLLBACKs . This interface pattern supports both point-to-point communication using Web services and communication using the Integration Server with the help of the Web service adapter.

the TU&C/C protocol requires agreement between the consumer and provider, it is only suitable for scenarios within a system landscape and not for cross-company scenarios such as communication with anonymous users using the Internet

Regards,

Raj