Setting the Managed Bean Expiration Policy
If you create custom pages in the Fabric Tasks area of My webMethods Server, it is possible to specify the managed bean expiration policy for a Fabric folder (and for workspace templates as well) in My webMethods Server. By default, a page’s managed bean is destroyed when the user navigates to another page. When the user returns to the original page, it must be completely reloaded.
To avoid this, you can use the Bean Expire Policy property for Fabric folders and workspace templates to specify that the managed bean does not expire. For more information, see Administering My webMethods Server.
Related Topics