Getting a list of actions that can be executed by the execute action function

Ops Center Analyzer REST API Reference Guide

Version

11.0.x

Audience

anonymous

Part Number

MK-99ANA003-20

You can obtain a list of actions that the execute action function can perform.

Execution permission

Admin, Modify

Request line

POST baseURL/v1/services/CustomAction/actions/getActionTemplateList/invoke

Request body

The structure of the request body and the object attributes are as follows:

Action

{
        "name":"...",
        "href":"...",
        "method":"...",
        "type":"...",
        "parameters":["...", ...]
}

Action (Type: Action)

Attribute	Type	Description
name	string	Name of the action.
href	string	URL for the action.
method	string	Name of the method.
type	string	Data format for the object.
parameters	anyType[]	A list of GetActionTemplateListParam objects necessary to execute an operation. For details, see the table below.

GetActionTemplateListParam

{
        "componentID":"...",
        "nodeID":"...",
        "targetTypes":["...", ...]
}

GetActionTemplateListParam (Type: GetActionTemplateListParam)

Attribute	Type	Description
componentID	string	ID of the component specified as the action execution target. The ID of the device that the component belongs to must also be specified. To execute an action for a device, omit this parameter.
nodeID	string	ID of the device specified as the action execution target
targetTypes	enum[]	Type of actions to be acquired. (For details about the valid values, see the table TemplateType in List of enumerators.)

Attribute

Type

Description

componentID

string

ID of the component specified as the action execution target. The ID of the device that the component belongs to must also be specified. To execute an action for a device, omit this parameter.

nodeID

string

ID of the device specified as the action execution target

targetTypes

enum[]

Type of actions to be acquired.

(For details about the valid values, see the table TemplateType in List of enumerators.)

Response body

The structure of the response body and the object attributes is as follows:

Job

{
        "instanceID":"...",
        "created":"...",
        "updated":"...",
        "completed":"...",
        "state":"...",
        "affectedResource":["...", ...],
        "result":["...", ...]
}

Job (Type: Job)

Attribute	Type	Description
instanceID	string	ID of the Instance.
created	string	Date the object is generated in "yyyy-mm-ddThh:mm:ss.mmmTZD" format (e.g., 2017-08-25T20:07:39.472+09:00).
updated	string	Time the object is updated in "yyyy-mm-ddThh:mm:ss.mmmTZD" format (e.g., 2017-08-25T20:07:39.472+09:00).
completed	string	Time the processing completed in "yyyy-mm-ddThh:mm:ss.mmmTZD" format (e.g., 2017-08-25T20:07:39.472+09:00).
state	string	One of the following values is set: "failed": The operation failed. "success": The operation completed successfully.
affectedResource	string[]	A blank space is set.
result	anyType[]	A list of ActionTemplate objects. For details, see the table below.

ActionTemplate

{
        "instanceID":"...",
        "name":"...",
        "description":"...",
        "templateFileName":"...",
        "templateType":"...",
        "multipleResources":"...",
        "automationDirectorServiceGroupName":"...",
        "automationDirectorServiceName":"..."
}

ActionTemplate (Type: ActionTemplate)

Attribute	Type	Description
instanceID	string	ID of the action
name	string	Name of the action
description	string	Description of the action
templateFileName	string	Name of the template file in which the action is registered
templateType	enum	Template type of action (For details about the valid values, see the table TemplateType in List of enumerators.) COMMAND MAIL
multipleResources	boolean	Whether the template supports the use of multiple resource IDs
automationDirectorServiceGroupName	string	The name of an Ops Center Automator service group
automationDirectorServiceName	string	The name of an Ops Center Automator service

Status codes

Status code	Reason phrase	Description
200	OK	Success.
400	Bad Request	The format of the request body is invalid.
401	Unauthorized	No login privilege.
403	Forbidden	No update privilege.
404	Not Found	The resource was not found.
412	Precondition Failed	The server is not available.
500	Internal Server Error	Server processing error.
503	Service Unavailable	Analyzer detail view server communication error.

Example code

[Request Header]
POST /Analytics/v1/services/CustomAction/actions/getActionTemplateList/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json

[Request Body]
{
  "name": "getActionTemplateList",
  "href": "http://localhost:22015/Analytics/v1/services/CustomAction/actions/getActionTemplateList/invoke",
  "method": "POST",
  "type": "application/json",
  "parameters":[{
    "nodeID":"h#ITPDLab_172.17.17.115_host-258"
  }]
}

[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 17:56:21 GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json


[Response Body]
{
  "instanceID" : "4bc7ea0e-284a-4fab-a4fe-ba8a8ace40fe",
  "created" : "2016-08-12T02:56:21.855+09:00",
  "updated" : "2016-08-12T02:56:22.711+09:00",
  "completed" : "2016-08-12T02:56:22.711+09:00",
  "state" : "success",
  "affectedResource" : [ ],
  "result" : [ {
    "instanceID" : 0,
    "name" : "MailActionTemplate",
    "description" : "mail template description",
    "templateFileName" : "/opt/hitachi/Analytics/conf/template/mail/MailTemplate.txt",
    "templateType" : "MAIL"
  }, {
    "instanceID" : 1,
    "name" : "CommandActionTemplate",
    "description" : "command template description",
    "templateFileName" : "/opt/hitachi/Analytics/conf/template/command/CmdTemplate.txt",
    "templateType" : "COMMAND"
  } ]
}