Refer to the System OverviewThe UserInterface window that contains information about the Automation Engine system. (category Cache) to obtain current information about the Cache. Settings for the individual Cache types can be specified in the category Server.
Each work processA part of the component Automation Engine. It is responsible for an Automation Engine system's processes (see also 'Primary work process'). has its own Cache. Only the actually used memory is allocated, and the Cache size indicates the limit. If new entries are stored in the Cache when the limit has been reached, a background reorganization process is triggered which removes those entries from the Cache which were longest unused. This procedure is continued until the used memory could have been reduced below the specified maximum value. Each Cache has its on refresh control to always keep it up to date. Hence, manual control is not necessary.
Currently the System Overview only shows the Cache workload/utilization of the primary work processIt is responsible for the execution of Automation Engine-internal tasks and work processes.. If the workload of all work processes is equally distributed, however, the values obtained from the primary work process also apply to the other work processes. The utilization/hit ratio is recorded in the log file whenever the Caches change or the work process ends. The workload/hit ratio of all work processes can be controlled in this log file.
When the PrimaryMode=parameter in the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes.'s UCSRV.INI is set to 1, the cache utilization of the PWP is not representative for other WPs. In this case, the PWP accepts PWP messages only. Therefore, the workload of all work processes including PWP is not equally distributed.
The Cache is composed of the following types:
Script
When activating an objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task, the corresponding scriptA particular Automation Engine object type. is first searched in the Cache. If it cannot be found there or if it has been modified since it has last been stored in the Cache, it is read from the databaseA database is an organized collection of data including relevant data structures. and at the same time replaced in the Cache.
Vara
The Cache type "Vara" acts in the same way as the Cache type "Script". It contains the values of variables.
MQMEM
If a transaction is interrupted - e.g. a script when the time has expired or caused by the script element that is to be processed - the required memory is stored in the database table MQMEM and in the Cache. If this transaction is then continued in the same work process (in which it has been interrupted), no database access is made. Hence, the size of the required Cache depends on processing and configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied..
ODOC
This Cache type contains GUI descriptions (XML) for the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."]. The Cache content is not replaced.
XREQ
This type includes special AE Scripts for handling the GUI. They are pre-compiled when the work process is started and stored in the Cache.
USER
The same rules apply as for the Cache type "Script". User data is stored in the Cache. This is mainly important for the UserInterface converting the User ID (USR_Idnr) to the name and departmentDepartment name to which the Automation Engine user belongs..
OBJECT_IDNR and OBJECT_NAME
This data is stored in the Cache in order to facilitate the conversion of the object code (OH_Idnr) to the object name (OH_Name) and vice versa without directly accessing the database.
HACL
In this Cache type, the records for 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 authorizations to clients are buffered so that access authorizations can be checked without accessing the database being necessary. Data is not replaced. An access ratio below 100% just indicates that a non-existing access authorization was searched for.
This optimum size is checked through the System Overview and the Cache hit ratio.
Cache type |
Optimal size |
Refresh control |
---|---|---|
Script |
Depends on the number of objects. |
Usage counters of the object (Header tab). |
Vara |
Depends on the number of objects. |
Usage counters of the object (Header tab). |
MQMEM |
Depends on the particular number of messages |
None, as each entry is only used once. |
ODOC |
Fixed value |
None, as there are no changes. |
XREQ |
Fixed value. The hit ratio is always 100% |
None, as there are no changes. |
USER |
Depends on the number of users. |
|
OBJECT_IDNR and OBJECT_NAME |
Depends on the number of objects. |
The Cache is automatically renewed in all work processes whenever objects are renamed. |
HACL |
Fixed value |
The Cache is automatically set invalid when hostComputer, target system. authorizations are modified and newly created during the first usage. |
See also:
System Overview - Cache
System Overview - Server - Settings
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |