Foglight 6.3.0 - Installing Foglight on Windows with an External PostgreSQL Database

Step 12: Foglight repository database type

This step allows you to select the Foglight database type. The server on which the database is located must be running before you complete this step.At the completion of this step, the installer creates the user (foglight is the default user ID) in the database and sets the appropriate permissions.

•

Select SQL Server (External database) and then click Next. See the following section for instructions.


	NOTE: The embedded database option does not appear if you selected HA as the server startup mode in Step 10: Foglight mode.

SQL Server external database

If the Management Server you are installing is configured to be part of an HA cluster, you must also configure it to connect to the same database instance as all other members of the cluster. In this case, you set Server name and Database Name to the same values as the values used for the other members. In some rare cases, certain settings might be different. For example, the value for Server name might be different if there is a firewall between the database and certain members of the cluster in your environment.

When using gMSA for authentication, you must install Foglight using SQL Server Authentication. Once Foglight is installed, you can configure the appropriate gMSA account for repository authentication. Refer to Planning for authentication with gMSA for more information.

In the Server name box, type the database host name or IP address (the default is localhost).


	IMPORTANT: If the port number of the database is not 1433 (standard), specify the host and port (host,port) or host and instance (host\instance). For example: 10.30.125.92,14341 or 10.30.125.92\SHREK.

From the Repository User Account Authentication drop-down list, select a method of authentication (Windows® or SQL Server®).

If you select Windows Authentication, your Windows user name is populated in the User Name box.


	NOTE: For Windows authentication, using the LAN Manager Authentication security policy Send NTLMv2 response only. Refuse LM & NTLM is not supported. If the authentication level on the host is set for this policy, change the policy before continuing the installation.

In the Repository User Name box, type the user name if it is not already pre-filled. The Management Server uses this account to connect to the database.

In the Repository User Account Password box, accept the default password (foglight) or type an alternate one. The Management Server uses this password to connect to the database.

In the Repository User Account Retype Password box, accept the default (foglight) or, if you have provided an alternate password, re-type the password for verification.


	NOTE: This box is applicable only if you selected SQL Server authentication in step 2.

In the Database Name box, type the name of the database (the default is foglight). This name is the name of the Microsoft® SQL Server instance to which you want the Management Server to connect.


	IMPORTANT: If you are using a SQL Server default or named instance, the SQL Server Browser Service must be running for Foglight to start up and connect correctly.

Select one of the following Repository Creation options:

•

Automatically create the repository database

•

Manually create the repository database

If you select Manually create the repository database, there are two methods you can use to create the database. For more information, see Manual database configuration.


	IMPORTANT: You must manually create the database before proceeding.

If you select Automatically create the repository database, select the Repository Administrator Account Authentication Method, and then type the Repository Administrator Account User Name and Password. The Management Server uses the administrator account credentials to create the SQL Server database.


	NOTE: The Repository Administrator Account User Name cannot be the same as the User Account User Name you created in step 3.


	IMPORTANT: If the Management Server you are installing is configured to be part of an HA cluster, set the Repository Administrator Account User Name and Password to the same values as the values used for the other Management Servers that share the same HA partition name.

Click Next.

If a database schema exists, the Foglight Database Found screen appears. This screen allows you to keep your existing data, create a database, or select a different database. If you are running in HA mode, select Keep existing data.

If you chose Manually create the repository database in step 7, and did not create the database at that time, an error message appears. For more information, see Manual database configuration.

Step 13: Foglight ports configuration

Configure the server ports. The Foglight Ports Configuration screen displays default ports that you can assign.


	NOTE: In certain configurations, the Management Server uses other ports than the ones that you can set on this screen; for example, when Foglight is running in High Availability (HA) mode. See the Administration and Configuration Help for details.

If you are installing Foglight in High Availability (HA) mode and are planning to have multiple HA partitions on the same sub-network, configure a different Cluster Multi-cast Port for each HA partition. The primary server and secondary servers within each HA partition must be configured to use the same Cluster Multi-cast Port.

You can set this port from the Foglight Ports Configuration screen, or change it after installation in the server.config file. See Configuring the cluster multicast port used in High Availability mode for information about changing this port after installing Foglight.


	IMPORTANT: Errors can occur if servers that are not part of the same HA partition are configured to multicast on the same port on the same sub-network as the HA partition. See Running the Management Server FAQ for more information about these errors.

If you want to revert to the default values, click Defaults.

Click Next.


	NOTE: If there are any port assignment conflicts, an error message dialog box appears. Click Review Ports, if you want to return to the Foglight Ports Configuration screen to configure the conflicting port(s), or click Ignore and Continue to continue with the installation without resolving the port conflicts. Select one of these options to continue.

Step 14: Add Foglight license file

Specify the path to the Foglight license file in the Install a license from the following file box, or browse to a license file by clicking the Browse button.


	IMPORTANT: See the Administration and Configuration Guide for information about license requirements, managing licenses, and the different categories of cartridges (based on their license requirements).

Click Next.

Alternatively, you can provide a license file to the Management Server after the installation is complete. To do so, leave the Install a license from the following file box blank and click Next.

If you selected Enable Foglight as a Service in Step 6: Foglight Service, the Management Server service is enabled and started at this point.

Step 15: Add Foglight to system service

The Foglight Server Startup step enables to add Foglight to the system service.


	NOTE: To customize the Foglight Management Server starts as a system service, the current user must have sudo without password privilege; otherwise the script will be generated without being added into the system service and you can edit and execute the script later.

To start the Foglight Management Server without adding Foglight to the system service (the default setting), click Next.

To start the Foglight Management Server as a system service, select Yes, add foglight to the system service.

제품을 선택하십시오.

더 나은 서비스 제공을 위해 채팅 목적을 작성해 주십시오.

문제에 대한 권장 솔루션

Foglight 6.3.0 - Installing Foglight on Windows with an External PostgreSQL Database

Step 12: Foglight repository database type

Step 13: Foglight ports configuration

Step 14: Add Foglight license file

Step 15: Add Foglight to system service