This is the ABL procedure prototype for the FindCustomerByNum.p external procedure:

ABL procedure prototype

/* FindCustomerByNum.p */

DEFINE INPUT PARAMETER CustomerNumber AS INTEGER. 
DEFINE OUTPUT PARAMETER CustomerName AS CHARACTER.

The boldface elements in this prototype are the main information that ProxyGen maps into the corresponding Web service operation definition. These include the procedure name (filename for an external procedure) and for any parameters, the parameter mode (input or output), names, and data types.

Note: Some information can only be specified in ProxyGen, such as whether the ABL RETURN-VALUE is used and (for external procedures) what Open Client object this operation belongs to.

These are the message section definitions in the RPC/Encoded and RPC/Literal WSDL file for the FindCustomerByNum operation request and response messages:

  <message name="OrderInfo_FindCustomerByNum">
    <part name="CustomerNumber" type="xsd:int"/>
  </message> 
  <message name="OrderInfo_FindCustomerByNumResponse">
    <part name="CustomerName" type="xsd:string"/>
  </message>

Note that the request message contains the input parameter, CustomerNumber, and the response message contains the output parameter, CustomerName, both defined by appropriate XML data types.

This is the definition for the FindCustomerByNum operation in the portType section of the WSDL:

  <portType name="OrderInfoObj">
    <operation name="FindCustomerByNum"
               parameterOrder="CustomerNumber CustomerName">
      <input message="tns:OrderInfo_FindCustomerByNum"/>
      <output message="tns:OrderInfo_FindCustomerByNumResponse"/>
      <fault name="OrderInfoFault" message="tns:FaultDetailMessage"/>
    </operation>
    ...
  </portType>

The portType section defines the object in which the operation is defined, in this case, the AppObject, OrderInfo (as specified in ProxyGen). Note that this definition groups together the request (input) and response (output) messages, along with a generic fault message as part of the operation definition.

This is the definition for the FindCustomerByNum operation in the Bindings section for the OrderInfo AppObject:

  <binding name="OrderInfoObj" type="tns:OrderInfoObj">
    <soap:binding style="rpc"
        transport="http://schemas.xmlsoap.org/soap/http"/>

    <operation name="FindCustomerByNum">
      <soap:operation soapAction="" style="rpc"/>
      <input> 
        <soap:header message="tns:OrderInfoID" part="OrderInfoID"
                  use="encoded" 
                  encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                  namespace="urn:OrderSvc:OrderInfo" wsdl:required="true">
        </soap:header>
        <soap:body use="encoded"
                  encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                  namespace="urn:OrderSvc:OrderInfo"/>
      </input> 
      <output> 
        <soap:body use="encoded"
                  encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                  namespace="urn:OrderSvc:OrderInfo"/>
      </output>
      <fault name="OrderInfoFault"> 
        <soap:fault name="OrderInfoFault" use="encoded"
                  encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                  namespace="http://servicehost:80/wsa/wsa1"/>
      </fault>
    </operation>
    ...
  </binding>

Note that this definition specifies that the transport protocol as SOAP over HTTP, and goes on to define the content for SOAP messages request (input) and response (output) messages for the operation. This is where the object ID definitions are referenced for operations that require them.

This is the port definition in the service section for the object (OrderInfo AppObject) containing the FindCustomerByNum operation:

  <service name="OrderInfoService">
    <port name="OrderInfoObj" binding="tns:OrderInfoObj">
      <documentation/>
      <soap:address location="http://servicehost:80/wsa/wsa1"/>
    </port>
    ...
  </service>

Note that the URL for the web service is specified in soap:address.