Support

After installation, ARGEKA Sync runs locally. Use http://localhost:8080 for the panel and review each connection, query, mapping and run log before production use.

First login

The demo account is admin@argeka.local / admin123. Change the password before real use.

Connection test

Check host, port, database name, user permissions, SSL mode and VPN requirements before connecting to an ERP database.

Backup

Use backup.ps1 and restore.ps1 as a starting point for local backup and restore operations.

Connection and query support

Support starts with connection boundaries. Source ERP databases should use read-only technical users whenever possible, while target reporting databases can have permissions according to insert or upsert needs. SQL date fields also need review because document date, movement date, created date and closing date may not mean the same thing.

Column mapping is the contract of the transfer. If a source text value is mapped to a numeric target column, or if a required target field is empty, the run should fail or quarantine the row according to the selected policy.

Production support workflow

When a transfer fails, support should start with the run log. Read count, written count, skipped rows and error messages usually show whether the problem is in the source query, the target table, the mapping or the connection. The same source query should then be tested with the same parameters outside the scheduled job.

Column mapping problems are common in ERP environments. A field that looks like a number may contain text in old records, date fields may use different meanings and required target fields may not exist in the source query. ARGEKA Sync keeps these decisions visible so support can review the exact mapping instead of guessing from a hidden script.

Before enabling schedules

Run each job manually with a small dataset first. Confirm normal records, exception records and expected failure records. Only after this review should hourly, daily or weekly schedules be enabled.