The purpose of these entities is to develop and generate the server-side components of Pacbench C/S graphic or TUI applications.
The Server Dialog is a logical envelope which groups the various server components of an application.
In the Server Dialog, you give the general characteristics of the application. You specify the generation variants and options which apply by default to all the attached components.
The structure of the service does not depend on the presence or absence of a monitor.
However you must enter the processing specific to the communications technology or the security system in use in each Business Component.
The processing specific to the database management is specified in each service.
The database connection or opening is optionally indicated at the beginning of the Business Component processing.
A monitor groups common information and processing (communications management, compacting, trace, COMMIT/ROLLBACK, site-specific features). For some platforms, like MICRO FOCUS and TUXEDO, using a monitor is a requirement.
However, some requirements of the application (confidentiality, data encryption) or technical constraints (communication protocols) require the use of an architecture with a monitor program. The monitor option makes it easier to interface with your own communication method and to insert data security and encryption/decryption processing.A Business Component supports a set of services on a Logical View.
These services can be generic and dedicated to selections and updates on a Logical View. They can also be specific and support functional requirements.
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 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 generates the messages associated with the errors detected by the Business Components. These messages are stored in a dedicated and generated file.
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 statements that 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.
For the instances imported from Pacbase, the skeleton language of the local generation is identical to the Pacbase skeleton language. This piece of information is retrieved from the extraction of the Pacbase models and from the import. It is stored in the Library.