Web services server program deployment

The Genero Application Server (GAS) manages Web services. You must consider GAS configuration when deploying your Web service in a production environment.


In a production environment, Genero Web Services becomes a part of a global application architecture handled by the Genero Application Server (GAS). The GWS DVMs are managed by the GAS.

This architecture takes care of:

  • Security issues
  • Scalability
    • Load management
    • Balancing of the Web service requests amongst the available virtual machines
  • Runtime monitoring

GAS configuration

For deployment, the GWS Server application must be added to the GAS configuration. See Configure applications for Web service in the Genero Application Server User Guide.

The web services application can be added to the GAS in different ways:

  • GWS Server application implementing a single Web service.

    This application can be deployed on various physical machines. A Genero Web Services VMProxy (GWSProxy) is started on each machine where the GWS Server application is executed, to manage the requests for a service and manage the DVMs that handle the requests. A single VMProxy can communicate with multiple GWS DVMs, and manage the load balancing.

  • GWS Server application implementing multiple Web Services.

    The GWSProxy would manage the client requests, dispatching the request to the appropriate DVM and the appropriate web service.

A Web Service Server must be stateless; several instances of the same Service can be created to support load balancing.

The basic deployment strategy can be implemented in varying permutations, depending on your business needs and the volume of requests.

Figure: Deployment strategy

Diagram showing path from client to web server to GAS dispatcher to GWS Proxy to DVMs to Database server (and back)
  • Using the World Wide Web, a Web Service client requests WSDL information for a particular Web Service from the Web Server.

  • The Web Service client uses this information to make a Web Service request from the Web Server.

  • The Web server passes the request to the GAS dispatcher.

  • The GAS dispatcher starts a GWSProxy, which will be in charge of the pool of DVMs that will serve the web service application.

  • The GWSProxy will start the number of DVMs specified by the START element defined for the web service application.

For a more detailed explanation of the Services Pool for web services, refer to the GAS Architecture topic in the Genero Application Server User Guide.

Access the web services server from a client application

To reach the web service from the internet, client applications must use the following URL form:

  1. host-name defines the web server host name where the GAS is running.
  2. app_id is the XCF file of the GAS web services application.