By now, we should have a rough idea about what the future batch environment will be like estimated amount of jobs, how many Control-M/Servers, how many Control-M/Agents, Agentless Technology that will or will not be used, which high availability solution will be selected, and so on. It is necessary to document everything and keep it as a standard for future expansion of the environment, but before the actual installation starts, we also need to make sure the machines are meeting the Control-M pre-installation technical requirements.
Control-M components are designed to be installed on a wide range of computer system environment. Choosing the right operating system type, version, and machine architecture is the first step in building a stable Control-M batch environment. It is good to utilize the latest technology, but we must check the compatibility information listed on each product's release note or visit the Product Availability...