How to install Control-M v8 Products on Amazon Web Service (AWS) Elastic Cloud Computing (EC2) ?

Version 1

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    Control-M/Enterprise Manager


    Control-M/Enterprise Manager


    Control-M/Enterprise Manager 8.0.00 Amazon Web Service (AWS) Elastic Cloud Computing (EC2)


    Installing Control-M V8 Oneinstall on AWS Red Hat LINUX 6.5 using Postgres

    The below process  will install the Control-M/Enterprise Manager V8(64 bit), Control-M/Server V8(64 bit), Control-M/Agent V8(32 bit) and the Control Modules(32bit) as one installation using only 1 Unix user. This will install the default Postgres database. These Control Modules are installed:  Control-M for SAP 7.0.00, Control-M for PeopleSoft 8.0.00, Control-M for Informatica 7.0.00, Control-M for Databases 7.0.00, Control-M for SAP Business Objects 7.0.00.

    The System Administration commands are supplied as examples.




    Amazon Web Services (AWS) Background

    Amazon Web Services is a collection of remote computing services that together make up a cloud computing platform, offered over the Internet by at


    Server platforms are created and maintained by the AWS Management Console.  In AWS, Amazon uses the EC2 (Elastic Cloud Compute) to allow users to rent virtual computers called “instances”.


    By default, an EC2 instance has two IP addresses at launch time: a private IP address and a public IP address that is mapped to the private IP address through network address translation (NAT). Every time an instance is stopped/restarted, the instance will get a new public hostname/IP address. The Private hostname/IP address will stay the same until the instance is terminated. The way to keep a static Public hostname/IP address is to allocate an Elastic IP address and associated it with the instance. Elastic IP (An Elastic IP address (EIP)) is a static Public IP address designed for dynamic cloud computing. With an EIP, you can mask the failure of an instance or software by rapidly remapping the address to another instance in your account.


    Note: most problems are related to the using the public vs private IP address. The private IP address is not reachable from the Internet. Be sure that the hostnames used in the configuration files that need to be accessed externally resolve to the public IP address. Customers can add these Public hostnames to their DNS servers.




    Create a Red Hat 6.5 instance (or other Control-M supported OS version)


    a.       In the AWS EC2 Service, select Instance and “Launch Instance”. Take the defaults except the following.


    b.      Select a supported Control-M OS with at least 4GB of RAM


    c.       Add at least 30GB of storage


    d.      Give it a ‘tag’ for easy reference. E.G. CONTROLM


    e.      The Security Group needs to have:


                                                                   i.      TCP port 22 for SSH access to login to the server


                                                                 ii.      TCP port 13075 for CORBA


                                                                iii.      TCP ports 13100-13119 for EM components (any range of 20 ports)


                                                               iv.      TCP port 18080 for the web server


    f.        Create and Store a Public/Private security key pair for logging in with SSH


    g.       In EC2 Network, create an Elastic IP address an associate it with your server instance




    2)      Login to the AWS server using SSH


    a.       Login username is ec2-user, not root.


    b.      SSH login format:  ssh -i <path>/<private key file>   ec2-user@<public hostname>


    c.       Note: you will not be able to SSH from within the BMC network to the AWS instance. You will need to have IT open the AWS instance IP address for SSH or access the AWS instance from outside of the BMC network.


    d.      Login as root:  sudo su –




    3)      Configure the server


    a.       Change the hostname to be less than 32 chars


                                                                   i.      modify the hostname parameter in the /etc/sysconfig/network file.


    For example, to




                                                                 ii.      Reboot with the command:  reboot


    b.      Create the controlm unix group: groupadd controlm


    c.       Create the controlm unix user: useradd –d /home/ctm –g controlm –s /bin/csh ctm


    Note: The Control-M OneInstall will install the EMV8 (64 bit), Server V8(64bit), Agent V8(32bit) and the CM’s (32bit) as one install using 1 Unix user. The OneInstall requires the unix user shell to be either csh or tcsh since these are the only shells all 3 products support. You can use either one.


    d.      Change permission on the home directory:  chmod 755 /home/ctm




    4)      sftp the Control-M installation image to the AWS server


    a.       AWS only supports sftp and not ftp, however the BMC EPD does not support sftp


    b.      You will have to ftp the V8 installation Image to a server


    c.       Then sftp the V8 image to the AWS server




    5)      Run to verify server


    a.       Download the file check_req_tar.Z attached to KA409263 “When running the script on Red Hat EL 6.5 for Control-M V8 the following message is returned: is not supported.”


    Otherwise you will get the error: “This Red Hat Enterprise Linux Server release 6.5 (Santiago), kernel release 2.6.32-431.29.2.el6.x86_64 64 bit computer is not supported by Control-M product components version 8.0.00 with PostgreSQL.”


    The KA check_req has Red Hat specific checks.


    b. got the following errors. (This is because the Agent is 32bit and requires some 32bit runtime libraries.)


     Install glibc.i686:el6 to value >= 2.12-1.7


     Install libstdc++.i686:el6 to value >= 4.4.5-6


     Install pam.i686:el6 to value >= 1.1.1-4




    c.       Run:       yum install glibc.i686


    d.      Run:       yum install libstdc++.x86_64


    yum install libstdc++.i686


                                                    Note: it was necessary to update the 64bit version of the library first.


    e.      Run:       yum install pam.x86_64


    yum install pam.i686


    f.        Run:       yum install compat-libstdc++-33.i686


    Note: the Agent(32 bit) also requires this library


    g.       Run:       yum install ksh


    The Korn shell will be needed later for installing fixpacks


    h.      For the check_req error: “Not enough free swap space. At least 3GB free swap is required.”


    This will create a 6GB swap space file but for production systems you should allocate a swap device instead.


                                                                   i.      Create the swap file:


     dd if=/dev/zero of=/swapfile bs=1024 count=6291456


                                                                 ii.      Change the permission of the new swap file:


                 chmod 0600 /swapfile


                                                                iii.      Setup the swap file with the command:  mkswap /swapfile


                                                               iv.      enable the swap file:  swapon /swapfile


                                                                 v.      Enable it at boot time- edit /etc/fstab to include:


    /swapfile swap swap defaults 0 0


                                                               vi.      Verify the swap file space:  cat /proc/swaps  or  free




    i.         For the check_req error: “Change the kernel.sem (semmni) value to higher or equal to 500”


                                                                   i.      To  view current settngs run: cat /proc/sys/kernel/sem


                                                                 ii.      To change settngs run:  sysctl –w kernel.sem=”250 32000 100 500”


    j.        The Java version is OK.


    6)      Run the Control-M V8 Setup


    a.       Login as the control-M user and run


    ??Note:  Oneinstall does not ask you for the ControlM Server DB login/password.


    b.      Select all of the defaults unless something is required for the install


    c.       If your hostname is less than 32 characters, then your EM components will start OK. If the hostname is longer then you will have to edit each EM component to use a hostname less than 32 characters. For example, if your hostname is “”, then you can assign the EM components the unqualified name “ip-172-31-16-37”.


    d.      Shutdown the EM components.


    e.      CORBA changes. It’s necessary to change CORBA so that CORBA and the EM components listen on the public IP address. Normally, orbconfigure is used to configure this but X-Windows is not available so we will modify the file manually. The file is <EM_install>/ctm_em/etc/domains/config.xml.


    In the “default” section(“<scope name="default">”), after the line:


    <variable name="-SSLVersionList" value="SSLv2,SSLv3,TLSv1"/>




          Add these 3 lines:


    <variable name="-APPSSL" value="8"/>


    <variable name="-ORBCollocation" value="global"/>


    <variable name="-ORBListenEndpoints" value="iiop://:13100/portspan=20&amp;"/>






                    13100 with the starting port address for your EM components(if you are not using 13100-13119)


                    “” with a Public name of your EC2 instance.




    In the “ns” section, change the line to have the public hostname:




    <variable name="-ORBListenEndpoints" value="iiop://:13075/reuse_addr=0"/>




    <variable name="-ORBListenEndpoints" value="iiop://:13075/"/>


         replacing “” with a Public name of your EC2 instance.




    f.        Before restarting the Naming Server, remove all of the files from the directory: 


    <EM Installation>/ctm_em/var


    g.       Restart the EM components




    7)      Install the latest EM, Server and Agent fixpacks


    8)      From the Windows EM V8 client


    a.       On the EM client, in the <EM install>/default/etc/domains/config.xml file, change the


    <variable name="-ORBDottedDecimalAddresses" value="0"/>   to


    <variable name="-ORBDottedDecimalAddresses" value="1"/>


                                    This tells CORBA not to resolve the IP address to a name


    b.      Using the CCM, login to CMS using the Public hostname




    9)      (Optionally) if you need to add a storage volume


                                                                   i.      Create the storage volume in EC2


                                                                 ii.      Associate it with the Instance


                                                                iii.      Login to the server and create the partition on it using fdisk: fdisk


                                                               iv.      Create the file system using mkfs: mkfs -t ext4 /dev/xvdb


                                                                 v.      Mount it to a directory: mount -t ext4 /dev/xvdb  /media/controlm


                                                               vi.      Add it to the /etc/fstab file so it automatically mounts on reboot


    E.G.  /dev/xvdf               /media/controlm         ext4    defaults        1 2  

    Additional Information:
    -    For Deployment Control-M 9.0.00 on Amazon Web Service (AWS) Elastic Cloud Computing (EC2), please refer to KA 000132990  




    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles