Install Historian Mirror Primary Server Using the Installer

Before you begin

Set up the Historian environment.
If you are changing the role of a Historian server that was previously a distributed node in any other configuration (single-server or mirror primary server), you must first uninstall Historian.

About this task

This topic describes how to install the Historian mirror primary server using the installer. You can also install it at a command prompt.

Procedure

Log in as an administrator to the machine on which you want to install Historian.
Run the InstallLauncher.exe file.
Select Install Historian.
The welcome page appears.
Select Next.
The license agreement appears.
Select the Accept check box, and then select Next.
The Where do you want to install Historian? page appears.
If needed, change the default installation drive of the Historian server, and then select Next.
The Override the default Historian data Path? page appears.
If needed, change the default folder of the log files, and then select Next.
The UAA Configuration page appears.
If needed, modify the value in the Confirm the UAA Details box.
UAA details are required if you want to use Web-based Clients.
By default, the local hostname and the port number of 443 are considered. If the UAA service is on the same machine on which you are installing the Historian server, you can accept the default value. If, however, the UAA service is on a different machine or uses a different port number, replace those values in the URL as follows:
```
https://<UAA server>:<port number>/uaa
```
where:
- <UAA server> is the name of the machine on which UAA is installed. If the machine uses a fully qualified domain name (FQDN), provide the FQDN
- <port number> is the one that you have specified for the public https port in the TCP Port Assignments page during Web-based Clients installation.
Note: You can install a UAA service using Operations Hub or Historian Web-based Clients. You can provide the URL of an existing UAA instance. Or, if a UAA service is not available, you can install it during Web-based Clients installation.
Select Next.
The Historian Security Groups page appears. Using Historian security groups provides an added layer of control over access to your Historian system.
By default, the option to create Historian security groups is not selected.
If you want the installer to create Historian security groups, select the corresponding check box, and then select Next.
The Choose the type of install you want to perform page appears.
Select Historian Mirror Primary Server, and then select Next.
The Ready to Install page appears.
Select Install.
The installation begins.
When you are asked to reboot your system, select Yes.
Historian mirror primary server is installed. In addition, the RemoteCollectorConfigurator utility is installed. By default, it is located in the C:\Program Files\GE Digital\NonWebCollectorInstantiationTool folder. Using this utility, you can add and manage collector instances without the need to install Web-based Clients. For instructions on using this utility, refer to About Installing and Managing Collectors Remotely.

What to do next

Install the distributed nodes using the installer or at a command prompt.
While installing the Historian server, if you have allowed the installer to create Historian security groups, create a local Windows user with the format <Web-based Clients server name>.admin, and add the user to the ihSecurityAdmins group.
This user will log in to Web-based Clients.
Alternatively, you can create UAA users in an external UAA and map their security groups. For information, refer to About UAA Groups.
Depending on whether the Historian server will use local or domain security groups, select the appropriate option in Historian Administrator.