Start a Managed Server
You can send a POST request to synchronously start a Managed server in your WebLogic domain. The following steps show how to build this POST request using cURL:
-
Identify the host name and port of your domain's Administration Server and construct the GET request using the
/management/weblogic/{version}/domainRuntime/serverLifeCycleRuntimes/{name}/start
endpoint. This WebLogic Server request uses the following URL structure:http://localhost:7001/management/weblogic/{version}/domainRuntime/serverLifeCycleRuntimes/{name}/start
-
Specify the headers on the cURL command line:
-
-H X-Requested-By:MyClient
-
-H Accept:application/json
-
-H Content-Type:application/json
-
-
Construct the POST request. In the URL, specify the name of the server you want to start. In this example, we are starting the server,
Cluster1Server1
.http://localhost:7001/management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/Cluster1Server1/start
The following sample shows the complete POST request.
curl -v \
--user admin:admin123 \
-H X-Requested-By:MyClient \
-H Accept:application/json \
-X POST http://localhost:7001/management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/Cluster1Server1/start
The POST request returns the progress of the task. If the server starts successfully, the COMPLETED
status is returned.
HTTP/1.1 200 OK
Response Body:
{
"links": [{
"rel": "job",
"href": "http:\/\/localhost:7001\/management\/weblogic\/latest\/domainRuntime\/serverLifeCycleRuntimes\/Cluster1Server1\/tasks\/_0_start"
}],
"identity": [
"serverLifeCycleRuntimes",
"Cluster1Server1",
"tasks",
"_0_start"
],
"running": false,
"systemTask": false,
"endTimeAsLong": 1507164728441,
"name": "_0_start",
"progress": "success",
"description": "Starting Cluster1Server1 server ...",
"serverName": "Cluster1Server1",
"taskError": null,
"startTimeAsLong": 1507164708726,
"type": "ServerLifeCycleTaskRuntime",
"operation": "start",
"taskStatus": "TASK COMPLETED",
"parentTask": null,
"completed": true,
"intervalToPoll": 1000,
"startTime": "2017-10-04T20:51:48.726-04:00",
"endTime": "2017-10-04T20:52:08.441-04:00"
}