explorer tree of backoffice is missing after login

[Former Member]

Hi Experts,

we plan to not reset for everylogin to backoffice so we set the below property as backoffice.cockpitng.reset.triggers=start

But in cluster envt,we see that explorer tree is missed and i had to reset everythng in orchestrator mode (F4). How can i avoid this for every login.

[arvind-kumar_avinash]

Hi - By default, automatic reset of all configurations on the application startup, and after each login, is disabled. If you want to enable it, you need to set the following properties:

 backoffice.cockpitng.reset.triggers=start,login
 backoffice.cockpitng.reset.scope=widgets,cockpitConfig

Since you do not want automatic reset of all configurations on each login, you should comment out this property.

[arvind-kumar_avinash]

Hi - please update if it worked for you.

[Former Member]

hi ,

Unfortunately no luck.

When we tried resetting in Orchestrator mode for one node (logged into node specific backoffice) , the tree goes missing in another node which belongs to same cluster.

This is a problem is when people work over load balancer url which points to either nodes , the reset by one person on a node ,makes the tree disappear for the other person working on different node in the same cluster.