Abas Sql Connector 2.1.0

ABAS SQL CONNECTOR 2.1.0

LEGAL DISCLAIMER

The names and data used in this manual are entirely fictitious. Please note that the abas ERP version of this manual may differ from your abas ERP version.

The content of this document has been compiled with the utmost care. However, should you notice any errors, please do not hesitate to contact us. Please note that abas Software GmbH cannot be held liable for the accuracy of the content of this manual.

This manual is protected by copyright. Any reproduction and distribution, in whatever form or by whatever media, is prohibited without the prior written consent of abas Software GmbH.

Revision 2

TABLE OF CONTENTS

1 Introduction...... 9 2 Licensing of abas SQL Connector...... 11 3 Setting up the abas ERP clients ...... 12 3.1 Requirements ...... 12 3.2 Installing the SQLConnectorExtensionPack abas ESDK package ...... 12 3.3 Communication of abas SQL Connector via abas REST API...... 13 4 Installing and registering abas SQL Connector on the Microsoft Windows server...... 14 4.1 Microsoft Windows server system requirements...... 14 4.2 Microsoft SQL server requirements ...... 15 4.3 Installing abas SQL Connector...... 16 4.4 Registering abas SQL Connector at an MS SQL database...... 17 4.5 Starting the user interface ...... 18 4.6 Subsequently changing the connection to the configuration database ...... 19 5 Working with abas SQL Connector...... 21 5.1 Connecting abas ERP clients ...... 21 5.2 Windows service administration...... 27 5.3 Logging in abas SQL Connector...... 30 5.4 Applications ...... 32 5.5 Database synchronization ...... 35 5.6 Infosystem synchronization...... 46 5.7 Down Times ...... 51 6 Upgrading abas SQL Connector version 1...... 53 6.1 Requirements ...... 53 6.2 Transferring the field list from version 1 to version 2...... 54 6.3 Follow-up work ...... 54 7 Appendix ...... 55 7.1 Related links ...... 55 7.2 Index ...... 57

HOW TO USE THIS MANUAL

The most important information for using this manual effectively can be found below. STRUCTURE

At the start of each chapter, there is an introduction to the topic which is covered in the respective chapter Most of the chapters contain guidelines in addition to useful information Exercises and solutions for the training are provided in the corresponding workbooks and solution books An index can be found at the end of the manual SYMBOLS

TYPOGRAPHY

ABAS SQL CONNECTOR

1 INTRODUCTION

This manual will show you

how to prepare abas ERP clients for the connection to abas SQL Connector how to install and configure abas SQL Connector on a Windows server how to use and administrate abas SQL Connector

abas SQL Connector is a Microsoft Windows Server application ™ which consists of a user interface and two Windows services.

abas SQL Connector provides the following options:

Export data from tables from databases of different abas ERP clients to a Microsoft SQL Server™ database Incrementally synchronize the exported data with the data set of the connected abas ERP clients Export execution results of infosystems in multiple clients to Microsoft SQL Server™ database tables in a configurable mode

If abas ERP clients are to be connected to one or multiple MS SQL databases through abas SQL Connector, it must be possible to access them via abas REST API. Furthermore, the supplied SQLConnectorExtensionPack must be installed in the appropriate version in these clients.

Further information can be found under Setting up the abas ERP clients (see page 12).

abas SQL Connector consists of the following components:

User interface to configure the interface abas SQL Connector Windows service to synchronize abas ERP databases abas SQL Connector – Infosystem Windows service to synchronize the execution results of infosystems SQLConnectorExtensionPack abas ESDK package for installation in the connected abas ERP clients abas SQL Connector is available as an openly configurable or closed interface.

9 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

OPEN INTERFACE

The open version of abas SQL Connector is subject to a fee and is activated through the licensing of at least one connected abas ERP client.

You have the following options:

Configure database synchronization: configuring new databases for synchronization or expanding existing ones Synchronize execution results of infosystems from multiple abas ERP clients with tables in MS SQL Server

CLOSED INTERFACE

In this version, you can only synchronize databases of abas ERP clients with an MS SQL Server database. It is not possible to export execution results of infosystems. You can export data from abas ERP clients only with defined, not changeable formats. These formats are represented by encrypted XML files, which you can only obtain together with products using abas SQL Connector.

EXAMPLE

The encrypted XML file abasBI.exml is supplied with abas BI Essentials, using which you can create the basis for abas BI through abas SQL Connector.

10 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

2 LICENSING OF ABAS SQL CONNECTOR

This chapter will show you

how to license abas SQL Connector which license types are available

abas SQL Connector communicates with the connected abas ERP clients via abas REST API. For this, you must license at least one of the connected clients for abas SQL Connector. To ensure stable operation of abas SQL Connector, it should be possible to access this client via abas REST API at all times.

To determine the license type, run the View configuration command > Expansions page tab MS SQL section in the Master files > Systems admin. files > Configuration > Application folder in abas ERP.

A license is required for abas SQL Connector (MS SQL Connector checkbox) in order to use it for the configurable synchronization of database tables from abas ERP clients and the synchronization of infosystems.

If you select the abas BI Professional license type in addition, Primary- and Foreignkey- fields are generated for all applications in abas SQL Connector for database synchronization as well as for infosystem synchronization.

Further information on the effects of the different license types can be found under Windows service administration (see page 27).

Further information can be found under the key word License type in the daily updated Online Help (see page 55).

11 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

3 SETTING UP THE ABAS ERP CLIENTS

This chapter will show you

which requirements must be met in abas ERP clients to use them with abas SQL Connector how to prepare abas ERP clients for the use with abas SQL Connector

3.1 REQUIREMENTS abas ERP clients from Version 2016r4n13 can be used together with abas SQL Connector. For abas ERP clients to be connected with abas SQL Connector, it must be possible to access them via abas REST. Another requirement is the installation of the supplied SQLConnectorExtensionPack abas ESDK package matching the main version of the client.

Furthermore, the MS SQL server in which the client data should be transferred must be accessible from the Linux environment via an ODBC connection. 3.2 INSTALLING THE SQLCONNECTOREXTENSIONPACK ABAS ESDK PACKAGE

The SQLConnectorExtensionPack abas ESDK package enables abas ERP clients to export data to MS SQL databases via abas SQL Connector. The ESDK package replaces all Linux scripts as well as the Samba share, which were required for operating abas SQL Connector version 1. Before the installation, select the ESDK package version compatible with your client from the installation archive of abas SQL Connector.

EXAMPLE

If you operate a client of the main version 2018r4, you must use the SQLSync-2018r4-(version)-standalone-app.jar ESDK package in this client.

To install the SQLSync ESDK package, the following is required:

Shell login for the server on which the client that you would like to connect with abas SQL Connector is located abas EDP user User rights to install infosystems in the relevant abas ERP client User rights to create infosystem workspaces in abas ERP

You can find further detailed information on the installation of the ESDK package as well as a Linux script to facilitate the installation in the download archive for the SQLConnectorExtensionPack.

Further information on the installation of ESDK packages in abas ERP can be found under the key word abas-app-installer under Related links (see page 55).

12 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

Note that you'll need to assign this workspace to every user who will use the abas SQL Connector. This workspace will be automatically assigned to the EDP user that was used to install the SQLConnectorExtensionPack.

3.3 COMMUNICATION OF ABAS SQL CONNECTOR VIA ABAS REST API abas REST is a technology to communicate with abas ERP client via Hyper Text Protocol (HTTP). Via abas REST API, you can operate abas SQL Connector with abas ERP clients which are in a different network. abas REST API is available from abas ERP Version 2016r4n13 and is supplied with abas ERP. However, it is recommended to install abas REST API using Docker. Detailed instructions can be found in the abas REST API installation documentation.Ensure that at least product version 0.76.0 is selected when setting up abas REST API.

Further information on setting up abas REST can be found under Related links (see page 55).

If abas REST was set up successfully for a client, you can use this client with abas SQL Connector. Requirement: The SQLConnectorExtensionPack abas ESDK package was also successfully installed in this client. Furthermore, clients can now be connected to abas SQL Connector through abas Cloud Connect.

abas Cloud Connect is a technology to implement Hybrid Cloud scenarios with abas ERP. The connection of a client through abas Cloud Connect allows this client to be in different network than abas SQL Connector.

13 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

4 INSTALLING AND REGISTERING ABAS SQL CONNECTOR ON THE MICROSOFT WINDOWS SERVER

This chapter will show you

which system requirements apply which requirements the connected MS SQL server must met how to install and configure abas SQL Connector

4.1 MICROSOFT WINDOWS SERVER SYSTEM REQUIREMENTS

To operate abas SQL Connector, you require a Microsoft Windows server. This Windows server should meet the following requirements:

Hardware/Software requirements

RAM 8 GB or more

Hard disk Approx. 50 MB

Screen resolution 1280 x 1024 pixels

Operating system Microsoft Windows Server 2008 R2 – Windows Server 2016

MS SQL Server At least standard edition 2012, 2014, 2016, 2017

.NET Framework 4.6.2 or higher

Service account for SQL Connector Local system account

If you intend to jointly operate SQL Connector and MS SQL Server on a host system, you can find a detailed description of the hardware and software requirements in the Hardware requirements for abas BI servers document. Further information can be found under Related links (see page 55).

When using a firewall, ensure that the outgoing HTTP/HTTPS connections for the service account of the abas SQL Connector are permitted.

14 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

If a firewall is active on the Microsoft Windows server, you'll need to ensure that incoming and outgoing connections for the MS SQL server are permitted. Further information can be found under Related links (see page 55).

4.2 MICROSOFT SQL SERVER REQUIREMENTS

abas SQL Connector exports data from abas ERP to Microsoft SQL Server. The following Microsoft SQL Server editions are supported:

At least standard edition of MS SQL Server 2012, 2014, 2016, 2017 Azure SQL Database-as-a-Service databases

When configuring abas SQL Connector, it is registered at an MS SQL database. For this registration, you require an SQL Server user with at least the following server roles:

public db_creator

Furthermore, the abas SQL Connector requires a database collation, which does not take uppercase and lowercase into account. We recommend using Latin1_General_CI_AS for this.

Further information can be found under Related links (see page 55).

When using the abas SQL Connector, we recommend the option Simple in the recovery model of the database. Other recovery models tend to let the log files of the abas SQL Connector database become unnecessarily large.

Further information about the Recovery mode in the MS SQL server can be found under Related links (see page 55).

We also recommend regularly shrinking the database and the database log files.

Further information can be found under Related links (see page 55).

Further information on server roles in MS SQL Server can be found under Related links (see page 55).

If you use a database collation that takes uppercase and lowercase into account, then errors occur in the application and the tool will not be usable.

15 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

4.3 INSTALLING ABAS SQL CONNECTOR

To install abas SQL Connector on your Microsoft Windows server, unpack the content of the installation archive to any folder on your Microsoft Windows server. Perform the following steps in the directory with the installation files:

1. Open the abas SQL Connector (x64) Setup.msi file. The Setup Wizard opens. The Setup Wizard guides you through the entire setup. 2. Click Next. The Select Installation Folder step opens. You can select an alternative installation directory here, if required. 3. Click the Disk Cost button. You can use it to determine the minimum disk space required. 4. Click the OK button. 5. Use the check boxes Everyone and Just me to define whether the application can be used by all users of the server or only be the current user. We recommend the installation for all users, as this way abas SQL Connector can be operated user- independently on the server. 6. Click Next. The Confirm Installation step opens. 7. Click Next. abas SQL Connector is installed. The Installation Complete step opens. 8. Click the Close button. Result: You have installed abas SQL Connector with the two Windows services.

16 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

4.4 REGISTERING ABAS SQL CONNECTOR AT AN MS SQL DATABASE

After successfully installing abas SQL Connector, you can start operating it with an MS SQL Server user. To do so, go to the installation directory of abas SQL Connector. Run the abas.SQLConnector.UI.exe file with administrative rights. The registration window opens.

The current user requires administration rights only for the initial start of the user interface. Otherwise, the installation directory cannot be written to depending on the location in the operating system.

Proceed as follows:

1. In the Datasource field, enter the fully qualified host name or the IP address of the database under which you would like to operate abas SQL Connector. Note: a. The entry 0.0.0.0 or localhost as the host address is not permitted for the MS SQL database. b. An already existing configuration database ConnectorManagement of abas SQL Connector version 1 cannot be used for abas SQL Connector version 2. A database of version 1 must be deleted manually. 2. Enter the MS SQL Server user with which you would like to operate abas SQL Connector in the Username field. 3. Enter the password for the MS SQL user in the Password field. The Status field displays information on the registration. 4. To test the entered MS SQL connection, click the Test Connection button. 5. To register abas SQL Connector at the selected MS SQL Server database, click the Register button. Result: After successfully registering abas SQL Connector at a database, the ConnectorManagement configuration database is generated in this SQL Server database. All applications created in abas SQL Connector as well as the configuration of abas SQL Connector are managed in this database. Furthermore, the interface of abas SQL Connector opens.

Further information on user rights can be found under Microsoft SQL server requirements (see page 15).

17 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

4.5 STARTING THE USER INTERFACE

After the registration, run the abas.SQLConnector.UI.exe file again in the installation directory of abas SQL Connector. The login window of abas SQL Connector opens.

Enter the MS SQL user in the Username field with which you previously registered abas SQL Connector at the selected MS SQL database.

Enter the password of the selected MS SQL user in the Password field.

To subsequently configure the connection to the configuration database, click this button.

To close the program, click this button.

Further information on the subsequent change of the connection to the configuration database can be found under Subsequently changing the connection to the configuration database (see page 19).

18 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

4.6 SUBSEQUENTLY CHANGING THE CONNECTION TO THE CONFIGURATION DATABASE

To change the connection to the configuration database or generate it on another MS SQL database server, click the SQL icon in the login window of abas SQL Connector. The SQL Server Connection Settings registration window opens with the previously configured connection. You can change the user as well as the database connection.

CHANGING THE MS SQL USER FOR ABAS SQL CONNECTOR

If required, you can change the MS SQL user with which you are operating abas SQL Connector in the relevant database using the SQL Server Connection Settings screen. Ensure for the new user that he is allocated to the ConnectorManagement configuration database in the selected MS SQL database server.

The user must be assigned at least the following roles in the database:

public db_datareader db_datawriter

Recommendation: Assign the new MS SQL user the roles public and db_owner . Only in this way can the basic settings of the database be changed or deleted by the user.

To change an existing user, proceed as follows:

1. Open the SQL Server Connection Settings registration window opens with the configured connection. 2. Overwrite the entry in the Username field with the name of the new user. 3. Enter the password of the new user in the Password field. 4. Click the Register button. Result: abas SQL Connector is now operated with the selected user.

19 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

CHANGING THE MS SQL DATABASE CONNECTION

If you would like to operate abas SQL Connector on another MS SQL database server, you can enter the new connection here and register at this database.

Further information on registration can be found under Registering abas SQL Connector at an MS SQL database (see page 17).

20 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

5 WORKING WITH ABAS SQL CONNECTOR

This chapter will show you

how to connect abas ERP clients to abas SQL Connector how to administrate the services of abas SQL Connector how to monitor the interface how to create and manage new applications in abas SQL Connector how to synchronize abas ERP databases with MS SQL Server how to export execution results of infosystems to the MS SQL database

5.1 CONNECTING ABAS ERP CLIENTS

After you have successfully installed abas SQL Connector and registered it at an MS SQL database, the user interface opens after logging in to abas SQL Connector. If you have not set up abas clients yet, a message prompting you to set up at least one abas ERP client opens. This is a mandatory step, as only in this way the current license status of abas SQL Connector can be evaluated.

Further information can be found under Licensing of abas SQL Connector (see page 11).

To create a new abas ERP client in abas SQL Connector or to manage the connected abas ERP clients, click the following icon in the upper left corner of the user interface:

The Manage Clients screen opens. You can create, edit and delete connections to abas ERP clients in this screen.

21 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

CREATING AND CONNECTING NEW CLIENTS

Proceed as follows:

1. Click the New button in the table of the Manage Clients screen. The right window area Client is released for editing. 2. Enter a descriptive name for the client in the Displayname field. This name is used in the user interface of abas SQL Connector to uniquely reference the client. 3. Enter the abas REST API connection to the abas ERP client in the fields on the Connection page tab. 4. Use the Authentifictation Mode selection list to define how abas SQL Connector should authenticate to abas REST API. 5. Use the Operating Language selection list to define the operation language for the abas REST API connection. 6. To validate the entered MS SQL connection, click this button. Result: You can see the result of the connection attempt with the abas ERP client in the lower left corner of the window.

22 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

FIELDS ON THE CONNECTION PAGE TAB

Detailed information on steps 3 to 5:

You can use these fields to define the following properties for the connection:

Client Name: The name of the client which is to be connected. Use the name of the client defined in abas REST API, as it may differ from the actual client name (configured in abas ERP). abasRest Host: The name of the host on which abas REST is operated. abasRest Port: Optionally, you can specify a port here via which abas SQL Connector communicates with abas REST API. If you leave this field blank, no port is considered when establishing the connection to the abas ERP client. Https Connection: If you select this option, only HTTPS connections to the abas ERP client are established. This setting is particularly important if abas ERP clients are to be connected via abas Cloud Connect.

Further information can be found under Communication of abas SQL Connector via abas REST API (see page 13).

To determine authentication, you have the following options:

Basic: use of HTTP-Basic authentication to connect to abas REST API You can define a user name and password. If you use password authentication in the abas ERP client, you must specify the user name abas_. Note that HTTP-Basic authentication is primarily used if the client cannot be accessed via abas Cloud Connect. This is particularly the case if abas SQL Connector is operated in the same network as the relevant abas ERP client. Auth0: Use of Auth0 authentication If you select Auth0 authentication, you authenticate with the relevant Client Id and the corresponding Client Secret. This type of authentication is used to connect to the client when using abas Cloud Connect. You receive the Client Id and the corresponding Client Secret by setting up a new application in abas Cloud Connect.

Further information can be found under the key word abas Cloud Connect under Related links (see page 55).

This setting only affects the user interface of abas SQL Connector. The operating languages are dynamically retrieved from the client while entering the connection data. Note that this setting does not affect the results during the data export from abas ERP. Regardless of the operating language for the connection, the export in abas SQL Connector always takes place in language-independent notation.

23 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

FIELDS AND BUTTONS ON THE ADVANCED SETTINGS PAGE TAB

You can define further settings for the client here:

Inkrexport section:

The abas internal command line tool inkrexport is used to export abas ERP database tables to the abas SQL server. Similar to abas SQL Connector version 1, this tools initially writes data from abas ERP to a folder. You can define this folder in the Working Directory text field. You can define the folder relative to the client directory or relative to the root node on the relevant Linux system. Note that this folder has to be accessed from abas ERP. If Debug Mode is not active in the client, these folders are always deleted from abas ERP after the export.

You can define the size of the folder in the Directory Size in 2^x Bytes field. If a smaller folder size is selected here, the export of the data from abas ERP takes place in several steps. Smaller folder sizes may affect the execution time of the export. However, this has the positive side effect that multiple snapshots of the synchronization status can be created during the data export. The recommended folder size is between 28 and 31.

24 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

Export section:

With the Max. Concurrent Threads setting, you can define the degree of parallelization of the database export from abas ERP.

If you do not want to define a limit for the degree of parallelization of the export, activate the Unrestricted checkbox. You can restrict parallelization through the value in the Count field. This value defines how many tables can be exported in the client at the same time. This setting is particularly important if there are resource bottlenecks on the abas ERP host. There is no general recommendation for the degree of parallelization. It must be determined through a corresponding analysis of the workload on the abas ERP server during the data exports. You can define the number of database connections used when generating the field list in the Max. concurrent DB sessions field in the selected abas ERP client:

Note that a higher value is only suitable if your fields lists are correspondingly long and contain many different abas ERP database groups. In the case of short field lists, higher values may lead to performance loss. We recommend a value of 1, as this fully deactivates parallelization. Activate the Debug Mode field to activate analysis mode for the database export from abas ERP. If analysis mode is active, you can find all synchronization execution results in the defined working directory:

All files exported through inkrexport Files transformed through the ESDK SQLConnectorExtensionPack Detailed log under /java/log/sqlSync.log

Note that all execution results in the abas ERP clients will be stored when using this option. These execution results will no longer be cleaned up and must be removed manually from the abas ERP server after the analysis is complete. We recommend to use this option only in the case of difficulties during the data export from abas ERP, as in a short period of time large amounts of data will be stored on the abas ERP server.

Down Time section: Define here at which intervals no operation by abas SQL Connector can take place in the abas ERP clients.

Further information can be found under Down Times (see page 51).

If you have completely created the connection for your abas ERP client, you can generate the abas ERP client in abas SQL Connector. To do so, click the Create button. Note that only clients which can be reached via abas REST API on setup and for which the SQLConnectorExtensionPack ESDK package is installed can be created.

25 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

Note that errors can occur in the interface when copying a client and Varreorgs, if this is active at the corresponding times. For regular client copies and Varreorgs, we highly recommend setting up a down time for the corresponding clients or the corresponding application. Further information can be found under Down Times (see page 51).

If this is the first client which you connect to abas SQL Connector, the license status of abas SQL Connector is evaluated. The user interface of abas SQL Connector adapts accordingly: You can see the connected client on the left side of the Manage Clients window in the table. Here, you can also see the Id of the client. This Id is used to reference the abas ERP client in the exported data.

EXAMPLE

EDITING AND DELETING CLIENTS

To edit the configuration of an abas ERP client, select the relevant client in the table on the right. Click the Edit button. Note that the client configuration can only be saved if the relevant client can be accessed via abas REST API and has the SQLConnectorExtensionPack ESDK package installed.

To remove the configuration of an abas ERP client from abas SQL Connector, click the Delete button. A message opens asking if the already exported data records of the client which you would like to delete should be kept in the set up applications.

Note that the license status which is recorded for abas SQL Connector in the deleted client will be lost for abas SQL Connector. This also means that the features of abas SQL Connector activated through the license status will no longer be available. This can have significant impact on already existing applications in abas SQL Connector.

Further information on licenses can be found under Licensing of abas SQL Connector (see page 11) and Windows service administration (see page 27).

26 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

5.2 WINDOWS SERVICE ADMINISTRATION abas SQL Connector works with 2 Windows services to manage synchronization from the abas ERP clients. The abas SQL Connector Windows service controls database synchronization from the abas ERP clients. With the abas SQL Connector - Infosystem Windows service, infosystem data from the abas ERP clients are exported to the MS SQL database. SERVICE CONFIGURATION To define basic settings or configure the control of these services, click the following icon in the upper left corner of the user interface:

The Service Administration screen opens.

27 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

You can define and change basic settings for the Windows services on the Settings page tab.

Use the Select Service selection list to define the Windows service which you would like to administrate:

abasSQLConnector: Settings/Control of the abas SQL Connector Windows service abasInfosystemConnector: Settings/Control of the abas SQL Connector - Infosystem Windows service

In the Clean Up section, you can configure how the relevant service should handle log files and execution results:

Logs: Delete log files after: If you activate this checkbox, you can define for how many days the log files will be kept. If you deactivate this checkbox, the log files will not be deleted. Delete SQL log entries older than: If you activate this checkbox, you can define after how many days the entries in the SQL log of the configuration database for the relevant service should be deleted. If you deactivate this checkbox, these logging rows will not be deleted. Statistics: The services perform synchronization which is stored as statistics in the configuration database of abas SQL Connector. If you activate this checkbox, you can define how many days the entries should be kept. If you deactivate the checkbox, the Statistics entries will not be deleted.

In the Logging section, you can set the log behavior of the selected service. To make these changes effective, restart the corresponding service.

Loglevel: Use this selection list to define which log messages should be stored by abas SQL Connector. Debug: All SQL statements as well as HTTP requests executed by abas SQL Connector Storage in the file log Only suitable for error analysis Can generate very large log files Verbose: Transfer of detailed information on synchronization in abas SQL Connector to the SQL log table Only suitable for error analysis Info: Global status messages for the relevant synchronization Error: Errors and warnings Directory: Directory in which the log files are to be stored

Further information on logging in abas SQL Connector can be found under Logging in abas SQL Connector (see page 30).

28 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

SERVICE STATUS AND ADMINISTRATION

On the State & Control page tab, you can view the status of the selected service and administrate the service.

In the Select Service section, you can select which of the Windows services you would like to administrate:

abasSQLConnector: Administration for the abas SQL Connector Windows service abasInfosystemConnector: Administration for the abas SQL Connector - Infosystem Windows service

The State section provides information on the status of the selected service:

Service active since: Date and time of the service start Status: Indicates the current status of the service, e.g. whether it is active or inactive Up Time: Period for which the service is active Active Applications: Number of active applications (further information can be found under Applications (see page 32))

29 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

The License section provides information on the current license status of abas SQL Connector:

Last license check: Date and time of last license determination. The services of abas SQL Connector check the current license status of the connected abas ERP clients at regular intervals. License state: License status of abas SQL Connector: Unlicensed: abas SQL Connector only exports data with export formats defined in exml files (further information can be found under Configuring the field list for database synchronization in an application (see page 35)). Synchronizing infosystems is not possible. Changing the export format is not possible. Primary and foreign key fields are not generated. Partial: Changing the export formats for database synchronization is possible. Synchronizing infosystems is possible. Primary and foreign key fields are not generated. Full: Changing the export formats for database synchronization is possible. Synchronizing infosystems is possible. Primary and foreign key fields are generated during database and infosystem synchronization.

If you started the user interface of abas SQL Connector with administrative rights, you can start, restart or stop the relevant service in the Service Control section.

Further information on the licensing of abas SQL Connector can be found under Licensing of abas SQL Connector (see page 11).

5.3 LOGGING IN ABAS SQL CONNECTOR

Different log entries are created while executing the services and the abas SQL Connector user interface. Part of these log entries is transferred to the configuration database of abas SQL Connector. To also generate useful messages if there are difficulties connecting to the configuration database, the services of abas SQL Connector create additional log files in the selected directory. If serious errors occur in abas SQL Connector, they are additionally transferred to the Windows Event Log. The Windows Event Log is a central collection of log files in a Windows operating system.

Further information on the Windows Event Log can be found under Related links (see page 55).

Further information on setting the log behavior of the abas SQL Connector Windows services can be found under Windows service administration (see page 27).

By default, the user interface writes the log to the AppData folder of the user who operates the user interface of abas SQL Connector. This is a non-visible folder below the Documents folder of the relevant user. You can make this folder visible by entering the command %AppData% in Windows Explorer. The abas folder contains the log files of the abas SQL Connector user interface.

30 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

If you would like to view the log entries of the abas SQL Connector Windows services using the user interface of abas SQL Connector, click the following button:

The Service Log Messages screen opens. SERVICE LOG MESSAGES

31 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

You can view existing log entries using the following filter settings:

Select the Windows service whose log entries you would like to view here. If you select abasSQLConnector , you can filter the log entries by abas ERP clients. If you select abasInfosystemConnector , you can filter the log entries by Infosystem Jobs.

Select the log level whose log entries you would like to view here.

You can have the log entries for a relevant application displayed here. If you select All, the log entries for all applications are displayed.

If you have selected the abasSQLConnector service, you can have the log entries for an abas ERP client displayed. If you select All, the log entries for all abas ERP clients are displayed.

If you have selected the abasInfosystemConnector service, you can have the log entries for an infosystem job displayed. If you select All, the log entries for all infosystem jobs are displayed.

If this checkbox is activated, you can restrict the number of loaded log entries.

Click this button to load the log entries for the selected filter into the user interface.

Click this button to remove the loaded log entries from the user interface.

Clicking the Show button or double-clicking a log entry opens the Log message details window. This window contains further information on the selected log entry.

5.4 APPLICATIONS

If you create an application in abas SQL Connector, a new database with the application name is created on the selected MS SQL server. In abas SQL Connector, you can then define which data from abas ERP are to be exported to this application or database. Furthermore, you can create multiple Infosystem Jobs for these applications, which also transfer your data to the application database.

32 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

CREATING AN APPLICATION

To create an application in abas SQL Connector, click the following icon in the upper left corner of the abas SQL Connector user interface:

The Manage Application window opens in Create mode:

Proceed as follows:

1. Enter the name of the application in the Name field. 2. Click the SQL icon. The SQL Server Connection Settings screen opens: a. Enter the connection to the database server on which the application is to be created. If you activate the Use Management Database connection checkbox, the application database is generated on the same MS SQL server as the one on which the configuration database of abas SQL Connector is located. b. To test the connection, click the Test Settings button. c. To save the connection, click the Apply button. The SQL Server Connection Settings screen closes. 3. To activate the application, activate the Enabled checkbox. 4. Enter a Down Time for the application, if required. 5. Click the Create button. Result: You have created a new application in abas SQL Connector and can now use it to synchronize databases and execution results of infosystems from abas ERP with the corresponding application database. Furthermore, it becomes selectable in the drop-down menu in the header row of the abas SQL Connector user interface.

Note that the connection of an application to a specific database cannot be edited afterward. If database connection properties are changed, this application must be removed using the SQL Connector interface and created again.

Note that an application can only be created if an application with the same name does not yet exist in abas SQL Connector. On the selected database server, no database with the application name can exist either before the creation of an application.

33 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

Further information on creating Down Times can be found under Down Times (see page 51).

EDITING AN APPLICATION To edit an application, choose it from the selection list in the upper left corner of the user interface and click the following icon:

The Manage Application window opens in Edit mode:

You have the following options:

Changing the MS SQL Server user for the database connection Activating or deactivating the application Setting up a Down Time for the application

To make your changes effective, click the Save button. DELETING AN APPLICATION To delete an application, choose it from the selection list in the upper left corner of the user interface and click the following icon:

A message asking if you really want to delete the application including the application database on the selected database server is displayed. If yes, click the OK button.

To delete the application, at least one of the Windows services of abas SQL Connector must be active.

34 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

5.5 DATABASE SYNCHRONIZATION 5.5.1 CONFIGURING THE FIELD LIST FOR DATABASE SYNCHRONIZATION IN AN APPLICATION

To configure the database synchronization of an application, go to the Database Export page tab. CONFIGURING THE FALLBACK FIELD LIST

The fallback field list must be in exml format. You obtain it from products using abas SQL Connector. The fallback field list is mandatory for synchronizing databases in abas SQL Connector.

If you have created a new application and not yet configured database synchronization, you must set up the Fallback Fieldlist first. This field list specifies the initially transferred database format. To select the Fallback Fieldlist, click the following icon:

If your abas SQL Connector is licensed and you would like to define an application without pre-configured database export format, use the default.exml field list from the installation directory of abas SQL Connector. If you have successfully configured a fallback field list for data synchronization in the selected application, you can allocate clients to database synchronization.

Further information on encrypted field list files can be found under Introduction (see page 14).

Note that the abas SQL Connector Windows service requires access to this file at all times. Therefore, the file should not be moved after the setup.

35 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

CREATING A FIELD LIST BACKUP

To create a backup of the field list of an application, click the Backup button in the Fieldlist section of the user interface. Then select a storage location for this field list file and confirm the selection. An xml file with the name of the selected application and a time stamp is created in this folder. IMPORTING A FIELD LIST BACKUP

If you would like to restore the field list of an application, you can only do this with previously created field list backups. To import a field list backup, click the Restore button in the Fieldlist section of the user interface. Then select the xml file with the previously created backup of the field list. EDITING THE FIELD LIST OF AN APPLICATION

To edit the field list of an application, click the Edit button. This is only possible if you have allocated at least one abas ERP client to the application.

Further information about allocating clients to applications can be found under Configuring connected abas ERP clients for database synchronization (see page 36).

Further information on editing the field list of an application can be found under Configuring the field list for database synchronization in an application (see page 35).

5.5.2 CONFIGURING CONNECTED ABAS ERP CLIENTS FOR DATABASE SYNCHRONIZATION

To configure the database synchronization of an application, go to the Database Export page tab. On this page tab, you can connect abas ERP clients to an application, edit or delete this connection. ALLOCATING ABAS ERP CLIENTS TO DATABASE SYNCHRONIZATION

If you have successfully configured a fallback field list for the application, you can connect a configured abas ERP client to this application.

For this, click the following icon in the Attached Clients section:

The Manage Client Mapping window opens:

36 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

To connect an abas ERP client to database synchronization, proceed as follows:

1. Choose the previously configured abas ERP client which you want to allocate to this application from the Attached client selection list. 2. Select the intervals at which the abas ERP client is to be synchronized with the application database in the Export-Timeout field. 3. If synchronization should be activated for this client, activate the Enabled checkbox. 4. Click the Create button. Result: You have connected an abas ERP client to the database synchronization of the selected application. You can now see this allocation in the table in the Attached Clients section of the user interface. The tables or abas databases synchronized by this client are displayed in the Exported Tables section. If the abas SQL Connector Windows service is active, the databases of the abas ERP client are synchronized with the application database immediately. You can see the status of database synchronization in the user interface.

EXAMPLE

37 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

EDITING THE CONNECTION OF THE ABAS ERP CLIENT TO DATABASE SYNCHRONIZATION

To edit the connection of an abas ERP client to the database synchronization of an application, select the relevant client in the Attached Clients section. Click the following icon:

The Manage Client Mapping window opens in Edit mode:

You have the following options:

Activating or deactivating database synchronization for this client using the Enabled checkbox Changing the interval at which the abas ERP client is synchronized with the application database in the Export- Timeout field

REMOVING ABAS ERP CLIENTS FROM DATABASE SYNCHRONIZATION

To remove the allocation of an abas ERP client from the database synchronization of an application, select the relevant client in the Attached Clients section. Click the following icon:

A window opens. You have the following options:

Removing the client allocation including the data which the client exported to the application database > click the Yes button Removing the client allocation while the exported data remain in the application database > Click the No button

5.5.3 EDITING THE FIELD LIST OF AN APPLICATION

To configure the field list for the database synchronizations of an application, go to the Database Export page tab. Select one of the configured clients in the table under Attached Clients. The available databases and their fields of this client are displayed.

To edit the field list for an application, click the Edit button in the Fieldlist section. The Fieldlist window opens.

38 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

This table displays all databases available for export of the selected abas ERP client. If the Exported table checkbox is activated, fields of this database are already being exported.

You can filter the current database list by the database name here.

This table displays all exportable fields of the database selected in the left table. If the Exported table checkbox is activated, the database field has already been exported.

You can filter the current field list of the selected database by a certain field name here.

This table displays the changes made to the field list.

39 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

You can use this button to adjust how the abas SQL Connector makes changes to the database schema. If fields are added to or removed from a specific exported table, the corresponding table will need to be re-created. You can use the reset option to adjust how the re-creation of the table should be performed by the abas SQL Connector:

Hard: This option will re-export all data objects of the corresponding tables from all clients. The corresponding tables will first be emptied in the application database of the abas SQL Connector, before the table schema is adjusted. Afterward, the table will be filled with the data records of the connected clients. Soft: This option will re-export all data objects of the corresponding tables from all clients. Before this synchronization, only the table schema will be adjusted by the abas SQL Connector here. This means the data set of the table is retained and newly added columns will be added iteratively.

ADDING AND DELETING DATABASE FIELDS To add or delete database fields for an exported database, select the relevant database using the table on the left. Then the database field editor displays the already exported fields of this database in the table on the left-hand side:

Here you can filter the table by field names. You can use this selection list to set a filter for skip fields.

To add a field to database synchronization, activate the Exported table checkbox. The row of the field is highlighted in green.

To remove a field from database synchronization, deactivate the Exported table checkbox. The row of the field is highlighted in red.

40 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

To cancel the selection of all fields of the database, click the None button.

To select all fields of the database, click the All button.

To see all fields of the database header, activate the Head checkbox.

To see all fields of the database table, activate the Table checkbox.

If you have changed the field list, the changes are displayed in the Staged Changes section, which allows you to track your changes in multiple databases.

EXAMPLE

To make the changes to the field list effective, click the Commit button. To undo all changes, click the Clear button. If you have edited one or multiple databases using the Fieldlist window, the corresponding tables for all clients connected to the application are reset and updated.

Further information on resetting tables in abas SQL Connector can be found under Administrating synchronized tables of an application (see page 41).

When you add skip fields to the table schema you'll receive a message that this could slow the export. This is because skip fields in abas ERP are not persistent database fields. These skip fields are calculated during operation, for example, upon accessing an object in an abas ERP database screen. These calculations take place during the data export if you add skip fields to the database export.

Furthermore, changes to the values of the skip fields will not be allocated to the data object. For this reason, the SQL Connector does not recognize these changes and also doesn't synchronize them. This means that skip fields in the database export via the abas SQL Connector do not necessarily represent the current data set.

5.5.4 ADMINISTRATING SYNCHRONIZED TABLES OF AN APPLICATION

To synchronize the status of the tables, go to the Database Export page tab. Select an entry in the Attached Clients table.

41 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

You can see the abas database number and group of the synchronized table. The table section belongs to an abas database if the Table Part checkbox is activated.

If data have already been successfully exported for the relevant abas database, you can see the name of the corresponding table in the application database here.

You can see the total number of rows in the corresponding table in the application database.

Information up to which abas ERP database Commit-Point the relevant table has been synchronized. If the value is 0.0.0 , no data have been exported for this table yet or it has been reset. In this case, the entire history for this table is synchronized with the application database again.

Use this button to reset the commit point for the relevant table to the initial value 0.0.0. For this table, all data are exported again from the selected abas ERP client.

Use this button the reset the commit point for the selected client to 0.0.0. This means that every synchronized table is updated for this client.

This button resets all clients of the selected application. The Commit-Point of each table of the application will be reset to 0.0.0 for each client. Furthermore, all tables synchronized in the application will be emptied. You can only perform this operation if the service is stopped or the client synchronization is deactivated.

Use this button to refresh the view.

42 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

You can use this option to influence the loading behavior of the table. If this check box in deactivated, the table will no longer be updated automatically. You can still update the table manually.

CHANGING THE STRUCTURE OF THE FIELD LIST

If you have edited the field list, this affects the exported tables. To ensure that field lists can be reliably changed in running operation, they only become effective when the synchronization of all clients is completed in the relevant application. If this point has been reached, only the tables changed in the application database are updated by resetting the commit point to the value 0.0.0. Manual intervention is not required. ANALYZING ERRORS

If the synchronization of individual tables fails for a client in abas SQL Connector, you can analyze these errors in the abas SQL Connector user interface. If the synchronization of a table fails, it is highlighted in red.

EXAMPLE

43 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

To view the corresponding error messages, click the Show Errors button. Alternative: Double-click the entry. The Failed SQL Exports window opens:

You can see when errors occurred and during which exports. You can also see the processing Commit-Point.

You can see the corresponding error messages.

Use this button to mark all errors as corrected.

Use this button to mark the selected error as corrected.

If errors occur when synchronizing tables, you should reset them after correcting the errors to ensure a complete data set. The error message will be deleted automatically.

If an error occurs while synchronizing a specific table, the appropriate Commit-Point will be requested again by abas ERP. If the synchronization of the table is successful, the error will also be treated as resolved and the corresponding error message will be deleted.

44 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

5.5.5 VIEWING EXPORT STATISTICS

To receive information on the synchronization of the selected abas ERP client, go to the Database Export page tab. Select a client in the Attached Clients table.

You can see the following details in the Client Export Statistics section:

When did synchronization take place in the selected abas ERP client How much data was transferred during the exports Were the exports successful

If you activate the Show last Results checkbox, you can define the number of displayed export results.

If you activate the Show results of last checkbox, you can restrict the result to a number of days.

Use this button to reload the table.

45 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

5.6 INFOSYSTEM SYNCHRONIZATION 5.6.1 SYNCHRONIZING INFOSYSTEMS

To synchronize infosystems, go to the Infosystem page tab in the user interface of abas SQL Connector. Click the following button:

The Infosystem Job Wizard window opens.

46 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

Proceed as follows:

1. Select the abas ERP clients from which you would like to export infosystem execution results in the Available clients section. 2. Click the Load button. The available infosystems are displayed in the Select Infosystem section. 3. Select the infosystem which you want to synchronize. You can use the Filter by selection list to filter the list by search word, identity number, infosystem name and infosystem working directory. 4. Click the Next button. The Configure Inputs window opens. 5. Select the desired input value in the Input Fields section. 6. Enter the input value in the Input column. 7. Test the execution results in the Test Execution section. a. Use the Client selection list of the client in which the infosystem is to be run. b. Enter in seconds how long the test execution can take before the process is canceled in the Query-Timeout (sec.) field. This setting does not affect infosystem synchronization. c. Specify how many rows are to be loaded during the test execution (maximum of 1000 rows) in the Max. Row count field. This setting does not affect infosystem synchronization. 8. Click the Next button. The Job Settings window opens. 9. Enter a name for the infosystem synchronization job in the Job Name field. 10. To activate the synchronization job, activate the Enabled field. 11. Optionally, enter a suffix for the SQL table name in the SQL table name suffix field. 12. Determine the behavior during infosystem synchronization in the Import Settings section. a. Append new data: New execution results are always imported in the SQL table without deleting the old execution results. b. Override existing data: The SQL table is emptied before inserting new execution results. 13. Define the frequency and time of execution for the infosystem synchronization job in the Schedule section. a. Interval: The infosystem is synchronized at regular intervals, e.g. every hour. b. Custom: The infosystem is synchronized at fixed times, e.g. every Wednesday at 16:30:00. 14. Click the Create button. Result: You have configured a new infosystem synchronization job. It is displayed for the relevant application in the Infosystem Jobs table in the Infosystem page tab. If the abas SQL Connector - Infosystem Windows service is active, the infosystem is now synchronized with the application database.

The header fields of the infosystem are set in the same order as they are stored in the table of variables of the infosystem. When creating the first infosystem export, the target tables for the export of the databases may be reset.

47 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

EXAMPLE

48 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

5.6.2 ADMINISTRATING INFOSYSTEM SYNCHRONIZATION

To administrate an available infosystem synchronization job, go to the Infosystem page tab in the user interface of abas SQL Connector. VIEWING THE INFOSYSTEM JOB STATUS AND DETAILS

You can view the status of the infosystem synchronization job for the selected application in the Infosystem Jobs table. You can see the details for the selected infosystem synchronization job in the Infosystem Jobs table in the Job Details table.

You can see the status of the infosystem synchronization job for the selected application including the time of the last and next synchronization.

You can see the infosystem covered by the job here.

You can see name of the corresponding SQL table, the number of the rows contained in it as well as the selected export behavior of the set up job here.

You can see the schedule according to which the selected job is executed here.

You can see a list of clients connected to this synchronization job here. The selected infosystem is run in these clients and synchronized with the SQL table.

You can see here when settings of the infosystem synchronization job were last changed.

49 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

CHANGING THE CONFIGURATION OF AN INFOSYSTEM SYNCHRONIZATION JOB

Select the relevant infosystem synchronization job in the Infosystem Jobs table. Click the following icon at the end of the row:

The Infosystem Job Wizard window opens in Edit mode.

You have the following options:

Adding other clients to the infosystem synchronization job Changing the input field configuration for the synchronization job Editing the schedule of the synchronization job Changing the export behavior of the synchronization job Activating or deactivating the synchronization job To apply the changes to the infosystem synchronization job, click the Update button.

Further information on the configuration of infosystem synchronization can be found in chapter Synchronizing infosystems (see page 46).

DELETING INFOSYSTEM SYNCHRONIZATION JOBS

Select the relevant infosystem synchronization job in the Infosystem Jobs table. Click the following icon at the end of the row:

A message window opens.

You have the following options:

Deleting the infosystem synchronization job including the corresponding SQL table > Yes button Deleting the infosystem synchronization job without the corresponding SQL table > No button

Note that the infosystem synchronization job can only be completely removed if the abas SQL Connector - Infosystem Windows service is active.

50 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

5.6.3 EXPORT STATISTICS

Export statistics provide further information on infosystem synchronization.

Go to the Infosystem page tab. Select an infosystem synchronization job in the Infosystem Jobs table. The Job Statistics section displays information on the selected infosystem synchronization job, e.g. when synchronization took place, how much data was transferred during synchronization and if synchronization was successful.

You can define how many of the last synchronization results are to be displayed in this field.

You can define the number of days of which you would like to have the synchronization results displayed in this field.

Use this button to reload the table.

5.7 DOWN TIMES

Down Times are intervals in which no synchronization takes place. The Down Times affect both Windows services. You can define Down Times for abas ERP clients or applications.

The following example application scenarios are included:

Down Times for an abas ERP client Updates on the ERP server Backups on the ERP server Regular Varreorgs Client copies Other processes preventing smooth data synchronization Down Times for an application ETL processes directly accessing tables in the application database and locking them for a longer period Backups Other processes preventing smooth data synchronization

51 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

DOWN TIMES SETUP

You can set up Down Times for existing or new applications or abas ERP clients.

Start the corresponding Down Time configurator: In the Manage Clients window for applications, in the Manage Clients window > Edit or Create > Advanced Settings section for abas ERP clients

Further information on setting up or editing applications and abas ERP clients can be found under Applications (see page 32) and Connecting abas ERP clients (see page 21).

You set the Down Times in the Down Time section of the respective editors.

EXAMPLE

On 3 January the abas ERP client is not synchronized once for a total of 90 minutes in the relevant applications:

You have the following options for setting up Down Time:

Once from a defined point in time for a defined period > Down Time Schedule Once Regularly: Daily > Down Time Schedule Daily Weekly on a certain day of the week > Down Time Schedule Weekly Monthly on a defined day of the month > Down Time Schedule Monthly

52 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

6 UPGRADING ABAS SQL CONNECTOR VERSION 1

This chapter will show you

the requirements for upgrading from old abas SQL Connector versions how to transfer your field list from abas SQL Connector version 1 to abas SQL Connector version 2 which follow-up work is required

6.1 REQUIREMENTS

ABAS ERP CLIENTS

Information on these requirements can be found under Requirements abas ERP clients (see page 12).

ABAS SQL CONNECTOR

Further information on how to transfer the field list from a certain application in abas SQL Connector version 1 to an application in abas SQL Connector 2 can be found under Transferring the field list from version 1 to version 2 (see page 54).

To prepare the installation of abas SQL Connector version 2 without transfer, proceed as follows:

1. Stop the two services of abas SQL Connector on your Windows machine. 2. Close the user interface of abas SQL Connector. 3. Remove the ConnectorManagement database from MS SQL Server. 4. Remove all application databases of abas SQL Connector from MS SQL Server. 5. Uninstall abas SQL Connector.

The configuration database and application databases which were created by abas SQL Connector in version 1 can no longer be used in version 2. The databases must be removed manually from MS SQL Server.

As the way in which abas SQL Connector communicates with abas ERP has changed, neither the configuration for the abas ERP clients nor the created infosystem synchronization jobs from version 1 can be transferred to version 2. The must be setup again after a successful upgrade.

53 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

6.2 TRANSFERRING THE FIELD LIST FROM VERSION 1 TO VERSION 2

To transfer the field list of one or multiple applications of version 1 to version 2, use version abas SQL Connector 1.4.3, which is available in addition to abas SQL Connector version 2 on the extranet. Using this version, you can export the field list for a certain application in XML format.

Proceed as follows:

1. Install abas SQL Connector version 1.4.3. 2. Select the application whose field list you would like to transfer to abas SQL Connector version 2. 3. Export this field list with a name chosen by you: In the user interface of abas SQL Connector version 1.4.3, go to the Application page tab > Export Fieldlist section. 4. Meet the upgrade requirements. 5. Install abas SQL Connector version 2. 6. Create the desired application using the user interface of abas SQL Connector 2. 7. Define a fallback field list for this application. 8. Perform a restore with the field list which you generated using abas SQL Connector 1.4.3. Result: You have created an application in abas SQL Connector version 2 which processes the same field list as the one you previously defined for the relevant application.

Further information can be found in the following chapters: Requirements (see page 53), Introduction (see page 14), Applications (see page 32) and Configuring the field list for database synchronization in an application (see page 35).

6.3 FOLLOW-UP WORK

After installing abas SQL Connector version 2, you can remove some dependencies of abas SQL Connector 1 from your systems.

Windows server: SQL Server Management Objects Version 11, contained in Microsoft® SQL Server® 2012 SP1 Feature Pack ActiveX interface EDP API (edpapi.dll) ERP server:

A Samba share is no longer required for the exchange between the Windows server and the ERP server. Created cronjobs for the exchange of the data can be deactivated.

54 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

7 APPENDIX

This chapter will show you

where to find additional information

7.1 RELATED LINKS

Keyword Hyperlink

abas-app-installer https://documentation.abas.cloud/en/esdk/#abas-app-installer

abas Cloud Connect https://documentation.abas.cloud/en/cloud-connect/

Database collation https://docs.microsoft.com/de-de/sql/relational-databases/ collations/set-or-change-the-database-collation?view=sql- server-ver15

Setting up abas REST API https://extranet.abas.de/sub_de/abas-business-suite/erp/apis- tools/middleware/

https://www.mahttps://www.microsoft.com/en-us/download/ Elements for SQL Server Management Objects details.aspx?id=35580icrosoft.com/de-de/download/ (versions higher than 2012) details.aspx?id=35580

License type https://extranet.abas.de/sub_de/help/he/html/2.6.10.6.html

https://extranet.abas.de/sub_en/abas-business-suite/erp.php Hardware requirements for abas BI servers

Server roles in MS SQL Server https://docs.microsoft.com/en-us/sql/relational-databases/ security/authentication-access/server-level-roles?view=sql- server-2017ses/security/authentication-access/server-level- roles?view=sql-server-2017

Shrinking a file https://docs.microsoft.com/de-de/sql/relational-databases/ databases/shrink-a-file?view=sql-server-ver15

Recovery mode in the MS SQL server https://docs.microsoft.com/de-de/sql/relational-databases/ backup-restore/recovery-models-sql-server?view=sql-server- ver15

Windows Event Log https://docs.microsoft.com/en-us/windows/desktop/wes/ windows-event-log

55 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

Keyword Hyperlink

Configuring the Windows firewall https://docs.microsoft.com/de-de/sql/sql-server/install/ configure-the-windows-firewall-to-allow-sql-server-access? view=sql-server-ver15

56 of 58 This document is protected by copyright. Reproduction and distribution prohibited. ABAS SQL CONNECTOR

7.2 INDEX

C I Interface Change connection ▪ Closed 10 ▪ MS SQL database 20 ▪ Open 10 ▪ MS SQL user 19 Clients L ▪ Create and connect 22, 27, 31 License type ▪ Edit and delete 26 ▪ BI Professional 11 R Roles 15, 19