Force Suspend
post
/management/weblogic/{version}/domainRuntime/serverLifeCycleRuntimes/{name}/forceSuspend
Transitions the server from RUNNING to ADMIN state forcefully cancelling inflight work.
Work that cannot be cancelled is dropped. Applications are brought into the admin mode forcefully.
This method supports both asynchronous and best effort synchronous invocations. The behavior is controlled by the 'Prefer' header.
Request
Path Parameters
-
name: string
The name property of the instance in the collection.
-
version: string
The version of the WebLogic REST interface.
Header Parameters
-
Prefer(optional): string
The 'Prefer' header parameter can be used to specify the preference on how this method runs. A value of 'respond-async' specifies a preference to submit the request and return immediately without waiting for completion. Alternatively a value of 'wait=#seconds' specifies a preference to wait for #seconds for method completion before returning. If the Prefer header is not specified or invalid, then a 300 second wait will be used.
-
X-Requested-By: string
The 'X-Requested-By' header is used to protect against Cross-Site Request Forgery (CSRF) attacks. The value is an arbitrary name such as 'MyClient'.
Security
-
Admin: basic
Type:
basic
Description:A user in the Admin security role.
-
Operator: basic
Type:
basic
Description:A user in the Operator security role.
Response
Supported Media Types
- application/json
200 Response
Returns the following fields:
Root Schema : Return
Type:
object
Title:
Show Source
Return
-
return(optional):
array Server Life Cycle Task Runtime Reference
Title:
Server Life Cycle Task Runtime Reference
Contains the server life cycle task runtime reference.Returns the action's result.
Nested Schema : Server Life Cycle Task Runtime Reference
Type:
array
Title:
Server Life Cycle Task Runtime Reference
Contains the server life cycle task runtime reference.
Show Source
Returns the action's result.
Examples
Synchronously invoke the forceSuspend action.
This example uses the POST method to synchronously invoke the forceSuspend action.
Example Request
curl -v \ --user admin:admin123 \ -H X-Requested-By:MyClient \ -H Accept:application/json \ -H Content-Type:application/json \ -d "{}" \ -X POST http://localhost:7001/management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/Cluster-0-Server-1/forceSuspend?links=job,abort&fields=completed,progress,serverName,operation,taskStatus
Example Response
HTTP/1.1 200 OK Response Body: { "links": [{ "rel": "job", "href": "http:\//localhost:7001/management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/Cluster-0-Server-1/tasks/_8_forceSuspend" }], "progress": "success", "serverName": "Cluster-0-Server-1", "operation": "forceSuspend", "taskStatus": "TASK COMPLETED", "completed": true }
Asynchronously invoke the forceSuspend action.
This example uses the POST method to asynchronously invoke the forceSuspend action.
Example Request
curl -v \ --user admin:admin123 \ -H X-Requested-By:MyClient \ -H Accept:application/json \ -H Content-Type:application/json \ -d "{}" \ -H "Prefer:respond-async" \ -X POST http://localhost:7001/management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/Cluster-0-Server-1/forceSuspend?links=job,abort&fields=completed,progress,serverName,operation,taskStatus
Example Response
HTTP/1.1 200 OK Response Body: { "links": [{ "rel": "job", "href": "http:\//localhost:7001/management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/Cluster-0-Server-1/tasks/_20_forceSuspend" }], "progress": "success", "serverName": "Cluster-0-Server-1", "operation": "forceSuspend", "taskStatus": "TASK COMPLETED", "completed": true }Back to Top