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

If you chose Manually create the repository database while installing the Management Server for use with an external database, there are two ways in which you can configure the database before starting the Management Server. Choose the one that best suits your needs:

•

Option 1 - Run the Foglight database tool to configure the database

•

Option 2 - Run SQL scripts to configure the database

Option 1 - Run the Foglight database tool to configure the database

Run Foglight’s database tool from the command line after exiting the installer. The database tool is located in the <foglight_home>\client\ directory.


	NOTE: Option 1 does not currently support the creation of a SQL Server® database with Windows® integration.

To perform manual database configuration:

•

Create the database. Run the following command, including the -D parameters and values as required:

java [-D...] -jar foglight-database-tool.jar createdb

For example:

java ‑Dserver.database.type=sqlsvr ‑Dserver.database.host=sqldbhost01 ‑Dserver.database.port=1433 ‑Dserver.database.name=foglight ‑Ddb.admin.user=sa ‑Ddb.admin.password=foglight ‑Ddb.schema.username=foglight ‑Ddb.schema.password=foglight ‑Ddb.schema.name=foglight ‑jar foglight-database-tool.jar createdb


	NOTE: The following SQL warnings may appear when creating the database on SQL Server®: 2012-07-03 14:52:21.231 INFO Create database "foglight"... 2012-07-03 14:52:21.809 WARN SQL Warning: Changed database context to 'master'. 2012-07-03 14:52:46.981 WARN SQL Warning: Changed database context to 'foglight'. 2012-07-03 14:52:47.044 INFO Create Schema for database "foglight"... 2012-07-03 14:52:47.512 WARN SQL Warning: Warning! The maximum key length is 900 bytes. The index 'idx_cfgbinder_agent' has maximum length of 1530 bytes. For some combination of large values, the insert/update operation will fail. 2012-07-03 14:52:47.715 WARN SQL Warning: Warning! The maximum key length is 900 bytes. The index 'incident_ticket_index' has maximum length of 1020 bytes. For some combination of large values, the insert/update operation will fail. 2012-07-03 14:52:47.715 WARN SQL Warning: Warning! The maximum key length is 900 bytes. The index 'idx_pcm_name_type' has maximum length of 1786 bytes. For some combination of large values, the insert/update operation will fail. 2012-07-03 14:52:47.934 INFO Populate for database "foglight"...

The database tool requires the following parameters:

•

-Dserver.database.type=<mysql|sqlsrv|oracle|postgresql>

•

-Dserver.database.host

•

-Dserver.database.port

•

-Dserver.database.name

•

-Ddb.admin.user


	NOTE: The -Ddb.admin.user must exist, and must have database administrator privileges.

•

-Ddb.admin.password

•

-Ddb.schema.username


	NOTE: The tool creates the -Ddb.schema.username user when you run the command.

•

-Ddb.schema.password

•

-Ddb.schema.name


	NOTE: To delete the database and start over, run the database tool with the dropdb option instead of the createdb option shown in the preceding example. The dropdb option does not remove an existing or new Repository User account.

Option 2 - Run SQL scripts to configure the database

If you clicked Create during the database installation step, the SQL scripts in the <foglight_home>\scripts\sql directory are prepared with the provided configuration options. SQL Server® generates four SQL scripts for each Authentication type:

•

SQL Server Authentication:

•

sqlsvr_drop_db.sql

•

sqlsvr_create_db.sql

•

sqlsvr_create_schema.sql

•

sqlsvr_populate_db.sql

•

Windows Authentication:

•

sqlsvr_integratedauth_drop_db.sql

•

sqlsvr_integratedauth_create_db.sql

•

sqlsvr_create_schema.sql

•

sqlsvr_populate_db.sql

You can review these scripts before running them.

You must run the configured scripts against the database using a third-party tool.

To perform manual database configuration with SQL Server Authentication:

Launch a command window.

Run the .sql scripts by issuing the following commands from the prompt in the order shown:


	NOTE: In the following commands, replace <admin_username> and <admin_password> with the user name and password for the user account of the Microsoft SQL Server administrator.