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://www.youtube.com/watch?v=TmkS6EXX9lQ&feature=youtu.be Open link

To adjust the heap size of a CDP server on Windows

Stop the BMC Atrium Orchestrator Configuration Distribution Peer service.
From the command prompt, go to <AO_HOME>\tomcat\bin and run the tomcat6w.exe //ES//<CDPService> command.
On the CDP Peer Properties dialog box, click the Java tab.
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.
Click Apply and then click OK.
Start Grid Manager and ensure that it is up and running.

To adjust the heap size for a Linux computer

Go to the $AO_HOME\bin directory.
Back up the the server.sh file.
Open the server.sh file for editing.
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.
Save the file.
Start Grid Manager and ensure that it is up and running.

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

Last modified by Dee dee Rothery on Sep 19, 2016

configuration overview post-installation task heap_size

Comments

Javier Prieto sabugo

Maybe would be worth to mention the proceddure, for Linux installations, to register bao as a service. Maybe trivial for people with Linux knowledge, but I think someone might find it helpful
Already refered in the comunities, under:
https://communities.bmc.com/docs/DOC-20823

[root@RHELBAO bin]# cd /opt/bmc/ao/cdp/bin
[root@RHELBAO bin]# cp bao.sh /etc/init.d/bao
[root@RHELBAO bin]# ln -s /etc/init.d/bao /etc/rc2.d/S99bao
[root@RHELBAO bin]# ln -s /etc/init.d/bao /etc/rc0.d/K99bao
[root@RHELBAO bin]# /sbin/chkconfig bao on

Mar 28, 2014 09:23
1. Javier Prieto sabugo
  
  Hello, just wanted to do 2 extra remarks:
  
  1 - IN THE CASE OF INSTALLING AM AND CDP IN A SINGLE SERVER
  
  Of course you will have to add the 2 different "bao.sh" scripts as 2 different services (please see log behind [consider that it is for SLES]
  
  2 - IN CASE YOU ARE USING SLES instead RHEL
  
  The syntax of the chkconfig and the path where the init/stop scripts have to be copied are slightly different, please find also the example
  
  vlt60990:/opt/bmc/ao/cdp/bin # cp bao.sh /etc/init.d/baocdp
  vlt60990:/opt/bmc/ao/amrepo/bin # cp bao.sh /etc/init.d/baoamrepo
  
  vlt60990:/ # ln -s /etc/init.d/baoamrepo /etc/rc.d/rc2.d/S99baoamrepo
  vlt60990:/ # ln -s /etc/init.d/baoamrepo /etc/rc.d/rc0.d/K99baoamrepo
  vlt60990:~ # chkconfig -add baoamrepo
  insserv: warning: script 'baoamrepo' missing LSB tags
  insserv: warning: script 'baoamrepo' missing LSB tags
  insserv: Default-Start undefined, assuming default start runlevel(s) for script `baoamrepo'
  baoamrepo 0:off 1:off 2:off 3:on 4:off 5:on 6:off
  
  vlt60990:/ # ln -s /etc/init.d/baocdp /etc/rc.d/rc2.d/S99baocdp
  vlt60990:/ # ln -s /etc/init.d/baocdp /etc/rc.d/rc0.d/K99baocdp
  vlt60990:~ # chkconfig -add baocdp
  insserv: warning: script 'baocdp' missing LSB tags
  insserv: warning: script 'baocdp' missing LSB tags
  insserv: Default-Start undefined, assuming default start runlevel(s) for script `baocdp'
  baocdp 0:off 1:off 2:off 3:on 4:off 5:on 6:off
  
  Apr 10, 2014 05:36
Gordon McKeown

I will take the opportunity to plug my one-hit installation script, which does this setup for you

Mar 31, 2014 05:29
Shweta Hardikar

Thanks Javier, we will revise this document as early as possible. Did you use Gordon's one-hit installation script?

Apr 01, 2014 12:22
Oleksii Volkov
For Windows services you should extend the procedure with 2 extra steps before "(4) Start Grid Manager...":
- Under "Administrator" run "bao.bat uninstall" & "bao.bat install" to re-install the service with the new configuration applied.
- (Optional) After CDP/AP Windows service re-install Log On account will be default "Local System", so change it, if required in your environment.
Also I propose to mention, how customer can easily check active memory configuration:
- For CDP servers: http(s)://<cdp-host>:<cdp-port>/baocdp/console
- For AP servers: http(s)://<ap-host>:<ap-port>/baoap/console
May 16, 2014 08:19
Shweta Hardikar

Hi,
We have updated the instructions for changing the heap size and added a video demonstration to the topic. Let us know if this helps.
Thanks!

Jun 03, 2014 01:08
Wookie Houle

The "initial memory pool" value, also known as "-Xms" should not be changed from the defaults. Doing so will impact the ability of the JVM to garbage collect effectively, and can cause high memory utilization and outOfMemoryErrors.

May 29, 2015 09:57
1. Dorothy Poole
  
  Thanks Wookie. Per our discussion, I have added this comment to BAO-512 to confirm with the team and will update the page when that happens.
  
  May 29, 2015 10:02

Log in or register to comment.

Using a command line to uninstall platform components

Upgrading