Originally posted by: cubeweaver

We use WMB 6.1 on z/OS with WTX 8.2.0.4 if3 as transformation engine. Every time we deploy an updated version of our WTX maps, we have to recycle the broker to refresh cached maps.

My question to those with similar software/infrastructure setup: Is there a "hot" deployment feature for WTX cached maps?

Many thanks.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: cubeweaver

Obtained from online Help:

Map caching
At design time, set map caching to optimize run time.
When you use map caching, the run time is optimized because the process does not load the compiled map for every iteration of the running of the map. The compiled map is loaded only when the execution group, which is a grouping of message flows for a broker, starts, or a flow containing a WTX Map node is started.

If map caching is set on, any changes that you make to the compiled map are used by the message after you stop and restart the message flow. If map caching is set off, any changes that you make to the compiled map are used by the next message that passes through the message flow.

Set up map caching for each WTX Map node. This enables individual control for each map node instance. Set map caching on in the Basic tab under Properties in the WebSphere Message Broker Toolkit. Run maps are cached using the settings on the parent map. For maps that are cached, you must stop and restart the message flow through the WebSphere Message Broker Toolkit.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

After IBM confirmed that the documentation was wrong and the behaviour was right, I raised a PMR for the documentation - 31945,999,866
This was over a year ago but IBM support should be able to find it if you want to raise a call too.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

No, if you cache your maps you need to restart the broker (also still true for WMB 7 and WTX 8.3)

The documentation is a bit misleading too as it implies a flow restart would work.

I've just raised an enhancement request for this. I thought it was possible to do this (load and unload maps from memory) using the API, but i guess if it was easy they would already have done it.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: cubeweaver

Much appreciate, Oliver.

So this statement is not correct? "If map caching is set off, any changes that you make to the compiled map are used by the next message that passes through the message flow."

If so, broker has to be restarted NO MATTER how map caching was set.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

The following statement is correct:
"If map caching is set off, any changes that you make to the compiled map are used by the next message that passes through the message flow."

If you turn off map caching then the map will always be reloaded from disk each time it is run - i.e. the map is never stored in memory.

My comment on loading and unloading the map was for when it is cached in some reusable memory area (i.e. when the cache tick box is checked).

We're going to implement our WTX maps with caching turned off.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: cubeweaver

Oliver,
1. IBM could not locate PMR 31945,999,866 in archive. Maybe over 1 year old.
2. Do you have any concern regarding performance as your practice is to turn off map cache?
3. If I understood you correctly, the documentation is wrong in stating that with map cache checked, map will be reloaded upon broker restarted. Please confirm.

Sorry for all the troubles.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

1. IBM could not locate PMR 31945,999,866 in archive. Maybe over 1 year old.
OK

2. Do you have any concern regarding performance as your practice is to turn off map cache?
yes, performance is not as good. You'll have to test your system to work out the impact and whether you can live with the caching off.

3. If I understood you correctly, the documentation is wrong in stating that with map cache checked, map will be reloaded upon broker restarted. Please confirm.
That's correct - with map cache checked the map will only be reloaded upon broker a restart.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: GerryCullen

The Tech Note published for PMR 31945,999,866 is here:

Correction to map caching description in WebSphere Transformation Extender for Message Broker documentation
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: cubeweaver

My appreciation to Oliver and Gerry. This question is now closed for good.

I responded to IBM as follows in closing my own PMR today:
"...It seems that misleading information still exists in WTX online help (Wrong Info.doc). With “cache map” selected in WMB 6.1, message broker (not message flow) must be restarted."
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

IBM have told me that using mqsireload to restart an execution group will clear any cached maps - so it can be done at a level lower than the Broker.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: cubeweaver

Thanks Oliver for following up. Btw the erroneous documentation (identified by you to IBM) has been fixed in WTX 8.3 doc.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange