Troubleshooting the JTL migration

Here you find solutions for the most common stumbling blocks when migrating from JTL-Wawi.

#Connection

#jtl-bridge reports “Die Wawi-API … ist nicht erreichbar” (the Wawi API is not reachable)

jtl-bridge cannot reach the REST server. Check: Is the REST server running? Are the port and database name in the address correct? The port is the one you set for the REST server in the Wawi (e.g. 5883 or 5885). At startup, the program searches ports 5883 to 5890 itself and asks again after a failure. The easiest way is to start jtl-bridge directly on the computer your JTL-Wawi runs on. If you start it on another PC, the server's Windows firewall must allow the port.

#“Die Wawi-API lehnt den API-Schlüssel ab” (the Wawi API rejects the API key)

The application was removed in the Wawi or the key is wrong. Simply start jtl-bridge again: it then registers allverto anew, you click through the wizard in the Wawi up to Einrichtung abschließen, and the new key replaces the old one. Details: Setting up the REST API.

#How do I register allverto in the Wawi?

In JTL-Wawi, open Anwendungsregistrierungen (application registrations) → Anwendung registrieren (register application) and click on to Registrierung beginnen (start registration). Only when it says “Es wird auf die Übermittlung einer Registrierungsanfrage … gewartet” (waiting for a registration request) there, press Enter in the jtl-bridge window – before that, the Wawi doesn't accept a request. Then click Weiter (next) on Anwendungsinformationen and Benutzer (pre-filled with the user you are logged in with), tick all three rows in the Erteilen (grant) column under Zugriffsverwaltung (all.read is already ticked; also salesinvoices.print and salesinvoicecorrections.print so allverto can take over the original PDFs of your invoices and invoice corrections) and click Einrichtung abschließen.

#Where do I find the API key in the Wawi?

Nowhere – and that is intended. The Wawi doesn't show a key and doesn't create one at the push of a button. It only issues it to an application that is requesting one right now. jtl-bridge takes care of that and hands the key over to allverto encrypted.

#“Test connection” says jtl-bridge does the test

Your address (e.g. localhost or 192.168.…) can only be reached on your server or in your company network, not from the internet. Start jtl-bridge on the server and paste the setup code – the result appears in the wizard.

#The window reports “Login failed” for the SQL Server

This means the user and password of the SQL Server (usually sa), not your sign-in to JTL-Wawi. After a failure, the window asks again – just enter the details once more. Details: Access via the JTL database.

#“Nur HTTPS ist erlaubt” (only HTTPS is allowed)

For security reasons, jtl-bridge only uploads via https://. Copy the setup code from allverto again – it contains the correct address.

#“Fetch data directly now” fails

This only works if your Wawi server is reachable from the internet and opens the port for the allverto servers (2.31.70.120, 2.31.74.112, 2.31.72.228). Check the address with Test connection. For the Wawi API, the API key must also be stored (Send registration from allverto). If your server is only reachable in your network, use jtl-bridge on the computer your JTL-Wawi runs on.

#“Dein REST-Server antwortet nur über HTTPS” (your REST server only answers over HTTPS)

Your REST server only accepts connections via https://. In the test result, click Change address to https://. allverto saves the address and tests again.

#allverto asks about the certificate

Your REST server uses a self-created certificate. allverto shows the fingerprint (SHA-256), the issuer and the validity. Compare the fingerprint with the certificate on your server and click Trust this certificate. After that, allverto only connects with exactly this certificate. If allverto later reports a different certificate, only confirm it if you renewed it yourself.

#Data and dry run

#The quantities under “Data found” don't match my Wawi

If you entered a changeover date, only documents up to that day are taken into account. With the API route, subscriptions and supplier invoices are missing if Add missing data from the database is off.

#What do the results in the log mean?

For each record you see whether it was newly created, updated, skipped (unchanged or not supported) or rejected – with the reason. Filter by result and data type and download the log as CSV if needed.

#Why are some attributes “skipped”?

The Wawi API only delivers item attributes as an ID without a name. With Add missing data from the database, jtl-bridge adds the names.

#Will data be created twice if I migrate several times?

No. For every JTL record, allverto remembers what it became. Unchanged records are skipped, changed ones are updated.

#Why don't migrated invoices draw a new number?

Documents are taken over 1:1 with their original number from JTL. That's why you migrate the number ranges first – so numbering continues with the next free number after the migration.

#Completion

#Can I sync again after completing?

No. After Complete changeover, the setup code is invalid and the staging area is deleted. So on the changeover date, first start a delta run and check the log.

#Are the logs kept?

Yes. Migrated data, mappings and logs are kept even after completion.