MWTM NBAPI WSDL and XSD Definitions
|
|
- Asher Carter
- 6 years ago
- Views:
Transcription
1 APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-10 ProvisionAPI.wsdl, page A-14 MWTM.xsd, page A-15 Common.xsd, page A-15 Inventory.xsd, page A-16 Event.xsd, page A-18 Provision.xsd, page A-19 Note MWTM NBAPI WSDL and XSD definitions can also be obtained at the following locations: ${MWTM_INSTALL_BASEDIR}/tomcat/webapp/nbapi/WEB-INF/wsdl/InventoryAPI.wsdl ${MWTM_INSTALL_BASEDIR}/tomcat/webapp/nbapi/WEB-INF/wsdl/EventAPI.wsdl ${MWTM_INSTALL_BASEDIR}/tomcat/webapp/nbapi/WEB-INF/wsdl/ProvisionAPI.wsdl ${MWTM_INSTALL_BASEDIR}/tomcat/webapp/nbapi/WEB-INF/wsdl/MWTM.xsd ${MWTM_INSTALL_BASEDIR}/tomcat/webapp/nbapi/WEB-INF/wsdl/Common.xsd ${MWTM_INSTALL_BASEDIR}/tomcat/webapp/nbapi/WEB-INF/wsdl/Inventory.xsd ${MWTM_INSTALL_BASEDIR}/tomcat/webapp/nbapi/WEB-INF/wsdl/Event.xsd ${MWTM_INSTALL_BASEDIR}/tomcat/webapp/nbapi/WEB-INF/wsdl/Provision.xsd InventoryAPI.wsdl <?xml version="1.0" encoding="utf-8" standalone="yes"?> <!-- Copyright (c) Cisco Systems, Inc. All rights reserved. --> <definitions targetnamespace=" name="inventoryapiservice" xmlns:tns=" xmlns:xsd=" xmlns:soap=" xmlns=" <types> 1. The XML Schema language (see A-1
2 InventoryAPI.wsdl Appendix A <xsd:schema> <xsd:import namespace=" schemalocation="mwtm.xsd"/> </xsd:schema> </types> <message name="apistatus"> <part name="apistatus" element="tns:apistatus"/> <message name="getnerequest"> <message name="getneresponse"> <part name="networkelement" type="tns:networkelement"/> <message name="normalizefqdnrequest"> <message name="normalizefqdnresponse"> <part name="normalizedfqdn" type="xsd:string"/> <message name="haschildrequest"> <message name="haschildresponse"> <part name="haschildflag" type="xsd:boolean"/> <message name="getallnesrequest"> <message name="getallnesresponse"> <message name="getallneswithfeaturerequest"> <part name="featurestr" type="xsd:string"/> <message name="getallneswithfeatureresponse"> <message name="getallnetypesrequest"> <message name="getallnetypesresponse"> <part name="netypelist" type="tns:netypelist"/> <message name="getallnesbytyperequest"> <part name="netype" type="xsd:string"/> <message name="getallnesbytyperesponse"> <message name="getrootnesrequest"> <message name="getrootnesresponse"> <message name="getrootneswithfeaturerequest"> <part name="featurestr" type="xsd:string"/> A-2
3 Appendix A InventoryAPI.wsdl <message name="getrootneswithfeatureresponse"> <message name="getrootnetypesrequest"> <message name="getrootnetypesresponse"> <part name="netypelist" type="tns:netypelist"/> <message name="getrootnesbytyperequest"> <part name="netype" type="xsd:string"/> <message name="getrootnesbytyperesponse"> <message name="getchildnesrequest"> <message name="getchildnesresponse"> <message name="getchildneswithfeaturerequest"> <part name="featurestr" type="xsd:string"/> <message name="getchildneswithfeatureresponse"> <message name="getchildnetypesrequest"> <message name="getchildnetypesresponse"> <part name="netypelist" type="tns:netypelist"/> <message name="getchildnesbytyperequest"> <part name="netype" type="xsd:string"/> <message name="getchildnesbytyperesponse"> <message name="getdescendantnesrequest"> <message name="getdescendantnesresponse"> <message name="getdescendantneswithfeaturerequest"> <part name="featurestr" type="xsd:string"/> <message name="getdescendantneswithfeatureresponse"> <message name="getdescendantnetypesrequest"> A-3
4 InventoryAPI.wsdl Appendix A <message name="getdescendantnetypesresponse"> <part name="netypelist" type="tns:netypelist"/> <message name="getdescendantnesbytyperequest"> <part name="netype" type="xsd:string"/> <message name="getdescendantnesbytyperesponse"> <message name="getnoterequest"> <message name="getnoteresponse"> <part name="note" type="xsd:string"/> <message name="setnoterequest"> <part name="userid" type="xsd:string"/> <part name="note" type="xsd:string"/> <message name="setnoteresponse"> <message name="appendnoterequest"> <part name="userid" type="xsd:string"/> <part name="note" type="xsd:string"/> <message name="appendnoteresponse"> <porttype name="inventoryapi"> <operation name="getne"> <input message="tns:getnerequest"/> <output message="tns:getneresponse"/> <operation name="normalizefqdn"> <input message="tns:normalizefqdnrequest"/> <output message="tns:normalizefqdnresponse"/> <operation name="haschild"> <input message="tns:haschildrequest"/> <output message="tns:haschildresponse"/> <operation name="getallnes"> <input message="tns:getallnesrequest"/> <output message="tns:getallnesresponse"/> <operation name="getallneswithfeature"> <input message="tns:getallneswithfeaturerequest"/> <output message="tns:getallneswithfeatureresponse"/> <operation name="getallnetypes"> <input message="tns:getallnetypesrequest"/> <output message="tns:getallnetypesresponse"/> A-4
5 Appendix A InventoryAPI.wsdl <operation name="getallnesbytype"> <input message="tns:getallnesbytyperequest"/> <output message="tns:getallnesbytyperesponse"/> <operation name="getrootnes"> <input message="tns:getrootnesrequest"/> <output message="tns:getrootnesresponse"/> <operation name="getrootneswithfeature"> <input message="tns:getrootneswithfeaturerequest"/> <output message="tns:getrootneswithfeatureresponse"/> <operation name="getrootnetypes"> <input message="tns:getrootnetypesrequest"/> <output message="tns:getrootnetypesresponse"/> <operation name="getrootnesbytype"> <input message="tns:getrootnesbytyperequest"/> <output message="tns:getrootnesbytyperesponse"/> <operation name="getchildnes"> <input message="tns:getchildnesrequest"/> <output message="tns:getchildnesresponse"/> <operation name="getchildneswithfeature"> <input message="tns:getchildneswithfeaturerequest"/> <output message="tns:getchildneswithfeatureresponse"/> <operation name="getchildnetypes"> <input message="tns:getchildnetypesrequest"/> <output message="tns:getchildnetypesresponse"/> <operation name="getchildnesbytype"> <input message="tns:getchildnesbytyperequest"/> <output message="tns:getchildnesbytyperesponse"/> <operation name="getdescendantnes"> <input message="tns:getdescendantnesrequest"/> <output message="tns:getdescendantnesresponse"/> <operation name="getdescendantneswithfeature"> <input message="tns:getdescendantneswithfeaturerequest"/> <output message="tns:getdescendantneswithfeatureresponse"/> <operation name="getdescendantnetypes"> <input message="tns:getdescendantnetypesrequest"/> <output message="tns:getdescendantnetypesresponse"/> <operation name="getdescendantnesbytype"> <input message="tns:getdescendantnesbytyperequest"/> <output message="tns:getdescendantnesbytyperesponse"/> A-5
6 InventoryAPI.wsdl Appendix A <operation name="getnote"> <input message="tns:getnoterequest"/> <output message="tns:getnoteresponse"/> <operation name="setnote"> <input message="tns:setnoterequest"/> <output message="tns:setnoteresponse"/> <operation name="appendnote"> <input message="tns:appendnoterequest"/> <output message="tns:appendnoteresponse"/> </porttype> <binding name="inventoryapiportbinding" type="tns:inventoryapi"> <soap:binding transport=" style="rpc"/> <operation name="getne"> <operation name="normalizefqdn"> <operation name="haschild"> <operation name="getallnes"> A-6
7 Appendix A InventoryAPI.wsdl <operation name="getallneswithfeature"> <operation name="getallnetypes"> <operation name="getallnesbytype"> <operation name="getrootnes"> <operation name="getrootneswithfeature"> A-7
8 InventoryAPI.wsdl Appendix A <operation name="getrootnetypes"> <operation name="getrootnesbytype"> <operation name="getchildnes"> <operation name="getchildneswithfeature"> <operation name="getchildnetypes"> <operation name="getchildnesbytype"> A-8
9 Appendix A InventoryAPI.wsdl <operation name="getdescendantnes"> <operation name="getdescendantneswithfeature"> <operation name="getdescendantnetypes"> <operation name="getdescendantnesbytype"> <operation name="getnote"> A-9
10 EventAPI.wsdl Appendix A <operation name="setnote"> <operation name="appendnote"> </binding> <service name="inventoryapiservice"> <port name="inventoryapiport" binding="tns:inventoryapiportbinding"> <soap:address location="replace_with_actual_url"/> </port> </service> </definitions> EventAPI.wsdl <?xml version="1.0" encoding="utf-8" standalone="yes"?> <definitions targetnamespace=" name="eventapiservice" xmlns:tns=" xmlns:xsd=" xmlns:soap=" xmlns=" <types> <xsd:schema> <xsd:import namespace=" schemalocation="mwtm.xsd"/> </xsd:schema> </types> <message name="apistatus"> <part name="apistatus" element="tns:apistatus"/> <message name="getalleventsastrapsrequest"> <part name="target" type="tns:traptarget"/> <message name="getalleventsastrapsresponse"> <part name="eventcount" type="xsd:int"/> A-10
11 Appendix A EventAPI.wsdl <message name="getfilteredeventsastrapsrequest"> <part name="target" type="tns:traptarget"/> <part name="filter" type="tns:eventfilter"/> <message name="getfilteredeventsastrapsresponse"> <part name="eventcount" type="xsd:int"/> <message name="cleareventsrequest"> <part name="eventlist" type="tns:eventidlist"/> <part name="userid" type="xsd:string"/> <part name="note" type="xsd:string"/> <message name="cleareventsresponse"> <message name="acknowledgeeventsrequest"> <part name="eventlist" type="tns:eventidlist"/> <part name="userid" type="xsd:string"/> <part name="note" type="xsd:string"/> <message name="acknowledgeeventsresponse"> <message name="deleteeventsrequest"> <part name="eventlist" type="tns:eventidlist"/> <message name="deleteeventsresponse"> <message name="changeseveritiesrequest"> <part name="eventlist" type="tns:eventidlist"/> <part name="severity" type="xsd:string"/> <part name="userid" type="xsd:string"/> <part name="note" type="xsd:string"/> <message name="changeseveritiesresponse"> <message name="getnoterequest"> <part name="eventid" type="xsd:long"/> <message name="getnoteresponse"> <part name="note" type="xsd:string"/> <message name="setnoterequest"> <part name="eventid" type="xsd:long"/> <part name="userid" type="xsd:string"/> <part name="note" type="xsd:string"/> <message name="setnoteresponse"> <message name="appendnoterequest"> <part name="eventid" type="xsd:long"/> <part name="userid" type="xsd:string"/> <part name="note" type="xsd:string"/> <message name="appendnoteresponse"> <porttype name="eventapi"> <operation name="getalleventsastraps"> <input message="tns:getalleventsastrapsrequest"/> <output message="tns:getalleventsastrapsresponse"/> <operation name="getfilteredeventsastraps"> <input message="tns:getfilteredeventsastrapsrequest"/> A-11
12 EventAPI.wsdl Appendix A <output message="tns:getfilteredeventsastrapsresponse"/> <operation name="clearevents"> <input message="tns:cleareventsrequest"/> <output message="tns:cleareventsresponse"/> <operation name="acknowledgeevents"> <input message="tns:acknowledgeeventsrequest"/> <output message="tns:acknowledgeeventsresponse"/> <operation name="deleteevents"> <input message="tns:deleteeventsrequest"/> <output message="tns:deleteeventsresponse"/> <operation name="changeseverities"> <input message="tns:changeseveritiesrequest"/> <output message="tns:changeseveritiesresponse"/> <operation name="getnote"> <input message="tns:getnoterequest"/> <output message="tns:getnoteresponse"/> <operation name="setnote"> <input message="tns:setnoterequest"/> <output message="tns:setnoteresponse"/> <operation name="appendnote"> <input message="tns:appendnoterequest"/> <output message="tns:appendnoteresponse"/> </porttype> <binding name="eventapiportbinding" type="tns:eventapi"> <soap:binding transport=" style="rpc"/> <operation name="getalleventsastraps"> <operation name="getfilteredeventsastraps"> A-12
13 Appendix A EventAPI.wsdl <operation name="clearevents"> <operation name="acknowledgeevents"> <operation name="deleteevents"> <operation name="changeseverities"> <operation name="getnote"> <operation name="setnote"> A-13
14 ProvisionAPI.wsdl Appendix A <operation name="appendnote"> </binding> <service name="eventapiservice"> <port name="eventapiport" binding="tns:eventapiportbinding"> <soap:address location="replace_with_actual_url"/> </port> </service> </definitions> ProvisionAPI.wsdl <?xml version="1.0" encoding="utf-8" standalone="yes"?> <definitions targetnamespace=" name="provisionapiservice" xmlns:tns=" xmlns:xsd=" xmlns:soap=" xmlns=" <types> <xsd:schema> <xsd:import namespace=" schemalocation="mwtm.xsd"/> </xsd:schema> </types> <message name="apistatus"> <part name="apistatus" element="tns:apistatus"/> <message name="provisionrequest"> <part name="request" type="tns:provisionrequest"/> <message name="provisionresponse"> <porttype name="provisionapi"> <operation name="provision"> <input message="tns:provisionrequest"/> <output message="tns:provisionresponse"/> A-14
15 Appendix A MWTM.xsd </porttype> <binding name="provisionapiportbinding" type="tns:provisionapi"> <soap:binding transport=" style="rpc"/> <operation name="provision"> </binding> <service name="provisionapiservice"> <port name="provisionapiport" binding="tns:provisionapiportbinding"> <soap:address location="replace_with_actual_url"/> </port> </service> </definitions> MWTM.xsd <?xml version="1.0" encoding="utf-8" standalone="yes"?> <xs:schema version="1.0" targetnamespace=" xmlns:tns=" xmlns:xs=" <xs:include schemalocation="common.xsd"/> <xs:include schemalocation="event.xsd"/> <xs:include schemalocation="inventory.xsd"/> <xs:include schemalocation="provision.xsd"/> </xs:schema> Common.xsd <?xml version="1.0" encoding="utf-8" standalone="yes"?> <xs:schema version="1.0" targetnamespace=" xmlns:tns=" xmlns:xs=" <!-- APIStatus contains StatusCode and Message when error occurs --> <xs:complextype name="apistatus"> A-15
16 Inventory.xsd Appendix A <xs:element name="statuscode" type="xs:int"/> <xs:element name="message" type="xs:string"/> <xs:element name="apistatus" type="tns:apistatus"/> <!-- inventory attribute types: Config, Monitor and All --> <xs:simpletype name="inventorytype"> <xs:restriction base="xs:string"> <xs:enumeration value="config"/> <xs:enumeration value="monitor"/> <xs:enumeration value="all"/> </xs:restriction> </xs:simpletype> <!-- provisioning operation types: Add, Modify, Delete --> <xs:simpletype name="operationtype"> <xs:restriction base="xs:string"> <xs:enumeration value="add"/> <xs:enumeration value="modify"/> <xs:enumeration value="delete"/> </xs:restriction> </xs:simpletype> </xs:schema> Inventory.xsd <?xml version="1.0" encoding="utf-8" standalone="yes"?> <!-- Copyright (c) Cisco Systems, Inc. All rights reserved. --> <xs:schema version="1.0" targetnamespace=" xmlns:tns=" xmlns:xs=" <!-- Attribute is a name/value pair --> <xs:complextype name="attribute"> <xs:simplecontent> <xs:extension base="xs:string"> <xs:attribute name="name" type="xs:string" use="required"/> <xs:attribute name="array" type="xs:boolean" default="false"/> </xs:extension> </xs:simplecontent> <!-- AttributeList is the base type for NetworkElement, AttributeGroup and Feature. It contains elements of Attributes, and/or AttributeGroups --> <xs:complextype name="attributelist"> <xs:choice minoccurs="0" maxoccurs="unbounded"> <xs:element name="attribute" type="tns:attribute"/> <xs:element name="attributegroup" type="tns:attributegroup"/> </xs:choice> <!-- AttributeGroup is a heterogeneous grouping of attributes --> A-16
17 Appendix A Inventory.xsd <xs:complextype name="attributegroup"> <xs:complexcontent> <xs:extension base="tns:attributelist"> <xs:attribute name="name" type="xs:string" use="required"/> <xs:attribute name="array" type="xs:boolean" default="false"/> <xs:attribute name="arraykey" type="xs:string"/> </xs:extension> </xs:complexcontent> <!-- Feature is a AttributeList with a feature name --> <!-- A Feature can optionally have a operation type for provisioning --> <xs:complextype name="feature"> <xs:complexcontent> <xs:extension base="tns:attributelist"> <xs:attribute name="name" type="xs:string" use="required"/> </xs:extension> </xs:complexcontent> <!-- NetworkElement is an AttributeList with a list of Features --> <!-- NetworkElement has type/subtype and FQDN for object identifier --> <xs:complextype name="networkelement"> <xs:complexcontent> <xs:extension base="tns:attributelist"> <xs:element name="feature" type="tns:feature" minoccurs="0" maxoccurs="unbounded"/> <xs:attribute name="parentfqdn" type="xs:string" use="required"/> <xs:attribute name="type" type="xs:string" use="required"/> <xs:attribute name="subtype" type="xs:string"/> <xs:attribute name="provisionable" type="xs:boolean" default="true"/> </xs:extension> </xs:complexcontent> <xs:element name="networkelement" type="tns:networkelement"/> <!-- NetworkElementList is a List of NetworkElement --> <xs:complextype name="networkelementlist"> <xs:element name="networkelement" type="tns:networkelement" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="networkelementlist" type="tns:networkelementlist"/> <xs:complextype name="netypelist"> <xs:element name="netype" type="xs:string" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="netypelist" type="tns:netypelist"/> </xs:schema> A-17
18 Event.xsd Appendix A Event.xsd <?xml version="1.0" encoding="utf-8" standalone="yes"?> <xs:schema version="1.0" targetnamespace=" xmlns:tns=" xmlns:xs=" <!-- A list of event IDs --> <xs:complextype name="eventidlist"> <xs:element name="id" type="xs:long" maxoccurs="unbounded"/> <xs:element name="eventidlist" type="tns:eventidlist"/> <!-- Trap Target specifies target host/port and SNMP parameters to send SNMP Trap notification to --> <xs:complextype name="traptarget"> <xs:element name="hostname" type="xs:string"/> <xs:element name="port" type="xs:int"/> <xs:element name="community" type="xs:string"/> <xs:element name="snmpversion"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:enumeration value="1"/> <xs:enumeration value="2c"/> </xs:restriction> </xs:simpletype> </xs:element> <xs:element name="mib"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:enumeration value="cisco-epm"/> <xs:enumeration value="cisco-syslog"/> </xs:restriction> </xs:simpletype> </xs:element> <xs:element name="traptarget" type="tns:traptarget"/> <!-- Event Filter --> <!-- If more than one conditions are specified, EventFilter applies "AND" on all specified conditions --> <xs:complextype name="eventfilter"> <xs:element name="eventids" type="tns:eventidlist" minoccurs="0"/> <xs:element name="startdate" type="xs:datetime" minoccurs="0"/> <xs:element name="enddate" type="xs:datetime" minoccurs="0"/> <xs:element name="severity" type="xs:string" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="category" type="xs:string" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="acknowledged" type="xs:boolean" minoccurs="0"/> <xs:element name="cleared" type="xs:boolean" minoccurs="0"/> <!-- filter "text" is based on whether event message contains given text --> <xs:element name="messagetext" type="xs:string" minoccurs="0"/> A-18
19 Appendix A Provision.xsd <xs:element name="networkelement" type="xs:string" minoccurs="0"/> <xs:element name="forward" type="xs:boolean" minoccurs="0"/> <xs:element name="eventfilter" type="tns:eventfilter"/> </xs:schema> Provision.xsd <?xml version="1.0" encoding="utf-8" standalone="yes"?> <!-- Copyright (c) Cisco Systems, Inc. All rights reserved. --> <xs:schema version="1.0" targetnamespace=" xmlns:tns=" xmlns:xs=" <xs:include schemalocation="common.xsd"/> <xs:include schemalocation="inventory.xsd"/> <xs:complextype name="devicecredential"> <xs:element name="username" type="xs:string"/> <xs:element name="password" type="xs:string"/> <xs:element name="enableusername" type="xs:string"/> <xs:element name="enablepassword" type="xs:string"/> <!-- a ProvisionOperation is an operation on NetworkElement --> <xs:complextype name="provisionoperation"> <xs:complexcontent> <xs:extension base="tns:networkelement"> <xs:element name="devicecredential" type="tns:devicecredential" minoccurs="0"/> <xs:attribute name="operation" type="tns:operationtype" use="required"/> <xs:attribute name="ioswritetostartup" type="xs:boolean" default="false"/> </xs:extension> </xs:complexcontent> <xs:element name="provisionoperation" type="tns:provisionoperation"/> <xs:complextype name="ioswritetostartup"> <xs:element name="devicecredential" type="tns:devicecredential" minoccurs="0"/> <xs:attribute name="fqdn" type="xs:string"/> <xs:complextype name="syncfromdevice"> <xs:attribute name="fqdn" type="xs:string"/> <!-- A ProvisionRequest contains a list of ProvisionOperation --> <xs:complextype name="provisionrequest"> A-19
20 Provision.xsd Appendix A <xs:choice minoccurs="0" maxoccurs="unbounded"> <xs:element name="provisionoperation" type="tns:provisionoperation"/> <xs:element name="ioswritetostartup" type="tns:ioswritetostartup"/> <xs:element name="syncfromdevice" type="tns:syncfromdevice"/> </xs:choice> <xs:element name="provisionrequest" type="tns:provisionrequest"/> </xs:schema> A-20
MWTM 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 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 informationCisco Prime Central 1.0 API Guide
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
More information<xsd:element name="name" maxoccurs="1" minoccurs="0" <xsd:element name="parentaccountid" maxoccurs="1" minoccurs="0" <xsd:element name="parentaccounti
More information
Oracle 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 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 informationWeb 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 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 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 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 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 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 informationGoProCaseSoap.wsdl <?xml version='1.0' encoding='utf-8'?><wsdl:definitions name="goprocasesoapservice"
More information
Restricting 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 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 informationEl fichero de descripción del servicio se puede obtener a partir de la siguiente URL:
WSDL El fichero de descripción del servicio se puede obtener a partir de la siguiente URL: https://invenes.oepm.es/invenesservices/invenessearchservice?wsdl Contenido del WSDL
More informationMWTM Provision API
CHAPTER 4 The allows the Operations Support and System (OSS) to provision the IP Transfer Point (ITP) Linkset, Link, Application Server (AS), and ASP using a programming interface. The MWTM 6.1.7 provides
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 informationTesting of Service Oriented Architectures A practical approach / APPENDIX V1.0
Testing of Service Oriented Architectures A practical approach / APPENDIX V1.0 Schahram Dustdar, Stephan Haslinger 1 Distributed Systems Group, Vienna University of Technology dustdar@infosys.tuwien.ac.at
More information3GPP TS V ( )
Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; User Data Convergence (UDC); User Data Repository Access Protocol over the Ud interface;
More informationETSI TS V9.2.0 ( ) Technical Specification
Technical Specification Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; User Data Convergence (UDC); User data repository access protocol
More informationUser Manual. HIPAA Transactions System Integration for Channel Partner Vendor. Version 15.2 May 2015
User Manual HIPAA Transactions System Integration for Channel Partner Vendor Version 15.2 May 2015 Trademarks and Copyrights Optum HIPAA Transactions System Integration Document Channel Partner Vendor
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 informationMailtips 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 informationProject Members: Aniket Prabhune Reenal Mahajan Mudita Singhal
CS-5604 Information Storage and Retrieval Project Report Scenario/Class Diagram Synthesis (American South 2) Project Members: Aniket Prabhune (aprabhun@vt.edu) Reenal Mahajan (remahaja@vt.edu) Mudita Singhal
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 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 information[MS-DPMDS]: Master Data Services Data Portability Overview. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-DPMDS]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationDeveloping Applications for the Java EE 7 Platform 6-2
Developing Applications for the Java EE 7 Platform 6-2 Developing Applications for the Java EE 7 Platform 6-3 Developing Applications for the Java EE 7 Platform 6-4 Developing Applications for the Java
More informationCustom Data Access with MapObjects Java Edition
Custom Data Access with MapObjects Java Edition Next Generation Command and Control System (NGCCS) Tactical Operations Center (TOC) 3-D Concurrent Technologies Corporation Derek Sedlmyer James Taylor 05/24/2005
More informationLifecycle Controller (LC) XML Schema Guide
Lifecycle Controller (LC) XML Schema Guide Interpretation of XML schema used by LC Steven Zessin Divya Vijayvargiya Pushkala Iyer This document is for informational purposes only and may contain typographical
More informationXSD Reference For EXPRESS XML language
VTT-TEC-ADA-08 Page 1 SECOM Co., Ltd. / VTT Building and Transport Yoshinobu Adachi E-Mail: yoshinobu.adachi@vtt.fi VTT-TEC-ADA-08 XSD Reference For EXPRESS XML language 2002/02/11 1. INTRODUCTION... 2
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 informationTED schemas. Governance and latest updates
TED schemas Governance and latest updates Enric Staromiejski Torregrosa Carmelo Greco 9 October 2018 Agenda 1. Objectives 2. Scope 3. TED XSD 3.0.0 Technical harmonisation of all TED artefacts Code lists
More informationeportfolio Interoperability XML Specification
eportfolio Interoperability XML Specification Version 1.0 DRAFT eportaro, Incorporated Updated: 29 January 2003 www.epixspec.org 2003 eportaro, Inc. Page i Notice 2003 eportaro Incorporated. All rights
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 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 informationOracle Enterprise Data Quality
Oracle Enterprise Data Quality Automated Loading and Running of Projects Version 9.0 January 2012 Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved. Oracle Enterprise Data Quality,
More informationPhysician Data Center API API Specification. 7/3/2014 Federation of State Medical Boards Kevin Hagen
7/3/2014 Federation of State Medical Boards Kevin Hagen Revision Description Date 1 Original Document 2/14/2014 2 Update with Degree search field 7/3/2014 Overview The Physician Data Center (PDC) offers
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 informationCustomer Market Results Interface (CMRI) For RC Interface Specification. Version: 1.0.0
Customer Market Results Interface (CMRI) For RC Interface Specification Version: 1.0.0 November 1, 2018 Revision History Date Version Description 11/01/2018 1.0.0 Initial document release Page 2 of 10
More informationDAFTAR REFERENSI. [GRE07] diakses tanggal 7 Desember 2007.
DAFTAR REFERENSI [GRE07] http://en.wikipedia.org/wiki/gregorian_calendar diakses tanggal 7 Desember 2007. [PHP07] http://www.php.net diakses tanggal 7 Desember 2007. [RIC06] Richards, Robert. Pro PHP XML
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
INDEX. Broadband Wireless Gateway 2-4 BWG 2-4
INDEX A ADD operation 4-3 alarms, definitions 3-1 API event 1-3 inventory 1-3, 2-1 provisioning 1-4 API operations 3-3 MWTM inventory 2-16 MWTM provision 4-7 application programming interface. See API
More informationQualys Cloud Platform v2.x API Release Notes
API Release Notes Version 2.37 February 20, 2019 Qualys Cloud Suite API gives you many ways to integrate your programs and API calls with Qualys capabilities. You ll find all the details in our user guides,
More informationData Bus Client Interface Manager Interface Control Document
SunGuide SM : Data Bus Client Interface Manager Interface Control Document SunGuide-DB-CIM-ICD-1.0.0 Prepared for: Florida Department of Transportation Traffic Engineering and Operations Office 605 Suwannee
More informationAdministering Oracle Enterprise Data Quality 12c (12.2.1)
[1]Oracle Fusion Middleware Administering Oracle Enterprise Data Quality 12c (12.2.1) E56642-01 October 2015 Describes how to administer Oracle Enterprise Data Quality. Oracle Fusion Middleware Administering
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 informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSXPROP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationApache UIMA Regular Expression Annotator Documentation
Apache UIMA Regular Expression Annotator Documentation Written and maintained by the Apache UIMA Development Community Version 2.3.1 Copyright 2006, 2011 The Apache Software Foundation License and Disclaimer.
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 informationConfiguring Capabilities Manager
Finding Feature Information, page 1 Prerequisites for, page 1 Information About Capabilities Manager, page 1 How to Configure Capabilities Manager, page 5 Additional References, page 8 Feature Information
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 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 informationAON Schemas. Archive Schema APPENDIXA
APPENDIXA This appendix contains schemas used by AMC. It includes the following: Archive Schema, page A-1 Programmatic Management Interface APIs, page A-15 Message Log Schemas, page A-26 Note This information
More informationSchema schema-for-json.xsd
Schema schema-for-json.xsd schema location: attributeformdefault: elementformdefault: targetnamespace:..\schema-for-json.xsd qualified http://www.w3.org/2015/exi/json Elements Complex types Simple types
More informationAlwaysUp Web Service API Version 11.0
AlwaysUp Web Service API Version 11.0 0. Version History... 2 1. Overview... 3 2. Operations... 4 2.1. Common Topics... 4 2.1.1. Authentication... 4 2.1.2. Error Handling... 4 2.2. Get Application Status...
More information<xs:element name="relationshipdata" type="rr:relationshipdatatype"/> <xs:element name="header" type="rr:rrheadertype"> </xs:element>
More information
Creating and Modifying EAP-FAST Profiles for Distribution to Users
CHAPTER 4 Creating and Modifying EAP-FAST Profiles for Distribution to Users This chapter explains how configure EAP-FAST module profiles both by using a Group Policy Object editor and by modifying the
More information[MS-OXWSXPROP]: Extended Properties Structure. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWSXPROP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
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 informationKeio Virtual Sensor System based on Sensor- Over- XMPP
Keio Virtual Sensor System based on Sensor- Over- XMPP 1. Basic information Keio virtual sensor system is based on XMPP PubSub mechanism. Thus, we basically follow XMPP PubSub protocol (XEP- 0060: Publish-
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 informationVDS Service Broker APIs
CHAPTER 2 This chapter describes the HTTPS RESTful APIs for VDS-SB and the XML schema. CDN Management API, page 2-1 BFQDN Management API BFQDN Policy API CDN Adaptation Policy API CDN Selection Policy
More informationPrivacy and Personal Data Collection Disclosure. Legal Notice
Privacy and Personal Data Collection Disclosure Certain features available in Trend Micro products collect and send feedback regarding product usage and detection information to Trend Micro. Some of this
More informationBrief guide for XML, XML Schema, XQuery for YAWL data perspective
Brief guide for XML, XML Schema, XQuery for YAWL data perspective Carmen Bratosin March 16, 2009 1 Data perspective in YAWL YAWL engine files are XML based. Therefore, YAWL uses XML for data perspective
More informationDeploying Axis in Mission-Critical Environments
Deploying Axis in Mission-Critical Environments Eugene Ciurana eugenex@walmart.com http://eugeneciurana.com Deploying Apache Axis in Mission-Critical Applications When should I suggest web services? When
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 information2006 Martin v. Löwis. Data-centric XML. XML Schema (Part 1)
Data-centric XML XML Schema (Part 1) Schema and DTD Disadvantages of DTD: separate, non-xml syntax very limited constraints on data types (just ID, IDREF, ) no support for sets (i.e. each element type
More informationApproaches to using NEMSIS V3 Custom Elements
NEMSIS TAC Whitepaper Approaches to using NEMSIS V3 Custom Elements Date August 17, 2011 July 31, 2013 (added section Restrictions, page 11) March 13, 2014 ( CorrelationID now reads CustomElementID as
More informationBBPS API Sepcifications
BBPS API Sepcifications v11.0 BBPS API Sepcifications v11.0 Page 1 Table of Contents 1 Bill Fetch Request 4 Sample Bill Fetch Request API 4 Bill Fetch Request Tag Details 5 Bill Fetch Request XSD 6 2 Bill
More informationConfiguring Capabilities Manager
Finding Feature Information, page 1 Prerequisites for, page 1 Information About Capabilities Manager, page 1 How to Configure Capabilities Manager, page 5 Additional References, page 10 Feature Information
More informationAutomated Load Forecast System (ALFS) For RC Interface Specification
Automated Load Forecast System (ALFS) For RC Interface Specification Version: 1.0 October 22, 2018 Revision History Date Version Description 10/23/2018 1.0 Initial document release related to the Load
More informationPISOA Interface Specification. Fall 2017 Release
PISOA Interface Specification Fall 2017 Release Version: 1.0 July 21, 2017 Revision History Date Version Description 07/21/2017 1.0 Initial document release related to the PISO Interfaces. RequestVERMeasurements
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 informationOracle Fusion Middleware Administering Oracle Enterprise Data Quality. 12c ( )
Oracle Fusion Middleware Administering Oracle Enterprise Data Quality 12c (12.2.1.3.0) E81338-01 July 2017 Oracle Fusion Middleware Administering Oracle Enterprise Data Quality, 12c (12.2.1.3.0) E81338-01
More information[MS-MSL]: Mapping Specification Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-MSL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationXML extensible Markup Language
extensible Markup Language Eshcar Hillel Sources: http://www.w3schools.com http://java.sun.com/webservices/jaxp/ learning/tutorial/index.html Tutorial Outline What is? syntax rules Schema Document Object
More informationSoftware Engineering Methods, XML extensible Markup Language. Tutorial Outline. An Example File: Note.xml XML 1
extensible Markup Language Eshcar Hillel Sources: http://www.w3schools.com http://java.sun.com/webservices/jaxp/ learning/tutorial/index.html Tutorial Outline What is? syntax rules Schema Document Object
More informationFall, 2005 CIS 550. Database and Information Systems Homework 5 Solutions
Fall, 2005 CIS 550 Database and Information Systems Homework 5 Solutions November 15, 2005; Due November 22, 2005 at 1:30 pm For this homework, you should test your answers using Galax., the same XQuery
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-CPSWS]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OTPCE]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More information[MS-TMPLDISC]: Template Discovery Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-TMPLDISC]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationDigital Signage Network Playlog Standards
Digital Signage Network Playlog Standards Version 1.1, August 23, 2006 Editor-In-Chief William Wu (DS-IQ) william.wu@ds-iq.com Editors Jeff Porter (Scala) jeff.porter@scala.com Steve Saxe (3M) sgsaxe@mmm.com
More informationPTS XML STANDARD GUIDELINE
PTS XML STANDARD GUIDELINE September 2012 Turkish Medicines & Medical Devices Agency, Department of Pharmaceutical Track & Trace System Söğütözü Mahallesi 2176 Sok. No: 5 P.K.06520 Çankaya, Ankara Phone:
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-MSL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSXPROP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
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 informationOracle Hospitality OPERA Electronic Distribution Systems (OEDS) Activity Web Service Specifications Version 5.1
Oracle Hospitality OPERA Electronic Distribution Systems (OEDS) Activity Web Service Specifications Version 5.1 January 2018 Copyright 1987, 2018, Oracle and/or its affiliates. All rights reserved. This
More information<?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:types="http://www.slc.co.uk/course/types/1.0" xmlns:xs="http://www.w3.org/2001/xmlschema"
More information
No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXSHRMSG]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationMarkup Languages. Lecture 4. XML Schema
Markup Languages Lecture 4. XML Schema Introduction to XML Schema XML Schema is an XML-based alternative to DTD. An XML schema describes the structure of an XML document. The XML Schema language is also
More informationPrivacy and Personal Data Collection Disclosure. Legal Notice
Privacy and Personal Data Collection Disclosure Certain features available in Trend Micro products collect and send feedback regarding product usage and detection information to Trend Micro. Some of this
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 information[MS-CPSWS]: SharePoint Claim Provider Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-CPSWS]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More information