QPR ProcessAnalyzer API: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
 
(142 intermediate revisions by 3 users not shown)
Line 1: Line 1:
QPR ProcessAnalzyer Web Service API (Application Programming Interface) can be used to automate operations and to create integration with other applications.
QPR ProcessAnalyzer API can be used to build integrations with other applications and automate operations in the process mining system.


== Functions ==
QPR ProcessAnalyzer API is a JSON based API following the REST design principles. All methods (except the [[Web_API:_Token|token]] and [[Web_API:_Serverinfo|serverinfo]]) require a prior login to establish a session. The session is initialized with the [[Web_API:_Token|token]] call with username and password, and the access token is returned as a response for a successful login. The methods requiring prior authenticated session, need to have a HTTP request header ''Authorization'' with value ''Bearer <access token>'' to identify the session.
The following functions are available in QPR ProcessAnalyzer Web Service API:


* [[QueryObjectProperties (API)|QueryObjectProperties]] returns all the listed properties queried for all the listed objects identified by unique identifiers.
Url for calling the API has the following form (replace the server hostname with a correct one):
* [[ValidateModel (API)|ValidateModel]] can be used to perform all the pending tasks stored in the work queue of the given model.
<pre>
 
https://customer.onqpr.com/qprpa/api/<methodName>
== Object Types and Their Properties ==
</pre>
* Common Properties for Object Types
The following properties are supported by all ProcessAnalyzer object types. These properties are used in the "properties" argument of the [[QueryObjectProperties (API)|QueryObjectProperties]] function:<br/>
: '''typename''': Name of the type of the object.<br/>
: '''name''': Name of the given object.<br/>
: '''properties''': List of all the supported properties for given object.<br/>
: '''relatedcount''': Integer number of how many child nodes there are in the next level of given hierarchy. This is 0 if the element doesn't support the relation or there are no child objects for the given object in given hierarchy. Requires hierarchy-parameter to be defined.
 
=== DataTable ===
The following properties are supported by the DataTable object type:
* '''typename''': "DataTable"
* '''<column identifier>''': A Data Table column name converted to script name and also prefixed with"custom_" when used as an object property name in QueryObjectProperties. For example: when the Data Table column name is "Actual", the column identifier is "custom_actual".
+ all Common Supported Properties
 
=== Product ===
The following properties are supported by the Product object type:
* '''typename''': "product"
* '''name''': Name of the product (QPR ProcessAnalyzer)
* '''version''': Dll version of the Qpr.ProcessAnalyzer.Core.dll
 
Supported Relations:
* '''related''': Returns the related objects. Supported relation hierarchies are:
* '''datatable''': Returns all the projects available for the user.
 
+ all Common Supported Properties
 
=== Project ===
The following properties are supported by the Project object type:
* '''typename''': "Project"
 
Supported Relations:
* '''related''': Returns the related objects. Supported relation hierarchies are:
* '''datatable''': Returns all the data tables in given project available for the user.


+ all Common Supported Properties
Following methods are available:
{| class="wikitable"
!'''Method'''
! '''Description'''
|-
||[[Web_API:_Token|token]]
||Login user using username and password and get a session token as a response.
|-
||[[Web_API:_Signout|api/signout]]
||Logs out a user session.
|-
||[[Web_API:_Expression|api/expression]]
||Runs an expression.
|-
||[[Web_API:_Expression/query|api/expression/query]]
||Runs query written using the expression language and returns result data as response.
|-
||[[Web_API:_Filters|api/filters]]
||Get filters for all models or filters for a single model.
|-
||[[Web_API:_Serverinfo|api/serverinfo]]
||Returns common system information needed by UI, such as the default UI language and in whether SSO has been configured.
|-
||[[Web_API:_Importfile|api/importfile]]
||Import data into datatable from .csv, .xes or .pacm file.
|-
||[[Web_API:_Usersettings|api/usersettings]]
||Save user specific settings to the server.
|-
||[[Web_API:_Operations/terminate|api/operations/terminate]]
||Stops the defined tasks (by the task id) to save computing resources.
|-
||[[Web_API:_Cancel|api/analysis/cancel]]
||Stops currently running tasks (by the task identifier) to save computing resources.
|-
||[[Web_API:_saml2/acs|api/saml2/acs]]
||Identity provider (IdP) will send the SAML 2.0 assertion to this endpoint, which responses with 302 to redirect to QPR ProcessAnalyzer UI.
|-
||[[Web_API:_saml2|api/saml2]]
||Returns the SAML 2.0 service provider (SP) metadata, if SAML 2.0 authentication has been configured.
|}


== Identifying QPR ProcessAnalyzer Objects ==
In addition, there are methods for
QPR ProcessAnalyzer unique identifiers are used to uniquely identify any object in QPR ProcessAnalyzer. The format of a unique identifier is:
* [[Web API for Workspace Elements|moving and deleting workspace elements]]
* [[Web_API_for_Projects|projects]]
* [[Web_API_for_Dashboards|dashboards]]
* [[Web_API_for_Models|models]]
* [[Web_API_for_Datatables|datatables]]
* [[Web_API_for_Scripts|scripts]]
* [[Web_API_for_User_Management|users, groups and roles]]


'''PA.<type>.<object>'''
== Examples ==
Following function written in Python starts a script in QPR ProcessAnalyzer by calling the REST API. The function does following: (1) login to QPR ProcessAnalyzer, (2) start the script, and (3) log out. The call just starts the script without waiting for it to complete (asynchronous behavior).


In the format, '''<type>''' can be any of the following:
<syntaxhighlight lang="python" line>
* '''0''': undefined (reserved, do not use)
def startQprProcessAnalyzerScript(serverUrl: str, username: str, password: str, scriptId: int):
* '''1''': project
  loginData = {
* '''2''': data table
      "grant_type": "password",
* '''3''': model
      "username": username,
* '''4''': filter
      "password": password
* '''5''': bookmark
  }
  loginResponse = requests.post(
    url = serverUrl + "/token",
    data = loginData
  )
  loginResponse.raise_for_status()
  sessionToken = loginResponse.json().get("access_token")
 
  startScriptResponse = requests.post(
    url = serverUrl + "/api/scripts/run/" + str(scriptId),
    headers = {
      "Authorization": "Bearer " + sessionToken,
      "Content-type": "application/json"
    }
  )
  startScriptResponse.raise_for_status()


== Example Usage==
  logOutResponse = requests.post(
<pre>
      url = serverUrl + "/api/signout",
//login               
      headers = {
$.ajax({
        "Authorization": "Bearer " + sessionToken,
  "method": "POST",
        "Content-type": "application/json"
  "url": "http://localhost/qprpa/Mainservice.svc/webHttp/Authenticate",
      }
  "dataType": "json", "contentType": "application/json; charset=utf-8",
    )
   "data": JSON.stringify({
   logOutResponse.raise_for_status()
    'logOnName': '<username>',
</syntaxhighlight>
    'password': '<password>',
    'parameters': ''
  })
});                     


//create user
The function can be called as follows:
$.ajax({
<syntaxhighlight lang="python" line>
  "method": "POST",
startQprProcessAnalyzerScript(
   "url": "http://localhost/qprpa/Mainservice.svc/webHttp/SetUser",
   serverUrl = "https://server.onqpr.com/qprpa",
   "dataType": "json", "contentType": "application/json; charset=utf-8",
   username = "qpr",
   "data": JSON.stringify({
   password = "demo",
    "sessionId": "547c1aa5-e85b-4642-bbb1-8cb656015002",
  scriptId = 1
    "user": {"Name": "user", "FullName": "first last" },
)
    "parameters": [{"Key": "Password", "Value": "demo"}]
</syntaxhighlight>
  })
The script id can be found in the scripts list in the Workspace.
});


//add user to group, value 8:12:0 is user:group:member type
__NOTOC__
$.ajax({
  "method": "POST",
  "url": "http://localhost/qprpa/Mainservice.svc/webHttp/ModifyUserRelations",
  "dataType": "json", "contentType": "application/json; charset=utf-8",
  "data": JSON.stringify({
    "sessionId": "749dcbdb-e57b-434b-a739-1f4ddc7ebc30",
    "parameters": [{"Key": "AddGroups", "Value": "8:12:0"}]
  })
});


//log off
[[Category: QPR ProcessAnalyzer]]
$.ajax({
  "method": "POST",
  "url": "http://localhost/qprpa/Mainservice.svc/webHttp/LogOff",
  "dataType": "json", "contentType": "application/json; charset=utf-8",
  "data": JSON.stringify({
    "sessionId":"75aa3d08-5ad9-4b0b-8981-7daca98348cd"
  })
});
</pre>
 
== PowerShell example of listing users ==
<pre>
$paService=New-WebServiceProxy –Uri “http://localhost/qprpa/MainService.svc ”
$connection=$paService.Authenticate("username","password",@())
$token=$connection.GetValue(0).Value
$token
$param=@()
$users=$paService.GetUsers($token,$null,$param)
$users
$paService | get-member | ? {$_.definition -match "GetAnalysis"}
</pre>

Latest revision as of 20:06, 14 December 2023

QPR ProcessAnalyzer API can be used to build integrations with other applications and automate operations in the process mining system.

QPR ProcessAnalyzer API is a JSON based API following the REST design principles. All methods (except the token and serverinfo) require a prior login to establish a session. The session is initialized with the token call with username and password, and the access token is returned as a response for a successful login. The methods requiring prior authenticated session, need to have a HTTP request header Authorization with value Bearer <access token> to identify the session.

Url for calling the API has the following form (replace the server hostname with a correct one):

https://customer.onqpr.com/qprpa/api/<methodName>

Following methods are available:

Method Description
token Login user using username and password and get a session token as a response.
api/signout Logs out a user session.
api/expression Runs an expression.
api/expression/query Runs query written using the expression language and returns result data as response.
api/filters Get filters for all models or filters for a single model.
api/serverinfo Returns common system information needed by UI, such as the default UI language and in whether SSO has been configured.
api/importfile Import data into datatable from .csv, .xes or .pacm file.
api/usersettings Save user specific settings to the server.
api/operations/terminate Stops the defined tasks (by the task id) to save computing resources.
api/analysis/cancel Stops currently running tasks (by the task identifier) to save computing resources.
api/saml2/acs Identity provider (IdP) will send the SAML 2.0 assertion to this endpoint, which responses with 302 to redirect to QPR ProcessAnalyzer UI.
api/saml2 Returns the SAML 2.0 service provider (SP) metadata, if SAML 2.0 authentication has been configured.

In addition, there are methods for

Examples

Following function written in Python starts a script in QPR ProcessAnalyzer by calling the REST API. The function does following: (1) login to QPR ProcessAnalyzer, (2) start the script, and (3) log out. The call just starts the script without waiting for it to complete (asynchronous behavior).

def startQprProcessAnalyzerScript(serverUrl: str, username: str, password: str, scriptId: int):
  loginData = {
      "grant_type": "password",
      "username": username,
      "password": password
  }
  loginResponse = requests.post(
    url = serverUrl + "/token",
    data = loginData
  )
  loginResponse.raise_for_status()
  sessionToken = loginResponse.json().get("access_token")
  
  startScriptResponse = requests.post(
    url = serverUrl + "/api/scripts/run/" + str(scriptId),
    headers = {
      "Authorization": "Bearer " + sessionToken,
      "Content-type": "application/json"
    }
  )
  startScriptResponse.raise_for_status()

  logOutResponse = requests.post(
      url = serverUrl + "/api/signout",
       headers = {
         "Authorization": "Bearer " + sessionToken,
         "Content-type": "application/json"
       }
    )
  logOutResponse.raise_for_status()

The function can be called as follows:

startQprProcessAnalyzerScript(
  serverUrl = "https://server.onqpr.com/qprpa",
  username = "qpr",
  password = "demo",
  scriptId = 1
)

The script id can be found in the scripts list in the Workspace.