The Login tab is 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-specific and is only found in the "Login" objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task. You can define loginAn Automation Engine object type that stores account credentials used by agents on target systems. data that is required by jobs and file transfers for logging on to operating systems and applications here.
Object: Login
Object class: System object
Object type (code designation): LOGIN
Field/Control | Description |
---|---|
Name |
The name of 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 or the backend system. You can select the agent from a dropdown listShows entities in a grid view. The list includes all the installed agents of the AE system. You can also directly enter a value in this field. This is required for specifying the name of a backend system (such as a Version ManagementThis refers to an object version that is stored when you have modified the object. system). Then you select the related system type in the "Type" column. It is the administrator who defines the system types (variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_LOGIN_TYPES). When you select "*", the selection is not limited to the name. In this case, you must always specify the type. The login information of this line then applies to all the agents / systems of the selected type. Lines that include a unique name are given preference to "*". |
Type | The platform of the agent or type of the backend system. The hostComputer, target system. type will automatically be set and cannot be changed when you select a particular agent. Specific host types: ILMStands for Information Lifecycle Management, which refers to a wide-ranging set of strategies for administering storage systems on computing devices. (only selectable in system 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. 0000) RA agents: Note that you must select the name of the solution. The administrator can define additional types for Login objects in the variable UC_LOGIN_TYPES. These types can be selected in the column when you either define "*" or any value for the name. |
Login info |
Login information to be used for logging on is specified here. Login information must be defined in the format which is suitable for the particular operating system or applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity.. Note that there can be platform-specific peculiarities. |
Password |
Login passwordA secret combination of characters for a Automation Engine user. shown with hidden characters. Maximum 20 characters MPE is an exception. 3 passwords can be specified. The password plus separators must not exceed 62 characters. Passwords must not include commas, regardless of the platform you use. |
Login information can be read using the scriptA particular Automation Engine object type. functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… GET_ATT and the corresponding job attributes.
Operating system / Application |
Format |
Conversion to capital letters |
---|---|---|
BS2000 |
entire field |
|
Database |
none |
|
GCOS8 |
user ID |
entire field |
JMX |
user name |
none |
MPE |
user ID.account[,groupAn Automation Engine object type that integrates tasks so that they can be processed together. name] |
entire field |
NSK |
Group name.user ID |
none |
Oracle Applications |
user name |
none |
z/OS |
user ID |
entire field |
OS/400 |
user ID |
entire field |
PeopleSoft |
Operator ID |
none |
SAP (ABAP Engine/Business Intelligence) |
Client,user ID |
none |
SAP (Exchange Infrastructure) |
XI user ID |
none |
UNIX |
user ID |
none |
VMS |
user ID |
entire field |
Windows |
domains\user ID |
domains only |
J2EE/JMX
Usually, it is only required to specify one password. Three passwords must be indicated (separated by commas) if WebSphere version 6 with the activated administrative security is used:
Oracle Applications
In Login objects, an internal OA user must be specified who should be used for processing jobs. By contract, a valid OA databaseA database is an organized collection of data including relevant data structures. user must be specified in the object ERP_LOGIN.
Windows
"*OWN" can be specified as domain when logging on for Windows. The Windows jobAn Automation Engine object type for a process that runs on a target system. is then processed with a local login authorization.
Note that Windows agents require particular rights to process jobs. These must be assigned to the user who starts the agent.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |