HP Matrix Operating Environment Software manual Data Model

4 Data Model

The complex data types that are used in the API operation definitions are defined here.

The Service data model incorporates many of the data types defined here. Figure 2 (page 48) shows the relationships between the major data types from a Service perspective, using Unified Modeling Language (UML) notation. Some of the data classes are separated into “Info” and “Details” classes, where the Details class extends the Info class. For example, the Service data type shown in Figure 2 represents the ServiceDetails class which extends ServiceInfo. This separation allows some operations (such as List) to return high-level data and others (like Get) to return deep containment data.

Figure 2 Service Data Model

The data model is designed to avoid indirect references. This design is intended to simplify data processing and it allows Service subcomponents, such as LogicalServer, to be self-contained. An outcome of this choice is that Service data may contain redundant components. For example, all the LogicalServers in a group may contain information about the same logical subnet.

Enumerated types are modeled with a structure that contains an enumeration value (with OTHER as a possible value) and an “other” string (which is used when the enumeration value is OTHER). The use of an explicit enumeration allows the set of possible values to be clearly defined in the WSDL. The inclusion of an OTHER value allows future extensions to the enumeration to be represented in this data model.

48 Data Model