WebSphere Process Server, Version 6.2.0.1
Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, i5/OS, z/OS
GET /v1/activity/{aiid}/fault?{parameters}
Name | Value Type | Description |
---|---|---|
faultName | string | Name of the fault for which a new fault is to be created - only allowed with new=true.
|
Name | Value Type | Description | ||||||
---|---|---|---|---|---|---|---|---|
new | boolean | Indicates whether an "empty" fault should be returned.
|
None.
The default content-type is application/xml.
The default content-type is application/json.
{ "description": "BFM Error Response", "type": "object", "properties": { "errorNumber": {"type": "string", "description":"Message ID of the exception." }, "errorMessage": {"type": "string", "description":"Message text of the exception." }, "programmersDetails": {"type": "object", "optional": true, "description":"Additional, exception details, for example, a stack trace." } } }
Code | Description |
---|---|
200 OK | Success completion. |
400 Bad Request | The parameters are not valid or they are missing. |
401 Unauthorized | The caller is not authorized for this request. |
403 Forbidden | A fault is not meaningful for this kind of activity.
|
404 Not Found | The activity or the activity fault does not exist.
|
500 Internal Server Error | A severe problem has occurred, programmer's details are provided. |
6.2
Parent Topic: Activity Instance Fault Data Resource