You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing training@inductiveautomation.com.
Version:
- Version 8.1 New
- Version 8.0
- Version 7.9
- Version 7.8 New
LESSON LIST
LESSON
Introduction to Enterprise Administration Module
Description
Learn the basics of the EAM and where to control and monitor a network of Ignition Gateways. Discover the differences between controllers and agents. See the various types of tasks that can be configured to run automatically on remote Gateways. Monitor the status of agents in real-time from a single location. The EAM uses the Gateway Network, which must be set up prior to getting started with the EAM.
Video recorded using: Ignition 8.1
Transcript
(open in window)[00:00] The Enterprise Administration module, or EAM, allows users to control and monitor any number of Ignition gateways from a central Gateway via the Gateway Network. In this lesson, I'll provide an overview of the various features included with the module. I have two Ignition gateways on my machine, and I've already configured one as the controller and the other as an agent. On the controller gateway webpage, I can navigate to config, enterprise administration, agent management, and from here I can interact with the various agents connected to this controller. In my case, there's just one. From here I can delete agents, and then additional options will appear if I click the more button and then I can see details, visit the agent gateway webpage, or restart the agent. Clicking details takes me to another page that allows me to view more about the agent, such as saved gateway backups, license details, the list of installed modules, and project details. One of the main features of EAM is the ability to set up tasks for each agent. If I navigate to the agent tasks page, I can take a look at available tasks, tasks that are currently running or scheduled to run, and then a history of previously run tasks.
[01:11] You can see that I already have a collect backup task scheduled for my agent and that it's set to repeat every day at midnight. To create a new task, I can click create new gateway task and choose from a variety of other tasks, including activating or unactivating licenses, installing modules, running a gateway upgrade, or sending resources to gateways. Once a task has been chosen, I can configure it to execute immediately, on demand, at a specific time, or I can set it to execute repeatedly on a custom schedule I create here. In addition to the config pages, there are also some EAM status pages for monitoring your agents and tasks. EAM agents will show all agents connected to the controller, their statuses, and any relevant logs so that you're aware of any potential errors coming from agent gateways. The EAM tasks page will provide an overview of the executing, scheduled, and recently completed tasks for all agents, and will also provide the ability to pause and resume tasks.
[02:06] Some of the benefits of these features coming together is the ability to efficiently synchronize modules and resources between gateways, quickly recover from system failures, and monitor the health of agents.