• SOAP web services (presented on this page).
• REST web services. For more details, see Creating a REST web service.

• Web services deployed on a WEBDEV Application Server (compatible with all the Web servers).
• Numerous web service deployment options (HTTP, FTP, Cloud).
• Heavy workload possible.
• Web services that can operate on all the Windows versions (32 and 64 bits) as well as in Linux.

1. Creating a SOAP web service.
2. Generate a SOAP web service.
3. SOAP Webservice deployment on a WEBDEV Application Server.

1. Create a web service SOAP WINDEV or WEBDEV project, or a web service SOAP configuration in an existing project.
   • When creating a project, select "SOAP or REST web service".
     
     Then select "SOAP Webservice".
   • To create a SOAP webservice project configuration, in the "Project Explorer" pane, open the "Configurations" context menu and select "New configuration". In the wizard that launches, select "SOAP or REST web service" then "SOAP web service".
2. Create one or more sets of procedures:
   • In the "Project Explorer" pane, select the "Procedures" folder.
   • Select "New" in the context menu..
     
     
3. Create the global procedures or the functions corresponding to the processes that must be performed on the server.
   

   // Procédure globale Addition
   PROCEDURE Addition(nNombre1 is int, nNombre2 is int)
   
   nRésultat is int
   nRésultat = nNombre1 + nNombre2
   
   RETURN nRésultat

   
   Each global procedure can be run by the WEBDEV Application Server.
   
   Remarks:
   • Parameter typing If Procedure parameters are not typed, they will automatically be received as Unicode character strings. Therefore, you must specify the type of the parameters that must be different from a Unicode character string.
   • Scope of procedures The procedures can be public, restricted or private.
     • A public procedure can be used in projects that import the SOAP webservice.
     • A private procedure cannot be used in projects that import the SOAP web service (the procedure will not be visible in the "Project Explorer" pane).
     • A restricted procedure can be used throughout the project, but will not be exported when a web service or external Component is generated.
     Note: It is possible to specify the scope of a procedure:
     • when creating the procedure.
     • via the Procedure context menu in the "Project Explorer" pane.
   • Return value Procedures can return classes, structures, arrays of structures or arrays of classes. The returned arrays are limited to one dimension.
   Attention The SOAP web service must have no GUI/UI (no window, status, trace window or dialog box). It is also limited by the rights defined on the Web server ("Internet guest" account in Windows).
4. Type (if necessary) the initialization code and the project closing code. These two codes will be respectively run when loading and when unloading the library of the web service.

Using an HFSQL database

• To simply copy a record from an HFSQL data file to a structure or object, use the FileToMemory function.
• To simply copy the contents of an HFSQL data file into a structure or object, use the FileToArray function.
• To easily create classes corresponding to database files, use the "Project Explorer" pane:
  1. Select the required data file.
  2. From the context menu, select "Generate template class".

1. If necessary, select the configuration corresponding to the SOAP web service via the "Project Explorer" pane.
2. Generate the SOAP web service:
   • On the "Project" tab, in the "Generation" group, click "Generate".
   • Click the generation icon in the quick access buttons.
     
3. The SOAP webservice generation wizard is launched.
4. In the wizard, specify:
   • the name of the web service. By default, the web service name corresponds to the name of the current project. You can change the name of the web service (the project name will not change).
   • the mode for passing parameters to the functions.
     Note: It is advisable to use direct function settings.
5. Go to the next step.
6. Select the elements that will be included in the web service. This excludes all UI elements (window, page, report, etc.).
   
   Check the elements to include and the ones that will be called in the web service. You can:
   • Add elements
     Any type of file can be added to the list of items inserted in the library: images, text files, etc.
   • Delete elements
     The corresponding files and their dependencies will be ignored in the library.
   • Create the web service from an existing description (*.WDU file)
     When creating a WINDEV library, a ".WDU" file with the same name is automatically created. This file contains all the references of the elements included in the library.
7. Go to the next step.
8. Check the accessible elements. The accessible elements correspond to the procedures that contain functions visible by the client application that calls the web service.
   
   
   Warning If you make a collection of procedures accessible, all global procedures belonging to this collection will be accessible. Two methods can be used to hide some procedures:
   • include these procedures in a specific set and do not make this set accessible.
   • use the word PRIVE to make the procedure inaccessible (syntax: PROCEDURE PRIVE MaProc()). For more details, see Global procedures.
9. Complete the wizard to generate the SOAP web service.
10. The deployment wizard automatically opens.

Deploying a web service

There are several deployment methods:

• Deploy web service to a remote WEBDEV Application Server.
• Deploy web service to the cloud for PC SOFT applications.
• Deploy web service to PC SOFT test hosting service.
• Create a remote deployment package.
• Create installation media.
• Deploy web service to the local computer.
• Creating a web service docker image.