Find Telecommunication Device operation
The Find Telecommunication Device operation retrieves the details of a telecommunication device.
The following table describes the elements of the <items>
XML element and the adapter request. If not specified, the valid value for an element should be assumed to be a string.
Elements for the <items> XML element and adapter request for the Find Telecommunication Device operation
Element |
Definition |
Required |
---|---|---|
|
Specifies the name of the operation: |
Yes |
|
Contains the other elements in the request |
Yes |
|
Contains elements that uniquely identify a record |
Yes |
|
Specifies a unique name for identifying a telecommunication device |
No |
|
Specifies a unique storage item record |
Yes |
|
Specifies the attributes for a telecommunication device |
Yes |
|
Specifies the status of the telecommunication device item
|
No |
|
Specifies the assignment group for the telecommunication device |
No |
|
Specifies the name of the vendor for the telecommunication device |
No |
|
Specifies the serial number of the telecommunication device |
No |
|
Specifies the location of the telecommunication device |
No |
|
Specifies the type of the configuration item |
No |
|
Specifies the part number related to the telecommunication device |
No |
|
Specifies the version of the telecommunication device |
No |
|
Specifies the model of the telecommunication device item |
No |
|
Specifies the name of the person who last updated the record |
No |
|
Specifies the subtype for a selected type for a configuration item
|
No |
|
Specifies the building for the telecommunication device |
No |
|
Specifies the floor related to the location |
No |
|
Specifies information about the room |
No |
|
Specifies whether the system is down
|
No |
|
Specifies the asset for the record |
No |
|
Specifies the name of the company |
No |
|
Specifies the system time when the record was last modified |
No |
|
Specifies the user name that last modified the record |
No |
|
Specifies the number of times the record was modified |
No |
|
Specifies the environment of the telecommunication device
|
No |
|
Specifies the department that owns the telecommunication device |
No |
|
Specifies the default impact of the telecommunication device
|
No |
|
Specifies the title for the telecommunication device |
No |
|
Specifies the priority of the telecommunication device
|
No |
|
Specifies the ID of the telecommunication device |
No |
|
Contains child elements for describing the telecommunication device; is a structure-type element |
Yes |
The following figure displays a sample adapter request for the Find Telecommunication Device operation.
Sample adapter request for the Find Telecommunication Device operation
<hp-service-manager-request>
<entity>configurationitem</entity>
<entity-type>telecommunication-device</entity-type>
<request>
<operation-name>retrieve-telecommunication-device</operation-name>
<parameters>
<retrieve-telecommunication-device-request>
<model>
<keys>
<logical-name>
<value>TD-010</value>
<type>String</type>
</logical-name>
</keys>
<instance>
<file-device>
<type>Structure</type>
<istatus>
<value>Received</value>
<type>String</type>
</istatus>
<vendor>
<value>Compaq</value>
<type>String</type>
</vendor>
<model>
<value>2011</value>
<type>String</type>
</model>
<serial-no>
<value>Sr no</value>
<type>String</type>
</serial-no>
<location>
<value>Asia</value>
<type>String</type>
</location>
<configuration-item-type>
<value>telecom</value>
<type>String</type>
</configuration-item-type>
<id>
<value>CI10893</value>
<type>String</type>
</id>
<updated-by>
<value>falcon</value>
<type>String</type>
</updated-by>
<part-no>
<value>1007</value>
<type>String</type>
</part-no>
<version>
<value>V 1.1</value>
<type>String</type>
</version>
<subtype>
<value>Desk Phone</value>
<type>String</type>
</subtype>
<location-code>
<value>advantageasia</value>
<type>String</type>
</location-code>
<vendor-id>
<value>CPQ</value>
<type>String</type>
</vendor-id>
<floor>
<value>2</value>
<type>String</type>
</floor>
<room>
<value>Delta</value>
<type>String</type>
</room>
<problem-priority>
<value>1</value>
<type>String</type>
</problem-priority>
<assignment>
<value>Application</value>
<type>String</type>
</assignment>
<title>
<value>Title of the Furnishing</value>
<type>String</type>
</title>
<environment>
<value>Development</value>
<type>String</type>
</environment>
<owner>
<value>D-0001</value>
<type>String</type>
</owner>
<default-impact>
<value>1</value>
<type>Decimal</type>
</default-impact>
</file-device>
<sysmodtime>
<value>2010.02.03 11:48:32</value>
<type>DateTime</type>
</sysmodtime>
<sysmodcount>
<value>2</value>
<type>Decimal</type>
</sysmodcount>
<sysmoduser>
<value>falcon</value>
<type>String</type>
</sysmoduser>
<file-telecom>
<type>Structure</type>
</file-telecom>
</instance>
</model>
</retrieve-telecommunication-device-request>
</parameters>
</request>
</hp-service-manager-request>
The following figure displays an adapter response for the Find Telecommunication Device operation.
Sample adapter response for the Find Telecommunication Device operation
<hp-service-manager-response>
<metadata>
<count>1</count>
</metadata>
<responses>
<response>
<metadata>
<count>1</count>
</metadata>
<item>
<metadata>
<status>success</status>
</metadata>
<parameters>
<model>
<keys>
<logical-name>
<value>TD-010</value>
<type>String</type>
</logical-name>
</keys>
<instance>
<file-device>
<type>Structure</type>
<vendor>
<value>Compaq</value>
<type>String</type>
</vendor>
<model>
<value>2011</value>
<type>String</type>
</model>
<serial-no>
<value>Sr no</value>
<type>String</type>
</serial-no>
<location>
<value>Asia</value>
<type>String</type>
</location>
<group>
<value>grp</value>
<type>String</type>
</group>
<configuration-item-type>
<value>telecom</value>
<type>String</type>
</configuration-item-type>
<id>
<value>CI10893</value>
<type>String</type>
</id>
<updated-by>
<value>falcon</value>
<type>String</type>
</updated-by>
<description>
<value>description</value>
<type>String</type>
</description>
<part-no>
<value>1007</value>
<type>String</type>
</part-no>
<istatus>
<value>Received</value>
<type>String</type>
</istatus>
<version>
<value>V 1.1</value>
<type>String</type>
</version>
<subtype>
<value>Desk Phone</value>
<type>String</type>
</subtype>
<location-code>
<value>advantageasia</value>
<type>String</type>
</location-code>
<vendor-id>
<value>CPQ</value>
<type>String</type>
</vendor-id>
<building>
<value>building</value>
<type>String</type>
</building>
<floor>
<value>2</value>
<type>String</type>
</floor>
<room>
<value>Delta</value>
<type>String</type>
</room>
<sysmodtime>
<value>2010.02.10 17:49:12</value>
<type>DateTime</type>
</sysmodtime>
<sysmodcount>
<value>2</value>
<type>Decimal</type>
</sysmodcount>
<sysmoduser>
<value>falcon</value>
<type>String</type>
</sysmoduser>
<problem-priority>
<value>1</value>
<type>String</type>
</problem-priority>
<assignment>
<value>Application</value>
<type>String</type>
</assignment>
<location-comments>
<type>Array</type>
<location-comments>
<element>
<value>location comment1</value>
<type>String</type>
</element>
<element>
<value>location comment2</value>
<type>String</type>
</element>
</location-comments>
</location-comments>
<title>
<value>Title of the Furnishing</value>
<type>String</type>
</title>
<environment>
<value>Development</value>
<type>String</type>
</environment>
<owner>
<value>D-0001</value>
<type>String</type>
</owner>
<default-impact>
<value>1</value>
<type>Decimal</type>
</default-impact>
</file-device>
<file-telecom>
<type>Structure</type>
<sysmodtime>
<value>2010.02.10 17:49:12</value>
<type>DateTime</type>
</sysmodtime>
<sysmoduser>
<value>falcon</value>
<type>String</type>
</sysmoduser>
<sysmodcount>
<value>1</value>
<type>Decimal</type>
</sysmodcount>
</file-telecom>
<uniquequery>file.device,logical.name="TD-010"</uniquequery>
</instance>
</model>
<status>SUCCESS</status>
<message>Success</message>
<schema-revision-date>2005.03.15 00:00:00</schema-revision-date>
<schema-revision-level>1</schema-revision-level>
<return-code>0</return-code>
</parameters>
</item>
</response>
</responses>
</hp-service-manager-response>
Comments
Log in or register to comment.