Firebird test environment

The following describes the creation of an esoffice test environment when using a Firebird database.

Tools required:

• FlameRobin

• esdbm

Copying the esoffice Firebird database

Copying a Firebird database with the FlameRobin tool for a test environment, for example. This backs up the database once (Backup) and restores it under a different name (Restore).

Save database (backup)

Firebird database backup

1. Open the Flamerobin tool

2. Right click on the esoffice database (usually ESDATA)

3. Select Tools > Backup database in the context menu

   

4. The target for the database backup is set in the following dialog.

Backup File

The path for the backup file is specified here. This should ideally indicate the same folder where ESDATA.FDB is located. The name of the backup file itself will be ESDATA.FBK in this case.

5. Now click on the Start Backup button.

6. A message in the lower part of the window indicates when the backup is complete (Database backup finished...). You can close the window once the backup is finished.

   

Create alias for database copy

To enable access to the copied database, you must create a database alias.

1. Open the esdbm menu and select the command.Connection settings

2. In the Databases list, mark the alias for the esoffice productive database (usually ESWin). Then click on the Duplicate link icon in the toolbar.

   

3. A copy of the database alias will be created. Change the Alias name to ESWin_Test, for example.

4. Now enter the name of the copied database under DataBase and then click on the Save button in the toolbar.

   

5. You can test that the link to the database works by clicking the Test link button or by pressing the F9 key.

SQL script execution

The next step requires execution of an SQL script on the database copy to remove the links to the productive system.

1. Download the file and unpack the file.Testumgebung.zip The ZIP file contains the SQL script Testumgebung_Demo_esoffice_datenbank_werte_löschen.sql. You can also copy the script below onto the clipboard, paste it into an editor (Notepad, for example) and save it as an SQL file.

    

   You can adjust the script to your requirements if you have the necessary knowledge of SQL.

   Copy

   SQL script Testumgebung_Demo_esoffice_datenbank_werte_löschen.sql

   /* ########## Dokumentenpfade ########## */Wurzelpfad entfernen (Vermeidung von Zugriff auf produktives DMS)
   UPDATE EinGlob SET EinGlobValue=“ WHERE EinGlobID=10;
   Diverse Pfade entfernen (Vermeidung von Zugriff auf produktives DMS)
   UPDATE DokuPfad SET Pfad=“;
   /* ########## Einstellungen allgemein ########## */
   Clientadministration deaktivieren (Suche nach Serverdiensten verhindern)
   UPDATE EinAllg SET EinAllgValue='0' WHERE EinAllgID=10706;
   EMail über Server deaktivieren (Suche nach Serverdiensten verhindern)
   UPDATE EinAllg SET EinAllgValue='0' WHERE EinAllgID=363;
   EMail Import für die Mailgruppen deaktivieren
   DELETE FROM MailGrp;
   /* ########## Exchange Einstellungen ########## */
   Exchange Abgleich deaktivieren
   UPDATE SetServer SET SetValue='0' WHERE SetID=10607;
   Exchange URL entfernen
   UPDATE SetServer SET SetValue=“ WHERE SetID=10609;
   Autodiscvover deaktivieren
   UPDATE SetServer SET SetValue=“ WHERE SetID=10610;
   /* ########## esServer Einstellungen allgemein ########## */
   Verbindung zu den Serverdiensten entfernen
   UPDATE SetServer SET SetValue=“ WHERE SetID IN (31,32);
   /* ########## Diamant ##########*/
   nur notwendig, wenn die Schnittstelle zur Diamant-Fibu vorhanden ist
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 422;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 423;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 424;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 438;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 444;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 445;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 446;
   UPDATE EinAllg SET EinAllgValue = „ WHERE EinAllgID = 447;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 448;
   UPDATE EinAllg SET EinAllgValue = „ WHERE EinAllgID = 457;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 458;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 459;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 460;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 461;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 598;
   UPDATE EinAllg SET EinAllgValue = '01-01-0001 00:00:00' WHERE EinAllgID = 620;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 9508;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 9509;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 9510;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 9511;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 9512;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 9513;
   UPDATE EinAllg SET EinAllgValue = „ WHERE EinAllgID = 9519;
   UPDATE EinAllg SET EinAllgValue = „ WHERE EinAllgID = 9520;
   UPDATE EinAllg SET EinAllgValue = „ WHERE EinAllgID = 9521;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 9807;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 9808;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 9809;
   UPDATE EinAllg SET EinAllgValue = 0 WHERE EinAllgID = 10516;

2. Open esdbm and select Open file in the Filemenu.

   

3. Now select the SQL script file in the file selection window and click on the Open button.

   

4. The SQL query module opens in a separate tab and the SQL script loads.

   

    

   Log in data

   An esoffice user login is required when a module is opened or a function that acesses an esoffice database is executed.

   

   The user requires 110 - Basic settings authorization.

   If you have successfully logged in to an esoffice database (alias) in esdbm, your log in data will not be requested again when you access the database alias again.

5. Select the newly created Database alias in the Databases list.

   

    

   You can make adjustments to the script before it is run. Detailed knowledge of esoffice databases and SQL is required for this.

6. Start execution of the SQL script by clicking the Execute query button.

7. A message and the execution time are displayed when the SQL script has run.

   

8. You can now close esdbm

Create program shortcut to test environment

esoffice can be started using various parameters, which can be used in a shortcut.

Also see Start parameters

Thus it is also possible to start esoffice with a different database alias using the parameter -a:.

1. Create a new shortcut to esoffice.exe, for example by copying an existing shortcut.

2. Under Target, add the parameter -a:[name of newly created database alias] to the esoffice callup, for example: -a:ESWinTest.

   

3. To ensure that the program window for the test environment can be distinguished from the productive esoffice environment, you can use the start parameter -m: to display your own text in the title bar of the program window.

   Also see Window line label