ECONZ Web Services

From
(Difference between revisions)
Jump to: navigation, search
m (Background)
(Links to EService Soap API's)
 
(6 intermediate revisions by one user not shown)
Line 1: Line 1:
 
{{MainSectionLinks}}
 
{{MainSectionLinks}}
 
==Documentation==
 
==Documentation==
Apart from the Web Service API's that are listed on this page, there is also a downloadable overview document, containing a summary list of the major methods invokable on the service, and the basic data structures passed through these methods.
+
This page documents the externally accessible Web Service APIs provided by Econz Wireless for its cloud based solutions EService and Timecard.  This page is the best place to get the most up to date information on our Web Service APIs.  For convenience there is also a downloadable overview document which contains a summary list of the major methods invokeable on these services and the basic data structures passed through these methods.
 
+
[http://iweb.econz.co.nz/wiki/images/c/cc/EService_%26_Timecard_SOAP_Overview.pdf To download the EService & Timecard SOAP Overview.pdf, click here.]
+
  
 
== Links to EService Soap API's ==
 
== Links to EService Soap API's ==
ECONZ provides the following [http://www.w3.org/2002/ws/ Web Services]:
+
Econz Wireless provides the following [http://www.w3.org/2002/ws/ Web Services]:
 
*[[EService Soap API]].
 
*[[EService Soap API]].
 
*[[timecard Soap API | Timecard Soap API]].
 
*[[timecard Soap API | Timecard Soap API]].
  
== Background ==
+
== Soap Interface Purpose ==
  
From the draft W3C specification: SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment.  It is an XML based communication protocol that consists of three parts:
+
The SOAP interface to EService and '''Time'''card is intended for communicating and responding to requests from a client application.  As such the format is designed with machine readability rather than human readability in mind.
 +
 
 +
The SOAP interface has two major roles:
 +
 
 +
#Receipt and processing of incoming SOAP requests that describe new jobs or tasks to be created and dispatched, or changes to data in EService or Timecard.
 +
#Generation and sending of responses to requests detailing job progress/status information to the originator of the job.
 +
 
 +
== Encoding ==
 +
 
 +
Messages in this document are written to conform to the SOAP specification as registered at http://schemas.xmlsoap.org/soap/envelope.  More specifically, the internal structure of the messages match the WSDL describing the exact message structure used in relation to the EService and '''Time'''card SOAP interfaces.
 +
 
 +
== SOAP Background ==
 +
 
 +
''From the draft W3C specification:''
 +
 
 +
SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment.  It is an XML based communication protocol that consists of three parts:
  
 
*An envelope that defines a framework for describing what is in a message and how to process it;
 
*An envelope that defines a framework for describing what is in a message and how to process it;
Line 46: Line 59:
 
|---- bgcolor=#CCFFFF
 
|---- bgcolor=#CCFFFF
 
|WSDL
 
|WSDL
|[[http://www.w3.org/TR/wsdl|Web Services Description Language]]
+
|[http://www.w3.org/TR/wsdl Web Services Description Language]
 
|}
 
|}
 
== Soap Interface Purpose ==
 
 
The SOAP interface to EService and '''Time'''card is intended for communicating and responding to requests from a client application.  As such the format is designed with machine readability rather than human readability in mind.
 
 
The SOAP interface has two major roles:
 
 
#Receipt and processing of incoming SOAP requests that describe new jobs to be created and dispatched, or changes to data in EService
 
#Generation and sending of responses to requests detailing job progress/status information to the originator of the job.
 
 
== Encoding ==
 
 
 
Messages in this document are written to conform to the SOAP specification as registered at [http://schemas.xmlsoap.org/soap/envelope/].  More specifically, the internal structure of the messages match the WSDL describing the exact message structure used in relation to the EService and '''Time'''card SOAP interfaces.
 

Latest revision as of 23:52, 6 December 2016

Main Page Latest News F.A.Q. EService Timecard Web Services Client Software Downloads

[edit] Documentation

This page documents the externally accessible Web Service APIs provided by Econz Wireless for its cloud based solutions EService and Timecard. This page is the best place to get the most up to date information on our Web Service APIs. For convenience there is also a downloadable overview document which contains a summary list of the major methods invokeable on these services and the basic data structures passed through these methods.

[edit] Links to EService Soap API's

Econz Wireless provides the following Web Services:

[edit] Soap Interface Purpose

The SOAP interface to EService and Timecard is intended for communicating and responding to requests from a client application. As such the format is designed with machine readability rather than human readability in mind.

The SOAP interface has two major roles:

  1. Receipt and processing of incoming SOAP requests that describe new jobs or tasks to be created and dispatched, or changes to data in EService or Timecard.
  2. Generation and sending of responses to requests detailing job progress/status information to the originator of the job.

[edit] Encoding

Messages in this document are written to conform to the SOAP specification as registered at http://schemas.xmlsoap.org/soap/envelope. More specifically, the internal structure of the messages match the WSDL describing the exact message structure used in relation to the EService and Timecard SOAP interfaces.

[edit] SOAP Background

From the draft W3C specification:

SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based communication protocol that consists of three parts:

  • An envelope that defines a framework for describing what is in a message and how to process it;
  • A set of encoding rules for expressing instances of application-defined data types; and
  • A convention for representing remote procedure calls and responses.

Web Services Description Language (WSDL) is a specification defining how to describe Web Services in a common XML grammar. It describes four critical pieces of data:

  • Interface information describing all publicly available functions
  • Data type information for all message requests and message responses
  • Binding information about the transport protocol to be used
  • Address information for locating the specified service

WSDL is platform and language-independent and is used primarily (although not exclusively) to describe SOAP services. Using WSDL, a client can locate a web service and invoke any of its publicly available functions. With WSDL-aware tools (such as .NET), you can automate this process, enabling applications to easily integrate new services with little or no manual code.

[edit] Definitions, Acronyms and Abbreviations

This document uses the following definitions, acronyms and abbreviations.

Acronym Definition
SOAP Simple Object Access Protocol
XML Extended Mark-up Language
WSDL Web Services Description Language
Personal tools
MediaWiki Appliance - Powered by TurnKey Linux