The following input XML describes the input message XML for a DDR message.

<Report>

    <ReportHeader>

        <Identification>

            <Machine>

                <ClientInstalled></ClientInstalled>

                <ClientType></ClientType>

                <ClientID></ClientID>

                <ClientVersion></ClientVersion>

                <NetBIOSName></NetBIOSName>

                <CodePage></CodePage>

                <SystemDefaultLCID></SystemDefaultLCID>

            </Machine>

        </Identification>

        <ReportDetails>

            <ReportContent></ReportContent>

            <ReportType></ReportType>

            <Date></Date>

            <Version></Version>

            <Format></Format>

        </ReportDetails>

        <InventoryAction>

            <InventoryActionID></InventoryActionID>

            <Description>Discovery</Description>

            <InventoryActionLastUpdateTime></InventoryActionLastUpdateTime>

        </InventoryAction>

    </ReportHeader>

    <ReportBody>

        <Instance>

            <WMIClass>

                <Property></Property>

            </WMIClass >

        </Instance>

    </ReportBody>

</Report>

The DDR endpoint XML schema is split into two parts: a header and a body. The header contains information that identifies the client and other report details. The body contains the actual report data. The body is constructed from one or more Instance elements. Each instance represents a discovery property. An instance contains an element with the same logical name as the reported Windows Management Instrumentation (WMI) class, which itself contains one or more elements containing property data. The property data names are used to create the DDR and correspond with the logical defined property names for the corresponding resource type ( sms_r_system, sms_r_user or sms_r_usergroup) reported properties.

The literal text value of the property name does not necessarily match the equivalent DDR or WMI literal text value. It does match logically, however. For example, "MACAddress" matches in meaning but not in literal string value with "MAC Address" in the DDR or with "MACAddresses" in SMS_R_System.

The element data is the textual representation of the property value. (Element name WMIClass is used in this documentation to represent the resource). The resource name is the same as that found in the SMS Provider within sms_r_system, sms_r_user or sms_r_usergroup.

There is no XML returned.

You use ISmsMessaging::Post Method to pass the message to the data discovery record manager endpoint, MP_DdrEndpoint. You set the target endpoint with ISmsMessage::SetTargetEndpoint Method.

The report header is passed in Post.pRequest parameter. The report body is passed by using ISmsMessageAttachment Interface. The report body attachment must be named {00000000-0000-0000-0000-000000000003}.

The following security flags can be applied to the message:

Security Mode	Required	Optional
Mixed	MPAPI_SECURITY_FLAG_MIXED_MODE MPAPI_SECURITY_FLAG_SIGN_MESSAGE.	MPAPI_SECURITY_FLAG_ENCRYPT_MESSAGE
Native	MPAPI_SECURITY_FLAG_NATIVE_MODE MPAPI_SECURITY_FLAG_SIGN_MESSAGE	MPAPI_SECURITY_FLAG_ENABLE_CRL_CHECKING

Use ISmsMessage4::SetSecurityFlags Method to set the security flags for the message.

For information about MPAPI security flags, see MPAPI_SECURITY_FLAGS Enumeration.

Other Resources

Configuration Manager Management Point Interface
Configuration Manager Management Point Message Schema