How to install and configure Pawa Connector (Windows)

Prerequisites

• A Windows 10/11 system with write access to D:\Pawa.

• Network access to your Pawa instance (e.g., https://yourinstance.pawa.zone/).

• A Pawa API token.

• Access to your data source (e.g., via ODBC DSN).

• .NET Desktop Runtime if required by your environment.

• Administrative rights to create Windows Scheduled Tasks.

Download and Unblock the Pawa Connector

1. Download Pawa Connector from:
   https://secure.pawa.zone/PawaConnector.zip

2. Before extracting:

   • Right-click the ZIP file → Properties.

   • On the General tab, check Unblock (if visible).

   • Click Apply → OK.

3. Extract the ZIP into D:\Pawa\PawaConnector\.

If you skip the unblock step, Windows may block executables and prevent them from running.

Recommended Folder Structure

Create the following structure in D:\Pawa

• D:\Pawa

  ├─ configs\

  │ └─ configs.json

  ├─ scripts\

  │ └─ ImportTSUMasterList.sql

  ├─ logs\

  │ └─ prod.log

  ├─ PawaConnector\

  │ ├─ Pawa.Connector.exe

  │ └─ Tools.json

  ├─ LoadToPawa.bat

  └─ pawa.token

Suggested configuration

Create the Batch File (LoadToPawa.bat)

Create D:\Pawa\LoadToPawa.bat with the following content:

cd /d %~dp0 
cd PawaConnector
Pawa.Connector.exe --Tool ApiLoader --Args ..\configs\configs.json > ..\logs\prod.log

echo %errorlevel%

exit %errorlevel%

• Execution logs are saved to D:\Pawa\logs\prod.log.

• The process exit code is propagated, useful for monitoring or scheduled tasks.

Configure Tools.json

Edit or create D:\Pawa\PawaConnector\Tools.json

[
  {
    "ToolName": "ApiLoader",
    "ApiBearerToken": "file:..\\pawa.token",
    "CheckVersionUrl": "https://yourinstance.pawa.zone/api/api-loader/version",
    "DownloadPackageUrl": "https://yourinstance.pawa.zone/api/api-loader/download",
    "ExeName": "Pawa.ApiLoader.exe"
  }
]

Replace yourinstance.pawa.zone with your Pawa instance domain.

Configure configs.json

Edit or create D:\Pawa\configs\configs.json

{
  "ApiSettings": {
    "PawaRootUrl": "https://yourinstance.pawa.zone/",
    "ApiToken": "file:..\\pawa.token"
  },
"EmailSettings": {
    "FailureEmailAddress": "youremail@domain.com"
  },
  "ImportSettings": {
      "DataSourceConnectionString": "DSN=Pawa........",
      "DataSourceProvider": "ODBC",
      "Imports": [
	{
      "Api": "Core",
	  "Methodname": "CreateHealthMonitorLog",
	  "DataSourceQuery": "SELECT 'Importation Update Start' Source, 'start' JsonLog"
     },
     {
       "Api": "Sop",
       "Methodname": "ImportTSUMasterList",
       "DataSourceQueryFile": "scripts\\30-ImportTSUMasterList.sql"
     },
     {
       "Api": "Core",
	   "Methodname": "CreateHealthMonitorLog",
	   "DataSourceQuery": "SELECT 'Importation Success NaturaeDecor' Source, 'start' JsonLog"
      }
 	]
  }
}

PawaRootUrl → your Pawa instance.
FailureEmailAddress → recipient of error alerts.
DataSourceConnectionString → your ODBC DSN or connection string.
scripts\*.sql → adjust to match your SQL script names.

Add the Pawa API Token

• Create a file: D:\Pawa\pawa.token.

• Paste your API token as a single line (no quotes).

• Restrict access to this file for security (e.g., NTFS permissions).

Test a Manual Run

Double click on D:\Pawa\LoadToPawa.bat

No Administrator right required

• Check D:\Pawa\logs\prod.log for success or errors.

• Validate in your Pawa instance (Health Monitor or entity data) that imports succeeded.

Schedule Automatic Execution (Windows Task Scheduler)

• Open Task Scheduler → Create Task….

• General Tab

  • Name: Pawa – LoadToPawa

  • Check: Run with highest privileges

  • Configure for: Windows 10/11

• Triggers Tab

  • New trigger:

    • Every X hours: Choose Daily → Repeat task every X hours → Indefinitely.

    • Every X days: Choose Daily → Recur every X days.

• Actions Tab

  • Program/script: D:\Pawa\LoadToPawa.bat

• Settings Tab

  • Check Run task as soon as possible after a missed start.

  • Check Stop task if it runs longer than 2 hours.

• Save the task and provide credentials if prompted.

• Test by right-clicking the task → Run. Verify prod.log.