The jtl-bridge helper
jtl-bridge reads JTL-Wawi (database or REST API) in the company network and uploads the data to allverto in encrypted form. Commands, options and security.
jtl-bridge is a small command-line program for the migration. It runs on a computer in your company network – where JTL-Wawi and its SQL Server can be reached –, reads the data and uploads it to allverto over an encrypted connection. This way you don't have to expose either your database or the Wawi's REST server to the internet.
How jtl-bridge gets its credentials
You store the server, user and password or the address and API key in the migration wizard. jtl-bridge signs in to allverto with the import token and fetches these details in encrypted form. Alternatively, you set the password and API key only locally (JTL_DB_PASSWORD, JTL_API_KEY).
You generate the import token in the wizard with Create import token. It is shown only once and is valid for 30 days, at most until the migration is completed. Extend by 30 days extends it from today; with New import token, the old one becomes invalid. The token is also only valid as long as the person who created or last extended it is active and may "Migrate from JTL-Wawi".
Commands
| Command | What for |
|---|---|
jtl-bridge check --url <allverto-address> --token <import-token> | Check the connection and database structure, count quantities – uploads nothing. |
jtl-bridge upload --url <allverto-address> --token <import-token> | Read and upload data. |
jtl-bridge register --api-url http://wawi-server:<port>/api/eazybusiness | Register allverto as an app in the Wawi and fetch the API key (see Setting up the REST API). |
The wizard shows the matching upload command with your address in the jtl-bridge helper box – with a button to copy it.
Important options
| Option | Meaning |
|---|---|
--source db, --source api | Force the route (otherwise the source from allverto applies) |
--fill-from-db | With the API route: add from the database what the API doesn't deliver |
--until YYYY-MM-DD | only documents up to this day (changeover date) |
--entities a,b,c | only certain data types |
--no-pdfs | don't fetch invoice PDFs |
--db-host, --db-instance, --db-port, --db-name, --db-user, --db-encrypt | Override database details locally |
--api-url | Override the REST server address locally |
Security
- jtl-bridge uploads only via HTTPS and aborts otherwise (“Nur HTTPS ist erlaubt (Daten verlassen das Firmennetz).” – only HTTPS is allowed, data leaves the company network).
- In addition to the HTTPS connection, the data is encrypted with a key derived from the import token.
- allverto only stores a fingerprint of the import token, never the token itself.
- After ten invalid tokens from the same address, allverto blocks further attempts for a few minutes.
- After Complete changeover, the token is invalid and the cached JTL data is deleted.
Typical flow
jtl-bridge check …– is everything OK?jtl-bridge upload …– upload the data.- In allverto: Mappings → Dry run → Migration.
- Before the changeover date, run
uploadagain and in allverto Start delta run.