JMS transport protocol instead of HTTP

[Former Member]

Hi Experts,

Please suggest me how to do the below scenario with PI.

1. In the Client Business service(webservice), I have to use JMS transport protocol instead of HTTP. ( Usually, we have only HTTP transport protocol for webservice scenario.)

This is for Asynchronous scenario.

3. Ensure that XI uses queues behind the scenes to persist messages to promote message reliability.

4. If the platform supports WS-ReliableMessaging, create WS-ReliableMessaging policy and apply it to the XI endpoint used by the clients to connect to the service.

This is mainly needed to implement Message Reliability from PI. Please share your suggestions.

Regards

Sara

[Former Member · Accepted solution]

Hi sara

Ensure that XI uses queues behind the scenes to persist messages to promote message reliability.

For async message , persistece is on by default. so u dont have to worry about this point

regarrds

krishna

[prateek]

WS-ReliableMessaging wont be supported in PI 7.0. So the last requirement cant be met without PI 7.1

Regards,

Prateek

[Former Member]

Could you please provide some features to support Message Reliability from PI ?

Regards

Sara

[prateek]

I dont think this functionality can be supported in PI 7.0

Regards,

Prateek

[Former Member]

Hi

Usually, we have only HTTP transport protocol for webservice scenario.)

for a webservice scenario, we use SOAP adapter

regards

krishna