Showing posts with label client. Show all posts
Showing posts with label client. Show all posts

Wednesday, February 8, 2017

Weather or temperature conversion webservice WSDL

<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://webservices.daehosting.com/temperature" name="TemperatureConversions" targetNamespace="http://webservices.daehosting.com/temperature">
<types>
<xs:schema elementFormDefault="qualified" targetNamespace="http://webservices.daehosting.com/temperature">
<xs:element name="CelsiusToFahrenheit">
<xs:complexType>
<xs:sequence>
<xs:element name="nCelsius" type="xs:decimal"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CelsiusToFahrenheitResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="CelsiusToFahrenheitResult" type="xs:decimal"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="FahrenheitToCelsius">
<xs:complexType>
<xs:sequence>
<xs:element name="nFahrenheit" type="xs:decimal"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="FahrenheitToCelsiusResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="FahrenheitToCelsiusResult" type="xs:decimal"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="WindChillInCelsius">
<xs:complexType>
<xs:sequence>
<xs:element name="nCelsius" type="xs:decimal"/>
<xs:element name="nWindSpeed" type="xs:decimal"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="WindChillInCelsiusResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="WindChillInCelsiusResult" type="xs:decimal"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="WindChillInFahrenheit">
<xs:complexType>
<xs:sequence>
<xs:element name="nFahrenheit" type="xs:decimal"/>
<xs:element name="nWindSpeed" type="xs:decimal"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="WindChillInFahrenheitResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="WindChillInFahrenheitResult" type="xs:decimal"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</types>
<message name="CelsiusToFahrenheitSoapRequest">
<part name="parameters" element="tns:CelsiusToFahrenheit"/>
</message>
<message name="CelsiusToFahrenheitSoapResponse">
<part name="parameters" element="tns:CelsiusToFahrenheitResponse"/>
</message>
<message name="FahrenheitToCelsiusSoapRequest">
<part name="parameters" element="tns:FahrenheitToCelsius"/>
</message>
<message name="FahrenheitToCelsiusSoapResponse">
<part name="parameters" element="tns:FahrenheitToCelsiusResponse"/>
</message>
<message name="WindChillInCelsiusSoapRequest">
<part name="parameters" element="tns:WindChillInCelsius"/>
</message>
<message name="WindChillInCelsiusSoapResponse">
<part name="parameters" element="tns:WindChillInCelsiusResponse"/>
</message>
<message name="WindChillInFahrenheitSoapRequest">
<part name="parameters" element="tns:WindChillInFahrenheit"/>
</message>
<message name="WindChillInFahrenheitSoapResponse">
<part name="parameters" element="tns:WindChillInFahrenheitResponse"/>
</message>
<portType name="TemperatureConversionsSoapType">
<operation name="CelsiusToFahrenheit">
<documentation>
Converts a Celsius Temperature to a Fahrenheit value
</documentation>
<input message="tns:CelsiusToFahrenheitSoapRequest"/>
<output message="tns:CelsiusToFahrenheitSoapResponse"/>
</operation>
<operation name="FahrenheitToCelsius">
<documentation>
Converts a Fahrenheit Temperature to a Celsius value
</documentation>
<input message="tns:FahrenheitToCelsiusSoapRequest"/>
<output message="tns:FahrenheitToCelsiusSoapResponse"/>
</operation>
<operation name="WindChillInCelsius">
<documentation>
Windchill temperature calculated with the formula of Steadman
</documentation>
<input message="tns:WindChillInCelsiusSoapRequest"/>
<output message="tns:WindChillInCelsiusSoapResponse"/>
</operation>
<operation name="WindChillInFahrenheit">
<documentation>
Windchill temperature calculated with the formula of Steadman
</documentation>
<input message="tns:WindChillInFahrenheitSoapRequest"/>
<output message="tns:WindChillInFahrenheitSoapResponse"/>
</operation>
</portType>
<binding name="TemperatureConversionsSoapBinding" type="tns:TemperatureConversionsSoapType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="CelsiusToFahrenheit">
<soap:operation soapAction="" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="FahrenheitToCelsius">
<soap:operation soapAction="" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="WindChillInCelsius">
<soap:operation soapAction="" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="WindChillInFahrenheit">
<soap:operation soapAction="" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<binding name="TemperatureConversionsSoapBinding12" type="tns:TemperatureConversionsSoapType">
<soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="CelsiusToFahrenheit">
<soap12:operation soapAction="" style="document"/>
<input>
<soap12:body use="literal"/>
</input>
<output>
<soap12:body use="literal"/>
</output>
</operation>
<operation name="FahrenheitToCelsius">
<soap12:operation soapAction="" style="document"/>
<input>
<soap12:body use="literal"/>
</input>
<output>
<soap12:body use="literal"/>
</output>
</operation>
<operation name="WindChillInCelsius">
<soap12:operation soapAction="" style="document"/>
<input>
<soap12:body use="literal"/>
</input>
<output>
<soap12:body use="literal"/>
</output>
</operation>
<operation name="WindChillInFahrenheit">
<soap12:operation soapAction="" style="document"/>
<input>
<soap12:body use="literal"/>
</input>
<output>
<soap12:body use="literal"/>
</output>
</operation>
</binding>
<service name="TemperatureConversions">
<documentation>
DataFlex Web Service to convert temperature values between Celsius and Fahrenheit
</documentation>
<port name="TemperatureConversionsSoap" binding="tns:TemperatureConversionsSoapBinding">
<soap:address location="http://webservices.daehosting.com/services/TemperatureConversions.wso"/>
</port>
<port name="TemperatureConversionsSoap12" binding="tns:TemperatureConversionsSoapBinding12">
<soap12:address location="http://webservices.daehosting.com/services/TemperatureConversions.wso"/>
</port>
</service>
</definitions>



Wednesday, October 26, 2016

Adding an SFTP client policy



How to add an SFTP client policy to a user agent.
About this task
The user agent controls the client settings for outgoing SFTP connections for requests that match the URL expression. These settings can be further overridden by query parameters in the URL that initiates the file transfer.
Without SFTP client policies, the client authentication settings are controlled by the basic authentication and public key authentication policies.
Availability: These setting are available for only appliances with the B2B feature.
Procedure
  1. In the search field, enter User Agent.
  2. From the search results, click User Agent.
  3. Click the name of a user agent configuration.
  4. Click the SFTP Client Policies tab.
  5. Add a policy.
    1. Click Add.
    2. In the URL Matching Expression field, enter a shell-style expression to be the matching pattern for the URL set.
    3. From the SSH client profile list, select an SSH client profile.
    4. Optional: Set the Use unique file names property to off to disable the generation of a unique file name for puts to a remote directory.
    5. Click Apply.
  6. Optional: Repeat the previous step to add another policy.
  7. Click Apply to save the changes to the running configuration.
  8. Click Save Configuration to save the changes to the persisted configuration.

Adding an SMTP client policy



Adding an SMTP client policy
How to add an SMTP client policy to a user agent.
About this task
Availability: Appliances with the B2B feature.
The user agent controls the client settings for outgoing SMTP connections for requests that match the URL expression. These client settings can be overridden by query parameters in the URL that initiates the mail transfer.
Procedure
  1. In the search field, enter User Agent.
  2. From the search results, click User Agent.
  3. Click the name of a user agent configuration.
  4. Click the SMTP Client Policies tab.
  5. Add a policy.
    1. Click Add.
    2. In the URL Matching Expression field, enter a shell-style expression to be the matching pattern for the URL set.
    3. In the Recipient email field, enter the default email address to which to send email messages.
    4. In the Sender email field, enter the default email address that identifies the sender.
    5. In the Subject field, enter the default subject for email messages.
    6. From the Options list, click the check boxes for the SMTP options to enable.
    7. To use the Simple Authentication and Security Layer (SASL) client authentication: From the Client Authentication list, select the authentication method.
    8. Click Apply.
  6. Optional: Repeat the previous step to add another policy.
  7. Click Apply to save the changes to the running configuration.
  8. Optional: Click Save Configuration to save the changes to the persisted configuration.

Distributed Computing: A Guide to Comparing Data Between Hive Tables Using Spark

In big data, efficient data comparison is essential for ensuring data integrity and validating data migrations. Apache Spark, with its in-me...