SOAP Web services in BAM

BAM supports the use of Simple Object Access Protocol (SOAP) Web Services.

SOAP web services use the Web Services Description Language (WSDL) standard. The SOAP Web Service implementation consists of:

  • A Web Service Server, created as an entity in the BA diagram.

    A SOAP Web Service Server entity contains the main logic to publish services. It listens for incoming requests and executes the relevant service operation.

    The SOAP Web Service Server requires you to set the Namespace property. When implemented, it generates a .4wsprg file.

  • One or more Web Services, with or without forms. The Web Services are created as entities and linked to the Web Service Server in the BA diagram.

    A standalone SOAP Web Service entity generates a web service with its CRUD operations, but with no accessible form. When implemented, it generates a .4ws file.

    A CRUD form and SOAP Web Service entity generates the code for a CRUD form (a GUI doing create, read, update and delete functionality) and the code for a single standalone Web Service. When implemented, it generates a .4fdmws file.

    A Zoom form and SOAP Web Service entity generates the code for a Zoom form (a GUI supporting read operations only) and the code for a single standalone Web Service. When implemented, it generates a .4fdzws file.

When the BAM entities are implemented, they generate business records.

The Web Service client (consumer) is created outside BAM. See Create a SOAP web service client.

Figure: SOAP Web Services in BAM

This figure is a diagram showing how SOAP Web services work in BAM. The contents are described in the surrounding text.

For more information regarding SOAP Web services, refer to the Genero Business Development Language User Guide.