Connect the Web Admin Console with the Historian Server

Before you begin

Deploy the Web Admin console.
Initialize the EC2 instance on which you have deployed Proficy Historian for AWS.

About this task

This topic describes how to generate a configuration file for the Web Admin console. The configuration file is used to connect these applications with the Historian server.

Note: If you restart the EC2 instance on which you have deployed the Web Admin console, you must generate the configuration file once again to connect the Web Admin console with the Historian server.

Procedure

Run Command Prompt as an administrator.
Run the CloudHistorianConfigurationUtility.exe file. It is provided along with the collectors installer. After you install collectors, it will be available in the C:\Program Files\GE Digital\Historian Cloud Config folder by default.
Enter the number corresponding to generating a configuration file.

Enter the following details:


Field	Description
NLB DNS	Enter the Amazon Network Load Balancer (NLB) DNS. Tip: To find the NLB DNS: Access the EKS cluster on which you have deployed Proficy Historian for AWS. Access the EC2 instance. In the navigation pane, under Load Balancing, select Load Balancers. Select the load balancer for which you want to find the DNS. In the Description section, copy the DNS name.
Username	Enter the username to connect to Proficy Historian for AWS.
Password	Enter the password to connect to Proficy Historian for AWS. Tip: This is the value you entered in the Password field under Proficy Authentication Configuration when you created the stack.
DNS or public IP address of the EC2 instance	Enter the public IP address or DNS of the EC2 instance on which you have installed the Web Admin console.
Key file path	Enter the path to the .pem file that was downloaded when you created a key pair while installing the Web Admin console.

The Web Admin console is connected with the Historian server.