Exporting asset data to OTbase Inventory

While you can inspect asset data in the configuration client of OTbase Asset Discovery, this is only intended for verifying that your devices are discovered properly. Once that this is the case, you will use Asset Discovery only to make changes to the probing configuration. All other asset management workflows are accomplished in Asset Center. This means that discovery data must somehow arrive at Asset Center.

Data transmission alternatives

Discovery results from Asset Discovery are always transmitted to Asset Center as a flat file. This file is produced by Asset Discovery either at scheduled intervals or by manual command. It contains all the information Asset Center needs to know about the particular Asset Discovery node, and it is encrypted.

How this result file ends up in Asset Center is irrelevant for functionality and results. The following alternatives are possible:

• If a direct online connection exists, the logical way is to transmit the result file by HTTP, HTTPS, or SSH.
• If an indirect online connection exists, implying intermediate servers in a DMZ, for example, the logical way is to have Asset Discovery transmit the result file to the intermediate server using SSH, a file share, or a HTTP/HTTPS proxy server. You can use the OTbase Discovery Proxy for this task: More information.
• If no online connection exists between Asset Discovery and Asset Center but you are able to connect to both, you can 1) export discovery results to your computer and then 2) connect to Asset Center where you can manually import the discovery file.
• If no online connection exists, the solution of last resort is to use removable media or mobile computer.

Set the metadata properly before exporting discovery results

Before even thinking about exporting data to Asset Center, make sure that you have set the relevant metadata according to this guideline.

Automated, scheduled export

In production use, Asset Discovery automatically exports result files every 24 hours. You can configure the time of day and export method used, in the details pane for the Asset Discovery node.

The destination that you specify, using either a hostname or an IP address, is the computer where the result file is sent to. You can select between various methods how to transfer the file:

• None
• HTTP Post
• HTTPS Post
• SSH
• File (usually involving a remote file system).

If you select "None", no export will take place, but automatic probes will. You can then inspect probing results in the Asset Discovery configuration client.

Using HTTP or HTTPS

When using HTTP or HTTPS, please consider the following. You must specify the hostname or IP address of OTbase Asset Center.

DO NOT CHANGE THE DEFAULT PATH. THE PATH FOR ASSET DISCOVERY UPLOADS IS NOT "/OT-BASE". ASSET DISCOVERY USES A DIFFERENT ENDPOINT ON THE SERVER, "/AGENT-SINK". IF YOU HAVE CONFIGURED LOAD BALANCERS, PROXYS, OR FIREWALLS, YOU MUST MAKE SURE THAT ASSET DISCOVERY CAN ACCESS THIS ENDPOINT.

When using HTTPS, you can also specify a client certificate (.p12). Such a certificate is required, for example, when accessing OTbase Cloud.

Exporting to the file system

If HTTP, HTTPS and SSH cannot be used for whatever reason, you can also export asset data to the file system. Just remember that the file still must travel to Asset Center. One way to make this happen could involve the use of shared folders. Asset Discovery doesn't care if the folder you are exporting to is shared or private.

Setting export time of day and activating the export

Automatic exports are triggered every 24 hours, and you can define the desired time of day using 24 hour notation. So as an example, "1:00" is 1 a.m., whereas 1 p.m. is "13:00".

Automatic exports are activated by checking the "Active" box. Don't forget to save your changes by clicking "Set" at the bottom of the pane.

Testing the export route

After having made all required configuration settings, you will probably want to test the export without waiting until the scheduled export time, which may be somewhere in the middle of the night. In order to do this, simply click on "Export" in the main menu.

Manually exporting to a local file

If you don't have an online route to Asset Center (let's assume because your IT department hasn't made the appropriate changes in firewalls, proxy server etc.) or you just want to check export data manually without using an online connection, you manually export to a local file. There are two ways to make it happen:

1. In the "Destination OTbase Asset Center" section, select "None" for the Asset Center destination and click on "Set" at the bottom of the details pane. If you then click on "Export" in the main menu, Asset Discovery knows that you want to export to a local file and opens a file selector box.
2. If there is a valid entry in the "Destination OTbase Asset Center" section that you don't want to change, right-click to open the context menu for the Asset Discovery node and select "Export to File".

You can then manually import the discovery data in Asset Center in the INVENTORY/IMPORT section.

Verifying the export in OTbase Asset Center

You can verify that your asset data was successfully imported by logging on to Asset Center, then select INVENTORY/IMPORT. Import operations are listed in the import log. To get details, double-click on the entry that you want to inspect. In the import protocol that pops up you can see details. Clicking on a device ID of any of the devices listed will launch the respective device profile.