How to create BMC Server Automation(BSA) configuration file, depot and job objects for deploying new Control-M Agents on Unix/Linux servers This document details the steps needed to create automatic installation BSA packages for deploying new Control-M Agents. In order to create these packages, the BSA and Control-M administrators will need to work together as knowledge of both products is required. These steps use temporary directories for the installation files, but this is normally only needed for DMZ servers as you can remotely mount the BSA server share as the source directory. Likewise, the CONFIG.dat updates are only required for DMZ servers. These steps also assume local entries for the Control-M Agent user account and group, but you could also LDAP and NIS instead. Steps for a clean install are documented, but you could modify the package for upgrades by removing steps for creating the user, group, local directory, and startup scripts.
15
Embed
How to create BMC Server Automation(BSA) for deploying … · How to create BMC Server Automation(BSA) ... i. Add local controlm group ii. ... Created Date: 3/2/2014 3:06:29 PM ...
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
How to create BMC Server Automation(BSA) configuration file, depot and job objects for deploying new Control-M Agents on Unix/Linux servers
This document details the steps needed to create automatic installation BSA packages for deploying new
Control-M Agents. In order to create these packages, the BSA and Control-M administrators will need to
work together as knowledge of both products is required.
These steps use temporary directories for the installation files, but this is normally only needed for DMZ
servers as you can remotely mount the BSA server share as the source directory. Likewise, the
CONFIG.dat updates are only required for DMZ servers. These steps also assume local entries for the
Control-M Agent user account and group, but you could also LDAP and NIS instead. Steps for a clean
install are documented, but you could modify the package for upgrades by removing steps for creating
the user, group, local directory, and startup scripts.
Table of Contents Standards for Depot and Job structure ................................................................................................ 3