Integration Schemas
Integration XML and Schemas 83
These elements are referenced in service level schemas and only the MXPERSON
and MXPERSONSet can be outside the context of a service level schema. For
example, internal applications such as Deployment Manager use schemas
comparable to MXPERSON and MXPERSONSet. Integration users must use
object structure services within the context of a service level schema.
Object content The following content is in the object element:
T Element MXPERSON has type MXPERSONType
T Complex type MXPERSONType has element PERSON (object name), which
has type MXPERSON_PERSONType.
T Complex type MXPERSON_PERSONType has elements for all the configured
attributes of the PERSON object and elements for the child objects in the
object structure (PHONE, EMAIL, and SMS).
T Additional objects in the schema have a corresponding complex type like
MXPERSON_PERSONType, that defines the PERSON object.
The following example shows the structure of the corresponding XML:
<MXPERSON>
<PERSON>
<PHONE>
</PHONE>
.
.
<EMAIL>
</EMAIL>.
.
.
<SMS>
</SMS>
.
.
</PERSON>
</MXPERSON>
Object set content For the preceding MXPERSON example, MXPERSONSet replaces the
MXPERSON element and MXPERSONSetType replaces the complex type
MXPERSONType. Everything else remains the same.
Object Type
PHONE MXPERSON_PHONEType
EMAIL MXPERSON_EMAILType
SMS MXPERSON_SMSType
To Next Page
Loading...