Hi Stefano,

There is no way to change the token expiration time.

ZMF explorer establishes 5 pre-defined 'sessions' with the ZMF REST server. We pull a session from the pool to perform your current set of functions. Once that set is complete the 'session' is returned to the pool. If a session is left inactive (i.e. you leave the current function in-flgiht) it is terminated by the ZMF REST server after a period of time. This should not cause any functional problems, you just click to re-establish the session and then proceed with what you want to do.

Is this causing a problem ?

All the best - Steve

Thank you Steve.

Users just told me that it's annoying having to re-establish session. I was just wondering if there is a parameter for this... So not even at ZMF REST Server I may "add" some time before terminating session? 

I've tried to change SESSION_TIMEOUT in ZMFPARMS member of the z/OS Tomcat installation but nothing happened.

Any advice?

Thank you.

The SESSION_TIMEOUT parameter is the right one. It is specified in minutes and has a default of 30 minutes !   That ought to be enough for anybody, yes ?

Which makes me wonder what else is going on here.

I'll try and do some testing at my end (but that may have to wait till next week). In the meantime, do you have a feel for how long a user leaves an explorer initiated function inactive before they get this "Inactive Toke Expired" message ?

Thanks

The SESSION_TIMEOUT parameter works fine for me - we use a setting of 10 (i.e. 10 minutes). The default setting is 30 (minutes). You can make it longer if you wish but why would you want to do that? The local representation of the tree is a point-in-time snapshot. Something may have changed in the period since you last interacted with ZMF - refreshing the tree is a good idea.

On reflection, I believe that the setting we use (i.e. SESSION_TIMEOUT=10) is a good compromise.

You can make this longer but all you're doing is using up more resources in the ZMF REST server (e.g. if a user doesn't do anything for 30 minutes, surely it's a good idea to release resources ?). And relying on a tree that is 30 (or whatever the SESSION_TIMEOUT value is set to) minutes old is not a good idea anyway ?

All the best - Steve