eG Administration

MANAGER SETTINGS - ADVANCED SETTINGS For configuring advanced manager settings, click on the Advanced Settings subnode under the Manager Settings node of the SETTINGS tree structure. This will result in the display of the ADVANCED SETTINGS section. Using this section, you can configure the following: You can now restart the eG manager from the eG administrative console itself. To restart the eG manager immediately, set the Restart the manager now? flag to Yes. By default, it is set to No. To enable logging of the errors and output related to the eG manager's activities, set the Manager Output and Error flag to Yes. This automatically creates the managererr.log and the managerout.log files in the <EG_INSTALL_DIR>\manager\logs directory. While the errors are logged in the managererr.log, the output of manager operations is logged in the managerout.log. Using these log files, you can quickly and easily track the status of the eG manager's activities, capture the errors that occur, and analyze the reasons for these errors/failures. Sometimes, after logging manager-related errors and output for a while, you may switch off logging for a brief period, and then switch it back on. Likewise, for some reason, you may decide to restart an eG manager, which is actively logging manager errors and output. In both these cases, new error and output messages will emerge, waiting to be written to the log files that pre-exist. By setting the Output and Error mode flag to Overwrite, you can ensure that the new messages completely replace the existing contents of the log files. Setting this flag to Append on the other hand, ensures that the new messages are only appended to the old contents. Typically, whenever a user manually changes a configuration file (.ini file) of the eG manager, he/she would have to restart the eG manager for the changes to take effect. To make sure that changes to configuration files are effected even without a manager restart, then, soon after you make modifications to one/more configuration files, set the Update Manual Config Files flag to Yes, and click the Update button. This will automatically update the eG manager with the configuration changes. Once the updation is complete, the status of the Update Manual Config Files will automatically switch to No. Note: The Update Manual Config Files flag cannot be used to update the eG manager with changes to language files. Do changes to language files to take effect, you will always have to restart the eG manager. The Metric Aggregation capability of the eG Enterprise Suite allows administrators to group one or more components of a particular type and monitor that group as a single logical entity termed as an aggregate component. This aggregate component provides a collective view of the performance of all the components that are grouped together. Aggregates can be used to represent all the components of a specific type, or all components of a type in a geography or in a business unit. Different organizations may want to view performance in different ways - some by type, some by geographies, and some by business unit. To provide administrators with maximum flexibility, and help them to configure a number of aggregate components without being constrained by the licensing of the eG monitors, eG Enterprise performs metric aggregation using external agents. By default, the Agents for aggregate components flag is set to External indicating that the default external agent bundled with the eG Enterprise suite is capable of monitoring an aggregate component. This helps the administrators to add any number of aggregate components depending on the views of their infrastructure they desire without needing additional licenses. In case, if you wish to monitor the aggregate components using a remote agent, then set this flag to Remote. Note: If you are already monitoring aggregate components using an external agent and now, if you wish to monitor the same aggregate components using a remote agent, then, you are required to purchase the premium licenses accordingly. If enough licenses are not available, then a message to that effect will be displayed and the external agent will continue to monitor the aggregate components. Finally, click the Update button.