Configure the scanner

To configure the filesystem search for Snow Inventory Oracle Middleware Scanner, use the include and exclude paths defined in the agent configuration file, snowagent.config, as described in The scanning process.

Schedule the scan in a Linux or Unix environment

In Linux and Unix environments, the execution of the scanner is scheduled by the cron configuration file siomscron.conf, which must be included in the agent installation package. For more information, see Snow Inventory Oracle Scanners Install Tools Repository in the Snow Inventory section of the Release Notes page.

Command	Description
version	Print current version to stdout
-v	Verbose logging

Schedule the scan in a Windows environment

In a Windows environment, the scanner is triggered by the Snow Inventory Oracle Middleware Scanner Launcher PowerShell script. The script must be included in the installation package for the Snow Inventory Agent for Windows.

• To schedule the execution of the scanner, run the following command with any option to show what options are available:

  $java -jar snowmiddlewarescanner.jar help

  Unknown arguments on the command line [help]

  Help for SnowMiddleWareScanner

  Usage: java -jar snowmiddlewarescanner.jar [options]

Command	Description
version	Print current version to stdout
-v	Verbose logging

EXAMPLE

From the command line, run the following script and the output file will be saved in the default location:

$JAVA_HOME/bin/java -jar snowmiddlewarescanner.jar

Snow Inventory Oracle Middleware Scanner configuration file

You can make additional configurations to the scanner by using the snowmiddlewarescanner.config file, which can be included in the agent installation package. You only have to include the file if you want to customize any of the parameters in the file. If the file is not included, the scanner will execute the scan with the default values.

The configuration file contains the following elements and default values:

<Configuration>
    <UseDataOptimization>false</UseDataOptimization>
    <Anonymization>
        <File filename="config.xml">
            <Xpath>//listen-port</Xpath>
            <Xpath>//listen-address</Xpath>
            <Xpath>//credential-encrypted</Xpath>
            <Xpath>//node-manager-password-encrypted</Xpath>
        </File>
    </Anonymization>
</Configuration>

The available configurations via the configuration file are described in the following sections.

Configure the scanner to inventory only top-level Middleware components

By enabling this option in the configuration file, only the top-level Middleware components will be inventoried, ignoring all the child Middleware components. This will optimize the data volume, which can be useful when dealing with big estates. It will not affect the visibility of Middleware products, but the drawback is that any additional child components related to those products will not be detected.

To enable the option, use the following configuration in the snowmiddlewarescanner.config file:

    <UseDataOptimization>true</UseDataOptimization>

The default value is false and is used in all other circumstances than the one described above.

Configure the scanner to anonymize data

Use the Anonymization element in the configuration file to enable data anonymization. Wildcard characters can be used in the filename part. Both xpaths and regular expressions can be used to define the optimization rules.

• Wildcards in the filename are supported. Example: <file filename="*.xml">

• Absolute xpaths are supported, these are paths defined from the root element. Wildcards in the xpaths are also supported. Example: <xpath>/machine/*/name\</xpath>

• Relative xpaths are supported, all elements that match the name in the XML document will be anonymized. Example: <xpath>//listen-address</xpath>

• Regular expressions are supported. With this example, all IP addresses found will be anonymized: <regex>^(?:[0-9]{1,3}\.){3}[0-9]{1,3}$</regex>