2.3.1 Run Response Action window

The Run Response Action window is for manually executing response action. You can start the Run Response Action window in one of the following ways:

For response action associated with event-information

In the Operation menu, click the Run Response Action (Event information inheritance) menu.
In the Event details dialog, click the Run Response Action button.

When response action is not associated with the event-information

From Integrated Operation Viewer window Option menu, select the Run Response Action menu.

[Action type]

Select the type of action to be executed from the pull-down menu.

cmd: Execute with command.
restApi: Run in REST API.
eventStatus: Changes the response status of an event.
jump: Jumps to the specified URL.

The displayed screen differs depending on the type of action selected.

Organization of this subsection

(1) When cmd is selected as an action type
(2) When restApi is selected as an action type
(3) When eventStatus is selected as an action type
(4) When jump is selected as an action type

(1) When cmd is selected as an action type

The following explains when cmd is selected as the action type.

Figure 2‒12: **Run Response Action** window (when the action type is cmd)

[Inherit information]

Displays events that are inherited by response action executable (events subject to inheritance). If there are no JP1 events, they are inactive.

[Inheriting information]

Checked when inheriting the information of the event subject to inheritance to the execution content of response action.

If it is not checked, it will not be inherited.

[Execute host name]

Specify the host name under which response action is to be executed, up to 255 bytes.

[Execute command]

Specifies the command line to be executed.

You can specify a command line of up to 4096 bytes.

Attribute information of JP1 event displayed in [Inherit information] can be passed as a parameter of the command using a variable. For details about the variables that can be specified, see "7.8 Response actions manual execution inheritance function" in JP1/Integrated Management 3 -Manager Overview and System Design Guide.

[Environment variable file]

Specifies the name of environment variable file stored on the host where response action is executed, as a full path of no more than 255 bytes.

[Action name]

Specify the action name within 50 bytes.

It is recommended that you enter a meaningful name for each response action to see the history of the actions taken.

[Execute] button

The following occurs depending on whether the [Inherit information] check box is selected in [Inheritance information].

When the [Inheriting information] check box is selected

The [Preview response action Executions] window is displayed.
When the [Inheriting information] check box is not checked

Executes the specified response action.

[Execution History]

Display the execution history list. When you hover over a line in the execution history, the tooltip text displays its contents.

A maximum of 100 execution histories are displayed. When the number exceeds 100, the oldest one is deleted from the oldest one.

To Page Top

(2) When restApi is selected as an action type

The following explains when restApi is selected as the action type.

Figure 2‒13: **Run Response Action** window (when the action type is restApi)

[Inherit Information]

Displays events that are inherited by response action executable (events subject to inheritance). If there are no JP1 events, they are inactive.

[Inherit information]

Checked when inheriting the information of the event subject to inheritance to the execution content of response action.

If it is not checked, it will not be inherited.

[Method]

Select REST API method from the pull-down menu.

GET
HEAD
POST
PUT
PATCH
DELETE
OPTIONS
TRACE

[URL]^#

Specifies URL of REST API, up to 2046 bytes.

[Request Header] ^#

Specifies REST API request header in object format. Specify within 65,536 bytes.

[Body] ^#

Specifies the body of REST API in an objectformat. If you specify GET, or DELETE in [Method], you can omit it if you do not need the body. If it exceeds 10MB(10,485,760 byte), an error will occur.

[Action name]

Specify the action name within 50 bytes.

It is recommended that you enter a meaningful name for each response action to see the history of the actions taken.

[Execute] button

The following occurs depending on whether the [Inherit Information] check box is selected in [Inheritance Information].

When the [Inherit Information] check box is selected

The [Preview response action Executions] window is displayed.
When the [Inherit Information] check box is not checked

Executes the specified response action.

[Execution History]

Display the execution history list. When you hover over a line in the execution history, the tooltip text displays its contents.

A maximum of 100 execution histories are displayed. When the number exceeds 100, the oldest one is deleted from the oldest one.

#

Attribute information of JP1 event displayed in [Inheritance Information] can be passed as a parameter using a variable. For details about the variables that can be specified, see "7.8 Response actions manual execution inheritance function" in JP1/Integrated Management 3 -Manager Overview and System Design Guide.

To Page Top

(3) When eventStatus is selected as an action type

The following explains when eventStatus is selected as the action type.

Figure 2‒14: **Run Response Action** window (When the action type is eventStatus)

[Inheritance information]

Displays events that are inherited by response action executable (events subject to inheritance). If there are no JP1 events, they are inactive.

[Inherit information]

Checked when inheriting the information of the event subject to inheritance to the execution content of response action.

If it is not checked, it will not be inherited.

[Response status]

Specify the response status. The default is [Not taken].

Unaddressed
Corrective action completed
In process
Hold

[JP1 Events SID,...]

Specifies SID of JP1 events for which you want to obtain response status. If you want to specify SID for more than one JP1 event, specify SID of JP1 event concatenated with ",". You can specify up to 2000 SID. An error occurs if the value is 10MB or higher.

The attribute information of JP1 event displayed in [Inheritance information] can be passed as a parameter of SID of JP1 event using a variable. For details about the variables that can be specified, see "7.8 Response actions manual execution inheritance function" in JP1/Integrated Management 3 -Manager Overview and System Design Guide.

[Action Name]

Specify the action name within 50 bytes.

It is recommended that you enter a meaningful name for each response action to see the history of the actions taken.

[Execute] button

The following occurs depending on whether the [Inherit Information] check box is selected in [Inheritance Information].

When the [Inherit Information] check box is selected

The [Preview response action executions] window is displayed.
When the [Inherit Information] check box is not checked

Executes the specified response action.

[Execution History]

Display the execution history list. When you hover over a line in the execution history, the tooltip text displays its contents.

A maximum of 100 execution histories are displayed. When the number exceeds 100, the oldest one is deleted from the oldest one.

To Page Top

(4) When jump is selected as an action type

The following explains when jump is selected as the action type.

Figure 2‒15: **Run Response Action** window (When the action type is jump)

[Inheritance Information]

Displays events that are inherited by response action executable (events subject to inheritance). If there are no JP1 events, they are inactive.

[Inherit information]

Checked when inheriting the information of the event subject to inheritance to the execution content of response action.

If it is not checked, it will not be inherited.

[URL]^#

Specify URL to be jumped to, up to 2046 bytes.

Specify "http://", "https://", or "index?" at the beginning.

The following characters can be specified:

Single-byte alphanumeric characters and ";", ";", "/", "?", ":", "@", "&", "=", "+", "$", ", "-", "_", ".", "!", "~", "*", "'", "'", "(", ")", "%"

[HTML's target properties] ^#

Specifies target of HTML when opening the jumped URL, up to 64 bytes.

The following characters cannot be specified:

_self
_parent
_top
Value starting from "JP1IM_"

If a character that cannot be specified is included when the [Execute] button is clicked, KAJY64703-E messaging window is displayed.

If the specification is omitted, "_blank" is assumed.

If a URL beginning with "index" is specified for [URL], this specification is ignored.

[Action Name]

Specify the action name within 50 bytes.

It is recommended that you enter a meaningful name for each response action to see the history of the actions taken.

[Execute] button

The following occurs depending on whether the [Inherit Information] check box is selected in [Inheritance Information].

When the [Inherit Information] check box is selected

The [Preview response action executions] window is displayed.
When the [Inherit Information] check box is not checked

Executes the specified response action.

#

Attribute information of JP1 event displayed in [Inheritance information] can be passed as a parameter using a variable. For details about the variables that can be specified, see "7.8 Response actions manual execution inheritance function" in JP1/Integrated Management 3 -Manager Overview and System Design Guide.

To Page Top