Install Historian Mirror Primary Server at a Command Prompt
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
After you install Historian at a command prompt, you can choose to generate a template XML file, which contains the installation parameters and the values that you have provided. You can use this XML file for subsequent installations. Similarly, you can use a template XML file instead of providing command-line arguments.
Procedure
Results
- The RemoteCollectorConfigurator utility: A command-line tool, which allows you to manage collectors remotely. By default, it is located in the C:\Program Files\GE Digital\NonWebCollectorInstantiationTool folder. For instructions on using this utility, refer to About Installing and Managing Collectors Remotely.
- The UAA Configuration tool: A utility that allows you to specify the UAA server details to match with the UAA server used by Web-based Clients. By default, it is located in the C:\Program Files\Proficy\Proficy Historian\x64\Server folder. For instructions on using this tool, refer to Change the UAA Server.
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.