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

Object class: Passive object

Object type/Short name: LOGIN

Overview

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

• if it is correct, the task is processed using the operation system ID that is stored with the Login object.
• if it is incorrect, the operating system or application rejects processing the task.

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:

• CREATE_OBJECT: Creates a new Login object.
• MODIFY_OBJECT: Changes the attributes of a Login object.
• REMOVE_OBJECT: Deletes a Login object.

Defining Login Objects

A Login definition is made up of the following pages:

• Standard pages common to all objects:
  • General Page
  • Version Management Page
  • Documentation Page

• The object-specific settings described here.

To Define the Login Information

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

2. Do one of the following

   • To apply this Login object to a specific Agent, click the folder icon on the Agent/Name cell to open the Select Agent dialog, where you can search for and select it. The Type of the object is automatically selected
   • To apply this Login object to all Agents of a type, enter "*". This activates the dropdown list in the Type column. The Agent type is either an OS or an application

   Example: Using "*" as login

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

   

   This means that the second one (with the wildcard) is applied in all logins of JMX Agents EXCEPT in those for which you enter a specific Agent name. In our example, the AGENT.JMX login is always applied to this Agent. For all other JMX Agents, the definitions in "*" are applied.

3. If you have selected a specific Agent, the Type is already populated, otherwise, click the arrow icon to open the dropdown list and select the type of Agent to which definition will apply.

   The following special types are available here:

   • ILM (only in Client 0)
   • MAIL - used for email 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 (see UC_LOGIN_TYPES - Defining Additional Platform and System Types for Login Objects). These types can be selected in the column when you either define "*" or any value for the name.

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	Format	Conversion to capital letters
   BS2000	User ID, account	Entire field
   Database	User name	None
   JMX	User name	None
   LDAP	domain\user ID	Windows: domains only Oracle Active Directory: none
   MAIL	SMTP user ID	none
   MPE	User ID.account [group 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

5. Enter a Password. The password length is unlimited, and all characters are allowed (including commas).
6. Save your changes

Platform-Specific Features

Platform	Special Features
JMX	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 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.
Windows	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.