Documentation
Back to website >

Install shop interface

The SHOP interface expects an installed EULANDA and the installed SHOP system nopCommerce:

  • Serial number for SHOP interface
  • Administration password of the PC
  • Administration password of the SQL server (the user is always called"sa" here)
  • The data for: E-mail, PublicKey and PrivateKey from the installation of the Odata plug-in
  • Check prerequisites

Note that a separate SHOP interface is required for each EULANDA client. In contrast to integrated modules, plug-ins must always be licensed individually
If you have not yet installed the ODATA plug-in for the nopCommerce shop, you will find instructions in the chapter on nopCommerce.

If you have not yet installed the ODATA plug-in for the nopCommerce shop, you will find instructions in the chapter on nopCommerce.

Installation with direct connection to nopCommerce-SHOP

For the installation the following files are delivered in a ZIP file.

  • Default.ini
  • DMS.cninst
  • SHOP.sql
  • SHOP.cnreg
  • EUL.exe
  • NOP.exe
  • PIC.exe
  • KEY.exe
  • JobOrder.bat
  • JobStock.bat
  • JobProduct.bat

  1. First create a file folder on the hard disk of the EULANDA SQL-Server. We recommend creating the folder "C:\Exchange\Mlient" and unpacking or copying the installation files into it.
  2. Start EULANDA and install the DMS system "DMS.cninst" under accessories and there under "Plugin-Manager". If the document system is already installed, this step is not necessary.
  3. In the next step, call up the SQL registry under the EULANDA system management and import the file "SHOP.cnreg".
  4. Next open the SQL-Designer under EULANDA system management. Log on as sa user with the corresponding sa password (administration password of the SQL server) under File and with the item "Log on SQL user again". Read the file "SHOP.sql" under "Load Script", execute it under the menu item "Edit" and.
  5. Rename the file "Default.ini" to "Config.ini". For security reasons, the template is not delivered as Config.ini, so that it is not automatically overwritten during an update.
  6. Double-click on "Config.ini" and start completing the configuration. The default profile is called[EULANDA]. Add the necessary parameters there.
    The cryptic key information from the ODATA installation such as PublicKey and "AuthInfo" are also stored in the configuration file.
    After saving the configuration file in the folder of the installation files, you are done with the actual installation.

If you have used a section name other than[EULANDA], the BAT files (= batch files) in Notepad must be adapted via the "Profile" parameter.
Stock movements are transferred via "JobStock.bat" and orders are read in via "JobOrder.bat". All three batch files can be entered via Windows task scheduling and retrieved at specific intervals
We recommend that the product transfer is only carried out once a day, for example at "02:00" at night. The other two batch files can be executed at short intervals such as 5-minute intervals.