Qorus Integration Engine
3.0.4.p7
|
Qorus implemented two network-available system APIs:
Future Qorus API development will be made with the REST API.
The REST API is accessible from the Qorus HTTP server anchored at the path "/api/"
.
The Qorus REST API follows the following REST design principles:
GET
requests never make changes (do not alter state)PUT
requests can change server state and are also idempotentPOST
requests create new objects or configurationDELETE
requests delete existing objects or configurationIn the following sections the REST API is documented by leading URI path component. For REST API details, see Qorus REST API Details.
The following is a representation of the top levels of the URL path tree in the REST API anchored at /api/
:
The Qorus RPC API is exported through the Qorus HTTP server as XML-RPC, JSON-RPC, and YAML-RPC methods, and is optionally callable with third-party messaging systems such as TIBCO Rendezvous if the system.tibrv-api-gateway service is loaded (only possible if you have the appropriate TIBCO Rendezvous licenses and software from TIBCO, inc, and the software is available and configured on your UNIX server).
System service methods can be called from external systems using the appropriate Qorus API entry points (omq.system.service.[servicename].[method]() or omq.user.service.[servicename].[method]()) with XML-RPC, JSON-RPC, or YAML-RPC and from Qorus user code (workflows and user services).
The Qorus Integration Engine RPC API is made up of a set of RPC methods providing access to system internal data such as workflow cache information, loaded service information, workflow execution instance status; it also provides methods for starting and stopping workflows, starting and stopping services, rotating log files, etc. Below the system RPC API methods are presented in various logical groups according to their functionality.