Agent Pre-installation Procedures for UNIX

Before you install Control-M/Agent on UNIX, you must perform the following procedures:

• Configuring a User Account on UNIX: Describes how to configure specific parameters for an Agent.

• Setting the Java Environment Variable: Describes how to set the Java environment variable, which points to an external Java installation.

• Verifying Operating System Levels and Patches: Describes how to verify the operating system levels and patches with Agent requirements.

• Verify that your host has outgoing HTTPS access (port 443) to the following URLs, as described in Agent Management:

  • *.controlm.com:443

  • *.amazonaws.com:443

Configuring a User Account on UNIXLink copied to clipboard

This procedure describes how to configure a user account on UNIX with specific parameters for Control-M.

Before You Begin

• The account cannot contain any data, it must be solely dedicated to the Agent, and the account name cannot exceed 30 characters.

  The user profile is replaced during the installation.

• The Agent Run as User An OS account name that is used to execute jobs on the host. can be a local, LDAP, or NIS user.

• The Agent account home directory can be located on a local disk or Network File System (NFS).

  Plug-ins A Control-M component that extends functionality to third-party applications like Hadoop or SAP and can be integrated with other jobs in a single workflow. are not supported on NFS directories.

Begin

1. Do one of the following:

   • Run the following command to create a user account:

     /usr/sbin/useradd -u <numeric_user_id> -g <user_group> -d <user_home>

   • Run the following command to create a group:

     /usr/sbin/groupadd <user_group>

     The <user_shell> account must be defined as one of the following names or programs:

     • /bin/csh

     • /bin/sh

     • /bin/ksh

     • /bin/bash

     • /bin/tcsh

2. Configure the predefined limits that are designed to prevent excessive resource utilization by a single process, as described in Control-M Limits on UNIX Accounts.

3. Do the following to verify that the HOST environment variable is defined on all shells:

   1. Run the following command: 

      env

   2. If the HOST environment variable is not defined, contact your system administrator.

4. Do the following to verify that the HOME directory is configured with 755 permissions

   1. Run the following command on the Agent account:

      Is Id

      ls -ld /home/ctmag

      drwxr-xr-x 25 ctmag users 4096 Dec 2 13:47 /home/ctmag

   2. If the permissions are not set to 755, run the following command to set them:

      chmod

      chmod 755 /home/ctmag

Control-M Limits on UNIX AccountsLink copied to clipboard

The following table describes Control-M limits on UNIX accounts. If you install Control-M components in separate accounts, each account must have the minimum ulimit limit settings. The soft or hard kernel setting must reflect the sum total that is required by each account.

Parameter	Description
datasize	Determines the maximum size of the data segment of a process. BMC recommends that you define this value as unlimited.
stacksize	Determines the maximum size of the stack segment of a process. BMC recommends that you allocate 8 MB on all UNIX hosts.
coredumpsize	Determines the maximum size that a core dump can reach. BMC recommends that you define this value as datasize, which enables you to generate a complete core dump if a failure occurs.
descriptors	Determines the maximum number of descriptors that a single process can use. BMC requires the value of 4,096. Do not set the parameter value to unlimited.
memoryuse	Determines the maximum amount of memory to be used by a single process. BMC recommends setting this value to unlimited.
maxproc	Determines the maximum number of user processes. Default: 4,096

Verifying Operating System Levels and PatchesLink copied to clipboard

This procedure describes how to verify the operating system levels and patches with Control-M requirements.

Begin

1. Download the archived CheckReq utility file.

2. Log in to the host as an Agent user.

3. Extract the archived CheckReq utility file to the required directory.

4. Run the following command:

   checkReqRun.sh

5. Follow the on-screen instructions.

   If the operating system and patches meet Control-M requirements, a dialog appears which states that the product can be installed.

   Otherwise, a list of missing requirements appears.

   If the checkReqRun.sh utility alerts you about a missing patch or library (such as libnsl), check with your system administrator to determine whether this patch or library is included in one of the bundled packages that are installed on your host.