Integration

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

XML integration also handles task splitting and handling. Each file is split into multiple smaller requests, that are logged and handled individually. In that way an error in a single line, will not prevent the complete batch from executing.

Files are split in the following way

• Tasks awaiting execution
• Task that have been executed
  • Tasks with errors
  • Tasks completed

This allows for easy resubmission of problem data ("with errors"), by copying the file back to the preocessing folder ("awaiting execution").

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

Documentation and examples

• Tempus Serva REST interface.pdf
• Netbeans sample project