Installing Control-M on EC2 Linux platform

The following procedure describes how to install Control-M on EC2 Linux platform.

NOTE: If you are using an Oracle database, swap memory must be enabled on AWS Linux.

To install Control-M on EC2 Linux platform:

1. Create a Control-M supported Linux OS instance (for example, Red Hat 6.5 or higher instance) by doing the following:
   1. In the Cloud Services Management Console, select the instance operating system.
   2. Select the instance type
   3. Use the default configuration except for the following:
      • Select a supported Control-M OS with at least 8GB of RAM or as specified in the installation for hardware requirements for the components you will be installing.
      • Add at least 30GB of storage or as specified in the installation guide for disk space requirements.
   4. Tag the instance with a name for easy reference, e.g. CONTROLM.
   5. Configure the Security Group as follows:
      • TCP port 22 for SSH access to login to the server
      • TCP port 13075 for Control-M EM CORBA Naming Service
      • TCP ports 13076-13098 for Control-M EM components (or any range of 22 ports)
      • TCP port 18080 for the Control-M EM Web Server
      • TCP port 7105 for Control-M Agent-Server communication
      • TCP port 7106 for Control-M/Server-Agent communication
      • TCP port 2368 for Control-M/Server High Availability, communication between Primary and Secondary
      • TCP port 2369 for Control-M/Server to Control-M EM Configuration Server communication
      • TCP port 2370 for Control-M/Server to Control-M EM Gateway communication
      • TCP port 8443 for Control-M Automation API
      • Open inbound traffic for RDS Oracle/PG or your own MSSQL ports
   6. Review the instance configuration and launch the instance.
   7. Create and Store a Public/Private security key pair for logging in with SSH.
   8. In the Cloud Instance Network, create an Elastic IP address (Public IP) and associate it with your server instance.
2. Log in to the Cloud Services server using SSH by doing the following:
   1. Login user name is Cloud Instance user, not root.
   2. Set the SSH login format as follows:

       ssh -i <path>/<private key file>   <Cloud Instance user>@<public hostname>

   3. Login as root:  sudo su –

   NOTE: you may not be able to SSH from within the company network to the Cloud Services instance. You may need to have IT open the Cloud Services instance IP address for SSH or access the Cloud Services instance from inside the company network.

3. Configure the cloud instance by doing the following:
   1. Create the controlm unix group: groupadd control
      • For Linux environment, it is recommended that Control-M Enterprise Manager and Control-M/Server are installed in its own individual OS accounts.

        Create the Control/EM unix user: useradd –d /home/ctmem –g controlm –s /bin/csh ctmem

        Create the Control/Server unix user: useradd –d /home/ctmserv –g controlm –s /bin/csh ctmserv

      • After installing Control-M/EM repeat steps 4 – 7 below for Control-M/Server. Step 5 should be performed only once on a given machine.
      • Using Full Install:

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

   2. Change permissions in the Control-M/EM and Control-M/Server home directory to 755:

      chmod 755 /home/ctm

4. sftp the Control-M installation image to the Cloud Services server as follows:

   Post Cloud Services only supports sftp and not ftp, however the BMC EPD does not support sftp

   1. Use ftp to transfer the Control-M installation image to a server
   2. Use sftp to transfer the Control-M image to the Cloud Services server
5. Run check_req.sh to verify server by doing the following:
   1. Copy the file check_req_tar.Z from the installation media.
   2. Ensure Korn shell is installed on the system. If not, install Korn shell by running yum install ksh.

      The Korn shell will be needed later for installing fixpacks

   3. Ensure csh, psmisc, bc, flex, io libraries are installed. If not, install the libraries as follows:
      • yum install csh
      • yum install psmisc
      • yum install libaio
      • yum install bc
      • yum install flex

   NOTE: If the following check_req error occurs Not enough free swap space. At least 4GB free swap is required, then the following steps will create a 6GB swap space file but for production systems you should allocate a swap device instead, as follows:

   1. Create the swap file: dd if=/dev/zero of=/swapfile bs=1024 count=6291456
   2. Change the permission of the new swap file: chmod 0600 /swapfile
   3. Setup the swap file with the command: mkswap /swapfile
   4. enable the swap file: swapon /swapfile
   5. Enable it at boot time- edit /etc/fstab to include: /swapfile swap swap defaults 0 0
   6. Verify the swap file space: cat /proc/swaps  or  free

   If the following check_req error occurs Change the kernel.sem (semmni) value to higher or equal to 500 do the following:

   1. To view current settings run: cat /proc/sys/kernel/sem
   2. To change settings run: sysctl –w kernel.sem="250 32000 100 500"
6. Run the Control-M Setup logged in to Control-M account.
7. (Optional) If you need to add a storage volume do the following:
   1. Create the storage volume in Cloud Instance and associate it with the Instance
   2. Log in to the server and create the partition on it using fdisk: fdisk
   3. Create the file system using mkfs: mkfs -t ext4 /dev/xvdb
   4. Mount it to a directory: mount -t ext4 /dev/xvdb  /media/controlm
   5. Add it to the /etc/fstab file so it automatically mounts on reboot.

      For example,  /dev/xvdf               /media/controlm         ext4    defaults        1 2