home > API > |
The API uses a subset of the "Hypertext Transfer Protocol" (HTTP/1.1) and a
"Character Separated Values" (CSV) data format.
|
Token Mechanism |
In order to support optimistic caching strategies on the client, Jedox OLAP uses a token
mechanism to track changes on the server, databases, dimensions, and cubes as follows.
Each of these objects have an associated token. This token is changed whenever the
object is changed. I. e., if the dimension hierarchy is modified the corresponding
dimension token is changed. The cube token is changed, whenever an element from
a used dimension is deleted. The database token is changed whenever the cube or dimension
token of any contained cube or dimension is changed. The server token is changed,
whenever the token of the contained database is changed. The client can deliver the corresponding
token in a request. If there is a mismatch, an error is returned and the client can update
its cache.
For client side cell caching a second cube token called "client cache" token is delivered.
A client has to update all cached cell values of the cube as soon as the token changes.
The behavior of the "client cache" token can be set in a system cube called #_CONFIGURATION_.
A change of the "client cache" token has no impact on the other tokens.
Possible values and meanings of the client cache configuration:
- "N": No client cache. The token changes after each request to force each client to invalidate its cache.
- "Y": Use a client cache. The token changes after a cell insert, update or delete.
- "E": Use a client cache for cubes without enterprise rules. The token changes after a cell insert, update or delete.
The tokens are delivered in HTTP header fields X-PALO-SV (server), X-PALO-DB (database), X-PALO-DIM (dimensions),
X-PALO-CB (cubes) and X-PALO-CC (cube client cache).
See example 1.
For data changing requests a counter is delivered in HTTP header field X-PALO-AC. This counter is the commit number of the related
asynchronous writeback operation. If the operation fails the user's next request is not performed
and this commit number together with the error description is delivered.
|
HTTP requests |
The Jedox OLAP server supports the following requests (examples): |
Server |
|
Database |
|
Dimension |
|
Element |
|
Cube |
|
Cell |
|
Events |
request |
description |
token |
/event/begin |
Requests an exclusive lock. |
server |
/event/end |
Releases an exclusive lock. |
server |
|
Rules |
|
Scripts |
|
Supervision Server |
request |
description |
token |
/svs/info |
Gets information about Supervision Server. |
- |
/svs/restart |
Restarts all SVS processes to reload PHP scripts. |
- |
/svs/edit |
Editing and displaying content of SVS scripts |
- |
|
View |
|
Hold |
|
SAML |
request |
description |
token |
/meta-sp |
Retrives Service Provider Metadata XML |
saml |
|
JWT |
request |
description |
token |
/token_info |
Validates a JWT token |
- |
|
User |
|
Error codes |
If a parameter is missing or wrong the server returns an
error code and a description. The complete liste of error
codes is here. |