< draft-moats-dmtf-application-ldap-00.txt   draft-moats-dmtf-application-ldap-01.txt >
Internet-Draft Ryan Moats Internet-Draft Ryan Moats
draft-moats-dmtf-application-ldap-00.txt Gerald Maziarski draft-moats-dmtf-application-ldap-01.txt Gerald Maziarski
Expires in six months AT&T Expires in six months AT&T
John Strassner John Strassner
cisco Systems cisco Systems
October 1999 December 1999
LDAP Schema for the DMTF Application CIM Model LDAP Schema for the DMTF Application CIM v2.1 Model
Filename: draft-moats-dmtf-application-ldap-00.txt Filename: draft-moats-dmtf-application-ldap-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 1, line 43 skipping to change at page 1, line 43
This draft presents a LDAP schema for the DMTF CIM Application model This draft presents a LDAP schema for the DMTF CIM Application model
version 2.2 [4]. version 2.2 [4].
1. Introduction 1. Introduction
This draft presents a LDAPv3 [1,2] schema for the DMTF CIM This draft presents a LDAPv3 [1,2] schema for the DMTF CIM
Application model. Associations are mapped using a combination of Application model. Associations are mapped using a combination of
auxiliary classes and DIT structure rules. Where auxiliary classes auxiliary classes and DIT structure rules. Where auxiliary classes
are used, name form and DIT content rules are specified. are used, name form and DIT content rules are specified.
2. Differences between this schema and the source CIM model This document is not a product of the DMTF, and represents the view
of the authors.
The only issue in mapping this model to LDAP is that there is an INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
attribute definition collision between this model and the system ModelDecember 1999
model. The attribute codeSet is defined with different syntax in
both models, so codeSet in this model has been renamed codeSetString. 2. Modifications to cimAssociationInstance
The core mapping [5] defined cimAssociationInstance as a helper
class. To support the auxiliary classes, the following classes
should be added to cimAssociationInstance's content rule:
cim22DirectorySpecificationFileAuxClass
cim22ActionSequenceAuxClass
cim22SoftwareFeatureSoftwareElementsAuxClass
cim22ToDirectorySpecificationAuxClass
cim22FromDirectorySpecificationAuxClass
cim22ToDirectoryActionAuxClass
cim22FromDirectoryActionAuxClass
cim22SoftwareFeatureSAPImplementationAuxClass
cim22ApplicationSystemSoftwareFeatureAuxClass
cim22InstalledSoftwareElementAuxClass
Also, the following structure rules defined here need to be added to
the structure rule for cimAssociationInstance: <sr25>, <sr26>,
<sr27>, <sr28>,
3. Class Definitions 3. Class Definitions
For efficiency in the LDAP representation, associations are specified For efficiency in the LDAP representation, associations are specified
as a combination of auxiliary classes and DIT structure rules. as a combination of auxiliary classes and DIT structure rules.
Attribute definitions for each class are presented with the object Attribute definitions for each class are presented with the object
class. Other definitions are also provided when necessary. class. Other definitions are also provided when necessary.
This approach minimizes the number of DN pointers stored in the This approach minimizes the number of DN pointers stored in the
schema, but some pointer dereferencing is necessary. While not schema, but some pointer dereferencing is necessary. While not
explicitly stated in the definitions below, we assume that all explicitly stated in the definitions below, we assume that all
attributes with DN support the matching rule defined in [3]. attributes with DN support the matching rule defined in [3].
Attribute names for DN pointers also follow the convention that a Attribute names for DN pointers also follow the convention that a
single pointer's name ends in "Ref", while an array of pointers' name single pointer's name ends in "Ref", while an array of pointers' name
ends in "Refs". ends in "Refs".
Note: all OIDs are place holders, and OIDs in definitions have been Note: all attribute, object class, and name form OIDs are place
replaced by names for clarity. holders, and syntax OIDs in definitions have been replaced by names
for clarity.
3.1 dmtfApplicationSystem 3.1 cim22ApplicationSystem
This class represents an application or a software system that This class represents an application or a software system that
supports a particular business function and that can be managed as supports a particular business function and that can be managed as
independent units. The dmtfSoftwareFeature class allows such a system independent units. The cim22SoftwareFeature class allows such a
to be decomposed into its functional pieces. The software features system to be decomposed into its functional pieces. The software
for a particular application or software system are located using features for a particular application or software system are located
dmtfApplicationSystemSoftwareFeatureAuxClass. using cim22ApplicationSystemSoftwareFeatureAuxClass.
( <oid-oc231> NAME 'dmtfApplicationSystem' INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
DESC 'represents an application or a software system that ModelDecember 1999
supports a particular business function and that can be
managed as independent units.' ( <oid-oc96> NAME 'cim22ApplicationSystem'
SUP dmtfSystem DESC 'The cim22ApplicationSystem class is used to represent an
application or a software system that supports a particular
business function and that can be managed as an independent
units. Such a system can be decomposed into its functional
components using the cim22SoftwareFeature class. The
software features for a particular application or software
system are located using the
cim22ApplicationSystemSoftwareFeature association.'
SUP cim22System
) )
3.2 dmtfSoftwareElement The following content rule specifies the auxiliary classes that may
be attached to cim22ApplicationSystem.
This class decomposes a dmtfSoftwareFeature object into a set of ( <oid-oc96> NAME 'cim22ApplicationSystemContentRule'
DESC 'The auxiliary classes that may be attached to
cim22ApplicationSystem'
AUX (cim22ApplicationSystemSoftwareFeatureAuxClass)
)
3.2 cim22SoftwareElement
This class decomposes a cim22SoftwareFeature object into a set of
individually manageable or deployable parts for a particular individually manageable or deployable parts for a particular
platform. A software element's underlying hardware architecture and platform. A software element's underlying hardware architecture and
operating system uniquely identifies its platform. As such, to operating system uniquely identifies its platform. As such, to
understand the details of how the functionality of a particular understand the details of how the functionality of a particular
software feature is provided on a particular platform, the software feature is provided on a particular platform, the
dmtfSoftwareElement objects referenced by cim22SoftwareElement objects referenced by
dmtfSoftwareFeatureSoftwareElementAuxClass are organized in disjoint cim22SoftwareFeatureSoftwareElementAuxClass are organized in disjoint
sets based on the targetOperatingSystem property. A sets based on the targetOperatingSystem property. A
dmtfSoftwareElement object captures the management details of a part cim22SoftwareElement object captures the management details of a part
or component in one of four states characterized by the or component in one of four states characterized by the
SoftwareElementState property. SoftwareElementState property.
( <oid-at552> NAME 'softwareElementState' ( <oid-at171> NAME 'cimSoftwareElementState'
DESC ' The SoftwareElementState is defined in this model to DESC ' The SoftwareElementState is defined in this model to
identify various states of a software elements life identify various states of a software elements life
cycle. - A software element in the deployable state cycle. - A software element in the deployable state
describes the details necessary to successful distribute describes the details necessary to successful distribute
it and the details (conditions and actions) required to it and the details (conditions and actions) required to
create a software element in the installable state (i.e, create a software element in the installable state (i.e,
the next state). - A software element in the installable the next state). - A software element in the installable
state describes the details necessary to successfully state describes the details necessary to successfully
install it and the details (conditions and actions install it and the details (conditions and actions
required to create a software element in the executable required to create a software element in the executable
state (i.e., the next state). - A software element in the state (i.e., the next state). - A software element in the
executable state describes the details necessary to
successfully start it and the details (conditions and INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
actions required to create a software element in the ModelDecember 1999
running state (i.e., the next state). - A software element
in the running state describes the details necessary to executable state describes the details necessary to
monitor and operate on a start element. May be used as an successfully start it and the details (conditions and
RDN. Allowed values are: "Deployable", "Installable", actions required to create a software element in the
"Executable", "Running".' running state (i.e., the next state). - A software element
in the running state describes the details necessary to
monitor and operate on a start element. May be used as an
RDN. Allowed values are: "Deployable", "Installable",
"Executable", "Running".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at553> NAME 'softwareElementID' ( <oid-at172> NAME 'cimSoftwareElementID'
DESC ' This is an identifier for this software element and is DESC ' This is an identifier for this software element and is
designed to be used with other keys to designed to be used with other keys to
create a unique representation of this SoftwareElement. create a unique representation of this SoftwareElement.
May be used as an RDN.' May be used as an RDN.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at554> NAME 'targetOperatingSystem' ( <oid-at173> NAME 'cimTargetOperatingSystem'
DESC ' The Target Operating System property allows the provider DESC ' The Target Operating System property allows the provider
to specify the operating system environment. The value of to specify the operating system environment. The value of
this property does not ensure binary executable. Two other this property does not ensure binary executable. Two other
pieces of information are needed. First, the version of pieces of information are needed. First, the version of
the OS needs to be specified. using the OS Version the OS needs to be specified. using the OS Version
Check. The second piece of information is the architecture Check. The second piece of information is the architecture
the OS runs on. This information is capture with the the OS runs on. This information is capture with the
ArchitectureCheck class. The combination of these ArchitectureCheck class. The combination of these
constructs allows the provider to clearly identify the constructs allows the provider to clearly identify the
level of OS required for a particular software element. level of OS required for a particular software element.
May be used as an RDN. Allowed values are: "Unknown", May be used as an RDN. Allowed values are: "Unknown",
"Other", "MACOS", "ATTUNIX", "DGUX", "DECNT", "Digital "Other", "MACOS", "ATTUNIX", "DGUX", "DECNT", "Digital
Unix", "OpenVMS", "HPUX", "AIX", "MVS", "OS400", "OS/2", Unix", "OpenVMS", "HPUX", "AIX", "MVS", "OS400", "OS/2",
"JavaVM", "MSDOS", "WIN3x", "WIN95", "WIN98", "WINNT", "JavaVM", "MSDOS", "WIN3x", "WIN95", "WIN98", "WINNT",
"WINCE", "NCR3000", "NetWare", "OSF", "DC/OS", "Reliant "WINCE", "NCR3000", "NetWare", "OSF", "DC/OS", "Reliant
UNIX", "SCO UnixWare", "SCO OpenServer", "Sequent", UNIX", "SCO UnixWare", "SCO OpenServer", "Sequent",
"IRIX", "Solaris", "SunOS", "U6000", "ASERIES", "IRIX", "Solaris", "SunOS", "U6000", "ASERIES",
"TandemNSK", "TandemNT", "BS2000", "LINUX", "Lynx", "TandemNSK", "TandemNT", "BS2000", "LINUX", "Lynx",
"XENIX", "VM/ESA", "Interactive UNIX", "BSDUNIX", "XENIX", "VM/ESA", "Interactive UNIX", "BSDUNIX",
"FreeBSD", "NetBSD", "GNU Hurd", "OS9", "MACH Kernel", "FreeBSD", "NetBSD", "GNU Hurd", "OS9", "MACH Kernel",
"Inferno", "QNX", "EPOC", "IxWorks", "VxWorks", "MiNT", "Inferno", "QNX", "EPOC", "IxWorks", "VxWorks", "MiNT",
"BeOS", "HP MPE", "NextStep", "PalmPilot", "Rhapsody".' "BeOS", "HP MPE", "NextStep", "PalmPilot", "Rhapsody".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at555> NAME 'otherTargetOS' ( <oid-at174> NAME 'cimOtherTargetOS'
DESC ' The otherTargetOS property records the manufacturer and DESC ' The otherTargetOS property records the manufacturer and
operating system type for a software element when the operating system type for a software element when the
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
targetOperatingSystem property has a value of 1 ("Other") targetOperatingSystem property has a value of 1 ("Other")
For all other values of TargetOperatingSystem, the For all other values of TargetOperatingSystem, the
OtherTargetOS property is to be NULL.' OtherTargetOS property is to be NULL.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at556> NAME 'buildNumber' ( <oid-at175> NAME 'cimBuildNumber'
DESC 'The internal identifier for this compilation of this DESC 'The internal identifier for this compilation of this
software element.' software element.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at442> NAME 'codeSetString' ( <oid-at176> NAME 'cimCodeSet'
DESC 'Array defining the character sets' DESC 'Array defining the character sets'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at557> NAME 'identificationCode' ( <oid-at177> NAME 'cimIdentificationCode'
DESC ' The value of this property is the manufacturer's DESC ' The value of this property is the manufacturer's
identifier for this software element. Often this will be a identifier for this software element. Often this will be a
stock keeping unit (SKU) or a part number.' stock keeping unit (SKU) or a part number.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at558> NAME 'languageEdition' ( <oid-at178> NAME 'cimLanguageEdition'
DESC 'The value of this property identifies the language edition DESC 'The value of this property identifies the language edition
of this software element. The language codes defined in ISO of this software element. The language codes defined in ISO
639 should be used. Where the software element represents 639 should be used. Where the software element represents
multi-lingual or international version of a product, the multi-lingual or international version of a product, the
string multilingual should be used.' string multilingual should be used.'
SYNTAX string{32} SINGLE-VALUE SYNTAX string{32} SINGLE-VALUE
) )
( <oid-oc232> NAME 'dmtfSoftwareElement'
DESC 'decomposes a dmtfSoftwareFeature object into a set of ( <oid-oc97> NAME 'cim22SoftwareElement'
individually manageable or deployable parts for a DESC 'The cim22SoftwareElement class is used to decompose a
particular platform.' cim22SoftwareFeature object into a set of individually
SUP dmtfLogicalElement manageable or deployable parts for a particular platform. A
MUST (name $ version $ softwareElementState $ softwareElementID $ software element's platform is uniquely identified by its
targetOperatingSystem $ otherTargetOS $ manufacturer $ underlying hardware architecture and operating system (for
buildNumber $ serialNumber $ codeSetString $ identificationCode $ example Sun Solaris on Sun Sparc or Windows NT on
languageEdition) Intel). As such, to understand the details of how the
functionality of a particular software feature is provided
on a particular platform, the cim22SoftwareElement objects
referenced by cim22SoftwareFeatureSoftwareElement
associations are organized in disjoint sets based on the
TargetOperatingSystem property. A cim22SoftwareElement
object captures the management details of a part or
component in one of four states characterized by the
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
SoftwareElementState property.'
SUP cim22LogicalElement
MAY (cimName $ cimVersion $ cimSoftwareElementState $
cimSoftwareElementID $ cimTargetOperatingSystem $
cimOtherTargetOS $ cimManufacturer $ cimBuildNumber $
cimSerialNumber $ cimCodeSet $ cimIdentificationCode $
cimLanguageEdition)
) )
3.3 dmtfSoftwareFeature ( <oid-nf27> NAME 'cim22SoftwareElementNameForm'
OC cim22SoftwareElement
MUST (orderedCimModelPath)
)
( <sr27> NAME 'cim22SoftwareElementStructureRule'
FORM cim22SoftwareElementNameForm
)
The following content rule specifies the auxiliary classes that may
be attached to cim22SoftwareElement.
( <oid-oc97> NAME 'cim22SoftwareElementContentRule'
DESC 'The auxiliary classes that may be attached to
cim22SoftwareElement'
AUX (cim22SoftwareFeatureSoftwareElementsAuxClass $
cim22InstalledSoftwareElementAuxClass $
cim22LogicalIdentityAuxClass $ cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
)
3.3 cim22SoftwareFeature
This class defines a particular function or capability of a product This class defines a particular function or capability of a product
or application system. It captures the level of granularity that is or application system. It captures the level of granularity that is
significant to a consumer or user of a product rather than the units significant to a consumer or user of a product rather than the units
that reflect how the product is built or packaged, which is captured that reflect how the product is built or packaged, which is captured
using the dmtfSoftwareElement class. When a software feature can using the cim22SoftwareElement class. When a software feature can
exist on multiple platforms or operating systems (for example, a exist on multiple platforms or operating systems (for example, a
client component of a three tiered client/server applications might client component of a three tiered client/server applications might
run on Solaris, Windows NT, and Windows 95), a software feature is a run on Solaris, Windows NT, and Windows 95), a software feature is a
collection of all the software elements for these different collection of all the software elements for these different
platforms. Here, the users of the model must be aware of this since platforms. Here, the users of the model must be aware of this since
typically they will be interested in a sub-collection of the software typically they will be interested in a sub-collection of the software
elements required for a particular platform. Software Features are elements required for a particular platform. Software Features are
always defined in the context of a dmtfProduct class using DIT always defined in the context of a cim22Product class using DIT
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
structure rules since features are delivered through products. structure rules since features are delivered through products.
Optionally, software features from one or more products can be Optionally, software features from one or more products can be
organized into application systems using the organized into application systems using the
dmtfApplicationSystemSoftwareFeatureAuxClass object. it reuses cim22ApplicationSystemSoftwareFeatureAuxClass object.
identifyingNumber, vendor, version, and name and defines productName.
( <oid-at559> NAME 'productName'
DESC 'Commonly used Product name. May be used as an RDN.'
SYNTAX string{256} SINGLE-VALUE
)
( <oid-oc233> NAME 'dmtfSoftwareFeature'
DESC 'defines a particular function or capability of a product or
application system.'
SUP dmtfLogicalElement
MUST (identifyingNumber $ productName $ vendor $ version $ name)
)
While a variety of attributes may be used as RDN, the following
structural rules are recommended.
( 28 NAME 'dmtfSoftwareFeatureStructureRule1'
FORM dmtfSoftwareFeatureNameForm1
SUP 30 31
)
( <oid-nf28> NAME 'dmtfSoftwareFeatureNameForm1' ( <oid-at179> NAME 'cimProductName'
OC dmtfSoftwareFeature DESC 'Commonly used Product name'
MUST (name) SYNTAX string SINGLE-VALUE
) )
( 29 NAME 'dmtfSoftwareFeatureStructureRule2' ( <oid-oc98> NAME 'cim22SoftwareFeature'
FORM dmtfSoftwareFeatureNameForm2 DESC 'The cim22SoftwareFeature class defines a particular function
SUP 30 31 or capability of a product or application system. This
class in intended to capture the level of granularity that
is meaningful to a consumer or user of a product rather
than the units that reflect how the product is built or
packaged. The latter detailed is captured using a
cim22SoftwareElement class. When a software feature can
exist on multiple platforms or operating systems (for
example, a client component of a three tiered client/server
applications might run on Solaris, Windows NT, and Windows
95), a software feature is a collection of all the software
elements for these different platforms. In this case, the
users of the model must be aware of this situation since
typically they will be interested in a sub-collection
of the software elements required for a particular
platform. Software Features are always defined in the
context of a cim22Product class using the
cim22ProductSoftwareFeature association since features are
delivered through products. Optionally, software features
from one or more products can be organized into application
systems using the cim22ApplicationSystemSoftwareFeature
association.'
SUP cim22LogicalElement
MUST (cimIdentifyingNumber $ cimProductName $ cimVendor $
cimVersion)
MAY (cimName)
) )
( <oid-nf29> NAME 'dmtfSoftwareFeatureNameForm2' ( <oid-nf28> NAME 'cim22SoftwareFeatureNameForm'
OC dmtfSoftwareFeature OC cim22SoftwareFeature
MUST (identifyingNumber) MUST (orderedCimModelPath)
) )
( 30 NAME 'dmtfProductStructureRule1' ( <sr28> NAME 'cim22SoftwareFeatureStructureRule'
FORM dmtfProductNameForm1 FORM cim22SoftwareFeatureNameForm
SUP <sr6>
) )
( <oid-nf30> NAME 'dmtfProductNameForm1' INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
OC dmtfProduct ModelDecember 1999
MUST (name)
)
( 31 NAME 'dmtfProductStructureRule2' The following content rule specifies the auxiliary classes that may
FORM dmtfProductNameForm2 be attached to cim22SoftwareFeature.
)
( <oid-nf31> NAME 'dmtfProductNameForm2' ( <oid-oc98> NAME 'cim22SoftwareFeatureContentRule'
OC dmtfProduct DESC 'The auxiliary classes that may be attached to
MUST (identifyingNumber) cim22SoftwareFeature'
AUX (cim22SoftwareFeatureSoftwareElementsAuxClass $
cim22SoftwareFeatureServiceImplementationAuxClass $
cim22SoftwareFeatureSAPImplementationAuxClass $
cim22ApplicationSystemSoftwareFeatureAuxClass $
cim22LogicalIdentityAuxClass $ cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
) )
3.4 dmtfCheck 3.4 cim22Check
A Check is a condition or characteristic that is expected to be true A Check is a condition or characteristic that is expected to be true
in an environment defined or scoped by an instance of a in an environment defined or scoped by an instance of a
dmtfComputerSystem. They are associated with a particular software cim22ComputerSystem. They are associated with a particular software
element and are organized into one of two groups using the Phase element and are organized into one of two groups using the Phase
property. Conditions that are expected to be satisfied when a property. Conditions that are expected to be satisfied when a
software element is in a particular environment are known as in-state software element is in a particular environment are known as in-state
conditions. Conditions that need to be satisfied to transition the conditions. Conditions that need to be satisfied to transition the
current software element to its next state are known as next-state current software element to its next state are known as next-state
conditions. conditions.
it reuses name, version, softwareElementState, softwareElementID, ( <oid-at180> NAME 'cimCheckID'
targetOperatingSystem, description, and caption. It also defines DESC 'An identifier used in conjunction with other keys to
checkID, phase and checkMode. uniquely identify the check'
SYNTAX string SINGLE-VALUE
( <oid-at560> NAME 'checkID'
DESC 'An identifier used with other keys to
uniquely identify the check. May be used as an RDN.'
SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at561> NAME 'checkMode' ( <oid-at181> NAME 'cimCheckMode'
DESC 'The CheckMode property is used to show whether the DESC 'The CheckMode property is used to indicate whether the
condition is expected to exist or not exist in the condition is expected to exist or not exist in the
environment. When the value is True, the condition is environment. When the value is True, the condition is
expected to exist (e.g., a file is expected to be on a expected to exist (e.g., a file is expected to be on a
system) so invoke() is expected to return True. When the system) so invoke() is expected to return True. When the
value is False, the condition is not expect to exist (e.g., value is False, the condition is not expect to exist (e.g.,
a file is not to be on a system) so invoke is expected to a file is not to be on a system) so invoke is expected to
return false.' return false'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at562> NAME 'phase' ( <oid-oc99> NAME 'cim22Check'
DESC ' The Phase property shows whether the referenced check
is an in-state check or a next-state check. Allowed
values are: "In-State", "Next-State".'
SYNTAX integer SINGLE-VALUE
)
( <oid-oc234> NAME 'dmtfCheck'
DESC 'A Check is a condition or characteristic that is expected
to be true in an environment defined or scoped by an
instance of a dmtfComputerSystem.'
SUP top ABSTRACT
MUST (name $ version $ softwareElementState $ softwareElementID $
targetOperatingSystem $ checkID $ description $ caption $
checkMode)
)
While various attributes of dmtfCheck may be used as RDNs, the
following structural rules are recommended.
( 32 NAME 'dmtfCheckStructureRule1'
FORM dmtfCheckNameForm1
SUP 34 35
)
( <oid-nf32> NAME 'dmtfCheckNameForm1'
OC dmtfCheck
MUST (name)
)
( 33 NAME 'dmtfCheckStructureRule1'
FORM dmtfCheckNameForm1
SUP 34 35
)
( <oid-nf33> NAME 'dmtfCheckNameForm1'
OC dmtfCheck
MUST (checkID)
)
( 34 NAME 'dmtfSoftwareElementStructureRule1' INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
FORM dmtfSoftwareElementNameForm1 ModelDecember 1999
)
( <oid-nf34> NAME 'dmtfSoftwareElementNameForm1' DESC 'A Check is a condition or characteristic that is expected
OC dmtfSoftwareElement to be true in an environment defined or scoped by an
MUST (name) instance of a cim22ComputerSystem. The checks associated
with a particular software element are organized into one
of two groups using the Phase property of the
cim22SoftwareElementChecks association. Conditions that are
expected to be satisfied when a software element is in a
particular environment are known as in-state
conditions. Conditions that need to be satisfied in order
to transition the current software element to its next
state are known as next-state conditions A
cim22ComputerSystem object represents the environment in
which cim22SoftwareElements are already installed or in
which cim22SoftwareElements will be installed. For the case
in which a software element is already installed, the
cim22InstalledSoftwareElement association is used to
identify the cim22ComputerSystem object that represents the
"environment". When a software elements is being
distributed and installed on a different computer system,
the cim22ComputerSystem object for the targeted system is
the environment.'
SUP top
MUST (orderedCimModelPath)
MAY (cimName $ cimVersion $ cimSoftwareElementState $
cimSoftwareElementID $ cimTargetOperatingSystem $
cimCheckID $ cimDescription $ cimCaption $ cimCheckMode)
) )
( 35 NAME 'dmtfSoftwareElementStructureRule2' ( <oid-nf25> NAME 'cim22CheckNameForm'
FORM dmtfSoftwareElementNameForm2 OC cim22Check
MUST (orderedCimModelPath)
) )
( <oid-nf35> NAME 'dmtfSoftwareElementNameForm2' ( <sr25> NAME 'cim22CheckStructureRule'
OC dmtfSoftwareElement FORM cim22CheckNameForm
MUST (softwareElementID) SUP <sr27>
) )
3.5 dmtfDirectorySpecification 3.5 cim22DirectorySpecification
A directory specification captures the major directory structure of a A directory specification captures the major directory structure of a
software element and organizes the files of a software element into software element and organizes the files of a software element into
manageable units that can be relocated on a computer system. manageable units that can be relocated on a computer system.
it defines the attributes directoryType, directoryPath. ( <oid-at182> NAME 'cimDirectoryType'
( <oid-at563> NAME 'directoryType'
DESC 'The DirectoryType property characterizes the type of DESC 'The DirectoryType property characterizes the type of
directory being described. Allowed values are: "Product directory being described.'
base directory", "Product executable directory", "Product
library directory", "Product configuration directory",
"Product include directory", "Product working directory",
"Product log directory", "Shared base directory", "Shared
executable directory", "Shared library directory", "Shared
include directory", "System base directory", "System
executable directory", "System library directory", "System
configuration directory", "System include directory",
"System log directory", "Other".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
) )
( <oid-at564> NAME 'directoryPath' ( <oid-at183> NAME 'cimDirectoryPath'
DESC 'The DirectoryPath property is used to capture the name of a DESC 'The DirectoryPath property is used to capture the name of a
directory. The value supplied by an application provider is directory. The value supplied by an application provider is
actually a default or recommended path name. The value can actually a default or recommended path name. The value can
be changed for a particular environment.' be changed for a particular environment.'
SYNTAX string{1024} SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc235> NAME 'dmtfDirectorySpecification' ( <oid-oc100> NAME 'cim22DirectorySpecification'
DESC 'The dmtfDirectorySpecification class captures the major DESC 'The cim22DirectorySpecification class captures the major
directory structure of a software element. it is directory structure of a software element. This class is
used to organize the files of a software element into used to organize the files of a software element into
manageable units that can be relocated on a computer manageable units that can be relocated on a computer
system.' system.'
SUP dmtfCheck SUP cim22Check
MUST (directoryType $ directoryPath) MAY (cimDirectoryType $ cimDirectoryPath)
) )
3.6 dmtfArchitectureCheck The following content rule specifies the auxiliary classes that may
be attached to cim22DirectorySpecification.
( <oid-oc100> NAME 'cim22DirectorySpecificationContentRule'
DESC 'The auxiliary classes that may be attached to
cim22DirectorySpecification'
AUX (cim22DirectorySpecificationFileAuxClass $
cim22ToDirectorySpecificationAuxClass $
cim22FromDirectorySpecificationAuxClass)
)
3.6 cim22ArchitectureCheck
Architecture checks specify the hardware platform a software element Architecture checks specify the hardware platform a software element
can run on. Its attributes are compared with the corresponding can run on. Its attributes are compared with the corresponding
processor attributes. As long as there is at least one processor processor attributes. As long as there is at least one processor
that satisfies the details of the condition, the check is satisfied. that satisfies the details of the condition, the check is satisfied.
( <oid-at565> NAME 'architectureType' ( <oid-at184> NAME 'cimArchitectureType'
DESC 'The ArchitectureType property identifies a particular type DESC 'The ArchitectureType property identifies a particular type
of architecture or architecture family that is required to of architecture or architecture family that is required to
properly execute a particular software element. The intent properly execute a particular software element. The intent
is to capture the details about the machine instructions is to capture the details about the machine instructions
exploited by the executables of the software element.' exploited by the executables of the software element.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc236> NAME 'dmtfArchitectureCheck' ( <oid-oc101> NAME 'cim22ArchitectureCheck'
DESC 'specifies the hardware platform a software element can run
on.' INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
SUP dmtfCheck ModelDecember 1999
MUST (architectureType)
DESC 'The Architecture Check specifies the hardware platform a
software element can run on. The details of this checks are
compared with the corresponding details found in a
cim22Processor object referenced by a
cim22ComputerSystemProcessor association for the
cim22ComputerSystem object that describes the
environment. As long as there is at least one cim22Processor
that satisfies the details of the condition, the check is
satisfied. In other words, all the processors on the
relevant computer system do not need to satisfy the
condition. There needs to be at least one.'
SUP cim22Check
MAY (cimArchitectureType)
) )
3.7 dmtfMemoryCheck 3.7 cim22MemoryCheck
Memory checks specifiy the minimum amount of memory that a system Memory checks specify the minimum amount of memory that a system must
must have available. When an operating system has more free physical have available. When an operating system has more free physical
memory than the value specified in MemorySize, the condition is memory than the value specified in MemorySize, the condition is
satisfied. satisfied.
( <oid-at566> NAME 'memorySize' ( <oid-at185> NAME 'cimMemorySize'
DESC 'The amount of memory that needs to exist on a computer DESC 'The amount of memory that needs to exist on a computer
system for a software element to executing properly.' system for a software element to executing properly.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc237> NAME 'dmtfMemoryCheck' ( <oid-oc102> NAME 'cim22MemoryCheck'
DESC 'specifies a condition for the minimum amount of memory that DESC 'The MemoryCheck specifies a condition for the minimum
needs to be available on a system.' amount of memory that needs to be available on a
SUP dmtfCheck system. The amount is specified in the MemorySize
MUST (memorySize) property. The details of this checks are compared with the
value of the FreePhysicalMemory property of the
cim22OperatingSystem object referenced by an InstalledOS
association for the cim22ComputerSystem object that
describes the environment. When the value of
FreePhyscalMemory property is greater than or equal to the
value specified in MemorySize, the condition is satisfied.'
SUP cim22Check
MAY (cimMemorySize)
) )
3.8 dmtfDiskSpaceCheck 3.8 cim22DiskSpaceCheck
Disk space checks specify the minimum amount of disk space that a Disk space checks specify the minimum amount of disk space that a
system must have available. When a file system have more available system must have available. When a file system have more available
space than the value specified in availableDiskSpace, the condition space than the value specified in availableDiskSpace, the condition
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
is satisfied. is satisfied.
( <oid-at567> NAME 'availableDiskSpace' ( <oid-at186> NAME 'cimAvailableDiskSpace'
DESC 'Amount of disk space needed.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc238> NAME 'dmtfDiskSpaceCheck' ( <oid-oc103> NAME 'cim22DiskSpaceCheck'
DESC 'specifies the amount of disk space the needs to be DESC 'The Disk Space Check the amount of disk space the needs to
available on the system.' be available on the system. The amount is specified in the
SUP dmtfCheck AvailableDiskSpace property. The details of this checks are
MUST (availableDiskSpace) compared with the value of the AvailableSpace property of
the cim22FileSystem object associated with the
cim22ComputerSystem object that describes the
environment. When the value of AvailableSpace property is
greater than or equal to the value specified in
AvailableDiskSpace, the condition is satisfied.'
SUP cim22Check
MAY (cimAvailableDiskSpace)
) )
3.9 dmtfSwapSpaceCheck 3.9 cim22SwapSpaceCheck
Swap space checks specify the minimum amount of swap space that a Swap space checks specify the minimum amount of swap space that a
system must have available. When a system have more swap space system must have available. When a system have more swap space
available that the value in swapSpaceSize, the condition is available that the value in swapSpaceSize, the condition is
satisfied. satisfied.
( <oid-at568> NAME 'swapSpaceSize' ( <oid-at187> NAME 'cimSwapSpaceSize'
DESC 'specifies the minimum number of Kilo bytes of swap space DESC 'The SwapSpaceSize property specifies the minimum number of
that needs to be available on the target system.' Kilo bytes of swap space that needs to be available on the
target system.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc239> NAME 'dmtfSwapSpaceCheck' ( <oid-oc104> NAME 'cim22SwapSpaceCheck'
DESC 'specifies the amount of swap space that needs to be DESC 'The Swap Space Check specifies the amount of swap space
available on the system.' that needs to be available on the system. The amount is
SUP dmtfCheck specified in the SwapSpaceSize property. The details of
MUST (swapSpaceSize) this checks are compared with the corresponding details
found in a cim22OperatingSystem object referenced by
InstalledOS association for the cim22ComputerSystem object
describing the environment. When the value of
TotalSwapSpaceSize property is greater than or equal to the
value specified in SwapSpacesize, the condition is
satisfied.'
SUP cim22Check
MAY (cimSwapSpaceSize)
) )
3.10 dmtfOSVersionCheck INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
3.10 cim22OSVersionCheck
This class specifies the versions of the OS that can support this This class specifies the versions of the OS that can support this
software element. This check can be for a specific, minimum, maximum software element. This check can be for a specific, minimum, maximum
or a range of releases of an OS. To specify a specific version the or a range of releases of an OS. To specify a specific version the
minimum and maximum versions must be the same. To specify a minimum, minimum and maximum versions must be the same. To specify a minimum,
the minimum version needs only be specified. To specify a maximum the minimum version needs only be specified. To specify a maximum
version, the maximum version needs only be specified. To specify a version, the maximum version needs only be specified. To specify a
range both minimum and maximum version need to be specified. The range both minimum and maximum version need to be specified.
targetOperatingSystem attributes of the owning SoftwareElement
specifies the type of operating system. The details of this checks
are compared with the corresponding details found in a
dmtfOperatingSystem object referenced by dmtfInstalledOSAuxClass. As
long as there is at least one dmtfOperatingSystem object that
satisfies the details of the condition, the check is satisfied. Also,
note the the oSType attribute property of the dmtfOperatingSystem
class must match the type of the targetOperatingSystem property.
( <oid-at569> NAME 'minimumVersion' ( <oid-at188> NAME 'cimMinimumVersion'
DESC 'Minimum version of required operating system. The value is DESC 'Minimum version of required operating system. The value is
encoded as <major>.<minor>.<revision> or encoded as <major>.<minor>.<revision> or
<major>.<minor><letter revision>.' <major>.<minor><letter revision> '
SYNTAX string{64} SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at570> NAME 'maximumVersion' ( <oid-at189> NAME 'cimMaximumVersion'
DESC 'Maximum version of required operating system. The value is DESC 'Maximum version of required operating system. The value is
encoded as <major>.<minor>.<revision> or encoded as <major>.<minor>.<revision> or
<major>.<minor><letter revision>.' <major>.<minor><letter revision> '
SYNTAX string{64} SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc240> NAME 'dmtfOSVersionCheck' ( <oid-oc105> NAME 'cim22OSVersionCheck'
DESC 'specifies the versions of the OS that can support this DESC 'The OS Version Check class specifies the versions of the OS
software element.' that can support this software element. This check can be
SUP dmtfCheck for a specific, minimum, maximum or a range of releases of
MUST (minimumVersion $ maximumVersion) an OS. To specify a specific version the minimum and
maximum versions must be the same. To specify a minimum,
the minimum version needs only be specified. To specify a
maximum version, the maximum version needs only be
specified. To specify a range both minimum and maximum
version need to be specified. The type of operating system
is specified in the TargetOperatingSystem property of the
owning SoftwareElement. The details of this checks are
compared with the corresponding details found in a
cim22OperatingSystem object referenced by InstalledOS
association for the cim22ComputerSystem object that
describes the environment. As long as there is at least one
cim22OperatingSystem that satisfies the details of the
condition, the check is satisfied. In other words, all the
operating systems on the relevant computer system do not
need to satisfy the condition. There needs to be at least
one. Also, note the the OSType property of the
cim22OperatingSystem class must match the type of the
TargetOperatingSystem property.'
SUP cim22Check
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
MAY (cimMinimumVersion $ cimMaximumVersion)
) )
3.11 dmtfSoftwareElementVersionCheck 3.11 cim22SoftwareElementVersionCheck
This class specifies a type of software element that must exist in This class specifies a type of software element that must exist in
the environment. This check can be for a specific, minimum, maximum the environment. This check can be for a specific, minimum, maximum
or a range of versions. To specify a specific version the lower and or a range of versions. To specify a specific version the lower and
upper versions must be the same. To specify a minimum the lower upper versions must be the same. To specify a minimum the lower
version needs only be specified. To specify a maximum version the version needs only be specified. To specify a maximum version the
upper version needs only be specified. To specify a range both upper upper version needs only be specified. To specify a range both upper
and lower version need to be specified. The details of this checks and lower version need to be specified. The details of this checks
are compared with the corresponding details found in a are compared with the corresponding details found in a
dmtfSoftwareElement object referenced by an InstalledSoftwareElement cim22SoftwareElement object referenced by an InstalledSoftwareElement
association for the dmtfComputerSystem object. As long as there is at association for the cim22ComputerSystem object. As long as there is
least one dmtfSoftwareElement that satisfies the details of the at least one cim22SoftwareElement that satisfies the details of the
condition, the check is satisfied. condition, the check is satisfied.
( <oid-at571> NAME 'softwareElementName' ( <oid-at190> NAME 'cimSoftwareElementName'
DESC 'The name of the software element being checked.' DESC 'The name of the software element being checked.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at572> NAME 'lowerSoftwareElementVersion' ( <oid-at191> NAME 'cimLowerSoftwareElementVersion'
DESC 'The minimum version of a software elements being checked.' DESC 'The minimum version of a software elements being checked.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at573> NAME 'upperSoftwareElementVersion' ( <oid-at192> NAME 'cimUpperSoftwareElementVersion'
DESC 'The maximum version of a software elements being checked.' DESC 'The maximum version of a software elements being checked.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at574> NAME 'softwareElementStateDesired' ( <oid-at193> NAME 'cimSoftwareElementStateDesired'
DESC 'The state of the software element being checked. Allowed DESC 'The state of the software element being checked.'
values are: "Deployable", "Installable", "Executable",
"Running".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at575> NAME 'targetOperatingSystemDesired' ( <oid-at194> NAME 'cimTargetOperatingSystemDesired'
DESC 'The target operating system of the software element being DESC 'The target operating system of the software element being
checked. Allowed values are: "Unknown", "Other", "MACOS", checked.'
"ATTUNIX", "DGUX", "DECNT", "Digital Unix", "OpenVMS",
"HPUX", "AIX", "MVS", "OS400", "OS/2", "JavaVM", "MSDOS",
"WIN3x", "WIN95", "WIN98", "WINNT", "WINCE", "NCR3000",
"NetWare", "OSF", "DC/OS", "Reliant UNIX", "SCO UnixWare",
"SCO OpenServer", "Sequent", "IRIX", "Solaris", "SunOS",
"U6000", "ASERIES", "TandemNSK", "TandemNT", "BS2000",
"LINUX", "Lynx", "XENIX", "VM/ESA", "Interactive UNIX",
"BSDUNIX", "FreeBSD", "NetBSD", "GNU Hurd", "OS9", "MACH
Kernel", "Inferno", "QNX", "EPOC", "IxWorks", "VxWorks",
"MiNT", "BeOS", "HP MPE", "NextStep", "PalmPilot",
"Rhapsody".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc241> NAME 'dmtfSoftwareElementVersionCheck' ( <oid-oc106> NAME 'cim22SoftwareElementVersionCheck'
DESC 'specifies a type of software element that must exist in the DESC 'The Software Element Version Check class specifies a type
environment.' of software element that must exist in the
SUP dmtfCheck environment. This check can be for a specific, minimum,
MUST (softwareElementName $ lowerSoftwareElementVersion $
upperSoftwareElementVersion $ softwareElementStateDesired $ INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
targetOperatingSystemDesired) ModelDecember 1999
maximum or a range of versions. To specify a specific
version the lower and upper versions must be the same. To
specify a minimum the lower version needs only be
specified. To specify a maximum version the upper version
needs only be specified. To specify a range both upper and
lower version need to be specified. The details of this
checks are compared with the corresponding details found in
a cim22SoftwareElement object referenced by an
InstalledSoftwareElement association for the
cim22ComputerSystem object. As long as there is at least one
cim22SoftwareElement that satisfies the details of the
condition, the check is satisfied. In other words, all the
software elements on the relevant computer system do not
need to satisfy the condition. There needs to be at least
one.'
SUP cim22Check
MAY (cimSoftwareElementName $ cimLowerSoftwareElementVersion $
cimUpperSoftwareElementVersion $
cimSoftwareElementStateDesired $
cimTargetOperatingSystemDesired)
) )
3.12 dmtfFileSpecification 3.12 cim22FileSpecification
A dmtfFileSpecification object identifies a file that is either to be A cim22FileSpecification object identifies a file that is either to
on or off the system. DmtfDirectorySpecificationFileAuxClass be on or off the system. cim22DirectorySpecificationFileAuxClass
identifies the directory the file is to be located in. identifies the directory the file is to be located in.
( <oid-at576> NAME 'fileName' ( <oid-at195> NAME 'cimFileName'
DESC 'Either the name of the file or the name of the file with a DESC 'Either the name of the file or the name of the file with a
directory prefix.' directory prefix.'
SYNTAX string{1024} SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at577> NAME 'createTimeStamp' ( <oid-at196> NAME 'cimCreateTimeStamp'
DESC 'The creation date and time of the file.' DESC 'The creation date and time of the file.'
SYNTAX generalizedTime SINGLE-VALUE SYNTAX generalizedTime SINGLE-VALUE
) )
( <oid-at578> NAME 'fileSize' ( <oid-at197> NAME 'cimFileSize'
DESC 'Size of the File in bytes..'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at579> NAME 'checkSum' ( <oid-at198> NAME 'cimCheckSum'
DESC 'The File Checksum property is a checksum calculated as the DESC 'The File Checksum property is a checksum calculated as the
16-bit sum of the first 32 bytes of the file.' 16-bit sum of the first 32 bytes of the file.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at580> NAME 'cRC1' INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
DESC 'The File CRC 1 property is the CRC value calculated using ModelDecember 1999
the middle 512K bytes.'
( <oid-at199> NAME 'cimCRC1'
DESC 'The File CRC 1 property is the CRC value calculated using
the middle 512K bytes.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at581> NAME 'cRC2' ( <oid-at200> NAME 'cimCRC2'
DESC 'The File CRC 2 is the CRC value for the middle 512K bytes DESC 'The File CRC 2 is the CRC value for the middle 512K bytes
with a offset modulo 3 to the start of the file of zero.' with a offset modulo 3 to the start of the file of zero.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at582> NAME 'mD5Checksum' ( <oid-at201> NAME 'cimMD5Checksum'
DESC 'The MD5 checksum of the file.' DESC 'The MD5 algorithm is a well-known algorithm for computing a
128-bit checksum for any file or object. The likelihood of
two different files producing the same MD5 checksum is very
small (about 1 in 2^64), and as such, the MD5 checksum of a
file can be used to construct a reliable content identifier
that is very likely to uniquely identify the file. The
reverse is also true. If two files have the same MD5
checksum, it is very likely that the files are
identical. For purposes of MOF specification of the MD5
property, the MD5 algorithm always generates a 32 character
string. For example: The string abcdefghijklmnopqrstuvwxyz
generates the string c3fcd3d76192e4007dfb496cca67e13b. See
http://www. rsa.com/pub/rfc1321.txt for details on the
implementation of the MD5 algorithm.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc242> NAME 'dmtfFileSpecification' ( <oid-oc107> NAME 'cim22FileSpecification'
DESC 'identifies a file that is either to be on or off the system.' DESC 'A cim22FileSpecification identifies a file that is either to
SUP dmtfCheck be on or off the system. The file is to be located in the
MUST (fileName $ createTimeStamp $ fileSize $ checkSum $ cRC1 $ directory identified by the DirectorySpecificationFile
cRC2 $ mD5Checksum) associations. When the invoke() method is used, it is
expected that it will use the combination of information
provided to check for the file existence. Therefore, any of
the properties with a NULL value are not checked. So, if
only the Name and the MD5 properties have values, they are
the only ones consider by the invoke() method.'
SUP cim22Check
MAY (cimFileName $ cimCreateTimeStamp $ cimFileSize $
cimCheckSum $ cimCRC1 $ cimCRC2 $ cimMD5Checksum)
) )
3.13 dmtfVersionCompatibilityCheck The following content rule specifies the auxiliary classes that may
be attached to cim22FileSpecification.
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
( <oid-oc107> NAME 'cim22FileSpecificationContentRule'
DESC 'The auxiliary classes that may be attached to
cim22FileSpecification'
AUX (cim22DirectorySpecificationFileAuxClass)
)
3.13 cim22VersionCompatibilityCheck
This class specifies whether it is permissible to create the next This class specifies whether it is permissible to create the next
state of a software element. It defines the attributes state of a software element.
allowDownVersion, allowMultipleVersions, and reinstall.
( <oid-at583> NAME 'allowDownVersion' ( <oid-at202> NAME 'cimAllowDownVersion'
DESC 'The AllowDownVersion property shows that this software DESC 'The AllowDownVersion property indicates that this software
element can transition to its next state even if a higher element can transition to its next state even if a higher
or latter version of the software element already exists in or later version of the software element already exists in
the environment.' the environment.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at584> NAME 'allowMultipleVersions' ( <oid-at203> NAME 'cimAllowMultipleVersions'
DESC 'The AllowMultipleVersions option controls the ability to DESC 'The AllowMultipleVersions option controls the ability to
configure multiple versions of a product on a system.' configure multiple versions of a product on a system.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at585> NAME 'reinstall' ( <oid-at204> NAME 'cimReinstall'
DESC 'The Reinstall property shows that this software element DESC 'The Reinstall property indicates that this software element
can transition to its next state even if a software element can transition to its next state even if a software element
of the same version already exists in the environment.' of the same version already exists in the environment.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-oc243> NAME 'dmtfVersionCompatibilityCheck'
DESC 'specifies whether it is permissible to create the next ( <oid-oc108> NAME 'cim22VersionCompatibilityCheck'
state of a software element.' DESC 'The VersionCompatibilityCheck class specifies whether it is
SUP dmtfCheck permissible to create the next state of a software
MUST (allowDownVersion $ allowMultipleVersions $ reinstall) element.'
SUP cim22Check
MAY (cimAllowDownVersion $ cimAllowMultipleVersions $
cimReinstall)
) )
3.14 dmtfAction 3.14 cim22Action
This abstract class represents an operation that is part of a process This class represents an operation that is part of a process to
to either create a SoftwareElement in its next state or to eliminate either create a SoftwareElement in its next state or to eliminate the
the SoftwareElement in the current state. It uses the attributes SoftwareElement in the current state.
name, version, softwareElementState, softwareElementID,
targetOperatingSystem, actionID, direction, caption, and description. ( <oid-at205> NAME 'cimActionID'
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
( <oid-at586> NAME 'actionID'
DESC 'The ActionID property is a unique identifier assigned to a DESC 'The ActionID property is a unique identifier assigned to a
particular action for a software element. May be used as an particular action for a software element.'
RDN.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at587> NAME 'direction' ( <oid-at206> NAME 'cimDirection'
DESC 'The Direction property is used to show whether a DESC 'The Direction property is used to indicate whether a
particular action object is part of a sequence of actions to particular Actionobject is part of a sequence of actions to
transition the currentsoftware element to its next state, transition the currentsoftware element to its next state,
such as Install or to remove the current software element, such as Install or to remove the current software element,
such as Uninstall. Allowed values are: "Install", such as Uninstall.'
"Uninstall".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc244> NAME 'dmtfAction' ( <oid-oc109> NAME 'cim22Action'
DESC 'an operation that is part of a process to either create a DESC 'A cim22Action is an operation that is part of a process to
SoftwareElement in its next state or to eliminate the either create a SoftwareElement in its next state or to
SoftwareElement in the current state.' eliminate the SoftwareElement in the current state.'
SUP top ABSTRACT SUP top
MUST (name $ version $ softwareElementState $ softwareElementID $ MUST (orderedCimModelPath)
targetOperatingSystem $ actionID $ direction $ caption $ MAY (cimName $ cimVersion $ cimSoftwareElementState $
description) cimSoftwareElementID $ cimTargetOperatingSystem $
cimActionID $ cimDirection $ cimCaption $ cimDescription)
) )
Although a variety of attributes may be used as RDNs, the following ( <oid-nf26> NAME 'cim22ActionNameForm'
structural rules are recommended: OC cim22Action
MUST (orderedCimModelPath)
( 36 NAME 'dmtfActionStructureRule1'
FORM dmtfActionNameForm1
SUP 34 35
)
( <oid-nf36> NAME 'dmtfActionNameForm1'
OC dmtfAction
MUST (name)
) )
( 37 NAME 'dmtfActionStructureRule2' ( <sr26> NAME 'cim22ActionStructureRule'
FORM dmtfActionNameForm1 FORM cim22ActionNameForm
SUP 34 35 SUP <sr27>
) )
( <oid-nf37> NAME 'dmtfActionNameForm2' The following content rule specifies the auxiliary classes that may
OC dmtfAction be attached to cim22Action.
MUST (actionID)
( <oid-oc109> NAME 'cim22ActionContentRule'
DESC 'The auxiliary classes that may be attached to cim22Action'
AUX (cim22ActionSequenceAuxClass)
) )
3.15 dmtfDirectoryAction 3.15 cim22DirectoryAction
This abstract class manages directories to be managed. Creation of This class manages directories to be managed. Creation of directories
directories is handled by dmtfCreateDirectoryAction and removal is is handled by cim22CreateDirectoryAction and removal is handled by
handled by dmtfRemoveDirectoryAction. cim22RemoveDirectoryAction.
( <oid-at588> NAME 'directoryName' INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
DESC 'The name of the directory.' ModelDecember 1999
SYNTAX string{1024} SINGLE-VALUE
( <oid-at207> NAME 'cimDirectoryName'
SYNTAX string SINGLE-VALUE
) )
( <oid-oc245> NAME 'dmtfDirectoryAction' ( <oid-oc110> NAME 'cim22DirectoryAction'
DESC 'used for directories to be managed.' DESC 'The DirectoryAction is an class that is used for
SUP dmtfAction ABSTRACT directories to be managed. Creation of directories is
MUST (directoryName) handled by the CreateDirectoriesAction and removal is
handled by the RemoveDirectory action.'
SUP cim22Action
MAY (cimDirectoryName)
) )
3.16 dmtfCreateDirectoryAction The following content rule specifies the auxiliary classes that may
be attached to cim22DirectoryAction.
This class creates empty directories for dmtfSoftwareElement objects ( <oid-oc110> NAME 'cim22DirectoryActionContentRule'
DESC 'The auxiliary classes that may be attached to
cim22DirectoryAction'
AUX (cim22ToDirectoryActionAuxClass $
cim22FromDirectoryActionAuxClass)
)
3.16 cim22CreateDirectoryAction
This class creates empty directories for cim22SoftwareElement objects
to be installed locally. to be installed locally.
( <oid-oc246> NAME 'dmtfCreateDirectoryAction' ( <oid-oc111> NAME 'cim22CreateDirectoryAction'
DESC 'creates empty directories for SoftwareElements to be DESC 'The CreateDirectory action creates empty directories for
installed locally.' SoftwareElements to be installed locally.'
SUP dmtfDirectoryAction SUP cim22DirectoryAction
) )
3.17 dmtfRemoveDirectoryAction 3.17 cim22RemoveDirectoryAction
This class removes directories for dmtfSoftwareElement objects. This class removes directories for cim22SoftwareElement objects.
( <oid-at589> NAME 'mustBeEmpty' ( <oid-at208> NAME 'cimMustBeEmpty'
DESC 'shows whether the directory must be empty (TRUE) to be
removed'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-oc247> NAME 'dmtfRemoveDirectoryAction' ( <oid-oc112> NAME 'cim22RemoveDirectoryAction'
DESC 'removes directories for SoftwareElements.' DESC 'The RemoveDirectoryAction removes directories for
SUP dmtfDirectoryAction SoftwareElements.'
MUST (mustBeEmpty) SUP cim22DirectoryAction
MAY (cimMustBeEmpty)
) )
3.18 dmtfFileAction INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
This abstract class allows an implementor to locate files that 3.18 cim22FileAction
already exist on the users machine, and move or copy those files to a
new location.
( <oid-oc248> NAME 'dmtfFileAction' This class allows an implementor to locate files that already exist
DESC 'allows an implementor to locate files that already exist on on the users machine, and move or copy those files to a new location.
the users machine, and move or copy those files to a new
location.' ( <oid-oc113> NAME 'cim22FileAction'
SUP dmtfAction ABSTRACT DESC 'The cim22FileAction allows the author to locate files that
already exist on the users machine, and move or copy those
files to a new location.'
SUP cim22Action
) )
3.19 dmtfCopyFileAction The following content rule specifies the auxiliary classes that may
be attached to cim22FileAction.
( <oid-oc113> NAME 'cim22FileActionContentRule'
DESC 'The auxiliary classes that may be attached to
cim22FileAction'
AUX (cim22FromDirectorySpecificationAuxClass $
cim22FromDirectoryActionAuxClass)
)
3.19 cim22CopyFileAction
This class specifies files that exist on a computer system, and to This class specifies files that exist on a computer system, and to
move or copy those files to a new location. move or copy those files to a new location.
( <oid-at590> NAME 'source' ( <oid-at209> NAME 'cimSource'
DESC 'source location' SYNTAX string SINGLE-VALUE
SYNTAX string{1024} SINGLE-VALUE
) )
( <oid-at591> NAME 'destination' ( <oid-at210> NAME 'cimDestination'
DESC 'destination location' SYNTAX string SINGLE-VALUE
SYNTAX string{1024} SINGLE-VALUE
) )
( <oid-at592> NAME 'deleteAfterCopy' ( <oid-at211> NAME 'cimDeleteAfterCopy'
DESC 'boolean indicating if the file should be moved (true)'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-oc249> NAME 'dmtfCopyFileAction' ( <oid-oc114> NAME 'cim22CopyFileAction'
DESC 'specifies files that exist on a computer system, and to DESC 'The cim22CopyFileAction specifies files that exist on a
move or copy those files to a new location.' computer system, and to move or copy those files to a new
SUP dmtfFileAction location. The to/from information for the copy is specified
MUST (source $ destination $ deleteAfterCopy) using either the ToDirectorySpecification/
FromDirectorySpecification or the ToDirectoryAction/
FromDirectoryAction associations. The first set is
used when the source and/or the target are to exist before
any actions are taken. The second set is used when the
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
source and/or target are created as a part of a previous
action. In the latter case, the action to create the
directory must occur prior to the CopyFileAction object.'
SUP cim22FileAction
MAY (cimSource $ cimDestination $ cimDeleteAfterCopy)
) )
3.20 dmtfRemoveFileAction The following content rule specifies the auxiliary classes that may
be attached to cim22CopyFileAction.
( <oid-oc114> NAME 'cim22CopyFileActionContentRule'
DESC 'The auxiliary classes that may be attached to
cim22CopyFileAction'
AUX (cim22ToDirectorySpecificationAuxClass $
cim22ToDirectoryActionAuxClass)
)
3.20 cim22RemoveFileAction
This class uninstalls files, specified in the file attribute. This class uninstalls files, specified in the file attribute.
( <oid-at593> NAME 'file' ( <oid-at212> NAME 'cimFile'
DESC 'file to be removed' SYNTAX string SINGLE-VALUE
SYNTAX string{1024} SINGLE-VALUE
) )
( <oid-oc250> NAME 'dmtfRemoveFileAction' ( <oid-oc115> NAME 'cim22RemoveFileAction'
DESC 'uninstalls files' DESC 'The RemoveFileAction uninstalls files.'
SUP dmtfFileAction SUP cim22FileAction
MUST (file) MAY (cimFile)
) )
3.21 dmtfRebootAction 3.21 cim22RebootAction
This class causes a reboot of the system where the software element This class causes a reboot of the system where the software element
is installed. is installed.
( <oid-oc251> NAME 'dmtfRebootAction' ( <oid-oc116> NAME 'cim22RebootAction'
DESC 'Causes a reboot of the system where the SoftwareElement is DESC 'The RebootAction Causes a reboot of the system where the
installed.' SoftwareElement is installed.'
SUP dmtfAction SUP cim22Action
) )
3.22 dmtfExecuteProgram 3.22 cim22ExecuteProgram
This class causes files to be executed on the system where the This class causes files to be executed on the system where the
dmtfSoftwareElement object is installed. It uses the attributes cim22SoftwareElement object is installed.
programPath and commandLine.
( <oid-at594> NAME 'programPath' ( <oid-at213> NAME 'cimProgramPath'
DESC 'Path to the executable'
SYNTAX string{1024} SINGLE-VALUE INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
SYNTAX string SINGLE-VALUE
) )
( <oid-at595> NAME 'commandLine' ( <oid-at214> NAME 'cimCommandLine'
DESC 'A string that is invocable on a system command line.' DESC 'A string that is invocable on a system command line.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc252> NAME 'dmtfExecuteProgram' ( <oid-oc117> NAME 'cim22ExecuteProgram'
DESC 'causes files to be executed on the system where the DESC 'The ExecuteProgram causes files to be executed on the
SoftwareElement is installed.' system where the SoftwareElement is installed.'
SUP cim22Action
SUP dmtfAction MAY (cimProgramPath $ cimCommandLine)
MUST (programPath $ commandLine)
) )
3.23 dmtfSettingCheck 3.23 cim22SettingCheck
This class specifies information needed to check a particular setting This class specifies information needed to check a particular setting
file for a specific entry that contains a value that is equal to, or file for a specific entry that contains a value that is equal to, or
contains, the value specified. All compares are case insensitive. contains, the value specified. All compares are case insensitive.
( <oid-at596> NAME 'sectionKey' ( <oid-at215> NAME 'cimSectionKey'
DESC 'Key of section containing the settings to be checked.' DESC 'Key of section containing the settings to be checked.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at597> NAME 'entryName' ( <oid-at216> NAME 'cimEntryName'
DESC 'Name of the Entry to be checked.' DESC 'Name of the Entry to be checked'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at598> NAME 'entryValue' ( <oid-at217> NAME 'cimEntryValue'
DESC 'Value to be checked that is associated with the named DESC 'Value to be checked that is associated with the named
entry.' entry.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at599> NAME 'checkType' ( <oid-at218> NAME 'cimCheckType'
DESC 'This specifies the way the setting value should be DESC 'This specifies the way the setting value should be compared.'
compared. Allowed values are: "Matches", "Contains".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc253> NAME 'dmtfSettingCheck' ( <oid-oc118> NAME 'cim22SettingCheck'
DESC 'specifies information needed to check a particular setting DESC 'This class specifies information needed to check a
file for a specific entry that contains a value that is particular setting file for a specific entry that contains
equal to, or contains, the value specified.' a value that is equal to, or contains, the value
SUP dmtfCheck specified. All compares are assumed to be case insensitive.'
MUST (sectionKey $ entryName $ entryValue $ checkType $ fileName) SUP cim22Check
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
MAY (cimSectionKey $ cimEntryName $ cimEntryValue $
cimCheckType $ cimFileName)
) )
3.24 dmtfModifySettingAction 3.24 cim22ModifySettingAction
This class specifies the information to be used to change a This class specifies the information to be used to change a
particular setting file for a specific entry with a specific value. particular setting file for a specific entry with a specific value.
All additions are case sensitive while removes are case insensitive. All additions are case sensitive while removes are case insensitive.
( <oid-at600> NAME 'actionType' ( <oid-at219> NAME 'cimActionType'
DESC 'Type of action to be performed on the specified setting DESC 'Type of action to be performed on the specified setting
entry. Create - Creates the specified entry. Delete - entry. Create - Creates the specified entry. Delete -
Deletes the specified entry. Append - Append to the end of Deletes the specified entry. Append - Append to the end of
the specified entry. Remove - Remove the value from the the specified entry. Remove - Remove the value from the
specified entry. Allowed values are: "Create", "Delete", specified entry.'
"Append", "Remove".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc254> NAME 'dmtfModifySettingAction' ( <oid-oc119> NAME 'cim22ModifySettingAction'
DESC 'specifies the information to be used to change a particular DESC 'This class specifies the information to be used to modify a
setting file for a specific entry with a specif1ic value.' particular setting file for a specific entry with a
SUP dmtfAction specific value. The value specified is created as a new
MUST (sectionKey $ entryName $ entryValue $ fileName $ entry or appends to, replaces, removes from, or deletes the
actionType) specified entry. All additions are assumed to be case
sensitive. Removes are assumed to be case insensitive.'
SUP cim22Action
MAY (cimSectionKey $ cimEntryName $ cimEntryValue $ cimFileName $
cimActionType)
) )
3.25 dmtfDirectorySpecificationFileAuxClass 3.25 cim22DirectorySpecificationFileAuxClass
This class identifies the directory that contains the file being This class identifies the directory that contains the file being
specified by referencing the dmtfDirectorySpecification class. specified by referencing the cim22DirectorySpecification class.
( <oid-at601> NAME 'dmtfDirectorySpecificationRef' ( <oid-at220> NAME 'cimDirectorySpecificationRef'
DESC 'The directory specification' SYNTAX DN
SYNTAX DN SINGLE-VALUE
) )
( <oid-at602> NAME 'dmtfFileSpecificationRefs' ( <oid-at221> NAME 'cimFileSpecificationRef'
DESC 'File Specifications'
SYNTAX DN SYNTAX DN
) )
( <oid-oc255> NAME 'dmtfDirectorySpecificationFileAuxClass' ( <oid-oc120> NAME 'cim22DirectorySpecificationFileAuxClass'
DESC 'identifies the directorythat contains the file being DESC 'The cim22DirectorySpecificationFile association identifies
specified by referencing the dmtfDirectorySpecification the directorythat contains the file being specified by
class.' referencing the cim22DirectorySpecification class.'
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfDirectorySpecificationRef $ dmtfFileSpecificationRefs) MAY (cimDirectorySpecificationRef $ cimFileSpecificationRef)
) )
3.26 dmtfActionSequenceAuxClass 3.26 cim22ActionSequenceAuxClass
dmtfActionSequenceAuxClass defines a series of operations that either cim22ActionSequenceAuxClass defines a series of operations that
transitions the software element, referenced by either transitions the software element, referenced by
dmtfSoftwareElementActionsAuxClass, to its next state or removes the cim22SoftwareElementActionsAuxClass, to its next state or removes the
software element from its current environment. The action classes software element from its current environment. The action classes
participating in this association must have the same value for the participating in this association must have the same value for the
direction property since they are either part of a sequence to direction property since they are either part of a sequence to
transition a software element into its next state or to uninstall a transition a software element into its next state or to uninstall a
software element. The next-state actions and uninstall actions software element. The next-state actions and uninstall actions
associated with a particular software element must be a continuos associated with a particular software element must be a continuous
sequence. Since the action sequence is an association the loops on sequence. Since the action sequence is an association the loops on
the action class with roles for the 'prior' action and 'next' action the action class with roles for the 'prior' action and 'next' action
in a sequence, the need for a continous sequence implies: (1)Within in a sequence, the need for a continuous sequence implies: (1)Within
the set of next-state or uninstall actions, there is one and only one the set of next-state or uninstall actions, there is one and only one
action that does not have an instance of the ActionSequence action that does not have an instance of the ActionSequence
association referencing it in the 'next' role. This is the first association referencing it in the 'next' role. This is the first
action in the sequence. (2) Within the set of next-state or uninstall action in the sequence. (2) Within the set of next-state or uninstall
actions, there is one and only one action that does not have an actions, there is one and only one action that does not have an
instance of the ActionSequence association referencing it in the instance of the ActionSequence association referencing it in the
'prior' role. This is the last action in the sequence. (3) All other 'prior' role. This is the last action in the sequence. (3) All other
actions within the set of next-state and uninstall actions must actions within the set of next-state and uninstall actions must
participate in two instances of the ActionSequence association, one participate in two instances of the ActionSequence association, one
in a prior role and one in the next role. in a prior role and one in the next role.
( <oid-at603> NAME 'nextActionRef' ( <oid-at222> NAME 'cimNextRef'
DESC 'next action' SYNTAX DN
SYNTAX DN SINGLE-VALUE
) )
( <oid-at604> NAME 'priorActionRef' ( <oid-at223> NAME 'cimPriorRef'
DESC 'next action' SYNTAX DN
SYNTAX DN SINGLE-VALUE
) )
( <oid-oc256> NAME 'dmtfActionSequenceAuxClass' ( <oid-oc121> NAME 'cim22ActionSequenceAuxClass'
DESC 'used to define a series of operations that either DESC 'The cim22ActionSequence association is used to define a
transitions the software element, referenced by the series of operations that either transitions the software
dmtfSoftwareElementActions association, to its next state element, referenced by the cim22SoftwareElementActions
or removes the software element from its current association, to its next state or removes the software
environment.' element from its current environment. The Action classes
participating in this association must have the same value
for the Direction property since they are either part of a
sequence to transition a software element into its next
state or to uninstall a software element. The next-state
actions and uninstall actions associated with a particular
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
software element must be a continuous sequence. Since the
ActionSequence is an association the loops on the Action
class with roles for the "prior" action and "next" action
in a sequence, the need for a continuous sequence implies:
(1)Within the set of next-state or uninstall actions, there
is one and only one action that does not have an instance
of the ActionSequence association referencing it in the
"next" role. This is the first action in the sequence. (2)
Within the set of next-state or uninstall actions, there is
one and only one action that does not have an instance of
the ActionSequence association referencing it in the
"prior" role. This is the last action in the sequence. (3)
All other actions within the set of next-state and
uninstall actions must participate in two instances of the
ActionSequence association, one in a prior role and one in
the next role. Both attributes point to cim22Action objects.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (nextActionRef $ priorActionRef) MAY (cimNextRef $ cimPriorRef)
) )
3.27 dmtfSoftwareFeatureSoftwareElementsAuxClass 3.27 cim22SoftwareFeatureSoftwareElementsAuxClass
This auxiliary class identifies the software elements that make up a This auxiliary class identifies the software elements that make up a
particular software feature. In it, groupComponentRefs point to particular software feature.
dmtfSoftwareFeature objects and partComponentRefs point to
dmtfSoftwareElement objects.
( <oid-oc257> NAME 'dmtfSoftwareFeatureSoftwareElementsAuxClass' ( <oid-oc122> NAME 'cim22SoftwareFeatureSoftwareElementsAuxClass'
DESC 'identifies the software elements that make up a particular DESC 'The SoftwareFeatureSoftwareElements associations identifies
software feature.' the software elements that make up a particular software
SUP dmtfComponentAuxClass AUXILIARY feature. Attribute cimGroupComponentRef points to
cim22SoftwareFeature and attribute cimPartComponentRef points
to cim22SoftwareElement.'
SUP cim22ComponentAuxClass
MAY (cimGroupComponentRef $ cimPartComponentRef)
) )
3.28 dmtfToDirectorySpecificationAuxClass 3.28 cim22ToDirectorySpecificationAuxClass
This auxiliary class identifies the target directory for the file This auxiliary class identifies the target directory for the file
action and assumes that the target directory already existed. This action and assumes that the target directory already existed. This
association cannot exist with a dmtfToDirectoryActionAuxClass since a association cannot exist with a cim22ToDirectoryActionAuxClass since
file action can only involve a single target directory. a file action can only involve a single target directory.
( <oid-at605> NAME 'dmtfDirectorySpecificationRef' ( <oid-at224> NAME 'cimDestinationDirectoryRef'
DESC 'directory specification indicating the destination' SYNTAX DN
SYNTAX DN SINGLE-VALUE
) )
( <oid-at606> NAME 'dmtfCopyFileActionRefs' ( <oid-at225> NAME 'cimFileNameRef'
DESC 'List of copy file actions'
SYNTAX DN SYNTAX DN
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
) )
( <oid-oc258> NAME 'dmtfToDirectorySpecificationAuxClass' ( <oid-oc123> NAME 'cim22ToDirectorySpecificationAuxClass'
DESC 'identifies the target directory for the file action.' DESC 'The ToDirectorySpecification association identifies the
target directory for the file action. When this association
is used, the assumption is that the target directory
already existed. This association cannot exist with a
ToDirectoryAction association since a file action can only
involve a single target directory. Attribute
cimDestinationDirectoryRef points to
cim22DirectorySpecification and attribute cimFileNameRef
points to cim22CopyFileAction.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfDirectorySpecificationRef $ dmtfCopyFileActionRefs) MAY (cimDestinationDirectoryRef $ cimFileNameRef)
) )
3.29 dmtfFromDirectorySpecificationAuxClass 3.29 cim22FromDirectorySpecificationAuxClass
This auxiliary class identifies the source directory for the file This auxiliary class identifies the source directory for the file
action and assumed that the source directory already existed. This action and assumed that the source directory already existed. This
association cannot exist with a dmtfFromDirectoryActionAuxClass since association cannot exist with a cim22FromDirectoryActionAuxClass
a file action can only involve single source directory. since a file action can only involve single source directory.
( <oid-at607> NAME 'dmtfFileActionRefs' ( <oid-at226> NAME 'cimSourceDirectoryRef'
DESC 'a list of file actions'
SYNTAX DN SYNTAX DN
) )
( <oid-oc259> NAME 'dmtfFromDirectorySpecificationAuxClass' ( <oid-oc124> NAME 'cim22FromDirectorySpecificationAuxClass'
DESC 'identifies the source directory for the file action.' DESC 'The FromDirectorySpecification association identifies the
source directory for the file action. When this association
is used, the assumption is that the source directory
already existed. This association cannot exist with a
FromDirectoryAction association since a file action can
only involve single source directory. Attribute
cimSourceDirectoryRef points to cim22DirectorySpecification
and cimFileNameRef points to cim22FileAction.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfDirectorySpecificationRef $ dmtfFileActionRefs) MAY (cimSourceDirectoryRef $ cimFileNameRef)
) )
3.30 dmtfToDirectoryActionAuxClass 3.30 cim22ToDirectoryActionAuxClass
This auxiliary class identifies the target directory for the file This auxiliary class identifies the target directory for the file
action and assumes that a previos action creates the target directory action and assumes that a previous action creates the target
This association cannot exist with a directory This association cannot exist with a
dmtfToDirectorySpecificationAuxClass since a file action can only cim22ToDirectorySpecificationAuxClass since a file action can only
involve a single target directory. involve a single target directory.
( <oid-at608> NAME 'dmtfDirectoryActionRef' INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
DESC 'directory action reference' ModelDecember 1999
SYNTAX DN SINGLE-VALUE
)
( <oid-oc260> NAME 'dmtfToDirectoryActionAuxClass' ( <oid-oc125> NAME 'cim22ToDirectoryActionAuxClass'
DESC 'identifies the target directory for the file action.' DESC 'The ToDirectoryAction association identifies the target
directory for the file action. When this association is
used, the assumption is that the target directory was
created by a previous action. This association cannot exist
with a ToDirectorySpecification association since a file
action can only involve a single target
directory. Attribute cimDestinationDirectoryRef points to
cim22DirectoryAction and attribute cimFileNameRef
points to cim22CopyFileAction.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfDirectoryActionRef $ dmtfCopyFileActionRefs) MAY (cimDestinationDirectoryRef $ cimFileNameRef)
) )
3.31 dmtfFromDirectoryActionAuxClass 3.31 cim22FromDirectoryActionAuxClass
This auxiliary class identifies the source directory for the file This auxiliary class identifies the source directory for the file
action and assumes that a previous action creates the source action and assumes that a previous action creates the source
directory. It cannot exist with a directory. It cannot exist with a
dmtfFromDirectorySpecificationAuxClass since a file action can only cim22FromDirectorySpecificationAuxClass since a file action can only
involve a single source directory. involve a single source directory.
( <oid-oc261> NAME 'dmtfFromDirectoryActionAuxClass' ( <oid-oc126> NAME 'cim22FromDirectoryActionAuxClass'
DESC 'identifies the source directory for the file action.' DESC 'The FromDirectoryAction association identifies the source
directory for the file action. When this association is
used, the assumption is that the source directory was
created by a previous action. This association cannot exist
with a FromDirectorySpecification association since a file
action can only involve a single source
directory. Attribute cimSourceDirectoryRef points to
cim22DirectoryAction and cimFileNameRef points to
cim22FileAction.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfDirectoryActionRef $ dmtfFileActionRefs) MAY (cimSourceDirectoryRef $ cimFileNameRef)
) )
3.32 dmtfSoftwareFeatureServiceImplementationAuxClass 3.32 cim22SoftwareFeatureServiceImplementationAuxClass
This auxiliary class relates a service and how it is implemented in This auxiliary class relates a service and how it is implemented in
software and has a many-to-many cardinality. A service may be software and has a many-to-many cardinality. A service may be
provided by more than one software feature, operating in conjunction provided by more than one software feature, operating in conjunction
and, any software feature may provide more than one service. If and, any software feature may provide more than one service. If
different implementations of a service exist, each of these different implementations of a service exist, each of these
implementations are individual instantiations of the dmtfService implementations are individual instantiations of the cim22Service
object. These individual instantiations would then have associations object. These individual instantiations would then have associations
to the unique implementations. to the unique implementations.
( <oid-oc262> NAME 'dmtfSoftwareFeatureServiceImplementationAuxClass' ( <oid-oc127> NAME
DESC 'relation between a Service and how it is implemented in
software.' INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
SUP dmtfDependencyAuxClass AUXILIARY ModelDecember 1999
'cim22SoftwareFeatureServiceImplementationAuxClass'
DESC 'An association between a Service and how it is implemented
in software. The cardinality of this association is
many-to-many. A Service may be provided by more than one
SoftwareFeature, operating in conjunction. And, any
software Feature may provide more than one Service. When
multiple SoftwareFeatures are associated with a single
Service, it is assumed that these elements operate in
conjunction to provide the Service. If different
implementations of a Service exist, each of these
implementations would result in individual instantiations
of the Service object. These individual instantiations
would then have associations to the unique
implementations. Attribute cimAntecendentRef points to
cim22SoftwareFeature and attribute cimDependentRef points to
cim22Service.'
SUP cim22DependencyAuxClass
MAY (cimAntecedentRef $ cimDependentRef)
) )
3.33 dmtfSoftwareFeatureSAPImplementationAuxClass 3.33 cim22SoftwareFeatureSAPImplementationAuxClass
This auxiliary class represents the relationship between a eervice This auxiliary class represents the relationship between a service
access point and how it is implemented in software. The cardinality access point and how it is implemented in software. The cardinality
of this association is many-to-many. A SAP may be provided by more of this association is many-to-many. A SAP may be provided by more
than one SoftwareFeature, operating in conjunction. And, any than one SoftwareFeature, operating in conjunction. And, any
SoftwareFeature may provide more than one ServiceAccessPoint. a When SoftwareFeature may provide more than one ServiceAccessPoint. a When
many SoftwareFeatures are associated with single SAP, it is assumed many SoftwareFeatures are associated with single SAP, it is assumed
that these elements operate in conjunction to provide the that these elements operate in conjunction to provide the
AccessPoint. If different implementations of a SAP exist, each of AccessPoint. If different implementations of a SAP exist, each of
these implementations would result in individual instantiations of these implementations would result in individual instantiations of
the ServiceAccessPoint object. These individual instantiations would the ServiceAccessPoint object. These individual instantiations would
then have associations to the unique implementations. then have associations to the unique implementations.
( <oid-oc263> NAME 'dmtfSoftwareFeatureSAPImplementationAuxClass' ( <oid-oc128> NAME 'cim22SoftwareFeatureSAPImplementationAuxClass'
DESC 'relationship between a ServiceAccessPoint and how it is DESC 'An association between a ServiceAccessPoint and how it is
implemented in software.' implemented in software. The cardinality of this association
SUP dmtfDependency AUXILIARY is many-to-many. A SAP may be provided by more than one
SoftwareFeature, operating in conjunction. And, any
SoftwareFeature may provide more than one
ServiceAccessPoint. a When many SoftwareFeatures are
associated with single SAP, it is assumed that these
elements operate in conjunction to provide the
AccessPoint. If different implementations of a SAP exist,
each of these implementations would result in individual
instantiations of the ServiceAccessPoint object. These
individual instantiations would then have associations to
the unique implementations. Attribute cimAntecendentRef
INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999
points to cim22SoftwareFeature and attribute cimDependentRef
points to cim22ServiceAccessPoint.'
SUP cim22DependencyAuxClass
MAY (cimAntecedentRef $ cimDependentRef)
) )
3.34 dmtfApplicationSystemSoftwareFeatureAuxClass 3.34 cim22ApplicationSystemSoftwareFeatureAuxClass
This auxiliary class identifies the software features, which may be This auxiliary class identifies the software features, which may be
part of different products, that make up a particular application part of different products, that make up a particular application
system. system.
( <oid-oc264> NAME 'dmtfApplicationSystemSoftwareFeatureAuxClass' ( <oid-oc129> NAME 'cim22ApplicationSystemSoftwareFeatureAuxClass'
DESC 'identifies the software features that make up a particular DESC 'The ApplicationSystemSoftwareFeature associations
application system.' identifies the software features that make up a particular
SUP dmtfSystemComponentAuxClass AUXILIARY application system. The software features can be part of
different products. Attribute cimGroupComponentRef points
to cim22ApplicationSystem and attribute cimPartComponentRef
points to cim22SoftwareFeature.'
SUP cim22SystemComponentAuxClass
MAY (cimGroupComponentRef $ cimPartComponentRef)
) )
3.35 dmtfInstalledSoftwareElementAuxClass 3.35 cim22InstalledSoftwareElementAuxClass
This auxiliary class allows one to identify the computer system a This auxiliary class allows one to identify the computer system a
particular software element is installed on. particular software element is installed on.
( <oid-at609> name 'dmtfSoftwareElementRefs' ( <oid-at227> NAME 'cimSoftwareRef'
DESC 'references software elements that are installed' DESC 'References the software element that is installed.'
SYNTAX DN SYNTAX DN
) )
( <oid-at610> name 'dmtfComputerSystemRef' ( <oid-at228> NAME 'cimSystemRef'
DESC 'references the computer system hosting a particular DESC 'References the computer system hosting a particular
software element' software element.'
SYNTAX DN SINGLE-VALUE SYNTAX DN
) )
( <oid-oc265> name 'dmtfInstalledSoftwareElementAuxClass' ( <oid-oc130> NAME 'cim22InstalledSoftwareElementAuxClass'
DESC 'identifies the Computer System a particular Software DESC 'The InstalledSoftwareElement association allows one to to
element is installed on.' identify the Computer System a particular Software element
is installed on. Attribute cimSoftwareRef points to
cim22SoftwareElement and attribute cimSystemRef points to
cim22ComputerSystem.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfSoftwareElementRefs $ dmtfComputerSystemRef) MAY (cimSoftwareRef $ cimSystemRef)
4. DIT Content Rules
The following DIT Content Rules apply to objects in this schema.
These content rules reference not only auxiliary classes in this
draft but auxiliary classes from other DMTF schemata [5, 6, 7, 8, 9]
( <oid-oc231> NAME 'dmtfApplicationSystemContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfApplicationSystem class'
AUX (dmtfApplicationSystemSoftwareFeatureAuxClass)
)
( <oid-oc232> NAME 'dmtfSoftwareElementContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfSoftwareElement class'
AUX (dmtfDeviceSoftwareAuxClass $
dmtfSoftwareFeatureSoftwareElementsAuxClass)
)
( <oid-oc233> NAME 'dmtfSoftwareFeatureContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfSoftwareFeature class'
AUX (dmtfOperatingSystemSoftwareFeatureAuxClass $
dmtfSoftwareFeatureSoftwareElementsAuxClass $
dmtfSoftwareFeatureServiceImplementationAuxClass $
dmtfSoftwareFeatureSAPImplementationAuxClass $
dmtfApplicationSystemSoftwareFeatureAuxClass)
)
( <oid-oc235> NAME 'dmtfDirectorySpecificationContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfDirectorySpecification class'
AUX (dmtfDirectorySpecificationFileAuxClass $
dmtfToDirectorySpecificationAuxClass $
dmtfFromDirectorySpecificationAuxClass)
)
( <oid-oc242> NAME 'dmtfFileSpecificationContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfFileSpecification class'
AUX (dmtfDirectorySpecificationFileAuxClass)
)
( <oid-oc244> NAME 'dmtfActionContentRule'
DESC 'shows what auxiliary classes may go with the dmtfAction
class'
AUX (dmtfActionSequenceAuxClass)
)
( <oid-oc245> NAME 'dmtfDirectoryActionContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfDirectoryAction class'
AUX (dmtfToDirectoryActionAuxClass $
dmtfFromDirectoryActionAuxClass)
)
( <oid-oc248> NAME 'dmtfFileActionContentRule'
DESC 'shows what auxiliary classes may go with the dmtfFileAction
class'
AUX (dmtfFromDirectorySpecificationAuxClass $
dmtfFromDirectoryActionAuxClass)
) )
( <oid-oc249> NAME 'dmtfCopyFileActionContentRule' INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
DESC 'shows what auxiliary classes may go with the ModelDecember 1999
dmtfCopyFileAction class'
AUX (dmtfToDirectorySpecificationAuxClass $
dmtfToDirectoryActionAuxClass)
)
5. References 4. References
Request For Comments (RFC) and Internet Draft documents are available Request For Comments (RFC) and Internet Draft documents are available
from numerous mirror sites. from numerous mirror sites.
[1] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access [1] M. Wahl, T. Howes, S. Kille, "Lightweight Directory
Protocol (v3)," RFC 2251, Decemeber 1997. Access Protocol (v3)," RFC 2251, December 1997.
[2] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight
Directory Access Protocol (v3): Attribute Syntax Defini-
tions," RFC 2252, December 1997.
[3] Ryan Moats, Gerald Maziarski, John Strassner, "Extensible
Match Rule to Dereference Pointers", Internet Draft (work in
progress), June 1999.
[4] DMTF, "CIM Application Model, v2.2".
[5] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
for the DMTF Core CIM Model", September 1999.
[6] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [2] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Light-
for the DMTF Device CIM Model", September 1999. weight Directory Access Protocol (v3): Attribute
Syntax Definitions," RFC 2252, December 1997.
[7] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [3] Ryan Moats, Gerald Maziarski, John Strassner,
for the DMTF Network CIM Model", October 1999. "Extensible Match Rule to Dereference Pointers",
Internet Draft (work in progress), June 1999.
[8] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [4] DMTF, "CIM Application Model, v2.2".
for the DMTF System CIM Model", October 1999.
[9] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [5] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP
for the DMTF Physical CIM Model", October 1999. Schema for the DMTF Core CIM v2.2 Model", Internet
Draft (work in progress), December 1999.
6. Author's Addresses 5. Author's Addresses
Ryan Moats Jerry Maziarski John Strassner Ryan Moats Jerry Maziarski John Strassner
15621 Drexel Circle Room C3-3Z01 Cisco Systems, Bldg 1 15621 Drexel Circle Room C3-3Z01 Cisco Systems, Bldg 1
Omaha, NE 68135 200 S. Laurel Ave. 170 West Tasman Drive Omaha, NE 68135 200 S. Laurel Ave. 170 West Tasman Drive
USA Middletown, NJ 07748 San Jose, CA 95134 USA Middletown, NJ 07748 San Jose, CA 95134
E-mail: jayhawk@att.com USA E-mail: E-mail: jayhawk@att.com USA E-mail:
johns@cisco.com johns@cisco.com
E-mail: gfm@qsun.att.com E-mail: gfm@qsun.att.com
 End of changes. 223 change blocks. 
713 lines changed or deleted 979 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/