This variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. is used to specify the templatesPre-defined 'workflows' for specific components/tasks, e.g. Tomcat, SubVersion. that can be used in order to create particular object types.
Key |
Value |
New start required |
---|---|---|
No |
This variable is supplied in 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 and can be assumed and adjusted to the particular client.
One way of creating objects is to use the command New in the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."]'s context menu. In doing so, a dialog opens which contains a listShows entities in a grid view of the various object types. By default, all object types are displayed. Adjust the variable if you want to restrict this selection. As it is possible to assume this variable to various clients (e.g. test client), you can also define individual selection lists.
You can also limit this list on the basis of authorizations. Specify value "N" in TEMPLATE_SHOW_ALL in the variable UC_CLIENT_SETTINGS and users only see the object types they are allowed to create.
First define an appropriate name in the key that is by default an object-type abbreviation (such as JOBS.R3). Enter the name of a template in the value section. These object templates are either supplied in the folderTop level entities such as Environment, Deployment Target, Activity, … are stored in folders. The permissions a user has on an entity depend on the permissions that are set on the folder for the entities. "Template" of system client 0000 or have individually been created.
If you want to create an individual template, simply create an object (such as a file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object).). Then enter its name in the variable UC_OBJECT_TEMPLATE. Automic recommends using significant names and an extra folder for these templates. If 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. creates an object using this template, by default the suggested name is composed of the template name, the term "NEW" plus a serial number (such as JSCH.NEW.2) or a counter. It is also possible to define more than one template per object type.
Templates can be adjusted according to your requirements at any time. They should make it easier for users to create objects (such as a template for an 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 in Unix jobs). Note that users can adjust these templates, the pre-filled lines are only suggestions.
If a client contains its own UC_OBJECT_TEMPLATE, it is also possible to provide a collection of own templates. A template is always first searched in the particular client. If it is not available in the client, the corresponding template of system client 0000 is used. If no template is found, the corresponding entry is not displayed in the selection list.
Pay attention in system client 0000: Entries can be added to the object UC_OBJECT_TEMPLATE but the supplied standard entries MUST NOT be deleted. Otherwise, problems occur in XML imports.
Excerpt of variable UC_OBJECT_TEMPLATE:
Key |
Value |
---|---|
Cockpit |
CPIT |
Notification for alarm messages |
CALL_ALARM |
Notification for requests |
CALL_REQUEST |
See also:
Overview of all variables
in table form
Variable
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |