No./Category | Question/Answer | Back To Top |
1 | What is AbaConnect ? | |
GENERAL |
|
No./Category | Question/Answer | Back To Top |
2 | Where can I find information about AbaConnect ? | |
GENERAL |
Information about AbaConnect is also available on the Abacus Homepage (www.abacus.ch) under Downloads - Documentation - AbaConnect (https://downloads.abacus.ch/downloads/abaconnect/dokumentationen) (contains the general documentation for the AbaConnect Interfaces and Batch File/Command Line) and Downloads - Drivers/Tools - AbaConnect (https://downloads.abacus.ch/downloads/abaconnect/webservices) (for developers : contains the AbaConnect WSDL's, documentation, and examples in .NET und Java - available after registration by Email) WebService examples are available in .NET and Java for ADRE, FIBU, DEBI, KRED, LOHN und PROJ. |
No./Category | Question/Answer | Back To Top |
3 | Is there any licence required to use AbaConnect interfaces ? | |
GENERAL |
|
No./Category | Question/Answer | Back To Top |
4 | What licence is necessary to use Dossiers via the AbaConnect interfaces ? | |
GENERAL |
In order to export and import Dossier via the AbaCOnnect in interfaces it is necessary to have :
Note : The best way to check Dossier access and configuration via AbaConnect is to export an interface via Prog 625 AbaConnect in the Abacus-UI, with the specific Abacus User |
No./Category | Question/Answer | Back To Top |
5 | How can Dossiers be exported and imported via AbaConnect ? | |
GENERAL |
EXPORT : When an interface is exported with Dossiers via the Abacus Prog 625 AbaConnect, a ZIP file will be created. The ZIP file contains the exported AbaConnect XML file, with the Dossiers exported in a ZIP-folder called "bindata". The "bindata" folder contains the dossier files, which are referenced with the short file name in the XML-File. When the interface supports a "Dossier"-Element in the structure, the reference field in the interface is generally via the <FileName>-Field. The file name in the interface XML structure is always specified without the path, only the short file name is used to reference the dossier file. Other interfaces that support a single Dossier file without the "Dossier"-Element, will have a designated field in the interface structure, where the Dossier filename is specifed (e.g. <DocumentPicture>, <PortraitPicture>, etc.). Please refer to the interface documentation for specific details of these fields. IMPORT : An import XML-file has the same structure as an export file. The data can either be imported as a ZIP file (in the correct structure), or the XML Import file and Dossier files can be specified separately in the corresponding areas in the Prog 625 Import. In Prog 625 Import, the Dossier files, corresponding to Import XML file, can be added in panel "Binär Daten" on the right-hand side of the selected XML Import file. A ZIP file must contains the import AbaConnect XML file, with the Dossiers specified in a ZIP-folder called "bindata". The dossier files in the "bindata" folder, are referenced in the interface XML structure via the short file name (identical to an exported ZIP file with Dossiers). WEB SERVICES : For the interfaces supporting Dossier transfers, the Dossiers can also be transferred via AbaConnect WebServices. AbaConnect WebServices transfer the data and Dossier files via SOAP using the MTOM Standard. The Dossier files are transferred as attachments. The XML-Element fields used to reference the attachment "Name" in the XML structure via WebService, uses the same concept as transfer via the XML Import and Export file. For further Abaconnect WebService examples using Dossiers, please refer the AbaConnect WebService on the Abacus Homepage. The ATK, DEBI, KRED, and LOHN AbaConnect WebService examples all have implementations of interfaces which demonstrate the use of Dossiers. Note : The following prerequisites are required to transfer Dossiers via AbaConnect interfaces :
|
No./Category | Question/Answer | Back To Top |
6 | What is the difference between AbaConnect ASCII and XML interfaces ? | |
ABACONNECT XML |
|
No./Category | Question/Answer | Back To Top |
7 | What is the difference between AbaConnect Flat and Hierarchy interfaces ? | |
ABACONNECT XML |
|
No./Category | Question/Answer | Back To Top |
8 | Does an AbaConnect Import XML File have to contain all the XML Element fields in the Default Mapping ? | |
ABACONNECT XML |
|
No./Category | Question/Answer | Back To Top |
9 | What is the correct way to edit or save an XML file to retain the encoding in UTF-8 ? | |
ABACONNECT XML |
A simple test to check most XML encoding problems is to open the XML file in the Internet Explorer. Encoding errors will normally be shown with an error message. Make sure to scroll to the end of the XML file in the Internet Browser when looking for errors. If the XML file is written via a program, the program must use the defined encoding to write the XML file. |
No./Category | Question/Answer | Back To Top |
10 | What are special characters and how can they be represented in XML using UTF-8 encoding ? | |
ABACONNECT XML |
Alternatively, special characters can be represented with a decimal code (&#<decimal-nummer>;) that is compatible with UTF-8. For Example :
|
No./Category | Question/Answer | Back To Top |
11 | How can I detect error responses during AbaConnect Command Line exports and imports ? | |
COMMAND LINE |
1. Normal messages that are logged in the AbaConnect response file. 2. Exception messages that interrupt the running process before it can be fully completed. In the 1st case the error messages can be analysed in the repsonse file. The response file has the same format as the response file generated using the Abacus Menu Prog 625. The 2nd case is usually caused by bad command line arguements (e.g. Username and Password are incorrectly defined or AbaConnect interface ID, etc.). This may cause the command line process to end before a reponse file can be written. Hint : It is recommended to always write a response file for AbaConnect command line (with "-responseYES") and after the execution, check if the response file was generated. e.g. rem Delete any existing files before running the AbaConnect command line if NOT EXIST "x:\test_export.xml" del /Q "x:\test_export.xml" if NOT EXIST "x:\test_response.xml" del /Q "x:\test_response.xml" abaconnectexportconsole.exe "/USRAdministrator" "/PWeli" "-M7777" "-aADRE" "-P625" "-datamodeXML" "-version2007.10" "-acidContacts" "-mapidAbaDefault" "-responseYES" "-responsefilex:\test_response.xml" "-exportfilex:\test_export.xml" if NOT EXIST "x:\test_export.xml" echo **** UNSUCCESSFUL : No export file found ! **** if NOT EXIST "x:\test_response.xml" echo **** UNSUCCESSFUL : No response file found ! **** |
No./Category | Question/Answer | Back To Top |
12 | Where can I find the required parameters to export an AbaConnect interface via command line ? | |
COMMAND LINE |
|
No./Category | Question/Answer | Back To Top |
13 | How can I tell if an AbaConnect interface is accessible via WebServices ? | |
WEB SERVICES |
Downloads - AbaConnect WebServices (https://downloads.abacus.ch/downloads/abaconnect/webservices) This page contains the WSDL's for the released AbaConnect WebServices. Many of the XML AbaConnect interfaces are also available as WebService, but if the WSDL for the interface is not listed on the Homepage, then the interface cannot be used via WebServices. |
No./Category | Question/Answer | Back To Top |
14 | How can I test if an Abacus installation supports AbaConnect WebServices ? | |
WEB SERVICES |
http://localhost:40000 - this should display the ULC start page http://localhost:40000/abaconnect/services - this should display a message from AbaConnect (e.g. "Welcome to AbaConnect-Webservices. For more Information see http://www.abacus.ch") The same tests can also be extended to test over a network by replacing "localhost" with the Abacus Server computer name. e.g. http://<Server-Computer-Name>:40000/abaconnect/services If an connection error message (for the URL http://<Server-Computer-Name>:40000/abaconnect/services) is displayed in the Internet Browser e.g. Not found (404) The requested resource can not be found. then the AbaConnect WebServices are not available. Hint : The AbaConnect WebService Examples available on the Abacus Homepage can also be used to test AbaConnect WebService connections. Generally, the JAVA and Microsoft .NET AbaConnect examples include the compiled JAR-file or executable file in the example ZIP file. Provided that JAVA or Microsoft .NET Framework 4.0 is installed on a computer, these example JAR-file or executable files can be unpacked and run without the need to compile the supplied source code. More information about this is contained in the examples. |
No./Category | Question/Answer | Back To Top |
15 | How can Apache TCPMon be configured to view and save the SOAP messages ? | |
WEB SERVICES |
AbaConnect_TCPMon_de.pdf (https://downloads.abacus.ch/fileadmin/ablage/abaconnect/zipfiles/documents/AbaConnect_TCPMon_de.pdf) Note : The Apache TCPMon is no longer actively developed by Apache, but the program and source code is still available from the Apache WebSite Archives As of Abacus V2021 SP 15.03.2022 an extended version of the TCPMon Program is available on the Abacus-Installation in the Abacus Server folder : x:\abac\setup\tcpmon.zip The TCPMon Program can be copied from this location and run with a JAVA command-line where JAVA is available. The Program is usually used on the same computer where the AbaConnect WebService Client program is running The extended version of TCPMon has a few extra features that may be useful for modern connections, such as SSL connections to the server. The use of extended Version is identical to the original version of TCPMon. |
No./Category | Question/Answer | Back To Top |
16 | Can the Abacus AbaEngine WebService be used for exporting data ? | |
WEB SERVICES |
Downloads :
If Abacus is locally installed Further Information about the AbaEngine WebService is available via the URL :
As of Abacus V2016 the AbaEngine SOAP WebService is not activated by default. The following entries are required in the Abacus System configuration files ("\abac\system\abasystem.properties") to activate the AbaEngine SOAP WebService : abaengine.soap.reports = true (true if AbaReports are being used) abaengine.soap.views = true (true if AbaViews are being used) Note : If the "\abac\system\abasystem.properties" does not already exist, it can be created with a standard text editor. As of Abacus V2019, the settings can also be entered in the Abacus Service Manager. Please re-start the Abacus Services after changes to the "\abac\system\abasystem.properties" file. Please Note : AbaView Reports must be saved as WebReports (*.avx) if they are to be used with the AbaEngine SOAP WebService The *.avx must be present in the x:\abac\kd\abav\web folder in order to be read via WebService Abacus V2021: As of Abacus V2021 there is also an AbaReport REST-API available for accessing configured AbaReports via a REST-API WebService. The functionality of the REST-API similar to the AbaEngine (SOAP) WebService. More information is available with the following link : AbaReport REST-API |
No./Category | Question/Answer | Back To Top |
17 | Where is more detailed information about developing with AbaConnect WebService ? | |
WEB SERVICES |
Downloads :
|
No./Category | Question/Answer | Back To Top |
18 | How can User access be limited using AbaConnect.WebService.Users property ? | |
WEB SERVICES |
Login failed for user: Administrator (unknown user or password, user is disabled, or user is not configured for AbaConnect.WebService.Users). is a general error message by Login, and it usually means the user must be configured to have access via AbaConnect WebServices.
Examples : AbaConnect.WebService.Users= No Users have access to AbaConnect WebServices AbaConnect.WebService.Users=user1,user2 The users "user1" and "user2" have access to AbaConnect WebServices When the error message appears by Login, the following check list should be assessed :
|
No./Category | Question/Answer | Back To Top |
19 | What are the main differences between using AbaConnect WebServices and AbaConnect XML file ? | |
WEB SERVICES |
The interface documentation is valid for the AbaConnect XML files and for WebService Each AbaConnect Webservice call contains 1 data record, and each call is processed as 1 transaction. In an AbaConnect XML file the standard and recommended process handling is also 1 data-record per transaction, although some interfaces may allow multiple data elements to be processed in 1 Transaction (e.g. Fibu-Bookings and Project-Bookings). |
No./Category | Question/Answer | Back To Top |
20 | Why can timeouts occur with .NET WebService Programs with Abacus V2019 ? | |
WEB SERVICES |
One of the following methods can be used to deactivate .NET "Expect100Continue" configuration. As of Abacus V2021 SP 15.03.2022 the "Expect100Continue" should be better supported by the Abacus WebServer "AbaWebServer". Source Code - Endpoint configuration : Directly configured o the Endpoint (following example with AbaEngine Service) : AbaEngineWrapperService abaEngineService = new AbaEngineWrapperService(); abaEngineService.Url = connectionUrl; System.Net.ServicePoint servicePoint = System.Net.ServicePointManager.FindServicePoint(abaEngineService.Url, abaEngineService.Proxy); if (servicePoint != null) { servicePoint.Expect100Continue = false; } Source Code - Global Einstellungen - Attention: this can affect other .NET Endpoints created after the .NET configuration has changed. System.Net.ServicePointManager.Expect100Continue = false; // Note : this can also be done directly in the .NET configuration file // with : <system.net> <settings> <servicePointManager expect100Continue="false" /> </settings> </system.net> |