Hello

I have a WSP with an MQ as FSH. The backend expect a PUT request, so in the policy I use the 'Method Rewrite' option and set with 'PUT'

When i check in probes, the method is empty, 

is there an impossibility between an mq INPUT and a http out ? I remember, few years ago, i already have this issue and we solved it with this technique below

 <dp:set-request-header name="'X-HTTP-Method-Override'" value="'PUT'"/> this simulate a PUT method, but the backend doesn't accept :)

I also try this command : <dp:set-variable name="'var://service/protocol-method'" value="'PUT'"/> But it doesn't work :

any idea ?

Hi D@viid, I guess you can't change the HTTP method to PUT as the SOAP specification only allows POST and GET. The question now is, why does your backend expect a PUT?

Alternatively, you could use an MPGW service.

Hello

I have a WSP with an MQ as FSH. The backend expect a PUT request, so in the policy I use the 'Method Rewrite' option and set with 'PUT'

When i check in probes, the method is empty, 

is there an impossibility between an mq INPUT and a http out ? I remember, few years ago, i already have this issue and we solved it with this technique below

 <dp:set-request-header name="'X-HTTP-Method-Override'" value="'PUT'"/> this simulate a PUT method, but the backend doesn't accept :)

I also try this command : <dp:set-variable name="'var://service/protocol-method'" value="'PUT'"/> But it doesn't work :

any idea ?

The reason is the backend migrated from soap request to REST request.

So, we keep the consumer call the WSP and i need to map the request to a json format and the new backend is expected a PUT method.

But the problem is not PUT or GET into WSP datapower object, the problem is it's impossible to change method when WSP consume a MQ message as input request

Hi D@viid, I guess you can't change the HTTP method to PUT as the SOAP specification only allows POST and GET. The question now is, why does your backend expect a PUT?

Alternatively, you could use an MPGW service.

Hello

I have a WSP with an MQ as FSH. The backend expect a PUT request, so in the policy I use the 'Method Rewrite' option and set with 'PUT'

When i check in probes, the method is empty, 

is there an impossibility between an mq INPUT and a http out ? I remember, few years ago, i already have this issue and we solved it with this technique below

 <dp:set-request-header name="'X-HTTP-Method-Override'" value="'PUT'"/> this simulate a PUT method, but the backend doesn't accept :)

I also try this command : <dp:set-variable name="'var://service/protocol-method'" value="'PUT'"/> But it doesn't work :

any idea ?

In this case I would do service chaining i.e. the WSP sends the SOAP request to a subsequent MPGW which does the mapping.

The reason is the backend migrated from soap request to REST request.

So, we keep the consumer call the WSP and i need to map the request to a json format and the new backend is expected a PUT method.

But the problem is not PUT or GET into WSP datapower object, the problem is it's impossible to change method when WSP consume a MQ message as input request

Hi D@viid, I guess you can't change the HTTP method to PUT as the SOAP specification only allows POST and GET. The question now is, why does your backend expect a PUT?

Alternatively, you could use an MPGW service.

Hello

I have a WSP with an MQ as FSH. The backend expect a PUT request, so in the policy I use the 'Method Rewrite' option and set with 'PUT'

When i check in probes, the method is empty, 

is there an impossibility between an mq INPUT and a http out ? I remember, few years ago, i already have this issue and we solved it with this technique below

 <dp:set-request-header name="'X-HTTP-Method-Override'" value="'PUT'"/> this simulate a PUT method, but the backend doesn't accept :)

I also try this command : <dp:set-variable name="'var://service/protocol-method'" value="'PUT'"/> But it doesn't work :

any idea ?