Default values have been specified for most parameters. They can be changed if required. Parameters that must be adjusted to your system environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. are written in red letters.
The INI-file sections [USERID] and [UC_USER] only affect UNIX jobs. They do not affect FileTransfers or FileSystem eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase. objects.
The following is valid for the target hostComputer, target system.: Regardless of the parameters that have been set the UNIX agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host also considers links in file paths. The following conditions apply:
The behavior of the source host is controlled by the parameter FT_Linkfiles.
Section/Parameter | Description |
---|---|
[GLOBAL] | |
name= | The name of the agent.
The agent name is limited to 32 of the following characters: A-Z, 0-9, _, ., $, @, - and #. The host name is used instead if this parameter remains undefined. Lowercase letters are converted to uppercase letters. Hyphens ("-") are only allowed in agent names. They must not be used in the names of any other objects. |
system= |
The name of the AE system. |
logging= | The path and file name of the log file.
The xxx characters in the file
name are placeholders. They stand for the three-digit abbreviation of
the respective UNIX version. The number signs serve as placeholders for a series in numerical order. When you start the agent, the log files are renamed so that the most current log file is always the one with the number 00. |
logcount= | The number of stored log files. |
helplib= | The name of the message file. |
licence_class= | The license class that corresponds to the acquired license
and the hardware and software that you use. Allowed values: 1-9, S, V 1 - 9 = The agent's license class. S = The agent that is used for administration tasks on the Server computer. V = The agent's virtual license class. |
language= |
The language that should be used for the logging. You can specify a primary and a secondary language. Allowed values: "E", "D",
"F" If there is no message in the primary language, the system searches for a message in the secondary language. |
open_file_max= |
Sets the users 'open file descriptor' limit. A value of 0 forces the agent to set the users soft limit to the existing users hard limit. A value not equal to 0 forces the agent to set the soft limit and the hard limit to that value. If the value exceeds the users existing hard limit, the agent even sets that value, if it is operated with root privilegesPrivileges in the Automation Engine refer to user rights to work with certain frontend and user interface functions. You grant privileges to users in the Automation Engine.. If the value exceeds the users existing hard limit and the agent is not operated with root privileges, the agent cannot exceed the hard limit and sets the users soft limit to the users hard limit. Default value: 32768 |
userid_type= | You use this parameter to allow or reject certain users.
Allowed values: INCL, EXCL (default value) INCL = Access must be granted to every single userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. in the [USERID] section. |
UC_user_type= | The option that can be used to allow or reject particular AE users.
Allowed values: INCL, EXCL (default value) INCL = Access must be granted to every single user in the [UC_USER] section. |
rcv_max= | The time period in seconds during which the agent waits for the
rest of a partially received message. After this period of time,
the connection is considered as interrupted. Automic recommends keeping this time period short.
Default value: 30 seconds |
Password check. Allowed values: yes and no (default value) See: Description of the settings ANONYMOUS_FT and ANONYMOUS_JOB in the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_HOSTCHAR_DEFAULT). |
|
ReportMode= |
A mask in three octal digits that you can use to assign additional rights to the jobAn Automation Engine object type for a process that runs on a target system. reportA report provides more detailed information about a task's execution or a component. file. Default value: 600 The default value is the minimum value. The value 6 is used even if you specify an ownerEntities are owned by a specific user or team. Only this user//users inside the team may change the entity. authorization level below this value. |
JobFileMode= |
A mask in three octal digits that you can use to assign additional rights to the job file. Default value: 700 The default value is the minimum value. The value 7 is used even if you specify an owner authorization level below this value. |
FT_Owner= |
The owner of file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object). files. Allowed values: "user" (default value) and "directory" "user" - The user who is defined in the Login objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task is the file owner (User ID) of the transferred file(s). The owner of existing files that might be overwritten is kept."directory" - The transferred file(s) obtein the owner of the target folderTop level entities such as Environment, Deployment Target, Activity, … are stored in folders. The permissions a user has on an entity depend on the permissions that are set on the folder for the entities.. The same rule applies for existing files that are overwritten. This parameter does not affect file rights or the groupAn Automation Engine object type that integrates tasks so that they can be processed together.. The new file transfer protocol (source and target agent are of version 9 or later) ignores this parameter. In this case, the owner is always the user who is defined in the Login object. |
ReadUserAlways= |
You allow or reject User IDs by using the parameter userid_type= in the [USERID] section. You can use the parameter ReadUserAlways= in order to specify whether this section should always be read before a job starts or only once when the agent starts. Reading this section only once improves the performance of your system and is therefore the default value. Allowed values: yes and no (default value) yes = The agent always reads the [USERID] section before a job starts. |
KillSignal= |
The signal that is sent to the job if it is canceled through the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."]. Allowed values: SIGTERM, SIGABRT and SIGKILL (default value) SIGTERM - The job is terminated (15). |
ft_temp_file= |
This parameter creates temporary files in file transfers. Allowed values: yes (default value) and no yes = The file obtains a temporary
name which is composed of the letter T and an alphabetic string
that originates from the RunIDShort for "run number". It is a number that provides unique information about a task's execution. The RunID can include 7 to 10 digits. It is assigned by the Automation Engine component .. The new file transfer protocol additionally appends a file ID in order to obtain a unique file name because basically, only a RunID is provided. The file is renamed after it has successfully
been transferred. |
tcp_nodelay= |
Nagle algorithm usage for file transfers and all the agent's other sockets. Allowed values: yes (default value) and no no = Activates the Nagle algorithm. Activating the Nagle algorithm can improve the performance of file transfers, especially if you transfer many small files. The BS2000 agent always uses the Nagle algorithm. Therefore, it does not include this INI-file parameter. Note that this parameter should only be set in close cooperation with Automic Support! |
FileProcessingTimeout= |
The time limit in second for the file search The file search aborts when the specified time limit is reached. No time limit applies when you either define the setting "0" (default) or "-1". This parameter is relevant for FileSystem events and the scriptA particular Automation Engine object type. element GET_FILESYSTEM. |
FileProcessingMaxDepth= |
The maximum level of sub-directories for FileSystem events. You use this setting in order to determine the extent to which the directory structure is included in your search for FileSystem event files. The search directory serves as the basis for the maximum sub-directory level. By limiting the directory level, you can improve the performance of FileSystem events especially when their folder structure is deeply nested and includes numerous files. Allowed values: This parameter is relevant for FileSystem events and the script element GET_FILESYSTEM. |
[AUTHORIZATION] | |
InitialPackage= |
The name and the path of the file that includes the authentication package (company-key file). This parameter must be specified if you use the authentication methods "Server" or "Server and Agent". Any attempt to log in fails if the company-key file cannot be found. When the agent starts, it reads the company-key file and stores its information in the file that is specified in the parameter KeyStore=. The first file is deleted afterward. |
KeyStore= |
The name and the path of the file that includes the information of the authentication packageA Package is an instance (a version, a revision, a tag, …) of your application and defines the content which you want to deploy. Here you decide, if you want to deploy the entire application or just a few specified components. (see parameter InitialPackage=). If no file name and/or path is specified, the system uses the name (file ending *.kstr) or the path of the agent's INI file. If you define a file name, the ending *.kstr is not automatically appended. The KeyStore file is created when the agent starts for the first time. You must not delete, rename or move it subsequently. Regardless of the authentication method that you use, any attempt to log in will fail if the agent cannot find this file when it starts. In this case, you must open the menu item "Renew transfer key" in the affected agent's System Overview. |
[USERID] |
The definition of the authorized UNIX users in the format: Definition of the non-authorized UNIX users in the format: Default value: root=NO_START |
[UC_USER] | The definition of the authorized AE users in the format: User ID=START The definition of the non-authorized AE users in the format: The User ID (OH_IDNR) of each user is registeredThis is the status of a task that runs within a group and is waiting for its start. in the AE databaseA database is an organized collection of data including relevant data structures. in the OH table. |
[FILETRANSFER] | |
ft_check_free_disk_space= |
This parameter checks the available hard disk space before a file transfer is processed. Allowed values: Checking the available space of network drives may occasionally lead to an incorrect result. |
FT_Linkfiles= |
By using the parameter FT_Linkfiles you control, if the agent should transfer linked files of the source or ignore them. Allowed values: Executing a Wildcard-FileTransfer with "no" as value, may result in the transfer being set to ENDED_EMPTY, in case there are only links in the source directory. |
[VARIABLES] |
This section contains the agent variables that include agent settings and information. |
[TRACE] | |
file= | The path and the file name of the trace file.
The xxx characters in the file
name are placeholders. They stand for the three-digit abbreviation of
the respective UNIX version. The number signs serve as placeholders for a series in numerical order. When you start a trace, the trace files will be renamed so that the most current trace file is always the one with the number 00. |
trccount= | Number of the stored trace files. |
tcp/ip= event= job_debug= ft_debug= ex_init= signal= mail= memory= |
The trace flags of the agent.
Allowed values: 0 (default value) to 9 Trace flags must only be used in close cooperation with Automic Support. |
[HOSTS] |
Assignment of an agent's name to its address (DNS name or TCP/IP address) if it cannot directly be accessed through the address that is stored in the server. Specify several assignments line by line, there is no upper limit for the number of assignments. In file transfers, the sending agent obtains the destination agent's internal address from the Automation Engine. The sending agent replaces this internal address by the external address that is defined here. This setting is only required if you run file transfers with agents that cannot directly establish a TCP/IP connection between each other by using the address that they have received from the Server. This can happen if the agents that are involved in the file transfer are located on different networks or if a firewall is used.
|
[TCP/IP] |
|
port= | The port number of the agent.
Other agents and the Job Messenger use this port number in order to establish a connection. |
bindaddr= |
The IP address or host name for the connection to the agent. You can use this parameter if a specific IP address should be used for the connection (if the computer has more than one network interface card). Alternately, you can also specify the IP address or host name in port= (Format: port=IP address:port or DNS name:port). Specifications that are made in bindaddr= are ignored in this case. |
bindlocal= |
The consideration of the local host (127.0.0.1). This parameter must be used in combination with bindaddr=. Allowed values: 0 (default value), 1 0 = No listen socket is created. |
connect= |
The ime interval in seconds in which the agent tries to establish a connection to the Automation Engine. This setting affects the connection establishment for a restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts. of when the connection has been lost. The former parameter name agent= is still valid for compatibility reasons. |
maxrepcnt= |
The maximum number of report blocks that should be transferred to the Automation Engine at the same time. Default value: 8 blocks |
maxMsgSize= |
Maximum length of messages (in bytes) that the agent accepts. Default value: 500 000 |
cp= |
The address of the communication processA communication process is part of the component Automation Engine. It is responsible for connecting the components. in the AE system to which the agent should connect. Allowed formats: |
tcp_keepalive= |
This sends keep-alive packets in order to keep the agent connections. Allowed values: "N" and "Y" (default value)
This parameter is only checked when the agent runs under Linux. |
tcp_keepalive_time= |
The time interval in seconds in which packagesDelivery package, a bundle of functionality. for keeping the connections are sent. The default value that depends on the system environment is used if you do not specify this parameter or use the value 0. |
SendBufferSize= |
Size of the TCP/IP input buffer for messages that should be sent (MB, KB or bytes). Bytes are used by default. Alternately, you can also append the letter "K" or kilobytes or "M" for megabytes to the number. You can use uppercase or lowercase letters for this purpose. Examples (the following definitions are identical): Default value: 1 Mbyte |
RecvBufferSize= |
Size of the TCP/IP input buffer for messages that should be received (MB, KB or bytes). Bytes are used by default. Alternately, you can also append the letter "K" or kilobytes or "M" for megabytes to the number. You can use uppercase or lowercase letters for this purpose. Default value: 1 Mbyte |
[MISC] |
|
FileBufferSize= |
Size of the input buffer for files that are transferred with a FileTransfer object (MB, KB or bytes). Bytes are used by default. Alternately, you can also append the letter "K" or kilobytes or "M" for megabytes to the number. You can use uppercase or lowercase letters for this purpose. Default value: 0 (The OS setting is used). |
authentification= |
Authentication method for the login data in the Login objects of the jobs and file transfers. Allowed values: local (default) and PAM local = OS calls PAM authentication is only supported for agents that run on AIX, Linux and Sun Solaris. |
TraceFileSize= |
The maximum size of a trace file. The agent creates a new file if this value has been reached. Bytes are used by default. Alternately, you can also append the letter "K" or kilobytes or "M" for megabytes to the number. You can use uppercase or lowercase letters for this purpose. |
FileEndDelimiter= |
This adds a line breack (LF) at the end of text files that have been sent using a file transfer. Allowed values: "yes" and "no" (default value) "yes" - The agent always adds an LF to the end of text files in file transfers in which it is the receiving agent.e It is irrelevant whether the files already end with an LF. |
processinfo= |
Collection of process information. Allowed values: yes (default) and no yes = The agent retrieves the process information of all AE processes and sends it to the Automation Engine for the periodic job check. By doing so, the consumed CPU time is refreshed in the UserInterface. Note that this can negatively affect CPU and performance if many active processes are involved.
This parameter is not available for AIX. |
MsgStdout= |
Logging output in the terminal that is used to start the agent. Allowed values: yes and no (default) yes = The agent's logging data is output in the console. An additional log file is written. |
FileRemoveCheck= |
Authorization check before the source file is deleted. Allowed value: yes (default value) and no yes - The user's authorization to delete the source file is verified. |
[PAM] |
|
Libname= |
Path and filename of the PAM library. Specify the library name if the PAM authentication methodshould be used (see also parameter authentication=) By default, the file libpam.so is searched in the agent's directory. This parameter is only relevant for AIX, Linux and Sun Solaris agents. |
pam_open_session= |
If turned on and PAM authentication is used, a PAM user session is opened for each job also applying the session credentials by PAM (e.g. limits defined in /etc/security/limits.conf). This setting applies to jobs, but not FileTransfers or file events. Allowed value: yes and no (default value) |
[STARTCMD] |
|
start_type= | Method that is applied to start jobs.
Allowed values: fork (default value), batch fork = The job starts with fork functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,…. |
Bourne_Shell= | Shell options for starting jobs under Bourne Shell.
You can use this line if jobs should be started with a batch command. |
C_Shell= | Shell options for starting jobs under C Shell.
You can use this line if jobs should be started with a batch command. |
Korn_Shell= | Shell options for starting jobs under Korn Shell.
You can use this line if jobs should be started with a batch command. |
Other_Shell= |
Shell options for starting jobs under any Shell.
|
shell_pfad= |
The specification of a specific Shell path. The environment variable PATH is used if you do not specify this parameter. If this variable is not available, the system uses the "/bin" directory. |
[CP_LIST] |
List of communication processes. This listShows entities in a grid view is created when
the agent starts and it is extended when new communication processes are
activated. The communication process that is defined in the parameter cp= ( [TCP/IP] section) is not included in the cp list. Format: |
[GLOBAL]
name = UNIX01
system = UC4
logging = ../temp/UCXJxxx.l##
logcount = 10
helplib = ucx.msl
licence_class = V
language = e,d
userid_type = EXCL
UC_user_type = EXCL
; rcv_block = yes
; rcv_max = 30
login_check=yes
ReportMode=600
JobFileMode=700
ReadUserAlways=no
KillSignal=SIGKILL
ft_temp_file=yes
[AUTHORIZATION]
InitialPackage=
KeyStore=
[USERID]
;root = NO_START
[UC_USER]
; 6 = START
; 7 = NO_START
; ft_check_free_disk_space=yes
; standard : ft_check_free_disk_space=no
; FT_Linkfiles=yes
; standard FT_Linkfiles=no
[VARIABLES]
UC_HOST_CODE = UC_CODE
UC_HOST_JCL_VAR = UNIX
UC_EX_PATH_BIN = ./
UC_EX_PATH_JOBREPORT = ../out/
UC_EX_PATH_TEMP = ../temp/
UC_EX_JOB_MD = ucxjxxxm
[TRACE]
file = ../temp/UCXJxxx.t##
trccount = 10
tcp/ip = 0
event = 0
job_debug = 0
ft_debug = 0
ex_init = 0
signal = 0
mail = 0
[HOSTS]
; <AE-name>=<dns-name> or
; <AE-name>=<ip-addr>
[TCP/IP]
port = 2220
alarm = 30
maxrepcnt = 8
cp = PC01:2217
[MISC]
authentification=PAM
FileEndDelimiter=yes
processinfo=yes
[PAM]
Libname=libpam.so
pam_open_session=yes
[STARTCMD]
; start_type = batch
; Bourne-Shell = nohup batch < \`su - &user -c "&jobFile 1>> &jobReport 2>&1"\`&
; C-Shell = nohup batch < \`su - &user -c "&jobFile >>& &jobReport"\`&
; Korn Shell = nohup batch < \`su - &user -c "&jobFile 1>> &jobReport 2>&1"\`&
; Other-Shell = nohup batch < \`su - &user -c "&jobFile 1>> &jobReport 2>&1"\`&
; Only for SunOS 5.4 (US4):
; [STARTCMD]
; Bourne-Shell = batch < \`su - &user -c "nohup &jobFile >> &jobReport 2>&1"\`&
; C-Shell = batch < \`su - &user -c "nohup &jobFile >>& &jobReport"\`&
; Korn Shell = batch < \`nohup su - &user -c "&jobFile >>& &jobReport 2>&1"\`&
; Other-Shell = batch < \`nohup su - &user -c "&jobFile >>& &jobReport 2>&1"\`&
[CP_LIST]
2218=PC01
See also:
Notes for Configuration-File Adjustments
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |