[00:00] A Remote History Provider allows us to use the History Provider of another Gateway, as well as its corresponding database connection. While it's fairly simple to set up, we first need to make sure we have at least two Gateways. I have one installed locally, and one installed remotely on another machine, and we need to ensure that both of them are connected to each other through the Gateway network. We then want to go to the Configure section of the Gateway webpage, and scroll down to the History page under the TAGS section. As you can see, I currently don't have any Historical Tag Providers defined. This is because Historical Tag Providers are automatically added whenever we set up a new database connection. But I don't have any of those on this Gateway. However, I do have a Historical Tag Provider and database connection on my remote Gateway, and we can use that one. Because we are making a Remote History Provider, we don't need to connect this local Gateway directly to the database and add another connection to it.

[01:08] We can click the Create new Historical Tag Provider link to get started. First we want to select the Remote History Provider option and click the Next button at the bottom. Then we want to make sure our Remote Gateway is properly selected. If we have multiple Gateways in our Gateway Network, they would show up here as well. Once the proper Gateway is selected, we're going to want to hit the Next button at the bottom. We then want to select the proper History Provider. The Remote Gateway's History Provider and corresponding database connection are called DB, so I'm going to select that one, and then click the Next button at the bottom. We can give our History Provider a unique name, and we also should confirm that the remote Gateway name and the remote History Provider name are both correct. Finally, we need to decide if we want to allow storage on this History Provider. If this setting is unchecked, we will only be able to read Historical Data coming from the History Provider of the remote Gateway.

[02:06] Keeping it checked allows us to both read and store history to the Historical Provider. I'm going to leave it checked, and then click the button at the bottom that says Create New Historical Tag Provider. You may have noticed that right away it says that storage is Faulted. This is because by default, the service security settings of any Gateway will only allow read access to any of its providers. And because we kept allow storage setting checked, it is not able to properly store data there, because the Gateway is preventing it. If you have never created security zones, or set up any service security, you may run into this issue. To fix it, we're simply going to go into the remote Gateway, go into the Configure section, and go down to the Service Security section. We're going to want to go into the Security Zone that defines our local Gateway, we're going to go down to the History Provider Access section.

[03:05] You'll notice that the default profile access is set to Query Only. I'm going to want to Query and Store data to my History Provider, so I'm going to set this setting to Query and Storage. Once that's set, we're going to scroll down to the bottom, click the Save button, and then go back to our local Gateway, and simply edit and then Save the connection without making any changes, to re-initialize it. You'll notice now it's Running just fine. Now that that's set up, I can set History on some of my Tags, even though I don't have any database connections to this local Gateway. Let's go ahead and open up a Designer. I have one already open here. I can then go and edit a tag, go down to the History section, and when I store History and choose a History provider, you can see my remote Gateway Database connection is now selectable. In addition, I can also set up Tag History bindings using that Historical Provider, say from a Table on the Data Property.

[04:09] You can see when I go to the Tag History Binding, my Remote Gateway Provider is there as well. This can be used for things like tables, charts, and even in reports. With Remote History Providers, I can set up a database at one central location, and have all of my historical data funnel through that Gateway. This way, I don't have to worry about setting up a database near every single one of my Gateways, and I can also view the Historical data of any Gateway from any other Gateway in my Gateway Network.