Home
Configuring
After you install BigFix Inventory, configure the application. Create accounts for the users who need access to the application and set up scans to collect software and hardware inventory data from your environment.
Setting up scans to discover software and hardware inventory
The scanner is an independent, well-defined component that is used by BigFix Inventory. It is installed and managed through the BigFix client, and it enables the software and capacity scans. Software and capacity scans collect data that is later on displayed on the BigFix Inventory reports. For environments with up to a few thousand computers, you can enable the default scan configuration. In this case, the analyses are activated and software and capacity scans as well as uploads of their results are scheduled automatically on the computers that are subscribed to the BigFix Inventory site. For larger environments, it is advisable to divide the computers into groups and manually configure a separate scan schedule for each group to avoid performance issues.
Discovering software and hardware on IBM i
Available from 9.2.5. You can discover software and hardware inventory on IBM i systems by using disconnected scans that do not require direct connection between the scanned computers and BigFix server. Scripts that are provided in the disconnected scanner package initiate software and capacity scans, and prepare scan results that you later on upload to BigFix Inventory.
Disconnected scanner requirements
The list of disk space requirements, the supported IBM i version compatible with the disconnected scanner and other relevant requirements.

Configuring
After you install BigFix Inventory, configure the application. Create accounts for the users who need access to the application and set up scans to collect software and hardware inventory data from your environment.
- Creating users and groups
  Each user who has access to BigFix Inventory must be assigned a role and a computer group. The role defines which reports and panels the user can view. The computer group narrows down the scope of these reports and panels to computers that meet certain criteria.
- Setting up scans to discover software and hardware inventory
  The scanner is an independent, well-defined component that is used by BigFix Inventory. It is installed and managed through the BigFix client, and it enables the software and capacity scans. Software and capacity scans collect data that is later on displayed on the BigFix Inventory reports. For environments with up to a few thousand computers, you can enable the default scan configuration. In this case, the analyses are activated and software and capacity scans as well as uploads of their results are scheduled automatically on the computers that are subscribed to the BigFix Inventory site. For larger environments, it is advisable to divide the computers into groups and manually configure a separate scan schedule for each group to avoid performance issues.
  - Frequency of scans and uploads of data
    By default, software and capacity scans are scheduled with a frequency that meets auditing requirements. If you want to change the default frequency, ensure that the new setup fulfills the minimal requirements and all considerations.
  - Default scan configuration
    Default scan configuration is advised for environments with up to a few thousand computers. It ensures that the required analyses are activated and software and capacity scans as well as uploads of their results are scheduled automatically. These actions are necessary to collect data from the computers in your infrastructure and to display it on the BigFix Inventory reports. You can enable the default scan configuration during the configuration of BigFix Inventory connections to the databases or when adding another data source.
  - Manual scan configuration
    Manual scan configuration is advised for environments with more than a few thousand computers. It requires that analyses are activated and software and capacity scans as well as uploads of their results are scheduled manually after the installation. These actions are necessary to collect data from the computers in your infrastructure and display in on the BigFix Inventory reports. Flexibility of the manual scan configuration allows for avoiding performance issues that might occur when you scan too many computers at the same time.
  - Advanced scan configuration
    After you successfully schedule software and capacity scans and the scan data is displayed on the BigFix Inventory reports, you can further customize the scans. For example, you can exclude directories from software scans or scan remote shared file systems.
  - Discovering software and hardware on IBM i
    Available from 9.2.5. You can discover software and hardware inventory on IBM i systems by using disconnected scans that do not require direct connection between the scanned computers and BigFix server. Scripts that are provided in the disconnected scanner package initiate software and capacity scans, and prepare scan results that you later on upload to BigFix Inventory.
    - Disconnected scanner requirements
      The list of disk space requirements, the supported IBM i version compatible with the disconnected scanner and other relevant requirements.
    - Adding a new data source for disconnected scans
      Available from 9.2.5. All scan results are imported to BigFix Inventory from a directory dedicated to disconnected scans. You must add this directory as a data source to allow BigFix Inventory to check its content and import all packages that are stored within. The packages are imported during each data import.
    - Preparing installation files for disconnected scans
      Available from 9.2.5. After you add the data source, prepare the installation package and distribute it to IBM i endpoints. The package should contain the disconnected scanner and configuration files used to initiate the scans. These files are downloaded from the BigFix console.
    - Installing the scanner and gathering initial data
      Available from 9.2.5. After you distribute the disconnected scanner package to the computers in your infrastructure, install the scanner and run the initial scans.
    - Running software scans and gathering scan results on IBM i systems
      Available from 9.2.5. The script that is responsible for the software scan collects the results of the catalog-based, package data, and software ID tags scan as well as retrieves results of the capacity scan and the computer.yml file. All these results are combined and compressed into a common ZIP package that can be imported to BigFix Inventory.
    - Importing scan results to BigFix Inventory
      Available from 9.2.5. To import new scan results to BigFix Inventory, copy the package to the disconnected scans directory that you added as a data source.
    - Disconnected scanner maintenance and troubleshooting
      Available from 9.2.5. You can use the maintenance and troubleshooting tasks related to the disconnected scanner to monitor the scan progress, optimize the processor usage during the scan, understand and fix the most common issues, or learn more about the log files.
    - (Optional) Manually installing the scanner and running the scans
      Available from 9.2.5. scripts that automate the scans are not appropriate for your environment, and you need to customize the execution of scans without changing the required scan frequency, refer to this appendix. The appendix describes how to run each scan, how to collect the results, and finally how to create the final package that can be uploaded to BigFix Inventory manually. The automated scripts, however, remain a recommended way of discovering on IBM i systems.
- Performing optional configuration
  You can perform optional configuration tasks to further customize the application.
- Classifying the BigFix client used by multiple BigFix products

Disconnected scanner requirements for IBM i

The list of disk space requirements, the supported IBM i version compatible with the disconnected scanner and other relevant requirements.

Supported operating systems, versions and required disk space

Table 1. Disconnected scanner requirements for IBM i systems
Operating system	Supported versions	Required disk space in the installation directory
IBM i	For information about supported versions, see: and BigFix Detailed System requirements.	Scanner installation directories: /etc/cit - at least 20 MB. Also, provide disk space for the scanner cache. /cit 50 MB for the script and installation media 50 MB for capacity scan results for 90 days /qsys.lib/qtivcit.lib/ - 200 MB
Windows		40 MB + disk space for the scanner cache
Red Hat Linux		24 MB + disk space for the scanner cache
Solaris		80 MB + disk space for the scanner cache
AIX		80 MB + disk space for the scanner cache
HP-UX		48 MB + disk space for the scanner cache

Other requirements

Ensure that IBM i computers meet the following criteria.

The disconnected scanner consumes up to 10 jobs. Ensure that the job limit is sufficient. The jar tool is available on the computer. To check whether the tool is available, type jar in the QSH.
The QSH touch command provided by IBM is available (/QOpenSys/pkgs/bin/touch). The use of touch commands provided by other sources is not supported.
JAVA_HOME variable is set on the computer and exported to your process.
1. To set the JAVA_HOME variable, run one of the following commands from the IBM i Main Menu.
  - To add the variable to your current interactive job, run the following command.
```
ADDENVVAR ENVVAR(JAVA_HOME) VALUE('/QOpenSys/QIBM/ProdData/JavaVM/jdk80/64bit')
```
  - To set the variable at the system level, run the following command.
```
ADDENVVAR ENVVAR(JAVA_HOME) VALUE('/QOpenSys/QIBM/ProdData/JavaVM/jdk80/64bit') LEVEL(*SYS)
```
2. Export the JAVA_HOME variable to your process
  - To open a QSH session, run the STRQSH command.
  - To export the variable to your process, run the following command.
```
export -s JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk80/64bit
```