Jump to

• Request
• Response

Restart Node Manager

post

/management/weblogic/{version}/domainRuntime/rolloutService/restartNodeManager

Restart NodeManager. The java based NodeManager process will exit and the startNodeManager script will detect the need to restart and will restart the NodeManager using the same original call path that was used to start the NodeManager. If this call path was using a symbolic link, then the NodeManager will be started from the location of the symbolic link which may have the affect of starting the NodeManager with an updated set of binaries or scripts.

This method supports both asynchronous and best effort synchronous invocations. The behavior is controlled by the 'Prefer' header.

Request

Supported Media Types

• application/json

Path Parameters

• 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'.

Body ()

Must contain the following fields:

Root Schema : Arguments

Type: object

Title: Arguments

Show Source

• isAdminServer(optional): boolean

  true if the affected server is the AdminServer

• machineName(optional): string

  Name of MachineMBean where NodeManager runs

• timeoutMillis(optional): integer(int64)

  How long to wait for the client to reconnect to the NodeManager after it restarts. Timeout exceeded will consider the task failed and the NodeManager not reachable. Default is 3 minutes.

{
    "type":"object",
    "title":"Arguments",
    "properties":{
        "isAdminServer":{
            "type":"boolean",
            "description":"<p>true if the affected server is the AdminServer</p>"
        },
        "machineName":{
            "type":"string",
            "description":"<p>Name of MachineMBean where NodeManager runs</p>"
        },
        "timeoutMillis":{
            "type":"integer",
            "format":"int64",
            "description":"<p>How long to wait for the client to reconnect to the NodeManager after it restarts.  Timeout exceeded will consider the task failed and the NodeManager not reachable. Default is 3 minutes.</p>"
        }
    },
    "description":""
}

Security

• Admin: basic
  Type: basic

  Description: A user in the Admin security role.

Back to Top

Response

Supported Media Types

• application/json

200 Response

Returns the following fields:

Body ()

Root Schema : Return

Type: object

Title: Return

Show Source

• return(optional): array Workflow Task Runtime Reference
  Title: Workflow Task Runtime Reference

  Contains the workflow task runtime reference.

  Returns the action's result.

{
    "type":"object",
    "title":"Return",
    "properties":{
        "return":{
            "title":"Workflow Task Runtime Reference",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"Contains the workflow task runtime reference. <p>Returns the action's result.</p>"
        }
    },
    "description":""
}

Nested Schema : Workflow Task Runtime Reference

Type: array

Title: Workflow Task Runtime Reference

Contains the workflow task runtime reference.

Returns the action's result.

Show Source

• Array of: string

{
    "title":"Workflow Task Runtime Reference",
    "type":"array",
    "items":{
        "type":"string",
        "description":""
    },
    "description":"Contains the workflow task runtime reference. <p>Returns the action's result.</p>"
}

Back to Top