The table shown below describes the XML file structure of a Variable object and explains the individual elements.
Key |
Value |
Restart required |
---|---|---|
Container number Allowed values: "1" - "999" Value must start with "1" and be ascending. |
MS SQL Server: Name of a file group The file group name must not exceed 200 characters. Oracle: Name of a tablespace |
No |
These variables are supplied in client 0000. Their settings apply globally for the whole AE system and must only be changed in client "0000".
The data records which are stored with ILMStands for Information Lifecycle Management, which refers to a wide-ranging set of strategies for administering storage systems on computing devices. in partitions can be divided into three categories. There is a separate variable for each of them:
The utility AE.DB Load automatically fills these variables with data during the ILM installation.
A container corresponds to a partition.
Example for UC_ILM_CONTAINER_STATISTICS:
Key |
Value |
---|---|
1 |
UC4_DATA_STATISTICS_1 |
2 | UC4_DATA_STATISTICS_2 |
3 | UC4_DATA_STATISTICS_3 |
We assume that three partitions should be online. The Automation Engine starts to store the data records in container "1". After a partition change, the data records are stored in container "2" etc. After container "3", the Automation Engine starts again with container "1".
The variable UC_ILM_SETTINGS contains the number of the current container in its key ACT_CONTAINER.
Important notes:
See also:
Overview of all variables in Table Form
Variable
Partitioning with ILM