Cisco Prime Central 1.0 API Guide
|
|
- Valentine Gregory
- 6 years ago
- Views:
Transcription
1 Cisco Prime Central 1.0 API Guide Cisco Prime Central API Cisco Prime Central Information Model and API's to support the following features. Managed Elements and Equipment Inventory Object Create, Delete and Update notification Cisco Prime Central Information Model is designed to conform to MTOSI 2.0 information model and operational API's. Cisco reference implementation extensions are introduced to support proprietary APIs and name space as per Cisco PRIME Release 1 requirements. The sections below documents all the APIs supported by Cisco Prime Central and the information on how to get the corresponding WSDL document. getallmanagedelementnames WSDL document can be obtained by following URL ManagedElementNamesRetrieval_RPC?wsdl Where primecentralserver is the hostname or IP address of Prime Central Server and mtosiport is the port number where CXF service for mtosi is running. By default port number is 9110 <?xml version="1.0" encoding="utf-8"?> - <wsdl:definitions name="managedelementnamesretrievalrpcservice" targetnamespace=" xmlns:ns1=" xmlns:ns2=" xmlns:soap=" xmlns:tns=" xmlns:wsdl=" xmlns:xsd=" - <wsdl:types> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 124
2 - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:ns1=" xmlns:tns=" xmlns:xs=" <xs:import namespace=" /> - <xs:element name="header"> <xs:element minoccurs="0" name="activityname" type="xs:string" /> <xs:element minoccurs="0" name="msgname" type="xs:string" /> <xs:element minoccurs="0" name="msgtype" type="tns:messagetypetype" /> <xs:element minoccurs="0" name="senderuri" type="xs:anyuri" /> <xs:element minoccurs="0" name="destinationuri" type="xs:anyuri" /> <xs:element minoccurs="0" name="replytouri" type="xs:anyuri" /> <xs:element minoccurs="0" name="originatoruri" type="xs:anyuri" /> <xs:element minoccurs="0" name="failurereplytouri" type="xs:anyuri" /> <xs:element minoccurs="0" name="activitystatus" type="tns:activitystatustype" /> <xs:element minoccurs="0" name="correlationid" type="xs:string" /> <xs:element minoccurs="0" name="security" type="xs:string" /> <xs:element minoccurs="0" name="securitytype" type="xs:string" /> <xs:element minoccurs="0" name="priority" type="xs:string" /> - <xs:element minoccurs="0" name="msgspecificproperties"> - <xs:element maxoccurs="unbounded" minoccurs="0" name="property" nillable="true"> <xs:element name="propname" type="xs:string" /> <xs:element name="propvalue" type="xs:string" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 124
3 <xs:element minoccurs="0" name="communicationpattern" type="tns:communicationpatterntype" /> <xs:element minoccurs="0" name="communicationstyle" type="tns:communicationstyletype" /> <xs:element minoccurs="0" name="requestedbatchsize" type="xs:unsignedint" /> <xs:element minoccurs="0" name="batchsequencenumber" type="xs:unsignedint" /> <xs:element minoccurs="0" name="batchsequenceendofreply" type="xs:boolean" /> <xs:element minoccurs="0" name="iteratorreferenceuri" type="xs:anyuri" /> <xs:element minoccurs="0" name="filelocationuri" type="xs:anyuri" /> <xs:element minoccurs="0" name="compressiontype" type="tns:compressiontypetype" /> <xs:element minoccurs="0" name="packingtype" type="tns:packingtypetype" /> <xs:element minoccurs="0" name="timestamp" type="xs:datetime" /> <xs:element minoccurs="0" name="vendorextensions" type="ns1:anylisttype" /> - <xs:complextype name="activitystatustype"> - <xs:simplecontent> - <xs:extension base="tns:activitystatusenumtype"> <xs:attribute name="qualifier" type="xs:string" /> </xs:simplecontent> - <xs:complextype name="compressiontypetype"> - <xs:simplecontent> - <xs:extension base="tns:compressionenumtype"> <xs:attribute name="extension" type="xs:string" /> </xs:simplecontent> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 3 of 124
4 - <xs:complextype name="packingtypetype"> - <xs:simplecontent> - <xs:extension base="tns:packingenumtype"> <xs:attribute name="extension" type="xs:string" /> </xs:simplecontent> - <xs:simpletype name="messagetypetype"> - <xs:restriction base="xs:string"> <xs:enumeration value="request" /> <xs:enumeration value="response" /> <xs:enumeration value="notification" /> <xs:enumeration value="error" /> </xs:restriction> </xs:simpletype> - <xs:simpletype name="activitystatusenumtype"> - <xs:restriction base="xs:string"> <xs:enumeration value="success" /> <xs:enumeration value="failure" /> <xs:enumeration value="warning" /> </xs:restriction> </xs:simpletype> - <xs:simpletype name="communicationpatterntype"> - <xs:restriction base="xs:string"> <xs:enumeration value="simpleresponse" /> <xs:enumeration value="multiplebatchresponse" /> <xs:enumeration value="bulkresponse" /> <xs:enumeration value="notification" /> </xs:restriction> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 4 of 124
5 </xs:simpletype> - <xs:simpletype name="communicationstyletype"> - <xs:restriction base="xs:string"> <xs:enumeration value="msg" /> <xs:enumeration value="rpc" /> </xs:restriction> </xs:simpletype> - <xs:simpletype name="compressionenumtype"> - <xs:restriction base="xs:string"> <xs:enumeration value="no_compression" /> <xs:enumeration value="gzip" /> <xs:enumeration value="vendor_ext" /> <xs:enumeration value="minor_ext" /> </xs:restriction> </xs:simpletype> - <xs:simpletype name="packingenumtype"> - <xs:restriction base="xs:string"> <xs:enumeration value="no_packing" /> <xs:enumeration value="zip" /> <xs:enumeration value="tar" /> <xs:enumeration value="vendor_ext" /> <xs:enumeration value="minor_ext" /> </xs:restriction> </xs:simpletype> </xs:schema> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:tns=" xmlns:xs=" <xs:element name="nvlist" type="tns:nameandanyvaluelisttype" /> <xs:element name="nvslist" type="tns:nameandvaluestringlisttype" /> - <xs:complextype name="anylisttype"> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 5 of 124
6 <xs:any maxoccurs="unbounded" minoccurs="0" namespace="##other" processcontents="lax" /> - <xs:complextype name="nameandanyvaluelisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="nv" nillable="true" type="tns:nameandanyvaluetype" /> - <xs:complextype name="nameandanyvaluetype"> <xs:element name="name" type="xs:string" /> <xs:any namespace="##other" processcontents="lax" /> - <xs:complextype name="nameandvaluestringlisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="nvs" nillable="true" type="tns:nameandstringvaluetype" /> - <xs:complextype name="nameandstringvaluetype"> <xs:element name="name" type="xs:string" /> <xs:element name="value" nillable="true" type="xs:string" /> - <xs:complextype name="notificationidentifierlisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="notificationid" nillable="true" type="xs:string" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 6 of 124
7 - <xs:complextype name="multieventinventoryattributestype"> <xs:element name="netime" type="xs:string" /> <xs:element name="eventindication" type="xs:string" /> - <xs:complextype mixed="true" name="queryexpressiontype"> <xs:any maxoccurs="unbounded" minoccurs="0" namespace="##other" processcontents="lax" /> <xs:attribute name="dialect" type="xs:string" use="required" /> - <xs:complextype name="aliasnamelisttype"> - <xs:element maxoccurs="unbounded" minoccurs="0" name="alias" nillable="true"> <xs:element name="aliasname" type="xs:string" /> <xs:element name="aliasvalue" nillable="true" type="xs:string" /> </xs:schema> - <xs:schema targetnamespace=" version="1.0" xmlns:ns1=" xmlns:xs=" <xs:import namespace=" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 7 of 124
8 <xs:element name="managedelementnamesresponsetype" type="ns1:managedelementnamesresponsetype" /> </xs:schema> - <xs:schema attributeformdefault="unqualified" elementformdefault="unqualified" targetnamespace=" xmlns:tns=" xmlns:xs=" - <xs:element name="filtertype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="domainmanagernames" nillable="true" type="xs:string" /> - <xs:element name="getallmanagedelementspassingfilterrequest"> - <xs:element minoccurs="0" name="filter"> <xs:element maxoccurs="unbounded" minoccurs="0" name="domainmanagernames" nillable="true" type="xs:string" /> - <xs:complextype name="managedelementnamesresponsetype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="managedelementnames" nillable="true" type="xs:string" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 8 of 124
9 - <xs:complextype name="getallmanagedelementnamesexception"> <xs:element name="originatingdomain" nillable="true" type="xs:string" /> <xs:element name="getallmanagedelementnamesexception" type="tns:getallmanagedelementnamesexception" /> - <xs:element name="getallmanagedelementnamesrequest" nillable="true"> - <xs:element minoccurs="0" name="filter"> <xs:element maxoccurs="unbounded" minoccurs="0" name="domainmanagernames" nillable="true" type="xs:string" /> <xs:element name="getallmanagedelementnamesresponse" nillable="true" type="tns:managedelementnamesresponsetype" /> </xs:schema> </wsdl:types> - <wsdl:message name="getallmanagedelementnamesexception"> <wsdl:part element="tns:getallmanagedelementnamesexception" name="getallmanagedelementnamesexception" /> </wsdl:message> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 9 of 124
10 - <wsdl:message name="getallmanagedelementnamesresponse"> <wsdl:part element="tns:getallmanagedelementnamesresponse" name="mtopbody" /> <wsdl:part element="ns1:header" name="mtopheader" /> </wsdl:message> - <wsdl:message name="getallmanagedelementnames"> <wsdl:part element="ns1:header" name="mtopheader" /> <wsdl:part element="tns:getallmanagedelementnamesrequest" name="mtopbody" /> </wsdl:message> - <wsdl:porttype name="managedelementnamesretrieval_rpc"> - <wsdl:operation name="getallmanagedelementnames" parameterorder="mtopheader mtopbody"> <wsdl:input message="tns:getallmanagedelementnames" name="getallmanagedelementnames" /> <wsdl:output message="tns:getallmanagedelementnamesresponse" name="getallmanagedelementnamesresponse" /> <wsdl:fault message="tns:getallmanagedelementnamesexception" name="getallmanagedelementnamesexception" /> </wsdl:operation> </wsdl:porttype> - <wsdl:binding name="managedelementnamesretrievalrpcservicesoapbinding" type="tns:managedelementnamesretrieval_rpc"> <soap:binding style="document" transport=" /> - <wsdl:operation name="getallmanagedelementnames"> <soap:operation soapaction="getallmanagedelementnames" style="document" /> - <wsdl:input name="getallmanagedelementnames"> <soap:header message="tns:getallmanagedelementnames" part="mtopheader" use="literal" /> <soap:body parts="mtopbody" use="literal" /> </wsdl:input> - <wsdl:output name="getallmanagedelementnamesresponse"> <soap:header message="tns:getallmanagedelementnamesresponse" part="mtopheader" use="literal" /> <soap:body parts="mtopbody" use="literal" /> </wsdl:output> - <wsdl:fault name="getallmanagedelementnamesexception"> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 10 of 124
11 <soap:fault name="getallmanagedelementnamesexception" use="literal" /> </wsdl:fault> </wsdl:operation> </wsdl:binding> - <wsdl:service name="managedelementnamesretrievalrpcservice"> - <wsdl:port binding="tns:managedelementnamesretrievalrpcservicesoapbinding" name="managedelementnamesretrieval_rpcport"> <soap:address location=" /> </wsdl:port> </wsdl:service> </wsdl:definitions> ManagedElementRetrieval Apis WSDL document can be obtained by following URL Where primecentralserver is the hostname or IP address of Prime Central Server and mtosiport is the port number where CXF service for mtosi is running. By default port number is 9110 only getmanagedelement API is supported in Cisco Prime Central 1.0 release <?xml version="1.0" encoding="utf-8"?> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 11 of 124
12 - <wsdl:definitions name="managedelementretrievalrpcservice" targetnamespace=" xmlns:ns1=" xmlns:ns2=" xmlns:ns3=" xmlns:soap=" xmlns:tns=" xmlns:wsdl=" xmlns:xsd=" - <wsdl:types> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:ns1=" xmlns:xs=" <xs:import namespace=" /> - <xs:element name="setcommonattributesexception"> - <xs:complexcontent> - <xs:extension base="ns1:allexceptionstype"> <xs:sequence /> </xs:complexcontent> </xs:schema> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:ns1=" xmlns:ns2=" xmlns:tns=" xmlns:xs=" <xs:import namespace=" /> <xs:import namespace=" /> <xs:element name="tcp" type="tns:trafficconditioningprofiletype" /> - <xs:complextype name="trafficconditioningprofiletype"> - <xs:complexcontent> - <xs:extension base="ns2:commonresourceinfotype"> <xs:element name="isdefaultprofile" type="xs:boolean" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 12 of 124
13 <xs:element minoccurs="0" nillable="true" ref="ns1:transmissionparameterslist" /> </xs:complexcontent> - <xs:complextype name="trafficconditioningprofilelisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="tcp" nillable="true" type="tns:trafficconditioningprofiletype" /> </xs:schema> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:ns1=" xmlns:tns=" xmlns:xs=" <xs:import namespace=" /> <xs:element name="me" type="tns:managedelementtype" /> - <xs:complextype name="managedelementlisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="me" nillable="true" type="tns:managedelementtype" /> - <xs:complextype name="managedelementtype"> - <xs:complexcontent> - <xs:extension base="ns1:commonresourceinfotype"> <xs:element name="location" type="xs:string" /> <xs:element name="manufacturer" type="xs:string" /> <xs:element name="manufacturedate" type="xs:string" /> <xs:element name="productname" type="xs:string" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 13 of 124
14 <xs:element name="softwareversion" type="xs:string" /> <xs:element name="isinsyncstate" type="xs:boolean" /> <xs:element name="supportedconnectionlayerratelist" type="ns2:layerratelisttype" xmlns:ns2=" /> <xs:element name="communicationstate" type="tns:communicationstatetype" /> <xs:element name="asapref" type="ns3:namingattributetype" xmlns:ns3=" /> </xs:complexcontent> - <xs:simpletype name="communicationstatetype"> - <xs:restriction base="xs:string"> <xs:enumeration value="cs_available" /> <xs:enumeration value="cs_unavailable" /> </xs:restriction> </xs:simpletype> </xs:schema> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:ns1=" xmlns:ns2=" xmlns:tns=" xmlns:xs=" <xs:import namespace=" /> <xs:import namespace=" /> <xs:element name="transmissionparameterslist" type="tns:layeredparameterslisttype" /> - <xs:complextype name="layeredparameterslisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="transmissionparameters" nillable="true" type="tns:layeredparameterstype" /> - <xs:complextype name="layeredparameterstype"> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 14 of 124
15 <xs:element minoccurs="0" name="layerrate" type="ns1:layerratetype" /> <xs:element minoccurs="0" name="parameterlist" type="ns2:nameandvaluestringlisttype" /> <xs:element minoccurs="0" name="vendorextensions" type="ns2:anylisttype" /> </xs:schema> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:tns=" xmlns:xs=" <xs:element name="layerratelisttype" type="tns:layerratelisttype" /> - <xs:complextype name="layerratelisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="layerrate" nillable="true" type="tns:layerratetype" /> - <xs:complextype name="layerratetype"> - <xs:simplecontent> - <xs:extension base="tns:layerrateenumtype"> <xs:attribute name="extension" type="xs:string" /> </xs:simplecontent> - <xs:simpletype name="layerrateenumtype"> - <xs:restriction base="xs:string"> <xs:enumeration value="vendor_ext" /> <xs:enumeration value="minor_ext" /> <xs:enumeration value="cisco_lr_mplstp" /> <xs:enumeration value="cisco_lr_mpls_path" /> <xs:enumeration value="cisco_lr_mpls_pw" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 15 of 124
16 <xs:enumeration value="cisco_lr_evc" /> <xs:enumeration value="lr_ds0_64k" /> <xs:enumeration value="lr_dsl" /> <xs:enumeration value="lr_not_applicable" /> <xs:enumeration value="lr_async_fots_150m" /> <xs:enumeration value="lr_async_fots_417m" /> <xs:enumeration value="lr_async_fots_560m" /> <xs:enumeration value="lr_async_fots_565m" /> <xs:enumeration value="lr_async_fots_1130m" /> <xs:enumeration value="lr_async_fots_1g7" /> <xs:enumeration value="lr_async_fots_1g8" /> <xs:enumeration value="lr_atm_ni" /> <xs:enumeration value="lr_atm_vc" /> <xs:enumeration value="lr_atm_vp" /> <xs:enumeration value="lr_d1_video" /> <xs:enumeration value="lr_digital_signal_rate" /> <xs:enumeration value="lr_physical_electrical." /> <xs:enumeration value="lr_dsr_1_5m" /> <xs:enumeration value="lr_dsr_2m" /> <xs:enumeration value="lr_dsr_4m" /> <xs:enumeration value="lr_dsr_6m" /> <xs:enumeration value="lr_dsr_8m" /> <xs:enumeration value="lr_dsr_16m" /> <xs:enumeration value="lr_dsr_34m" /> <xs:enumeration value="lr_e2_8m" /> <xs:enumeration value="lr_e5_565m" /> <xs:enumeration value="lr_encapsulation" /> <xs:enumeration value="lr_fragment" /> <xs:enumeration value="lr_dsr_45m" /> <xs:enumeration value="lr_dsr_140m" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 16 of 124
17 <xs:enumeration value="lr_dsr_565m" /> <xs:enumeration value="lr_dsr_fast_ethernet" /> <xs:enumeration value="lr_dsr_gigabit_ethernet" /> <xs:enumeration value="lr_dsr_10gigabit_ethernet" /> <xs:enumeration value="lr_dsr_oc1_stm0" /> <xs:enumeration value="lr_dsr_oc3_stm1" /> <xs:enumeration value="lr_dsr_2xstm1" /> <xs:enumeration value="lr_dsr_oc12_stm4" /> <xs:enumeration value="lr_dsr_oc24_stm8" /> <xs:enumeration value="lr_dsr_oc48_and_stm16" /> <xs:enumeration value="lr_dsr_oc192_and_stm64" /> <xs:enumeration value="lr_dsr_oc768_and_stm256" /> <xs:enumeration value="lr_dsr_otu1" /> <xs:enumeration value="lr_dsr_otu2" /> <xs:enumeration value="lr_dsr_otu3" /> <xs:enumeration value="lr_e1_2m" /> <xs:enumeration value="lr_e20_2x2m" /> <xs:enumeration value="lr_e30_8x2m" /> <xs:enumeration value="lr_e3_34m" /> <xs:enumeration value="lr_e4_140m" /> <xs:enumeration value="lr_escon" /> <xs:enumeration value="lr_ethernet" /> <xs:enumeration value="lr_etr" /> <xs:enumeration value="lr_fast_ethernet" /> <xs:enumeration value="lr_fc_12_133m" /> <xs:enumeration value="lr_fc_25_266m" /> <xs:enumeration value="lr_fc_50_531m" /> <xs:enumeration value="lr_fc_100_1063m" /> <xs:enumeration value="lr_fddi" /> <xs:enumeration value="lr_ficon" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 17 of 124
18 <xs:enumeration value="lr_fr_if" /> <xs:enumeration value="lr_fr_pvc" /> <xs:enumeration value="lr_gigabit_ethernet" /> <xs:enumeration value="lr_isdn_bri" /> <xs:enumeration value="lr_line_oc1_sts1_and_ms_stm0" /> <xs:enumeration value="lr_line_oc3_sts3_and_ms_stm1" /> <xs:enumeration value="lr_line_oc12_sts12_and_ms_stm4" /> <xs:enumeration value="lr_line_oc24_sts24_and_ms_stm8" /> <xs:enumeration value="lr_line_oc48_sts48_and_ms_stm16" /> <xs:enumeration value="lr_line_oc192_sts192_and_ms_stm64" /> <xs:enumeration value="lr_line_oc768_sts768_and_ms_stm256" /> <xs:enumeration value="lr_low_order_tu3_vc3" /> <xs:enumeration value="lr_och_data_unit_1" /> <xs:enumeration value="lr_och_data_unit_2" /> <xs:enumeration value="lr_och_data_unit_3" /> <xs:enumeration value="lr_och_transport_unit_1" /> <xs:enumeration value="lr_och_transport_unit_2" /> <xs:enumeration value="lr_och_transport_unit_3" /> <xs:enumeration value="lr_sts3c_and_au4_vc4" /> <xs:enumeration value="lr_sts4c_and_vc3_4c" /> <xs:enumeration value="lr_sts5c_and_vc3_5c" /> <xs:enumeration value="lr_sts6c_and_vc4_2c" /> <xs:enumeration value="lr_sts7c_and_vc3_7c" /> <xs:enumeration value="lr_sts8c_and_vc3_8c" /> <xs:enumeration value="lr_sts9c_and_vc4_3c" /> <xs:enumeration value="lr_optical_channel" /> <xs:enumeration value="lr_optical_multiplex_section" /> <xs:enumeration value="lr_optical_section" /> <xs:enumeration value="lr_optical_transmission_section" /> <xs:enumeration value="lr_physical_medialess" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 18 of 124
19 <xs:enumeration value="lr_physical_optical" /> <xs:enumeration value="lr_pots" /> </xs:restriction> </xs:simpletype> </xs:schema> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:ns1=" xmlns:tns=" xmlns:xs=" <xs:import namespace=" /> <xs:element name="commonresourceinfo" type="tns:commonresourceinfotype" /> - <xs:complextype name="resourcestatetype"> - <xs:simplecontent> - <xs:extension base="tns:resourcestateenumtype"> <xs:attribute name="overlap" type="xs:string" /> <xs:attribute name="qualifier" type="xs:string" /> <xs:attribute name="extension" type="xs:string" /> </xs:simplecontent> - <xs:complextype abstract="true" name="commonresourceinfotype"> - <xs:complexcontent> - <xs:extension base="ns1:commonobjectinfotype"> <xs:element name="source" type="tns:sourcetype" /> <xs:element name="networkaccessdomain" type="xs:string" /> <xs:element name="meiattributes" type="ns2:multieventinventoryattributestype" xmlns:ns2=" /> <xs:element name="resourcestate" type="tns:resourcestatetype" /> <xs:any namespace="##other" processcontents="lax" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 19 of 124
20 </xs:complexcontent> - <xs:complextype name="sourcetype"> - <xs:simplecontent> - <xs:extension base="tns:sourceenumtype"> <xs:attribute name="qualifier" type="xs:string" /> </xs:simplecontent> - <xs:simpletype name="resourcestateenumtype"> - <xs:restriction base="xs:string"> <xs:enumeration value="vendor_ext" /> <xs:enumeration value="minor_ext" /> <xs:enumeration value="under_maintenance" /> <xs:enumeration value="synchronizing" /> <xs:enumeration value="installing" /> <xs:enumeration value="installing_accepted" /> <xs:enumeration value="installing_commissioned" /> <xs:enumeration value="installing_delivered" /> <xs:enumeration value="installing_installed" /> <xs:enumeration value="installing_integrated" /> <xs:enumeration value="installing_rejected" /> <xs:enumeration value="non_working" /> <xs:enumeration value="planning" /> <xs:enumeration value="planning_initial_plan" /> <xs:enumeration value="planning_ordered" /> <xs:enumeration value="planning_planned" /> <xs:enumeration value="retiring" /> <xs:enumeration value="retiring_decommissioned" /> <xs:enumeration value="retiring_deinstalled" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 20 of 124
21 <xs:enumeration value="retiring_deintegrated" /> <xs:enumeration value="retiring_recovered" /> <xs:enumeration value="retiring_stored" /> <xs:enumeration value="retiring_withdrawn_active" /> <xs:enumeration value="retiring_withdrawn_unavailable" /> <xs:enumeration value="unknown" /> <xs:enumeration value="working" /> <xs:enumeration value="working_activated" /> <xs:enumeration value="working_deactivated" /> </xs:restriction> </xs:simpletype> - <xs:simpletype name="sourceenumtype"> - <xs:restriction base="xs:string"> <xs:enumeration value="network_me" /> <xs:enumeration value="os" /> <xs:enumeration value="network_ems" /> </xs:restriction> </xs:simpletype> </xs:schema> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:ns1=" xmlns:ns2=" xmlns:ns3=" xmlns:ns4=" xmlns:tns=" xmlns:xs=" <xs:import namespace=" /> <xs:import namespace=" /> <xs:import namespace=" /> <xs:import namespace=" /> - <xs:element name="getallmanagedelementsexception"> - <xs:complexcontent> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 21 of 124
22 - <xs:extension base="ns4:allexceptionstype"> <xs:sequence /> </xs:complexcontent> - <xs:element name="getallmanagedelementspassingfilterexception"> - <xs:complexcontent> - <xs:extension base="ns4:allexceptionstype"> <xs:sequence /> </xs:complexcontent> - <xs:element name="getallmanagedelementspassingfilterrequest"> <xs:element minoccurs="0" name="mdref" type="ns1:namingattributetype" /> <xs:element minoccurs="0" name="filter" type="tns:filtertype" /> <xs:element name="getallmanagedelementspassingfilterresponse" type="tns:multiplemeobjectsresponsetype" /> - <xs:element name="getallmanagedelementsrequest"> <xs:element minoccurs="0" name="mdormlsnref" type="ns1:namingattributetype" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 22 of 124
23 <xs:element name="getallmanagedelementsresponse" type="tns:multiplemeobjectsresponsetype" /> - <xs:element name="getallmanagedelementswrtosexception"> - <xs:complexcontent> - <xs:extension base="ns4:allexceptionstype"> <xs:sequence /> </xs:complexcontent> - <xs:element name="getallmanagedelementswrtosrequest"> <xs:element minoccurs="0" name="osref" type="ns1:namingattributetype" /> <xs:element minoccurs="0" name="mdref" type="ns1:namingattributetype" /> <xs:element name="getallmanagedelementswrtosresponse" type="tns:multiplemeobjectsresponsetype" /> - <xs:element name="getmanagedelementexception"> - <xs:complexcontent> - <xs:extension base="ns4:allexceptionstype"> <xs:sequence /> </xs:complexcontent> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 23 of 124
24 - <xs:element name="getmanagedelementrequest"> <xs:element minoccurs="0" name="meref" type="ns1:namingattributetype" /> <xs:element name="getmanagedelementresponse" type="tns:singlemeobjectresponsetype" /> <xs:element name="getmanagedelementsiteratorexception" type="ns4:getalldataiteratorexceptiontype" /> <xs:element name="getmanagedelementsiteratorrequest" type="ns4:getalldataiteratorrequesttype" /> <xs:element name="getmanagedelementsiteratorresponse" type="tns:multiplemeobjectsresponsetype" /> - <xs:complextype name="filtertype"> <xs:element minoccurs="0" name="location" type="xs:string" /> <xs:element minoccurs="0" name="manufacturer" type="xs:string" /> <xs:element minoccurs="0" name="productname" type="xs:string" /> <xs:element minoccurs="0" name="resourcestate" type="ns2:resourcestatetype" /> - <xs:complextype name="multiplemeobjectsresponsetype"> <xs:element minoccurs="0" name="melist" type="ns3:managedelementlisttype" /> - <xs:complextype name="singlemeobjectresponsetype"> <xs:element minoccurs="0" name="me" type="ns3:managedelementtype" /> </xs:schema> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 24 of 124
25 - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:tns=" xmlns:xs=" - <xs:complextype name="namingattributetype"> <xs:element maxoccurs="unbounded" name="rdn" type="tns:relativedistinguishnametype" /> - <xs:complextype name="relativedistinguishnametype"> <xs:element name="type" type="xs:string" /> <xs:element name="value" type="xs:string" /> - <xs:complextype name="namingattributelisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="name" nillable="true" type="tns:namingattributetype" /> </xs:schema> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:ns1=" xmlns:ns2=" xmlns:tns=" xmlns:xs=" <xs:import namespace=" /> <xs:import namespace=" /> <xs:element name="accessdenied" type="tns:baseexceptionmessagetype" /> <xs:element name="capacityexceeded" type="tns:baseexceptionmessagetype" /> <xs:element name="commloss" type="tns:baseexceptionmessagetype" /> <xs:element name="entitynotfound" type="tns:baseexceptionmessagetype" /> <xs:element name="internalerror" type="tns:baseexceptionmessagetype" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 25 of 124
26 <xs:element name="invalidfilterdefinition" type="tns:baseexceptionmessagetype" /> <xs:element name="invalidinput" type="tns:baseexceptionmessagetype" /> <xs:element name="invalidtopic" type="tns:baseexceptionmessagetype" /> <xs:element name="notimplemented" type="tns:baseexceptionmessagetype" /> <xs:element name="notinvalidstate" type="tns:baseexceptionmessagetype" /> <xs:element name="notificationserviceproblem" type="tns:baseexceptionmessagetype" /> <xs:element name="objectinuse" type="tns:baseexceptionmessagetype" /> <xs:element name="protectioneffortnotmet" type="tns:baseexceptionmessagetype" /> <xs:element name="timeslotinuse" type="tns:baseexceptionmessagetype" /> <xs:element name="toomanyopeniterators" type="tns:baseexceptionmessagetype" /> <xs:element name="tpinvalidendpoint" type="tns:baseexceptionmessagetype" /> <xs:element name="unabletocomply" type="tns:baseexceptionmessagetype" /> <xs:element name="unsupportedcompressionformat" type="tns:baseexceptionmessagetype" /> <xs:element name="unsupportedpackingformat" type="tns:baseexceptionmessagetype" /> <xs:element name="unsupportedroutingconstraints" type="tns:baseexceptionmessagetype" /> <xs:element name="userlabelinuse" type="tns:baseexceptionmessagetype" /> - <xs:complextype name="allexceptionstype"> <xs:element minoccurs="0" name="accessdenied" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="capacityexceeded" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="commloss" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="entitynotfound" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="internalerror" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="invalidfilterdefinition" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="invalidinput" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="invalidtopic" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="notificationserviceproblem" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="notimplemented" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="notinvalidstate" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="objectinuse" type="tns:baseexceptionmessagetype" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 26 of 124
27 <xs:element minoccurs="0" name="protectioneffortnotmet" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="timeslotinuse" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="toomanyopeniterators" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="tpinvalidendpoint" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="unabletocomply" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="unsupportedcompressionformat" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="unsupportedpackingformat" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="unsupportedroutingconstraints" type="tns:baseexceptionmessagetype" /> <xs:element minoccurs="0" name="userlabelinuse" type="tns:baseexceptionmessagetype" /> - <xs:complextype name="baseexceptionmessagetype"> <xs:element minoccurs="0" ref="ns1:header" /> <xs:element minoccurs="0" name="reason" type="xs:string" /> <xs:element minoccurs="0" name="vendorextensions" type="ns2:anylisttype" /> - <xs:complextype name="getalldataiteratorexceptiontype"> - <xs:complexcontent> - <xs:extension base="tns:allexceptionstype"> <xs:sequence /> </xs:complexcontent> - <xs:complextype name="getalldataiteratorrequesttype"> <xs:sequence /> </xs:schema> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 27 of 124
28 - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:ns1=" xmlns:tns=" xmlns:xs=" <xs:import namespace=" /> - <xs:element name="header"> <xs:element minoccurs="0" name="activityname" type="xs:string" /> <xs:element minoccurs="0" name="msgname" type="xs:string" /> <xs:element minoccurs="0" name="msgtype" type="tns:messagetypetype" /> <xs:element minoccurs="0" name="senderuri" type="xs:anyuri" /> <xs:element minoccurs="0" name="destinationuri" type="xs:anyuri" /> <xs:element minoccurs="0" name="replytouri" type="xs:anyuri" /> <xs:element minoccurs="0" name="originatoruri" type="xs:anyuri" /> <xs:element minoccurs="0" name="failurereplytouri" type="xs:anyuri" /> <xs:element minoccurs="0" name="activitystatus" type="tns:activitystatustype" /> <xs:element minoccurs="0" name="correlationid" type="xs:string" /> <xs:element minoccurs="0" name="security" type="xs:string" /> <xs:element minoccurs="0" name="securitytype" type="xs:string" /> <xs:element minoccurs="0" name="priority" type="xs:string" /> - <xs:element minoccurs="0" name="msgspecificproperties"> - <xs:element maxoccurs="unbounded" minoccurs="0" name="property" nillable="true"> <xs:element name="propname" type="xs:string" /> <xs:element name="propvalue" type="xs:string" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 28 of 124
29 <xs:element minoccurs="0" name="communicationpattern" type="tns:communicationpatterntype" /> <xs:element minoccurs="0" name="communicationstyle" type="tns:communicationstyletype" /> <xs:element minoccurs="0" name="requestedbatchsize" type="xs:unsignedint" /> <xs:element minoccurs="0" name="batchsequencenumber" type="xs:unsignedint" /> <xs:element minoccurs="0" name="batchsequenceendofreply" type="xs:boolean" /> <xs:element minoccurs="0" name="iteratorreferenceuri" type="xs:anyuri" /> <xs:element minoccurs="0" name="filelocationuri" type="xs:anyuri" /> <xs:element minoccurs="0" name="compressiontype" type="tns:compressiontypetype" /> <xs:element minoccurs="0" name="packingtype" type="tns:packingtypetype" /> <xs:element minoccurs="0" name="timestamp" type="xs:datetime" /> <xs:element minoccurs="0" name="vendorextensions" type="ns1:anylisttype" /> - <xs:complextype name="activitystatustype"> - <xs:simplecontent> - <xs:extension base="tns:activitystatusenumtype"> <xs:attribute name="qualifier" type="xs:string" /> </xs:simplecontent> - <xs:complextype name="compressiontypetype"> - <xs:simplecontent> - <xs:extension base="tns:compressionenumtype"> <xs:attribute name="extension" type="xs:string" /> </xs:simplecontent> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 29 of 124
30 - <xs:complextype name="packingtypetype"> - <xs:simplecontent> - <xs:extension base="tns:packingenumtype"> <xs:attribute name="extension" type="xs:string" /> </xs:simplecontent> - <xs:simpletype name="messagetypetype"> - <xs:restriction base="xs:string"> <xs:enumeration value="request" /> <xs:enumeration value="response" /> <xs:enumeration value="notification" /> <xs:enumeration value="error" /> </xs:restriction> </xs:simpletype> - <xs:simpletype name="activitystatusenumtype"> - <xs:restriction base="xs:string"> <xs:enumeration value="success" /> <xs:enumeration value="failure" /> <xs:enumeration value="warning" /> </xs:restriction> </xs:simpletype> - <xs:simpletype name="communicationpatterntype"> - <xs:restriction base="xs:string"> <xs:enumeration value="simpleresponse" /> <xs:enumeration value="multiplebatchresponse" /> <xs:enumeration value="bulkresponse" /> <xs:enumeration value="notification" /> </xs:restriction> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 30 of 124
31 </xs:simpletype> - <xs:simpletype name="communicationstyletype"> - <xs:restriction base="xs:string"> <xs:enumeration value="msg" /> <xs:enumeration value="rpc" /> </xs:restriction> </xs:simpletype> - <xs:simpletype name="compressionenumtype"> - <xs:restriction base="xs:string"> <xs:enumeration value="no_compression" /> <xs:enumeration value="gzip" /> <xs:enumeration value="vendor_ext" /> <xs:enumeration value="minor_ext" /> </xs:restriction> </xs:simpletype> - <xs:simpletype name="packingenumtype"> - <xs:restriction base="xs:string"> <xs:enumeration value="no_packing" /> <xs:enumeration value="zip" /> <xs:enumeration value="tar" /> <xs:enumeration value="vendor_ext" /> <xs:enumeration value="minor_ext" /> </xs:restriction> </xs:simpletype> </xs:schema> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:tns=" xmlns:xs=" <xs:element name="nvlist" type="tns:nameandanyvaluelisttype" /> <xs:element name="nvslist" type="tns:nameandvaluestringlisttype" /> - <xs:complextype name="anylisttype"> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 31 of 124
32 <xs:any maxoccurs="unbounded" minoccurs="0" namespace="##other" processcontents="lax" /> - <xs:complextype name="nameandanyvaluelisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="nv" nillable="true" type="tns:nameandanyvaluetype" /> - <xs:complextype name="nameandanyvaluetype"> <xs:element name="name" type="xs:string" /> <xs:any namespace="##other" processcontents="lax" /> - <xs:complextype name="nameandvaluestringlisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="nvs" nillable="true" type="tns:nameandstringvaluetype" /> - <xs:complextype name="nameandstringvaluetype"> <xs:element name="name" type="xs:string" /> <xs:element name="value" nillable="true" type="xs:string" /> - <xs:complextype name="notificationidentifierlisttype"> <xs:element maxoccurs="unbounded" minoccurs="0" name="notificationid" nillable="true" type="xs:string" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 32 of 124
33 - <xs:complextype name="multieventinventoryattributestype"> <xs:element name="netime" type="xs:string" /> <xs:element name="eventindication" type="xs:string" /> - <xs:complextype mixed="true" name="queryexpressiontype"> <xs:any maxoccurs="unbounded" minoccurs="0" namespace="##other" processcontents="lax" /> <xs:attribute name="dialect" type="xs:string" use="required" /> - <xs:complextype name="aliasnamelisttype"> - <xs:element maxoccurs="unbounded" minoccurs="0" name="alias" nillable="true"> <xs:element name="aliasname" type="xs:string" /> <xs:element name="aliasvalue" nillable="true" type="xs:string" /> </xs:schema> - <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:tns=" xmlns:xs=" <xs:element name="commonobjectinfo" type="tns:commonobjectinfotype" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 33 of 124
34 - <xs:complextype abstract="true" name="commonobjectinfotype"> <xs:element name="name" type="ns1:namingattributetype" xmlns:ns1=" /> <xs:element name="userlabel" type="xs:string" /> <xs:element minoccurs="0" name="discoveredname" type="xs:string" /> <xs:element name="namingos" type="xs:string" /> <xs:element name="owner" type="xs:string" /> <xs:element name="aliasnamelist" type="ns2:aliasnamelisttype" xmlns:ns2=" /> <xs:element name="vendorextensions" type="ns3:anylisttype" xmlns:ns3=" /> </xs:schema> </wsdl:types> - <wsdl:message name="getmanagedelementexception"> <wsdl:part element="ns2:getmanagedelementexception" name="getmanagedelementexception" /> </wsdl:message> - <wsdl:message name="getallmanagedelementspassingfilter"> <wsdl:part element="ns1:header" name="mtopheader" /> <wsdl:part element="ns2:getallmanagedelementspassingfilterrequest" name="mtopbody" /> </wsdl:message> - <wsdl:message name="getallmanagedelementsexception"> <wsdl:part element="ns2:getallmanagedelementsexception" name="getallmanagedelementsexception" /> </wsdl:message> - <wsdl:message name="getmanagedelementresponse"> <wsdl:part element="ns2:getmanagedelementresponse" name="mtopbody" /> <wsdl:part element="ns1:header" name="mtopheader" /> </wsdl:message> - <wsdl:message name="getallmanagedelements"> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 34 of 124
35 <wsdl:part element="ns1:header" name="mtopheader" /> <wsdl:part element="ns2:getallmanagedelementsrequest" name="mtopbody" /> </wsdl:message> - <wsdl:message name="getallmanagedelementspassingfilterresponse"> <wsdl:part element="ns2:getallmanagedelementspassingfilterresponse" name="mtopbody" /> <wsdl:part element="ns1:header" name="mtopheader" /> </wsdl:message> - <wsdl:message name="getmanagedelement"> <wsdl:part element="ns1:header" name="mtopheader" /> <wsdl:part element="ns2:getmanagedelementrequest" name="mtopbody" /> </wsdl:message> - <wsdl:message name="getallmanagedelementspassingfilterexception"> <wsdl:part element="ns2:getallmanagedelementspassingfilterexception" name="getallmanagedelementspassingfilterexception" /> </wsdl:message> - <wsdl:message name="getallmanagedelementsresponse"> <wsdl:part element="ns2:getallmanagedelementsresponse" name="mtopbody" /> <wsdl:part element="ns1:header" name="mtopheader" /> </wsdl:message> - <wsdl:porttype name="managedelementretrieval_rpc"> - <wsdl:operation name="getallmanagedelementspassingfilter" parameterorder="mtopheader mtopbody"> <wsdl:input message="tns:getallmanagedelementspassingfilter" name="getallmanagedelementspassingfilter" /> <wsdl:output message="tns:getallmanagedelementspassingfilterresponse" name="getallmanagedelementspassingfilterresponse" /> <wsdl:fault message="tns:getallmanagedelementspassingfilterexception" name="getallmanagedelementspassingfilterexception" /> </wsdl:operation> - <wsdl:operation name="getallmanagedelements" parameterorder="mtopheader mtopbody"> <wsdl:input message="tns:getallmanagedelements" name="getallmanagedelements" /> <wsdl:output message="tns:getallmanagedelementsresponse" name="getallmanagedelementsresponse" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 35 of 124
36 <wsdl:fault message="tns:getallmanagedelementsexception" name="getallmanagedelementsexception" /> </wsdl:operation> - <wsdl:operation name="getmanagedelement" parameterorder="mtopheader mtopbody"> <wsdl:input message="tns:getmanagedelement" name="getmanagedelement" /> <wsdl:output message="tns:getmanagedelementresponse" name="getmanagedelementresponse" /> <wsdl:fault message="tns:getmanagedelementexception" name="getmanagedelementexception" /> </wsdl:operation> </wsdl:porttype> - <wsdl:binding name="managedelementretrievalrpcservicesoapbinding" type="tns:managedelementretrieval_rpc"> <soap:binding style="document" transport=" /> - <wsdl:operation name="getallmanagedelementspassingfilter"> <soap:operation soapaction="getallmanagedelementspassingfilter" style="document" /> - <wsdl:input name="getallmanagedelementspassingfilter"> <soap:header message="tns:getallmanagedelementspassingfilter" part="mtopheader" use="literal" /> <soap:body parts="mtopbody" use="literal" /> </wsdl:input> - <wsdl:output name="getallmanagedelementspassingfilterresponse"> <soap:header message="tns:getallmanagedelementspassingfilterresponse" part="mtopheader" use="literal" /> <soap:body parts="mtopbody" use="literal" /> </wsdl:output> - <wsdl:fault name="getallmanagedelementspassingfilterexception"> <soap:fault name="getallmanagedelementspassingfilterexception" use="literal" /> </wsdl:fault> </wsdl:operation> - <wsdl:operation name="getallmanagedelements"> <soap:operation soapaction="getallmanagedelements" style="document" /> - <wsdl:input name="getallmanagedelements"> <soap:header message="tns:getallmanagedelements" part="mtopheader" use="literal" /> <soap:body parts="mtopbody" use="literal" /> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 36 of 124
37 </wsdl:input> - <wsdl:output name="getallmanagedelementsresponse"> <soap:header message="tns:getallmanagedelementsresponse" part="mtopheader" use="literal" /> <soap:body parts="mtopbody" use="literal" /> </wsdl:output> - <wsdl:fault name="getallmanagedelementsexception"> <soap:fault name="getallmanagedelementsexception" use="literal" /> </wsdl:fault> </wsdl:operation> - <wsdl:operation name="getmanagedelement"> <soap:operation soapaction="getmanagedelement" style="document" /> - <wsdl:input name="getmanagedelement"> <soap:header message="tns:getmanagedelement" part="mtopheader" use="literal" /> <soap:body parts="mtopbody" use="literal" /> </wsdl:input> - <wsdl:output name="getmanagedelementresponse"> <soap:header message="tns:getmanagedelementresponse" part="mtopheader" use="literal" /> <soap:body parts="mtopbody" use="literal" /> </wsdl:output> - <wsdl:fault name="getmanagedelementexception"> <soap:fault name="getmanagedelementexception" use="literal" /> </wsdl:fault> </wsdl:operation> </wsdl:binding> - <wsdl:service name="managedelementretrievalrpcservice"> - <wsdl:port binding="tns:managedelementretrievalrpcservicesoapbinding" name="managedelementretrieval_rpcport"> <soap:address location=" /> </wsdl:port> </wsdl:service> 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 37 of 124
38 </wsdl:definitions> Equipment Retrieval Apis WSDL document can be obtained by following URL EquipmentInventoryRetrieval_RPC?wsdl Where primecentralserver is the hostname or IP address of Prime Central Server and mtosiport is the port number where CXF service for mtosi is running. By default port number is 9110 Supported API in this WSDL are getallequipment getequipment getcontainedequipment getallsupportedphysicaltermiminationpoints <?xml version="1.0" encoding="utf-8"?> - <wsdl:definitions name="equipmentinventoryretrievalrpcservice" targetnamespace=" xmlns:ns1=" xmlns:ns2=" xmlns:ns3=" xmlns:soap=" xmlns:tns=" xmlns:wsdl=" xmlns:xsd=" - <wsdl:types> - <xs:schema attributeformdefault="unqualified" elementformdefault="qualified" targetnamespace=" Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 38 of 124
GoProCaseSoap.wsdl <?xml version='1.0' encoding='utf-8'?><wsdl:definitions name="goprocasesoapservice"
More information
Web Service Provider Example - Enabling Visible Business
Web Services Example Web Service Provider Example - Enabling Visible Business Company A makes earrings. One of their suppliers, Company B, provides the glass beads that are used in the earrings. Company
More informationPublications Office. TED Website - Notice Viewer WS Technical Specifications Document - Appendix D - NoticeViewer
Publications Office Subject NoticeViewer WS API Version / Status 1.03 Release Date 17/02/2017 Filename Document Reference TED_WEBSITE-TSP-Technical_Specifications_Document-v1.03 TED-TSP-Appendix D Table
More information[MS-OXWSSYNC]: Mailbox Contents Synchronization Web Service Protocol Specification
[MS-OXWSSYNC]: Mailbox Contents Synchronization Web Service Protocol Specification Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes
More informationPRELIMINARY. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSTASK]: Tasks Web Service Protocol Specification Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation
More informationCMS SOAP CLIENT SOFTWARE REQUIREMENTS SPECIFICATION
CMS SOAP CLIENT SOFTWARE REQUIREMENTS SPECIFICATION CONTENTS 1. Introduction 1.1. Purpose 1.2. Scope Of Project 1.3. Glossary 1.4. References 1.5. Overview Of Document 2. Overall Description 2.1. System
More informationX-Road: Protocol for Management Services
X-Road: Protocol for Management Services Technical Document Version: 1.8 09.11.2015 22 pages Doc. ID: PR-MSERV 09.11.2015 1/22 Date Version Description Author 19.08.2015 0.1 Initial version Martin Lind
More informationMWTM NBAPI WSDL and XSD Definitions
APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM 6.1.4 Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-10 ProvisionAPI.wsdl, page
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWMT]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationDistribution List Creation and Usage Web Service Protocol
[MS-OXWSDLIST]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWOOF]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationCalendar Data API. Version gradleaders.com
Version 1.03 gradleaders.com Table of Contents 614.791.9000 TABLE OF CONTENTS Overview... 1 Example Code... 1 Web Service... 1 Invocation Result... 1 Configuration... 1 Method - GetCustomFields... 2 Method
More informationIVOA Support Interfaces: Mandatory Interfaces Version 0.3
IVOA Support Interfaces: Mandatory Interfaces Version 0.3 IVOA Working Draft 2007 May 16 This version: http://www.ivoa.net/internal/ivoa/ivoagridandwebservices /VOSupportInterfacesMandatory-0.3.pdf Previous
More informationMWTM 6.1 NBAPI WSDL and XSD Definitions
APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM 6.1 Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-5 ProvisionAPI.wsdl, page
More information[MS-OXWMT]: Mail Tips Web Service Extensions. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWMT]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationAutomotive Append - Version 1.0.0
Automotive Append - Version 1.0.0 WSDL: http://ws.strikeiron.com/autoappend?wsdl Product Web Page: http://www.strikeiron.com/data-enrichment/automotive-append/ Description: StrikeIron s Automotive Append
More information<wsdl:definitions targetnamespace="http://www.trustedcomputinggroup.org/xml/wsdl/migrationservi ce_1-00_1-00">
More information
@WebService OUT params via javax.xml.ws.holder
@WebService OUT params via javax.xml.ws.holder Example webservice-holder can be browsed at https://github.com/apache/tomee/tree/master/examples/webservice-holder With SOAP it is possible to return multiple
More informationIVOA Support Interfaces: Mandatory Interfaces Version 0.25
IVOA Support Interfaces: Mandatory Interfaces Version 0.25 IVOA Working Draft 2006 Sep 18 This version: http://www.ivoa.net/internal/ivoa/ivoagridandwebservices /VOSupportInterfacesMandatory-0.25.pdf Previous
More informationVoiceForge. xmlns:s=" xmlns:soap12="
VoiceForge 1. BASIC INFORMATION (Overview and purpose of the tool) 1. Webservice name VoiceForge Webservice (TTL2Ro) 2. Overview and purpose of the webservice The VoiceForge Webservice provides a set of
More informationExtensible Markup Language Processing
CHAPTER 3 Revised: July 2010, This chapter describes the Extensible Markup Language (XML) process in the Simple Object Access Protocol (SOAP) interface. Basic XML and SOAP Components Along with XML, the
More informationCandidate Resume Data API
Candidate Resume Data API Version 1.03 gradleaders.com Table of Contents 614.791.9000 TABLE OF CONTENTS OVERVIEW... 1 EXAMPLE CODE... 1 WEB SERVICE... 1 Invocation Result... 1 Configuration... 1 Method
More informationSOAP Web Services Objektumorientált szoftvertervezés Object-oriented software design. Web services 11/23/2016. Outline. Remote call.
SOAP Web Services Objektumorientált szoftvertervezés Object-oriented software design Outline Web Services SOAP WSDL Web Service APIs.NET: WCF Java: JAX-WS Dr. Balázs Simon BME, IIT 2 Remote call Remote
More information[MS-OXWSBTRF]: Bulk Transfer Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWSBTRF]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationArticulation Transfer Clearinghouse Implementation Guide
Articulation Transfer Clearinghouse for 8/2/2007 Implementation Details TABLE OF CONTENTS INTRODUCTION... 3 Project Identification... 3 DOCUMENT CONTROL... 4 Update History... 4 ENVIRONMENTS... 5 METHODS...
More informationHow to implement Heros Web Services
How to implement Heros Web Services Document name HowTo_HITRail_WebServices_v1.0.doc Date, version January 28, 2013, version 1.0 Our reference HIT Rail Web Services Status Final 2012 HIT Rail B.V. Referenced
More informationMessages are securely encrypted using HTTPS. HTTPS is the most commonly used secure method of exchanging data among web browsers.
May 6, 2009 9:39 SIF Specifications SIF Implementation Specification The SIF Implementation Specification is based on the World Wide Web Consortium (W3C) endorsed Extensible Markup Language (XML) which
More informationOracle B2B 11g Technical Note. Technical Note: 11g_005 Attachments. Table of Contents
Oracle B2B 11g Technical Note Technical Note: 11g_005 Attachments This technical note lists the attachment capabilities available in Oracle B2B Table of Contents Overview... 2 Setup for Fabric... 2 Setup
More informationThe following is a sample XML code from the HCSProductCatalog.wsdl file.
APPENDIXA This appendix contains sample WSDL and XSD files. It includes the following sections: HCSProductCatalog.wsdl File, page A-1 HCSProvision.xsd File, page A-27 HCSProvisionAsyncResponse.wsdl File,
More informationRed Hat JBoss Fuse 6.0
Red Hat JBoss Fuse 6.0 Tutorials Example integration applications Last Updated: 2017-10-13 Red Hat JBoss Fuse 6.0 Tutorials Example integration applications JBoss A-MQ Docs Team Content Services fuse-docs-support@redhat.com
More informationSERVICE ORIE TED COMPUTI G ARCHITECTURE FOR CLIMATE MODELI G
SERVICE ORIE TED COMPUTI G ARCHITECTURE FOR CLIMATE MODELI G Monish Advani 1, Varish Mulwad 2, Uzoma Obinna 2 1 Department of Information Systems 2 Department of Computer Science and Electrical Engineering
More information[MS-OXWOOF]: Out of Office (OOF) Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWOOF]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More information[MS-RMPR]: Rights Management Services (RMS): Client-to-Server Protocol
[MS-RMPR]: Rights Management Services (RMS): Client-to-Server Protocol This topic lists the Errata found in [MS-RMPR] since it was last published. Since this topic is updated frequently, we recommend that
More information/// Rapport. / Testdocumentatie nieuwe versie Register producten en dienstverlening (IPDC)
/// Rapport / Testdocumentatie nieuwe versie Register producten en dienstverlening (IPDC) / Maart 2017 www.vlaanderen.be/informatievlaanderen Informatie Vlaanderen /// Aanpassingen aan de webservices Dit
More informationPTC Integrity 10.7 Web Services Reference
PTC Integrity 10.7 Web Services Reference PTC Integrity 10.7 Web Services Reference Copyright 2015 PTC Inc. and/or Its Subsidiary Companies. All Rights Reserved. User and training guides and related documentation
More informationOracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1. September 2017
Oracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1 September 2017 Copyright 1987, 2017, Oracle and/or its affiliates. All rights reserved. This software and related
More informationDevelopment of distributed services - Project III. Jan Magne Tjensvold
Development of distributed services - Project III Jan Magne Tjensvold November 11, 2007 Chapter 1 Project III 1.1 Introduction In this project we were going to make a web service from one of the assignments
More information<xs:element name="relationshipdata" type="rr:relationshipdatatype"/> <xs:element name="header" type="rr:rrheadertype"> </xs:element>
More information
INFORMATION TECHNOLOGY. Automated Railcar Release, Switch and Resequence XML and WSDL documentation
INFORMATION TECHNOLOGY Automated Railcar Release, Switch and Resequence XML and WSDL documentation Revision Date: December 21, 2017 Table of Contents 1 Introduction... 4 1.1 Purpose of this document...
More informationWP5: Integration with the Digital Ecosystem platform
OPAALS PROJECT Contract n IST-034824 WP5: Integration with the Digital Ecosystem platform Del 5.8 Complete P2P infrastructure implementation Project funded by the European Community under the Information
More information[MS-OXWSGTZ]: Get Server Time Zone Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWSGTZ]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More information<xsd:element name="name" maxoccurs="1" minoccurs="0" <xsd:element name="parentaccountid" maxoccurs="1" minoccurs="0" <xsd:element name="parentaccounti
More information
Mailtips Extensions to Web Service Protocol Specification
[MS-OXWMT]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationPreliminary. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSPOST]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationRestricting complextypes that have mixed content
Restricting complextypes that have mixed content Roger L. Costello October 2012 complextype with mixed content (no attributes) Here is a complextype with mixed content:
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSMSHR]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More information[MS-OXWSMSHR]: Folder Sharing Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWSMSHR]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationPreliminary. Database Publishing Wizard Protocol Specification
[MS-SSDPWP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationExercise sheet 4 Web services
STI Innsbruck, University Innsbruck Dieter Fensel, Anna Fensel and Ioan Toma 15. April 2010 Semantic Web Services Exercise sheet 4 Exercise 1 (WSDL) (4 points) Complete the following WSDL file in a way
More informationQosPolicyHolder:1 Erratum
Erratum Number: Document and Version: Cross References: Next sequential erratum number Effective Date: July 14, 2006 Document erratum applies to the service document QosPolicyHolder:1 This Erratum has
More information@WebService handlers
@WebService handlers with @HandlerChain Example webservice-handlerchain can be browsed at https://github.com/apache/tomee/tree/master/examples/webservicehandlerchain In this example we see a basic JAX-WS
More informationSupport For assistance, please contact Grapevine: or
External OBS (incorporating Double Opt-in) User Manual Version 1.3 Date 07 October 2011 Support For assistance, please contact Grapevine: +27 21 702-3333 or email info@vine.co.za. Feedback Was this document
More informationAbout 1. Chapter 1: Getting started with soap 2. Remarks 2. Versions 2. Examples 2. General Information 2 SOAP 3
soap #soap Table of Contents About 1 Chapter 1: Getting started with soap 2 Remarks 2 Versions 2 Examples 2 General Information 2 SOAP 3 Differences between SOAP 1.1 and 1.2 4 Web Service Interoperability
More informationDeveloping a Service. Developing a Service using JAX-WS. WSDL First Development. Generating the Starting Point Code
Developing a Service Developing a Service using JAX-WS WSDL First Development Generating the Starting Point Code Running wsdl2java Generated code Implementing the Service Generating the implementation
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-SSDPWP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationOpenHealth. A Framework for the Delivery of CCR-based Services
OpenHealth A Framework for the Delivery of CCR-based Services October 24, 2006 1 2 TABLE OF CONTENTS 1. Introduction... 3 2. Goals and Strategies... 4 2.1 Major Goals... 4 2.2 Minor Goals... 5 2.3 Design
More informationReleased to: TSCP Architecture Committee
Business Authorization Identification and Labeling Scheme Version 1 (BAILS v.1.0) Prepared by: TSCP ILH Team Lead Author: Jean-Paul Buu-Sao, TSCP Released to: TSCP Architecture Committee Edition: 1.4 Published:
More informationCase study group setup at catme.org Please respond before Tuesday next week to have better group setup
Notes Case study group setup at catme.org Please respond before Tuesday next week to have better group setup Discussion To boost discussion, one write-up for the whole group is fine Write down the names
More informationData Pump User Guide
Data Pump User Guide CalAmp Corporation 13645 Dulles Technology Drive, Herndon, VA 20171 Document: MBUD-0189v6 Phone : (703) 262-0500 August 2015 FAX: (703) 262-0380 www.calamp.com FleetOutlook Data Pump
More informationSOA SOA SOA SOA SOA SOA SOA SOA SOA SOA SOA SOA SOA SOA
P P CRM - Monolithic - Objects - Component - Interface - . IT. IT loosely-coupled Client : - Reusability - Interoperability - Scalability - Flexibility - Cost Efficiency - Customized SUN BEA IBM - extensible
More information1 Adaptive Streaming Overview (Informative)
1 Adaptive Streaming Overview (Informative) Adaptive streaming is enabled by two main components: 1. A media format that can be delivered by an HTTP server as a sequence of Segments, each in response to
More information[MS-SSDPWP-Diff]: Database Publishing Wizard Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SSDPWP-Diff]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationSemantic Annotations for WSDL and XML Schema
Page 1 of 16 Semantic Annotations for WSDL and XML Schema W3C Recommendation 28 August 2007 This version: Latest version: http://www.w3.org/tr/sawsdl/ Previous version: http://www.w3.org/tr/2007/pr-sawsdl-20070705/
More informationCisco Unity Connection Notification Interface (CUNI) API
Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 2018 Cisco Systems, Inc. All rights
More informationXML Schema. Mario Alviano A.Y. 2017/2018. University of Calabria, Italy 1 / 28
1 / 28 XML Schema Mario Alviano University of Calabria, Italy A.Y. 2017/2018 Outline 2 / 28 1 Introduction 2 Elements 3 Simple and complex types 4 Attributes 5 Groups and built-in 6 Import of other schemes
More informationSimple Object Access Protocol. Web Services Description Language
Simple Object Access Protocol Web Services Description Language alfady@scs-net.org alnashed@scs-net.org ***"#$%& '() "! ... INTRODUCTION.. SIMPLE OBJECT ACCESS PROTOCOL...Why SOAPSOAP...SOAP Building BlocksSOAP...Syntax
More informationWeb Services Foundations: SOAP, WSDL and UDDI
Web Services Foundations: SOAP, WSDL and UDDI Helen Paik School of Computer Science and Engineering University of New South Wales Alonso Book Chapter 5-6 Webber Book Chapter 3-4 Mike Book Chapter 4-5 References
More informationMessage and Service Definitions
User s Guide Page: 1 / 281 User s Guide Product /Function: Message and Service Definitions Project: Shared Architecture CIM/CIE Project contract: ARC010 Version: 1.0 Category: C Start: M09/2008 Document
More information[MS-OXWSMTRK]: Message Tracking Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWSMTRK]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationONVIF TM. ONVIF Specification Version Release Notes. ONVIF
ONVIF TM ONVIF Specification Version 18.06 Release Notes ONVIF www.onvif.org info@onvif.org 2008-2018 by ONVIF TM All rights reserved. Recipients of this document may copy, distribute, publish, or display
More informationArtix ESB. Developing Artix Applications with JAX-WS. Making Software Work Together. Version 5.0 July 2007
Artix ESB Developing Artix Applications with JAX-WS Version 5.0 July 2007 Making Software Work Together Developing Artix Applications with JAX-WS IONA Technologies Version 5.0 Published 04 Oct 2007 Copyright
More informationDocument erratum applies to QosDevice:1. List other Erratum s or Documents that this change may apply to or have associated changes with
Erratum Number: Document and Version: Cross References: QosDevice:1 Erratum Next sequential erratum number Effective Date: July 14, 2006 Document erratum applies to QosDevice:1 List other Erratum s or
More informationUsing Inventory Export Guide
Introducing Inventory Import and Export XML Using Inventory Export Guide To Manage Your Inventory Data Version 1.0 ADD TO CART XML API GUIDE 5/28/13 PAGE 1 Copyright 2013 Shopatron, Inc. Using Inventory
More informationGeneral Service Subscription Management Technical Specification
General Service Subscription Management Technical Specification Approved Version 1.0 20 Dec 2011 Open Mobile Alliance OMA-TS-GSSM-V1_0-20111220-A OMA-TS-GSSM-V1_0-20111220-A Page 2 (32) Use of this document
More informationExpires: January 15, 2005 July 17, Extensible Markup Language (XML) Formats for Representing Resource Lists draft-ietf-simple-xcap-list-usage-03
SIMPLE J. Rosenberg Internet-Draft dynamicsoft Expires: January 15, 2005 July 17, 2004 Extensible Markup Language (XML) Formats for Representing Resource Lists draft-ietf-simple-xcap-list-usage-03 Status
More informationWS-MessageDelivery Version 1.0
WS-MessageDelivery Version 1.0 WS-MessageDelivery Version 1.0 W3C Member Submission 26 April 2004 This version: http://www.w3.org/submission/2004/subm-ws-messagedelivery-20040426/ Latest version: http://www.w3.org/submission/ws-messagedelivery/
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-SLIDELI]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationDFP Mobile Ad Network and Rich Media API
DFP Mobile Ad Network and Rich Media API v2.0, 12 June 2012 Background DFP Mobile is adopting a single open API for integrating with all ad networks and rich media vendors. This has the following benefits:
More informationPreliminary. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-SLIDELI]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationRequest for Comments: 4661 Category: Standards Track M. Lonnfors J. Costa-Requena Nokia September 2006
Network Working Group Request for Comments: 4661 Category: Standards Track H. Khartabil Telio E. Leppanen M. Lonnfors J. Costa-Requena Nokia September 2006 Status of This Memo An Extensible Markup Language
More informationExtensible Markup Language Processing
CHAPTER 2 Revised: June 24, 2009, This chapter describes the Extensible Markup Language (XML) process in the Common Object Request Broker Architecture (CORBA) adapter. XML and Components Along with XML,
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSCONT]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationQualys Cloud Suite API Release Notes
Qualys Cloud Suite API Release Notes Version 2.28 Qualys Cloud Suite API gives you ways to integrate your programs and API calls with Qualys capabilities. You ll find all the details in our documentation,
More informationG16-02SE-A02.1-NUE112_SchedaContatto-Rev5 <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/xmlschema"
More information
Columbia University R. Mahy, Ed. SIP Edge LLC November An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)
Network Working Group Request for Comments: 4235 Category: Standards Track J. Rosenberg Cisco Systems H. Schulzrinne Columbia University R. Mahy, Ed. SIP Edge LLC November 2005 Status of this Memo An INVITE-Initiated
More informationDeveloping JAX-RPC Web services
Developing JAX-RPC Web services {scrollbar} This tutorial will take you through the steps required in developing, deploying and testing a Web Service in Apache Geronimo. After completing this tutorial
More information[MS-OFFICIALFILE]: Official File Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OFFICIALFILE]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats,
More informationImplementation Guide for the ASAP Prescription Monitoring Program Web Service Standard
ASAP Implementation Guide for the ASAP Prescription Monitoring Program Web Service Standard Bidirectional Electronic Connections between Pharmacies, Prescribers, and Prescription Monitoring Programs Version
More information[MS-SPLCHK]: SpellCheck Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SPLCHK]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More information[MS-OXWSMSG]: Message Types Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWSMSG]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationRequest for Comments: 5025 Category: Standards Track December 2007
Network Working Group J. Rosenberg Request for Comments: 5025 Cisco Category: Standards Track December 2007 Status of This Memo Presence Authorization Rules This document specifies an Internet standards
More information[MS-STWEB]: Microsoft OneDrive Save to Web SOAP Web Service. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-STWEB]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationX3D Unit Specification Updates Myeong Won Lee The University of Suwon
X3D Unit Specification Updates Myeong Won Lee The University of Suwon 1 Units Specification ISO_IEC_19775_1_2008_WD3_Am1_2011_04_14 PDAM in ISO progress UNIT statement Defined in Core component UNIT statements
More informationTPF Users Group Fall 2007
TPF Users Group Fall 2007 Creating Web Services For Your z/tpf System Edwin W. van de Grift Venue: Ongoing TPF Education Contents Web Services Where we were Where we are now Creating a Web Service for
More informationOpen IPTV Forum Release 1 Specification. Volume 1 Overview. V1.0, January 6, Open IPTV Forum. Copyright 2009 Members of the Open IPTV Forum
Open IPTV Forum Release 1 Specification Volume 1 Overview V1.0, January 6, 2009 Open IPTV Forum Page 2 (39) Open IPTV Forum Postal address Open IPTV Forum support office address 650 Route des Lucioles
More informationNetwork Service Interface Topology Representation
GWD-R-P NSI-WG nsi-wg@ogf.org Jeroen van der Ham, UvA June 2013 Network Service Interface Topology Representation Status of This Document Group Working Draft (GWD), candidate Recommendations Proposed (R-P).
More informationHP Service Manager Software
HP Service Manager Software For the Windows and Unix Operating Systems Software version 9.20 Web Services Tailoring Guide Document Release Date: June 2010 Software Release Date: June 2010 Legal Notices
More information