Interface specification

This chapter discusses the specification of the SOAP interface.

Every operation takes a single argument whose type is dependent on the category of the operation and the entity to which the operation applies. For example, all query operations take a query object as input argument. It contains shared attributes that apply to all sorts of queries (e.g., the numRecords and skipRecords attributes) and attributes that are specific to the category of the operation (e.g., the user query object contains a template user). The category to which an operation belongs is derived from the name of the operation.

All operations are transactional. If an operation fails, the changes will not be reflected on the database.

nevisIDM does not evaluate the SOAPAction header. SOAPAction headers in requests are ignored.