Overview
Integration With Third-Party Systems
PEDS Third-Party makes integration into all types of existing IT systems simple. Process data may be exchanged easily with external systems including integration with ERP systems such as SAP and Microsoft Dynamics or your locally developed and custom software. This makes it simple to control all kinds of document flow through your organization. In addition, PEDS Third-Party API allows project specific integration by building individual interface modules. PEDS third-party interfaces are available either as a standard PEDS Third-Party feature, a PEDS Third-Party add-on module, or as a project-specific interface function:
Integration Options
PEDS-ThirdPary is an implementation of WCF and Web Services for the extensible use of service oriented features so that any external application or device can easily communicate and exchange transactional data with our Point of Sales and other systems. The integration implementation comes with three options; • WCF Service • Web Service • Share Folder (xml formats)
WCF Service
PEDS WCF-Service is a build of service-oriented application using Windows Communication Foundation (WCF) framework to receive and/or send data as asynchronous messages from and/or to external (third-party) service endpoint. The service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application. An endpoint (any third-party) can be a client of a service that requests data from PEDS WCF-Service endpoint. The messages can be as simple as a single character or word sent as XML, or as complex as a stream of binary data.
Web Service
PEDS Web-Service is an implementation of a web service developed to enable external (any third party) applications to interact with our Point of Sales and other systems over the Web in a platform-neutral, language independent environment to send and response a request to and/or from our service at a given URL by using the HTTP protocol.
Shared Folder Using Xml
A shared folder is a globally accessible folder by external applications where to dump an external transaction based on the standards and formats PEDS Third-Party has defined in an XML file format. This folder is secured and accessible only by services and applications granted upon a defined access rights. Then, PEDS Third-Party Service will automatically pick transactions read from the shared folder and processed for further integration requirements. This approach is highly recommended for systems which are not capable of referencing a .NET library and are not opened for customizations and/or integrations.
Available Resources
• API libraries • API full documentations • Standard Templates • Customization Manuals • Sample .NET Project, C# Client code
Third-Party Integrations
ERP And Accounting Systems
• SAP ERP • Microsoft Dynamics AX • Microsoft Dynamics SL • Microsoft Dynamics NAV • Cargospot, Cargo Management System • MBIO Soft • Sage 300 • Sage Evolution • Sage Accpac ERP • Peachtree Accounting (2007+) • XpertMart
Health Care & Hospitality Systems
• Fiesta PMS • Prime Care HMiS • Brisk HMiS
Online Applications Integration
• A • B • C
Devices And Cards
• Intelligent One Card Solution System • Door Locks • Card Readers • RFID • Fiscal Printers and Cash Registers • Order Printers (KOT and BOT) • Bar Code Printers and Scanners • QR Code Printers and Scanners
Office Applications
• Microsoft Outlook • Microsoft Word • Microsoft Excel • Microsoft Access
• SAP ERP • Microsoft Dynamics AX • Microsoft Dynamics SL• Microsoft Dynamics NAV• Cargospot, Cargo Management System• MBIO Soft• Sage 300• Sage Evolution• Sage Accpac ERP• Sage Accpac ERP• Peachtree Accounting (2007+)• XpertMart
• Fiesta PMS • Prime Care HMiS • Brisk HMiS
• A • B • C
• Intelligent One Card Solution System • Door Locks • Card Readers• RFID• Fiscal Printers and Cash Registers• Order Printers (KOT and BOT)• Bar Code Printers and Scanners• QR Code Printers and Scanners
