User Guide > Objects > Alphabetical Listing > Attributes Tab

Attributes Tab

The Attributes tab is objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task-specific and is only available in Agent objects. You can specify the license category that should be used in this tab.

Object: Agent
Object class: System object

Object type (short name): HOST 

Description

Field/Control Element

Description

License Category

The License Category that should be used by the 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 can be selected here. Allowed values are Production and Test, depending on whether the agent runs in a production or non-production 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..

Trustable IP-Addresses

If your AE system runs with encryption, you can specify IP addresses (separated by semicolons) from which the agent accepts non-encrypted connections.

Communication to components such as the Job Messenger, Event Monitors (BS2000, z/OS) or the Output Collector (NSK) takes place without encryption. By default, the agent accepts non-encrypted messages from the local hostComputer, target system. (127.0.0.1) and its own IP address.

If Event Monitors on z/OS are used in LPARs on different computers, you must specify the relevant IP addresses here.

Releasing individual IP addresses is only reasonable if the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. should always reject loginAn Automation Engine object type that stores account credentials used by agents on target systems. attempts of former agent versionsAn application version holds zero or more deployment packages and may have dependencies to zero or more application versions of the same (or to different) applications (see "Compatibility").

ServiceManagerA program that facilitates the starts and stops of Automation Engine components. Record

The settings that are defined here are required for the connection between the agent and a ServiceManager. Agents can so start directly via the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."] (System Overview) or by using the scriptA particular Automation Engine object type. element MODIFY_SYSTEM.

All values will automatically be replaced if the search for a corresponding ServiceManager service was successful. This search can be opened by using the"Refresh ServiceManager Scan" command in the System OverviewThe UserInterface window that contains information about the Automation Engine system.'s context menu. The default port number 8871 is used for the scan unless a different specification is provided in the setting SMGR_PORT_RANGE of the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_SYSTEM_SETTINGS.

Phrase Name of the ServiceManager environment.
Name Name of the service in the agent's ServiceManager .
Port Port number of the ServiceManager.
Linked to ServiceManager

Links the agent with the ServiceManager.

This specification is automatically set if the ServiceManager scan for the agent was successful. With this option being deactivated, you can no longer start the agent via the System Overview nor by using MODIFY_SYSTEM.

 

 


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

Copyright © 2016 Automic Software GmbH