Administration Guide > Utilities > AE DB Archive > Structure and Contents of the Archiving Directories

Archived Folder Structure

Archived data is stored in an archive 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. which is to be defined in the Archive tab. All a 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.'s archiving runs are collected in a folder which shows the four-digit client number. A subfolder is created with each archiving run. It contains all archived data and the corresponding index files. The subfolder name is composted of the prefix "UC_ARCHIV_", the current date in the format "YYYYMMDD", and a consecutive number (e.g. 0001\UC_ARCHIV_20030520_3).

The maximum folder size (presetting = 650 megabytes) can also be defined in the Archive tab. If the data to be archived exceeds the specified value,  a new folder with the next consecutive number is created and the archiving run is continued in this folder.

Numbering facilitates the filing of large archive stocks and makes it easier to retrieve data records. The archiving number is also shown in the index file.

Use the Archive Browser to view the contents of archive folders.


Index-File Structure

Index files are generated when the statistic al records of the tables AH and RH are archived in order to simplify searching and filtering data records in archive files  Each index line refers to a data record in the archive.

Index for AH: UC_AH.IDX

Position Description
1 Block code "H2"

2

Client

3

User

4

Department

5

AType

6

SType

7

RunIDShort for "run number". It is a number that provides unique information about a task's execution. The RunID can include 7 to 10 digits. It is assigned by the Automation Engine component .

8

Host name

9

Start time/start date

10

Parent ACT

11

Parent PRC

12

Archive Key 1

13

Archive Key 2

14

Object name

15

Byte position in the archive

16

Line position in the archive

17

Archive number

18

Record length in bytes

Example

H2;1;LF;PROG;JPAK;GRP;1302137;;28.08.1998 10:31:42;0;0;;;LF.JP.GROUP;73837;2555;7;148

 


Index for RH: UC_RH.IDX

Position Description
1 Block code "H3"

2

Client

3

Report type

4

Object name

5

RunID

6

Time the reportA report provides more detailed information about a task's execution or a component. was created

7

Time of last report update 

8

Byte position in the archive

9

Line position in the archive

10

Archive number

11

Record length in bytes

Example

H3;98;JE01;MM.CHECK.FREE.SPACE;1000020;24.05.2000 12:56:03;24.05.2000 12:56:10;2820;39;12;151

 


Message Archive: UC_MELD.TXT

Position Description
1 Block code "M"

2

Client

3

User

4

Department

5

Time that message was generated

6

Source

7

Category

8

Type

9

Host

10

Message Text

Example

M;1;LF;PROG;15.03.99 09:43:54;Automation Engine;Report;Error;;U0011021 Host 'LFT40' is not active!

 


Comment Archive: UC_ACMT.TXT

Position

Description

1

Block code "M"

2

Client

3

User/Department

4

Object name

5

RunID

6

Time that message was generated

7

Record length in Bytes

8

Message Text

Example

M;100;MH/PROG;TESTJOB;454711222;15.03.99 09:43:54;nnn;This task was modified by (MH).

 

See also:

General Procedure - Database Maintenance
Archive Browser

Archiving

Structure of the INI file, AE DB Archive

 

 


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

Copyright © 2016 Automic Software GmbH