Smarts SAM: Not all the topology actions are available after the SAM domain is restarted. What causes this?

Products

• VMware Smart Assurance

Environment

VMware Smart Assurance - SMARTS

Resolution

Not all of the topology actions are available after the SAM domain is restarted. Only until a user logs into the console, and performs an action, are they visible. Why does Smarts require an action/object that is invoked by a user in the console in order for these Map_Connectivity objects to be populated, instead of automatically?

Within Smarts, not all topology actions, are immediately available after a SAM Domain restart is due to:

1. The Map Instances need not be present in all layers of SAM.
   • Maps are only loaded on user request so when a user selects a notification instance, the console tries to load all the context related Menus, wherein it looks at the different Map Types supported and creates Map Type instances (if it is not present in server). 
   • Normally Users would connect to Presentation SAM and it should exist in there.
2. Lastly, the details about what map types are applicable/available for different classes are loaded during server startup, not the map instances itself.