DSE Deployables on Windows and Linux

Certified execution of generated Windows and Linux deployables

Use this section after Generate deployables completes. It documents the certification/run workflow for the generated win-x64 and native linux-x64 packages. These are generated integration runners, not the DSE commercial Windows/Container installer SKUs.

Windows deployable (windows/win-x64)

Copy the generated Windows folder to the certification machine (or extract the transferred archive), then work from the windows\win-x64 directory.

Verify these generated files are present before the first run:

• DataSourceExplorer.Runner.exe
• manager.cmd
• run.cmd
• schema-catalog.json
• source-connections.json
• destination-route.json (when routing is enabled)

Start the professional local Runtime Manager:

cd /d C:\Path\To\deployables\windows\win-x64
manager.cmd

manager.cmd launches DataSourceExplorer.Runner.exe --manager. The manager binds to 127.0.0.1 and normally opens the default browser automatically. If the browser does not open, run the executable directly and use the Local management URL printed in the console.

1. Confirm Runtime status is READY and there is no active execution.
2. In Connections, confirm each required source and destination is Configured. Leave protected fields blank when you want to keep the saved/embedded value.
3. For the first certification run, use Manual only scheduling and set the output directory to output.
4. Select Run now and wait for the status to return to READY.
5. Confirm Last result and Run history show Success, then independently verify the expected output/destination data.

For a one-time headless execution:

run.cmd

Linux deployable (linux/linux-x64) — validated Ubuntu Hyper-V workflow

The following procedure follows the validated Ubuntu Server 26.04.1 LTS / Microsoft Hyper-V guide supplied for certification. It runs the native Linux deployable; Docker is not required for this workflow.

Preferred secure browser access from Windows

Instead of exposing the manager on the VM network, you can create an SSH local port forward from Windows PowerShell after reading the manager port from the Linux log:

ssh -L 18093:127.0.0.1:<manager-port> <linux-user>@<VM-IP>

Then open http://127.0.0.1:18093/ on Windows. Keep the SSH session open while using the manager. The socat relay described below remains useful on an isolated/trusted certification network.

Purpose

This procedure creates a lightweight Ubuntu Server virtual machine and runs the native Linux deployable produced by DSE. It mirrors the Windows deployable workflow: copy the generated package, start the DSE Deployable Runtime Manager, open the manager from the Windows host, run the deployable, and verify the result.

Prerequisites

• Windows host with Hyper-V enabled
• Ubuntu Server LTS ISO
• DSE-generated linux folder containing linux/linux-x64
• At least 4 vCPU, 4 GB RAM, and a 40 GB virtual disk
• Network access from the VM to the required DSE source/destination systems

1. Create the Hyper-V virtual machine

Create a Generation 2 VM with the following baseline settings:

2. Prepare Ubuntu

Log in to Ubuntu and update the operating system. Then verify CPU, memory, disk, and IP address.

sudo apt update
sudo apt upgrade -y
hostname -I
nproc
free -h
df -h

If the 40 GB VHDX was created but the root logical volume is only about 18-19 GB, expand the LVM root volume to consume the free space.

sudo vgs
sudo lvextend -l +100%FREE -r /dev/ubuntu-vg/ubuntu-lv
df -h

3. Connect from Windows with SSH

Use the current VM IP reported by hostname -I. Hyper-V Default Switch addresses can change after a reboot.

ssh <linux-user>@<VM-IP>

4. Copy the generated Linux folder

Run ssh/scp from Windows PowerShell, not from the Ubuntu shell. DSE generates a linux folder, not a linux.zip file. Replace the example path, user, and IP with the actual values.

ssh <linux-user>@<VM-IP> "rm -rf /home/<linux-user>/dse-deploy/linux && mkdir -p /home/<linux-user>/dse-deploy"
scp -r "C:\Path\To\GeneratedDeployables\...\linux" <linux-user>@<VM-IP>:/home/<linux-user>/dse-deploy/

5. Prepare the deployable

Install socat if you will use the relay method, enter the copied linux-x64 directory, and apply Linux execute permissions. Current DSE-generated shell scripts are UTF-8 without a BOM; no extraction or BOM-removal step is required.

sudo apt update && sudo apt install -y socat
cd ~/dse-deploy/linux/linux-x64
chmod +x DataSourceExplorer.Runner manager.sh run.sh
ls -l DataSourceExplorer.Runner manager.sh run.sh

6. Verify source/destination connectivity

Before starting DSE, test that the Ubuntu VM can reach the required data source or destination port. The example below uses MongoDB on port 27017.

timeout 5 bash -c '</dev/tcp/<source-host>/<source-port>' \
  && echo 'Port reachable' \
  || echo 'Port NOT reachable'

# MongoDB example
timeout 5 bash -c '</dev/tcp/192.168.50.124/27017' \
  && echo 'MongoDB port reachable' \
  || echo 'MongoDB port NOT reachable'

7. Start the DSE Deployable Runtime Manager

Start the manager and read its console log. The manager binds to 127.0.0.1 and selects a local port.

cd ~/dse-deploy/linux/linux-x64
./manager.sh
sleep 2
cat .dse-manager/manager-console.log
curl http://127.0.0.1:<manager-port>/ | head

8. Make the manager available to the Windows browser

Use socat on Ubuntu to relay a stable VM port (18093) to the manager's current loopback port. The commands below detect both the VM IP and the manager port automatically.

cd ~/dse-deploy/linux/linux-x64
VM_IP=$(hostname -I | awk '{print $1}')
MANAGER_PORT=$(grep -oE '127\.0\.0\.1:[0-9]+' .dse-manager/manager-console.log | tail -1 | cut -d: -f2)
nohup socat TCP-LISTEN:18093,bind="$VM_IP",reuseaddr,fork TCP:127.0.0.1:"$MANAGER_PORT" > ~/dse-relay.log 2>&1 &
echo "Open: http://$VM_IP:18093/"
ss -ltnp | grep 18093

9. Run the deployable from the UI

1. Open the URL printed by the relay command in Edge or Chrome.
2. Confirm Runtime status shows READY and no active execution.
3. In Connections, confirm the source and destination show Configured. Leave protected connection fields blank when you want to keep the embedded values.
4. Set Scheduler configuration to Manual only for the first test. Set Output directory to output and save the runtime settings.
5. Select Run now. Wait for the status to return to READY.
6. Confirm Last result and Run history show Success, then verify the expected output files and destination data.

10. Stop, restart, and clean up

The VM IP and manager port can change after a VM restart. Start manager.sh again, read the new port, and restart the socat relay. To stop the relay:

pkill -f 'socat TCP-LISTEN:18093' || true

Verification checklist

• Ubuntu boots from the VHDX and SSH login works
• Root filesystem has adequate free space
• Data source/destination port is reachable from Ubuntu
• DataSourceExplorer.Runner, manager.sh, and run.sh are executable
• manager-console.log reports a local management URL
• Windows browser opens http://<VM-IP>:18093/
• Runtime status returns to READY after Run now
• Run history shows Success and expected output/destination data is present

Troubleshooting

Related resources

Use the video tutorial for a visual walkthrough, or return to the documentation center for additional DSE resources.

Documentation Home  •  Multilingual Video Help  •  Installation Guide  •  DSE Website