The scriptA particular Automation Engine object type. is processed in a specific way in the object typeAn individual object is provided for the individual activities: There are User, UserGroup, Notification, Cockpit, CodeTable, Documentation, Event, Agent, FileTransfer, Group, Include, Job, Workflow, Calendar, Login, Client, RemoteTaskManager, Schedule, Script, Server, Sync, Variable and TimeZone objects "Job". Depending on the JCL (Job Control LanguageShort form of "Job Control Language". It refers to applications that are processing steps executed on computers.) and the script elements, an executable jobAn Automation Engine object type for a process that runs on a target system. is generated for the respective target system and transmitted via file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object)..
The AE Script (if existing) and the JCL lines are processed and subsequently, the JCL is sent to the target system. AE Script is never sent to the target system.
On Windows the User Account Control (UAC) should be turned off to prevent errors because of missing permissions.
The databaseA database is an organized collection of data including relevant data structures. 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 regularly attempts to establish a connection to the database if its first attempt was not successful. The administrator can define this interval in the INI-file parameter connect=. The job remains in statusThis represents the condition of a task (such as active, blocked, generating). "Active" during these attempts to establis a connection.
The job also remains in status "Active" if the agent is not able to establish a connection because the loginAn Automation Engine object type that stores account credentials used by agents on target systems. data specified in the Login objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task is incorrect. It must be canceled manually either in the Activity Window, using the script functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… CANCEL_UC_OBJECTor directly in the job by monitoring the maximum runtime.
Keep in mind that it is not possible to end commands the agent has been processing in the database at the moment job canceling is initiated. The JDBC interface does not provide this function. Jobs can only be canceled between two commands. Therefore, the agent waits until a command which is just being processed is finalized and cancels the job afterwards. Use the functions of your database Server to cancel ongoing commands.
The administrator can specify the parameter login_check=yes in the MPE agent's INI file. The passwordA secret combination of characters for a Automation Engine user. defined in the Login object is then checked. For reasons of security, Automic recommends using this setting. Login_check=no only checks the user nameName of the Automation Engine user..
The 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. specified in the Login object also owns the job and reportA report provides more detailed information about a task's execution or a component. file. The administrator can assign authorizations for both files using the agent's INI-file parameters JobFileMode= and ReportMode=.
TThe administrator can specify the parameter login_check=yes in the UNIX agent's INI file. The password defined in the Login object is then checked. For reasons of security, Automic recommends using this setting. The setting Login_check=no only checks the user name.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |