Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "CMDBf Graph Reponse Viewer"

(CMDBf Graph Response Viewer)
Line 6: Line 6:
 
[[Image:cosmos_cmdbfviewer.jpg]]
 
[[Image:cosmos_cmdbfviewer.jpg]]
  
The properties view displays the property names and values of a selected item within a table.  The user can select an item using other web componentsFor example, the user can select a node within the [[Data Manager Navigator]] as shown below.
+
The CMDBf Graph Response Viewer contains two sections.  The top sections is composed of a table that shows the list of nodes and edges.  The first column of the table lists the set of sources nodes, the second column lists the edges while the third column lists the target.  As a result, the user can determine how the nodes relate to each other by viewing this tableThe user can select a template id from the drop down box to filter the nodes and edges shown in the table.
  
[[Image:cosmos_propnav.jpg]]
+
The detail section shown at the bottom of the view displays the contents of a particular item or edge that is selected in the above table.  The detail section shows the templateId, mdrId and localId of the selected item.  The table shown below displays the list of records associated with the item or relationship. 
 +
 
 +
Let us look at how the CMDBf graph response viewer visualizes the following CMDBf graph response document.
 +
 
 +
<pre>
 +
<queryResult>
 +
<nodes templateId="user">
 +
<item>
 +
<record xmlns:hr="http://example.com/people">
 +
<hr:ContactInfo>
 +
<hr:name>Pete the Lab Tech</hr:name>
 +
<hr:phone>111-111-1111</hr:phone>
 +
<hr:employeeNumber>33333</hr:employeeNumber>
 +
</hr:ContactInfo>
 +
<recordMetadata>
 +
<recordId>
 +
http://example.com/33333/Current
 +
</recordId>
 +
</recordMetadata>
 +
</record>
 +
<instanceId>
 +
<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
 +
<localId>http://example.com/PeteTheLabTech</localId>
 +
</instanceId>
 +
</item>
 +
</nodes>
 +
<nodes templateId="computer">
 +
<item>
 +
<record xmlns:comp="http://example.com/computerModel">
 +
<comp:ComputerConfig>
 +
<comp:CPUType>AMD Athlon 64</comp:CPUType>
 +
<comp:assetTag>XYZ9753</comp:assetTag>
 +
<comp:primaryMACAddress>
 +
00A4B49D2F41
 +
</comp:primaryMACAddress>
 +
<comp:name>LabMachineA</comp:name>
 +
</comp:ComputerConfig>
 +
<recordMetadata>
 +
<recordId>
 +
http://example.com/machines/XYZ9753/scanned
 +
</recordId>
 +
</recordMetadata>
 +
</record>
 +
<instanceId>
 +
<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
 +
<localId>http://example.com/machines/XYZ9753</localId>
 +
</instanceId>
 +
</item>
 +
<item>
 +
<record xmlns:comp="http://example.com/computerModel">
 +
<comp:ComputerConfig>
 +
<comp:CPUType>AMD Athlon 64</comp:CPUType>
 +
<comp:assetTag>XYZ9876</comp:assetTag>
 +
<comp:primaryMACAddress>
 +
00A4B49D2F42
 +
</comp:primaryMACAddress>
 +
<comp:name>LabMachineB</comp:name>
 +
</comp:ComputerConfig>
 +
<recordMetadata>
 +
<recordId>
 +
http://example.com/machines/XYZ9876/scanned
 +
</recordId>
 +
</recordMetadata>
 +
</record>
 +
<instanceId>
 +
<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
 +
<localId>http://example.com/machines/XYZ9876</localId>
 +
</instanceId>
 +
</item>
 +
</nodes>
 +
<edges templateId="administers">
 +
<relationship>
 +
<source>
 +
<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
 +
<localId>http://example.com/PeteTheLabTech</localId>
 +
</source>
 +
<target>
 +
<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
 +
<localId>http://example.com/machines/XYZ9876</localId>
 +
</target>
 +
<record xmlns:foo="http://example.com/computerModel">
 +
<foo:administers>
 +
<foo:adminSupportHours>
 +
business hours only
 +
</foo:adminSupportHours>
 +
</foo:administers>
 +
<recordMetadata>
 +
<recordId>adm10001</recordId>
 +
</recordMetadata>
 +
</record>
 +
<instanceId>
 +
<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
 +
<localId>
 +
http://example.com/administers/PeteTheLabTechToLabMachineB
 +
</localId>
 +
</instanceId>
 +
</relationship>
 +
<relationship>
 +
<source>
 +
<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
 +
<localId>http://example.com/PeteTheLabTech</localId>
 +
</source>
 +
<target>
 +
<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
 +
<localId>http://example.com/machines/XYZ9753</localId>
 +
</target>
 +
<record xmlns:foo="http://example.com/computerModel">
 +
<foo:administers>
 +
<foo:adminSupportHours>24/7</foo:adminSupportHours>
 +
</foo:administers>
 +
<recordMetadata>
 +
<recordId>adm10002</recordId>
 +
</recordMetadata>
 +
</record>
 +
<instanceId>
 +
<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
 +
<localId>
 +
http://example.com/administers/PeteTheLabTechToLabMachineA
 +
</localId>
 +
</instanceId>
 +
</relationship>
 +
</edges>
 +
</queryResult>
 +
</pre>

Revision as of 23:03, 7 March 2008

COSMOS Wiki > COSMOS Document Plan > COSMOS Manual Guide > COSMOS_UG_Web_Component_Library

CMDBf Graph Response Viewer

Purpose: This view visualize the structure of a CMDBf response document.

Cosmos cmdbfviewer.jpg

The CMDBf Graph Response Viewer contains two sections. The top sections is composed of a table that shows the list of nodes and edges. The first column of the table lists the set of sources nodes, the second column lists the edges while the third column lists the target. As a result, the user can determine how the nodes relate to each other by viewing this table. The user can select a template id from the drop down box to filter the nodes and edges shown in the table.

The detail section shown at the bottom of the view displays the contents of a particular item or edge that is selected in the above table. The detail section shows the templateId, mdrId and localId of the selected item. The table shown below displays the list of records associated with the item or relationship.

Let us look at how the CMDBf graph response viewer visualizes the following CMDBf graph response document.

<queryResult>
	<nodes templateId="user">
		<item>
			<record xmlns:hr="http://example.com/people">
				<hr:ContactInfo>
					<hr:name>Pete the Lab Tech</hr:name>
					<hr:phone>111-111-1111</hr:phone>
					<hr:employeeNumber>33333</hr:employeeNumber>
				</hr:ContactInfo>
				<recordMetadata>
					<recordId>
						http://example.com/33333/Current
					</recordId>
				</recordMetadata>
			</record>
			<instanceId>
				<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
				<localId>http://example.com/PeteTheLabTech</localId>
			</instanceId>
		</item>
	</nodes>
	<nodes templateId="computer">
		<item>
			<record xmlns:comp="http://example.com/computerModel">
				<comp:ComputerConfig>
					<comp:CPUType>AMD Athlon 64</comp:CPUType>
					<comp:assetTag>XYZ9753</comp:assetTag>
					<comp:primaryMACAddress>
						00A4B49D2F41
					</comp:primaryMACAddress>
					<comp:name>LabMachineA</comp:name>
				</comp:ComputerConfig>
				<recordMetadata>
					<recordId>
						http://example.com/machines/XYZ9753/scanned
					</recordId>
				</recordMetadata>
			</record>
			<instanceId>
				<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
				<localId>http://example.com/machines/XYZ9753</localId>
			</instanceId>
		</item>
		<item>
			<record xmlns:comp="http://example.com/computerModel">
				<comp:ComputerConfig>
					<comp:CPUType>AMD Athlon 64</comp:CPUType>
					<comp:assetTag>XYZ9876</comp:assetTag>
					<comp:primaryMACAddress>
						00A4B49D2F42
					</comp:primaryMACAddress>
					<comp:name>LabMachineB</comp:name>
				</comp:ComputerConfig>
				<recordMetadata>
					<recordId>
						http://example.com/machines/XYZ9876/scanned
					</recordId>
				</recordMetadata>
			</record>
			<instanceId>
				<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
				<localId>http://example.com/machines/XYZ9876</localId>
			</instanceId>
		</item>
	</nodes>
	<edges templateId="administers">
		<relationship>
			<source>
				<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
				<localId>http://example.com/PeteTheLabTech</localId>
			</source>
			<target>
				<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
				<localId>http://example.com/machines/XYZ9876</localId>
			</target>
			<record xmlns:foo="http://example.com/computerModel">
				<foo:administers>
					<foo:adminSupportHours>
						business hours only
					</foo:adminSupportHours>
				</foo:administers>
				<recordMetadata>
					<recordId>adm10001</recordId>
				</recordMetadata>
			</record>
			<instanceId>
				<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
				<localId>
					http://example.com/administers/PeteTheLabTechToLabMachineB
				</localId>
			</instanceId>
		</relationship>
		<relationship>
			<source>
				<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
				<localId>http://example.com/PeteTheLabTech</localId>
			</source>
			<target>
				<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
				<localId>http://example.com/machines/XYZ9753</localId>
			</target>
			<record xmlns:foo="http://example.com/computerModel">
				<foo:administers>
					<foo:adminSupportHours>24/7</foo:adminSupportHours>
				</foo:administers>
				<recordMetadata>
					<recordId>adm10002</recordId>
				</recordMetadata>
			</record>
			<instanceId>
				<mdrId>http://testSystem.com/DiscoveryMdr</mdrId>
				<localId>
					http://example.com/administers/PeteTheLabTechToLabMachineA
				</localId>
			</instanceId>
		</relationship>
	</edges>
</queryResult>

Back to the top