The table shown below describes the XML fileA format for imports and exports. An XML file contains object structures. structure of a Connection objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task and explains the individual elements.
Element |
Description |
---|---|
uc-export |
Main element of the export file clientvers = Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. version in which the export file was created |
PRPT |
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. = The client. |
HEADER |
XHEADER in executable objects HEADER = in active, passive and system objects see object types The attribute "stateThe state a package or a task currently is in." is used system-internally and must not be changed. |
Title |
User-defined, max. 255 characters |
Created |
Format: |
Modified |
Format:
|
LastUsed |
Format: |
ArchiveKey1 |
User-defined, Attribute: ARCHIVE_KEY1 |
ArchiveKey2 |
User-defined, Attribute: ARCHIVE_KEY2 |
CONN_ATTR_R3 |
Only in SAP connections (type "R3"). The attribute "state" is used system-internally and must not be changed. |
RFC HTTP |
RFC - Remote Function Call Allowed values: "1" (selected) or "0" (not selected) You can only select one of the two options. |
CONN_R3_HTTP |
The attribute "state" is used system-internally and must not be changed. |
citpanel |
Values and settings of the tab Each "componentA component is a single deployable application artifact. As an example, this can be yourfile.war to be deployed into a Tomcat container. Each component has different properties which determine where to get it from, how to configure it, etc. You will need one component per application artifact: e.g., one for the application tier and one for the database backend." XML element is a setting with the attribute "xmlName" storing the name and "value" the value. The name must be unique (e.g. "httpPassword": loginAn Automation Engine object type that stores account credentials used by agents on target systems. data - passwordA secret combination of characters for a Automation Engine user.). Allowed values for "xmlName":
The attributes "con", "enc" and "type" are used system-internally and must not be changed. |
CONN_R3_RFC |
The attribute "state" is used system-internally and must not be changed. |
RFCPANEL |
Values and settings of the tab Each "component" XML element is a setting with the attribute "xmlName" storing the name and "value" the value. The name must be unique (e.g. "httpPassword": login data - password). Allowed values for "xmlName":
The attributes "con", "enc" and "type" are used system-internally and must not be changed. |
DOCU_Title |
in all objects (DOCU_Title) The attribute "state" is used system-internally and must not be changed. The attribute "type" shows the type of documentation: text = normal documentation |
DOC |
Content of the Documentation tab Depending on the documentation type, the CDATA section contains the text or the XML structure. |
See also:
Export File of a Connection
XML File Structure for Imports and Exports
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |