This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Atrium Impact Simulator Performance Guide and Best Practices


You can perform various actions from a performance standpoint using BMC Atrium Impact Simulator (AIS). Normally, performance is not an issue unless you are simulating big models (having more than 1000 results), but there might be issues with smaller scenarios, when there are multiple concurrent users simulating.


BMC Atrium Impact Simulator is a plugin, and runs on Atrium Shared Plugin server. This implies that BMC Atrium Impact Simulator shares the plugin server resources with the other plugins.
The Atrium Shared Plugin Server is started by armonitor, and the starting line looks similar to the following:

"C:\Program Files\Java\jre1.8.0_91\bin\java" -Xmx768m -classpath "
C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\shared;
C:\Program Files\BMC Software\AtriumCore\cmdb\plugins;
C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arpluginsvr91_build001.jar;
C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arapi91_build001.jar;
C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arutil91_build001.jar;
C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\log4j-1.2.14.jar;
C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\cmdbapi91.jar;
C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\websvcjava91_build001.jar;
C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\federation\lib\axis.2.1.4_all.jar;
C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\federation\lib\
C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\cmdbbol91.jar" 
com.bmc.arsys.pluginsvr.ARPluginServerMain -x clm-aus-014670 -i 
"C:\Program Files\BMC Software\ARSystem" 

  • The shared folder path helps us ensure the right plugin line.
  • The -Xmx is the java option that determines how much memory this plugin can use.
  • The plugin has a default of 512m which you can, and should increase, as the first measure for Performance troubleshooting.
  • Normally, 1024m should suffice for normal usage of BMC Atrium Impact Simulator (a few concurrent users doing regular impact models - a few 100s results). If you have many concurrent users or big models of impact you should increase even further. You can always monitor the process to determine the amount of memory it uses and adjust accordingly.
  • Also, note that if you are using BMC Atrium Impact Simulator from a Change Management console the memory usage will be different because we store the Change Management impact analysis in memory even after you have closed the BMC Atrium Impact Simulator simulation window.
  • The time when we store this change request impact analysis can and should be configured accordingly to your environment requirements. To configure this setting you can modify the BMC Atrium Impact Simulator plugin settings adding a new line: <time_for_sim_cache_removal>number_of_minutes</time_for_sim_cache_removal>.
  • BMC Atrium Impact Simulator as a plugin does simulation computation, and also stores the CIs inputs and results in memory (since it is an ARDBC plugin). So, memory will build depending on the amount of simulation it has in memory at a certain point. Regular simulation done from BMC Atrium Impact Simulator (not from Change Management) are wiped from memory once you close the BMC Atrium Impact Simulator window.

Finally, there are many factors involved, if the simulation through BMC Atrium Impact Simulator is slow to show the results.

DataBase (DB)

To fetch the model of the Input CI, BMC Atrium Impact Simulator triggers a GraphWalk API call to the CMDB. This is the most expensive API call from the CMDB Engine, since it has to transverse the whole CI/Relationship/CI modeling, find all impacted CI and the impacted CI of those CIs and so on to infinite level of depth.

The GraphWalk API triggers multiple SQL calls. Some of the calls are quite expensive depending on DB Cache settings, threads, processing power, indexing, etc. DB Analysis during a slow AIS simulation is fundamental to discard DB problems.

BMC Remedy AR System Server

In the middle of the Plugin / CMDB / DB communication is the BMC Remedy AR System Server. If the BMC Remedy AR System Server is busy doing multiple other tasks, the BMC Atrium Impact Simulator API call is put on queue, so even if the DB is performing fine, the BMC Remedy AR System Server could be the bottleneck.

API/SQL/Filter logs run through AR Log Analyzer and is the best option to discard all these problems, and to find out which API/SQL call is causing the delays.

BMC Remedy Mid TierEven though the results of the simulation may quickly be acquired from the DB sent over BMC Remedy AR System Server, the BMC Remedy AR System Server sends them over to the AIS plugin. BMC Remedy Mid Tier may cause a delay and show the results slowly. It should be taken into account that showing thousands and thousand of results in a table field can take time, since the BMC Remedy Mid Tier needs to acquire and then draw all those results coming from BMC Remedy AR System Server.
Local BrowserIf BMC Remedy Mid Tier or BMC Remedy AR System Server communication is fluid, and the delay is not observed there, the issue could be the local browser. Again, since displaying and drawing all the results can be expensive, a lot of load is put not only on the browser memory but also in browser/ BMC Remedy Mid Tier network communication. This issue is rare, but sometimes observed during VPN connections to the  BMC Remedy Mid Tier where browser is far away from  BMC Remedy Mid Tier and network is not fluid between them.

Was this page helpful? Yes No Submitting... Thank you