Conception et analyse intégrées CA et CC
Model-Driven SCADA, EMS, PMS, ADMS & SAS
Contrôleurs intelligents et système de gestion
Une plate-forme jumelle numérique unifiéeConception, fonctionnement et automatisation
The ETAP API is a RESTful service that runs inside DataHub. DataHub is ETAP’s gateway for all data exchanges and is used by ETAP and third-party tools alike. ETAP API is the most prominent DataHub addition. While DataHub hosts various services (internal and public), ETAP API is the service mostly used by our customers.
The ETAP API is divided into four major sections: Application, Project Data, Studies, and Scenario. These sections can be all be explored via the Swagger page. The Swagger page enables users to see and interact with the ETAP API without having to write client code. It all works from the browser. The Swagger page allows both for quick experimentation and as a place to see what is offered by the ETAP API.
This section contains calls about the ETAP application. For example, in this section it is possible to retrieve both user name and project name.
This section contains calls to perform studies. For example, one can request that ETAP run a load flow study from the Swagger page.
This section contains calls that return project data. For example, one can request to view all bus elements or get parameters for elements by type.
This section contains calls that allow interacting with the ETAP Scenario Wizard. With ETAP Scenario Wizard one can trigger pre-configured studies remotely and invoke UI updates.
REST is an acronym for Representational State Transfer. It is an architectural style for distributed hypermedia systems and was first presented by Roy Fielding in 2000 in his dissertation.
Representational state transfer (REST) is a software architectural style that defines a set of constraints to be used for creating Web services. Web services that conform to the REST architectural style, called RESTful Web services, provide interoperability between computer systems on the internet. RESTful Web services allow the requesting systems to access and manipulate textual representations of Web resources by using a uniform and predefined set of stateless operations. Other types of Web services, such as SOAP Web services, expose their own arbitrary sets of operations.
Historically ETAP supported SOAP services through WCF WSDL files as the backend. These services are being migrated toward the more interoperable alternative (REST). Therefore, while ETAP currently supports SOAP services, these will be deprecated soon.
ETAP's REST API is organized into sections as summarized by the table below.
Each instance of ETAP exposes a dedicated REST API for public consumption over local http. One machine can run several ETAP instances (one per project)--or--one instance of ETAP can be commissioned on a per-machine basis. The latter is better suited
for a large volume of parallel workloads (e.g., running a large number of studies in parallel).
Callers can call ETAP from any REST-compatible client. Some of the clients we currently work with:
Logiciel d’analyse & d’exploitation de systèmes électriques
Abonnez-vous pour recevoir les nouveautés ETAP
Antigua & Barbuda
Bosnia & Herzegovina
British Indian Ocean Ter
Central African Republic
Congo Democratic Rep
French Southern Ter
Isle of Man
Papua New Guinea
Sao Tome & Principe
Serbia & Montenegro
St Pierre & Miquelon
St Vincent & Grenadines
Trinidad & Tobago
Turks & Caicos Is
United Arab Emirates
United States of America
Vatican City State
Virgin Islands (Brit)
Virgin Islands (USA)
Wallis & Futana Is
© 2022 Operation Technology, Inc. Tous droits réservés.