Try OpenEdge Now
skip to main content
Web Services
Creating ABL Clients to Consume OpenEdge SOAP Web Services : Invoking OpenEdge SOAP Web Service Operations from ABL : Preparing to invoke operations : Creating a Web service procedure object
Creating a Web service procedure object
You map the port type to the procedure object using a syntax similar to how you instantiate a remote persistent procedure:

RUN portTypeName[ SET hPortType ]ON SERVER hWebService[ NO-ERROR ].
For an ABL remote persistent procedure, you actually execute the procedure by name persistently; for a Web service port type, you invoke the operation using the name of the port type from the WSDL (portTypeName) that defines the operations you want to run. Otherwise, you can set and access a Web service proxy procedure handle (hPortType) the same way as for a remote persistent procedure. Like an AppServer, you use the server object handle bound to the Web service (hWebService) to indicate the remote location to receive Web service requests.
Note the lack of parameters in this statement. Where you might pass parameters when instantiating a remote persistent procedure, you cannot pass any parameters when creating a Web service procedure object, and the AVM raises an error if you do so.
All other attributes and methods on a Web service procedure object work much like they do for any proxy procedure object. Any attribute or method that has no meaning in the context of a Web service returns the Unknown value (?) or an empty string.
Note: A Web service procedure object supports an additional method, SET-CALLBACK-PROCEDURE( ), that is not used on a proxy procedure object. Callback procedures are internal procedures that access information in a SOAP header. For more information on callback procedures, see Specifying SOAP header callback procedures at run time.