Back to Contents

Deployment

Topics

• Deployment overview
• Deployment example

Deployment overview

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 SOAP requests amongst the available virtual machines
• Runtime monitoring

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

You can:

• Create a GWS Server application that contains a single Web Service. This application could 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 communication with multiple GWS DVMs, and manage the load balancing.
• Create a GWS Server application that contains multiple Web Services.  The GWSproxy would manage the client requests, dispatching the request to the appropriate DVM and the appropriate web service.

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

Back to the top

Deployment example

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

• 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 manual.

Example

Accessing a Genero Web Service over the internet:

http://webserver_host_name/ws/r/app_id/service_name

Back to the top