MQSeries.net :: View topic - Map Node - Saving fields between maps and service calls

Paul D

Here's my situation. I'm trying to use broker (v6.1) to do a series of service calls and would like to use maps for mapping the interface elements between the calls. I have XSD's for all interfaces. I've done broker for quite some time and know that I can do this with ESQL, but I'm trying to get to something 'simpler' for a team I support to use for this scenario. I have little experience with maps. I also do understand that there are other tools to do this from IBM such as Process Server (would be a really good fit).

OK, back to broker. Here's what I'm trying to do in more detail. I'll have a flow that takes in a request message like this:

Request A
Field A1
Field A2
Field A3

and I'll need to map that to a different interface for a service call, so I'd do this...

Map RequestA.FieldA1 to RequestB.FieldA1
Map RequestA.FieldA2 to RequestB.FieldA2

And do the call for Request B

Note, I don't use the RequestA.FieldA3 in the service call with Request B, but I do want to hold onto that field and use it later, either in a subsquent service call or my reply out back to the initial call that came into the flow.

So at this point, I did the call with Request B, and my flow has a body of Response B from Request B, a completely different structure. If I now am finished with my work in the flow and want to construct my reply message back to the flow caller, how do I get back to the field RequestA.FieldA3 to use it in my reply?

Remember that I'm trying to stick to a 'mapper' development paradigm here, trying to avoid use of ESQL. In ESQL, I'd have just saved that field to the environment or local environment tree before the call and referenced in from there to construct my final reply back to the flow caller.

What is the easiest way to get some parking lot or scratch pad that I can hold fields in between maps that I need later. It does not appear that this can be done directly inside the mapper. One idea I had was writing an ESQL routine save elements in the environment, that could be invoked from the mapper, but maybe there is a more straight forward way to do it. I'm sure others have needed to do this, what's the best approach? Is this just too complex that I should move back to ESQL?
_________________
Thanks!!!

Paul D