• State Not Answered
  • Replies 8 replies
  • Subscribers 5 subscribers
  • Views 3139 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Integrations

I am using the Call Web Service smart service and providing the following WSDL f

kevind605
I am using the Call Web Service smart service and providing the following WSDL for it:
<?xml version="1.0" encoding="ISO-8859-1"?>

<wsdl:definitions xmlns:soap="schemas.xmlsoap.org/.../"
          xmlns:tns="cpilookup.ws.soa.cheth.org"
          xmlns:cm="cpilookup.ws.soa.cheth.org/schema"
          xmlns:xs="www.w3.org/.../XMLSchema"
          xmlns:http="schemas.xmlsoap.org/.../"
          xmlns:wsdl="schemas.xmlsoap.org/.../"
          targetNamespace="cpilookup.ws.soa.cheth.org">

          <!-- Type definitions for input- and output parameters for webservice -->
          <wsdl:types>
                    <xs:schema targetNamespace="cpilookup.ws.soa.cheth.org">
                              <xs:import namespace="cpilookup.ws.soa.cheth.org/schema"
                              schemaLocation="patient_info.xsd"></xs:import>
                              <xs:element name="inputCPILookup">
                                        <xs:complexType>
                                                  <xs:sequence>
                                                            <xs:element type="cm:personInformation" name="person"/>
                                                  </xs:sequence>
                                        </xs:com...

patient_info.xsd

OriginalPostID-97094

OriginalPostID-97094

  Discussion posts and replies are publicly visible

Parents
  • 0
    ...plexType>
                                  </xs:element>
                                  <xs:element name="outputCPILookup">
                                            <xs:complexType>
                                                      <xs:sequence>
                                                                <xs:element type="xs:string" name="code"/>
                                                      </xs:sequence>
                                            </xs:complexType>
                                  </xs:element>
                        </xs:schema>
              </wsdl:types>

              <!-- Message definitions for input and output -->
              <wsdl:message name="inputCPILookup">
                        <wsdl:part name="in" element="tns:inputCPILookup"/>
              </wsdl:message>
              <wsdl:message name="outputCPILookup">
                        <wsdl:part name="out" element="tns:outputCPILookup"/>
              </wsdl:message>

              <!-- Port (interface) definitions -->
              <wsdl:portType name="CPILookupEndpoint">
                        <wsdl:operation name="CPILookup">
                                  <wsdl:input message="tns:inputCPILookup"/>
                                  <wsdl:output message="tns:outputCPILookup"/>
                        </wsdl:operation>
              </wsdl:portType>

              <!-- Port bindings to transports and encoding - HTTP, document literal encoding is used -->
              <wsdl:binding name="CPILookupBinding" type="tns:CPILookupEndpoint">
                        <soap:binding tran...
Reply
  • 0
    ...plexType>
                                  </xs:element>
                                  <xs:element name="outputCPILookup">
                                            <xs:complexType>
                                                      <xs:sequence>
                                                                <xs:element type="xs:string" name="code"/>
                                                      </xs:sequence>
                                            </xs:complexType>
                                  </xs:element>
                        </xs:schema>
              </wsdl:types>

              <!-- Message definitions for input and output -->
              <wsdl:message name="inputCPILookup">
                        <wsdl:part name="in" element="tns:inputCPILookup"/>
              </wsdl:message>
              <wsdl:message name="outputCPILookup">
                        <wsdl:part name="out" element="tns:outputCPILookup"/>
              </wsdl:message>

              <!-- Port (interface) definitions -->
              <wsdl:portType name="CPILookupEndpoint">
                        <wsdl:operation name="CPILookup">
                                  <wsdl:input message="tns:inputCPILookup"/>
                                  <wsdl:output message="tns:outputCPILookup"/>
                        </wsdl:operation>
              </wsdl:portType>

              <!-- Port bindings to transports and encoding - HTTP, document literal encoding is used -->
              <wsdl:binding name="CPILookupBinding" type="tns:CPILookupEndpoint">
                        <soap:binding tran...
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.