It really ought to be supported in the Mapping node but unfortunately it's not.
You can't do a cast to include it under LocalEnvironment either. Correct me if I'm wrong.
If you don't need to attach a payload to the request you can map to the (by IBM provided) TimeoutRequest message schema.
Else the only option is to build the LocalEnvironment TimeoutRequest through code.
Can't cast it.
I was asking because I wanted to make all i need with a Mapping Node. And I need the information supplied by TimeoutNotification.
I can do it with let's say Java node, but what's the actual use for Mapping node if it cannot support output from other integrated nodes.
Have you thought about putting that information on the RFH header? You should be able to map it there right? :innocent:
That's an option in TN node? Cause if I have to use other node I will process everything in it and not bother with Mapping node. And that doesn't answer the original question.
Note that in IIB v9.0 the built in schema for the LocalEnvironment does correctly provide the "TimeoutRequest" structure.
You could consider raising a PMR for the omission of this in the WMB v8 product.
Also note that "LocalEnvironment.TimeoutRequest" is the default location if you have not set the "Request location" property on the TimeoutControl node.
A possible workaround you could consider is to set the TimeoutControl node "Request location" property to be "LocalEnvironment.Variables.TimeoutRequest", and import the IBM supplied "TimeoutRequest" message and apply a Mapping cast.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum