Agent Pre-installation Procedures for UNIX

Before you install Agents A Control-M component installed on a host (computer) that runs and monitors the jobs on the host., you need to complete 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 operating system level and patches with Agent requirements.

The Agent communicates with the Server using an HTTPS protocol (port 443). If your organization blocks access to the Internet, you must contact your Network administrator to grant outgoing access to the following locations:

*.controlm.com:443 (HTTPS protocol) (Outgoing only)
*.amazonaws.com:443 (Outgoing only)

Configuring a User Account on UNIX

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, must be solely dedicated to the Agent, and the name must not 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 user, an LDAP user, or an NIS user.
The Agent account home directory can be located on a local disk or 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).

Begin

Do one of the following:
- Create a user account, as follows:
  
  /usr/sbin/useradd -u <numeric_user_id> -g <user_group> -d <user_home>
- Create a group, as follows:
  
  /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
Configure the predefined limits that are designed to limit or prevent the excessive use of resources by a single process, as described in Control-M Limits on UNIX Accounts.
Verify that the HOST environment variable is defined on all shells by running the env command.

If the HOST environment variable not defined, contact your IT system administrator.
Verify that the HOME directory is configured with 755 permissions by running Is Id on the Agent account.

ls -ld /home/ctmag

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

If the permissions are not set to 755, you can use the chmod command to set it.

chmod 755 /home/ctmag

Control-M Limits on UNIX Accounts

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 computer kernel soft or hard setting must reflect the sum total that is required by each account.

The limit parameters are listed in the context of CSH/TCSH. If you are using a different shell type, refer to your designated shell help documentation for the equivalent limit values for your shell type.

Parameter	Description
datasize	Determines the maximum size of the data segment of a process. BMC recommends setting this value to unlimited.
stacksize	Determines the maximum size of the stack segment of a process. BMC recommends 8 MB on all UNIX computers.
coredumpsize	Determines the maximum size that a core dump can reach. BMC recommends setting this value to datasize to generate a complete core dump if a failure occurs.
descriptors	Determines the maximum number of descriptors in use by a single process. 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 Patches

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

Begin

Download the Check_req utility.
Log in as an Agent user.
Extract the tar file and type the following command:

checkReqRun.sh
Complete the instructions as necessary.

If the operating system and patches meet Control-M requirements, you are advised that the product can be installed. Otherwise, a list of missing requirements appears.

If the script alerts you to a missing patch or library (such as libnsl), check with your system administrator to see if the patch or library is included in one of the bundled packages that are installed on your computer.