Control-M Installation on a Cloud Environment

The following procedures describe how to install Control-M on a Cloud environment:

Installing Control-M on EC2 Linux platform

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

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

Begin

  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 4GB 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 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 –

      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

      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/fstabto include: /swapfile swap swap defaults 0 0

      6. Verify the swap file space:cat /proc/swaps orfree

    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:

    • Create the storage volume in Cloud Instance and associate it with the Instance

    • Log in to the server and create the partition on it using fdisk: fdisk

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

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

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

      For example,/dev/xvdf/media/controlmext4defaults1 2

Installing Control-M on EC2 Windows Platform

The following procedure describes how to install Control-M on EC2 Windows platform, which enables you to use AWS to create a Windows virtual server and to install Control-M.

Before you begin

To install Control-M, do the following to assign AMI a hostname in the format of ‘ip-<hex Internal IP>’, so the AMIs can communicate with each other by private hostname:

  • Launch the EC2 Service Properties

  • Select the General tab

  • Check the Set Computer Name checkbox

Begin

  1. Create a Control-M Supported Windows Operating system (for example Windows 2012 Server instance). For the procedure, please refer to Step 1 in Installing Control-M on EC2 Linux platform, and select the desired Windows OS.

  2. Download Remote Desktop File for Windows instance.

  3. Get a password by doing the following:

    1. Click Get Password

    2. Browse the PEM file and decrypt password

  4. Log in to the Windows Image using Remote Desktop File as follows:

    1. Launch the downloaded RDP file

    2. Type in the username/password

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

    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

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

  6. Run the Control-M 9.0.21 Setup.

  7. Log in to the Control-M Configuration Manager, then create a GUI server, GCS, Web Server and a Control-M/Server.

Installing Control-M on AWS Marketplace

The following procedure describes how to create a Linux based Control-M 9.0.00 environment from AWS Marketplace.

Begin

  1. Create instance by doing one of the following:

    • Create instance from AWS Marketplace as follows:

      1. Log in to the AWS Marketplace, and search by keyword BMC.

      2. Select Control-M (BYOL), and click Continue.

      3. Launch by 1-Click Launch or Manual Launch.

      4. Navigate to Your Software Subscriptions, and Click View Instances.

      5. Find your AWS instance, and click Manage in AWS Console.

        Now, Control-M (BYOL) instance is manageable in AWS Console.

    • Create instance from AWS Marketplace under EC2 Console. This option enables you to customize instances, with an option to assign an existing security group and create brand new pem key file. Do the following:

      1. Log in to the EC2 Console and select AWS Marketplace.

      2. Find Control-M by searching for BMC.

      3. Choose the instance type and configure instance details, add storage, and add tags.

      4. Configure Security Group. You can choose either to create a new security group or select an existing one

      5. Click Launch and select key pair. You can choose either to use the existing key pair or create a new one

      6. Launch Control-M Instance.

Activating Control-M from AWS Marketplace

This procedure describes how to activate Control-M after the Control-M Instance has been created under AWS Marketplace or AWS Marketplace EC2 Console.

Begin

  1. Connect to the created Linux platform.

  2. Follow the prompt to setup the required username/password.

  3. Download and install the Control-M Client from the BMC Control-M website.

    NOTE: Ensure that the connection to Control-M/EM Web Server port at 18080 can be established.

    In order to connect to Control-M instance created from AWS Marketplace, note the following:

    • The ec2-user needs to be used to connect to the Control-M instance.

    • The created pem key file is also used for ec2-user authentication during connection.

    • The Control-M is installed under the user of control.

    • Each AWS instance has its internal (private) name and public DNS, Control-M listens on public DNS only.

    • Switch to controlm user from ecs-user

    • By default, the controlm user has the full administrative permission to manage the installed Control-M.

    • View installed Control-M products using OneInstall installation type.

Updating the DNS Server after Recycling the AMI

This procedure describes how to update the local DNS Server to use the new host name and public IP Address of the Amazon EC2 after recycling the AMI, and publishing Control-M/EM on the new public DNS name.

Amazon EC2 instance host names are derived from the IP address that is dynamically assigned to the instance at startup. Unless the Amazon EC2 instance is allocated with an Elastic IP address (static IP address), the instance will be assigned to a new public IPv4 address after a server restart.

Begin

  1. Stop Control-M/Enterprise Manager Configuration Agent.

  2. Launch the Windows task manager, ensure all the following processes are stopped:

    • emwa.exe

    • emcms.exe

    • emcmsg.exe

    • emgtw.exe

    • emguisr.exe

    • emmaintag.exe

    • eaming_service.exe

  3. Open the cmd.exe console and navigate to path to:

    <Drive:>\Program Files\BMC Software\Control-M EM 9.0.20\Default\bin>

  4. Run the command updateEmPublicHost.bat to update the Control-M/EM with the new IP Address

  5. Start Control-M/Enterprise Manager Server as per normal procedure.