View This Trigger Runtime Collection
/management/weblogic/{version}/serverRuntime/partitionRuntimes/{name}/resourceManagerRuntime/resourceRuntimes/{name}/triggerRuntimes
View this trigger runtime collection.
Request
-
name: string
The name property of the instance in the collection.
-
version: string
The version of the WebLogic REST interface.
-
excludeFields(optional): string
The 'excludeFields' query parameter is used to restrict which fields are returned in the response. It is a comma separated list of field names. If present, only fields whose name is not on the list will be returned. If not present, all fields are returned (unless the 'fields' query parameter is specified). Note: 'fields' must not be specified if 'excludeFields' is specified.
-
excludeLinks(optional): string
The 'excludeLinks' query parameter is used to restrict which links are returned in the response. It is a comma separated list of link relationship names. If present, only links whose relationship name is not on the list will be returned. If not present, all links are returned (unless the 'links' query parameter is specified). Note: 'links' must not be specified if 'excludeLinks' is specified.
-
fields(optional): string
The 'fields' query parameter is used to restrict which fields are returned in the response. It is a comma separated list of field names. If present, only fields with matching names are returned. If not present, all fields are returned (unless the 'excludeFields' query parameter is specified). Note: 'excludeFields' must not be specified if 'fields' is specified.
-
links(optional): string
The 'links' query parameter is used to restrict which links are returned in the response. It is a comma separated list of link relationship names. If present, only links with matching relationship names are returned. If not present, all links are returned (unless the 'excludeLinks' query parameter is specified). Note: 'excludeLinks' must not be specified if 'links' is specified.
-
Admin: basic
Type:
basicDescription:A user in the Admin security role. -
Deployer: basic
Type:
basicDescription:A user in the Deployer security role. -
Monitor: basic
Type:
basicDescription:A user in the Monitor security role. -
Operator: basic
Type:
basicDescription:A user in the Operator security role.
Response
- application/json
200 Response
Returns a list of trigger runtime entities.
object-
activated(optional):
boolean
Read Only:
trueIndicates if the Trigger is Activated
-
initiated(optional):
boolean
Read Only:
trueIndicates if a recourse action has been initiated for this Trigger as a result of the current resource usage by a Domain Partition exceeding its usage limit. A new
RecourseActionEventVBeanis added to the array returned by getRecourseActionEventsHistory().The kind of recourse action initiated (for example, a new recourse action or a withdrawal of an existing recourse action) can be determined through RecourseActionEventVBean#isActive().
-
lastTimeExecuted(optional):
string(date-time)
Read Only:
trueThe
This value represents a date as a string in ISO 8601 format, yyyy-MM-dd'T'HH:mm:ss.SSSXXXDatewhen the last recourse action was successfully executed for the current Trigger. -
name(optional):
string
Read Only:
trueThe name of the Trigger, as configured in the Resource Consumption Management policy of the Domain Partition.
-
recourseActionEventsHistory(optional):
array Items
Title:
ItemsRead Only:trueA list of recourse action events that have been initiated and executed.
-
type(optional):
string
Read Only:
trueReturns the type of the MBean.
Constraints
- unharvestable
arrayItemstrueA list of recourse action events that have been initiated and executed.
object-
action(optional):
string
Read Only:
trueThe recourse action type configured in the Domain Partition's Resource Consumption Management policy for the current Trigger.
-
actionSuccessful(optional):
boolean
Read Only:
trueIndicates if the recourse action execution was successfully completed.
-
active(optional):
boolean
Read Only:
trueIndicates if the recourse action is a new execution of a recourse action because the usage limit is exceeded or the withdrawal of an existing recourse action because the current resource usage has gone below the usage limit.
-
executionDate(optional):
string(date-time)
Read Only:
trueThe date and time the recourse action successfully executes.
This value represents a date as a string in ISO 8601 format, yyyy-MM-dd'T'HH:mm:ss.SSSXXX -
initiated(optional):
boolean
Read Only:
trueIndicates if a recourse action has been initiated for this Trigger as a result of the current resource usage by a Domain Partition exceeds its usage limit.
-
usage(optional):
integer(int64)
Read Only:
trueThe current resource usage by the Domain Partition when the recourse action was initiated.