Difference between revisions of "Integration"
Jump to navigation
Jump to search
old>Admin |
old>Admin |
||
| Line 1: | Line 1: | ||
The recommended way to communicate with Tempus Serva is through the webservice interface (REST). | 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 | Regardless of you are using the scheduled import services or the webservice interface, all restrictions from the solution models apply. | ||
== Scheduled data imports == | == Scheduled data imports == | ||
The services are actually run in the context of a user, that can have restricted access just as any other user. | |||
=== Database connection / SQL === | === Database connection / SQL === | ||
| Line 20: | Line 21: | ||
== Tempus Serva REST interface == | == Tempus Serva REST interface == | ||
The REST interface is allways running in the context of a user. | |||
=== Finding data === | === Finding data === | ||
Revision as of 00:44, 18 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 are actually run in the context of a user, 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 is allways running in the context of a user.