Set up SW-1100 Dibal
This profile queries the MySQL database of the Dibal software prepared by the supplier. Configure the cash machine and currency separately. The historical names SW1100Dibal V2 and V3 refer to this guide; retain working settings until the supplier confirms any change.
Preparation and commissioning
- Prepare the installation. Ask the administrator for the MySQL destination, active database and a private account authorised to read this integration. Check access from the Windows computer running ImaCash.
- Select the profile. In Configuration > Integration, choose POS and then SW1100Dibal. Retail is the website category; the application selector uses POS.
- Save the configuration. Complete the four fields. When closing, confirm saving if prompted and follow the proposed restart where applicable. A connection check does not validate tickets or cash.
- Check the workflow. In Settings, check terminal and operator filters against the installation’s values. During a supervised test, compare reference, date, terminal, operator, amount, sign and payment method with the source and actual cash.
The four private MySQL settings
The “Server IP” field identifies the MySQL service of the Dibal software. “Database name” takes the exact active database; “User” and “Password” take the private read account. The current selector has no port, folder, file or DSN field for this profile. There are no universal access values.
Tickets, terminals and payment methods
Reading from the synchronisation date may include amounts by payment method and supported cash drawer movements. The supplier must confirm cash, card, other payment and sign mapping. Terminals and operators identify the source, not the cash device. No product catalogue, shifts or bank totals are imported.
Reading and closure require separate checks
Seeing a ticket does not prove payment or closure. Local confirmation or rejection writes neither closure nor cancellation to Dibal. Agree on reconciling both programs. The Accept cards option does not prove a bank transaction.
Resynchronisation and uncertain outcomes
Resynchronising by date guarantees neither a complete history nor permission to charge again. After waiting or an uncertain outcome, review the source ticket, ImaCash and actual cash before repeating, resynchronising or restarting.