This lesson is part of the Enterprise Administration Module course. You can browse the rest of the lessons below.

LESSON LIST

Autoplay Off

Description

Learn to create a Controller Gateway and how to configure it. A database connection and archive file path are required to store information about the Agents.

Video recorded using: Ignition 8.1

Transcript

(open in window)

[00:00] In order to set up EAM, you must first designate a machine as the controller. In this lesson, I'll demonstrate how to configure this. Before this can be done, a database connection needs to be set up on the soon to be controller gateway. I've already set up my database, so I'll get started with the controller setup. To do this, I'll navigate to Config, Enterprise Administration and Setup. I'll choose the controller option and then click next. First, I'll need to choose the default database, which in my case will be ControllerDB. It's required to have a database connection to set up controller as it's needed to store historical event data for the agents. If you don't have a database connection at this point, you can go to the Databases Connections page and take care of that, and then come back here later. Next, I'll move on to the Archiving settings. You'll need to specify a location for the controller to store archived files. The archive location dropdown can be set to automatic so that the system manages this location, or it can be set to manual to specify a location.

[01:03] This location can be set to be on the machine or on a locally mounted network share, but keep in mind that the path will be relative to the controller gateway. It's recommended that you put a system into place to monitor the free size of the disk with the archive as gateway backups can potentially grow to be quite large, and with enough agents, quite a bit of space may be used up. The low disk space threshold can be configured so that the error messages will be thrown in this gateway when the archive disk drops below a certain number of megabytes. Furthermore, you can configure backups to be pruned based on either the number of backups, or their age, with the maximum retention count and maximum retention age settings. Once the specified count or age is reached, the oldest backups will be deleted while the newest will be retained. Having either setting at zero means that criteria will be ignored and won't affect the retention of the backups. I'm gonna leave the archiving settings on our default values and click finish, and then this gateway is now configured as a controller. If I scroll down to the Enterprise Administration section, the setup option has now disappeared and has been replaced with new options. To change any of the settings that were just configured, you can go to the new Controller Settings page and change the default database, the archiving settings, or uninstall the controller functionality from this gateway.

You are editing this transcript.

Make any corrections to improve this transcript. We'll review any changes before posting them.