機械翻訳について

ジョブIDによるサーバー操作のステータスの表示

get

/api/v1.1/instances/{identityId}/{serviceId}/servers/history/job/{jobId}

ジョブIDで指定されたスケーリング操作のステータスが返されます。

リクエスト

パス・パラメータ
jobId
タイプ: string
必須: true
スケーリング操作のジョブID。

レスポンス

サポートされるメディア・タイプ
  • application/json
  • text/plain
200レスポンス
OK
本文
ルート・スキーマ: ViewStatusOfServerOperationByJobIDStatus
ネスト・スキーマ: actLog
タイプ: array
ログに定義されたアクティビティをグループ化します。
ネスト・スキーマ: actLog

次の例は、cURLを使用してRESTリソースに対するGETリクエストを発行することによって、ジョブIDを使用したOracle SOA Cloud Serviceインスタンスのサーバー操作に関する情報の表示方法を示しています。 詳細は、「cURLの使用」を参照してください。

cURLコマンド

curl -X GET -u joe@example.com:Welcome1! -H "X-ID-TENANT-NAME:ExampleIdentityDomain" https://api-host/paas/service/soa/api/v1.1/instances/ExampleIdentityDomain/ExampleInstance/servers/history/job/505
注意:: この例では、アメリカ合衆国でのURL接頭辞(soacs)を使用しています。 世界の他の地域のURL接頭辞の詳細は、「リクエストの送信」を参照してください。

レスポンス・ヘッダーの例

レスポンス・ヘッダーの例を次に示します。

HTTP/1.1 200 OK
Date: Mon, 02 Feb 2015 22:22:34 GMT
Transfer-Encoding: chunked
Content-Type: application/json

レスポンス本文の例

次に、サービス・インスタンス停止リクエストに関するアクティビティ・ログを取得するレスポンス本文の例を示します。

{
    "actLog":
    {
        "activityLogId":112,
        "serviceId":101,
        "operation":
        {
            "operationId":56,
            "operationType":"CREATE_SERVICE"
        },
        "status":"SUCCEED",
        "startDate":"Apr 9, 2015 12:47:19 PM",
        "endDate":"Apr 9, 2015 1:07:37 PM",
        "identityDomain":"ExampleIdentityDomain",
        "serviceName":"ExampleInstance",
        "hostName":null,
        "serverName":null,
        "serverType":null,
        "jobId":269,
        "messages":[
        {
            "activityMessageId":199,
            "activityDate":"Apr 9, 2015 12:47:19 PM",
            "stepName":"NEW",
            "message":"Submitted Job, Status\u003dWaitingOnResource"        
        },
        {
            "activityMessageId":200,
            "activityDate":"Apr 9, 2015 12:47:19 PM",
            "stepName":"RUNNING",
            "message":"setComputeNamespace"
        },
        {
            "activityMessageId":201,
            "activityDate":"Apr 9, 2015 1:07:37 PM",
            "stepName":"RUNNING",
            "message":"setServiceState""
        }
        ]},
        "messages":[{},{},{},{}
        ]
    }
}

次に、スケール・アウト操作に関するアクティビティ・ログを取得するレスポンス本文の例を示します。

{
    "actLog":
    {
        "activityLogId":17,
        "serviceId":202,
        "operation":
        {
            "operationId":202,
            "operationType":"SCALE_OUT"
        },
        "status":"SUCCEED",
        "startDate":"Apr 9, 2015 8:35:44 PM",
        "endDate":"Apr 9, 2015 9:05:25 PM",
        "identityDomain":"ExampleIdentityDomain",
        "serviceName":"ExampleInstance",
        "hostName":"exampleinstance-wls-4",
        "serverName":"ExampleI_server_4",
        "serverType":null,
        "jobId":4010,
        "messages":[
        {
            "activityMessageId":1532,
            "activityDate":"Apr 9, 2015 8:35:44 PM",
            "stepName":"NEW",
            "message":"Submitted Job, Status\u003dInProgress"
        },
        {
            "activityMessageId":1533,
            "activityDate":"Apr 9,2015 8:35:44 PM",
            "stepName":"RUNNING",
            "message":"initializing"},
        {
            "activityMessageId":1534,
            "activityDate":"Apr 9, 2015 8:35:44 PM",
            "stepName":"RUNNING",
            "message":"Scaling job for service [ExampleInstance] in cluster [ExampleI_cluster] with factor [1] is prepared."
        },
        {
            "activityMessageId":1535,
            "activityDate":"Apr 9, 2015 8:35:46 PM",
            "stepName":"RUNNING",
            "message":"SOACS-SCALING-161: Completed submitting config lock script on service [ExampleInstance]"
        },        
        {
            "activityMessageId":1536,
            "activityDate":"Apr 9, 2015 8:36:50 PM",
            "stepName":"RUNNING",
            "message":"SOACS-SCALING-173: Checking for config lock is completed for service [ExampleInstance]"
        },
        {
            "activityMessageId":1537,
            "activityDate":"Apr 9, 2015 8:36:50 PM",
            "stepName":"RUNNING",
            "message":"SOACS-SCALING-119: Completed creating the backup child job for service [ExampleInstance]"
        },
        {
            "activityMessageId":1538,
            "activityDate":"Apr 9, 2015 8:37:56 PM",
            "stepName":"RUNNING",
            "message":"SOACS-SCALING-122: Completed creating the backup for service [ExampleInstance]"
        },
        {
            "activityMessageId":1540,
            "activityDate":"Apr 9, 2015 8:38:03 PM",
            "stepName":"RUNNING",
            "message":"New Managed Server name is [ExampleI_server_4]"
        },
        {
            "activityMessageId":1539,
            "activityDate":"Apr 9, 2015 8:38:03 PM",
            "stepName":"RUNNING",
            "message":"Created the required storage and compute configurations for WebLogic Server managed server [ExampleI_server_4]..."
        },
        {
            "activityMessageId":1541,
            "activityDate":"Apr 9, 2015 8:38:03 PM",
            "stepName":"RUNNING",
            "message":"SOACS-SCALING-129: Completed submitting child job for checking VM provisioning and health"
        },
        {
            "activityMessageId":1542,
            "activityDate":"Apr 9, 2015 9:00:35 PM",
            "stepName":"RUNNING",
            "message":"Started the required compute resources for WebLogic Server managed server [ExampleI_server_4]..."
        },
        {
            "activityMessageId":1543,
            "activityDate":"Apr 9, 2015 9:00:35 PM",
            "stepName":"RUNNING",
            "message":"Orchestration is in ready state, new VM is up for server [ExampleI_server_4]"
        },
        {
            "activityMessageId":1544,
            "activityDate":"Apr 9, 2015 9:00:35 PM",
            "stepName":"RUNNING",
            "message":"Completed submitting child job for checking managed server configuration "
        },
        {
            "activityMessageId":1545,
            "activityDate":"Apr 9, 2015 9:05:13 PM",
            "stepName":"RUNNING",
            "message":"Configured WebLogic Server managed server [ExampleI_server_4]..."
        },
        {
            "activityMessageId":1547,
            "activityDate":"Apr 9, 2015 9:05:25 PM",
            "stepName":"RUNNING",
            "message":"Scale out for service [ExampleInstance] succeeded"
        },
        {
            "activityMessageId":1546,
            "activityDate":"Apr 9, 2015 9:05:25 PM",
            "stepName":"RUNNING",
            "message":"Started WebLogic Server managed server [ExampleI_server_4]..."
        },
        {
            "activityMessageId":1548,
            "activityDate":"Apr 9, 2015 9:05:25 PM",
            "stepName":"RUNNING",
            "message":"Completed submitting OTD script for remote execution on service [ExampleInstance]"
        },
        {
            "activityMessageId":1549,
            "activityDate":"Apr 9, 2015 9:05:25 PM",
            "stepName":"SUCCEED",
            "message":"SOACS-SCALING-095: Service [ExampleInstance] is not provisioned with OTD, hence notifying OTD with server [ExampleI_server_4] is bypassed"
        },
        {
            "activityMessageId":1550,
            "activityDate":"Apr 9, 2015 9:05:25 PM",
            "stepName":"RUNNING",
            "message":"Service [ExampleInstance] is not provisioned with OTD, hence notifying OTD with server [ExampleI_server_4] is bypassed"
        },
        {
            "activityMessageId":1551,
            "activityDate":"Apr 9, 2015 9:05:25 PM",
            "stepName":"SUCCEED",
            "message":"addServerToOTDVerify"
        }
    ]},"messages":[{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{}
]}