Administration Guide > Start Parameters > Automation Engine and UserInterface

Start Parameters - Automation Engine and UserInterface

Program

Start Parameter

Description

Automation EngineThis component drives an Automation Engine system and consists of different types of server processes.

Communication process
UCSRVCP.EXE
Work process
UCSRVWP.EXE

-IPath and File name

The name of the INI file.

The start parameters for the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."] can be used:

Program

Start Parameter

Description

UserInterface
UCDJ.JAR

-V

Prints the Automation Engine version and hotfix number in the following format:

"AE OM-UserInterface AE Version plus hotfix number"

 

-VPath and file name

This prints the Automation Engine version and hotfix. number to the specified file in the following format:

"AE OM-UserInterface AE Version plus hotfix number"

 

-IFile name

The INI file path and name or 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 uc4config.xml.

You can use the parameter -l directly in the INI file in the line cmd=  in order to specify a particular configuration file for the UserInterface. Each 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. can individually create his/her own uc4config.xml with all the particular preferential settings.

 

-OFile name

The path and the name of the configuration file login_dat.xml.

You can use this parameter to specify a path for the configuration file loginAn Automation Engine object type that stores account credentials used by agents on target systems._dat.xml that is to be used. It contains the general settings for logging on to the UserInterface.

 

-LLanguage

Language

Allowed values: "D", "E", "F"
"D" = German, "E" = English, "F" = French

 

-Cmmmm

The number of the 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. for a single logon.
The user who is automatically used for logging on must only belong to one departmentDepartment name to which the Automation Engine user belongs..

 

-Dmmmm

The number of the client for a single logon.
The Windows domain is used as department.

 

-SAE System

The name of the AE system for a single logon.
The logon dialog is shown if this parameter is missing.

 

-UUser name

In the file login_dat.xml of the UserInterface automatically stores a template profile of each OS user who logs on to the UserInterface. This template includes the login data of the last UserInterface login and has the name of the OS user. In this configuration file, you can also manually create templatesPre-defined 'workflows' for specific components/tasks, e.g. Tomcat, SubVersion. and name them as you want.

You can use the parameter -U to indicate the name of such a template. The login dialog of the started UserInterface will then be pre-completed with the login data that this template includes.

It is helpful to use environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. variables for this parameter in order to obtain the correct template for the OS user who has currently logged on automatically:
Unix: -U$USER
Windows: -U%USERNAME%

The default template will be used if you do not specify this parameter or if the specified template is not available.


Program

Start Parameter

Description

Java loader of the UserInterface
UCDJ.EXE

-F0

This suppresses the splash screen.

 

-IPath and file name

The path and the name of the INI file UCDJ.INI.

 

-JParameter

The parameter of the UserInterface (see above).

You can also assign parameters to the UserInterface via the Java loader. They will then be added to the cmd command in the INI file. In doing so, you can determine a default setting in the INI file and control special options via the Java loader.

Keep in mind that:

  • The parameter chain must be written in double quotations.
  • Path specifications which contain blanks must additionally be written in double quotations (such as -J"-I""C:\AUTOMIC\my DC\uc4config.xml""").

For example:
The adequate language should be specified using user shortcuts.

INI-file abstract:

cmd="javaw" -Xmx1024m com.uc4.ucdf.UCDialogFactory -U%User%

A shortcut serves to pre-determine the language:

ucdj.exe -F0 -J"-LD"

 

See also:

Start Parameters - Agents
Start Parameters - Utilities

Start Parameters - ServiceManager

 


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

Copyright © 2016 Automic Software GmbH