Transformer required or not?

[duachirag]

I am trying to integrate MQ Series and external web service. Mule should pick up plain XML message from the queue and forward it to the web service. Finally Mule should put the response back on queue. Do I need a transformer? I don't have the environment to test this right now, just trying to come up with the configuration doc for the above scenario.

Web service is SOAP based. Mule should be able to form a request from plain XML on the queue. Am I right?
Another thing is I am trying to create a mock web service hosted inside Mule. Just in case if the external web service is down I want to continue my testing using this mock web service. Please let me know if this mock behaviour can be achieved in any other way (besides just writing a SOAP web service inside Mule from scratch).

[rotten]

Under the list of available transports there is a SOAP transport.  (It is deprecated in favor of the CXF and/or Axis transports.  It might be a good starting point.

If your input message is already in the format you need for output, and if your response message is already the same format you need to send back, you may not need any additional transformers.

On the other hand, odds are pretty good you'll want to set some headers, or tweak the message in some way.

I hate to say it, but trying to do a detailed architecture drawing before you have an intimate knowledge with the tool's idiosyncracies may be putting the cart a little bit in front of the horse.  I'd suggest starting  with a more "block level" plan.  Map out the rougher flow with well defined input and output specs.  Then build the tool to match that block diagram as best you can.  Then go back to fill in the miscellaneous details after you get it working.

Good luck!

duachirag wrote:

I am trying to integrate MQ Series and external web service. Mule should pick up plain XML message from the queue and forward it to the web service. Finally Mule should put the response back on queue. Do I need a transformer? I don't have the environment to test this right now, just trying to come up with the configuration doc for the above scenario.

Web service is SOAP based. Mule should be able to form a request from plain XML on the queue. Am I right?
Another thing is I am trying to create a mock web service hosted inside Mule. Just in case if the external web service is down I want to continue my testing using this mock web service. Please let me know if this mock behaviour can be achieved in any other way (besides just writing a SOAP web service inside Mule from scratch).

[duachirag]

Thanks for you response!


Under the list of available transports there is a SOAP transport.  (It is deprecated in favor of the CXF and/or Axis transports.  It might be a good starting point.

If your input message is already in the format you need for output, and if your response message is already the same format you need to send back, you may not need any additional transformers.

On the other hand, odds are pretty good you'll want to set some headers, or tweak the message in some way.

I hate to say it, but trying to do a detailed architecture drawing before you have an intimate knowledge with the tool's idiosyncracies may be putting the cart a little bit in front of the horse.  I'd suggest starting  with a more "block level" plan.  Map out the rougher flow with well defined input and output specs.  Then build the tool to match that block diagram as best you can.  Then go back to fill in the miscellaneous details after you get it working.

Good luck!

duachirag wrote:

I am trying to integrate MQ Series and external web service. Mule should pick up plain XML message from the queue and forward it to the web service. Finally Mule should put the response back on queue. Do I need a transformer? I don't have the environment to test this right now, just trying to come up with the configuration doc for the above scenario.

Web service is SOAP based. Mule should be able to form a request from plain XML on the queue. Am I right?
Another thing is I am trying to create a mock web service hosted inside Mule. Just in case if the external web service is down I want to continue my testing using this mock web service. Please let me know if this mock behaviour can be achieved in any other way (besides just writing a SOAP web service inside Mule from scratch).