GeneXus Evolution 1Today, within the paradigm of Web 2.0, is sought to use fewer and fewer computer resources within a system based on the Scheme Client / Server, in order, that local resources are used only as necessary, making the application is lightweight, yet powerful in its processes, achieving responsiveness almost instantly.

As a solution to this approach was defined using separate processes, making these services, causing the server to resolve and use its resources to generate the result and return a quick response.

Based on the requirements which arise today in the area of IT time is extremely vital, which can not be wasted on redundant processes and also could simplify the use of resources such as memory or processing of the client machines.

Using Web Services in Web applications generated with GeneXus X Evolution 1, is the effective solution to server-side requests, making the computers running the system, only consume resources relevant to its operation, and consuming or calling via a web Services or heavy tedious processes allowing the web server resolves and use its resources, respecting the client.

What does this help? The system does not consume resources such as memory, cache and client processing, avoiding form a bottleneck and thus a core dump on the client side.

Since it is possible to create a service with GeneXus, just a GeneXus procedure with properties:

Main Object=True,
Call Protocol=SOAP.

Environment must be generated on site, and once compiled, it is available to be consumed by any application (GeneXus or not, just KB or not.). The web services generated with GeneXus X Evolution I always expose a method execute (). The data input and output, are those specified in the parm rule () procedure.


In a Patient Care Express, as its name says, 'Express', the response time and processing is vital to the operation, together with what in this process is the price of products, resulting in money and service experience for the customer.

Today, the concept of Promise Date or Delivery Date Results are obtained by a Web Services, which is consumed from within the application, getting an answer instantly, almost to click.

When converting a service procedure, becomes a Web Services based on XML, as we can see:

Web service xml 

Which consume from the application:

web service xml application

web service xml application 2

Appreciating the composition of the external object, we see that preserves the structure of an XML file

xml file

Implementation of real-time service:

Patient Care System

Patient Care System 2

Patient Care System 3

The service resolves in less than 5 seconds, which in an operation with about 1500 users per day, makes the time factor is vital and essential to waste, making the system not only solves a need for the operation, but reduces the response time and optimizes the use of client resources.


comments powered by Disqus