Disconnected scanner installation requirements (disconnected scenario)

Edit online

9.2.5 Available from 9.2.5.

Ensure that the computer on which you want to install the disconnected scanner runs on a supported operating system, has enough disk space, and fulfills other relevant requirements.

Processor and RAM usage for the scanner

Table 1. Processor and RAM usage for the scanner
Component CPU RAM Comments
Software scan Up to 100 %

You can limit the usage by running the scan with the CPU threshold attribute. For more information, see: Optimizing processor utilization by disconnected scanner (disconnected scenario).

 < 80 MB The software scan runs on demand, and can be monitored by checking the following processes: wscansw, wscanfs.
Capacity scan < 1 % < 20 MB The capacity scan runs every 30 minutes, and can be monitored by checking the following process: wscanhw.

Supported operating systems and required disk space

Table 2. Supported operating systems and required disk space
Operating system Supported versions Disk space required in the installation directory
9.2.5 IBM i For information about supported versions, see: IBM License Metric Tool 9.2 - Supported Operating Systems.
  • /etc/cit - 20 MB + 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/ - 300 MB
9.2.7 Windows 100 MB + disk space for the scanner cache
9.2.7 Red Hat Linux 100 MB + disk space for the scanner cache
9.2.8 Solaris 100 MB + disk space for the scanner cache
9.2.9 AIX 100 MB + disk space for the scanner cache

Other requirements

Ensure that the computer fulfills all requirements that are specific for its operating system.
UNIX UNIX
UNIX commands should be installed in default locations. If a command that is required by the disconnected scanner is installed in a custom location, it causes errors with installing the disconnected scanner or running the scans. In such case, information about the command is provided in the following location.
  • Results of running the scanner installation playbook if you manage disconnected scans with Ansible
  • The log.txt file in other cases
To solve the problem, install the command in the default location or create a link from the default location to the custom location.
IBM i IBM i
Ensure that IBM i computers meet the following criteria.
  • The following PTFs are required:
    • For IBM i 7.3, SI81901 is required
    • For IBM i 7.4, SI82088 is required
    • For IBM i 7.5, SI81911 is required
  • 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.
  • Directory /usr/bin should be prior to any other entries in the PATH environment variable.
  • The QSH touch command provided by IBM is available (/usr/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.
      1. To open a QSH session, run the STRQSH command.
      2. To export the variable to your process, run the following command.
        export -s JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk80/64bit