Class CIM_BasicExecutionService
extends CIM_Service

The basic execution service (BES)is a service to which clients can send requests to initiate, monitor, and manage computational activities and access information about the BES. A BasicExecutionService can act on one or more execution environments - modeled, profiled, and instantiated as a ComputerSystem. There is no requirement that a BasicExecutionService reside on the node of a ComputerSystem on which it acts. The associations ServiceAvailToElement and ServiceAffectsElement relate the BasicExecutionService to ComputerSystem. The association HostedDependency expresses the concept that an execution environment may be contained within another execution environment. For example, in a grid or distributed/virtualized environment the whole point for not explicitly stating which execution environment to use up front is to allow some client software, e.g. scheduler, orchestrator, provisioner, application, to determine where to place the activity (in which execution environment) based on the input activity document (that activity's environment/resource requirements).

Table of Contents
Hierarchy
Direct Known Subclasses
Class Qualifiers
Class Properties
Class Methods


Class Hierarchy

CIM_ManagedElement
   |
   +--CIM_ManagedSystemElement
   |
   +--CIM_LogicalElement
   |
   +--CIM_EnabledLogicalElement
   |
   +--CIM_Service
   |
   +--CIM_BasicExecutionService

Direct Known Subclasses

Class Qualifiers

NameData TypeValue
DescriptionstringThe basic execution service (BES)is a service to which clients can send requests to initiate, monitor, and manage computational activities and access information about the BES. A BasicExecutionService can act on one or more execution environments - modeled, profiled, and instantiated as a ComputerSystem. There is no requirement that a BasicExecutionService reside on the node of a ComputerSystem on which it acts. The associations ServiceAvailToElement and ServiceAffectsElement relate the BasicExecutionService to ComputerSystem. The association HostedDependency expresses the concept that an execution environment may be contained within another execution environment. For example, in a grid or distributed/virtualized environment the whole point for not explicitly stating which execution environment to use up front is to allow some client software, e.g. scheduler, orchestrator, provisioner, application, to determine where to place the activity (in which execution environment) based on the input activity document (that activity's environment/resource requirements).
Experimentalbooleantrue
UMLPackagePathstringCIM::Core::Grid
Versionstring2.16.0

Class Properties

Inherited Properties

NameData Type
Captionstring
CommunicationStatusuint16
CreationClassNamestring
Descriptionstring
DetailedStatusuint16
ElementNamestring
EnabledDefaultuint16
EnabledStateuint16
Generationuint64
HealthStateuint16
InstallDatedatetime
InstanceIDstring
LoSIDstring
LoSOrgIDstring
Namestring
OperatingStatusuint16
OtherEnabledStatestring
PrimaryOwnerContactstring
PrimaryOwnerNamestring
PrimaryStatusuint16
RequestedStateuint16
Startedboolean
StartModestring
Statusstring
SystemCreationClassNamestring
SystemNamestring
TimeOfLastStateChangedatetime
TransitioningToStateuint16
AvailableRequestedStatesuint16[]
OperationalStatusuint16[]
StatusDescriptionsstring[]

Class Methods

Inherited Class Methods

NameReturn Type
ChangeAffectedElementsAssignedSequenceuint32
RequestStateChangeuint32
StartServiceuint32
StopServiceuint32