Difference between revisions of "Integration"
Jump to navigation
Jump to search
old>Admin |
old>Admin |
||
| Line 31: | Line 31: | ||
=== Documentation and examples === | === Documentation and examples === | ||
[http://www.tempusserva.dk/articlebase/Tempus%20Serva%20REST%20interface.pdf Tempus Serva REST interface.pdf] | * [http://www.tempusserva.dk/articlebase/Tempus%20Serva%20REST%20interface.pdf Tempus Serva REST interface.pdf] | ||
* [http://www.tempusserva.dk/articlebase/restExampleFirmabiler.zip Netbeans sample project] | |||
Revision as of 16:22, 20 February 2013
The recommended way to communicate with Tempus Serva is through the webservice interface (REST).
Regardless of you are using the scheduled import services or the webservice interface, all restrictions from the solution models apply.
Scheduled data imports
The services runs in the context of a user (static), that can have restricted access just as any other user.
Database connection / SQL
PLACEHOLDER ARTICLE
Parsing XML data files
PLACEHOLDER ARTICLE
Converting emails to data
PLACEHOLDER ARTICLE
Event driven data exports
PLACEHOLDER ARTICLE
Tempus Serva REST interface
The REST interface runs in the context of a user (dynamic), that can have restricted access just as any other user.
Credentials are provided with each system interaction, and its even possible to use your own credentials for testing.
Service operations
- Finding data
- Reading data
- Creating data
- Updating data