Server Reference Guide > Server Reference Guide > ASOLib--OpenROAD Server Library > How an Application Container Works
Was this helpful?
How an Application Container Works
An entire OpenROAD Server application can be deployed within a runtime container. This is a logical container implicitly created when exposed user class methods and regular procedures are wrapped with GSCPs.
In such a case, any client accessing the application must go through the GSCP layer, which means that functions such as security and audit, usage profiling, error logging, tracing, and so on, can be implemented at the container level, independent of core application functionality.
In addition, an application exposed through GSCPs also benefits from automatic XML input/output and automated OSCA error handling.
Two containers are implemented:
• The first is a system container reserved for use by Ingres-authored tools, utilities, and other functions.
• The second is a container for use by the 4GL developer. Its use is described in the following subsections: Entry Processing, Exit Processing, and Error Processing.
Last modified date: 12/20/2023