The following parameters are important when you start jobs under Windows:
The Windows user nameName of the Automation Engine user..
The user's passwordA secret combination of characters for a Automation Engine user..
You can allow a user to use particular loginAn Automation Engine object type that stores account credentials used by agents on target systems. types. The login types interactive and batch can be used. For example, if a user is only allowed to log on via batch, this user can start jobs only in batch mode. The parameter BATCH must be specified in this case.
This option should be specified if the jobAn Automation Engine object type for a process that runs on a target system. that should start expects particular user inputs. The process is then visible for any user who is logged in. This user can enter the required user inputs.
If this option is not specified and the process requires an input, the job hangs and can only be removed by using the taskAn executable object that is running. Tasks are also referred to as activities. manager.
Attributes are defined in the attribute cards of the job.
Depending on the operating system and the agent's start type, there are the following dependencies that apply:
Agent |
INI File | User | BATCH | DESKTOP |
---|---|---|---|---|
Agent on desktop |
logon=0 | 1. | 1. |
1. |
Agent on desktop |
logon=1 | 2. | 2. |
2. |
Agent as a service |
logon=1 | 3. | 3. |
3. |
Note the following peculiarities:
The agent does not load the job's user profile to the registry databaseA database is an organized collection of data including relevant data structures.. That means that a program that stores user-specific data in the registry (for example, the AE Dialog stores the latest logon) cannot access a this data through an AE job.
The start path is a CreateProcess
and CreateProcessAsUser parameter. It is not an obligatory AE parameter. If it is not specified, the agent passes it on to the AE job.
It is important to know that you can specify a start path
in the user definition. This start path is used if a normal interactive
logon is made. Note that it cannot be analyzed when you start the job using AE.
Automic recommends always specifying the start path.
Windows distinguishes four program types.
Types 1 and 2 (GUI and console programs) should be started from the command line if possible. The advantage is that AE can retrieve the correct program exit code.
Type 3 and 4 (DOS programs and OS commands) can only be started through a BAT file. The job ends correctly or incorrectly using the Job Messenger mechanism.
Automic recommends testing the BAT file or the command line on the target system before you start the job via the AE. Use the user who should later execute the AE if possible.
Using graphical programs can always cause unexpected user dialogs (message box). Automic recommends using the option DESKTOP for test runs.
Job reportA report provides more detailed information about a task's execution or a component.: The program output after STDOUT and STDERR is the job report of a Windows job. Usually, only 32-bit console programs and most DOS programs create a job report.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |