wsrm

var (
	// CONFIGTYPE_ACCOUNTING:  This operation targets the accounting configuration.
	ConfigTypeAccounting ConfigType = 1
	// CONFIGTYPE_NOTIFICATION:  This operation targets the notification configuration.
	ConfigTypeNotification ConfigType = 2
	// CONFIGTYPE_CALENDARING:  This operation targets the calendar configuration.
	ConfigTypeCalendaring ConfigType = 3
)

var (
	// SYSTEM_EXCLUSION_LIST:  The exclusion list is system-defined.
	ExclusionlistTypeSystemExclusionList ExclusionlistType = 1
	// USER_EXCLUSION_LIST:  The exclusion list is user-defined.
	ExclusionlistTypeUserExclusionList ExclusionlistType = 2
	// DEFAULT_USER_EXCLUSION_LIST:  The exclusion list is the default user-defined exclusion
	// list.<9>
	ExclusionlistTypeDefaultUserExclusionList ExclusionlistType = 4
)

var (
	// OVERWRITE_IMPORT:  Specifies that objects of a given type SHOULD be removed prior
	// to importing more objects of that type.
	ImportTypeOverwriteImport ImportType = 1
	// IGNORE_EXISTING_IMPORT:  Specifies that the import of objects that conflict with
	// existing objects in the configuration SHOULD be ignored.
	ImportTypeIgnoreExistingImport ImportType = 2
	// OVERRIDE_EXISTING_IMPORT:  Specifies that the import of objects that conflict with
	// existing objects in the configuration SHOULD cause the existing objects to be deleted.
	ImportTypeOverrideExistingImport ImportType = 3
	// SMART_MERGE_RENAME_EXISTING_IMPORT:  Specifies that existing objects in the configuration
	// that conflict with imported objects SHOULD be renamed prior to importing.
	ImportTypeSmartMergeRenameExistingImport ImportType = 4
	// SMART_MERGE_RENAME_IMPORTED_IMPORT:  Specifies that imported objects that conflict
	// with existing objects in the configuration SHOULD be renamed prior to importing.
	ImportTypeSmartMergeRenameImportedImport ImportType = 5
)

var (
	// OVERWRITE_MG_MERGE_OPTION:  Specifies that the machine group configuration SHOULD
	// be overwritten.
	MachineGroupMergeOptionsOverwriteMGMergeOption MachineGroupMergeOptions = 1
	// OVERRIDE_MG_MERGE_OPTION:  Specifies that the machine group configuration SHOULD
	// be overridden. That means that if the same machine group name exists with the same
	// hierarchy then this (along with its children) SHOULD be replaced by the new machine
	// group node. Nonconflicting new nodes SHOULD be imported as is. Nonconflicting existing
	// nodes SHOULD remain as is.
	MachineGroupMergeOptionsOverrideMGMergeOption MachineGroupMergeOptions = 2
	// APPEND_MG_MERGE_OPTION:  Specifies that the machine group configuration SHOULD be
	// appended. This means that nonconflicting nodes SHOULD remain as is in the existing
	// configuration. Nonconflicting new nodes SHOULD be imported as is. Conflicting nodes
	// SHOULD not be modified.
	MachineGroupMergeOptionsAppendMGMergeOption MachineGroupMergeOptions = 3
	// SMART_MG_MERGE_OPTION:  Specifies that the machine group configuration SHOULD be
	// handled smartly. This means that nonconflicting nodes SHOULD remain as is in the
	// existing configuration. Nonconflicting new nodes SHOULD be imported as is. Conflicting
	// nodes SHOULD be merged in a way that the name of the imported node will be changed
	// to avoid name conflict. The new name of the conflicting object, which is being imported,
	// is built by appending its original name with the string "##@" followed by a number.
	// The numbers used are in the range 1-16384 and a number, once used, is not reused
	// until the object it was used in is either deleted or renamed. For example, an object
	// name "ObjectName" might become "ObjectName##@1" after using this option. This range
	// is sufficiently large and is not consumed completely because, in the WSRM configuration,
	// the maximum allowed number of objects of each type is 128. In addition, whenever
	// an object with a smart name is deleted or renamed, the number that was used in its
	// name is available for reuse.
	MachineGroupMergeOptionsSmartMGMergeOption MachineGroupMergeOptions = 4
)

var (
	// MANUAL_ACTIVE_POLICY:  The server is in manual active policy mode. In this mode,
	// WSRM manages the CPU and memory allocation for different processes according to the
	// PMCs that are defined by the current resource policy. The current resource policy
	// is selected using the SetCurrentPolicy method (section 3.2.4.7.12).
	ManagementTypeManualActivePolicy ManagementType = 1
	// CALENDAR_POLICY:  The server is in calendar mode. In this mode, a resource policy
	// is managing the CPU and memory allocation for different processes according to the
	// PMCs defined by the policy. The policy was set and the management mode was set to
	// calendar mode as a result of a calendar event, which is created and managed by IWRMCalendar
	// methods (section 3.2.4.4).
	ManagementTypeCalendarPolicy ManagementType = 2
	// PROFILING:  The server is in profiling mode. In this mode, WSRM does not manage
	// the CPU and memory allocation for processes. If accounting is enabled, process properties
	// of all running processes are logged into the accounting database.
	ManagementTypeProfiling ManagementType = 3
)

var (
	// OBJECT_SELECTION_CRITERIA:  The target object is a process matching criteria (PMC).
	ObjectTypeSelectionCriteria ObjectType = 1
	// OBJECT_POLICY:  The target object is a policy.
	ObjectTypePolicy ObjectType = 2
	// OBJECT_SCHEDULE:  The target object is a calendar or a schedule object.
	ObjectTypeSchedule ObjectType = 3
)

var (
	// RESTORE_LAST_GOOD_STATE:  This value targets the last saved good state of the WSRM
	// configuration, which is defined as a consistent set of WSRM objects. WSRM objects
	// are stored in the XML files after successful completion of any method call of this
	// protocol.
	RestoreModeLastGoodState RestoreMode = 1
	// RESTORE_EMPTY_FILES:  This value targets the initial state of the WSRM configuration
	// with which the product is shipped. This means that only the out-of-box policies,
	// empty calendars, and conditional policies will be used in the restored state of the
	// object.
	RestoreModeEmptyFiles RestoreMode = 2
)