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

Depot hierarchy ............................................................................................................................... 3

Job Hierarchy ................................................................................................................................... 5

Configuration File Objects.................................................................................................................... 6

Unix Installation Steps ......................................................................................................................... 7

Linux DMZ clean install flow with screenshots ..................................................................................... 8

Batch Job with all steps .................................................................................................................... 8

Install check ..................................................................................................................................... 9

Add ctmagent service to /etc/services ........................................................................................... 10

Add ctmagent local account ........................................................................................................... 11

Copy install files since you can’t mount back to production from DMZ ........................................... 13

Silent install commands ................................................................................................................. 14

Create automatic startup script links.............................................................................................. 14

Remove install files ........................................................................................................................ 15

Update the CONFIG.dat entries for DMZ. ....................................................................................... 15

Standards for Depot and Job structure a. Create a consistent hierarchy structure

b. Evaluate the structure of the Source installation files

i. Download the installation files

ii. Place them in a directory on the BladeLogic Application Server share

iii. Directory will be copied or mounted for source directory

c. Hierarchy used in this document

i. Applications

ii. Application Name (Control-M)

iii. Specific OS folder (AIX, Solaris, HPUX, Linux, Windows)

iv. Common Unix

Depot hierarchy

Top Level for Control-M Agents

Specific OSes and Common Unix

Job Hierarchy

Configuration File Objects Connect to a server that already has a Control-M Agent installed to create the configuration file objects

for CONFIG.dat and installed-versions.txt. You will need configuration file objects for each different

Unix/Linux OS using name space value grammar (nsvp_space.gm). Once created, it will appear under the

Configuration branch for each server with a Control-M Agent.

Folder

Example server

Unix Installation Steps a. Remove any older 32 bit agents since they can’t be upgraded to 64 bit. Depending on

the use case, you may need to leverage 32 bit agents. For example, some Control

Modules are still only 32 bit on specific OSes.

i. Run shut-ag scripts

ii. Verify no more p_ctm* processes are running. This may indicate multiple

instances of the agent, so validate installation and configuration files.

iii. Archive sysout directory, if sysadmins would like to validate prior jobs.

iv. Delete the directory

d. Review prerequisites from installation documents

i. Check for sufficient disk space

ii. Check Install Path

iii. Check group membership

iv. Check user account

v. Add Control-M service to /etc/services

b. Actual install

i. File location

1. Mount for Production servers

2. Copy for DMZ servers

ii. Platform specific setup.sh calls silent install file

c. Setup automatic startup script links

d. Run Config.dat updates if needed.

e. Delete any temporary directories created for the installer

Linux DMZ clean install flow with screenshots

Batch Job with all steps

Install check

This must be a local directory and not NFS as per the installation documentation. Since this is a clean

install, the script fails and exits with a return code if the directory already exists.

Add ctmagent service to /etc/services

Add ctmagent local account

i. Add local controlm group

ii. Create /bmc/local/apps/controlm

iii. Create /bmc/local/apps/controlm/ctmagent

iv. Update permissions

v. Create actual user

Copy install files since you can’t mount back to production from DMZ

Network path to source

Silent install commands

(Generate silent installer XML via interactive installation)

#!/bin/sh

cd /bmc/local/apps/controlm/ctmagent &&

/bmc/local/apps/controlm/ctm8install/blswin/controlm/DRKAI.8.0.00/UNIX/Linux-i386/setup.sh -silent

/bmc/local/apps/controlm/ctm8install/blswin/controlm/DRKAI.8.0.00/controlm-install-user.xml

Create automatic startup script links

Remove install files

Update the CONFIG.dat entries for DMZ.

Each configuration entry is on a separate line. The Name and Value0 match the left hand side. Value1

matches the right hand side of the file. DMZ hosts will need to have ALLOW_COMM_INIT set to N and

PERSISTENT_CONNECTION set to Y. You will also need to update the settings in Control-M Configuration

Manager so that the Control-M Server initiates the connection to the DMZ server.