Automotive Append - Version 1.0.0

Size: px
Start display at page:

Download "Automotive Append - Version 1.0.0"

Transcription

1 Automotive Append - Version WSDL: Product Web Page: Description: StrikeIron s Automotive Append is a data enrichment service that can help expand your view of your customer by identifying which vehicles they own. What vehicles do your customers own that are likely in need of service or aftermarket parts? Who on your list might be shopping for a new vehicle soon? What prospects may be looking for new auto insurance based on a recent purchase? Dealerships, parts retailers, vehicle insurers, and marketers in related industries can use Automotive Append to answer these questions. For better sales and marketing, use Automotive Append to understand customer history and buying patterns. Create demographics about the vehicles purchased within a given regional area, stay ahead of your competition through a better understanding of vehicle buying trends and new market opportunities, and use it to personalize aftermarket sales to a given customer. Required License Information: The LicenseInfo parameter in our Web services provides the authentication credentials that allow you to invoke the Web service. If you are registered with StrikeIron, use the UserID and Password associated with your StrikeIron account in the UserID and Password fields. Alternatively, you can also use your license key obtained from your StrikeIron Account (leave the password blank). LicenseInfo Field: RegisteredUser Input UserID: Password: License Subscription Information Output LicenseStatusCode: This field returns a numeric code indicating the StrikeIron license action taken as a result of invoking this operation from the User ID and Password used for input. Valid license codes are 0, 1, and 2. For example, a valid User ID and Password returns the code 0 with a corresponding LicenseStatus value of Valid license key. LicenseStatus: This field returns the status of the StrikeIron User ID and Password corresponding to the LicenseStatusCode. LicenseActionCode: This field returns a numeric code indicating the StrikeIron license action taken as a result of invoking this operation. GetRemainingHits returns the code 5 with a corresponding LicenseAction value of Get remaining hits. LicenseAction: This field returns the license action taken as a result of invoking this operation from the User ID and Password used corresponding to the LicenseActionCode. RemainingHits: This field returns the number of hits against the StrikeIron User ID and Password used when invoking this operation. Integer. Amount: This field returns the number of hits used from the StrikeIron User ID provided to invoke this operation. Sample Input johndoe@strikeiron.com Password1 Sample Output 0 Valid license key 0 Decremented hit count 2 0 1

2 Available operations GetAutoDemographics GetAutoDemographicsBatch GetStatusCodesForMethod GetStatusCodes GetServiceInfo GetRemainingHits GetAutoDemographics Provides vehicle ownership information for a given individual or VIN. Operation: GetAutoDemographics Input (ServiceStatus) Sample Input Confidence Level: Confidence is an indicator of how closely an existing record matches the information you provided. LooseMatch: Equates to a good confidence match ApproximateMatch: Equates to a better confidence match SpecificMatch: Equates to the best confidence match LooseMatch First Name: The owner s first name. George Middle Name: The owner s middle name (or initial) J Last Name: The owner s last name. Menchiem Name Suffix: Jr., Sr., and the like Sr Address Line 1: Residential address for the owner Weston Parkway Address Line 2: Apt., Building, Floor, Apt 5 City: The city where the owner resides Cary State: The State where the owner resides NC ZIP: The postal code of the owner. A four-digit Zip+4 extension can be appended to the Zip delineated with - VIN: 17 characters, numbers and letters, associated with a specific vehicle or

3 Operation: GetAutoDemographicsResponse Output (ServiceResult) ServiceStatus: The response code provided by the web service for this operation. ServiceResult: The description for the ServiceStatus code. StatusNbr: This field returns a number referring to the status of this request. (See GetStatusCodes) StatusDescription: This field returns the description of the status number. (See GetStatusCodes) Sample Output 200 Found 200 Found Confidence Level: Confidence is an indicator of how closely an existing record matches the information you provided. LooseMatch: Equates to a good confidence match ApproximateMatch: Equates to a better confidence match SpecificMatch: Equates to the best confidence match ApproximateMatch NumRecords: The number of records within this result, 1 Records: The number of records within the array? 1 First Name: The owner s first name. Middle Name: The owner s middle name (or initial) Last Name: The owner s last name. George J Mancheem Name Suffix: Jr., Sr., and the like Address Line 1: Residential address for the owner Weston Parkway Address Line 2: Apt., Building, Floor, Apt 125 City: The city where the owner resides Cary State: The State where the owner resides ZIP: The postal code of the owner. A four-digit Zip+4 extension can be appended to the Zip delineated with - VIN: 17 characters, numbers and letters, associated with a specific vehicle. NC or AutoYear: Production year of the vehicle 1989 Make: Manufacturer of the vehicle Model: The manufacturer s designation for this class of car Honda Civic TransactionDate: Date in which vehicle was acquired 10/24/1989 Phone: Phone number of the person who acquired vehicle. Note that this phone number is that provided at the time of transaction and the current phone number of the individual may be different

4 GetAutoDemographics Rules 1. GetAutoDemographics and GetAutoDemographicsBatch lookups can be minimally performed using two sets of lookup criteria: a. Address Searching: Searching by address requires a minimum of either: i. Address Line 1 AND (city and State) or Zipcode (Zip or Zip+4) ii. Note that if searching by address the use of Zip/Zip+4 often produces the best results b. VIN searching: Searching by Vehicle Identification Number requires a minimum of: i. Vehicle Identification Number VIN 2. For a GetAutoDemographics request, the client submits the names and addresses of one or more individuals and expects one or more demographics to be returned for each individual or household. A Household level match is assumed unless an individual match is requested from the city and state. 3. For multi-zip cities the starting zip code will be used. This will affect the accuracy of the confidence levels returned. 4. The client may submit a VIN and expect a name and address to be returned plus one or more demographics for the household. A VIN reverse match cannot be combined with a name/address or address match search. 4

5 GetAutoDemographicsBatch Provides vehicle ownership information for a given individual or VIN. Processes one to many lookup requests per batch call. Operation: GetAutoDemographicsBatch Input (ServiceStatus) Confidence Level: Confidence is an indicator of how closely an existing record matches the information you provided. ITERATES = Requests LooseMatch: Equates to a good confidence match ApproximateMatch: Equates to a better confidence match SpecificMatch: Equates to the best confidence match Sample Input SpecificMatch Requests: The number of records/lookups associated to this batch transaction. 30 First Name: The owner s first name. George Middle Name: The owner s middle name (or initial) J Last Name: The owner s last name. Menchiem Name Suffix: Jr., Sr., and the like Sr Address Line 1: Residential address for the owner Weston Parkway Address Line 2: Apt., Building, Floor, Apt 5 City: The city where the owner resides Cary State: The State where the owner resides NC ZIP: The postal code of the owner. A four-digit Zip+4 extension can be appended to the Zip delineated with - VIN: 17 characters, numbers and letters, associated with a specific vehicle. Phone: Phone number of the person who acquired vehicle. Note that this phone number is that provided at the time of transaction and the current phone number of the individual may be different. GetAutoDemographicsBatch Rules 1. Reference the rules found for the GetAutoDemographics operation or

6 GetAutoDemographicsBatchResponse Provides vehicle ownership information for a given individual or VIN as response to the corresponding Get call. Operation: GetAutoDemographicsBatchResponse Output (ServiceResult) StatusNbr: This field returns a number referring to the status of this request. (See GetStatusCodes) StatusDescription: Returns the description of the status number. Sample Input 200 Found Confidence Level: Confidence is an indicator of how closely an existing record matches the information you provided. LooseMatch: Equates to a good confidence match ApproximateMatch: Equates to a better confidence match SpecificMatch: Equates to the best confidence match SpecificMatch ITERATES = NumRecords NumRecords: The number of records/lookups associated to this batch transaction. 30 First Name: The owner s first name. George Middle Name: The owner s middle name (or initial) J Last Name: The owner s last name. Menchiem Name Suffix: Jr., Sr., and the like Sr Address Line 1: Residential address for the owner Weston Parkway Address Line 2: Apt., Building, Floor, Apt 5 City: The city where the owner resides Cary State: The State where the owner resides NC ZIP: The postal code of the owner. A four-digit Zip+4 extension can be appended to the Zip delineated with - VIN: 17 characters, numbers and letters, associated with a specific vehicle or AutoYear: Production year of the vehicle 1989 Make: Manufacturer of the vehicle Honda Model: The manufacturer s designation for this class of car Civic TransactionDate: Date in which vehicle was acquired 10/24/1989 Phone: Phone number of the person who acquired vehicle. Note that this phone number is that provided at the time of transaction and the current phone number of the individual may be different. StatusNbr: This field returns a number referring to the status of this particular iteration lookup. (See GetStatusCodes) StatusDescription: Returns the description of the iteration lookup status number. 200 Found 6

7 GetStatusCodes This operation provides information about the Web service. The result set of this input is a list of all status codes and descriptions as a point of reference. Operation: GetStatusCodes Input (ServiceStatus) Note: The only input needed for this operation is the LicenseInfo (top of this document) data. Sample Input (No input required) Operation: GetStatusCodes Output (ServiceResult) StatusNbr: This field returns a number referring to the status of this request. StatusDescription: Returns the description of the status number. Sample Output 200 Found Operation: GetStatusCodes Output StatusNbr StatusDescription 200 Found 300 Not Found 500 Internal Error Sample Output Seen on left GetStatusCodesForMethod Returns the status codes available on a method-by-method basis. Operation: GetStatusCodesForMethod Input (ServiceStatus) MethodName: The name of the method for which you want to see relevant status codes. Operation: GetStatusCodesForMethod Output (ServiceResult) StatusNbr: This field returns a number referring to the status of this request. StatusDescription: Returns the description of the status number. Sample Input GetRemainingHits Sample Output Refer to GetStatusCodes Refer to GetStatusCodes 7

8 GetServiceInfo Provides status and details associated with the web service. Operation: GetServiceInfo Input (ServiceStatus) Note: The only input needed for this operation is the LicenseInfo data. This operation provides information about the Web service. Sample Input (No input required) Operation: GetServiceInfo Output (ServiceResult) LicenseStatusCode: This field returns a numeric code indicating the StrikeIron license action taken as a result of invoking this operation from the User ID and Password used for input. Valid license codes are 0, 1, and 2. For example, a valid User ID and Password returns the code 0 with a corresponding LicenseStatus value of Valid license key. LicenseStatus: This field returns the status of the StrikeIron User ID and Password corresponding to the LicenseStatusCode. Sample Output 0 Valid license key LicenseActionCode: This field returns a numeric code indicating the StrikeIron license action taken as a result of invoking this operation. GetRemainingHits returns the code 5 with a corresponding LicenseAction value of Get remaining hits. LicenseAction: This field returns the license action taken as a result of invoking this operation from the User ID and Password used corresponding to the LicenseActionCode. RemainingHits: This field returns the number of hits against the StrikeIron User ID and Password used when invoking this operation. Amount: This field returns the number of hits used from the StrikeIron User ID provided to invoke this operation. GetRemainingHitsResponse: This field only returns subscription information. InfoKey: A code referencing the web service s current status InfoValue: A description of the web service s current status. 0 Decremented hit count n/a n/s 8

9 GetRemainingHits Returns the number of API calls, hits, remaining for the given License Key. Operation: GetRemainingHits Input (ServiceStatus) Note: The only input needed for this operation is the LicenseInfo data. Sample Input (No input required) Operation: GetRemainingHits Output (ServiceResult) LicenseStatusCode: This field returns a numeric code indicating the StrikeIron license action taken as a result of invoking this operation from the User ID and Password used for input. Valid license codes are 0, 1, and 2. For example, a valid User ID and Password returns the code 0 with a corresponding LicenseStatus value of Valid license key. LicenseStatus: This field returns the status of the StrikeIron User ID and Password corresponding to the LicenseStatusCode. LicenseActionCode: This field returns a numeric code indicating the StrikeIron license action taken as a result of invoking this operation. GetRemainingHits returns the code 5 with a corresponding LicenseAction value of Get remaining hits. LicenseAction: This field returns the license action taken as a result of invoking this operation from the User ID and Password used corresponding to the LicenseActionCode. RemainingHits: This field returns the number of hits against the StrikeIron User ID and Password used when invoking this operation. Amount: This field returns the number of hits used from the StrikeIron User ID provided to invoke this operation. Sample Output 0 Valid license key 0 Decremented hit count 2 0 9

10 WSDL for Automotive Append The WSDL displayed here has been added as a convenience to the reader. Always refer to the latest WSDL definitions at to ensure you are working with the latest version. Methods GetAutoDemographics GetAutoDemographicsBatch GetStatusCodesForMethod GetStatusCodes GetServiceInfo GetRemainingHits WSDL document for namespace " <?xml version="1.0" encoding="utf-16"?> <wsdl:definitions xmlns:soapenc=" xmlns:mime=" xmlns:soap12=" xmlns:tns=" xmlns:soap=" xmlns:s=" xmlns:http=" xmlns:tm=" targetnamespace=" xmlns:wsdl=" <wsdl:types> <s:schema elementformdefault="qualified" targetnamespace=" <s:import namespace=" <s:import namespace=" <s:element name="getautodemographics"> <s:complextype> <s:element minoccurs="1" maxoccurs="1" name="confidence" type="tns:confidencelevel"/> <s:element minoccurs="0" maxoccurs="1" name="request" type="tns:autodatarequest"/> </s:element> <s:simpletype name="confidencelevel"> <s:restriction base="s:string"> <s:enumeration value="specificmatch"/> <s:enumeration value="approximatematch"/> <s:enumeration value="loosematch"/> </s:restriction> </s:simpletype> <s:complextype name="autodatarequest"> <s:element minoccurs="0" maxoccurs="1" name="firstname"

11 <s:element minoccurs="0" maxoccurs="1" name="middlename" <s:element minoccurs="0" maxoccurs="1" name="lastname" <s:element minoccurs="0" maxoccurs="1" name="namesuffix" <s:element minoccurs="0" maxoccurs="1" name="addressline1" <s:element minoccurs="0" maxoccurs="1" name="addressline2" <s:element minoccurs="0" maxoccurs="1" name="city" <s:element minoccurs="0" maxoccurs="1" name="state" <s:element minoccurs="0" maxoccurs="1" name="zip" <s:element minoccurs="0" maxoccurs="1" name="vin" <s:element name="getautodemographicsresponse"> <s:complextype> <s:element minoccurs="0" maxoccurs="1" name="getautodemographicsresult" type="tns:siwsoutputoflookupautodataresult"/> </s:element> <s:complextype name="siwsoutputoflookupautodataresult"> <s:element minoccurs="0" maxoccurs="1" name="servicestatus" type="tns:siwsstatus"/> <s:element minoccurs="0" maxoccurs="1" name="serviceresult" type="tns:lookupautodataresult"/> <s:complextype name="siwsstatus"> <s:element minoccurs="1" maxoccurs="1" name="statusnbr" type="s:int"/> <s:element minoccurs="0" maxoccurs="1" name="statusdescription" <s:complextype name="lookupautodataresult"> <s:element minoccurs="0" maxoccurs="1" name="confidence" <s:element minoccurs="1" maxoccurs="1" name="numrecords" type="s:int"/> <s:element minoccurs="0" maxoccurs="1" name="records" type="tns:arrayoflookupautodataresultrecord"/> <s:complextype name="arrayoflookupautodataresultrecord"> <s:element minoccurs="0" maxoccurs="unbounded" name="record"

12 nillable="true" type="tns:lookupautodataresultrecord"/> <s:complextype name="lookupautodataresultrecord"> <s:element minoccurs="0" maxoccurs="1" name="matchlevel" <s:element minoccurs="0" maxoccurs="1" name="firstname" <s:element minoccurs="0" maxoccurs="1" name="middlename" <s:element minoccurs="0" maxoccurs="1" name="lastname" <s:element minoccurs="0" maxoccurs="1" name="namesuffix" <s:element minoccurs="0" maxoccurs="1" name="address" <s:element minoccurs="0" maxoccurs="1" name="city" <s:element minoccurs="0" maxoccurs="1" name="state" <s:element minoccurs="0" maxoccurs="1" name="zip" <s:element minoccurs="0" maxoccurs="1" name="zip4" <s:element minoccurs="0" maxoccurs="1" name="vin" <s:element minoccurs="0" maxoccurs="1" name="autoyear" <s:element minoccurs="0" maxoccurs="1" name="make" <s:element minoccurs="0" maxoccurs="1" name="model" <s:element minoccurs="0" maxoccurs="1" name="transactiondate" <s:element minoccurs="0" maxoccurs="1" name="phone" <s:element name="getautodemographicsbatch"> <s:complextype> <s:element minoccurs="1" maxoccurs="1" name="confidence" type="tns:confidencelevel"/> <s:element minoccurs="0" maxoccurs="1" name="requests" type="tns:arrayofautodatarequest"/> </s:element> <s:complextype name="arrayofautodatarequest"> <s:element minoccurs="0" maxoccurs="unbounded" name="autodatarequest" nillable="true" type="tns:autodatarequest"/> <s:element name="getautodemographicsbatchresponse"> <s:complextype> <s:element minoccurs="0" maxoccurs="1" name="getautodemographicsbatchresult"

13 type="tns:siwsoutputofsiwsresultarrayoflookupautodataresultwithstatus"/> </s:element> <s:complextype name="siwsoutputofsiwsresultarrayoflookupautodataresultwithstatus"> <s:element minoccurs="0" maxoccurs="1" name="servicestatus" type="tns:siwsstatus"/> <s:element minoccurs="0" maxoccurs="1" name="serviceresult" type="tns:siwsresultarrayoflookupautodataresultwithstatus"/> <s:complextype name="siwsresultarrayoflookupautodataresultwithstatus"> <s:element minoccurs="0" maxoccurs="1" name="results" type="tns:arrayoflookupautodataresultwithstatus"/> <s:complextype name="arrayoflookupautodataresultwithstatus"> <s:element minoccurs="0" maxoccurs="unbounded" name="lookupautodataresultwithstatus" nillable="true" type="tns:lookupautodataresultwithstatus"/> <s:complextype name="lookupautodataresultwithstatus"> <s:complexcontent mixed="false"> <s:extension base="tns:siwsresultwithstatus"> <s:element minoccurs="0" maxoccurs="1" name="result" type="tns:lookupautodataresult"/> </s:extension> </s:complexcontent> <s:complextype name="siwsresultwithstatus" abstract="true"> <s:element minoccurs="0" maxoccurs="1" name="itemstatus" type="tns:siwsstatus"/> <s:element name="getstatuscodesformethod"> <s:complextype> <s:element minoccurs="0" maxoccurs="1" name="methodname" </s:element> <s:element name="getstatuscodesformethodresponse"> <s:complextype>

14 <s:element minoccurs="0" maxoccurs="1" name="getstatuscodesformethodresult" type="tns:siwsoutputofmethodstatusrecord"/> </s:element> <s:complextype name="siwsoutputofmethodstatusrecord"> <s:element minoccurs="0" maxoccurs="1" name="servicestatus" type="tns:siwsstatus"/> <s:element minoccurs="0" maxoccurs="1" name="serviceresult" type="tns:methodstatusrecord"/> <s:complextype name="methodstatusrecord"> <s:complexcontent mixed="false"> <s:extension base="tns:siwsresultarrayofsiwsstatus"> <s:element minoccurs="0" maxoccurs="1" name="methodname" </s:extension> </s:complexcontent> <s:complextype name="siwsresultarrayofsiwsstatus"> <s:element minoccurs="0" maxoccurs="1" name="results" type="tns:arrayofsiwsstatus"/> <s:complextype name="arrayofsiwsstatus"> <s:element minoccurs="0" maxoccurs="unbounded" name="siwsstatus" nillable="true" type="tns:siwsstatus"/> <s:element name="getstatuscodes"> <s:complextype/> </s:element> <s:element name="getstatuscodesresponse"> <s:complextype> <s:element minoccurs="0" maxoccurs="1" name="getstatuscodesresult" type="tns:siwsoutputofsiwsresultarrayofmethodstatusrecord"/> </s:element> <s:complextype name="siwsoutputofsiwsresultarrayofmethodstatusrecord"> <s:element minoccurs="0" maxoccurs="1" name="servicestatus" type="tns:siwsstatus"/> <s:element minoccurs="0" maxoccurs="1" name="serviceresult" type="tns:siwsresultarrayofmethodstatusrecord"/>

15 <s:complextype name="siwsresultarrayofmethodstatusrecord"> <s:element minoccurs="0" maxoccurs="1" name="results" type="tns:arrayofmethodstatusrecord"/> <s:complextype name="arrayofmethodstatusrecord"> <s:element minoccurs="0" maxoccurs="unbounded" name="methodstatusrecord" nillable="true" type="tns:methodstatusrecord"/> <s:element name="getserviceinfo"> <s:complextype/> </s:element> <s:element name="getserviceinforesponse"> <s:complextype> <s:element minoccurs="0" maxoccurs="1" name="getserviceinforesult" type="tns:siwsoutputofsiwsresultarrayofserviceinforecord"/> </s:element> <s:complextype name="siwsoutputofsiwsresultarrayofserviceinforecord"> <s:element minoccurs="0" maxoccurs="1" name="servicestatus" type="tns:siwsstatus"/> <s:element minoccurs="0" maxoccurs="1" name="serviceresult" type="tns:siwsresultarrayofserviceinforecord"/> <s:complextype name="siwsresultarrayofserviceinforecord"> <s:element minoccurs="0" maxoccurs="1" name="results" type="tns:arrayofserviceinforecord"/> <s:complextype name="arrayofserviceinforecord"> <s:element minoccurs="0" maxoccurs="unbounded" name="serviceinforecord" nillable="true" type="tns:serviceinforecord"/> <s:complextype name="serviceinforecord"> <s:element minoccurs="0" maxoccurs="1" name="infokey" <s:element minoccurs="0" maxoccurs="1" name="infovalue"

16 </s:schema> <xs:schema xmlns:tns1=" attributeformdefault="unqualified" elementformdefault="qualified" targetnamespace=" xmlns:xs=" <xs:import namespace=" <xs:import namespace=" <xs:element name="licenseinfo" type="tns1:licenseinfo"/> <xs:complextype name="licenseinfo"> <xs:sequence> <xs:element minoccurs="0" name="unregistereduser" type="tns1:unregistereduser"/> <xs:element minoccurs="0" name="registereduser" type="tns1:registereduser"/> </xs:sequence> </xs:complextype> <xs:complextype name="unregistereduser"> <xs:sequence> <xs:element minoccurs="0" name=" address" type="xs:string"/> </xs:sequence> </xs:complextype> <xs:complextype name="registereduser"> <xs:sequence> <xs:element minoccurs="0" name="userid" type="xs:string"/> <xs:element minoccurs="0" name="password" type="xs:string"/> </xs:sequence> </xs:complextype> <xs:element name="subscriptioninfo" type="tns1:subscriptioninfo"/> <xs:complextype name="subscriptioninfo"> <xs:sequence> <xs:element name="licensestatuscode" type="xs:int"/> <xs:element minoccurs="0" name="licensestatus" type="xs:string"/> <xs:element name="licenseactioncode" type="xs:int"/> <xs:element minoccurs="0" name="licenseaction" type="xs:string"/> <xs:element name="remaininghits" type="xs:int"/> <xs:element name="amount" type="xs:decimal"/> </xs:sequence> </xs:complextype> <xs:element name="getremaininghits"> <xs:complextype/> </xs:element> <xs:element name="getremaininghitsresponse"> <xs:complextype/> </xs:element> </xs:schema> </wsdl:types> <wsdl:message name="getautodemographicssoapin"> <wsdl:part name="parameters" element="tns:getautodemographics"/> <wsdl:message name="getautodemographicssoapout"> <wsdl:part name="parameters" element="tns:getautodemographicsresponse"/>

17 <wsdl:message name="getautodemographicsbatchsoapin"> <wsdl:part name="parameters" element="tns:getautodemographicsbatch"/> <wsdl:message name="getautodemographicsbatchsoapout"> <wsdl:part name="parameters" element="tns:getautodemographicsbatchresponse"/> <wsdl:message name="getstatuscodesformethodsoapin"> <wsdl:part name="parameters" element="tns:getstatuscodesformethod"/> <wsdl:message name="getstatuscodesformethodsoapout"> <wsdl:part name="parameters" element="tns:getstatuscodesformethodresponse"/> <wsdl:message name="getstatuscodessoapin"> <wsdl:part name="parameters" element="tns:getstatuscodes"/> <wsdl:message name="getstatuscodessoapout"> <wsdl:part name="parameters" element="tns:getstatuscodesresponse"/> <wsdl:message name="getserviceinfosoapin"> <wsdl:part name="parameters" element="tns:getserviceinfo"/> <wsdl:message name="getserviceinfosoapout"> <wsdl:part name="parameters" element="tns:getserviceinforesponse"/> <wsdl:message name="getremaininghitssoapin"> <wsdl:part xmlns:q1=" name="parameters" element="q1:getremaininghits"/> <wsdl:message name="getremaininghitssoapout"> <wsdl:part xmlns:q2=" name="parameters" element="q2:getremaininghitsresponse"/> <wsdl:message name="licenseinfomessage"> <wsdl:part xmlns:q3=" name="licenseinfo" element="q3:licenseinfo"/> <wsdl:message name="subscriptioninfomessage"> <wsdl:part xmlns:q4=" name="subscriptioninfo" element="q4:subscriptioninfo"/> <wsdl:porttype name="autoappendsoap"> <wsdl:operation name="getautodemographics"> <wsdl:documentation xmlns:wsdl=" auto and demographics data for one person.</wsdl:documentation> <wsdl:input message="tns:getautodemographicssoapin"/> <wsdl:output message="tns:getautodemographicssoapout"/> <wsdl:operation name="getautodemographicsbatch"> <wsdl:documentation xmlns:wsdl=" auto and

18 demographics data for one or more people.</wsdl:documentation> <wsdl:input message="tns:getautodemographicsbatchsoapin"/> <wsdl:output message="tns:getautodemographicsbatchsoapout"/> <wsdl:operation name="getstatuscodesformethod"> <wsdl:documentation xmlns:wsdl=" all status codes a method in the service might return.</wsdl:documentation> <wsdl:input message="tns:getstatuscodesformethodsoapin"/> <wsdl:output message="tns:getstatuscodesformethodsoapout"/> <wsdl:operation name="getstatuscodes"> <wsdl:documentation xmlns:wsdl=" all statuses this service might return.</wsdl:documentation> <wsdl:input message="tns:getstatuscodessoapin"/> <wsdl:output message="tns:getstatuscodessoapout"/> <wsdl:operation name="getserviceinfo"> <wsdl:documentation xmlns:wsdl=" information about the web service</wsdl:documentation> <wsdl:input message="tns:getserviceinfosoapin"/> <wsdl:output message="tns:getserviceinfosoapout"/> <wsdl:operation name="getremaininghits"> <wsdl:input message="tns:getremaininghitssoapin"/> <wsdl:output message="tns:getremaininghitssoapout"/> </wsdl:porttype> <wsdl:binding name="autoappendsoap" type="tns:autoappendsoap"> <soap:binding transport=" <wsdl:operation name="getautodemographics"> <soap:operation soapaction=" style="document"/> <wsdl:input> <soap:header message="tns:licenseinfomessage" part="licenseinfo" </wsdl:input> <wsdl:output> <soap:header message="tns:subscriptioninfomessage" part="subscriptioninfo" </wsdl:output> <wsdl:operation name="getautodemographicsbatch"> <soap:operation soapaction=" style="document"/> <wsdl:input> <soap:header message="tns:licenseinfomessage" part="licenseinfo"

19 </wsdl:input> <wsdl:output> <soap:header message="tns:subscriptioninfomessage" part="subscriptioninfo" </wsdl:output> <wsdl:operation name="getstatuscodesformethod"> <soap:operation soapaction=" style="document"/> <wsdl:input> <soap:header message="tns:licenseinfomessage" part="licenseinfo" </wsdl:input> <wsdl:output> <soap:header message="tns:subscriptioninfomessage" part="subscriptioninfo" </wsdl:output> <wsdl:operation name="getstatuscodes"> <soap:operation soapaction=" style="document"/> <wsdl:input> <soap:header message="tns:licenseinfomessage" part="licenseinfo" </wsdl:input> <wsdl:output> <soap:header message="tns:subscriptioninfomessage" part="subscriptioninfo" </wsdl:output> <wsdl:operation name="getserviceinfo"> <soap:operation soapaction=" style="document"/> <wsdl:input> <soap:header message="tns:licenseinfomessage" part="licenseinfo" </wsdl:input> <wsdl:output> <soap:header message="tns:subscriptioninfomessage" part="subscriptioninfo" </wsdl:output>

20 <wsdl:operation name="getremaininghits"> <soap:operation soapaction=" <wsdl:input> <soap:header message="tns:licenseinfomessage" part="licenseinfo" </wsdl:input> <wsdl:output> <soap:header message="tns:subscriptioninfomessage" part="subscriptioninfo" </wsdl:output> </wsdl:binding> <wsdl:service name="autoappend"> <wsdl:port name="autoappendsoap" binding="tns:autoappendsoap"> <soap:address location=" </wsdl:port> </wsdl:service> </wsdl:definitions> Copyright 2015

Candidate Resume Data API

Candidate 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 information

Sales and Use Tax Basic Version 5.0.0

Sales and Use Tax Basic Version 5.0.0 Sales and Use Tax Basic Version 5.. WSDL: http://ws.strikeiron.com/taxdatabasic5?wsdl Product Web Page: http://www.strikeiron.com/catalog/productdetail.aspx?pv=5..&pn=tax+data+systems+sales+and+us e+tax+basic

More information

Calendar Data API. Version gradleaders.com

Calendar 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 information

SMS Alerts and Notifications Version 4.0.0

SMS Alerts and Notifications Version 4.0.0 SMS Alerts and Notifications Version 4.. WSDL: http://ws.strikeiron.com/smsalerts4?wsdl Product Web Page: http://www.strikeiron.com/catalog/productdetail.aspx?pv=4..&pn=sms+alerts+and+notifications Description:

More information

CMS SOAP CLIENT SOFTWARE REQUIREMENTS SPECIFICATION

CMS 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 information

VoiceForge. xmlns:s=" xmlns:soap12="

VoiceForge. 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 information

Development of distributed services - Project III. Jan Magne Tjensvold

Development 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

Support For assistance, please contact Grapevine: or

Support 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 information

Web Service Provider Example - Enabling Visible Business

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 information

Exercise sheet 4 Web services

Exercise 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 information

Preliminary. Database Publishing Wizard Protocol Specification

Preliminary. 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 information

Cisco Prime Central 1.0 API Guide

Cisco 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

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

No 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 information

Case study group setup at catme.org Please respond before Tuesday next week to have better group setup

Case 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 information

[MS-SPLCHK]: SpellCheck Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[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

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

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 information

[MS-RMPR]: Rights Management Services (RMS): Client-to-Server Protocol

[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

Preliminary. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

Preliminary. 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 information

[MS-SSDPWP-Diff]: Database Publishing Wizard Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[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 information

SOA SOA SOA SOA SOA SOA SOA SOA SOA SOA SOA SOA SOA SOA

SOA 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 information

Publications Office. TED Website - Notice Viewer WS Technical Specifications Document - Appendix D - NoticeViewer

Publications 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

Implementation Guide for the ASAP Prescription Monitoring Program Web Service Standard

Implementation 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-OXWSSYNC]: Mailbox Contents Synchronization Web Service Protocol Specification

[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 information

SERVICE ORIE TED COMPUTI G ARCHITECTURE FOR CLIMATE MODELI G

SERVICE 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

IVOA Support Interfaces: Mandatory Interfaces Version 0.3

IVOA 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 information

Distribution List Creation and Usage Web Service Protocol

Distribution 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 information

IVOA Support Interfaces: Mandatory Interfaces Version 0.25

IVOA 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 information

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

No 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 information

Articulation Transfer Clearinghouse Implementation Guide

Articulation 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 information

Development of a Reliable SOA Framework

Development of a Reliable SOA Framework Chapter 4 Development of a Reliable SOA Framework Service-Oriented Architecture (SOA) supersedes the traditional software architecture because of its dynamic nature of service composition. Service is an

More information

WP5: Integration with the Digital Ecosystem platform

WP5: 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

PRELIMINARY. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

PRELIMINARY. 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 information

[MS-OXWMT]: Mail Tips Web Service Extensions. Intellectual Property Rights Notice for Open Specifications Documentation

[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

Dyalog APL SAWS Reference Guide

Dyalog APL SAWS Reference Guide The tool of thought for expert programming Dyalog APL SAWS Reference Guide SAWS Version 1.4 Dyalog Limited Minchens Court, Minchens Lane Bramley, Hampshire RG26 5BH United Kingdom tel: +44(0)1256 830030

More information

X-Road: Protocol for Management Services

X-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 information

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

No 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 information

@WebService OUT params via javax.xml.ws.holder

@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 information

Data Pump User Guide

Data 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 information

SOAP Primer for INSPIRE Discovery and View Services

SOAP Primer for INSPIRE Discovery and View Services SOAP Primer for INSPIRE Discovery and View Services Matteo Villa, Giovanni Di Matteo TXT e-solutions Roberto Lucchi, Michel Millot, Ioannis Kanellopoulos European Commission Joint Research Centre Institute

More information

Red Hat JBoss Fuse 6.0

Red 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 information

SOAP 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. 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-OXWOOF]: Out of Office (OOF) Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[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

OpenHealth. A Framework for the Delivery of CCR-based Services

OpenHealth. 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 information

[MS-OXWSBTRF]: Bulk Transfer Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[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 information

Openbravo WebServices

Openbravo WebServices Openbravo WebServices External Point Of Sale 16 August 2006 Revision 1.1 Visit us at www.openbravo.com Table of Contents I.Introduction... 3 II.Product definition... 4 II.1Product type... 4 II.2Category

More information

@WebService handlers

@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 information

Web Services in.net (7)

Web Services in.net (7) Web Services in.net (7) These slides are meant to be for teaching purposes only and only for the students that are registered in CSE4413 and should not be published as a book or in any form of commercial

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 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 information

Supplier Web Services (Full)

Supplier Web Services (Full) Supplier Web Services (Full) All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or

More information

Developing 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 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 information

Extensible Markup Language Processing

Extensible 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 information

User Manual. 3-Heights Document Converter API. Version 4.10

User Manual. 3-Heights Document Converter API. Version 4.10 User Manual 3-Heights Document Converter API Version 4.10 Contents 1 Introduction........................................................................ 3 1.1 Interfaces...........................................................................

More information

Creating simulation-based training tools for customer relationship management with serviceoriented

Creating simulation-based training tools for customer relationship management with serviceoriented Eastern Michigan University DigitalCommons@EMU Master's Theses and Doctoral Dissertations Master's Theses, and Doctoral Dissertations, and Graduate Capstone Projects 2011 Creating simulation-based training

More information

About 1. Chapter 1: Getting started with soap 2. Remarks 2. Versions 2. Examples 2. General Information 2 SOAP 3

About 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 information

Preliminary. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

Preliminary. 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 information

The following is a sample XML code from the HCSProductCatalog.wsdl file.

The 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 information

How to implement Heros Web Services

How 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 information

Web Service Architecture for Computer-Adaptive Testing on e-learning

Web Service Architecture for Computer-Adaptive Testing on e-learning Web Service Architecture for Computer-Adaptive Testing on e-learning M. Phankokkruad, K. Woraratpanya Abstract This paper proposes a Web service and serviceoriented architecture (SOA) for a computer-adaptive

More information

Media Object Server Protocol v Table of Contents

Media Object Server Protocol v Table of Contents Media Object Server (MOS ) Media Object Server Protocol v3.8.3 Table of Contents 3.2.6 4. Other messages and data structures 4.1. Other messages and data structures 4.1.1. heartbeat - Connection Confidence

More information

Port AdonisPort Port type Source code

Port AdonisPort Port type Source code Target Namespace: urn:adonis Port AdonisPort Port type Location: http://adonis.u-psud.fr/ws/serveur.php Protocol: SOAP Default style: rpc Transport protocol: SOAP over HTTP Operations: 1. 2. 3. 4. 5. 6.

More information

Message and Service Definitions

Message 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

:PRIA_DOCUMENT_v2_4_1.XSD

:PRIA_DOCUMENT_v2_4_1.XSD ==================================================================

More information

Web Services in.net (6)

Web Services in.net (6) Web Services in.net (6) These slides are meant to be for teaching purposes only and only for the students that are registered in CSE4413 and should not be published as a book or in any form of commercial

More information

Artix ESB. Developing Artix Applications with JAX-WS. Making Software Work Together. Version 5.0 July 2007

Artix 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 information

Wind Plant Operator Data Guide

Wind Plant Operator Data Guide GUIDE 9 Deleted: Forecast Wind Plant Operator Data Guide June 2010 Deleted: July April Deleted: 08 Version: 1.1 Revision Date: 06/15/2010 Deleted: 0 Deleted: 7 Deleted: 8 Deleted: 08 This document was

More information

BaswareONE SOAP interface

BaswareONE SOAP interface BaswareONE SOAP interface 2 20 Index 1 Introduction... 4 2 Authentication... 4 3 Scenario s with message flows... 4 3.1 Synchronous upload of files to BaswareONE... 4 3.1.1 Without signing the file...

More information

The Florida State University College of Arts and Sciences. WSDL Importer. Kiran Kaja. Major Professor: Dr. Robert van Engelen

The Florida State University College of Arts and Sciences. WSDL Importer. Kiran Kaja. Major Professor: Dr. Robert van Engelen The Florida State University College of Arts and Sciences WSDL Importer By Kiran Kaja Major Professor: Dr. Robert van Engelen A project submitted to the department of Computer Science in partial fulfillment

More information

TPF Users Group Fall 2007

TPF 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 information

Java and XML. XML documents consist of Elements. Each element will contains other elements and will have Attributes. For example:

Java and XML. XML documents consist of Elements. Each element will contains other elements and will have Attributes. For example: Java and XML XML Documents An XML document is a way to represent structured information in a neutral format. The purpose of XML documents is to provide a way to represent data in a vendor and software

More information

[MS-OXWSMSHR]: Folder Sharing Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[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 information

Introduction to Web Service

Introduction to Web Service Introduction to Web Service Sagara Gunathunga ( Apache web Service and Axis committer ) CONTENTS Why you need Web Services? How do you interact with on-line financial service? Conclusion How do you interact

More information

Artix Developing Artix Applications with JAX-WS and JAX-RS

Artix Developing Artix Applications with JAX-WS and JAX-RS Artix 5.6.3 Developing Artix Applications with JAX-WS and JAX-RS Micro Focus The Lawn 22-30 Old Bath Road Newbury, Berkshire RG14 1QN UK http://www.microfocus.com Copyright Micro Focus 2015. All rights

More information

Developing Interoperable Web Services for the Enterprise

Developing Interoperable Web Services for the Enterprise Developing Interoperable Web Services for the Enterprise Simon C. Nash IBM Distinguished Engineer Hursley, UK nash@hursley.ibm.com Simon C. Nash Developing Interoperable Web Services for the Enterprise

More information

Processing on-demand WPS Extension (WPS-G) Specification

Processing on-demand WPS Extension (WPS-G) Specification Open Geospatial Consortium Inc. Date: 2011-12-09 Reference number of this document: Version: 0.1.0 (Draft) Category: OGC Discussion Paper Editors: Patrick Jacques, Christophe Noël Processing on-demand

More information

[MS-OXWSMTRK]: Message Tracking Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[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 information

InForm Clinical Data API Guide

InForm Clinical Data API Guide InForm Clinical Data API Guide Oracle Health Sciences InForm 6.1 Part Number: E51806-01 Copyright 2014, Oracle and/or its affiliates. All rights reserved. The Programs (which include both the software

More information

XML Key Management Specification Bulk Operation (X-BULK)

XML Key Management Specification Bulk Operation (X-BULK) . For further information, contact: xbulk@research.baltimore.com XML Key Management Specification Bulk Operation (X-BULK).......... Baltimore Technologies Gemplus Oberthur Card Systems Schlumberger Draft

More information

User Management Interfaces for Earth Observation Services

User Management Interfaces for Earth Observation Services Open Geospatial Consortium Inc. Date: 208-04-23 Reference number of this OGC project document: 07-118r1 Version: 0.0.2 Category: OGC Interoperability Program Report Editors: R.Smillie, A.Cucumel SPACEBEL

More information

QosPolicyHolder:1 Erratum

QosPolicyHolder: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

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

No 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

Oracle Hospitality OPERA Exchange Interface Profile Lookup Vendor Specification. May 2018

Oracle Hospitality OPERA Exchange Interface Profile Lookup Vendor Specification. May 2018 Oracle Hospitality OPERA Exchange Interface Profile Lookup Vendor Specification May 2018 Copyright 2004, 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation

More information

Tutorial-AXIS-Camel. Tutorial using Axis 1.4 with Apache Camel. Prerequisites. Distribution. Introduction. Setting up the project to run Axis.

Tutorial-AXIS-Camel. Tutorial using Axis 1.4 with Apache Camel. Prerequisites. Distribution. Introduction. Setting up the project to run Axis. Tutorial-AXIS-Camel Tutorial using Axis 1.4 with Apache Camel Removed from distribution This example has been removed from Camel 2.9 onwards. Apache Axis 1.4 is a very old and unsupported framework. We

More information

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. [MS-ASCNTC]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,

More information

Pattern/Object Markup Language (POML): A Simple XML Schema for Object Oriented Code Description

Pattern/Object Markup Language (POML): A Simple XML Schema for Object Oriented Code Description Pattern/Object Markup Language (POML): A Simple XML Schema for Object Oriented Code Description Jason McC. Smith Apr 7, 2004 Abstract Pattern/Object Markup Language (or POML) is a simple XML Schema for

More information

[MS-OXWSGTZ]: Get Server Time Zone Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[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

TECNOLOGIAS DE MIDDLEWARE

TECNOLOGIAS DE MIDDLEWARE TECNOLOGIAS DE MIDDLEWARE Introdução ao WSDL. Concretização num Projecto de LBS. 18/11/2004 André Barbosa WSDL-SUMÁRIO SUMÁRIO DA APRESENTAÇÃO INTRODUÇÃO AO WSDL: Introdução ao WSDL Descrição e Utilização

More information

SLIC Web Service API Guide

SLIC Web Service API Guide SLIC Web Service API Guide Version: 4.4.1 September 28, 2012 Revision History Date Version Description Author 2002 1.0 October 2003 2.0 February 2007 3.0 Initial release of this document Revised to include

More information

Vocera Messaging Platform API Guide. Version 5.2.3

Vocera Messaging Platform API Guide. Version 5.2.3 Vocera Messaging Platform API Guide Version 5.2.3 Notice Copyright 2002-2018 Vocera Communications, Inc. All rights reserved. Vocera is a registered trademark of Vocera Communications, Inc. This software

More information

PTC Integrity 10.7 Web Services Reference

PTC 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 information

MWTM NBAPI WSDL and XSD Definitions

MWTM 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 information

Developing JAX-RPC Web services

Developing 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

Mailbox Contents Synchronization Web Service Protocol

Mailbox Contents Synchronization Web Service Protocol [MS-OXWSSYNC]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,

More information

[MS-RSWSRM2010]: Report Server Web Service for Report Management: ReportService2010

[MS-RSWSRM2010]: Report Server Web Service for Report Management: ReportService2010 [MS-RSWSRM2010]: Report Server Web Service for Report Management: ReportService2010 Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes

More information

Software Developer s Guide for Cisco Secure Access Control System 5.3

Software Developer s Guide for Cisco Secure Access Control System 5.3 Software Developer s Guide for Cisco Secure Access Control System 5.3 November 2012 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel:

More information

Web Services Foundations: SOAP, WSDL and UDDI

Web 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 information