Home
Managing the infrastructure
After you complete the initial configuration of BigFix Inventory, learn how to manage components of its infrastructure: VM managers, server, database, and data sources.
Administering the database
Perform administering tasks on your database to keep it in good condition, protect your data, or configure additional settings.
Updating the database password
You can update the database user password when needed, for example if the password is changed and users cannot log in to BigFix Inventory.

Managing the infrastructure
After you complete the initial configuration of BigFix Inventory, learn how to manage components of its infrastructure: VM managers, server, database, and data sources.
- Computer statuses
  Computer statuses provide information about the condition of the computers that are monitored by BigFix Inventory. To properly discover the installed software and measure its license metric utilization, ensure that computers in your environment work correctly.
- Managing VM managers
  VM managers are pieces of software that create, manage, and monitor virtual machines. You configure connections to VM managers so that BigFix Inventory can gather data that is required to calculate utilization of license metrics in virtual environments.
- Administering the server
  Perform administering tasks on your server to configure advanced settings, or restart its services.
- Administering the database
  Perform administering tasks on your database to keep it in good condition, protect your data, or configure additional settings.
  - Backing up and restoring the database
    Perform regular backups of the data that is stored in the database, and restore it when needed to prevent data loss.
  - Creating a new database
    To create a new database without reinstalling BigFix Inventory, you must modify the configuration file that stores information about the database. After you do so, you will be able to complete the initial configuration again, and create a new database.
  - Reinstalling BigFix Inventory with an existing database
    You can reinstall BigFix Inventory and connect it to an existing database. This allows you to preserve all the data collected so far and avoid changing configuration settings.
  - Moving the BigFix Inventory database
    To move the BigFix Inventory database to a different computer, back up the database, move it to the target computer, and point to that computer in the server.xml and database.yml files.
  - Updating the database password
    You can update the database user password when needed, for example if the password is changed and users cannot log in to BigFix Inventory.
- Removing inactive computers
  When you decommission a computer in your infrastructure, it continues to report to BigFix Inventory. The data is still collected from this computer, and displayed on the metric reports. To ensure that all infrastructure changes are reflected in BigFix Inventory, you should remove each decommissioned computer from BigFix. If you cannot remove this computer from BigFix for a valid reason, you can use an alternative solution, and decommission the computer in BigFix Inventory.
- Managing data sources
  Computers in an organization can be divided into organizational units, and can be monitored by multiple BigFix infrastructures. Each infrastructure is referred to as a data source. Data from multiple data sources can be imported to one instance of BigFix Inventory.

Updating the database password

You can update the database user password when needed, for example if the password is changed and users cannot log in to BigFix Inventory.

Before you begin

Before you can run the security utility you must set the JAVA_HOME environment variable, for example

export
                JAVA_HOME=install_dir/jre/jre

.

Important: Create a backup of server.xml and database.yml files before you make any change.

Procedure

Log in to the server where BigFix Inventory is installed.
Run the following command and enter the new password for the database user.
install_dir/wlp/bin/securityUtility encode
Note: If you use AES encryption, add the following parameter to the command above: --encoding=aes.
The password is returned as an encrypted string.
Edit the following configuration files, and enter the new encrypted password.
- install_dir/wlp/usr/servers/server1/server.xml
  Search the database entry "properties.db2.jcc" for DB2 and "properties.microsoft.sqlserver" for SQL Server and then change the password for the database entry.
  Copy the new encrypted password to password attribute, for example:
  - in case of 'xor' encoding : password="{xor}fgspGzAWPTApFzk="
  - in case of 'aes' encoding : password="{aes}fgspGzAWPTApFzk="
- install_dir/wlp/usr/servers/server1/config/database.yml
  Copy the new encrypted password to encrypted_password.
If you use the same user for the BigFix database, you must also enter the new password in the following locations:
1. Update the database password in the BigFix server. For more information, see: Changing the database password.
2. In BigFix Inventory, click Management > Data Sources. Enter the unencrypted password for the database user and click Save.
Restart the BigFix Inventory server.