HTTP REST Interface AnySenseConnect Version 3
|
|
|
- Elmer McLaughlin
- 10 years ago
- Views:
Transcription
1 Eemsgolaan DW Groningen P.O. Box BK Groningen The Netherlands HTTP REST Interface AnySenseConnect Version 3 T F [email protected] Date 8 March 2012 Author(s) Bram van der Waaij, Erik Langius, Matthijs Vonder, Mente Konsman, Wiltfried Pathuis Number of pages 51 Document number Document version 1.0 All rights reserved. No part of this publication may be reproduced and/or published by print, photoprint, microfilm or any other means without the previous written consent of TNO. In case this report was drafted on instructions, the rights and obligations of contracting parties are subject to either the General Terms and Conditions for commissions to TNO, or the relevant agreement concluded between the contracting parties. Submitting the report for inspection to parties who have a direct interest is permitted TNO
2 2 / 51 Contents 1 Introduction Interface Model Rest protocol Overall conventions HTTP command conventions AnySenseConnect REST Resource model Resource Project Resource ObserverOwner Resource Observer / RootObserver Resource ObserverType Resource MeasurementUnit Resource Measurement Resource ObserverGroup / RootGroup / LogicalGroup Resource ObserverGroupType Example using the REST resource model Formats UUID Timestamp format Mediatypes Timelines REST API Resource projects POST /projects GET /projects GET /projects/<projectid> PUT /projects/<projectid> DEL /projects/<projectid> Resource projects/observerowners POST /projects/<projectid>/observerowners GET /projects/<projectid>/observerowners GET /projects/<projectid>/observerowners/<observerownerid> PUT /projects/<projectid>/observerowners/<observerownerid> DEL /projects/<projectid>/observerowners/<observerownerid> Resource projects/observers POST /projects/<projectid>/rootobservers GET /projects/<projectid>/rootobservers GET /projects/<projectid>/observers/<observerid> PUT /projects/<projectid>/observers/<observerid> DEL /projects/<projectid>/observers/<observerid> Resource projects/types/observertypes POST /projects/<projectid>/types/observertypes GET /projects/<projectid>/types/observertypes GET /projects/<projectid>/types/observertypes/<observertypeid> PUT /projects/<projectid>/types/observertypes/<observertypeid> DEL /projects/<projectid>/types/observertypes/<observertypeid> Resource projects/types/measurementunits... 26
3 3 / POST /projects/<projectid>/types/measurementunits GET /projects/<projectid>/types/measurementunits GET /projects/<projectid>/types/measurementunits/<measurementunitid> PUT /projects/<projectid>/types/measurementunits/<measurementunitid> DEL /projects/<projectid>/types/measurementunits/<measurementunitid> Resource projects/rootgroups POST /projects/<projectid>/rootgroups GET /projects/<projectid>/rootgroups PUT /projects/<projectid>/rootgroups/<rootgroupid> DEL /projects/<projectid>/rootgroups/<rootgroupid> Resource projects/logicalgroups POST /projects/<projectid>/logicalgroups GET /projects/<projectid>/logicalgroups PUT /projects/<projectid>/logicalgroups/<logicalgroupid> DEL /projects/<projectid>/logicalgroups/<logicalgroupid> PUT /projects/<projectid>/logicalgroups/<logicalgroupid>/observergroups/ <observergroupid> DEL /projects/<projectid>/logicalgroups/<logicalgroupid>/observergroups/ <observergroupid> PUT /projects/<projectid>/logicalgroups/<logicalgroupid>/ observers/<observerid> DEL /projects/<projectid>/logicalgroups/<logicalgroupid>/ observers/<observerid> Resource projects/observergroups GET /projects/<projectid>/observergroups/<observergroupid> PUT /projects/<projectid>/observergroups/<observergroupid> Resource projects/types/observergrouptypes POST /projects/<projectid>/types/observergrouptypes GET /projects/<projectid>/types/observergrouptypes GET /projects/<projectid>/types/observergrouptypes /<observergrouptypeid> PUT /projects/<projectid>/types/observergrouptypes/<observergrouptypeid> PUT /projects/<projectid>/types/observergrouptypes/<observergrouptypeid>/ observergrouptypes/<observergrouptypeid> DEL /projects/<projectid>/types/observergrouptypes/<observergrouptypeid>/ observergrouptypes/<observergrouptypeid> PUT /projects/<projectid>/types/observergrouptypes/<observergrouptypeid>/ observertypes/<observertypeid> DEL /projects/<projectid>/types/observergrouptypes/<observergrouptypeid>/ observertypes/<observertypeid> Resource projects/timelines/observers/measurements GET /projects/<projectid>/timelines/core/observers/<observerid>/measurements/ <fromtimestamp>/<totimestamp>/<timezonecontinent>/<timezonecity> GET /projects/<projectid>/timelines/core/observers/<observerid>/measurements/ position/<timeposition>/<timezonecontinent>/<timezonecity> Resource timezones GET /timezones Appendix Timezones... 45
4 4 / 51 1 Introduction AnySenseConnect is a data collection and - distribution platform for large scale sensor infrastructures. This document describes the HTTP REST Interface for AnySenseConnect that can be used as Application Programming Interface (API) to request for data and meta data of observers and groups of observers over the internet. This HTTP REST interface can be used by third party applications to, for example, build apps for mobile devices, websites, control rooms, etc. We use the term observers instead of sensors because this has a broader meaning. Observers can be physical sensors but could also be text messages, pictures, messages from social media etc.
5 5 / 51 2 Interface Model 2.1 Rest protocol AnySenseConnect uses the REST protocol to interface with clients, REST stands for REpresentational State Transfer. One of the possible implementations is the well-known HTTP protocol. The table below shows four HTTP commands which are used in REST. HTTP Protocol POST GET PUT DELETE Data action Create a resource within a given collection Retrieve a resource Update a resource Delete a resource Based on these four commands, AnySenseConnect uses the following convention: Overall conventions - Identification of a group of resources or a single resource goes via the URL - The URL starts with /connect/v3 indicating this is the 3 rd version of the AnySenseConnect REST interface. - Specification of the attributes of resources is in the JSON format. - Resource elements all have a unique ID, using the UUID4 format HTTP command conventions GET Group-resource Returns a list of all resource elements within this group Example: GET /projects returns a list of all projects GET Element-resource Returns all attributes of a specific resource element. Example: GET /projects/12345 returns all attributes of project POST Group-resource Creates a new element from this group and adds it to the group. After that the HTTP call is redirected to the GET element-resource in order to return the uuid of the newly created resource element. Example: POST /projects creates a new project with a new ID (54321) and redirects the call to GET /projects/54321 PUT DEL Element-resource Updates the attributes of this resource element Example: PUT /project/12345 Updates the attributes of this project. Element-resource Removes this element from the group Example: DEL /projects/12345 Removes project 12345
6 6 / 51 PUT DEL Parent-element-resource/Child-element-resource Connects a child resource to a father resource Example: PUT /groups/12345/observer/67890 Connects the observer to the group Parent-element-resource/Child-element-resource Disconnects a child resource to a father resource Example: DEL /groups/12345/observer/67890 Disconnects the observer to the group AnySenseConnect REST Resource model Figure 1 shows the AnySenseConnect resource model belonging to the REST interface resources. The resource model can be divided into three layers, depicted in the three levels of grey. The top layer is about resources for the management. The middle layer is about the actual instances. The lower layer is about the templates, the instances are based upon. Figure 1: The REST resource model Resource Project Description A resource containing information about a project. AnySenseConnect can host several projects. Each project is entirely separated from other projects. Relations with A project can have several observerowners and observers. Note that the other resources are also bound to the project, via all the relations.
7 7 / Resource ObserverOwner Description A resource containing information about an owner of observers. Relations with An observerowner belongs to one project and can have several observers and observergroups Resource Observer / RootObserver Description A resource containing information about an observer. This can be a physical sensor, or virtual sensor, or any other source of measurement data. A special kind of observers are rootobservers 1. These are observers which exist as a single entity (not part of a device). So a temperature sensor is a rootobserver if it is a single temperature sensor. It is not a rootobserver if it is one of several sensors within a device. Note that in case of a cable of observers, the observers are rootobservers because they also can exist as a single entity. The cable can be described using the rootgroup resource. Relations with An observer has several measurements. Belongs to a project and is owned by an observerowner. Can belong to one or more observergroups. Is from a specific observertype Resource ObserverType Description A resource containing information about the type of an observer. The observer is one of many instances of one observertype. For example the type is a temperature observer of which there are four observers. Relations with An observertype can have several instantiations as an observer. Its measures measurementunits. It can belong to several observergrouptypes Resource MeasurementUnit Description A resource containing information about the unit of measurement. For example temperature can be described in Celsius, Fahrenheit, etc. All different measurement units. Relations with A measurement unit can be used by several observertypes. 1 The word Root is chosen because the RootObserver (and the RootGroups) form the root, the starting point of all available observers.
8 8 / Resource Measurement Description A resource containing information about a measurement. Possible measurements are: - Long - Double - Boolean - String - URL Relations with A measurement belongs to one observer Resource ObserverGroup / RootGroup / LogicalGroup Description A resource containing information about a group of observers and /or other observergroups. Observergroups can be used for two different purposes: 1. To model devices containing more than one sensor. For example a weather station contains temperature, air pressure, wind speed and direction sensors. All within the same device = observergroup. 2. To make groupings of observers and other groups which have a meaning for the user. For example all sensors within a certain room, or all temperature sensors in a building, etc. In the REST interface these two different uses are represented by three different subclasses of the ObserverGroup: 1. RootGroup 2 A resource for modeling devices containing several observers 2. LogicalGroup. A resource for modeling user defined groups. 3. A third group exists: groups within a device, the innergroup. For example: within the weather station device (a rootgroup), the windspeed and winddirection are grouped together into windparameters (an innergroup). Innergroups do not have their own resource, because they only exists as a template (ObserverGroupType). Only logical- and rootgroups can be created. The innergroups follow via the template. All groups can be accessed via the oberservergroup resource. 2 The word Root is chosen because the RootGroups (and the RootObservers) form the root, the starting point of all available observers. Containing observers and/or innergroups.
9 9 / 51 Figure 2: Three different kind of observer groups Relations with An observergroup is owned by one observerowner. Contains observers and/or observergroups. Can be based on a template observergrouptype Resource ObserverGroupType Description A resource containing information about the template of an observergroup. ObserverGroups can be used to described devices containing several observers. Those devices can be described using observergrouptypes in order to easily make many instances of these complex structures. Relations with An observergrouptype has several instantiations as an observergroup. It can belong to several observertypes.
10 10 / Example using the REST resource model In Figure 3 an example shows a real life situation how to model an set of observers and make a user defined view on them. Physically the following devices are present: - 1 water height sensor (WH) - 3 geobead sensor devices containing: o 1 Temperature sensor o 1 inclination group_sensor A CF component A CL component - 1 cable connecting the three geobeads. Logically the following groups are present: - A cross section containing references to o The inclination group_sensor of the three geobeads o The water height sensor Figure 3: An example of how to model observers in the REST resource model
11 11 / 51 3 Formats 3.1 UUID4 The REST API is designed as a computer interface, hence all identifications are computer readable, not necessarily human readable. The UUID version 4 uses a scheme relying only on random numbers. This algorithm sets the version number as well as two reserved bits. All other bits are set using a random or pseudorandom data source. Version 4 UUIDs have the form xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx where x is any hexadecimal digit and y is one of 8, 9, A, or B. e.g. f47ac10b-58cc-4372-a567-0e02b2c3d479" [see also Timestamp format Timestamps within AnySenseConnect can be in two formats: 1. A long containing the time in ms since 1970 (unix epoch) 2. A string with the format YYYY-MM-DDTHH:MM:SS.sss in which the milliseconds (.sss) or optional Timestamps are always in UTC unless specified otherwise 3.3 Mediatypes The AnysenseConnect HTTP REST interface can support different mediatypes. The current version supports - application/json Future versions may support: - application/xml - text/csv Mediatypes can also be described using wildcards (*), in that case AnySenseConnect will use the following mappings: - application/* maps on application/json - */* maps on HTML encapsulated application/json Note that when performing AnySenseConnect REST calls from a browser, the requested mediatype can vary. Most browsers can not directly request application/json. 3.4 Timelines An additional AnySenseConnect module can handle more than only the core timeline. The core timeline contains the raw measurements of the observers. Additional timelines offer functionality like: measurement versions, interpolation & aggregation, multiple simulation storage.
12 12 / 51
13 13 / 51 4 REST API This chapter describes all the in AnySenseConnect available resources and the different commands that can be performed on them. The following resource groups are available: /projects /projects/observerowners /projects/observers /projects/types/observertypes /projects/types/measurementunits /projects/rootgroups /projects/logicalgroups /projects/observergroups /projects/types/observergrouptypes /projects/timelines/observersmeasurements /timezones
14 14 / Resource projects POST /projects Syntax: Method: POST Creates a new project <name> is mandatory, must be unique and may not be empty <description> is optional <startdate> is mandatory and may not be empty <enddate> is optional and may not be empty The return is a redirect to the created project Payload (application/json): "name":"<name>", "startdate":"<timestamp utc formatted as long>", "enddate":"<timestamp utc formatted as long>" HTTP Redirect see other (303) to GET /projects/<projectid> HTTP CLIENT_ERROR_CONFLICT (409) when the project <name> already exists HTTP UNSUPPORTED_MEDIA_TYPE (415) when mediatype is not application/json HTTP BAD_REQUEST (400) when the json is not correct GET /projects Syntax: Method: GET Returns a list of all projects containing all attributes Return message (application/json): [ "name":"<name>", "startdate":"<timestamp utc formatted as a string>", "enddate":"<timestamp utc formatted as a string or empty string >" ] HTTP OK (200), appliation/xml, or text/csv
15 15 / GET /projects/<projectid> Syntax: Method: GET Returns info about this specific project Return message (application/json): "name":"<name>", "startdate":"<timestamp utc formatted as a string>", "enddate":"<timestamp utc formatted as a string or empty string >" HTTP OK (200) if <projectid> existed HTTP BAD_REQUEST (400) when the projectid is not correct HTTP NOT_FOUND (404) if <projectid> does not exist or application/xml PUT /projects/<projectid> Syntax: Method: PUT Update this specific project <name> is mandatory, must be unique and may not be empty <description> is optional <startdate> is mandatory and may not be empty <enddate> is optional Payload (application/json): "name":"<name>", "startdate":"<timestamp utc formatted as a long>", "enddate":"<timestamp utc formatted as a long>" HTTP OK (200) if <projectid> existed HTTP BAD_REQUEST (400) when the projectid or json is not correct HTTP CLIENT_ERROR_CONFLICT (409) when the project <name> already exists HTTP NOT_FOUND (404) if <projectid> does not exist HTTP UNSUPPORTED_MEDIA_TYPE (415) when mediatype is not application/json DEL /projects/<projectid> Syntax: Method: DEL Deletes this specific project HTTP OK (200) if <projectid> existed HTTP BAD_REQUEST (400) when the projectid is not correct HTTP NOT_FOUND (404) if <projectid> does not exist
16 16 / Resource projects/observerowners POST /projects/<projectid>/observerowners Syntax: Method: POST Creates a new observerowner in this project <name> is mandatory and must be unique <description> is optional (when missing it is made an empty string) The return is a redirect to the created observerowner Payload (application/json): "name":"<name>", "description":"<description>" HTTP Redirect see other (303) to GET /projects/<projectid>/observerowner/<oberserverownerid> HTTP CLIENT_ERROR_CONFLICT (409) when the observerowner <name> already exists HTTP BAD_REQUEST (400) when the json is not correct GET /projects/<projectid>/observerowners Syntax: Method: GET Returns a list of all observerowners within this project Return message (application/json): [ "name":"<name>", "description":"<description>" ] HTTP OK (200), appliation/xml, or text/csv
17 17 / GET /projects/<projectid>/observerowners/<observerownerid> Syntax: ownerid> Method: GET Returns info about this specific observerowner Return message (application/json): "name":"<name>", "description":"<description>" HTTP OK (200) if <projectid> and <observerownerid> exist HTTP BAD_REQUEST (400) when the <projectid> and/or <observerownerid> is not correct HTTP NOT_FOUND (404) if <projectid> and or <observerownerid> does not exist or application/xml PUT /projects/<projectid>/observerowners/<observerownerid> Syntax: ownerid> Method: PUT Update this specific observerowner <name> may not be empty and must be unique <description> is optional Payload (application/json): "name":"<name>", "description":"<description>" HTTP OK (200) if <projectid> and <observerownerid> exist HTTP BAD_REQUEST (400) when the <projectid> and/or <observerownerid> is not correct HTTP CLIENT_ERROR_CONFLICT (409) when the observerowner <name> already exists HTTP NOT_FOUND (404) if <projectid> and or <observerownerid> does not exist or application/xml
18 18 / DEL /projects/<projectid>/observerowners/<observerownerid> Syntax: ownerid> Method: DEL Deletes this specific observerowner. An observerowner can only be deleted if there are no other reference to this observerowner. HTTP OK (200) if <projectid> and <observerownerid> exists and there are no references to this observerownerid HTTP CLIENT_ERROR_EXPECTATION_FAILED (417) if there are still references to this observerownerid. HTTP BAD_REQUEST (400) when the <projectid> or <observerownerid> is not correct HTTP NOT_FOUND (404) if <projectid> or <observerownerid> does not exist
19 19 / Resource projects/observers POST /projects/<projectid>/rootobservers Syntax: Method: POST Create a new rootable observer in this specific project based on an existing observertype Description, displayname and location are optional, the other elements are mandatory <idusedbyowner> may not be empty and must be unique <displayname> is default the same as idusedbyowner <observertypeuuid> must be a valid UUID, must exist and must be rootable <observerowneruuid> must be a valid UUID and must exist The return is a redirect to the created observer Payload (application/json): "idusedbyowner":"<idusedbyowner>", displayname, <displayname>, "location":"<location>", timezone : <timezone>, "observertypeuuid":"<observertypeuuid>", "observerowneruuid":"<observerowneruuid>" HTTP Redirect see other (303) to GET /projects/<projectid>/observers/<observerid> HTTP BAD_REQUEST (400) when the projectid or json is not correct HTTP NOT_FOUND (404) if the provided <projectid> or <observertypeuuid> does not exist HTTP CLIENT_ERROR_CONFLICT (409) when the <idusedbyowner> already exists HTTP CLIENT_ERROR_CONFLICT (409) when the observertype <observertypeuuid> is not rootable
20 20 / GET /projects/<projectid>/rootobservers Syntax: Method: GET Returns a list of all available rootable observers Return message (application/json): [ uuid : <uuid>, "idusedbyowner":"<idusedbyowner>", displayname, <displayname>, "location":"<location>", timezone : <timezone>, observerowner : "name":"<name>", "description":"<description>", "observertype": "name":"<name>", "measurementtype":"<measurementtype>", "specification":"<specification>", "rootable":"true", "measurementunit": "quantity":"<quantity>", "unit":"<unit>", "description":"<description>" ] HTTP OK (200) HTTP BAD_REQUEST (400) when the projectid is not correct HTTP NOT_FOUND (404) if <projectid> does not exist, appliation/xml
21 21 / GET /projects/<projectid>/observers/<observerid> Syntax: Method: GET Returns information about this specific observer including information about the observerowner, observertype and measurementunit Return message (application/json): "idusedbyowner":"<idusedbyowner>", displayname, <displayname>, "location":"<location>", timezone : <timezone>, owner : "name":"<name>", "description":"<description>", "observertype": "name":"<name>", "measurementtype":"<measurementtype>", "specification":"<specification>", "rootable":"<rootable>", "measurementunit": "quantity":"<quantity>", "unit":"<unit>", "description":"<description>" HTTP OK (200) if <projectid> and <observerid> existed HTTP BAD_REQUEST (400) when the projectid or observerid is not correct HTTP NOT_FOUND (404) if <projectid> or <observerid> does not exist PUT /projects/<projectid>/observers/<observerid> Syntax: Method: PUT Update this specific observer in this specific project Idusedbyowner is mandatory, the other elements are optional <idusedbyowner> may not be empty and must be unique observertypeuuid and observerowneruuid may not be updated Payload (application/json): "idusedbyowner":"<idusedbyowner>", displayname, <displayname>, "location":"<location>", timezone : <timezone>, HTTP OK (200) if <projectid> and <observerid> existed HTTP BAD_REQUEST (400) when the projectid or observerid is not correct HTTP CLIENT_ERROR_CONFLICT (409) when the <isusedbyowner> already exists HTTP NOT_FOUND (404) if <projectid> or <observerid> does not exist
22 22 / DEL /projects/<projectid>/observers/<observerid> Syntax: Method: DEL Deletes this specific observer from this specific project HTTP OK (200) if <projectid> and <observerid> existed HTTP BAD_REQUEST (400) when the projectid or observerid is not correct HTTP NOT_FOUND (404) if <projectid> or <observerid> does not exist
23 23 / Resource projects/types/observertypes POST /projects/<projectid>/types/observertypes Syntax: Method: POST Create a new observertype in this specific project description and specification are optional, the other elements are mandatory <name> may not be empty and must be unique <measurementtype> is an enumeration of <double, long, string, boolean, url> <rootable> is a boolean value (true/false) <measurementunituuid> must be a valid UUID and must exist The return is a redirect to the created observer Payload (application/json): "name":"<name>", "measurementtype":"<measurementtype>", "specification":"<specification>", "rootable":"<rootable>", "measurementunituuid":"<measurementunituuid>", HTTP Redirect see other (303) to GET /projects/<projectid>/types/observertypes/<observertypeid> HTTP BAD_REQUEST (400) when the projectid or json is not correct HTTP NOT_FOUND (404) if the provided <projectid> or <measurementunituuid> does not exist HTTP CLIENT_ERROR_CONFLICT (409) when the <name> already exists GET /projects/<projectid>/types/observertypes Syntax: Method: GET Returns a list of all available observertypes Return message (application/json): [ "name":"<name>", "measurementtype";"<measurementtype>", "specification":"<specification>", "rootable":"<rootable>", measurementunit : "quantity":"<quantity>", "unit":"<unit>", "description":"<description>" ] HTTP OK (200) HTTP BAD_REQUEST (400) when the projectid is not correct HTTP NOT_FOUND (404) if <projectid> does not exist, appliation/xml
24 24 / GET /projects/<projectid>/types/observertypes/<observertypeid> Syntax: types/observertypes/<observertypeid> Method: GET Returns info about this observertype in this specific project Return message (application/json): "name":"<name>", "measurementtype";"<measurementtype>", "specification":"<specification>", "rootable":"<rootable>", measurementunit : "quantity":"<quantity>", "unit":"<unit>", "description":"<description>" HTTP OK (200) if <projectid> existed HTTP BAD_REQUEST (400) when the projectid and/or observertypeid is not correct HTTP NOT_FOUND (404) if <projectid> and/or observertypeid does not exist or application/xml PUT /projects/<projectid>/types/observertypes/<observertypeid> Syntax: types/observertypes/<observertypeid> Method: PUT Update this specific observertype in this specific project description and specification are optional, the other elements are mandatory <name> may not be empty and must be unique measurementunituuid may not be updated Payload (application/json): "name":"<name>", "measurementtype";"<measurementtype>", "specification":"<specification>", "rootable":"<rootable>" HTTP OK (200) if <projectid> and <observertypeid> existed HTTP BAD_REQUEST (400) when the projectid or observertypeid is not correct HTTP NOT_FOUND (404) if <projectid> or <observertypeid> does not exist HTTP CLIENT_ERROR_CONFLICT (409) when the <name> already exists
25 25 / DEL /projects/<projectid>/types/observertypes/<observertypeid> Syntax: types/observertypes/<observertypeid> Method: DEL Deletes this specific observertype from this specific project HTTP OK (200) if <projectid> and <observertypeid> existed HTTP BAD_REQUEST (400) when the projectid or observertypeid is not correct HTTP NOT_FOUND (404) if <projectid> or <observertypeid> does not exist
26 26 / Resource projects/types/measurementunits POST /projects/<projectid>/types/measurementunits Syntax: Method: POST Create a new measurementunit in this specific project description is optional, the other elements are mandatory <quantity> may not be empty <unit> may not be empty The return is a redirect to the created observer Payload (application/json): "quantity":"<quantity>", "unit":"<unit>", "description":"<description>" HTTP Redirect see other (303) to GET /projects/<projectid>/types/measurementunits/ <measurementunitid> HTTP BAD_REQUEST (400) when the projectid or json is not correct HTTP NOT_FOUND (404) if the provided <projectid> does not exist GET /projects/<projectid>/types/measurementunits Syntax: Method: GET Returns a list of all available measurementunits Return message (application/json): [ "quantity":"<quantity>", "unit":"<unit>", "description":"<description>" ] HTTP OK (200) HTTP BAD_REQUEST (400) when the projectid is not correct HTTP NOT_FOUND (404) if <projectid> does not exist, appliation/xml
27 27 / GET /projects/<projectid>/types/measurementunits/<measurementunitid> Syntax: types/measurementunits/<measurementunitid> Method: GET Returns info about this measurementunit in this specific project Return message (application/json): "quantity":"<quantity>", "unit":"<unit>", "description":"<description>" HTTP OK (200) if <projectid> existed HTTP BAD_REQUEST (400) when the projectid and/or measurementunitid is not correct HTTP NOT_FOUND (404) if <projectid> and/or measurementunitid does not exist or application/xml PUT /projects/<projectid>/types/measurementunits/<measurementunitid> Syntax: types/measurementunits/<measurementunitid> Method: PUT Update this specific measurementunit in this specific project description is optional, the other elements are mandatory <quantity> may not be empty <unit> may not be empty Payload (application/json): "quantity":"<quantity>", "unit":"<unit>", "description":"<description>" HTTP OK (200) if <projectid> and <measurementunitid> existed HTTP BAD_REQUEST (400) when the projectid or measurementunitid is not correct HTTP NOT_FOUND (404) if <projectid> or <measurementunitid> does not exist DEL /projects/<projectid>/types/measurementunits/<measurementunitid> Syntax: types/measurementunits/<measurementunitid> Method: DEL Deletes this specific measurementunit from this specific project HTTP OK (200) if <projectid> and <measurementunitid> existed HTTP BAD_REQUEST (400) when the projectid or measurementunitid is not correct HTTP NOT_FOUND (404) if <projectid> or <measurementunitid> does not exist
28 28 / Resource projects/rootgroups POST /projects/<projectid>/rootgroups Syntax: Method: POST Create a new root group in this specific project Idusedbyowner is mandatory and may not be empty observerowneruuid and rootgrouptypeuuid are mandatory <rootgrouptypeuuid> will be used the create all specified observers and groups Description, displayname and location are optional The default value voor displayname is idusedbywoner the return is a redirect to the created rootgroup payload (application/json): idusedbyowner : <idusedbyowner>, "displayname":"<displayname>", "location":"<location>", observerowneruuid : <observerownerid>, "rootgrouptypeuuid":"<rootgrouptypeuuid>" HTTP Redirect see other (303) to GET /projects/<projectid>/observergroups/<rootgroupid> HTTP BAD_REQUEST (400) when the projectid or json is not correct HTTP NOT_FOUND (404) if <projectid> or <rootgrouptypeuuid> or <observerowneruuid> does not exist HTTP BAD_REQUEST (400) when the <rootgrouptypeuuid> is not rooatble
29 29 / GET /projects/<projectid>/rootgroups Syntax: Method: GET Returns a list of all available rootgroups for this specific project Return message (application/json): [ isusedbyowner : <idusedbyowner>, "displayname":"<displayname>", "location":"<location>", observerowner : "name":"<name>", "description":"<description>", "rootgrouptype": uuid : <uuid>, name : <name>, rootable : <rootable> ] HTTP OK (200) HTTP BAD_REQUEST (400) when the projectid is not correct HTTP NOT_FOUND (404) if <projectid> does not exist PUT /projects/<projectid>/rootgroups/<rootgroupid> Syntax: Method: PUT Update this specific root group in this specific project Idusedbyowner is mandatory and may not be empty Description, displayname and location are optional The default value voor displayname is idusedbywoner The observerowneruuid and rootgrouptypeuuid cannot be updates payload (application/json): idusedbyowner : <idusedbyowner>, "displayname":"<displayname>", "location":"<location>" HTTP OK (200) if <projectid> and <rootgroupid> exist HTTP BAD_REQUEST (400) when the <projectid> or <rootgroupid> is not correct HTTP NOT_FOUND (404) if <projectid> or <rootgroupid> does not exist
30 30 / DEL /projects/<projectid>/rootgroups/<rootgroupid> Syntax: Method: DEL Deletes this specific rootgroup from this specific project HTTP OK (200) if <projectid> and <rootgroupid> exist HTTP BAD_REQUEST (400) when the <projectid> or <rootgroupid> is not correct HTTP NOT_FOUND (404) if <projectid> or <rootgroupid> does not exist
31 31 / Resource projects/logicalgroups POST /projects/<projectid>/logicalgroups Syntax: Method: POST Create a new logical group in this specific project Idusedbyowner and observerowneruuid are mandatory Description, displayname and location are optional The default value voor displayname is idusedbywoner The return is a redirect to the created logicalgroup payload (application/json): idusedbyowner : <idusedbyowner>, "displayname":"<displayname>", "location":"<location>", observerowneruuid : <observerownerid> HTTP Redirect see other (303) to GET /projects/<projectid>/observergroups/<logicalgroupid> HTTP BAD_REQUEST (400) when the projectid or json is not correct HTTP NOT_FOUND (404) if <projectid> or <observerowneruuid> does not exist GET /projects/<projectid>/logicalgroups Syntax: Method: GET Returns a list of all available logicalgroups for this specific project Return message (application/json): [ "displayname":"<displayname>", "location":"<location>", idusedbyowner : <idusedbyowner>, observerowner : "name":"<name>", "description":"<description>" ] HTTP OK (200) HTTP BAD_REQUEST (400) when the projectid is not correct HTTP NOT_FOUND (404) if <projectid> does not exist
32 32 / PUT /projects/<projectid>/logicalgroups/<logicalgroupid> Syntax: <logicalgroupid> Method: PUT Update this specific logical group in this specific project Idusedbyowner is mandatory and may not be empty Description, displayname and location are optional The default value voor displayname is idusedbywoner The observerowneruuid cannot be updates payload (application/json): idusedbyowner : <idusedbyowner>, "displayname":"<displayname>", "location":"<location>" HTTP OK (200) if <projectid> and <logicalgroupid> existed HTTP BAD_REQUEST (400) when the <projectid> or <logicalgroupid> is not correct HTTP NOT_FOUND (404) if <projectid> or <logicalgroupid> does not exist DEL /projects/<projectid>/logicalgroups/<logicalgroupid> Syntax: oupid> Method: DEL Deletes this specific logicalgroup from this specific project HTTP OK (200) if <projectid> and <logicalgroupid> existed HTTP BAD_REQUEST (400) when the <projectid> or <logicalgroupid> is not correct HTTP NOT_FOUND (404) if <projectid> or <logicalgroupid> does not exist
33 33 / PUT /projects/<projectid>/logicalgroups/<logicalgroupid>/observergroups/ <observergroupid> Syntax: logicalgroups/<logicalgroupid>/observergroups/<observergroupid> Method: PUT Add a new child observergroup (observergroupid) to this logicalgroup <locationwithingroup> is optional payload (application/json): "locationwithingroup":"<locationwithingroup>" HTTP OK (200) if <projectid> and <logicalgroupid> and <observergroupid> exist HTTP NOT_FOUND (404) if <projectid> or <logicalgroupid> or <observergroupid> not exist DEL /projects/<projectid>/logicalgroups/<logicalgroupid>/observergroups/ <observergroupid> Syntax: logicalgroups/<logicalgroupid>/observergroups/<observergroupid> Method: DEL Remove this child observergroup (observergroupid) from this logicalgroup HTTP OK (200) if <projectid> and <logicalgroupid> and <observergroupid> exist HTTP NOT_FOUND (404) if <projectid> or <logicalgroupid> or <observergroupid> not exist PUT /projects/<projectid>/logicalgroups/<logicalgroupid>/ observers/<observerid> Syntax: logicalgroups/<logicalgroupid>/observers/<observerid> Method: PUT Add a new child observer (observerid) to this logicalgroup <locationwithingroup> is optional payload (application/json): "locationwithingroup":"<locationwithingroup>" HTTP OK (200) if <projectid> and <logicalgroupid> and <observerid> exist HTTP NOT_FOUND (404) if <projectid> or <logicalgroupid> or <observerid> not exist
34 34 / DEL /projects/<projectid>/logicalgroups/<logicalgroupid>/ observers/<observerid> Syntax: logicalgroups/<logicalgroupid>/observers/<observerid> Method: DEL Remove this child observer (observerid) from this logicalgroup HTTP OK (200) if <projectid> and <logicalgroupid> and <observerid> exist HTTP NOT_FOUND (404) if <projectid> or <logicalgroupid> or <observerid> not exist
35 35 / Resource projects/observergroups GET /projects/<projectid>/observergroups/<observergroupid> Syntax: groupid> Method: GET Returns information about this specific observergroup in this specific project. These can be rootgroups, logicalgroups and/or internalgroups including: - list of all including observers - list of all underlying child observergroups Return message (application/json): idusedbyowner : <idusedbyowner>, "displayname":"<displayname>", "location":"<location>", observerowner : "name":"<name>", "description":"<description>", "rootgrouptype": uuid : <uuid>, name : <name>, rootable : <rootable>, "observers":[ "uuid":"<uuid>" "idusedbyowner":"<idusedbyowner>", displayname, <displayname>, "location":"<location>", timezone : <timezone>, observerownerid : <observerownerid>, "observertypeid": <observertypeid>, observeringroup : uuid : <uuid>, observernamewithingroup :, locationwithingroup : <locationwithingroup> logicalocation :, logicallocationdimensions : ], "observergroups": [ <!-- Here This entire json again for all child observergroups--> groupingroup : groupnamewithingroup :, locationwithingroup : <locationwithingroup>, logicalocation :, logicallocationdimensions : ] HTTP OK (200)
36 36 / 51 HTTP BAD_REQUEST (400) when the projectid or observerlgroupid is not correct HTTP NOT_FOUND (404) if <projectid> or <observergroupid> does not exist PUT /projects/<projectid>/observergroups/<observergroupid> Syntax: <observergroupid> Method: PUT Update a specific observergroup in this specific project description and location are optional displayname is mandatory and may not be empty observergrouptypeuuid cannot be updated. payload (application/json): "displayname":"<displayname>", "location":"<location>" HTTP OK (200) if <projectid> and <observergroupid> existed HTTP BAD_REQUEST (400) when the projectid or json is not correct HTTP NOT_FOUND (404) if <projectid> or <observergroupid> not exist
37 37 / Resource projects/types/observergrouptypes POST /projects/<projectid>/types/observergrouptypes Syntax: Method: POST Create a new observergrouptype in this specific project <name> and <rootable> are mandatory description is optional the return is a redirect to the created observergrouptype payload (application/json): "name":"<name>", "rootable":"<rootable>" HTTP Redirect see other (303) to GET /projects/<projectid>/observergrouptype/<observergrouptypeid> HTTP BAD_REQUEST (400) when the projectid or json is not correct HTTP NOT_FOUND (404) if <projectid> does not exist GET /projects/<projectid>/types/observergrouptypes Syntax: Method: GET Returns a list of all available observergrouptypes for this specific project Return message (application/json): [ "name":"<name>", "rootable":"<rootable>" ] HTTP OK (200) HTTP BAD_REQUEST (400) when the projectid is not correct HTTP NOT_FOUND (404) if <projectid> does not exist
38 38 / GET /projects/<projectid>/types/observergrouptypes /<observergrouptypeid> Syntax: types/observergrouptypes/<observergrouptypeid> Method: GET Returns information about this specific observergrouptype in this specific project.these can be rootgroups, logicalgroups and/or internalgroups including: - list of all including observertypes - list of all underlying child observergroups Return message (application/json): "name":"<name>", "rootable":"<rootable>", "observertypes":[ "name":"<name>", "measurementtype";"<measurementtype>", "specification":"<specification>", "rootable":"<rootable>" ], "observergrouptypes": [ "name":"<name>", "rootable":"<rootable>" ] HTTP OK (200) HTTP BAD_REQUEST (400) when the <projectid> or <observergrouptypeid> is not correct HTTP NOT_FOUND (404) if <projectid> or <observergrouptypeid> does not exist PUT /projects/<projectid>/types/observergrouptypes/<observergrouptypeid> Syntax: types/observergrouptypes/<observergrouptypeid> Method: PUT Update a specific observergrouptype in this specific project description is optional name and rootable are mandatory and may not be empty payload (application/json): "name":"<name>", "rootable":"<rootable>" HTTP OK (200) if <projectid> and <observergrouptypeid> existed HTTP BAD_REQUEST (400) when the projectid or json is not correct HTTP NOT_FOUND (404) if <projectid> or <observergrouptypeid> not exist
39 39 / PUT /projects/<projectid>/types/observergrouptypes/<observergrouptypeid>/ observergrouptypes/<observergrouptypeid> Syntax: types/observergrouptypes/<observergrouptypeid>/ observergrouptypes/<observergrouptypeid> Method: PUT Add a new child observergrouptype (observergrouptypeid) to this observergrouptype, <groupnamewithingroup>, <logicallocation> and <logicallocationdimensions> are optional payload (application/json): "groupnamewithingroup":"<groupnamewithingroup>", logicallocation : <logicallocation>, logicallocationdimensions : <logicallocationdimensions>, HTTP OK (200) if <projectid> and <observergrouptypeid> and <observergrouptypeid> exist HTTP NOT_FOUND (404) if <projectid> or <observergrouptypeid> or <observergrouptypeid> not exist DEL /projects/<projectid>/types/observergrouptypes/<observergrouptypeid>/ observergrouptypes/<observergrouptypeid> Syntax: observergrouptypes/<observergrouptypeid>/observergrouptypes/ <observergrouptypeid> Method: DEL Remove this child observergrouptype (observergrouptypeid) from this observergrouptype HTTP OK (200) if <projectid> and <observergrouptypeid> and <observergrouptypeid> exist HTTP NOT_FOUND (404) if <projectid> or <observergrouptypeid> or <observergrouptypeid> not exist
40 40 / PUT /projects/<projectid>/types/observergrouptypes/<observergrouptypeid>/ observertypes/<observertypeid> Syntax: types/observergrouptypes/<observergrouptypeid>/observertypes/<observe rtypeid> Method: PUT Add a new child observertype (observertypeid) to this observergrouptype <groupnamewithingroup>, <logicallocation> and <logicallocationdimensions> are optional payload (application/json): "groupnamewithingroup":"<groupnamewithingroup>", logicallocation : <logicallocation>, logicallocationdimensions : <logicallocationdimensions>, HTTP OK (200) if <projectid> and <observergrouptypeid> and <observertypeid> exist HTTP NOT_FOUND (404) if <projectid> or <observergrouptypeid> or <observertypeid> not exist DEL /projects/<projectid>/types/observergrouptypes/<observergrouptypeid>/ observertypes/<observertypeid> Syntax: types/observergrouptypes/<observergrouptypeid>/observertypes/<observe rtypeid> Method: DEL Remove this child observertype (observertypeid) from this observergrouptype HTTP OK (200) if <projectid> and <observergrouptypeid> and <observertypeid> exist HTTP NOT_FOUND (404) if <projectid> or <observergrouptypeid> or <observertypeid> not exist
41 41 / Resource projects/timelines/observers/measurements GET /projects/<projectid>/timelines/core/observers/<observerid>/measurements/ <fromtimestamp>/<totimestamp>/<timezonecontinent>/<timezonecity> Syntax: observers/<observerid>/measurements/<fromtimestamp>/<totimestamp>?maxcount=<maxcount>&returntimestampformat=<returntimestampformat> or observers/<observerid>/measurements/<fromtimestamp>/<totimestamp>/ <timezonecontinent>/<timezonecity>?maxcount=<maxcount>&returntimestamptype=<returntimestamptype> Method: GET Returns a set of measurements from this project, from this observer, within the core timeline, within the given time range [fromtimestamp.. totimestamp] Optionally a timezone (timezonecontinent>/<timezonecity>) can be specified, resulting in measurements with this timezone if the returntimestampformat is string. If the returntimestampformat is long they will be utc timestamps. If the timezone is specified, a totimestamp MUST also be specified. If all measurements are required, use a very large number (long time into the future). format of <fromtimestamp> and <totimestamp> is - long epoch time in utc - string in YYYY-MM-DDTHH:MM:SS.sss in utc time or in <timezonecontinent>/ <timezonecity> time Parameters: optional maxcount: The maximum number of measurements that must be returned. The absolute maximum is 1000 measurements in one request. To get the next set of measurements, get the measurements with the fromtimestamp the same as the last timestamp in the previous request optional returntimestamptype: The format the measurements timestamps must be returned. options are: - "long" (default) - "string" Return message general: Returned timestamps are formatted with in utc, or in the optionally specified timezone. Returned measurements always have interpolationmethod none. Return message (application/json): "observerid","<observerid>", "timelinename":"core", "timezone":"<timezonecontinent>/<timezonecity>", "timestamptype":"<timestamptype>", "measurementtype":"<measurementtype>", "interpolationmethod":"none", "measurements":[ "timestamp":"<timestamp>", "value":"<value>" ] Example: - Return message (application/json): timelines/core/observers/f47ac10b-58cc-4372-a567-0e02b2c3d479/ measurements/ / /europe/amsterdam?maxcount=100&returntimestamptype=string
42 42 / 51 "observerid","f47ac10b-58cc-4372-a567-0e02b2c3d479", "timelinename":"core", "timezone":"europe/amsterdam", "timestamptype":"string", "measurementtype":"double", "interpolationmethod":"none", "measurements":[ "timestamp":" t02:36: :00", "value":1054.0, "timestamp":" t02:41: :00", "value": ] HTTP OK (200) HTTP BAD_REQUEST (400) when the projectid, observerid, fromtimestamp, totimestamp, timezonecontinent, timezonecity or returntimestamptype is not correct HTTP NOT_FOUND (404) if the projectid, observerid, fromtimestamp, totimestamp, timezonecontinent, timezonecity or returntimestamptype does not exist
43 43 / GET /projects/<projectid>/timelines/core/observers/<observerid>/measurements/ position/<timeposition>/<timezonecontinent>/<timezonecity> Syntax: observers/<observerid>/measurements/position/<timepostion>?returntimestampformat=<returntimestampformat> or observers/<observerid>/measurements/position/<timeposition>/ <timezonecontinent>/<timezonecity>?returntimestamptype=<returntimestamptype> Method: GET Returns the oldest/newest measurement from this project, from this observer,within the core timeline timeposition indicates the desired position in time. Possible values are first or last Optionally a timezone (timezonecontinent>/<timezonecity>) can be specified, resulting in measurements with this timezone if the returntimestampformat is string. If the returntimestampformat is long they will be utc timestamps. Parameters: optional returntimestamptype: The format the measurements timestamps must be returned. options are: - "long" (default) - "string" Return message general: Returned timestamps are formatted with in utc, or in the optionally specified timezone. Returned measurements always have interpolationmethod none. Return message (application/json): "observerid","<observerid>", "timelinename":"core", "timezone":"<timezonecontinent>/<timezonecity>", "timestamptype":"<timestamptype>", "measurementtype":"<measurementtype>", "interpolationmethod":"none", "measurements":[ "timestamp":"<timestamp>", "value":"<value>" ] Example: - Return message (application/json): timelines/core/observers/f47ac10b-58cc-4372-a567-0e02b2c3d479/ measurements/position/first/europe/amsterdam?returntimestamptype=string "observerid","f47ac10b-58cc-4372-a567-0e02b2c3d479", "timelinename":"core", "timezone":"europe/amsterdam", "timestamptype":"string", "measurementtype":"double", "interpolationmethod":"none", "measurements":[ "timestamp":" t02:36: :00", "value": ]
44 44 / 51 HTTP OK (200) HTTP BAD_REQUEST (400) when the projectid, observerid, fromtimestamp, totimestamp, timezonecontinent, timezonecity or returntimestamptype is not correct HTTP NOT_FOUND (404) if the projectid, observerid, fromtimestamp, totimestamp, timezonecontinent, timezonecity or returntimestamptype does not exist 4.11 Resource timezones GET /timezones Syntax: Method: GET Returns a list of all available timezones Return message (application/json): [ "timezone":"<timezone>" ] Return code HTTP OK (200)
45 45 / 51 5 Appendix Timezones Format: timezonecontinent/timezonecity ACT AET Africa/Abidjan Africa/Accra Africa/Addis_Ababa Africa/Algiers Africa/Asmara Africa/Asmera Africa/Bamako Africa/Bangui Africa/Banjul Africa/Bissau Africa/Blantyre Africa/Brazzaville Africa/Bujumbura Africa/Cairo Africa/Casablanca Africa/Ceuta Africa/Conakry Africa/Dakar Africa/Dar_es_Salaam Africa/Djibouti Africa/Douala Africa/El_Aaiun Africa/Freetown Africa/Gaborone Africa/Harare Africa/Johannesburg Africa/Kampala Africa/Khartoum Africa/Kigali Africa/Kinshasa Africa/Lagos Africa/Libreville Africa/Lome Africa/Luanda Africa/Lubumbashi Africa/Lusaka Africa/Malabo Africa/Maputo Africa/Maseru Africa/Mbabane Africa/Mogadishu Africa/Monrovia Africa/Nairobi Africa/Ndjamena Africa/Niamey Africa/Nouakchott Africa/Ouagadougou Africa/Porto-Novo Africa/Sao_Tome Africa/Timbuktu Africa/Tripoli Africa/Tunis Africa/Windhoek AGT America/Adak America/Anchorage America/Anguilla America/Antigua America/Araguaina America/Argentina/Buenos_Aires America/Argentina/Catamarca America/Argentina/ComodRivadavia America/Argentina/Cordoba America/Argentina/Jujuy America/Argentina/La_Rioja America/Argentina/Mendoza America/Argentina/Rio_Gallegos America/Argentina/Salta America/Argentina/San_Juan America/Argentina/San_Luis America/Argentina/Tucuman America/Argentina/Ushuaia America/Aruba America/Asuncion America/Atikokan America/Atka America/Bahia America/Bahia_Banderas America/Barbados America/Belem America/Belize America/Blanc-Sablon America/Boa_Vista America/Bogota America/Boise America/Buenos_Aires America/Cambridge_Bay America/Campo_Grande America/Cancun America/Caracas
46 46 / 51 America/Catamarca America/Cayenne America/Cayman America/Chicago America/Chihuahua America/Coral_Harbour America/Cordoba America/Costa_Rica America/Cuiaba America/Curacao America/Danmarkshavn America/Dawson America/Dawson_Creek America/Denver America/Detroit America/Dominica America/Edmonton America/Eirunepe America/El_Salvador America/Ensenada America/Fort_Wayne America/Fortaleza America/Glace_Bay America/Godthab America/Goose_Bay America/Grand_Turk America/Grenada America/Guadeloupe America/Guatemala America/Guayaquil America/Guyana America/Halifax America/Havana America/Hermosillo America/Indiana/Indianapolis America/Indiana/Knox America/Indiana/Marengo America/Indiana/Petersburg America/Indiana/Tell_City America/Indiana/Vevay America/Indiana/Vincennes America/Indiana/Winamac America/Indianapolis America/Inuvik America/Iqaluit America/Jamaica America/Jujuy America/Juneau America/Kentucky/Louisville America/Kentucky/Monticello America/Knox_IN America/La_Paz America/Lima America/Los_Angeles America/Louisville America/Maceio America/Managua America/Manaus America/Marigot America/Martinique America/Matamoros America/Mazatlan America/Mendoza America/Menominee America/Merida America/Metlakatla America/Mexico_City America/Miquelon America/Moncton America/Monterrey America/Montevideo America/Montreal America/Montserrat America/Nassau America/New_York America/Nipigon America/Nome America/Noronha America/North_Dakota/Beulah America/North_Dakota/Center America/North_Dakota/New_Salem America/Ojinaga America/Panama America/Pangnirtung America/Paramaribo America/Phoenix America/Port_of_Spain America/Port-au-Prince America/Porto_Acre America/Porto_Velho America/Puerto_Rico America/Rainy_River America/Rankin_Inlet America/Recife America/Regina America/Resolute America/Rio_Branco America/Rosario America/Santa_Isabel America/Santarem America/Santiago America/Santo_Domingo
47 47 / 51 America/Sao_Paulo America/Scoresbysund America/Shiprock America/Sitka America/St_Barthelemy America/St_Johns America/St_Kitts America/St_Lucia America/St_Thomas America/St_Vincent America/Swift_Current America/Tegucigalpa America/Thule America/Thunder_Bay America/Tijuana America/Toronto America/Tortola America/Vancouver America/Virgin America/Whitehorse America/Winnipeg America/Yakutat America/Yellowknife Antarctica/Casey Antarctica/Davis Antarctica/DumontDUrville Antarctica/Macquarie Antarctica/Mawson Antarctica/McMurdo Antarctica/Palmer Antarctica/Rothera Antarctica/South_Pole Antarctica/Syowa Antarctica/Vostok Arctic/Longyearbyen ART Asia/Aden Asia/Almaty Asia/Amman Asia/Anadyr Asia/Aqtau Asia/Aqtobe Asia/Ashgabat Asia/Ashkhabad Asia/Baghdad Asia/Bahrain Asia/Baku Asia/Bangkok Asia/Beirut Asia/Bishkek Asia/Brunei Asia/Calcutta Asia/Choibalsan Asia/Chongqing Asia/Chungking Asia/Colombo Asia/Dacca Asia/Damascus Asia/Dhaka Asia/Dili Asia/Dubai Asia/Dushanbe Asia/Gaza Asia/Harbin Asia/Ho_Chi_Minh Asia/Hong_Kong Asia/Hovd Asia/Irkutsk Asia/Istanbul Asia/Jakarta Asia/Jayapura Asia/Jerusalem Asia/Kabul Asia/Kamchatka Asia/Karachi Asia/Kashgar Asia/Kathmandu Asia/Katmandu Asia/Kolkata Asia/Krasnoyarsk Asia/Kuala_Lumpur Asia/Kuching Asia/Kuwait Asia/Macao Asia/Macau Asia/Magadan Asia/Makassar Asia/Manila Asia/Muscat Asia/Nicosia Asia/Novokuznetsk Asia/Novosibirsk Asia/Omsk Asia/Oral Asia/Phnom_Penh Asia/Pontianak Asia/Pyongyang Asia/Qatar Asia/Qyzylorda Asia/Rangoon Asia/Riyadh Asia/Riyadh87
48 48 / 51 Asia/Riyadh88 Asia/Riyadh89 Asia/Saigon Asia/Sakhalin Asia/Samarkand Asia/Seoul Asia/Shanghai Asia/Singapore Asia/Taipei Asia/Tashkent Asia/Tbilisi Asia/Tehran Asia/Tel_Aviv Asia/Thimbu Asia/Thimphu Asia/Tokyo Asia/Ujung_Pandang Asia/Ulaanbaatar Asia/Ulan_Bator Asia/Urumqi Asia/Vientiane Asia/Vladivostok Asia/Yakutsk Asia/Yekaterinburg Asia/Yerevan AST Atlantic/Azores Atlantic/Bermuda Atlantic/Canary Atlantic/Cape_Verde Atlantic/Faeroe Atlantic/Faroe Atlantic/Jan_Mayen Atlantic/Madeira Atlantic/Reykjavik Atlantic/South_Georgia Atlantic/St_Helena Atlantic/Stanley Australia/ACT Australia/Adelaide Australia/Brisbane Australia/Broken_Hill Australia/Canberra Australia/Currie Australia/Darwin Australia/Eucla Australia/Hobart Australia/LHI Australia/Lindeman Australia/Lord_Howe Australia/Melbourne Australia/North Australia/NSW Australia/Perth Australia/Queensland Australia/South Australia/Sydney Australia/Tasmania Australia/Victoria Australia/West Australia/Yancowinna BET Brazil/Acre Brazil/DeNoronha Brazil/East Brazil/West BST Canada/Atlantic Canada/Central Canada/Eastern Canada/East-Saskatchewan Canada/Mountain Canada/Newfoundland Canada/Pacific Canada/Saskatchewan Canada/Yukon CAT CET Chile/Continental Chile/EasterIsland CNT CST CST6CDT CTT Cuba EAT ECT EET Egypt Eire EST EST5EDT Etc/GMT Etc/GMT+0 Etc/GMT+1 Etc/GMT+10 Etc/GMT+11 Etc/GMT+12 Etc/GMT+2 Etc/GMT+3 Etc/GMT+4 Etc/GMT+5
49 49 / 51 Etc/GMT+6 Etc/GMT+7 Etc/GMT+8 Etc/GMT+9 Etc/GMT0 Etc/GMT-0 Etc/GMT-1 Etc/GMT-10 Etc/GMT-11 Etc/GMT-12 Etc/GMT-13 Etc/GMT-14 Etc/GMT-2 Etc/GMT-3 Etc/GMT-4 Etc/GMT-5 Etc/GMT-6 Etc/GMT-7 Etc/GMT-8 Etc/GMT-9 Etc/Greenwich Etc/UCT Etc/Universal Etc/UTC Etc/Zulu Europe/Amsterdam Europe/Andorra Europe/Athens Europe/Belfast Europe/Belgrade Europe/Berlin Europe/Bratislava Europe/Brussels Europe/Bucharest Europe/Budapest Europe/Chisinau Europe/Copenhagen Europe/Dublin Europe/Gibraltar Europe/Guernsey Europe/Helsinki Europe/Isle_of_Man Europe/Istanbul Europe/Jersey Europe/Kaliningrad Europe/Kiev Europe/Lisbon Europe/Ljubljana Europe/London Europe/Luxembourg Europe/Madrid Europe/Malta Europe/Mariehamn Europe/Minsk Europe/Monaco Europe/Moscow Europe/Nicosia Europe/Oslo Europe/Paris Europe/Podgorica Europe/Prague Europe/Riga Europe/Rome Europe/Samara Europe/San_Marino Europe/Sarajevo Europe/Simferopol Europe/Skopje Europe/Sofia Europe/Stockholm Europe/Tallinn Europe/Tirane Europe/Tiraspol Europe/Uzhgorod Europe/Vaduz Europe/Vatican Europe/Vienna Europe/Vilnius Europe/Volgograd Europe/Warsaw Europe/Zagreb Europe/Zaporozhye Europe/Zurich GB GB-Eire GMT GMT0 Greenwich Hongkong HST Iceland IET Indian/Antananarivo Indian/Chagos Indian/Christmas Indian/Cocos Indian/Comoro Indian/Kerguelen Indian/Mahe Indian/Maldives Indian/Mauritius Indian/Mayotte
50 50 / 51 Indian/Reunion Iran Israel IST Jamaica Japan JST Kwajalein Libya MET Mexico/BajaNorte Mexico/BajaSur Mexico/General Mideast/Riyadh87 Mideast/Riyadh88 Mideast/Riyadh89 MIT MST MST7MDT Navajo NET NST NZ NZ-CHAT Pacific/Apia Pacific/Auckland Pacific/Chatham Pacific/Chuuk Pacific/Easter Pacific/Efate Pacific/Enderbury Pacific/Fakaofo Pacific/Fiji Pacific/Funafuti Pacific/Galapagos Pacific/Gambier Pacific/Guadalcanal Pacific/Guam Pacific/Honolulu Pacific/Johnston Pacific/Kiritimati Pacific/Kosrae Pacific/Kwajalein Pacific/Majuro Pacific/Marquesas Pacific/Midway Pacific/Nauru Pacific/Niue Pacific/Norfolk Pacific/Noumea Pacific/Pago_Pago Pacific/Palau Pacific/Pitcairn Pacific/Pohnpei Pacific/Ponape Pacific/Port_Moresby Pacific/Rarotonga Pacific/Saipan Pacific/Samoa Pacific/Tahiti Pacific/Tarawa Pacific/Tongatapu Pacific/Truk Pacific/Wake Pacific/Wallis Pacific/Yap PLT PNT Poland Portugal PRC PRT PST PST8PDT ROK Singapore SST SystemV/AST4 SystemV/AST4ADT SystemV/CST6 SystemV/CST6CDT SystemV/EST5 SystemV/EST5EDT SystemV/HST10 SystemV/MST7 SystemV/MST7MDT SystemV/PST8 SystemV/PST8PDT SystemV/YST9 SystemV/YST9YDT Turkey UCT Universal US/Alaska US/Aleutian US/Arizona US/Central US/Eastern US/East-Indiana US/Hawaii US/Indiana-Starke US/Michigan
51 51 / 51 US/Mountain US/Pacific US/Pacific-New US/Samoa UTC VST WET W-SU Zulu
No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-SPWFCSOM]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
IoT-Ticket.com. Your Ticket to the Internet of Things and beyond. IoT API
IoT-Ticket.com Your Ticket to the Internet of Things and beyond IoT API Contents 1 Introduction... 4 1.1 Overview... 4 1.2 Abbreviations and definitions... 4 1.3 Data Model... 4 1.4 General Information...
Fairsail REST API: Guide for Developers
Fairsail REST API: Guide for Developers Version 1.02 FS-API-REST-PG-201509--R001.02 Fairsail 2015. All rights reserved. This document contains information proprietary to Fairsail and may not be reproduced,
HTTP Data Logging Protocol
HTTP Data Logging Protocol Version 1.5 (introduced with Meteohub 4.9) 1. Mission Statement The mission of this document is to provide a protocol specification that allows to handover weather data logged
Manage Workflows. Workflows and Workflow Actions
On the Workflows tab of the Cisco Finesse administration console, you can create and manage workflows and workflow actions. Workflows and Workflow Actions, page 1 Add Browser Pop Workflow Action, page
VMware vcenter Log Insight Developer's Guide
VMware vcenter Log Insight Developer's Guide vcenter Log Insight 2.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new
BS1000 command and backlog protocol
BS1000 command and backlog protocol V0.3 2013/5/31 1 / 6 BS1000 command and backlog protocol Introduction When the bs1000 is updating a website, measurement data is transferred to the site using a http
Integration SDK (HTTP API)
Integration SDK (HTTP API) 1. General agreements............................................ 3 2. Infrastructure................................................ 3 2.1 Get unique identifier.........................................
Documentation to use the Elia Infeed web services
Documentation to use the Elia Infeed web services Elia Version 1.0 2013-10-03 Printed on 3/10/13 10:22 Page 1 of 20 Table of Contents Chapter 1. Introduction... 4 1.1. Elia Infeed web page... 4 1.2. Elia
Programming Autodesk PLM 360 Using REST. Doug Redmond Software Engineer, Autodesk
Programming Autodesk PLM 360 Using REST Doug Redmond Software Engineer, Autodesk Introduction This class will show you how to write your own client applications for PLM 360. This is not a class on scripting.
Passcreator API Documentation
Passcreator API Documentation Version 1.0 - December 2014 USt-IdNr.: DE290188967 Seite 1 von 9 About this Document 3 Obtaining an API key 3 Authentication 3 Testing 3 Get list of pass-templates 4 Get information
Traitware Authentication Service Integration Document
Traitware Authentication Service Integration Document February 2015 V1.1 Secure and simplify your digital life. Integrating Traitware Authentication This document covers the steps to integrate Traitware
Remote Access API 2.0
VYATTA A BROCADE COMPANY Vyatta System Remote Access API 2.0 REFERENCE GUIDE Vyatta A Brocade Company 130 Holger Way San Jose, CA 95134 www.brocade.com 408 333 8400 COPYRIGHT Copyright 2005 2015 Vyatta,
Specific API Usage Limitations... 6 Daily Limitation... 6 Concurrency Limitation... 6. API Description... 7 Site Data API... 7
Last update: July 2015 SolarEdge API SolarEdge API Contents Last update: July 2015... 1 SolarEdge API... 2 Contents... 2 General... 3 Purpose and scope... 3 Acronyms and abbreviations... 3 Introduction...
Cloud Elements ecommerce Hub Provisioning Guide API Version 2.0 BETA
Cloud Elements ecommerce Hub Provisioning Guide API Version 2.0 BETA Page 1 Introduction The ecommerce Hub provides a uniform API to allow applications to use various endpoints such as Shopify. The following
Online signature API. Terms used in this document. The API in brief. Version 0.20, 2015-04-08
Online signature API Version 0.20, 2015-04-08 Terms used in this document Onnistuu.fi, the website https://www.onnistuu.fi/ Client, online page or other system using the API provided by Onnistuu.fi. End
SPARROW Gateway. Developer Data Vault Payment Type API. Version 2.7 (6293)
SPARROW Gateway Developer Data Vault Payment Type API Version 2.7 (6293) Released July 2015 Table of Contents SPARROW Gateway... 1 Developer Data Vault Payment Type API... 1 Overview... 3 Architecture...
McAfee Cloud Identity Manager
NetSuite Cloud Connector Guide McAfee Cloud Identity Manager version 2.0 or later COPYRIGHT Copyright 2013 McAfee, Inc. All Rights Reserved. No part of this publication may be reproduced, transmitted,
Manual. Netumo NETUMO HELP MANUAL WWW.NETUMO.COM. Copyright Netumo 2014 All Rights Reserved
Manual Netumo NETUMO HELP MANUAL WWW.NETUMO.COM Copyright Netumo 2014 All Rights Reserved Table of Contents 1 Introduction... 0 2 Creating an Account... 0 2.1 Additional services Login... 1 3 Adding a
API Reference Guide. API Version 1. Copyright Platfora 2016
API Reference Guide API Version 1 Copyright Platfora 2016 Last Updated: 10:05 a.m. April 21, 2016 Contents Document Conventions... 5 Contact Platfora Support...6 Copyright Notices... 6 Chapter 1: Using
Infinitel HotSpotWeb User Manual
Infinitel HotSpotWeb User Manual INTRODUCTION... 5 REQUIREMENTS... 6 INSTALLATION... 7 FIRST STEP... 7 MICROSOFT WINDOWS... 7 Uninstall service... 7 OTHER OS... 7 ADVANCED INSTALLATION SETTINGS... 8 Application.properties
Cloud Elements! Marketing Hub Provisioning and Usage Guide!
Cloud Elements Marketing Hub Provisioning and Usage Guide API Version 2.0 Page 1 Introduction The Cloud Elements Marketing Hub is the first API that unifies marketing automation across the industry s leading
Taxi Service Design Description
Taxi Service Design Description Version 2.0 Page 1 Revision History Date Version Description Author 2012-11-06 0.1 Initial Draft DSD staff 2012-11-08 0.2 Added component diagram Leon Dragić 2012-11-08
How To Use Kiteworks On A Microsoft Webmail Account On A Pc Or Macbook Or Ipad (For A Webmail Password) On A Webcomposer (For An Ipad) On An Ipa Or Ipa (For
GETTING STARTED WITH KITEWORKS DEVELOPER GUIDE Version 1.0 Version 1.0 Copyright 2014 Accellion, Inc. All rights reserved. These products, documents, and materials are protected by copyright law and distributed
Intel Rack Scale Architecture Storage Services
Intel Rack Scale Architecture Storage Services API Specification Software v. August 205 Revision 002 Document Number: 332878-002 All information provided here is subject to change without notice. Contact
SyncTool for InterSystems Caché and Ensemble.
SyncTool for InterSystems Caché and Ensemble. Table of contents Introduction...4 Definitions...4 System requirements...4 Installation...5 How to use SyncTool...5 Configuration...5 Example for Group objects
Administration Quick Start
www.novell.com/documentation Administration Quick Start ZENworks 11 Support Pack 3 February 2014 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of
UpCloud API Documentation. API version 1.1.1 Updated Aug 13, 2013
UpCloud API Documentation API version 1.1.1 Updated Aug 13, 2013 INTRODUCTION 4 Version history... 4 ARCHITECTURE OVERVIEW 5 API overview... 5 API versioning... 5 Authentication... 5 Resource identifiers...
REST Webservices API Reference Manual
crm-now/ps REST Webservices API Reference Manual Version 1.5.1.0 crm-now development documents Page 1 Table Of Contents OVERVIEW...4 URL FORMAT...4 THE RESPONSE FORMAT...4 VtigerObject...5 Id Format...5
AXIGEN Mail Server Reporting Service
AXIGEN Mail Server Reporting Service Usage and Configuration The article describes in full details how to properly configure and use the AXIGEN reporting service, as well as the steps for integrating it
Monitoring Software Services registered with science.canarie.ca
Monitoring Software Services registered with.canarie.ca Introduction The software registry at.canarie.ca monitors each of the contributed services via the API defined in Research Service Support for the
cielo24 Documentation
cielo24 Documentation Release 1.4.10 cielo24 November 19, 2015 1 The Basics 3 1.1 Getting Started.............................................. 3 1.2 Sandbox API...............................................
Alarms & Events Plug-In Help. 2015 Kepware, Inc.
2015 Kepware, Inc. 2 Table of Contents Table of Contents 2 Alarms & Events Plug-In 3 Overview 3 OPC AE Plug-In Terminology 3 OPC AE Plug-In Conditions 4 The OPC AE Plug-In from the OPC AE Clients' Perspective
How To Use Query Console
Query Console User Guide 1 MarkLogic 8 February, 2015 Last Revised: 8.0-1, February, 2015 Copyright 2015 MarkLogic Corporation. All rights reserved. Table of Contents Table of Contents Query Console User
vcloud Air Platform Programmer's Guide
vcloud Air Platform Programmer's Guide vcloud Air OnDemand 5.7 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition.
BlackBerry Enterprise Service 10. Secure Work Space for ios and Android Version: 10.1.1. Security Note
BlackBerry Enterprise Service 10 Secure Work Space for ios and Android Version: 10.1.1 Security Note Published: 2013-06-21 SWD-20130621110651069 Contents 1 About this guide...4 2 What is BlackBerry Enterprise
Cite My Data M2M Service Technical Description
Cite My Data M2M Service Technical Description 1 Introduction... 2 2 How Does it Work?... 2 2.1 Integration with the Global DOI System... 2 2.2 Minting DOIs... 2 2.3 DOI Resolution... 3 3 Cite My Data
Wind River. Intelligent Device Platform XT EMS Profile EMS DEVICE MANAGEMENT USER'S GUIDE WIND RIVER 1.0
Wind River Intelligent Device Platform XT EMS Profile WIND RIVER EMS DEVICE MANAGEMENT USER'S GUIDE 1.0 Copyright Notice Copyright 2014 Wind River Systems, Inc. All rights reserved. No part of this publication
Contents. 2 Alfresco API Version 1.0
The Alfresco API Contents The Alfresco API... 3 How does an application do work on behalf of a user?... 4 Registering your application... 4 Authorization... 4 Refreshing an access token...7 Alfresco CMIS
How To Test Your Web Site On Wapt On A Pc Or Mac Or Mac (Or Mac) On A Mac Or Ipad Or Ipa (Or Ipa) On Pc Or Ipam (Or Pc Or Pc) On An Ip
Load testing with WAPT: Quick Start Guide This document describes step by step how to create a simple typical test for a web application, execute it and interpret the results. A brief insight is provided
Easy Manage Helpdesk Guide version 5.4
Easy Manage Helpdesk Guide version 5.4 Restricted Rights Legend COPYRIGHT Copyright 2011 by EZManage B.V. All rights reserved. No part of this publication or software may be reproduced, transmitted, stored
E*TRADE Developer Platform. Developer Guide and API Reference. October 24, 2012 API Version: v0
E*TRADE Developer Platform Developer Guide and API Reference October 24, 2012 API Version: v0 Contents Getting Started... 5 Introduction... 6 Architecture... 6 Authorization... 6 Agreements... 7 Support
Oracle Communications WebRTC Session Controller: Basic Admin. Student Guide
Oracle Communications WebRTC Session Controller: Basic Admin Student Guide Edition 1.0 April 2015 Copyright 2015, Oracle and/or its affiliates. All rights reserved. Disclaimer This document contains proprietary
Connection Broker Managing User Connections to Workstations and Blades, OpenStack Clouds, VDI, and more. Security Review
Connection Broker Managing User Connections to Workstations and Blades, OpenStack Clouds, VDI, and more Security Review Version 8.1 March 31, 2016 Contacting Leostream Leostream Corporation http://www.leostream.com
Notification messages
AXIS P8221 Network I/O Audio Module TECHNICAL NOTE Notification messages How to integrate AXIS P8221 Updated: August 19, 2011 Rev: 1.1 TABLE OF CONTENTS 1 INTRODUCTION 3 1.1 HTTP and TCP 3 1.2 VAPIX 3
Qlik REST Connector Installation and User Guide
Qlik REST Connector Installation and User Guide Qlik REST Connector Version 1.0 Newton, Massachusetts, November 2015 Authored by QlikTech International AB Copyright QlikTech International AB 2015, All
JobScheduler Web Services Executing JobScheduler commands
JobScheduler - Job Execution and Scheduling System JobScheduler Web Services Executing JobScheduler commands Technical Reference March 2015 March 2015 JobScheduler Web Services page: 1 JobScheduler Web
KMx Enterprise: Integration Overview for Member Account Synchronization and Single Signon
KMx Enterprise: Integration Overview for Member Account Synchronization and Single Signon KMx Enterprise includes two api s for integrating user accounts with an external directory of employee or other
Title page. Alcatel-Lucent 5620 SERVICE AWARE MANAGER 13.0 R7
Title page Alcatel-Lucent 5620 SERVICE AWARE MANAGER 13.0 R7 APPLICATION API DEVELOPER GUIDE 3HE-10590-AAAA-TQZZA Issue 1 December 2015 Legal notice Legal notice Alcatel, Lucent, Alcatel-Lucent and the
1. Starting the management of a subscribers list with emill
The sending of newsletters is the basis of an efficient email marketing communication for small to large companies. All emill editions include the necessary tools to automate the management of a subscribers
[MS-SPACSOM]: Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SPACSOM]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
AdRadionet to IBM Bluemix Connectivity Quickstart User Guide
AdRadionet to IBM Bluemix Connectivity Quickstart User Guide Platform: EV-ADRN-WSN-1Z Evaluation Kit, AdRadionet-to-IBM-Bluemix-Connectivity January 20, 2015 Table of Contents Introduction... 3 Things
Application for Splunk Enterprise
Application for Splunk Enterprise User Guide Document Version 1.77 28 October 2015 10004-01 EN Rev. A 2015 ThreatConnect, Inc. ThreatConnect is a registered trademark of ThreatConnect, Inc. UNIX is a registered
Web Services. with Examples. Telemark University College Department of Electrical Engineering, Information Technology and Cybernetics
Telemark University College Department of Electrical Engineering, Information Technology and Cybernetics Hans- Petter Halvorsen, 2014.03.01 Web Services with Examples Faculty of Technology, Postboks 203,
IBM Cloud Manager with OpenStack. REST API Reference, version 4.1
IBM Cloud Manager with OpenStack REST API Reference, version 4.1 IBM Cloud Manager with OpenStack REST API Reference, version 4.1 Note Before using this information and the product it supports, read the
Standaard voor Publicatie Dynamische Parkeerdata Standard for Publishing Dynamic Parking Data
Standaard voor Publicatie Dynamische Parkeerdata Standard for Publishing Dynamic Parking Data 2014-02-09 Document version 1.0 DOCUMENT INFORMATION Title: Customer: Author(s): Werkgroep SPDP Version: 1.0
Connection Broker Managing User Connections to Workstations, Blades, VDI, and more. Security Review
Connection Broker Managing User Connections to Workstations, Blades, VDI, and more Security Review Version 8.1 October 21, 2015 Contacting Leostream Leostream Corporation http://www.leostream.com 465 Waverley
Secure Envelope specification
Secure Envelope specification for Corporate Access File Transfer 2/13/2015 Version 1.0.3 This document defines how a file (e.g. a payment file) which will be sent to the bank is digitally signed by the
Sage Accpac CRM 5.8. Self Service Guide
Sage Accpac CRM 5.8 Self Service Guide Copyright 2005 Sage Technologies Limited, publisher of this work. All rights reserved. No part of this documentation may be copied, photocopied, reproduced, translated,
InternetVista Web scenario documentation
InternetVista Web scenario documentation Version 1.2 1 Contents 1. Change History... 3 2. Introduction to Web Scenario... 4 3. XML scenario description... 5 3.1. General scenario structure... 5 3.2. Steps
Web Services API Developer Guide
Web Services API Developer Guide Contents 2 Contents Web Services API Developer Guide... 3 Quick Start...4 Examples of the Web Service API Implementation... 13 Exporting Warehouse Data... 14 Exporting
TrendWorX32 SQL Query Engine V9.2 Beta III
TrendWorX32 SQL Query Engine V9.2 Beta III Documentation (Preliminary November 2009) OPC Automation at your fingertips 1. Introduction TrendWorX32 Logger logs data to a database. You can use the TrendWorX32
OpenID connect @ Deutsche telekom. Dr. Torsten Lodderstedt, Deutsche Telekom AG
OpenID connect @ Deutsche telekom Dr. Torsten Lodderstedt, Deutsche Telekom AG service ecosystem and Telekom Login Dr. Torsten Lodderstedt / OpenID Workshop @ IIW #18 2014-05-05 2 Open Standards: Our History
Data Mailbox. support.ewon.biz. Reference Guide
Reference Guide RG 005-0-EN / Rev. 1.0 Data Mailbox The Data Mailbox is a Talk2M service that gathers ewon historical data and makes it available for third party applications in an easy way. support.ewon.biz
CORD Monitoring Service
CORD Design Notes CORD Monitoring Service Srikanth Vavilapalli, Ericsson Larry Peterson, Open Networking Lab November 17, 2015 Introduction The XOS Monitoring service provides a generic platform to support
Facebook Twitter YouTube Google Plus Website Email
PHP MySQL COURSE WITH OOP COURSE COVERS: PHP MySQL OBJECT ORIENTED PROGRAMMING WITH PHP SYLLABUS PHP 1. Writing PHP scripts- Writing PHP scripts, learn about PHP code structure, how to write and execute
Internet Technologies. World Wide Web (WWW) Proxy Server Network Address Translator (NAT)
Internet Technologies World Wide Web (WWW) Proxy Server Network Address Translator (NAT) What is WWW? System of interlinked Hypertext documents Text, Images, Videos, and other multimedia documents navigate
Bitcoin Payment Gateway API
Bitcoin Payment Gateway API v0.3 BitPay, Inc. https://bitpay.com 2011-2012 BITPAY, Inc. All Rights Reserved. 1 Table of Contents Introduction Activating API Access Invoice States Creating an Invoice Required
Avaya Inventory Management System
Avaya Inventory Management System June 15, 2015 Jordan Moser Jin Oh Erik Ponder Gokul Natesan Table of Contents 1. Introduction 1 2. Requirements 2-3 3. System Architecture 4 4. Technical Design 5-6 5.
User manual BS1000 LAN base station
1/18 Contents 1.Introduction 2.Package of the LAN Base Station 3.Software installation 4.Installation of the Receiver 5.Sensor operation 6.Software operation Introduction The BS1000 is a receiver station
7 Why Use Perl for CGI?
7 Why Use Perl for CGI? Perl is the de facto standard for CGI programming for a number of reasons, but perhaps the most important are: Socket Support: Perl makes it easy to create programs that interface
UForge 3.4 Release Notes
UForge 3.4 Release Notes This document is for users using and administrating UShareSoft UForge TM Platform v3.4. This document includes the release notes for: UForge TM Factory UForge TM Builder UI UForge
HireDesk API V1.0 Developer s Guide
HireDesk API V1.0 Developer s Guide Revision 1.4 Talent Technology Corporation Page 1 Audience This document is intended for anyone who wants to understand, and use the Hiredesk API. If you just want to
WEB2CS INSTALLATION GUIDE
WEB2CS INSTALLATION GUIDE FOR PARALLELS / POA HTTP://WWW.XANDMAIL.COM XandMail 32, rue de Cambrai 75019 PARIS - FRANCE Tel : +33 (0)1 40 388 700 - http://www.xandmail.com TABLE OF CONTENTS 1. INSTALLING
E-mail Listeners. E-mail Formats. Free Form. Formatted
E-mail Listeners 6 E-mail Formats You use the E-mail Listeners application to receive and process Service Requests and other types of tickets through e-mail in the form of e-mail messages. Using E- mail
Portal Connector Fields and Widgets Technical Documentation
Portal Connector Fields and Widgets Technical Documentation 1 Form Fields 1.1 Content 1.1.1 CRM Form Configuration The CRM Form Configuration manages all the fields on the form and defines how the fields
WESTERNACHER OUTLOOK E-MAIL-MANAGER OPERATING MANUAL
TABLE OF CONTENTS 1 Summary 3 2 Software requirements 3 3 Installing the Outlook E-Mail Manager Client 3 3.1 Requirements 3 3.1.1 Installation for trial customers for cloud-based testing 3 3.1.2 Installing
Ciphermail Gateway PDF Encryption Setup Guide
CIPHERMAIL EMAIL ENCRYPTION Ciphermail Gateway PDF Encryption Setup Guide March 6, 2014, Rev: 5454 Copyright c 2008-2014, ciphermail.com. CONTENTS CONTENTS Contents 1 Introduction 4 2 Portal 4 3 PDF encryption
LANGuardian Integration Guide
LANGuardian Integration Guide October 2014 This document describes how to integrate LANGuardian with 3rd party systems. Author: Morgan Doyle Revision information: 1.0 NetFort Technologies Limited 2014.
Novell ZENworks 10 Configuration Management SP3
AUTHORIZED DOCUMENTATION Software Distribution Reference Novell ZENworks 10 Configuration Management SP3 10.3 November 17, 2011 www.novell.com Legal Notices Novell, Inc., makes no representations or warranties
Data Transfer Management with esync 1.5
ewon Application User Guide AUG 029 / Rev 2.1 Content Data Transfer Management with esync 1.5 This document explains how to configure the esync 1.5 Server and your ewons in order to use the Data Transfer
Sentinel EMS v7.1 Web Services Guide
Sentinel EMS v7.1 Web Services Guide ii Sentinel EMS Web Services Guide Document Revision History Part Number 007-011157-001, Revision E. Software versions 7.1 and later. Revision Action/Change Date A
Table of Contents INTRODUCTION... 2 HOME... 3. Dashboard... 5 Reminders... 8 Announcements... 12 Preferences... 13 Recent Items... 15 REQUESTS...
Table of Contents INTRODUCTION... 2 HOME... 3 Dashboard... 5 Reminders... 8 Announcements... 12 Preferences... 13 Recent Items... 15 REQUESTS... 16 Request List View... 17 Requests based on Filters...
MASTERTAG DEVELOPER GUIDE
MASTERTAG DEVELOPER GUIDE TABLE OF CONTENTS 1 Introduction... 4 1.1 What is the zanox MasterTag?... 4 1.2 What is the zanox page type?... 4 2 Create a MasterTag application in the zanox Application Store...
This Specification is provided for future development work within onem2m only. The Partners accept no liability for any use of this Specification.
This Specification is provided for future development work within onem2m only. The Partners accept no liability for any use of this Specification. The present document has not been subject to any approval
Availability Monitoring using Http Ping
Availability Monitoring using Http Ping With SAP Solution Manager 7.1 Introduction: This document describes how you can set up Http Ping metrics to monitor any URL. This is especially useful if you want
Lecture (02) Networking Model (TCP/IP) Networking Standard (OSI) (I)
Lecture (02) Networking Model (TCP/IP) Networking Standard (OSI) (I) By: Dr. Ahmed ElShafee ١ Dr. Ahmed ElShafee, ACU : Fall 2015, Networks II Agenda Introduction to networking architecture Historical
CARRIOTS TECHNICAL PRESENTATION
CARRIOTS TECHNICAL PRESENTATION Alvaro Everlet, CTO [email protected] @aeverlet Oct 2013 CARRIOTS TECHNICAL PRESENTATION 1. WHAT IS CARRIOTS 2. BUILDING AN IOT PROJECT 3. DEVICES 4. PLATFORM
Architecture and Data Flow Overview. BlackBerry Enterprise Service 10 721-08877-123 Version: 10.2. Quick Reference
Architecture and Data Flow Overview BlackBerry Enterprise Service 10 721-08877-123 Version: Quick Reference Published: 2013-11-28 SWD-20131128130321045 Contents Key components of BlackBerry Enterprise
General principles and architecture of Adlib and Adlib API. Petra Otten Manager Customer Support
General principles and architecture of Adlib and Adlib API Petra Otten Manager Customer Support Adlib Database management program, mainly for libraries, museums and archives 1600 customers in app. 30 countries
RIT Installation Instructions
RIT User Guide Build 1.00 RIT Installation Instructions Table of Contents Introduction... 2 Introduction to Excel VBA (Developer)... 3 API Commands for RIT... 11 RIT API Initialization... 12 Algorithmic
Introduction to Ingeniux Forms Builder. 90 minute Course CMSFB-V6 P.0-20080901
Introduction to Ingeniux Forms Builder 90 minute Course CMSFB-V6 P.0-20080901 Table of Contents COURSE OBJECTIVES... 1 Introducing Ingeniux Forms Builder... 3 Acquiring Ingeniux Forms Builder... 3 Installing
Barracuda Syslog Barracuda Web Site Firewall
Overview There are four types of logs generated by the which can be configured to be sent over the syslog mechanism to a remote server specified by the Barracuda Web Site Firewall administrator. These
Enabling SSL and Client Certificates on the SAP J2EE Engine
Enabling SSL and Client Certificates on the SAP J2EE Engine Angel Dichev RIG, SAP Labs SAP AG 1 Learning Objectives As a result of this session, you will be able to: Understand the different SAP J2EE Engine
User Manual Network connection and Mobics Dashboard (MIS) software for Dryer Controller M720
User Manual Network connection and Mobics Dashboard (MIS) software for Dryer Controller Manual version : v1.00 Networking and MIS Manual Dryer controller Page 1 of 16 Document history Preliminary version
