public interface Server extends AbstractDialogServer
Servers belongs to differents categories :
The Business Component
A Business Component runs on the server side of the application and supports a set of services on a Logical View.
These services can be generic and dedicated to selections and updates on the Logical View. They can also be specific and support functional requirements.
The Business Component must perform the processing associated with the selection, check and update services requested by the Logical Views. This processing includes:
Access to the external resources (files, databases),
Checks and updates,
Specific processing (calculations, extraction methods...),
Error management.
Generic services are independent of the storage medium used to manage their persistence.
A Business Component then describes the relations between a Logical View and the persistence objects used to select or update its instances.
The server monitor
This monitor, reserved for TUI applications. performs the following tasks. It:
Receives the information sent by the client using the communication area,
Calls the server which corresponds to the service requested by the client,
Returns the information to the client monitor.
The communication monitor
This monitor, reserved for graphic applications, performs the following tasks. It:
Handles the communication functions (message sending and receiving) according to the target environment.
Note: If an application is run on different environments, there must be as many communication monitors as there are environments. Several communication protocols can be used for the same environment (example: CICS ECI and CICS CPIC).
Checks each received message.
Controls the sending/receiving of the query.
Note: According to the size allowed for the physical message, several physical messages sometimes need to be issued in order to obtain the complete logical message. A work file must therefore be available for a temporary storage of the current query.
When the query is completely received, sequential processing of its services by successive calls to the corresponding Services Manager.
Handles the transactional management (COMMIT/ROLLBACK)
The communication monitor uses the COMMIT and ROLLBACK services of a database or of a transactional monitor, depending on its generation variant.
The server part runs a COMMIT or a ROLLBACK, according to the error context (protocol error or application error) established at the end of the query processing. If an error occurs, the query processing is stopped and an error message is sent. All the resources used by the query processing are then made available after the response has been sent.
The error message server
The error message server generates the messages associated with the errors detected by the Business Components. These messages are stored in a dedicated and generated file.
The initialization/termination Business Component
An initialization/termination Business Component is used to implement specific procedures before and after the execution of a request associated with a Folder.
Note: This functionality is then only available for graphic applications which use a Folder.
An I/T Component is called by the Services Manager before the first call to the Business Component associated with the request and after the last-executed Business Component.
It is available either for an Initialization or for a termination process.
For an initialization process, the only data that can be processed in input is that sent by the client component through the user buffer.
An I/T Component is used to run the services associated with all the Business Components of a Folder.
Therefore, the generation of an I/T Component contains the access functions and PERFORM which correspond to the services associated with all the Business Components of a Folder.
Each service associated with a node uses specific parameters in input and produces results defined in the WORKING-STORAGE SECTION of the I/T Component.
Modifier and Type | Field and Description |
---|---|
static java.lang.String |
copyright |
Modifier and Type | Method and Description |
---|---|
DialogServer |
getDialogServer() |
java.lang.String |
getServerExternalName() |
getCobolFolder, getCobolProject, getCobolType, getCPLines, getCSLines, getDialogServerType, getGELines, getGenerationLibrary, getGGLines, getGOLines, getMapType, getProgramExternalName, getTransactionCode
getGCLines
getCalledEntities, getDescriptionTypes, getDesignId, getKeywords, getLabel, getName, getPackage, getProject, isResolved
static final java.lang.String copyright
DialogServer getDialogServer()
Indicates the Dialog Server linked to the Server.
java.lang.String getServerExternalName()
This is the name of the program that is used in the IDENTIFICATION DIVISION of the generated program and the name of the module in the library of executable modules.