Foglight Evolve 6.1.0 - Installing Foglight on Windows with an External Microsoft SQL Server Database

Step 11: FIPS Compliance mode

This step allows you to enable FIPS Compliance mode. Select the checkbox if you want to enable FIPS compliance mode.

NOTE: Once the FIPS Compliance mode is enabled during installation, you cannot disable it without a complete reinstall of Foglight.

NOTE: In Foglight FIPS-compliant mode, it is required to set TrustStore for SQL Server JDBC driver if the SQL Server uses self-signed certificate. For more information, see Setting up an encrypted database connection .

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.

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.

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.

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.

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

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.

IMPORTANT: You must manually create the database before proceeding.

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.

Step 13: Foglight ports configuration

NOTE: In certain configurations, the Management Server uses other ports than the ones that you can set on this screen. See the Administration and Configuration Help for details.

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

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).

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