The client/server entities

You use these entities to describe and automatically generate client/server applications.

If the Clients are in textual mode (TUI), they are created and managed with the Client-type Screen entity in Rational® Programming Patterns. The Servers are developed with the Business Component-type Server entity. They are directly called from the Clients. The Screens and Servers are gathered in Dialogs that contain common options and characteristics.

If the Clients are graphic, they are created and managed in the graphic development tool. The Servers are developed with the Business Component-type Server entity in Rational Programming Patterns. They must be generated as proxies that the Client will use to remotely activate the services of the Business Components from the graphical application. Other entities are also used, depending on the applications.
  • If the application handles only one Logical View, the single-view proxy that is generated from the Business Component requires the generation of the associated service manager. This service manager is a purely technical component that must not be modified. It is automatically generated (in version 9.6 and higher) if the -GO Lines of the Business Component contain the LOCATION option and do not contain SRVMGR=NO. You must also generate the COBOL code of the Business Component and Communication Monitor.
  • If the application handles several Logical Views, the Business Components and their associated Logical Views must be gathered in a Folder. The multi-view proxy that is generated from the Folder manages the exchanges between the various components of the application. You must also generate the COBOL code of the Business Components and Communication Monitor. One or more Folder Views can be optionally defined to create partial views of the Folder.

Feedback