Find Site Component Status operation
The Find Site Component Status operation finds the status of a site component.
The following table describes the <items> XML elements for the Find Site Component Status operation:
Elements for the <items> XML element and adapter request for the Find Site Component Status operation
The following figure shows a sample adapter request for the Find Site Component Status operation:
Sample adapter request for the Find Site Component Status operation
<mssccm-request>
<operation-name>find-site-component-status</operation-name>
<arguments>
<target>config1</target>
<availability-state>Unknown</availability-state>
<component-name>SMS_WSUS_CONTROL_MANAGER</component-name>
<component-type>Monitored Thread Component</component-type>
<errors>56</errors>
<heartbeat-interval>0</heartbeat-interval>
<information>33</information>
<last-status-message>20110107144711.000000+***</last-status-message>
<last-heartbeat />
<last-started />
<site-system>machine</site-system>
<next-scheduled-time />
<site-code>123</site-code>
<thread-state>STARTED</thread-state>
<status>Critical</status>
<tally-interval>0201128000100008</tally-interval>
<startup-type>AUTOSTARTING</startup-type>
<warning>0</warning>
</arguments>
</mssccm-request>
<operation-name>find-site-component-status</operation-name>
<arguments>
<target>config1</target>
<availability-state>Unknown</availability-state>
<component-name>SMS_WSUS_CONTROL_MANAGER</component-name>
<component-type>Monitored Thread Component</component-type>
<errors>56</errors>
<heartbeat-interval>0</heartbeat-interval>
<information>33</information>
<last-status-message>20110107144711.000000+***</last-status-message>
<last-heartbeat />
<last-started />
<site-system>machine</site-system>
<next-scheduled-time />
<site-code>123</site-code>
<thread-state>STARTED</thread-state>
<status>Critical</status>
<tally-interval>0201128000100008</tally-interval>
<startup-type>AUTOSTARTING</startup-type>
<warning>0</warning>
</arguments>
</mssccm-request>
The following figure shows the adapter response for the sample request:
Sample adapter response for the Find Site Component Status operation
<mssccm-response>
<metadata>
<response-count>1</response-count>
<status>success</status>
</metadata>
<responses>
<response>
<metadata>
<target>config1</target>
<status>success</status>
<count>1</count>
</metadata>
<output>
<availability-state>Unknown</availability-state>
<component-name>SMS_WSUS_CONTROL_MANAGER</component-name>
<component-type>Monitored Thread Component</component-type>
<errors>56</errors>
<heartbeat-interval>0</heartbeat-interval>
<information>33</information>
<last-status-message>20110107144711.000000+***</last-status-message>
<last-heartbeat />
<last-started />
<site-system>machine</site-system>
<next-scheduled-time />
<site-code>123</site-code>
<thread-state>STARTED</thread-state>
<status>Critical</status>
<tally-interval>0201128000100008</tally-interval>
<startup-type>AUTOSTARTING</startup-type>
<warning>0</warning>
</output>
</response>
</responses>
</mssccm-response>
<metadata>
<response-count>1</response-count>
<status>success</status>
</metadata>
<responses>
<response>
<metadata>
<target>config1</target>
<status>success</status>
<count>1</count>
</metadata>
<output>
<availability-state>Unknown</availability-state>
<component-name>SMS_WSUS_CONTROL_MANAGER</component-name>
<component-type>Monitored Thread Component</component-type>
<errors>56</errors>
<heartbeat-interval>0</heartbeat-interval>
<information>33</information>
<last-status-message>20110107144711.000000+***</last-status-message>
<last-heartbeat />
<last-started />
<site-system>machine</site-system>
<next-scheduled-time />
<site-code>123</site-code>
<thread-state>STARTED</thread-state>
<status>Critical</status>
<tally-interval>0201128000100008</tally-interval>
<startup-type>AUTOSTARTING</startup-type>
<warning>0</warning>
</output>
</response>
</responses>
</mssccm-response>
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*