Access via the JTL database

JTL-Wawi stores everything in a Microsoft SQL Server database, usually named eazybusiness. With this route, allverto reads the data directly from there – without any REST server or application registration. It is the most complete route. If your SQL Server is reachable from the internet (e.g. on a rented server), allverto fetches the data itself. If it is only reachable in your network, the jtl-bridge helper transfers the data.

#Directly from allverto (main route)

If your SQL Server runs on a rented server and is reachable from the internet, allverto fetches the data itself. You then don't need any program on your server.

This works if:

• the SQL Server is reachable under a public IP address or a public name – not under localhost, an address in your office network or a computer name.
• the port is 1433 or 1024 or higher.
• the SQL Server user and password are stored.

How to do it:

1. Open Settings → Data migration → Migration from JTL-Wawi, step Connect source, and choose JTL database.
2. Under Connection details, enter the SQL server (e.g. 217.160.19.64), the Port, the User and the Password. You can also add the port after a comma, e.g. 217.160.19.64,10401.
3. Click Save and then Test connection. allverto checks the login and reads the Wawi version.
4. Click Fetch data directly now. allverto fetches the data in the background. The quantities then appear under Data found.

If you enter localhost or an address from your office network, the field shows: “This address is only reachable on your server. Enter your server's public IP – or use jtl-bridge below.” If your SQL Server is not reachable from the internet, use the route with jtl-bridge further below.

#What you need

• Access to your Wawi's SQL Server. On the computer your JTL-Wawi runs on, this is usually server localhost with the instance JTLWAWI.
• The SQL Server user and its password – usually sa. This is not the user you sign in to JTL-Wawi with. You set the password when installing the Wawi or the SQL Server (or your JTL service partner knows it). If you like, you can create a separate user with read permission only instead – jtl-bridge never writes anything to your Wawi.

#With jtl-bridge (server not reachable from the internet)

1. Open Settings → Data migration → Migration from JTL-Wawi, step Connect source, and choose JTL database. You don't have to enter anything – jtl-bridge enters the details.
2. Expand the box Server not reachable from the internet? Transfer data with jtl-bridge below and follow the steps (in detail: The jtl-bridge helper):
   1. Download jtl-bridge.
   2. Copy the file to the server your JTL-Wawi runs on – e.g. via Remote Desktop onto the desktop.
   3. On the server, start the file with a double-click.
   4. Click “Create setup code” here, copy the code, paste it into the window with a right-click and press Enter.
   5. Answer the questions in the window – usually Enter is enough.
   6. Wait until “Done” appears – allverto then ticks off the step.
3. The window asks for SQL Server [localhost], Instance [JTLWAWI], Database [eazybusiness], User [sa] and Password. If the suggestion in brackets fits, just press Enter. If there is no instance, enter a minus -. You don't see the password while typing.
4. The program checks the login right away. If it doesn't work, it explains why and asks again. It hands the checked details over to allverto encrypted; in the wizard they appear under Connection details. The password is never shown.
5. In the window, jtl-bridge reports the Wawi version and the company and checks whether all required tables and columns exist (“Schema-Prüfung: alle benötigten Tabellen und Spalten vorhanden.” – schema check: all required tables and columns present). Then it uploads the data.
6. In allverto, the Detected source box shows the version, company and time of the last upload. Continue with Data found.

#If signing in to the SQL Server fails

If the window reports “connection to SQL Server failed” or “Login failed for user …”:

• After a failure, the window asks for all details again. Just enter the user and password correctly once more.
• This means the SQL Server user (usually sa), not your Wawi user.
• Check SQL Server and instance. On the Wawi server, localhost with instance JTLWAWI usually fits. If you entered the IP address of the server the program is running on, localhost is enough.

#Test connection

With Test connection, allverto checks your SQL Server itself if it is reachable from the internet: login and Wawi version. The result appears in the wizard, e.g. “Last checked by allverto: connected ✓”.

If your SQL Server is under localhost, an address in your office network or a computer name, allverto cannot reach it. Then jtl-bridge does the test and reports the result, e.g. “Last checked by jtl-bridge: connected ✓”.

#What is only possible via the database

• Subscriptions (recurring orders from JTL)
• Supplier invoices
• Lines of invoice corrections
• Number range counters exactly as the Wawi keeps them
• Bill of materials components, attribute names and SEPA mandates of customer bank accounts

#Versions

The database structure changes between Wawi versions. allverto detects the version and reads accordingly. This route is tested for Wawi 2.1 and 2.2; older versions from 1.5 can usually be read but are not tested. jtl-bridge reports missing tables or columns before anything is uploaded (“FEHLT: …” (missing) or “Optional fehlt: …” (optional, missing)).