PI 7.1 "stateless" service interfaces prerequisites and limitations

[former_member188019]

are there any prerequisites and limitations for "stateless" Service interfaces.

We are directly implementing PI 7.1, (i.e not upgrading form 7.0 or 3.0).

so for all our service interfaces, shall we safely use tne interface pattern "statelss" instead of "Stateless(xi 3.0 compatible)".

if use the "stateless", are there any addition prerequisites or constraints/limitations.

can we use abap proxies, java proxies, providing webservices via xi, and consuming other webserivces in xi, all adapters, asynch, synch scenarios with "stateless" interface patterns.

In short, are there any things that can be done using "Stateless(xi 3.0 compatible)" and cannot be done using "stateless" interface

are there any specific requirements for using "Stateless(xi 3.0 compatible)" even in newly implemented PI 7.1

thanks in advance,

Madhu.

[former_member200962 · Accepted solution]

When it is an upgrade from 7.0 to 7.1 the default Interface pattern is Stateless (XI 30 Compatible)

Using Stateless Interface Patterns wont cause any harm/ restriction on any of the development.

The only twist will be in the way a condition is specified in the Receiver Determination.

For any Interface pattern (other than Stateless(XI30 Compatible)) you wont be able to see the message structure in the Condition Editor of Receiver Determination. All other functionality (Async, Sync, Proxy) will be available.

In such a case Condition should be specified as shown in this blog: /people/abhishek.salvi/blog/2009/07/15/sap-pi71-receiver-determination-xpath-and-you

Regards,

Abhishek.

[former_member188019]

thanks for your feedback

[former_member200962]

After working on Stateless (XI 30 Compatible) and Stateless Interface Pattern I found the former to have limitations in SAP PI7.1.

Stateless (XI 30 Compatible) cannot be used for Multiple Operations, cannot be used in WS communication (involving WS adapter type in the CC). These limitations are however covered by Stateless pattern

[former_member188019]

thanks, that means, when we directly implement PI 7.1, the recommended approach is to go for "Stateless" Interface Pattern.

it can take care all requirements handled by "Stateless xi 3.0 compatible" and new requirements of using WS adapter type.

thanks,

Madhu.

[former_member200962]

Yes,Stateless Interface pattern implementation should not cause any limitation to any scenario (Async, Sync, BPM, Proxy).

Update:

When a Service Interface is to be included in a BPM, then you need to have only Stateless (XI30 Compatible) or Stateless Interface Pattern....may not be related to your Q ....but just FYI.

Regards,

Abhishek.

Edited by: abhishek salvi on Aug 11, 2009 11:07 AM