Section/Parameter | Description |
---|---|
[GLOBAL] | |
system= | Name of the AE system |
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.= | Client number of the AE system, which will be monitored. |
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.= | User name, whose context the monitoring will run in. |
passwordA secret combination of characters for a Automation Engine user.= | User's password. |
language= |
Language, which will be used for message translations. Value: D, E or F In version 11.2 the messages are available in English only, regardless of the values defined here. Other languages will be available in future versionsAn application version holds zero or more deployment packages and may have dependencies to zero or more application versions of the same (or to different) applications. |
reconnect= |
Reconnect interval. Value: seconds Format: integer |
logcount= | Number of stored log files |
logging= |
Path and file name of the log file The number signs serve as placeholders for a series in numerical order. When starting the EMI, the log files are renamed so that the most current log file is always the one with the number "00". |
[COLLECTIONS] |
Format: integer Example: 5 means, that the statusThis represents the condition of a task (such as active, blocked, generating). of all agents in EMI will be refreshed every 5 seconds. |
agents= |
Value represents the refresh interval for all agents Default: 15 |
cache= |
Set value for cache section. Default: 10 |
client= |
Client section Default: 60 |
databaseA database is an organized collection of data including relevant data structures.= |
Database and MQ section Default: 10 |
licenses= |
Licenses section Default: 60 |
queues= |
Queues section Default: 5 |
servers= |
Servers section Default: 5 |
usage= |
Usage section Default: 1500 |
users= |
Users section 60 |
[TRACE] |
In version 11.2 the following four parameters are not yet considered, as the EMI creates a log file only. |
file= |
Path and file name of the trace file The number signs serve as placeholders for a series in numerical order. When starting a trace, the trace files will be renamed so that the most current trace file is always the one with the number "00". Default: ./temp/trace_##.log |
trccount= |
Number of stored trace files Default: 10 |
tcp/ip= |
Trace flags of the EMI Allowed values: "0" (default value) to "9" Set trace flags only in close cooperation with our support team. |
emi= |
Trace options for EMI processing Allowed values: "0" to "9" Default: "0" |
[JMX] |
![]() |
usePlatformBeanServer= |
Indicates, whether the MBeanServer is visible for local connections. Allowed values: "1" or "0" Default: "1" |
jxmPort= |
TCP-port for RMI connection You may reach the MBeanServer on this default address: service:jmx:rmi:///jndi/rmi://hostname:jmxPort/Automic Default port value (jmxPort): 9091 |
[CP_LIST] |
![]() |
In order for a user to be able to access the information the EMI provides, these privilegesPrivileges in the Automation Engine refer to user rights to work with certain frontend and user interface functions. You grant privileges to users in the Automation Engine. have to be set in the respective User objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task:
See also:
EMI - External Monitoring Interface
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |