Login Object (LOGIN)

The Login object stores login information for agents. Jobs and file transfer use this data to access operating systems and applications. The steps for defining Login objects (LOGIN) are the same as any other Automic object. This section describes the settings that are specific to only Logins.

Object Definition


Agents pass the login information defined in the Login object to the operating system or application in which jobs or file transfers are processed. This information is validated and

Some operating systems allow deactivating the login validation. Whether the login should be validated or not for these operating systems can be defined in the agent .ini file .

You can also use the following script elements to handle Login objects:

Defining Login Objects

A Login definition is made up of the following pages:

To Define the Login Information

  1. Click Add row on the toolbar to add a new row.

  2. In the Agent/Name cell enter the name of the agent to which this login information will apply.

    Do one of the following:

    • Select an existing agent from the dropdown list.

      The adjacent Type cell automatically displays the platform of the agent.

    • Enter the name of the agent (or a part of it).

      If it is already available, the "find as you type" function lists the hits right away.

    • Enter "*" to apply this login to all agents of this type.

      In this case, you must specify the type. The login information of this line then applies to all the agents/systems of the selected type.

      ClosedExample Using "*" as login

      A Login object has been defined for agent VMS.NEW.3 with type VMS.

      A second Login object has been defined for type VMS, but this time using the "*" wildcard character as type.

      The result of this definition is as follows: The second one (with the wildcard) is applied in all logins of this agent EXCEPT in those for which you enter a specific agent name. In our example, the VMS.NEW.3 login is always applied to this agent. For all other VMS agents, the "*" is applied.

    • In the Type cell enter the type of the agent (or a part of it). If it is already available, the "find as you type" function lists the hits right away.

      In you have selected an existing agent, the type is predefined and you cannot change it.

      The following special types are available here:

      • ILM (only in Client 0)
      • MAIL - used for e-mail connections via SMTP
      • DB - for partitioning with RA agents. In this case, you must select the name of the solution

      The administrator can define additional types for Login objects in the UC_LOGIN_TYPES variable. These types can be selected in the column when you either define "*" or any value for the name.

  3. From the Type dropdown list select the agent platform, which is either an OS or an application.
  4. Enter a Username/ID that complies with the format requirements of the target system.

    The table below provides information on the platforms that are available for selection by default as well as on some of the most common ones:

    Operating system/Application


    Conversion to capital letters


    User ID, account

    Entire field


    User name



    User name


    LDAP domain\user ID Windows: domains only
    Oracle Active Directory: none
    MAIL SMTP user ID none


    User ID.account [group name]

    Entire field


    Group name.user ID


    Oracle Applications

    User name



    User ID

    Entire field


    User ID

    Entire field


    Operator ID


    SAP (ABAP Engine/Business Intelligence)

    Client, user ID


    SAP (Exchange Infrastructure)

    XI user ID



    User ID



    User ID

    Entire field


    Domains\user ID

    Domains only

  5. Enter a Password that is not longer that 20 characters. Exception: For MPE you can specify three passwords. The passwords plus separators cannot exceed 62 characters.

Passwords cannot include commas, regardless of the platform you use.

Platform-Specific Features


Platform Special Features

Usually, you need to specify one password. However, if you use WebSphere version 6 with activated administrative security, you must specify three passwords, namely User password, Keystore password and Truststore password.

The screenshot above illustrates the Set Passwords dialog that opens up when defining a Login object for MPE agents. The same applies for JMX objects.

Oracle Applications In Login objects, you need to specify an internal OA user that is used for processing jobs. In addition, you must specify an OA database user in the ERP_LOGIN object.

You can specify "*OWN" as domain when logging in to Windows. The Windows job is then processed with a local login authorization.

Windows agents require particular rights to process jobs that must be assigned to the user who starts the agent.

See also:

Defining Objects