RayVentory Scan Engine is able to push software and hardware inventory results to a parent instance. The following parent instances are supported:
•RayVentory Scan Engine
•RayManageSoft Reporting Location
•RayVentory Reporting Location
RayVentory Scan Engine also supports the following upload locations:
•Local directory
•UNC folder path
•FTP address
These settings enables the user to control which parent instance is in use and how to upload data to it.
Setting up these values is not relevant if you do not intend to upload the data to any parent server (for example if your RayVentory Scan Engine instance is already self-contained root).
URL to Upload Inventory Files
The full URL to the parent upload location (see supported types section). This value should include the protocol and the port number. RayVentory Scan Engine uses this path for uploads of inventory files (.ndi). If you do not know this value, ask your administrator.
URL to Upload Discovery Data
The full URL to the parent upload location (see supported types section). This value should include the protocol and the port number. RayVentory Scan Engine uses this path for uploads of discovery files (.disco). If you do not know this value, ask your administrator.
Upload Discovery Data during Manually Triggered Inventory Upload
If this checkbox is checked, .disco files will be uploaded to parent URL at the beginning of every inventory upload. If this checkbox is unchecked, the files will not be uploaded automatically during a manually triggered inventory upload.
Delay in seconds between discovery and inventory upload
The delay after uploading discovery data and before uploading inventory data. The delay is supposed to ensure that if the upload target was a RayVentory Server with direct import enabled for discovery and inventory then the server has enough time to process the discovery data before inventory import, in order to avoid missing inventory status updates for the network devices based views and reports.
Upload rules
By default, RayVentory Scan Engine only uploads .ndi files to the HTTP server. For these files, the built-in routing is applied to ensure that they are correctly parsed. The Upload Rules option can be used to also upload other file types. In order to enable the upload of other files, check the Upload other files that were received checkbox. Click on the + button to open the Add Upload Rule dialog. Enter the upload location into the URL field and the extension of the files to the File Extensions field. Either click on the Apply button to add the rule to the Upload Rules and enter the next one or click on the OK button to add the rule and close the dialog. Upload rules can be created for .mmi and .xml files.
As .gz files will always be uncompressed by RayVentory Scan Engine, therefore no additional upload rules for compressed files are necessary.
Ignore Server Certificate Errors
If this checkbox is checked and HTTPS is used as the communication protocol, any SSL-related errors will be ignored.
|
Note: The connection will be not secure if SSL-errors are ignored. |
Certificate for Authentication against the Upload Endpoint
A custom certificate (.cer) which is used for encrypted connections via HTTPS protocol. If no value is provided, the standard Windows Certificate Store will be used.
Use Credentials from the Credential Store for Authentication to the Upload Endpoint
In case the parent location requires basic authentication, you can select the required credentials from the list. Credentials can be defined in the Credential Store screen.
Proxy Settings
Optional proxy settings used for communication with the parent upload location.