Chatee ahora con Soporte
Chat con el soporte

Foglight 5.9.8 - Installing Foglight on Windows with an External Oracle Database

Before Installing Foglight Installing Foglight
Preparing to install Installing a new version of the Management Server Installed directories Foglight settings HP patch checking tool Uninstalling Foglight Upgrading the Management Server Installing Foglight FAQ
Running the Management Server Installing and Upgrading Cartridges Installing Agents

Changing external database credentials

Use the following method to reconfigure Foglight to start up with a new database password. The password can be updated in the server.config file.

 
* 
IMPORTANT: Do not use “<“ and “>” in your password, for example jo<anne>123. These characters corrupt the XML in the server.config file, causing Foglight to fail to start successfully.
To encrypt your database password using the keyman command:
1
Specify the following from the command line:
> bin\keyman -d [FGLHOME\config] encpwd "<new password>" foglight.defaultkey
The encrypted password appears.
2
Open the server.config file.
3
Replace the existing database password with the new encrypted database password on the following line:
server.database.password = "q4056753111e8a24c9a722048fc6df1f0"
4
Restart the Management Server.

Importing self-signed certificates to Foglight TrustStore

Foglight needs to verify self-signed certificates. It is necessary to configure the TrustStore properly for encrypted database/LDAP connection.

Non-FIPS mode

In non-FIPS mode, to be compatible with former Foglight versions, Foglight uses JRE TrustStore as the default TrustStore. The default TrustStore will NOT be preserved during Foglight upgrade. Foglight also support a separate TrustStore, which will be preserved during upgrade. Choose the one that best suits your needs:

Option 1: Import the certificate into the embedded JRE TrustStore, <foglight_home>\jre\lib\security\cacerts (default password: changeit), with the following command:
<foglight_home>\jre\bin\keytool -import -file <path_to_cert_file> -alias <alias_of_cert> -keystore <foglight_home>\jre\lib\security\cacerts -storepass <store_pwd>
Option 2: Prepare and import the certificate into Foglight TrustStore with the following steps:
1
Prepare TrustStore: copy <foglight_home>\config\security\trust.keystore.sample to <foglight_home>\config\security\trust.keystore
2
Import the certificate into the Foglight TrustStore, <foglight_home>\ config\security\trust.keystore (default password: nitrogen), with the following command:
<foglight_home>\jre\bin\keytool -import -file <path_to_cert_file> -alias <alias_of_cert> -keystore <foglight_home>\config\security\trust.keystore -storepass <store_pwd>

FIPS-compliant mode

In FIPS-compliant mode, it is required to use FIPS-validated KeyStore type BCFKS.

Import the certificate into the Foglight default TrustStore in FIPS-compliant mode, <foglight_home>\config\security\trust.fips.keystore (default password: nitrogen) with the following command:
<foglight_home>\jre\bin\keytool -import -trustcacerts -alias <alias_of_cert> - file <path_to_cert_file> -keystore <foglight_home>\config\security\trust.fips.keystore -deststoretype BCFKS - provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath <foglight_home>\server\core\bc-fips.jar -storepass <store_pwd>
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación