Send SOAP message with JMS adapter ?

[Former Member]

Hi,

We asked me a question and I did not know / find the answer...

By using JMS Adapter, is it possible to create SOAP message and send them across JMS ?

neither HTTP nor SOAP adapter but JMS...

I will appreciate your feedback, coz I have not an idea.

Regards.

Mickael

PS.: PI 7.0 - SP14

[Shabarish_Nair · Accepted solution]

one idea is to create the SOAP message i.e the SOAP envelope, header and body using a Java or XSLT and then use the JMS adapter to push the payload to the queue.

But why do you need to send a SOAP message via a JMS adapter ???

[Former Member · Accepted solution]

Hi Shabarish,

Why ? I don't know, it's my legacy we ask me that... and compare to me, he should be a JMS specialist...

for your solution, that means we have somehting like that:

JMS Header

JMS Properties

JMS payload which contains a SOAP Enveloppe + SOAP Header + SOAP Body/Payload.

but does that means SOAP is encalpsulate inside a JMS payload, so it should be not reaaly a SOAP.

I know my question is strange, but I find also that the Legacy ask is strange...

Else natively, if I well understood.... with a JMS adapter we do not have SOAP message, but a JMS messages, is not it ?

Thanks

Mickael

[stefan_grube · Accepted solution]

Hi Mickael,

this question is not uncommon. The feature is asked a lot. The point is that there is no standard about SOAP over JMS. That menas that you can of course send a SOAP message over JMS, when you create SOAP envelope by yourself, but the filling of JMS attributes and headers is different in each JMS messenger provider.

When you compare JMS and SOAP: JMS is a transport protocol like HTTP, SOAP describes the message structure.

What you have to do: Provide a SOAP envelope with Java or XSLT mapping, povide JMS header fields with help of dynamic message attributes.

Hope that helps

Stefan

[Shabarish_Nair · Accepted solution]

>

> Hi Shabarish,
> Why ? I don't know, it's my legacy we ask me that... and compare to me, he should be a JMS specialist...
> 
> for your solution, that means we have somehting like that:
> JMS Header
> JMS Properties
> JMS payload which contains a SOAP Enveloppe + SOAP Header + SOAP Body/Payload.
> 
> but does that means SOAP is encalpsulate inside a JMS payload, so it should be not reaaly a SOAP.
> 
> I know my question is strange, but I find also that the Legacy ask is strange...
> 
> Else natively, if I well understood.... with a JMS adapter we do not have SOAP message, but a JMS messages, is not it ?
> 
> Thanks
> Mickael

as i had mentioned you can create the soap mesage using a java or xslt.

then regarding the JMS header and stuff the JMS adapter itself creates them. but the payload will be created by you which will be a SOAP message

[Former Member · Accepted solution]

Hi Stefan,

So I have to create the whole SOAP enveloppe manually.... with my litle hands... :-((

I thank to use just a Module in Adapter to convert the body to a SOAP...

According to you, there is no Module, it's what you say ?

Regards.

Mickael

[stefan_grube · Accepted solution]

I think you can use the Axis framework for this.

But I have never done it myself.

Check the SAP note FAQ Axis adapter for JMS.

Regards

Stefn

[former_member200962 · Accepted solution]

You can use MessageTransformBean and then include your XSLT mapping in that.....this will enclose the message within the SOAP envelope...hope that my suggestion is in-line with what Stefan is suggesting

[Former Member · Accepted solution]

Hi,

I would prefer a more standard solution, than to create myself my XSLT Mapping (either in I.R or in CC).

thanks for your suggest.

Mickael

[Former Member · Accepted solution]

Hi Stefan,

To be complete with you, we (Legacy and I) are searching different ways to communicate together:

1. SOAP adapter: classic !

2. SOAP adapter with Axis and eventually with the version SOAP 1.2 (SAP help is good)

3. JMS adapter: standard use.

4. and the last one: JMS adapter with a SOAP message ... which is not really a standard way for PI if I well understood.

To everybody,

Many thanks for your feedbacks, that help me to suggest a way of communication.

Regards.

Mickael

P.S: we have a dozen interfaces which will use the same method, so I prefer the more efficient... the lowest cost.

Edited by: Mickael Huchet on Nov 24, 2009 2:27 PM