Administration Guide > Configuration > Structure of the Configuration Files > Notes for Adjusting Configuration Files

Notes for Configuration-File Adjustments

Adjustments in INI files represent a significant intervention in the AE system and should therefore exclusively be made by the administrator. Trace flags (activating program analysis) should only be used in close cooperation with support and development staff.

All modifications made in INI files are only effective after program restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts.. Exception: No restart is required for modifications made in the section [HOST] of the agents' INI files.

At least the parameters shown below must be supplied with values:  

The entries must correspond 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. and reflect the requirements of the AE system to be created. Some general notes are listed below. Additional notes in the documentation of the relevant INI file is to be considered.

System Name

The system nameName of the Automation Engine instance to which a user is connected. identifies a complete AE environment. Automation EngineThis component drives an Automation Engine system and consists of different types of server processes.s and agents of an AE environment must use the same system name. It can consist of a maximum of 8 figures. Allowed are the upper-case letters A to Z, numbers and "_".

If a new system name is used, it must also be modified in all relevant INI files (Automation Engines and agents). End all running tasks (events, schedules, workflows etc.) before you start your modifications because otherwise, these tasks will not continue after a system name modification.

Note that there is a peculiarity in using the z/OS 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 in combination with SMF technique. The z/OS Event Monitor converts the character "_" if used in the system name to "#".

Server Processes

AE automatically generates server processThe core of the component Automation Engine. Different types are available: communication, work and dialog processes, as well as nonstop processes. names. They consist of the following parts:

Example: UC4G#CP001

Server processes including their process numbers are defined in the INI file of the Automation Engine. At the same time, Server processes are assigned port numbers which must be clearly defined for the entire AE system.

Agent Names

The agent name is limited to 32 of the following characters: "A-Z", "0-9", "_", ".", "$", "@", "-" and "#". It can be defined in its INI file using the parameter name=. The hostComputer, target system. name is used instead if this parameter remains undefined.

Database Access

If an INI file contains information about the connection to the databaseA database is an organized collection of data including relevant data structures. (section [ODBC]), the appropriate passwordA secret combination of characters for a Automation Engine user. should be encoded. Find the description on how to install and use the particular program UCYBCRYP.EXE in the document "Encoding Passwords".

 


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

Copyright © 2016 Automic Software GmbH