Web Services with GeneXus

Unofficial Content

Read the same content in Spanish

The following page describes Web Service's general concepts and how to work with them using GeneXus.

Provider

This is the Web Service itself.

To build a Provider using GeneXus you have to create a Procedure objectData Provider object or a Transaction set as Business Component with the following properties:


Once the Procedure (or Data Provider or Business Component Transaction) is compiled it is ready to be consumed by any application (developed with GeneXus or not).

GeneXus generated Web Services always expose a method execute(). Input and outputs are specified using the parm() rule in the Procedure.

It may also provide a Web Service using  Business component as Web Service  or Data Provider as Web Service.

WSDL

GeneXus generates this. When you specify and compile an object set as a Web Service, GeneXus also generates the WSDL (Web Service Description Language). If the Web Service is called "GetCustomer" and is available at HTTP://server/baseurl/aGetCustomer.aspx, the WSDL for this procedure is located at HTTP://server/baseurl/aGetCustomer.aspx/?WSDL

Consumer

It is possible with GeneXus to consume an external Web Service (developed by a third party with GeneXus or any other tool). To do this please refer to:

After that, the Web Service could be invoked using the external object like any other data type). If it is necessary a Structured Data Type (SDT) object would be created, in order to manage the Web Service parameters.


Both options allow GeneXus to import the Web Service definition so that it can be accessed (consumed). If the Web Service is defined in the same KB it can be called with a simple call().

See Also


Note: This page was created by the Collaborative Project WebServices-FENIX/MX1 WebServices-FENIX/MX1