WAPT WAPT

Import your software inventory and WAPT deployment status

The WAPT connector allows you to import your software inventory deployed via WAPT, package status and machines managed by WAPT.

Objective

The WAPT connector allows you to import the following information:

  • Inventory of software deployed via WAPT
  • Package and deployment status
  • Managed and enrolled machines

Prerequisites

  • CSV files generated by WAPT
  • Active and configured WAPT server

Procedure

Generate the WAPT export file

  1. Access your WAPT Server console.
  2. Navigate to Inventory or Packages depending on desired data.
  3. Select packages or machines to export.
  4. Click Export and choose the CSV format.
  5. The file will be downloaded in .csv format.

Import into OverView

  1. In OverView, go to Data Sources Settings > Sources.
  2. Select WAPT and click Configure.
  3. Drop your .csv file in the upload area.
  4. Click Save Configuration.

OverView will automatically import software inventory, deployment status and machine management information.

CSV file format

The CSV file must contain the following columns:

  • machine_name: Name of the machine
  • package_name: Name of the package
  • version: Package version
  • status: Deployment status (installed, pending, failed)
  • last_update: Last update date

Synchronization frequency

WAPT exports can be scheduled regularly via:

  • Manual weekly export
  • Integration with a scheduler for automatic export
  • Periodic export script via WAPT API

Uploading files through DropPoint

Files for the WAPT connector are stored in a dedicated S3 bucket named wapt. Drop your CSV (or JSON) files at the root of s3://wapt/: OverView automatically detects new files and imports them on the next synchronization.

Where do the files go?

Bucket : s3://wapt/

Example : s3://wapt/export.csv

Several ways to send your files

You can populate your bucket in several ways:

  • OverView web interface — import your files, configure the mapping, then click “Replace” to refresh the data without redoing the mapping.
  • AWS CLI — for a one-off or scripted upload.
  • S3 SDK (boto3, etc.) — to fully automate recurring imports.

Using the AWS CLI

# Upload a file to the wapt bucket
aws s3 cp export.csv s3://wapt/export.csv --profile ovs_your_org

# Or sync a whole local folder
aws s3 sync ./exports/ s3://wapt/ --profile ovs_your_org

Automating the import via S3

import boto3

s3 = boto3.client(
    "s3",
    endpoint_url="https://s3.oversoc.com",
    region_name="fr-par",
    aws_access_key_id="YOUR_ACCESS_KEY",
    aws_secret_access_key="YOUR_SECRET_KEY",
)

# Push the export into the wapt bucket
s3.upload_file("export.csv", "wapt", "export.csv")

Pair this script with a scheduled task (cron on Linux, Task Scheduler on Windows) to push your exports automatically at a regular interval. Each upload triggers a new import on the OverView side.

Prerequisite: generate your S3 credentials and configure your client (endpoint, profile) as described in the OverView DropPoint guide. The profile and endpoint used here are explained there.

← PreviousMicrosoft SCCM (MECM)Next →WSUS (Windows Server Update Services)