Changing the heap size on App Visibility components

Under certain circumstances, you might need to change the memory heap size on one or more App Visibility components. For example, in large deployments of TrueSight Synthetic Monitor, the heap size on the collector must be increased to 6 GB.

To change the heap size of App Visibility components on Windows

  1. Stop the service of the component you want to modify. See Starting and stopping the App Visibility server services for more details.

    Note

     If you are working in a high-availability environment, stop the component service on the standby node first, and then stop the service on the active node.

  2. Delete the service. 
    1. Open a command prompt as an administrator.
    2. Enter the appropriate command for the component you are updating:
      • sc delete adop_collector
      • sc delete adop_portal
      • sc delete adop_apm_proxy
  3. Navigate to the bin folder of the component (for example, <collectorInstallationDirectory>\collector\bin).
  4. Create the service with the new values to set the values of the initial and maximum memory heap in megabytes.
    Enter the appropriate command for the component you are updating:

    Collector
    createCollectorService.bat /service_name "adop_collector" /service_exe ADOPCollectorService.exe /JvmMs 2048 /JvmMx 6048
    Portal
    createPortalService.bat /service_name "adop_portal" /service_exe ADOPPortalService.exe /JvmMs 2048 /JvmMx 6048
    Proxy
    createApmProxyService.bat /service_name "adop_apm_proxy" /service_exe ApmProxyService.exe /JvmMs 2048 /JvmMx 6048
  5. Start the service.

    Note

     If you are working in a high-availability environment, start the component service on the active node first, and then start the service on the standby node.

To change the heap size of App Visibility components on Linux

  1. Stop the service of the component you want to modify. See Starting and stopping the App Visibility server services for more details.

    Note

     If you are working in a high-availability environment, stop the component service on the standby node first, and then stop the service on the active node.

  2. Navigate to the /etc/bmc folder. 
  3. Open the appropriate conf file for the component you are updating:
    • portalDeamon.conf
    • collectorDaemon.conf
    • apm-proxyDeamon.conf
  4. Modify the INITIAL_MEMORY and MAXIMUM_MEMORY properties with the new values.
  5. Start the service.

    Note

     If you are working in a high-availability environment, start the component service on the active node first, and then start the service on the standby node.

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

Comments