Administration Guide > Configuration > Structure of the Configuration Files > Structure of login_dat.xml

UserInterface

The configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. file loginAn Automation Engine object type that stores account credentials used by agents on target systems._dat.xml includes general login settings. Having successfully installed the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."], the system provides a default template from which you can create the templatesPre-defined 'workflows' for specific components/tasks, e.g. Tomcat, SubVersion. for the individual users. This is done when a 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. logs on to the AE system for the very first time. The values that are stored in an individual template (including changed settings such as the language or the appearance of the UserInterfaces) are then used as the particular user's default values and are stored whenever s/he logs off.

Note that it is not required to adjust the configuration file manually because the individual values are supplied by the AE system.

You can also specify the path to the file login_dat.xml by using the start parameter -O.

Structure of login_dat.xml

Section/Parameter Description
<login> This marks the beginning of this file.
An XML element must be available.
<default> Beginning of the elements for the default values that are used for logging on to the AE system for the first time.
An XML element must be available.
<login src="adm"> The definition for logging on to an AE system.
An XML element must be available.

The attribute src= adm must be specified.

<system>system</system>

Alias for the connection to the AE system. This entry is specified in the file uc4config.xml, parameter <connection name= ....

An XML element must be available.

<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.>n</client> Client number.
XML element must be available.

Allowed values: 0 - 9999

<name>name</name> User name.
An XML element must be available.
<departmentDepartment name to which the Automation Engine user belongs.>department</department> User department.
An XML element must be available.
<language>language</language>

The language affects the display of the UserInterface.
An XML element must be available.

Allowed values: E (default value), D, F
E = English
D = German
F = French

<clienttype>D</clienttype>

Client type.
An XML element must be available.

Allowed value: D
D = Dialog

<clientvers>version</clientvers> AE system version.
XML element must be available.
<os/> Operating system.
An XML element must be available.
<hostname>localhost</hostname> The name of the local hostComputer, target system. computer.
<color>color:r,g,b</color>

The color definition for visualizing this connection to the client of the AE system.

r = value between 0 and 255, red color segment
b = value between 0 and 255, blue colo r segment

</default>

Completion of XML element <default>.
XML element must be available.

<username-Template>

The user-specific login template.

It contains login information of the last login.
An individual template will automatically be created for each OS user when they log on to the system for the first time and it will be refreshed (when the data has been changed) when the individual user logs off.
username refers to the name that the user has entered in order to log on to the local computer.

You can also create templates manually and assign any name of your choice. In this case, you can refer to this template name by using the start parameter -U.

:
:
The structure and contents of the user-specific login information complies with the structure and contents of the XML element <default>.
</username-Template> Completion of the XML element <username template>.
</login> Completion of the XML element <login>.
An XML element must be available.

Example of login_dat.xml

<login>
<default>
<login src="adm">
<system>UC4</system>
<client>0</client>
<name>UC</name>
<department>UC</department>
<passw/>
<language>D</language>
<clienttype>D</clienttype>
<clientvers>11.0.0</clientvers>
<os/>
<hostname>dialogpc</hostname>
<color>color:255,255,0</color>
<laf>com.uc4.plaf.uc4.UC4LookAndFeel</laf>
</login>
</default>
<smith-Template>
<login src="adm">
<system>UC4</system>
<client>97</client>
<name>SMITH</name>
<department>UC4</department>
<passw/>
<language>E</language>
<clienttype>D</clienttype>
<clientvers>3.2B</clientvers>
<os/>
<hostname>dialogpc</hostname>
<color>color:42,152,255</color>
</login>
</smith-Template>
</login>

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH