Monitor > Processes > Process management APIs for deployed processes
Process management APIs for deployed processes
You can use REST APIs to manage and perform various functions on the deployed processes.
REST APIs for viewing processes
You can use REST APIs to get a list all the processes that run on the Cloud Server or a Secure Agent.
If the REST API call is successful, the API returns the status code 200 in the response body.
REST APIs for viewing all processes
You can use REST APIs to view all the processes that run on the Cloud Server or a Secure Agent. The maximum number of processes that is returned by default is 20. The following table describes the REST APIs:
API
Description
Authorization Header
Status Code
GET <Informatica Cloud Application Integration URL>/active-bpel/restadmin/processes/
Lists all the processes that run on the Cloud Server.
IDS-SESSION-ID
200
GET http://<agentName>:<httpPortNumber>/process-engine/restadmin/processes/
Lists all the processes that run on a specific Secure Agent.
IDS-SESSION-ID
200
The following example shows a sample response when you view the list of processes on the Cloud Server:
You can use REST APIs to view a process execution status using the run ID of the process that was run on the Cloud Server or a Secure Agent. The following table describes the REST APIs:
API
Description
Authorization Header
Status Code
GET <Informatica Cloud Application Integration URL>/active-bpel/restadmin/processes/?processId=<RunID>/?
View the process execution status using the run ID of the process that was run on the Cloud Server.
IDS-SESSION-ID
200
GET http://<agentName>:<httpPortNumber>/process-engine/restadmin/processes/?processId=<RunID>/
View the process execution status using the run ID of the process that was run on a Secure Agent.
IDS-SESSION-ID
200
The following example shows a sample response when you view the process execution status based on the run ID that run on the Cloud Server:
Get method to fetch the details of a process using filters and advanced query
You can use REST APIs to fetch the details of a process using a filter value. The following table describes the REST APIs:
API
Description
Authorization Header
Status Code
GET http://<agentName>:<httpPortNumber>/process-engine/restadmin/processes?<Filters>
Fetch the details of a process using filters. You must append parameters to the URL to filter the process by using the & symbol.
IDS-SESSION-ID
200
GET <Informatica Cloud Application Integration URL>/active-bpel/restadmin/processes?<Filters>
Use the filters to fetch the details of a process that run on Cloud Server. You must append parameters to the URL to filter the process by using the & symbol.
IDS-SESSION-ID
200
GET http://<agentName>:<httpPortNumber>/process-engine/restadmin/processes?<AdvancedQuery>
Fetch the details of a process based on the advanced process filter condition. You can combine the advanced query filters and append the parameters to the URL using the AND condition.
IDS-SESSION-ID
200
GET <Informatica Cloud Application Integration URL>/active-bpel/restadmin/processes?<Filters>
Use the advanced process filter condition to fetch the details of a process that run on Cloud Server. You can combine the advanced query filters and append the parameters to the URL using the AND condition.
For example: {{ <Informatica Intelligent Cloud Services URL>}}/active-bpel/restadmin/processes?advancedQuery=getProcessProperty("Version")=3.0 and getProcessProperty("Title") = "Process_fault_multiple_version"
IDS-SESSION-ID
200
The following table describes the query parameters to the request URL using filters:
Parameter
Type
Description
processState
String
The state of the process. Refer to the following states: SUSPENDED, COMPLETED, RUNNING, COMPENSATABLE, FAULTED.
processName
String
The API name of the process.
processNameNamespace
String
The value that isolates a process from other processes.
processGroup
String
The name of the process group. For example, $system, or RT.User.
hideSystem
Boolean
The value is TRUE when the system parameters are hidden and the value is FALSE when the system parameters are not hidden.
hidePublicTenant
Boolean
The value is TRUE when the tenant details are hidden and the value is FALSE when the tenant details are not hidden.
listStart
Encoded Integer
The starting point of the list.
maxReturn
Encoded Integer
The max number of results to return.
processId
String
The ID of the process.
The following example shows a sample response when you fetch the details of a process using a filter value:
The following table describes the query parameters to the request URL using advanced query:
Parameter
Type
Description
State
String
The state of the process. The following list describes the state reason values and the associated state reason codes:
- 3. COMPLETED
- 4. FAULTED
- 1. RUNNING
- 2. SUSPENDED
- 5.COMPENSATABLE
Version
String
The version number of the published asset.
EndDate
String
The date the process expired.
Start Date
String
The date the process was run.
Initiator
String
The name of the user who initiated the process.
StateReason
String
The reason why a process is in a specific state. The following list describes the state reason values and the associated state reason codes:
- Suspended (Manual). 0. Applies to processes that were suspended manually.
- Suspended (Faulting). 1. Applies to processes that were suspended due to a fault that was not caught.
- Suspended (Activity). 2. Applies to processes that were suspended at a BPEL suspend activity.
- Suspended (Migration Error). 7. Applies to processes that were suspended due to a migration error for a process that has been migrated to a new process version.
- Suspended (Migration Warning). 8. Applies to processes that were suspended due to a migration warning for a process that has been migrated to a new process version. Warnings indicate differences found in the new version that might need review and updates before you resume the process.
- Pre Migration Copy. 20. Applies to an old process instance that has been saved temporarily until the new process instance has been resumed or terminated.
The following example shows a sample response when you fetch details of a single process using the advanced query output:
You can use REST APIs suspend, resume, or terminate a process that runs on the Cloud Server or a Secure Agent. For authorization, you can pass the IDS-SESSION-ID in the headers.
If the REST API call is successful, the API returns the status code 204 in the response body.
You can use REST APIs to manage all the processes that run on the Cloud Server or a Secure Agent. The following table describes the REST APIs:
API
Description
PUT <Informatica Cloud Application Integration URL>/active-bpel/restadmin/processes/<process-id>/suspend
Suspend a process that runs on the Cloud Server within a specific organization.
PUT http://<agentName>:<httpPortNumber>/process-engine/restadmin/processes/<process-id>/suspend
Suspend a process that runs on a specific Secure Agent.
PUT <Informatica Cloud Application Integration URL>/active-bpel/restadmin/processes/<process-id>/resume
Resume a process that was suspended on the Cloud Server within a specific organization.
PUT http://<agentName>:<httpPortNumber>/process-engine/restadmin/processes/<process-id>/resume
Resume a process that was suspended on a specific Secure Agent.
PUT <Informatica Cloud Application Integration URL>/active-bpel/restadmin/processes/<process-id>/terminate
Terminate a process that was run or suspended on the Cloud Server within a specific organization.
PUT http://<agentName>:<httpPortNumber>/process-engine/restadmin/processes/<process-id>/terminate
Terminate a process that was run or suspended on a specific Secure Agent.