BVQ software installation

BVQ software installation

Installation modules


The installation of BVQ is divided into the several modules:

Installation module

Installation file

Description

BVQ DB setup

bvq-db-setup-<version>-installer.jar

Create a new BVQ database schema in DB2

BVQ DB schema migration

bvq-schema-migration-<verion>-installer.jar

Update an existing BVQ database schema to the latest level

BVQ GUI 32-bit

bvq-gui-<version>-installer.jar/exe

Installation of  BVQ GUI, 32-bit

BVQ GUI 64-bit

bvq-gui-<version>-x64-installer.jar/exe

Installation of  BVQ GUI, 64-bit

BVQ scanner

bvq-scanner-<version>-installer.jar

Installation of  BVQ scanners

BVQ scheduler

bvq-scheduler-<version>-installer.jar

Installation of  BVQ schedulers

Birt reporting 32-bit

bvq-reporting-birt-<version>-installer-exe.zip

Installation of  BVQ Birt reporting engine, 32-bit

Birt reporting 64-bit

bvq-reporting-birt-<version>-installer-x64-exe.zip

Installation of  BVQ Birt reporting engine, 64-bit

BVQ reports

bvq-standard-reports-<version>-installer.jar

Installation of  BVQ standard reports

(warning) For the GUI and the BVQ Birt reporting engine, the correct 32/64 bit version has to be used. Please see  #Java Runtime Environment (JRE).

BVQ database

Create a new BVQ database with the necessary database schema BVQ-db-setup-<version> installer.jar.

Create a new BVQ database user account

A BVQ user has to be created in the Windows User Administration.
(warning) If a domain login is used, the BVQ database user has to be created in the active directory!
Default values for quick install written in italics.

Attribute

Value

Name

bvq-user bvq

Full name

BVQ application user

Password

bvq-user-pwd bvq

Must change password

No

User cannot change password

Yes

Password never expires

Yes

Account is disabled

No

Groups

DB2ADMNS

Create the BVQ database schema

Execute the BVQ Install file 'bvq-db-setup-<version>-installer.jar'.

1. Click 'Next'.

2. Select a location for the database. Default is '%ProgramFiles%\SVA\BVQ\bvq-db-setup'.
Click 'Next'.

3. Use the settings shown above.

Click 'Next'.

4. Enter the user name and the password of the BVQ user. Click 'Next'.

5. Enter the name and the drive for the BVQ database. Default name is BVQ .
Please note that the drive name has to be entered without colon!

Click 'Next'.

6.Please enter the name of the database (step before).
Click 'Next'.

7. Please enter the name of the database. The value 8192 is recommended and should not be modified!

Click 'Next'.

8.Wait until install preparations have finished.
Click 'Next'.

 

9. This shows the file name of one of the SQL install files for service purposes.
No user interaction necessary - click 'Next'.

10. This shows the file name of one of the SQL install files for service purposes.
No user interaction necessary - click 'Next'.

11. This shows the file name of one of the SQL install files for service purposes.
No user interaction necessary - click 'Next'.

12. This shows the file name of one of the SQL install files for service purposes.
No user interaction necessary - click 'Next'.

13. This shows the file name of one of the SQL install files for service purposes.
No user interaction necessary - click 'Next'.

14. This shows the file name of one of the SQL install files for service purposes.
No user interaction necessary - click 'Next'.

15. This shows the file name of one of the SQL install files for service purposes.
No user interaction necessary - click 'Next'.

16. The screen displays the output of the SQL install file.

17. Monitors whether the processing was completed successfully.
Click 'Next'.

18. The BVQ database has been created successfully.
Click 'Done'
.


BVQ GUI

Open the BVQ GUI installation-file with the name bvq-gui<version>-installer-x64-exe.zip or bvq-gui<version>-installer-x32-exe.zip.
(warning) Please check whether the name of the file fits to the used operating system and Java version!

1. Click 'Next'.

2.Click 'Next'.

3. Enter an installation path for the GUI. Default is: %ProgramFiles%\SVA\BVQ\bvq-gui.
Click 'Next'.

4. Click 'Next'.

5. Choose shortcut settings - if the install process stops here, the wrong bit level for the operating system has been chosen.
Click 'Next'.

6. Enter here the BVQ database host name (BVQ DB server oder localhost), the database name and the database user.
Click 'Next'.

7. Enter the storage size of the tree Java process for optimal performance. Values larger than 512M should be chosen. If the server has 2 GB of available memory than 1024M should be entered here.
Please note that the 'M' behind the number is mandatory here!
Click 'Next'.

8. Wait until the GUI installation is finished
Click 'Next'.

9. The installation process finished successfully.
10. Check the box 'Launch BVQ GUI' to start the GUI after the installation process for entering the license information.

11. The license validation dialog opens here because no valid license has yet been provided.
12. Choose 'Yes' to important a valid license.

13. Select the adequate license file and click 'Open'.
Please mark that the license file has to be stored on the BVQ server! An attempt to open the license file from another destination in the network will fail!

!

14. Here the results of the entered license information are displayed.
Press 'Save license'.

15. After a restart of the BVQ GUI the license becomes valid


Bei Scan Intervallen > 15min ist eine Anpassung der GUI notwendig

Icon

Die BVQ GUI prüft regelmäßig, ob der Topologie-Scanner spätestens alle 30 Minuten neue Daten liefert.
Eine Überschreitung wird durch ein (warning) im Scanner Status Icon in der Statusleiste angezeigt.

Wird beim Scanner im Installationsdialog unter Forced topolgy scan interval (sec) ein Wert größer als 25min konfiguriert, sollte die Prüfung der GUI angepasst werden.

Die Anpassung wird wie folgt vorgenommen:

  1. Voraussetzung: Administrator-Rechte
  2. Alle laufenden BVQ GUIs beenden.
  3. Ins BVQ GUI Installationsverzeichnis wechseln (typisch: %PROGRAMFILES%\SVA\BVQ\bvq-gui)
  4. bvq-gui-<version>.jar ist ein ZIP-Archiv welches sich mit den üblichen ZIP Tools öffnen lässt.
  5. Darin gibt es ein Config-File: bvq-runtime.properties
  6. Darin den Eintrag gui.missingScannerLogEntryWarningThresholdMs ändern von 1800.000 (30min) auf einen Wert nach folgender formel: (Forced topolgy scan interval (sec) + 300) * 1000
  7. Speichern - Fertig

Eventuell lässt sich das .jar File, bedingt durch Windows Security (UAC) Einstellungen mit dem aktuelle eingeloggten Benutzer nicht speichern. Dann zuerst das JAR-File auf den Desktop kopieren/verschieben, dort die Änderungen machen und Schließlich wieder zurück kopieren.


BVQ scanner

Execute the BVQ install file bvq-scanner-<version>-installer.jar.

1. Click 'Next'.

2. Click 'Next'.

3. Choose the install path. Default is: %ProgramFiles%\SVA\BVQ\bvq-scanner.
Click 'Next'.

4. Click 'Next'.

5. Enter the BVQ database host name (BVQ DB server oder localhost), the database name and the database user.
Click 'Next'.

6. Enter the name, password and optionally the domain of the BVQ Windows service user. If no domain is used just enter ".".
Normally the service user is also the BVQ database user.
7. Choose 'Yes' to include DB2 as a dependent service, if the database and scanner are on the same server (default).
Click 'Next'.

8. Enter the number of scanner instances (SVC clusters or Storwize systems)
Click 'Next'.

9.   Enter the cluster IP address of the first SVC or Storwize system.
10. The forced topologies scan control is set to 300 which is a recommended value.
11. The audit logs scan interval is set to 30, which is a recommended value
12. Select the received private key file.
13. The Java max heap size is set to 512 which is a recommended value and should not be changed!

This step has to be repeated for every instance selected in the step before.

14. Wait until installation preparation is finished
Click 'Next'.

15. Wait until processing is finished.
Click 'Next'.

16. The installation was finished successfully.
Click 'Done'.

BVQ scheduler

Start the installation of the BVQ scheduler by executing the file: installfile bvq-scheduler-<version>-installer.jar.

1. Click 'Next'.

2. Display ahowa informations about the scheduler-nstallation.

Click 'Next'.

3. Enter the path for the installation. Default is: %ProgramFiles%\SVA\BVQ\bvq-scheduler

Click 'Next'.

4. Click 'Next'.

5. Enter the BVQ database host name (BVQ DB Server oder localhost), the database name and the database user
Click 'Next'.

6. Enter the name, password and optionally the domain of the BVQ Windows service user. If no domain is used just enter ".".
Normally the service user is also the BVQ database user.
7. Choose 'Yes' for "Include DB2 as a dependent service:", if database and scanner are on the same server (default).
8. If not already set, then enter '256' as value for "Java max heap size"
Click 'Next'.

9. Please wait until the install-preparations are finished.
Click 'Next'.

10.  The service will now be installed. Please wait until processing is finished.
Click 'Next'.

11. The installation of the scheduler was finished successfully
Click Done
.

BVQ reporting BIRT

Execute the installation files for the BVQ reporting engine: bvq-reporting-birt<version>-x64-installer-exe.zip


1. Click 'Next'.

2. Displayed installation information.
Click 'Next'.

3. Enter the install path. Default is: %ProgramFiles%\SVA\BVQ\bvq-reporting-birt .
Click 'Next'.

4. Click 'Next'.

5. Decide about shortcut settings.
Click 'Next'.

6. Enter the BVQ database host name(BVQ DB Server oder localhost), the database name and the database user
Click Next

7. Use the default value here
Click Next

8. Wait until install has finished.
Click Next

9. the reporting engine has been installed successfully,
Click Next

BVQ Reports

install the BVQ standard reports with the following file bvq-standard-reports-<version>-installer.jar.

1. Click Next

2. enter the install path. Default is %ProgramFiles%\SVA\BVQ\bvq-reporting-birt\reports\bvq-standard

Click Next

3. Click Next

4.wait until installation has finished
Click Next

5. the insulation has finished successfully
Click Done