Install Web-Based Clients Using the Installer

About this task

This task describes how to install web-based clients using a GUI-based installer. You can also install web-based clients using the command line.

Run the Historian installer.
Select Install Web-based Clients.
The welcome page appears.
Select Next.
The license agreement appears.
Select the Accept check box, and then select Next.
The TCP port assignments page appears.

Enter the values for TCP port assignments as described in the following table, and then select Next.


Field	Description
Public https port	Port for https protocol communication. The default value is 443. You can change this value.
UAA http port	Port where UAA runs on the machine where it is installed.
UAA database port	Port where UAA data (postgreSQL UAA database) is stored on the machine where it is installed.
Historian database port	Port where postgreSQL Historian database is stored on the machine where it is installed.
Historian http port	Port where Historian web applications run on the machine where they are installed.

The Fully Qualified Domain Name(s) page appears.

In the FDQNs box, enter the fully qualified domain names and then, select Next.
This enables you to access Historian web applications remotely. You can use it to access the web admin console using alias names. Enter the values separated by commas.
To access the web admin console using any of the following URLs, enter Test.htclab.ge.com,localhost,127.0.0.1,aliasName
Important: Do not enter a space between the values.
The User Authentication and Authorization Service page appears.
Enter the Admin client secret, and then select Next.
The password must satisfy the following conditions:
- Must not contain only numbers.
- Must not begin or end with a special character.
Note: The format of username for Historian web-based clients is <host name>.admin. It is case-sensitive.
Alternatively, if you want to use an external UAA service, select the Use External UAA check box.
The fields for the external UAA service appear.

Enter values as described in the following table, and then select Next.


Field	Description
UAA Base URL	Enter the URL of the external UAA server in the following format: https://<UAA server name>:<port number>
Admin Client Secret	Enter the client secret for local installation, which is required to access the web admin console, trend client, and REST APIs.
Re-enter secret	Enter the client secret again.
External UAA Client Name	Enter the client name that you provided while installing the external UAA. The default value is admin.
External UAA Client Secret	Enter the client secret that you provided while installing the external UAA.

Select the installation drive for web-based clients, and then select Next.
The Customize Log Files and Postgres Sata Locations page appears.
Select a location for log files and postgreSQL data, and then select Next.
The following page appears.
Provide the name of the destination Historian server, and then select Next.

Note: If you want to connect to a remote Historian server, you must disable the Enforce Strict Client Authentication and Enforce Strict Collector Authentication options using Historian Administrator in the remote server.

The You are ready to install page appears.
Select Install.

The Historian web-based clients are installed.

To migrate to the UAA that you have been using, use the uaa_config_tool provided in the Utilities folder of the ISO package.
For more information, refer Migrate User Authentication Data from Historian to Common UAA Service.
Note: After installation, uaa_config_tool is available in the following folder as well: <installation drive of Historian>\Program Files\GE Digital\Historian Config
If you want to use an external UAA, refer to Connect to the Remote UAA Service.
If you have set up LDAP or LDAPS, map the LDAP groups with Historian UAA.