1 karl 1.1.2.2 // Copyright (c) 2007 DMTF. All rights reserved.
2 [Version ( "2.7.0" ),
3 UMLPackagePath ( "CIM::Metrics::UnitOfWork" ),
4 Description (
5 "A LogicalElement that describes units of work (e.g. "
6 "transactions). This class represents the definitional "
7 "components of a unit of work, and not the unit itself." )]
8 class CIM_UnitOfWorkDefinition : CIM_LogicalElement {
9
10 [Override ( "Name" ),
11 Description (
12 "The name of the Definition. This name does not have to "
13 "be unique, but should be descriptive. It may contain "
14 "blanks." )]
15 string Name;
16
17 [Description (
18 "A free format string describing the context of the "
19 "defined UnitOfWork. For example an \'Add Order\' Unit "
20 "could be defined in the context of a book ordering "
21 "application, whereas another \'Add Order\' UnitOfWork "
22 karl 1.1.2.2 "could be defined for a computer ordering application. It "
23 "may contain blanks." )]
24 string Context;
25
26 [Key, Description (
27 "A 16 byte value that uniquely identifies the UnitOfWork "
28 "Definition. The use of OSF UUID/GUIDs is recommended." ),
29 MaxLen ( 16 )]
30 string Id;
31
32 [Description (
33 "A 16 byte value that uniquely identifies the applied "
34 "semantics and format of the trace levels used in the "
35 "instances of UnitOfWork. The use of OSF UUID/GUIDs is "
36 "recommended. \n"
37 "TraceLevelTypeId allows management applications to "
38 "efficiently discriminate between different trace level "
39 "semantics of different UnitOfWorkDefinitions. I.E., "
40 "CIM_UnitOfWork.TraceLevel = 1 may have different "
41 "semantics if TraceLevelTypeId is different for the "
42 "respective instances of UnitOfWork. \n"
43 karl 1.1.2.2 "It is not assumed that different trace level semantics "
44 "are used within the same UnitOfWorkDefinition in order "
45 "to promote uniform trace level encodings. (Keep in mind: "
46 "At least the developers of the business actions "
47 "represented by the same UnitOfWorkDefinition instance "
48 "should strive to use the same trace level encoding, "
49 "otherwise the administrator will have a hard time to "
50 "figure out what detailed information to expect.) \n"
51 "If the string is empty no traces are expected to be "
52 "produced. If the string is not empty, an associated "
53 "instance of TraceLevelType may be attached to the "
54 "UnitOfWorkDefinition instance. Still, it is useful to "
55 "incorporate TraceLevelTypeId into UnitOfWorkDefinition, "
56 "to relate to an instance of TraceLevelType. The "
57 "management application can more easily detect different "
58 "trace level types." ),
59 MaxLen ( 16 ),
60 ModelCorrespondence { "CIM_TraceLevelType.InstanceID" }]
61 string TraceLevelTypeId;
62
63
64 karl 1.1.2.2 };
|