Web services server program deployment

Introduction

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:

GAS configuration

For deployment, the GWS Server application must be added to the GAS configuration. See Adding Applications in the GAS manual.

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

Note: 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.


Diagram showing path from client to web server to GAS dispatcher to GWS Proxy to DVMs to Database server (and back)

Figure 1. Deployment strategy

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

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:

http://host_name/ws/r/app_id
  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.