Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Configuring after installation

A user or administrator must perform this task before using the product (or part of the product) to accomplish user goals.

Configuring the memory settings

For the production (and potentially lower) environments, the number of concurrent jobs and memory consumption of those individual jobs might require an increase to the Java heap size for the BMC Atrium Orchestrator JVMs.

You can adjust the heap size on the server by editing the Tomcat properties.

Video demonstration

This video describes how to adjust the heap size of a CDP server on Windows (03:26 mins).

Use player to increase quality or switch to full screen | YouTube: https://youtu.be/TmkS6EXX9lQ

To adjust the heap size of a CDP server on Windows

  1. Stop the BMC Atrium Orchestrator Configuration Distribution Peer service. See Starting and stopping product components and services.
  2. From the command prompt, go to <AO_HOME>\tomcat\bin and run the tomcat7w.exe //ES//<CDPService> command.
  3. On the CDP Peer Properties dialog box, click the Java tab.
  4. You can edit the values of the following parameters to determine the heap size:
    • Initial memory pool
    • Maximum memory pool
      Here, the default value of the parameters is Initial memory pool=1024 and Maximum memory pool=1280. Do not increase the Maximum memory pool value (default 1280) to more than half of the computer's total memory. Also, do not increase this value beyond 8192 (8 GB) without consulting BMC Customer Support.
  5. Click Apply and then click OK.
  6. Start the CDP service. See Starting and stopping product components and services.

To adjust the heap size for a Linux computer

  1. Stop the BMC Atrium Orchestrator Configuration Distribution Peer service. See Starting and stopping product components and services.
  2. Go to the <AO_HOME>/bin directory.
  3. Back up the the server.sh file.
  4. Open the server.sh file for editing.
  5. Edit the values of the following parameters to determine the heap size:
    • -Xms
    • -Xmx
      Here, the default value of the parameters is: -Xms1024m and -Xmx1280m. Do not increase the set maxMemSize value (defaut 1280) to more than half of the computer's total memory. Also, do not increase this value beyond 8192 (8 GB) without consulting BMC Support.
  6. Save the file.
  7. Start the CDP service. See Starting and stopping product components and services.

Related topics

Using software configuration management systems when creating workflows

Integrating

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

Comments

  1. Manoj Potluri

    I followed the steps mentioned above to update the java heap size on a windows server, I updated the (set initMemSize and set maxMemSize) values in bao.bat file. But my changes are not being reflected when i re started the CDP service. 

    My windows server has 16 gigs of ram. 

    how did i know that the changes were not applied ? is by looking at the console view of the grid manager it is showing max mem size as 742. 

    ---------------------------------------------contents of bao.bat----------------------------------------------

    :doInstall
    set initMemSize=512(Updated this to 2048)
    set maxMemSize=768(Updated this to 2048)
    set jvmOptions=-XX:NewSize=256m;-XX:MaxNewSize=256m;-XX:MaxPermSize=128m;-XX:+HeapDumpOnOutOfMemoryError;-XX:HeapDumpPath="D:\Apps\BMC Software\CDP-OC\tomcat\logs";-XX:+UseConcMarkSweepGC;-XX:+DisableExplicitGC;-Dcatalina.base="D:\Apps\BMC Software\CDP-OC\tomcat";-Dao.home="D:\Apps\BMC Software\CDP-OC"
    set SERVICE_DISPLAYNAME="BMC Atrium Orchestrator Configuration Distribution Peer"
    set SERVICE_DESCRIPTION=""
    echo Setting up tomcat as a service.
    call service.bat install AO-CDP
    rem Setting the memory allocation and jvm options
    call tomcat7 //US//AO-CDP --Startup=auto --JvmMs=%initMemSize% --JvmMx=%maxMemSize% ++JvmOptions=%jvmOptions% --DisplayName=%SERVICE_DISPLAYNAME% --Description=%SERVICE_DESCRIPTION%
    rem Resets the variables
    set initMemSize=(Even tried to Update this Value to 2048)
    set maxMemSize=(Even tried to Update this Value to 2048)
    set jvmOptions=
    set SERVICE_DISPLAYNAME=
    set SERVICE_DESCRIPTION=
    goto end

     

    Thanks,

    Manoj Potluri.

    Oct 28, 2013 11:01
    1. Shweta Hardikar

      Hi Manoj, 

      We will get back to you on this. 

      Thanks. 

      Oct 29, 2013 01:19
  2. James Annis

    Any updates on this?

    Feb 17, 2014 07:35
  3. Shweta Hardikar

    Hi, 

    We have corrected the steps for changing the heap size for CDP server on Windows and also added a video demonstration. Let us know if this helps!

    Thanks!

    Jun 03, 2014 01:11
  4. Manoj Potluri

    thanks that helps.

    Jun 05, 2014 10:29
  5. Bruno Muniz

    I've installed OCP separated from CDP. Is it recommended to do the same configuration also for the OCP service?

    Do you have any sizing information that relates number of process with minimum and maximum memory sizes? Or any other sizing information?

    Aug 14, 2014 01:33
    1. Shweta Hardikar

      Hi Bruno,

      Yes you can do the same configuration for the OCP service as well.

      Sorry, we do not have any sizing information with us. 

      Hope this helps.

      Aug 26, 2014 04:27
      1. Bruno Muniz

        Thanks, Shweta. It helped.

        About the sizing, no problem, but that's an important information to us. If you could coordinate internally for this information to be generated, I would be grateful. 

        Regards.

        Aug 26, 2014 12:23
      1. Bruno Muniz

        To help others, there's some sizing information at https://docs.bmc.com/docs/display/public/itsm81/Hardware+requirements, search for "BMC Atrium Orchestrator".

        Best Regards.

        Aug 27, 2014 01:46
        1. Shweta Hardikar

          Thanks Bruno.

          Sep 02, 2014 03:47