Administration Guide > Configuration > Structure of the Configuration Files > Utility for OS/400

Utility for OS/400

Structure of the INI File

Section/Parameter Description
[GLOBAL]   

system=

The name of the AE system.

This entry must be identical to the entry in the INI file of the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes..

helplib=

The name of the message file.

language=

The language in which the logging is processed. Entries for primary and secondary language.

Allowed values: "E", "D", "F"
Default: "E,D" (Primary English, secondary German)

If there is no log in the primary language, a log in the secondary language is searched for.

logging=

logcount=

The OS/400 CallAPIA programming interface that processes a script in the Automation Engine system. It can be called directly from within the program itself or from a different program. writes output to JobLog instead of a log file and standard out. Therefore, these parameters are ignored in the INI file for OS/400.

timeout=

The time in seconds during which the CallAPI waits for a response from AE. If this is exceeded, the CallAPI ends with a timeout error.

Default value: 60

With the parameter timeout=0 being used, the CallAPI waits (without time limit) until the Automation Engine acknowledges.

queueA particular Automation Engine (AE) object type. In AE, a queue determines the maximum number of concurrent tasks, their priorities and the order in which tasks should be executed. In ARA, queues are containers for workflow executions that should be executed at a certain time one after another.=

The specification of a particular Queue objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task in which the CallAPI should be executed.

This parameter overrides the setting API_QUEUEin the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_CLIENT_SETTINGS.

TRACE

Trace designation.

Allowed values:
"0" (default) = Deactivate trace
"1" = Activate trace

If the trace parameter is set to 1, additional information is written to STDOUT

[USER]

 

clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type.=

Login specifications: Client.

Login data from this section is used when no logon data is specified at service-program call

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.=

Login specifications: The name of the user.

dept=

Login specifications: The departmentDepartment name to which the Automation Engine user belongs. of the user.

pass=

Login specifications: Password (optional).

[CP_LIST] or [CPLIST]

The address of the communication processes in the AE system.

Allowed formats:
Port number=DNS Name
Port number=TCP/IP Address

Example of an INI File

[GLOBAL]
system=UC4
helplib=UC4/MSL
language=E,D
timeout=60
;queue=

TRACE=1



[USER]
client=
user=
dept=
pass=


[CP_LIST]
2217=uc4srv01
; 2218=uc4srv02

 

See also:

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH