DMTF Developers Conference1Page June 13 2001 Application Model & Metrics Model Update June 2001 Karl Schopmeyer The Open Group [email protected]

DMTF Developers Conference 1PageJune 13 2001

Application ModelApplication Model&&

Metrics ModelMetrics ModelUpdateUpdate

June 2001June 2001Karl Schopmeyer

The Open [email protected]

This presentation is dedicated to Heather Kreger and all of the work

she has done to move application management forward

Version 1.00 13 June


Agenda

• The Objectives of Application Management• The Original Model – Life Cycle Management• The Metrics Model• The Work Today

– Managing Running Applications

• Directions and Futures.


The Objectives of Application The Objectives of Application ManagementManagement

• Life-Cycle Management of Applications– Distribution, installation, etc.

• Management of running Applications, Services, Business Applications– Performance Information, Executing Operations,

State of the application, etc.


A Short History of the GroupA Short History of the Group

• Application Model – Lifecycle– One of the first models finished (1999)

• DAP – Model finished 2000

• Application RunTime– Group initiated 2000– First Submission CIM V2.5– Merge with DAP (common Metrics) 2001– In process now


Major ParticipantsMajor Participants

• Mark Johnson (Tivoli) • Heather Kreger (IBM)• Alex Keller (IBM)• Takaki Kuroda (Hitachi)• Vijay Machiraju (Hewlett Packard)• Mike Reynolds (BMC Software)• Karl Schopmeyer (The Open Group, Tivoli)• John Sweitzer (Tivoli Systems)• AndreaWesterinen (Cisco Systems)


User’s of the Application ModelUser’s of the Application Model

CIM-based Application Management

Information

ProduceOperating Systems

Install Utility

Install Utility

System Based Software Inventory

System Based Software Inventory

Consumed

ByManagement

Tool

Software Distribution, Dependency Checking,Change Management

Consumed

By

Application Developers and Providers

Produced ByHand

Application Development

Tool

Produced using tools like change management tools.

Systems Systems Systems


The Existing ModelsThe Existing Models

Application Management Model


Application Model OverviewApplication Model Overview

SoftwareFeature

ApplicationSystem

Core Model

Application Model

ProductSoftwareFeature ApplicationSystemSoftwareFeature

SoftwareFeatureSoftwareElements

SoftwareElement

Product Service

Unit of Component ManagementUnit of Component Management

Unit of AcquisitionUnit of Acquisition

Unit of DeploymentUnit of Deployment

Execution ServiceExecution Service

Collect Features into Business

System

Collect Features into Business

System


Software ElementsSoftware Elements

• The Unit of Deployment– Installed and uninstalled

• Represent a collection of files and associated details that are individually managed

• Abstracted to Software Features

This is what actually gets installed

SoftwareElement


Software FeatureSoftware Feature

• Unit of component management

• Components meaningful to consumer or user of the application

• Reflect functions or roles of a component of an application

• Ex. Trading client, quote server, etc.

This is what the user sees

SoftwareFeature


Software ProductSoftware Product

• Unit of acquisition

• Implies agreement between consumer and supplier– License, support, warrantee, …

This is what we pay for

Product


Application SystemsApplication Systems

• Collect features into business systems

• Support a business function

• Collections of software features from one or more products combined to fulfill business function

This is how the managers would like to view the environment

ApplicationSystem


Life-Cycle ManagementLife-Cycle Management


the

Application Life-Cycle


Application Life CycleApplication Life Cycle

• Critical states in process of transition from development to operational

• Applies to lowest-level component– Software Elements

• States

Deployable Executable RunningInstallable


Refining Software ElementRefining Software Element

SoftwareElement

States Deployable Installable Executable Running

Platform

NT

Windows 95

Solaris

HPUX

...

Details

•Number•Conditions•Actions


DeployableState

InstallableState

ExecutableState

RunningState

Software Element Conditions

Conditions are situations that are expect to exist or not exist in an environment

Conditions Conditions Conditions Conditions

In-State Conditions are characteristics of an environment that contains an element.

In-State In-State In-State In-State

Next-State Conditions are characteristics that need to be true in the target environment for the next state of a software element.

Next State Next State Next State Next State






DeployableState

InstallableState

ExecutableState

RunningState

Software Element Actions

Actions are a sequence of operations

Actions Actions Actions Actions

Next State Actions create a software element in a particular state.

Next State Next State Next State Next State

Uninstall Actions properly remove a software element

Uninstall Uninstall Uninstall Uninstall


Actions Description

Directory An action to create or remove a directory.

File An action to create or remove a file.

Re-boot An action the signals the need to reboot the computersystem.

ExecuteProgram

An action that execute a program. This can be the installscript or program (e.g., setup.exe) when a software elementin the installable state transitions to the executable state.

Deployable Installable Executable Running

Software Element Actions


Check

SoftwareElementChecks

PhaseSoftwareElement

SoftwareElementState

Action

Direction

SoftwareElementAction

ActionSequence

More on the Model


Resource Life Cycle

Planning

Operating

Configuring

Deploying

Diagnosing

Evaluating

Executable

Deployable

Installable

Running

Current Modeling work is focused on the “Running Application Requirements”



The DAP Model

-

Measuring Performance


DAP Working GroupDAP Working Group

• DAP = Distributed Application Performance

• DAP model incorporated into Schema in Schema 2.3 or 2.4

• DAP work to merge with runtime application work group.


DAP CharterDAP Charter

• Define common model for standard runtime behavior of distributed applications in heterogeneous environments– Includes quality of service objects– Relate to other CIM models– Evolve standard methods to populate the model

• Develop a unifying model for a unit of work


DAP StatusDAP Status

• Define common model for standard runtime behavior of distributed applications in heterogeneous environments– Includes quality of service objects [DONE]– Relate to other CIM models [TBD??]– Evolve standard methods to populate the model

• Will DAP ever do this?• Emphasis has been on compatibility with existing interfaces (ARM in

particular), rather than defining new ones

• Unifying model for a unit of work [DONE]


Unifying concept for a unit of Unifying concept for a unit of workwork

• A unit of work can be many things, such as:– Batch job– User-initiated interactive operation– Transaction executed by a TP Monitor– Short server transactions, such as a database read


Thoughts on namingThoughts on naming

• Why is the term “Unit of Work” used instead of “Transaction”?– “Transaction” can imply specific behavior, such as

commit and rollback– Batch jobs and similar units of work are not often

thought of as “transactions”


Major schema classesMajor schema classes

• Definition of unit of work type• Instances of these unit of work types that have started

executing– Common measurements are properties

• Definition of metrics associated with the unit of work• Values of metrics

Note: what has also been added since the last version

was the asociation to CIM_ManagedSystemElementfrom the CIM Core Schema.


CIM_LogicalElement

UOWMetric

Definition

UOWDefinition

Logical ElementUOW Definition

UOW MetricDefinition

Logical Elementperforms UOW

Sub UOWDefinition

SubUOW

UOW Metric

w

Started UOW

MetricValue

ManagedElement


LogicalE lem ent

ManagedSystem Elem ent

InstallDate:datetim eNam e:stringStatus:string

Title : DAP Schema v2.3aFilename: CIM_DAP23.vsdAuthor : John LeeDate : February 1, 2000

Association

Aggregation

Association with W EAK reference

Inheritance

Aggregation with W EAK reference

w

w

id : s int64 [key]UoW DefId: string [key, propagated]UserNam e: stringStartT im e: datetim eE lapsedTim e: datetim eStatus : uint16

UnitO fW ork

0..n

0..n SubUoW Def

Dependent

Antecedent

Context : string [required]Nam e : string [required]Id : string [key]

UnitO fW orkDefinition

0..nw

1..1

S tartedUoW

0..n

0..n

LogicalE lem entPerform sUoW

MetricDefinition

id : string [key]Nam e: string[required]DataType: uint16 [required]Calculable: uint16 [required]Units: stringValidity: uint16

0..n

1..n

UoW MetricDefintion

0..n 0..

nUoW Metric

Value : string

UoW Metric

0..n

0..1

SubUoW

Dependent

Antecedent

0..n

0..n

LogicalE lem entUnitO fW orkDef

elapsed tim e hasresponse tim e ifU n itO fW ork has

com ple ted

ManagedElem ent

Caption: stringDescription string

NEW

Title : DAP Schema v2.3aFilename: CIM_DAP23.vsdAuthor : John LeeDate : February 1, 2000


Unit Of WorkUnit Of WorkDefinitionDefinition

• Defines a type of work

• Examples:– Update account balance– Backup file system– Query data server– Execute subroutine/method


UOW DefinitionUOW DefinitionPropertiesProperties

• ID - 16 bytes long [key]– Use of OSF UUID is recommended

• MAC address (or substitute)• Current date and time• Counter to handle high-frequency allocations• A clock sequence and related state to handle the

retrograde movement of clocks.

• Name

• Context (such as application name)


Unit of WorkUnit of Work

• Represents a UOW that has started (and maybe completed) executing

• Always associated to its definition– Weak association with propagated key– This provides separation of the namespace to avoid

collisions


Unit of WorkUnit of WorkMeasurementsMeasurements

• Response time or elapsed time (if still executing)

• Status• Active• Suspended• Completed (with unknown state)• Completed Good• Completed Failed• Completed Aborted

• Metrics (in a separate class)


Unit of WorkUnit of WorkPropertiesProperties

• ID [key]

• UOW ID [key, propagated]

• User Name [or ID or context or ???]

• Start time

• Elapsed time since UOW started (response time if complete)

• Status


AssociationsAssociationsbetween between UOWsUOWs

• UOW may be associated to other units of work (parent or children)– Ex: a server UOW may be the child of the client

UOW that invoked it

• Association can be at either or both of two levels– Between UOW definitions– Between UOW instances


AssociationsAssociations to toLogical ElementsLogical Elements

• A UOW instance may be associated to the Logical Element that performs it

• Examples:– Computer system/processor– Printer– Application system


AssociationsAssociations to toLogical Elements-2Logical Elements-2

• A UOW definition may be associated to another logical element

• Semantics of the association are not specified


MetricMetricDefinitionDefinition

• The Class– Defines metrics associated with a unit of work– Even if defined, a value may not be provided at all times

• Properties– ID [key]– Name– Data type (sint32, uint64, string, …)– Calculable (What type of calculations, if any, are OK: none, sum,

no sum)– Units (bytes, files, milliseconds, …)– Validity (start/middle/stop) [??]


MetricMetric

• Contains the actual value at any point in time

• Value is a string so it can contain any of the several data types

• Constraint on Metric Definition:– Must be associated to the same UOW Definition

to which the UOW is weakly associated



Managing

Operational Applications


Running Application RequirementsRunning Application Requirements

Running Application Requirements have many interpretations.

They can focus on the “Resource View”…

Model the operational issues for an application in isolation.

They can focus on the “Service View”…

Model the operational issues of a service for a user

They can focus on the “Business View”…

Model the operational issues for an application that is part of a business process.


Operations

Running Application Ingredients

Configuration Information

HeartbeatExerciser

Monitors

(Thresholds)Metrics

Run Time

Relationships

ApplicationDescription

Events


More Details for Configuration Information

Configuration Information

Classes: What classes can have configuration information? (Product, Software Feature, Software Element, Services, etc.)

Scope: How does one express the existence of a setting before values are known?

Leverage: How does the Core Model classes for Configuration and Setting fit into the requirements?

Operations: What assumptions does a particular approach make about how configuration is changed? (method call, property value, etc.)


More Details for MetricsMore Details for Metrics

Classes: What classes can have metrics? Does the answer change for resource/service/business views?

Scope: How does one express the existence of a metrics before values are known?

Leverage: How does the DAP Model relate?

Policy: How does the policy model impact metrics?

Metrics


More Details for Operations

Classes: What classes can have runtime operations? (Product, Software Feature, Software Element, Services, etc.)

Scope: How does one express the existence of an operation?

Leverage: Can runtime operations be expressed using the CIM method concept?

Parameters: What are the type of parameters?

Operations


Issues with Managing AppsIssues with Managing Apps

• There are so many of them

• There is no single clear model for the organization of Applications

• Application structure and architecture varies widely

• Moving from static to dynamic applications and relationships


The State of the ModelThe State of the Model

• Metrics Model– Preliminary defined

• Operations Model– Preliminary Defined

• Configuration Information– In Process

• State Management– Preliminary Discussion

• Incremental Changes Passed Schema 2.5


Modeling MetricsModeling Metrics

• Step 1 -Started with an independent Model

• Step 2 –Realized commonality with DAP

• Step 3 – Blended two in to Metrics work group

• Step 4 – Blended metrics back into Runtime Apps

• Status Today– Preliminary model defined– Needs documentation


The Metrics ModelThe Metrics Model

Base Metric Definition

Metric Definition

BaseMetric

ManagedElement

ManagedSystemElement

LogicalElement

UnitofWorkDefinition

UnitofWork

MetricForMe

MetricDefForMe

CIM_UoWMetricDef

UoWMetric

LEPerformsUoW

StartedUoWPolicyRule

CIMMetricValidityPolicy

LEUoWDef

PRELIMINARYPRELIMINARY


LogicalElement

ManagedSystemElement

InstallDate:datetimeName:stringStatus:string

Title : Metric Schema v2.6Filename: CIM_Metric26.vsdAuthor : Heather KregerDate : January 19, 2001

Association

Aggregation

Association with WEAK reference

Inheritance

Aggregation with WEAK reference

w

w

id : sint64 [key]UoWDefId: string [key, propagated]UserName: stringStartTime: datetimeElapsedTime: datetimeStatus : uint16

UnitOfWork

0..n

0..nSubUoWDef

Dependent

Antecedent

Context : string [required]Name : string [required]Id : string [key]

UnitOfWorkDefinition

0..n w

1..1

StartedUoW

0..n

0..n

LogicalElementPerformsUoW

MetricDefinition

id : string [key]Name: string[required]DataType: uint16 [required]Calculable: uint16 [required]Units: stringValidity: uint16

0..n

0..n

UoWMetric

Value : string

UoWMetric0..n0..1

SubUoW

DependentAntecedent

0..n

0..n

LogicalElementUnitOfWorkDef

elapsed time hasresponse time ifUnitOfWork has

completed

ManagedElement

Caption: stringDescription string

BaseMetricDefinition

id : string [key]Name: string[required]DataType: uint16 [required]Calculable: uint16 [required]Units: string

id: string[key]defId: string[key]time: datetimeValue : string

BaseMetric

Name: stringDescription: stringCaption: string

StatisticalInformation

PolicyGroup

*

*

CIM_MetricValidityPolicy

1..n

0..n

CIM_UoWMetricDefinition

0..n

0..n

MetricDefForME

PolicyRule

1

0..n wMetricInstance

0..n

0..n

MetricForME

**CIM_MetricValidityPolicyGroup

The Metrics ModelThe Metrics Model



The Operations ClassesThe Operations Classes

• Assumes that operations are required against applications but they may be dynamic– Exist only when app exists– Time oriented, etc.

• Model the concept of an Operation• Separate definition from instances of operation• Allow operations to be attached to services• Separate operation parameters from operations

and allow late binding.


Operations ModelOperations Model

Operation

OperationDefinition

ManagedElement

MethodParameters

Service

OperationalService

ApplicationSystem

ServicOperationDefinition

AppOperationDefinition

SoftwareFeature

Associations for input, default

And output parametersSoftFeatureOperationDefinition

ServicOperationOperationn DefaultParms

OperationInstanceDefinition



The Operations ModelThe Operations Model

ApplicationSystem

IdentifyingNumber:stringProductName:stringVendor:stringVersion:stringName:string

SoftwareFeature

CIM_PolicyGroup

*

*

CIM_ApplicationSystemSoftwareFeature

OperationDefId [key]:uint64Name: stringImpact: uint16 (U/NC/C)Presentation: stringInputParameters: stringOutputParameters: string

OperationDefinition

*

*

CIM_OperationDefPreExecutionPolicy

*

*

ServiceOperationDefTimeout: uint64

*

*

ApplicationSystemOperationDefTimeout:uint64

*

*

SoftwareFeatureOperationDefTimeout:uint64

ManagedElement

Description: stringCaption: string

OperationalService

CreationClassName: string [key]Name: string [key]

CreationClassName: string [key]Name: string [key]StartMode: stringStarted: boolean

StartService(): uint32StopService(): uint32

Service

*

*

CIM_OperationDefPostExecutionPolicy

OperationId [key]:uint32OperationDefId [key]: uint32

VerifyOKToInvoke([IN] CIM_ManagedElement

Ref instanceId,[IN] CIM_MethodParameters Ref

inParms) :uint32)

Invoke([IN] CIM_ManagedElement


inParms,[OUT] CIM_MethodParmeters Ref

outParms) :uint32

VerifyInvocationResults([IN]CIM_ManagedElement ref instanceId,[IN] CIM_MethodParameters

inParms,[OUT] CIM_MethodParmeters

outParms):uint32

Operation

1..1 W

*

CIM_OperationInstanceDefinition

1..*

*

CIM_OperationOutParameters

1...*

*

CIM_OperationInParameters

MethodParameters

MethodParametersID: stringDescription: stringCaption: string

1..*

*

CIM_OperationDefaultInParameters

*

0..1

OperationDefDefaultInParameters

*

*CIM_OperationPreExecutionPolicy

*

*CIM_OperationPostExecutionPolicy

Timeout: uint16

ServiceOperation

Timeout: uint16

ApplicationSystemOperation

Timeout: uint16

SoftwareFeatureOperation

*

*

ServiceOperationTimeout: uint64

*

*

ApplicationSystemOperationTimeout:uint64 Operation

ApplicationSystem

*

*

SoftwareFeatureOperationTimeout:uint64

SoftwareFeature



RuntimeElement ModelRuntimeElement ModelAssociation

AggregationAssociation with WEAK reference

Inheritance

Aggregation with WEAK reference

w

w

* equivalent to: 0 .. n

Title : RuntimeElement Model Specification 2.6Filename : CIM_Runtime20010201.vsdAuthor : DMTF Application Working GroupDatetime : 200102011445445.050000+600Page 1 : Object Classes

CIM_LogicalElement

CIM_LogicalIdentityCIM_Synchronized*

* *

*

CIM_RuntimeElement

CreationClassName:stringName:stringSystemCreationClassName:stringSystemName:stringterminate():uint32

CreationClassName:stringName:stringStartMode:stringStarted:booleanSystemCreationClassName:stringSystemName:stringStartService():uint32StopService():uint32

CIM_Service CIM_ServiceComponent

CIM_RuntimeElementProvidesService

Name:stringStatus:stringUserStatus:stringCreationClassName:stringSystemCreationClassName:stringSystemName:stringRuntimeElementName:string

CIM_RuntimeState

OperationId [key]:uint32OperationDefId [key]: uint32

VerifyOKToInvoke([IN] CIM_ManagedElement


inParms) :uint32)

Invoke([IN] CIM_ManagedElement


inParms,[OUT] CIM_MethodParmeters Ref

outParms) :uint32

VerifyInvocationResults([IN]CIM_ManagedElement ref instanceId,[IN] CIM_MethodParameters

inParms,[OUT] CIM_MethodParmeters

outParms):uint32

Operation

CIM_RuntimeElementDesiredState

CIM_RuntimeElementCurrentState

CIM_RuntimeStateOperation

1

1 1

1

*

*

Name:stringRuntimeElementClass:string

CIM_RuntimeStateInfo

Name:stringVersion:stringSoftwareElementState:uint16SoftwareElementID:stringTargetOperatingSystem:uint16OtherTargetOS:stringManufacturer:stringBuildNumber:stringSerialNumber:stringCodeSet:stringIdentificationCode:stringLanguageEdition:string

CIM_SoftwareElement

CIM_RuntimeStateStateDependency

CIM_RuntimeElementSoftwareElementBind

Name:stringStrength: stringPrerequiste:booleanDependent: ref RuntimeStateAntecedent:ref RuntimeState

CIM_RuntimeStateStateDependency

CIM_RuntimeStateInstanceCIM_NextRuntimeState

0..1

1

*

w

CreationClassName:stringName:stringNameFormat:stringPrimaryOwnerContact:stringPrimaryOwnerName:stringRoles[]:string

CIM_SystemCIM_HostedRuntimElement

1

w*

0..1

1

*

1

*

*



Changes Made for CIM 2.5Changes Made for CIM 2.5

• Associating Services with Processes

• Expressing Nested Software Features

• Distinguishing Multiple Product Installations

• Additional Semantic for Properties

• Added value to CIM_ManagedElement.status

• Indicate unset value consistently for CIM_Setting


Associating Services with Associating Services with ProcessesProcesses

• CIM_ServiceProcess Association– Relates services and system

processes– Allow apps to determine

processes that represent a particular application

Process

CIM_ServiceProcess

Service

**


Expressing Nested Software Expressing Nested Software FeaturesFeatures

• CIM_SoftwareFeatureComponent– Models subordinate software feature

which are aggregated– Allows software features to be

contained within other software features

• Example– English/French dictionary within

dictionary

SoftwareFeatureCIM_SoftwareFeatureComponent

*

*


Distinguishing Multiple Distinguishing Multiple Product InstallationsProduct Installations

• Problem– A product could be installed multiple times on a

system– Previously model could not distinguish between

these separate installations

• Examples– Production and development installations


Multiple Product Installation(2)Multiple Product Installation(2)

• Added one new class and three new associations between the new class and existing classes– CIM InstalledProduct - new class, which represents the collection of Software Features

and Software Elements that make up an installed product. Various properties for distinguishing between multiple instances are defined.

– CIM InstalledProductImage - association that relates an arbitrary number of CIM InstalledProducts to one CIM Product. CIM InstalledProduct is on the “weak” side of the association because it has to have a CIM Product counterpart for being existent.

– CIM CollectedSoftwareFeatures - aggregation, which does for CIM InstalledProduct that CIM ProductSoftwareFeatures does for CIM Product. Aggregates the various CIM SoftwareFeatures into a CIM InstalledProduct and allows one e.g., to find all the product installations in which a software feature is represented.

– CIM CollectedSoftwareElements is an aggregation that collects various CIM SoftwareElements into a CIM InstalledProduct. This aggregation is used, e.g., to find all the product installations in which a software element is deployed.


Multiple Product Installation(3)Multiple Product Installation(3)


Additional Semantic for Additional Semantic for PropertiesProperties

• Added PropertyUsage as optional Qualifier

• Possible values:– Descriptive – describes element– Capability – inherent capability of element– Configuration – influences configuration– State – can be used to derive status– Metric – numeric representing statistic, etc.– CurretContext – determined by position in schema

• Provides additional meta-information for properties


Added value to Added value to CIM_ManagedElement.statusCIM_ManagedElement.status

• CIM_ManagedSystemElement.Status– Represents operational, administrative or usage status– Operational status such as “OK”, “degraded” …– Non Operational status such as “error”, “starting” …

• However no value to represent not activated• ADDED

– “Stopped”– Semantics are

• Exits but not operational (or)• Not encountered an error but purposely made non-operational


What is Next?

•Dormant for 4 Months•Merge of the Metrics and Application Groups•Immediate Objectives

•Finish the current models•Document the models

•How we want to work•Regular Telecons•Working Papers to define conclusions•At least one F2F

•It is up to the committee members


Lessons LearnedLessons Learned

• REALLY understanding the existing model is not easy.• If you do not understand the existing models you will

probably make a mess• Modeling is not easy• Complex modeling needs implementation early to test

the model• Changes can affect and demand changes to other

parts of the model• Sometimes the existing models do not allow reuse or

extension (ex. The changes made to V 2.5)


Q & A

?


Example

CustomerFirst Application...

IncidentTracker

Advance Graphic Package

Problem Manager

RelationalDBMS


CIM_Product

Caption = “CustomerFirst Support Product”Description = “ The product for everyone.”

Vendor = “First Always Co.”Name = “CustomerFirst”ProductNumber = “PROD-001”IdentificationNumber = “TYR-99-003”Version = “01.01.00”

CIM_SoftwareFeature

Caption = “Your Favorite Incident Manager”Description = “ The best.”

Vendor = “First Always Co.”ProductName = “CustomerFirst”ProductNumber = “PROD-001”IdentificationNumber = “TYR-99-003”Version = “01.01.00”Name = “Incident Trcker”

CIM_SoftwareFeature


Vendor = “First Always Co.”ProductName = “CustomerFirst”ProductNumber = “PROD-001”IdentificationNumber = “TYR-99-003”Version = “01.01.00”Name = “Advance Graphics Package”

CIM_SoftwareFeature

Caption = “Your Favorite Problem Tracker”Description = “ The best.”

Vendor = “First Always Co.”ProductName = “CustomerFirst”ProductNumber = “PROD-001”IdentificationNumber = “TYR-99-003”Version = “01.01.00”Name = “Problem Tracking”

CustomerFirst Features

instance of CIM_SoftwareFeature as $feat001{ Vendor = "First Always Co." ; ProductName = "CustomerFirst" ; ProductNumber = "PROD-001" ; IdentificationNumber = "TYR-99-003" ; Version = "01.01.00" ; Name = "Incident Tracker"; Caption = " Your Favorite Incident Manager"; Description = "The best." ; };

instance of CIM_SoftwareFeature as $feat001{ Vendor = "First Always Co." ; ProductName = "CustomerFirst" ; ProductNumber = "PROD-001" ; IdentificationNumber = "TYR-99-003" ; Version = "01.01.00" ; Name = "Incident Tracker"; Caption = " Your Favorite Incident Manager"; Description = "The best." ; };

instance of CIM_Product as $prod001{ Vendor = " First Always Co."; Name = "CustomerFirst"; ProductNumber = "PROD-001"; IdentifyingNumber = " TYR-99-003"; Caption = " CustomerFirst Support Product"; Description = "The product for everyone "; Version = "01.01.00"; };

instance of CIM_ProductSoftwareFeatures{ Product = $prod001 ; Component = $feat001 ; };


Incident Tracker Software Elements

CustomerFirst Application...

IncidentTracker

States

Platform Deployable Installable Executable Running

NT 1 1 1 1

Windows 95 1 1 1 1

Map out the software elements by platform


CIM_SoftwareFeature


Vendor = “First Always Co.”ProductName = “CustomerFirst”ProductNumber = “PROD-001”IdentificationNumber = “TYR-99-003”Version = “01.01.00”Name = “Incident Tracker”

CIM_SoftwareElememnt

Manufactuer = “First Always, Co,”SerialNumber = “ “LanguageEdition = “en”;

Name = “Incident Manager Element”TargetOperatingSystem = 17Version = “01.01.01”SoftwareElementState = 0;SoftwareElementID = “Definition”Version = “01.01.01”









Name = “Incident Manager ElementTargetOperatingSystem = 17Version = “01.01.01”SoftwareElementState = 1;SoftwareElementID = “Definition”Version = “01.01.01”

Software Elements for Incident Tracker Feature on NT

Some Software Elements


Software Element Keys



Name = “Incident Manager ElementVersion = “01.01.01”

TargetOperatingSystem = 17SoftwareElementState = 1

SoftwareElementID = “Definition”

Basics

Platform and State Cross Product

Instance Specific


Feature Platform Details Deployable Installable Executable Running

Version 3.5.1 3.5.1

NT Disk Space .75 MB 2 MB 15 MB 3 MB

Memory 8 MB 32 MB

Incident Software Oracle Oracle

Manager Version

Win. 95 Disk Space .75 MB 2 MB 15 MB 3 MB

Memory 8 MB 32 MB

Software Oracle Oracle

Version

NT Disk Space 1 KB 5 KB 1 MB

Advance Memory

Graphics Software Excel

Probl. Tracker

Package Version

Win. 95 Disk Space 1 KB 5 KB 1 MB

Memory

Software Excel

Probl. Tracker

Software Element ConditionsSoftware Element Conditions

Version row refers to the operating system version required by the software element in the specified state,

Disk space row refers to the minimum amount of disk space required to transition in the specified state,

Memory row refers to the minimum amount of memory required to transition into the specified state,

Software row refers to the software elements that are expect to exist for the software element in the specified state.




Name = “IM. On NT in Inst. State”TargetOperatingSystem = 17Version = “01.01.01”SoftwareElementState = 1;SoftwareElementID = “Definition”Version = “01.01.01”

CIM_DirectorySpecification

Description = “ ”Caption = “ ”CheckMode = “ ”DirectoryType = 000;DirectoryPath = “ \”

Name = “IM. On NT in Inst. State ”TargetOperatingSystem = 17Version = “01.01.01”SoftwareElementState = 1;SoftwareElementID = “Definition”Version = “01.01.01”CheckID = “Master Directory”

In-State

CIM_FileSpecification

Description = ““Caption = ““CheckMode = ““Name = “custfir.bmp“CreateTimeStamp = “199704201048**.*******-300” ;FileSize = 30218 ; // kilobytes

Name = “IM. On NT in Inst. State ”TargetOperatingSystem = 17Version = “01.01.01”SoftwareElementState = 2;SoftwareElementID = “Definition”Version = “01.01.01”CheckID = “OS VersionCheck”

























In-State

More on ChecksMore on Checks

Files/Directory are expected conditions in an environment.

Documents

DMTF Developers Conference1Page June 13 2001 Application Model & Metrics Model Update June 2001 Karl Schopmeyer The Open Group [email protected]