CMDB Impact Simulator issues
Perform the following checks when you notice that CMDB Impact Simulator widgets are not rendered correctly as expected.
|Issue||Cause and Resolution|
Impact Simulator permissions issue
If you encounter a permissions issue with Impact Simulator, confirm with your system administrator that you have the required role and permissions.
To view data and to work with the CIs in Impact Simulator, you must have the Impact Simulator User role and the permissions to query the CIs stored in BMC CMDB. The role and the permissions are mapped to the CMDB Data View group by default.
Impact Simulator uses Rest APIs that are called from the Impact Simulator User Interface to accept the CI information in the request. As a response, Impact Simulator returns a simulation ID, which is used to fetch the simulation results in the form of a graph.
To know if there are issues with the REST APIs, in Configurations > Core Configurations > Impact Simulator, change the Log Level to Debug. View the debug logs to check for any issues with REST APIs.
Redirect-URL is pointing to an incorrect jetty.
Verify that the Redirect URL is pointing to the correct jetty. The Redirect URL configuration(com.bmc.arsys.server.shared / *) is a map of ‘Server’ name on mid tier and the load balancer URL for its Jetty. Its syntax is as follows:
cmdb.<midtier server name>:<Jetty Load balancer URL for Server>;
If there are multiple servers, for example, Alpha and Beta configured on mid tier, then the syntax is as follows:
cmdb.alpha:<Jetty Load balancer URL for Alpha>; cmdb.beta:<Jetty Load balancer URL for Beta>;
For Helix setup, the format is as follows:
cmdb.<Helix server name>:<URL for Server>;
For information about configuring the redirect URL to access the new CMDB UI through mid tier with relevant examples, see Configuring the URL to access CMDB Portal through Mid Tier.
Check the Access-Control-Allow-Origin setting
Component name: com.bmc.arsys.server.shared
This setting defines whether cross-origin requests are allowed, and indicates the origins that can make REST API calls on the AR System Server.